Patent Grant
12062069
Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are incorporated by reference under 37 CFR 1.57 and made a part of this specification.
The present disclosure relates to the field of for-hire vehicles such as taxis, limousines, shuttles, buses or any other vehicle that provides shared transportation or transports one or more passengers between locations of the passengers' choice. The present disclosure also relates to the field of advertising, sales and promotion.
A for-hire vehicle (FHV) generally charges fares for transporting a passenger from one location to another. Some FHVs, such as taxicabs, operate with a meter, while others such as limos and shuttles transport passengers for a pre-trip negotiated rate. FHVs are common in tourist destinations, business traveler destinations (for example, where convention centers are prevalent) or in densely populated urban areas where vehicle ownership is relatively less common or impractical. Areas of high FHV use often offer numerous entertainment options. The entertainment options may include, among other things, shows, plays, concerts, dining, sporting events, or other special events. Travelers, business people and urban dwellers may frequent these entertainment options through the use of a FHV. For example, a business person in town for a convention may wish to dine at a restaurant and may hail a taxi to transport him to the restaurant. Individual service providers, such as taxi drivers, may be consulted for their recommendations regarding entertainment or dining options. Therefore, dining and entertainment venues may desire access to, or contact with, taxi drivers or other service providers in order to increase the likelihood that their goods or services will be recommended.
Many entertainment options are time, location and quantity sensitive; the entertainment options offer a service that is available for a fixed time, at a specific location and only for a fixed number of people. For example, a play may start at 8 PM (fixed time), be performed at the Downtown Theater (specific location) and have 200 seats available (fixed number of people). In some cases, the number of tickets sold for the event is less than the seats available. For example, only 150 tickets may have been sold for the play in the 200 seat venue. As the 8 PM start time approaches, it may become clear to the vendor operating the play at the venue that the remaining 50 seats will not be sold. Once the play starts, any empty seat in the venue is a lost revenue opportunity. Restaurant owners face a similar lost revenue opportunity, even though the restaurant option may not have strictly fixed time. Empty tables at a restaurant, when there is adequate staff to serve the tables, is also a lost revenue opportunity.
Embodiments of the disclosure will now be described with reference to the accompanying figures, wherein like numerals refer to like elements throughout. The terminology used in the description presented herein is not intended to be interpreted in any limited or restrictive manner, simply because it is being utilized in conjunction with a detailed description of certain specific embodiments of the disclosure. Furthermore, embodiments of the disclosure may include several novel features, no single one of which is solely responsible for its desirable attributes or which is essential to practicing the embodiments of the disclosure herein described.
In order for vendors offering entertainment options to maximize their revenue opportunity when dealing with a time, location and quantity sensitive asset, an opportunity arises to advertise, for a short period of time, the entertainment option at a discount. Furthermore, passengers of FHVs are a good target demographic for vendors; passengers are often travelers from out of town and may be looking for interesting and inexpensive entertainment options. The present disclosure recognizes this opportunity and that it is advantageous for vendors to offer discounted rates for their entertainment options to passengers of FHVs as they may be likely to purchase the offer at the discounted rate. Further, additional value may advantageously be added by including the fare to the venue in the discounted rate. It may also be advantageous for drivers of FHVs, or other individuals or entities, to be incentivized to promote offers to their passengers, customers, or whomever is within their sphere of contact. Furthermore, vendors may have an interest in receiving information related to the promotional activities of such individuals or entities. For example, a vendor may wish to provide some sort of benefit or promotional material to a subset of FHV drivers based on transactional or purchase data associated with the drivers' promotional activities.
Accordingly, embodiments of the present disclosure describe systems and methods for integrating product and service discounting with requests for the reservation and dispatch of for-hire vehicles. In one embodiment, a deal manager computer system (or “deal manager”) manages deals offered by vendors and receives promotional offer (or “deal”) data from a vendor computer system. The vendor computer system may advantageously permit the entry of the promotional offer data though the use of a web page or other user interface. Based on the received promotional offer information, the deal manager computer system generates a deal, or offer, which is then communicated to a deal presenter computer system that displays the deal. Once a consumer purchases the deal, the deal manager computer system receives a notification of acceptance of the deal, or promotional offer. The acceptance may include location data and payment data. The deal manager uses the location data to reserve and dispatch an FHV to pick up the person who accepted the deal, or to modify the trip information for a current passenger of an FHV. The deal manager computer system uses the payment information to process payment for the deal. In addition, the deal manager computer system may also communicate a confirmation message to the deal presenter computer system and may communicate a confirmation message to the vendor computer system. The confirmation message to the deal presentation computer system may include a voucher number, code, or scanable image that may be used to validate the deal with the vendor and the driver of the dispatched for-hire vehicle, if necessary. The confirmation message may also include pick-up location information informing the consumer as to where a for-hire vehicle may pick them up. Once the consumer arrives at the venue of the vendor who offered the deal, the vendor may validate the purchased deal
In another embodiment, a deal presenter computer system is installed in a for-hire vehicle. The deal presenter computer system comprises a display that is affixed to the for-hire vehicle and a point-of-sale terminal for accepting payment instruments such as credit cards. The deal presenter computer system receives promotional offers (or “deals”) from a deal manager computer system that manages deals for one or more vendors. The received deals are shown on the display. A consumer (or “user”) may select one or more of the received deals and the deal presenter computer system may accept input indicating an acceptance of the deal. The deal presenter computer system may also accept payment information through the point-of-sale terminal. The promotional offer computer system may then transmit the acceptance and payment information to the deal manager computer system. The deal manager computer system may then process the received payment information and process a notification for the for-hire vehicle. The notification may contain location information associated with the vendor so that the for-hire vehicle computer system (or “trip computer”) may update the trip information associated with the passenger's current trip and route the for-hire-vehicle to the vendor location.
In another embodiment, transactional data relating to the promotional activities of one or more drivers of FHVs (meaning, promoters) is maintained for various purposes. For example, such information may provide a mechanism for determining when and how to compensate promoters for promotional activities. Furthermore, in an embodiment, a system provides a means for vendors to receive transactional data and convey benefits and or promotional information to one or more promoters in response to receiving such data.
Display 103 may be, in some embodiments, a touchscreen that allows for passenger 115 to make input choices by touching display 103. For example, display 103 may generate graphical buttons for viewing another deal, accepting a deal, or inputting personal information upon accepting a deal. In some embodiments, instead of a touchscreen, display 103 may have a separate input device, such as a keyboard, attached to it so that deal presenter 100 may accept user input choices from passenger 115. Examples of the various user interfaces that may be shown on display 103 will be discussed below in greater detail with respect to
When passenger 115 wishes to accept a deal, the passenger may provide input to deal presenter 100 indicating acceptance of the deal. For example, display 103 may be a touchscreen, that generates an “accept” button that passenger 115 touches to accept the deal. By way of further example, deal presenter 100 may comprise an input button housed on the external surface of the deal presenter unit 100 thereby allowing passenger 115 to accept a deal by depressing the button. Once the deal has been accepted, deal presenter 100 will process the deal acceptance and request payment from passenger 115. Payment may be made, for example, with a credit card. The embodiment of
In some embodiments, transportation to the venue providing the deal is included in the purchase price. That is, once passenger 115 accepts the deal and pays the purchase price, FHV 120 will change the passenger's 115 destination from her original destination to the venue offering the deal. In one embodiment, passenger 115 may be en route to a different location and once she accepts the deal, deal presenter 100 may communicate with trip computer system 125 to change the trip information to indicate that passenger 115 will now be traveling to the venue offering the deal. For example, passenger 115 may be traveling in FHV 120 en route to her hotel. Deal presenter 100 may then display a deal to go to a show. Passenger 115 accepts the deal, which includes transportation to the show. Once passenger 115 accepts and pays for the deal, deal presenter 100 may then communicate with trip computer system 125 to update the destination information and change it from the passenger's hotel, to the location of the show. The FHV would then change the passenger's desired destination the passenger from the hotel to the show. In one embodiment, deal presenter 100 is directly connected to trip computer 125 and updates to the passenger's trip occur through communications between deal presenter 100 and trip computer 125. In other embodiments, deal presenter 100 may send notification of the deal acceptance to deal manager 300 (discussed in
Turning now to
Once consumer 215 accepts the deal displayed by deal presenter 100, consumer 215 may pay for the deal with mobile device 210. For example, consumer 215 may enter their credit card information using the input devices and displays that are part of mobile device 210. In some embodiments, an acceptance message may then be sent from mobile device 210 to network connection point 230 of deal presenter 100. Upon receipt, deal presenter 100 may, as described in greater detail below, send an acceptance message to deal manager 300 (see
In one embodiment, consumer 215 may install a dedicated deal application on mobile device 210. The deal application may be configured to receive deal offers and display them on screen so that consumer 215 may accept them, thereby making consumer computing system 210 an embodiment of deal presenter 100. The deal application may advantageously allow for consumer 215 to browse currently available deals, and may permit consumer 215 to accept a deal without being in the presence of FHV 120. Once consumer 215 accepts the deal through the application, mobile device 210 (acting as a deal presenter 100) may then communicate the acceptance to deal manager 300. Deal manager 300 may then reserve an FHV to transport the consumer 215 to venue offering the deal. In some embodiments, deal manager 300 may be in communication with reservation and dispatch computing system 350. In other embodiments, deal manager 300 may comprise modules that handle the reservation and dispatch of for-hire vehicles (as shown with respect to
In one embodiment, deal manager 300 is a computing system responsible for managing deals. Deal manager 300 advantageously provides interfaces for vendors to define deals and may accept deal definitions created by vendors. Deal manager 300 also handles the publication of deals to deal presenter 100 and may monitor the currently defined deals for publication. For example, deals may be time restricted, that is, they may only be offered during a fixed period of time defined by a start time and an end time. For example, a deal may run on Oct. 1, 2011 from 5 PM (start time) to 8 PM (end time). Deal manager 300 may execute a process that checks the currently defined deals in the system and publishes them to deal presenter 100 at the start time of the deal. The deal manager advantageously is in periodic communication with the vendor system to confirm that the deals listed are still current, and when a deal is sold the vendor system is updated. The frequency of this periodic communication will depend on the type of deal. For example if seats to a show are being offered then the communication with the vendor system needs to be sufficient to prevent the sale of two identical seats. It is contemplated that this communication can be accomplished automatically without the need for human intervention. The Deal manager 300 may also handle the acceptance of the deal. Once deal manager 300 receives notification from deal presenter 100 that a deal has been accepted, deal manager 300 may interface with reservation and dispatch 350 to request a FHV, and it may also interface with payment processor 320 to process payment. Deal manager 300 may also maintain historical data of past deal campaigns for reporting purposes to vendor system 310.
In one embodiment, deal manager 300, is a computing system that is IBM, MACINTOSH® or LINUX®/Unix compatible. Deal manager 300 may, in some embodiments, include one or more central processing units (“CPU”) 301, which may include one or more conventional or proprietary microprocessors. Deal manager 300 may further include memory 302, such as random access memory (“RAM”) for temporary storage of information and read only memory (“ROM”) for permanent storage of information, and data store 303, such as a hard drive, diskette, or optical media storage device. In certain embodiments, data store 303 stores data needed for managing and maintaining deals. In other embodiments, data store 303 might store historical deal information. Embodiments of data store 303 may store data in databases, flat files, spreadsheets, or any other data structure known in the art. Typically, the modules of deal manager 300 are in communication with one another via a standards based bus system. In different embodiments, the standards based bus system could be Peripheral Component Interconnect (PCI), Microchannel, SCSI, Industrial Standard Architecture (ISA) and Extended ISA (EISA) architectures, for example. In another embodiment, deal manager 300 leverages computing and storage services available over the Internet (cloud computing).
Deal manager 300 is generally controlled and coordinated by operating system software, such as the WINDOWS® 95, 98, NT, 2000, XP, VISTA®, LINUX®, SunOS, SOLARIS®, PalmOS, BLACKBERRY® OS, or other compatible operating systems. In Macintosh systems, the operating system may be any available operating system, such as MAC OS X. In another embodiment, deal manager may be controlled by a proprietary operating system, that is one that had been custom made for the purposes of embodying the systems and methods described herein. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, and I/O services, and may provide a user interface, such as a graphical user interface (“GUI”) for display, among other things.
Deal manager 300 may also include one or more commonly available I/O devices and interfaces 304, such as for example, a printer, buttons, a keyboard, a LED display, a monitor, a touchpad, a USB port, a RS 232 port and the like. In one embodiment, I/O devices and interfaces 304 include one or more display devices, such as a monitor, that allows the visual presentation of data, such as fare and operation data, to a user. In the embodiment of
Deal manager 300 may also include several application modules that may be executed by CPU 301. The software code of the modules may be stored on a tangible computer-readable medium such as for example, RAM or ROM. More particularly, the application modules may include deal definition module 305 and deal publishing module 306.
In general, the word module, as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions stored on a non-transitory and/or tangible computer-readable storage, possibly having entry and exit points, written in a programming language, such as, for example, C, C++, C #, or JAVA®. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, PERL®, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules may be stored in any type of computer-readable storage, such as a memory device (for example, random access, flash memory, and the like), an optical medium (for example, a CD, DVD, BluRay, and the like), firmware (for example, an EPROM), or any other storage medium. The software modules may be configured for execution by one or more CPUs in order to cause computing systems described herein, such as deal presenter 100 and deal manager 300, to perform particular operations.
It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage.
Deal manager 300 may include, in some embodiments, deal definition module 305. Deal definition module 305 may comprise code executed by CPU 301 that is responsible for the definition of deals. For example, deal definition module 305 may generate user interfaces, such as the illustrative user interfaces of
In some embodiments, deals may be defined as part of an advertising campaign, that is, a vendor may define a series of deals it may offer, or standard deals it may offer on a regular basis, that are related to the same set of condition parameters triggering the deal offer. For example, if a vendor offers a show in a venue that seats 200 people, the vendor may define a standard deal offering tickets at 50% off if less than 150 seats have been sold by thirty minutes before the show's scheduled start time. Alternatively, a steakhouse may define an all you can eat campaign, that offers a deal for an all you can eat buffet at a special price on Tuesdays. Deal definition module 305 may provide user interfaces or other means for allowing vendors to define a deal campaign. Deal definition module 305 may also comprise code for execution that stores and retrieves data related to vendor campaign.
In one embodiment, vendor system 310 may launch a predefined deal by sending a message to deal manager 300, or more specifically to deal definition module 305, to launch the particular deal. For example, if a vendor predefines a standard deal offering an all you can eat buffet for $10, the vendor system 310 may launch the predefined deal by sending a command to deal manager 300 that the deal should be executed immediately. Vendor system 310 may command the deal manager 300 through a web interface provided by deal manager 300. In other embodiments, vendor system 310 may have installed on it a deal queue application that lists the vendor's predefined deals and may contain options for launching the deal. The application may be a mobile application as shown in
In another embodiments, deal definition module 305 advantageously allows vendor systems to define deal triggers. A deal trigger is a predefined deal with deal offer conditions that must be satisfied before the deal is to be published. The deal offer conditions may relate to the time the deal is offered, the location of where the deal is offered, the current inventory of the vendor, a combination of conditions, or other deal conditions that may be defined by the vendor. For example, a vendor may wish to fill most of its seats for a show prior to show time. The vendor may create a predefined deal that offers the show tickets at 50% off. The vendor may create deal offer conditions associated with predefined deal that will trigger the deal once the conditions are satisfied. The deal conditions may be, for example, “(1) if there are less than 100 seats sold, (2) at 30 minutes before show time, (3) offer the deal for the next 40 minutes.” Once interest is shown in particular seats for example by making the appropriate selection through the deal presenter 100 then the seats are held for a limited time (maybe 5 to 10 minutes) to give the customer the opportunity to complete the payment process. The deal conditions may also be location based. For example, hotels may only wish to present deals to passengers being picked up at the airport, train station, or bus station. In such instances, the vendor may associate a deal condition with their predefined deal indicating the deal should only be presented on deal presenters that are at the airport, train station or bus station. The vendor may create location based deal offer conditions using, for example, a map interface such as the map interface shown in
In some embodiments, deal manager 300 may comprise deal publishing module 306. Deal publishing module 306 advantageously comprises code that when executed handles the publication of deals and processing of deals once published. For example, deal publishing module 306 may execute a looped process that checks the contents of data store 303 to determine if any defined deals based on time should be published, or if any deal conditions related to deal triggers have been satisfied. Deal publishing module 306 may check the current time and then compare that to the publishing time of a particular deal. If deal publishing module 306 determines a deal should be published, it may then send a message containing the deal, or a “deal packet” out over network 380 that may be consumed by deal presenter 100. Deal packets may contain data related to the deal, such as price of the deal, details of the deal (time, location and/or event information about the deal), and display and formatting information about the deal (such as, for example, HTML code defining how the deal should be displayed on deal presenter 100). The deal packet may also contain code for execution upon passenger 115 or consumer 215 accepting the deal. The code may contain, for example, network information defining where the data should be sent.
In some embodiments, deal publishing module 306 may take a “snapshot” of the current passengers riding in FHVs. The snapshot may include information and data describing the passengers at a particular instant in time. For example, the snapshot may include information about where passengers where picked up or where they may be dropped off and identification information identifying the deal presenter 100 that is affixed to the FHV in which the passengers are traveling. The deal publishing module 306 may then compare the information and data from the snapshot to potential customer attributes defined by a vendor which may define to whom the vendor would like to present deals. If the information and data from the snapshot indicates that some passengers may be interested in the deal, deal publishing module 306 may publish a deal to those passengers. For example, suppose a vendor wants to attract passengers who are staying at luxury hotel. The vendor may set up a customer attribute that indicates they would like to present deals to those passengers who were picked up at the luxury hotel. When there is a need to offer deals, deal publishing module 306 may take a snapshot of the current passengers of FHVs in a location close to the venue of the vendor. If any of those passengers were picked up from the luxury hotel, deal publishing module 306 may publish a deal to those passengers.
In addition, deal publishing module 306 advantageously processes accepted deals. As described in greater detail below, deal publishing module 306 generally processes payment, generates FHV fulfillments (which may include reserving a FHV or communicated updated trip information to a FHV), generates voucher information, sends confirmations, and then waits for a message indicating a voucher has been redeemed. The processing involved upon deal acceptance is discussed in greater detail with respect to
Returning to
In one embodiment, deal presenter 100, is a computing system that is IBM, MACINTOSH® or LINUX®/Unix compatible. Deal manager 300 may, in some embodiments, include one or more central processing units (“CPU”) 101, which may include one or more conventional or proprietary microprocessors. deal presenter 100 may further include memory 102, such as random access memory (“RAM”) temporary storage of information and read only memory (“ROM”) for permanent storage of information. Typically, the modules of deal manager 300 are in communication with one another via a standards based bus system. In different embodiments, the standards based bus system could be Peripheral Component Interconnect (PCI), Microchannel, SCSI, Industrial Standard Architecture (ISA) and Extended ISA (EISA) architectures, for example. In another embodiment, deal manager 300 leverages computing and storage services available over the Internet (cloud computing).
As described above, deal presenter 100 may be a dedicated computing system specifically designed to display deals. For example, deal presenter 100 may be a custom in-vehicle display, or it may be computing system that is part of a FHV-top display. In other embodiments, deal presenter 100 may be an application module that executes on a general-purpose computer such as a mobile phone, tablet computing device, laptop computer or desktop computer. In other embodiments, deal presenter 100 may be a module that executes with another application such as a web browser.
Deal presenter 100 is generally controlled and coordinated by operating system software, such as the WINDOWS® 95, 98, NT, 2000, XP, Vista, LINUX® SunOS, Solaris, PalmOS, BLACKBERRY® OS, iOS, or other compatible operating systems. In MACINTOSH® systems, the operating system may be any available operating system, such as MAC OS X. In another embodiment, deal manager may be controlled by a proprietary operating system, that is one that had been custom made for the purposes of embodying the systems and methods described herein. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, and I/O services, and may provide a user interface, such as a graphical user interface (“GUI”) for display, among other things.
Deal presenter 100 may also include one or more commonly available I/O devices and interfaces 104, such as for example, a printer, buttons, a keyboard, a monitor, a touchpad, a USB port, a RS 232 port and the like. In the embodiment of
Deal presenter 100 may also include several application modules that may be executed by CPU 301. The software code of the modules may be stored on a tangible computer-readable medium such as for example, RAM or ROM. More particularly, the application modules may include presentation module 105 and POS terminal 106.
In one embodiment, presentation module 105 may include code that determines whether deals should be displayed and may also contain code for generating user interfaces that will be shown on display 103. In some embodiments, the decision logic that determines whether a deal should be displayed may take into account the current time, the current location of deal presenter 100, the current fare accumulated by passenger 115, and demographic information about passenger 115 or consumer 215. Presentation module 105 may maintain in memory 102 a data structure (the “monitor queue”) that stores all published deals it receives and may periodically review the deals in the monitor queue to determine if it should display the deal. The manner in which the monitor queue and the presentation module 105 operate to determine if a deal should be presented is explained in connection with
In some embodiments, deal presenter 100 may be connected to or include a GPS receiver. The GPS receiver may, for example, be an external GPS receiver that provides GPS coordinates to deal presenter 100 via I/O devices and interfaces 104. In another embodiment, deal presenter may comprise an on board GPS receiver that communicates with the modules and other components of deal presenter 100. In some embodiments, presentation module 105 may correlate received GPS coordinates with known points of interest for the purpose of determining whether to display a deal. For example, presentation module 105 may contain logic for correlating a GPS coordinate with the airport or a particular high-end hotel.
In one embodiment, deal presenter 100 may include POS terminal 106. POS terminal 106 may include hardware and software capable of accepting a payment instrument, such as credit card, debit card or gift card. In some embodiments POS terminal 106 may be a “card swipe” device, for example, a device that reads the payment instrument when a user runs the magnetic stripe of the payment instrument through a grove of POS terminal 106. In another embodiment, POS terminal may include a keypad where a user may input a payment instrument account number. Many commercially available POS terminals exist and such POS terminals may be connected to deal presenter 100 by any means known in the art for connecting POS terminals to computing systems, such as for example, USB.
Turning back to
In some embodiments, FHV 120 may include dispatch module 125 which has been configured to handle receiving dispatch messages. Dispatch module 125 may be, in some embodiments, a dedicated dispatch computing system. In other embodiments, it may be an application module running on a general purpose computer such as, for example, a mobile phone, tablet, laptop, or other general purpose computing device suitable for in-vehicle use. FHV 120 may also contain a meter, that is, a device used for calculating and reporting fares. In some embodiments, the meter of FHV 120 is advantageously connected to deal presenter 100 to facilitate the accurate calculation of deals based on the current fare accumulated by passenger 115. FHV 120 may also contain a POS terminal for accepting credit card payments for trip fares. The POS terminal may also be connected to deal presenter 100 so that passenger 115 may use the POS terminal to pay for deals in addition to paying for trip fares.
Vendor system 310 may be a computing system that is owned and operated by a vendor that is offering a deal. Vendor system 310 advantageously includes a web browser allowing vendors to register their business (for example, using the illustrative user interface of
In some embodiments, vendor system 310 may also include a validation module. The validation module advantageously handled voucher redemption. The validation module may interface with a peripheral device such as UPC code or QR code scanner. In some embodiments, vendor system 310 may be a mobile device, such as a cell phone, that may be equipped with a QR code reader. In such embodiments, the validation module may interface with the QR code reader to receive voucher data from the QR code. In other embodiments, the validation module may interface with a keyboard. A user of vendor system 310 may enter in a voucher number, or serial number, for the voucher using the keyboard in order to redeem the voucher. The keyboard may, in some embodiments, be a virtual keyboard displayed on a touchscreen device such as a tablet computing device. Vendor system 310 may also interface with an interactive voice response (IVR) application in order to validate vouchers. A user may, for example, call the IVR application and read the voucher or serialized identifier over the phone in order to validate the voucher.
Payment processor 320 may, in some embodiments, be a computing system operated by a party appointed by a merchant to handle credit card transactions. For example, payment processor 320 may be a third party entity that handles the credit card transactions entered into POS terminal 106. Generally, payment processor 320 may expose an application program interface (API) that permits outside computer systems, such as deal manager 300, to process credit transactions.
In
The high level view of the deal lifecycle described in
Generally, the temporal flow of data starts with step 1 where vendor system 310 transmits deal definition data to deal manager 300. Next, at step 2, deal manager 300 publishes deals to deal presenter 100. At step 3, deal presenter transmits a deal acceptance back to deal manager 300. In response, deal manager 300 processes the payment associated with the deal acceptance at step 4 by transmitting payment information to payment processor 320. At step 5, payment processor 320 transmits a confirmation back to deal manager 300 that the payment transaction was successful. Upon receipt of successful payment processing, deal manager 300, at step 6, verifies that the transportation request associated with the deal may be fulfilled by sending a message to reservation and dispatch 350 to insure that a FHV is available to transport the consumer 215 to the venue of the vendor. Once the transportation request has been fulfilled, deal manager 300 transmits a confirmation message containing a voucher for the deal to deal presenter 100 at step 7, and at step 8 transmits a message reserving a FHV to reservation and dispatch 350. Reservation and dispatch 350 then automatically transmits a dispatch notice to FHV 120 thereby dispatching FHV 120 for picking up the consumer who purchased the deal, at step 9. Finally, at step 10, the voucher generated and sent to deal presenter 100 at step 7 is validated and redeemed by vendor system 310 by transmitting a redemption message to deal manager 300.
In step 1 of
In some embodiments, vendors may register with deal manager 300. Registration may facilitate deal definition so that data related to the vendor is shared among the deals its offers thereby allowing for a more streamlined deal definition process. For example, the address of venue of the vendor may be communicated to deal manager 300 at the time of registration. When the vendor submits deals in the future, the address of the venue need not be entered.
In some embodiments, the data entered into vendor information block 630 by the vendor may be used by deal manager 300 to generate targeted deals. Targeted deals are deals that may be targeted to certain passengers or consumers based on demographic information or behavior that may be gleaned from their use of FHVs or other information. Data entered into the vendor information block 630 may be used to generate targeted deals by including some of the data in deals that are generated and communicated to deal presenter 100. In another embodiment, the data entered into vendor information block 630 may be used to associate a consumer category with the vendor and the deals the vendor offers. A consumer category may be an indicator of a consumer type. For example, a consumer category may be “affluent traveler”, “businessman”, “family”, “adult entertainment”, “frequent dinner.” Deal manager 300 may use keywords entered into vendor information block 630 to create an association with a consumer category. For example, if the vendor enters “We are an upscale dinning establishment serving fine French cuisine prepared by a world-class chef,” deal manager may detect the keywords “upscale”, “French cuisine” and “world-class chef” to associate the vendor with the “affluent traveler” consumer category. As the vendor defines deals, the deals may be tagged, or associated with the “affluent traveler” category. When the deals are published and communicated to deal presenter 100, the “affluent traveler” consumer category may be included in the deal information. Deal presenter 100 may then use the consumer category as part of its decision to display the deal. For example, as explained with respect to
In some embodiments, the vendor may define deals. The definition of a deal may comprise a title, a description, a price, and a retail price. For example, if the deal is for a show called “Great Show”, the title may be “Deal on Great Show!”, the description may be “The Great Show is an exciting mix of circus arts set to dramatic classical music”, the price may be $25 and the retail price may be $60. A deal definition may also include custom graphics, images, or videos that allow vendor 310 to create an attractive and persuasive deal advertisement for display on deal presenter 100. In some embodiments, deals may be time restricted, that is, they may only run between a first time and a second time. In such embodiments, the deal definition includes the start time and end time of the deal. The vendor may also restrict the areas where deals may run. For example, if the vendor wishes to run their deals on a FHV-top display or on in-vehicle displays, they may limit the display of the deal to a particular predefined area. In such embodiments, the deal definition may also include geospatial parameters that define the area where the deal will run.
Deals may be defined by the vendor using user interfaces provided by deal manager 300, or in other embodiments, by a custom client application executing on vendor 310 that is communication with deal manager 300.
In some embodiments, vendor system 310 may upload media such as images and/or video so that the deal may be more attractive to those that view it.
In some embodiments, more than one media may be uploaded and included as part of deal. For example, a deal may include several still images, several videos, or a mixture of images and videos. Media upload interface 800 may include buttons for adding additional media. As media is added, the vendor may set the transition and the display duration for each piece of media. In one embodiment, the order the media will be displayed to passenger 115 or consumer 215 is based upon the order the uploaded media appears in media upload interface 800. For example, if image 1 appears at the top of media upload interface 800, and image 2 appears at the bottom of media upload interface 800, consumer 215 will first see image 1 for the length of time set in the media duration slider associated with image 1, and then consumer 215 may see image 2 for the length of time set in the media duration slider associated with image 2. Media upload user interface 800 may also include a preview offer button 850 that allows the vendor to preview the deal thereby allowing the vendor to adjust the media, display duration of media, or transitions between media as needed.
In some embodiments, the vendor may wish to geographically restrict where deals may be presented.
In one embodiment, once the vendor has completed entering the deal information using the user interfaces of
Returning to
Once deal presenter 100 receives the deal, it may display the deal on display 103.
In one embodiment, deal presenter 100 may provide a user interface that allows passenger 115 to browse available deals.
In one embodiment, once passenger 115, or consumer 215, selects purchase button 1102, deal presenter 100 may display payment information user interface 1500. Payment information screen 1500 may contain, for example, quantity selection buttons 1501, advantageously allowing Passenger 115 may select the number of tickets he would like to purchase in the deal. The quantity selection may affect payment summary 1502, that is, as the quantity is changed, the total in payment summary 1502 may update. Payment information screen 1500 may also include payment instrument selector 1503, advantageously allowing for the selection of a payment instrument, such as, for example, a VISA® card, a MASTERCARD®, an AMERICAN EXPRESS® card or a DISCOVER® card. Payment information screen may also comprise credit card information entry user interface elements 1504 for entry of credit card numbers and CVN codes. Once passenger 115 has entered the appropriate data, passenger 115 may purchase the deal by selecting purchase button 1505. In some embodiments, purchase button 1505 may be disabled, or grayed out, until the passenger 115 has entered the required data for payment processing. If, however, passenger 115 does not wish to purchase the deal, they may exit payment information screen 1500 by pressing cancel button 1506.
Returning to
Once deal manager 300 receives the acceptance from deal presenter 100, deal manager 300 may attempt to process payment in step 4. Deal manager 300 may extract from the acceptance data, payment information that was part of the acceptance. For example, deal manager 300 may extract the payment instrument type selected with payment instrument selector 1503 and may also extract the credit card number and CVN code from the acceptance data. In some embodiments, this data may be encrypted using an encryption algorithm known in the art. In such embodiments, deal manager 300 may decrypt the payment information before packaging it to send to payment processor 320. Payment processor 320 may expose an API allowing payment information to be sent to it. Deal manager 300 and payment processor 320 may communicate using commonly understood methods of communication between computing systems.
Once payment processor 320 receives the payment information it may process it and return the result of processing to deal manager 300 at step 5. If the result of payment processing was successful, deal manager 300 may generate a voucher, voucher number or serialized number (“voucher”) that may be used to redeem the deal at the vendor system 310. The voucher advantageously represents a unique code or key that may be used by passenger 115 or consumer 215 to redeem the deal at the venue of the vendor. The voucher may be a string of alpha-numeric characters, or in other embodiments, may be a UPC code or QR code that will be scanned at the venue. Deal manager 300 may store a record of the voucher creation in data store 303. In embodiments where deals are limited by a fixed inventory, deal manager 300 may also conduct inventory management processing through the use of deal publishing module 306. Deal manager 300 may, for example, decrement an inventory value associated with the deal. For example, if a deal was defined as only having 10 tickets available, the number of tickets available may be adjusted to 9, to indicate that one ticket has been purchased. Deal manager 300 may also broadcast a message to deal presenters indicating that for that deal the number of available tickets has decreased by one thereby allowing deal presenters to update their deal displays.
Once payment has been verified, deal manager 300 may then determine, at step 6, if there is a for-hire vehicle available for transporting consumer 215 to the venue where the deal may be redeemed. Some deals, such as deals for shows or events, are time sensitive. As a result, deal manager 300 may, in some embodiments, make a request of reservation and dispatch 350 to determine if the consumer's transportation request can be fulfilled the estimated pick up time consumer 215. Once the estimated pick-up time is received, deal manager 300 may then use the location information of consumer 215 to estimate the time needed to travel to the venue offering the deal. Using the estimated pick-up time, and the estimated travel time, deal manager 300 may then estimate the length of time it would take for consumer 215 to get to the venue. Once the travel time is determined, it is added to the current time to ensure that consumer 215 will arrive on time for her deal. In the event that a FHV cannot pick up consumer 215 in time for the show or event, deal manager 300 may cancel the deal and refund the consumer's purchase of the deal. In some embodiments, the request to determine if consumer's transportation request can be fulfilled is completed prior to payment processing.
The flow of data then proceeds to step 7 where deal manager 300 then sends the voucher and purchase confirmation to deal presenter 100.
In some embodiments, deal manager 300 may generate a voucher coupon and send it to deal presenter 100. The voucher coupon may be, for example, an image file containing the voucher number and a UPC or QR code. The voucher coupon may also contain information related to the event for which the deal is was purchased. For example, the event name may be on the voucher coupon, and the deal amount may be on the voucher coupon. In some embodiments, deal presenter 100 may have a printer connected to it. For example, if deal presenter 100 is an in-vehicle display, a thermal printer may be connected to deal presenter 100 for printing the received voucher image. In embodiments where deal presenter 100 may be a mobile device, an image may be displayed on the mobile device so that vendor system 310 may scan the UPC code or QR code for redemption. In some embodiments, deal manager 300 may send the generated coupon image in an email to passenger 115 or consumer 215 to the email address entered in email text field 1603.
Also in step 7, deal manager 300 may send to vendor system 310 a confirmation message indication that deal has been purchased. The confirmation message may include identification information of passenger 115 or consumer 215, if available. The vendor may then use the information of the confirmation message as a further check with the validation of the voucher as a means of further preventing fraud. In addition, the confirmation message may indicate, if appropriate, a seat number, position number, or other customer unique identifier to prevent the vendor from double selling a unique item. For example, suppose the vendor is providing a show with fixed seating. The vendor offers several seats for sale, including seat 5A. Seat 5A is then sold in a deal presented on deal presenter 100. The vendor receives confirmation that Seat 5A was sold and as a result, will not then resell Seat 5A to another customer who may walk up to the venue and wish to purchase a seat without a pre-purchased deal. To make sure that two seats are not sold to different customers at the same time the seats are held for short time period (for example 5 to 10 minutes) when the customer has taken the first step to accept the deal. Then if the seat is not purchased within this time period the seat is released.
Moving to step 8, deal manager 300 advantageously sends a FHV request to reservation and dispatch 350 following the communication of the voucher to deal presenter 100 and the confirmation message to vendor system 310. The request may contain the location of consumer 215 and request an FHV to be dispatched to pick up consumer 215. For example, if consumer 215 received a deal on their mobile device at Las Vegas Blvd and Fremont for an event at Las Vegas Blvd and Flamingo, the request may indicate that the passenger is to be picked up at Las Vegas and Fremont and then transported to Las Vegas and Flamingo. The request may also indicate that the fare for the trip has already be paid and will be credited to the driver accepting the fare.
In some embodiments, deal presenter 100 may be an in-vehicle display and passenger 115 may be traveling to a first destination when the deal is displayed and accepted. In this embodiment, the request message may indicate that the request is not for a new dispatch, but rather to edit a current trip sheet. The request may contain the location of passenger 115 and request that the trip destination of passenger 115 be updated to reflect the location of the venue as the new destination. For example, if passenger 115 is traveling in a FHV to Las Vegas and Fremont when he accepts a deal for an event at Las Vegas and Flamingo, deal manager 300 may send a request to reservation and dispatch 350 that the trip taken by passenger 115 be altered so that the destination of Las Vegas and Fremont be changed to Las Vegas and Flamingo.
Once reservation and dispatch 350 receives the request, it may then send a dispatch message to FHV 120 at step 9. The dispatch message may, in some embodiments, be a dispatch to initiate a new passenger fare. In other embodiments, the dispatch message may be a message to update the trip sheet for passenger 115. Once dispatched, the driver of FHV 120 may pick up the passenger and take them to the venue of the vendor.
Finally, at step 10, the voucher sent to passenger 115 or consumer 215 may be validated. In some embodiments, vendor system 310 and FHV 120 may have a specialized reader device that may scan UPC or QR codes from voucher coupons. In other embodiments, the voucher code may be submitted by vendor system 310 or the driver of FHV 120 to deal manager 300 through the use of web portal, mobile or IVR application. For example,
Once deal manager 300 receives the voucher code, deal manager 300 may validate and redeem the deal. In one embodiment, deal publishing module 306 may mark a row in data store 303 corresponding to the voucher indicating that is was redeemed and can no longer be redeemed if the voucher code is valid. In some embodiments, vouchers may be redeemed by drivers (as part of transportation fulfillment) and may also be redeemed by vendors. As a result, deal manager 300 may maintain separate data structures for a voucher code indicating that it has been redeemed once by the driver of FHV 120, and once by the vendor system 310. If the voucher code is not valid, deal manager 300 may send a validation failed message back to vendor system 310 or the driver of FHV 120 indicating that the voucher is invalid.
In response to the received promotional offer data, deal manager 300 may generate a promotion offer, or deal, at block 1902. The deal or promotional offer may include some of the promotional offer data. In addition, the promotional offer may include a consumer category. The consumer category may describe the type of customer that may be interested in purchasing the deal. For example, a consumer category may be “affluent traveler”, “businessman”, “family”, “adult entertainment”, “frequent dinner.” Once the promotional offer is generated, at block 1903 the deal manager 300 may publish the deal according to methods described in the present disclosure. For example, deal manager 300 may publish the deal in a broadcast paradigm. Once the promotional offer publishes, deal manager 300 may wait for one or more acceptances of the promotional offer.
At block 1904, deal manager 300 receives the acceptance of a deal. Once the acceptance is received, deal manager 300 extracts location information and payment information from the acceptance. The location information indicates the location of deal presenter 100 at the time of acceptance. The payment information includes data related to the amount paid and the account number of the payment instrument. Deal manager 300 then, at block 1905, sends the payment information to payment processor 320 for processing. Once the payment successfully processes, deal manager 300 may generate a voucher and send it to deal presenter 100 at block 1906. Finally, at block 1907, deal manager 300 may generate and send a transportation request to reservation and dispatch 350 based on the extracted location information.
At block 2101, presentation module 105 determines if the time restrictions match the current time. If the time restrictions match the current time, then processing moves to block 2104. For example, a deal may have a time based restriction that it is to run from 1 PM on April 4 to 10 PM on April 5. Presentation module 105 may determine that the current time is 1:01 PM on April 4. As a result, processing may move to block 2104. If, however, the time restrictions do not match the current time, processing moves to block 2102, where the presentation module 105 determines if the deal has expired and should be removed from the monitor queue. Using the above example, if the current time is 10:03 PM on April 5, the deal has expired. As a result, presentation module 105 will remove the deal from the queue at block 2103. If, however, the current time is earlier than the start time, for example, 12:30 PM on April 4, the deal is returned to the monitor queue at block 2105 and is not displayed at block 2106. Another example is that the deal would be removed from the monitor queue if all the inventory (of seats for example) have been sold.
When the time restrictions are satisfied, processing moves to block 2104 where presentation module 105 determines if the current location matches the deal location parameters. The determination may depend on the current location of deal presenter 100. For example, suppose deal presenter 100 receives a deal that is geographically restricted to areas north of Interstate 215. The deal would enter the monitor queue along with other received deals. When presentation module 105 examines the deal from the queue, it will determine the current location of deal presenter 100. Presentation module 105 may, for example, determine its location through the use of a GPS unit connected to deal presenter 100 (in the case, for example, of an in-vehicle deal presenter) or it may use a GPS that is part of deal presenter 100 (in the case of a mobile phone application deal presenter or an in-vehicle deal presenter, for example). If deal presentation module determines that deal presenter 100 is in a FHV that is south of Interstate 215, presentation module 105 may not display the deal, but instead leave the deal in the monitor queue to be re examined later at block 2105. In some embodiments, presentation module 105 may store the deal in memory and then display the deal when deal presenter 100 travels north of Interstate 215, and processing may continue to block 2107.
At block 2107, the presentation module 105 determines if the deal target attributes match the attributes of the passenger or consumer viewing the deal presenter 100. The deal target attributes may, in some embodiments, be a consumer category. The deal may contain a consumer category that described a target consumer to which the deal should be displayed. The presentation module 105 may also decide whether the current consumer or passenger is of the same consumer category. In embodiments where deal presenter 100 is installed in a FHV, presentation module 105 may determine the passenger's consumer category based on information related to the passenger's trip. For example, if the FHV is a limo, as opposed to a shuttle or taxi, presentation module 105 may determine that the passenger is of the consumer class “affluent traveler” or if the FHV is a mini-van, as opposed to sedan, the presentation module 105 may determine the passenger is of the consumer class “family.” Presentation module 105 may also use the pick-up location, or current destination location, to glean information about the passenger that may be used to determine the consumer class for the passenger. For example, if the passenger is picked up at a high end hotel and is planning on traveling to a sushi restaurant, presentation module 105 may determine that the passenger is of the “affluent traveler” and “frequent diner” consumer categories. In embodiments where deal presenter 100 is a mobile device or other general purpose computing system, a consumer category may be determined from the consumer's prior deal purchase history, or consumer entered attributes. In some embodiments, instead of or in addition to consumer categories, destination information may be used to match deals with a passenger. For example, if the passenger is traveling to an adult entertainment venue, presentation module 105 may match the passenger with deals for other adult entertainment venues in the hope of the passenger changing his or her desired destination.
Once presentation module 105 determines that the deal target attributes match the passenger or consumer attributes, processing continues to block 2108. At block 2108, the total cost of the deal is determined. In some embodiments, deal presenter 100 may not present a deal if the deal does not provide a discount once the current accumulated fare is included in the deal. Accordingly, presentation module 105 sums the current accumulated fare and the deal rate at block 2108 after which processing moves to block 2109 to determine if the summed value is less than the retail price of the deal. For example, deal presenter 100 may receive a deal for $20 tickets for $10. If, however, passenger 115 has accumulated a fare of $12, the accumulated fare, plus the cost of the deal of $10 may result in a cost of $22 to accept the deal. Thus, presentation module 105 may not display the deal because the cost of accepting the deal for the ticket exceeds what the ticket would normally cost and the deal is returned to the monitor queue at block 2105. If, however, presentation module 105 determines that the accumulated fare plus the deal rate results in a deal price that is lower than the retail price, processing may move to block 2010, and the deal may be displayed. In another embodiment the functions of the presentation module 105 of the deal presenter may advantageously be handled as part of the deal manager 300. In this embodiment the deal manager would keep track of all the current information about the for-hire-vehicles in the overall system including for example location and fare status as well as what ever information is known about the passenger(s). This information would then be used to make the decision about where and when to present the offers available.
Returning to
In one embodiment, deal manager 2200, is a computing system that is IBM, MACINTOSH® or LINUX®/Unix compatible. Deal manager 2200 may, in some embodiments, include one or more processors, which may include one or more conventional or proprietary microprocessors. Deal manager 2200 may further include memory, such as random access memory (“RAM”) for temporary storage of information and/or read only memory (“ROM”) for permanent storage of information, and/or other data storage, such as a hard drive, diskette, or optical media storage device. In certain embodiments, the deal manager includes data storage needed for managing and maintaining deals, or for storing historical deal information. Such storage may store data in databases, flat files, spreadsheets, or any other data structure known in the art.
The deal manager 2210 may be generally controlled and coordinated by operating system software, such as the WINDOWS® 95, 98, NT, 2000, XP, VISTA®, LINUX®, SunOS, SOLARIS®, PalmOS, BLACKBERRY® OS, IPHONE® OS, Google Android, or other compatible operating systems. In MACINTOSH® systems, the operating system may be any available operating system, such as MAC OS X. In another embodiment, deal manager may be controlled by a proprietary operating system, that is, one that had been custom made for the purposes of embodying certain of the systems and methods described herein. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system architecture, networking, and I/O services, and may provide a user interface, such as a graphical user interface (“GUI”) for display, among other things.
The deal manager 2210 may also include one or more commonly available I/O devices, such as for example, a printer, buttons, a keyboard, a display, a touchpad, a USB port, and the like. In certain embodiments, the deal manager 2210 includes I/O devices and/or interfaces that provide a communication interface to various external devices. For example, the deal manager 2210 may be in communication with a computer network, such as any combination of one or more LANs, WANs, or the Internet, for example, via a wired, wireless, or combination of wired and wireless, connections via a network interface of I/O devices and/or interfaces. The deal manager 2210 may also include several application modules that may be executed by one or more processors. Software code associated with one or more modules included in the deal manager 2210 may be stored on a tangible computer-readable medium such as for example, RAM or ROM.
The modules represented as promoter entity 2220, promotions communication portal/device 2222, and deal service application 2223 may comprise many forms or attributes, as suitable or desirable. For example, in an embodiment, the promoter entity is an individual or company associated with an FHV, the FHV including a promotions computer display, or other promotional tool. In an embodiment comprising a computer display (such as the deal presenter described above), the computer display may prompt or allow access to a passenger of the FHV to view or interact with deal services, such as by using a downloaded, installed, or firmware-based deal services application.
In certain embodiments, the promoter entity is an individual or business entity that controls or operates a billboard that displays deal service content. The display may include an identifier, or code, associated with the promoter entity, that may be input to the deal manager 2210 in connection with a purchase or transaction made by a consumer. The identifier may be used by the promotion compensation module 2212 in calculating a benefit to provide to the promoter entity in compensation for promoting the deal service content. In another embodiment, the promoter entity is a commercial or residential building, such as an apartment building, hotel, office building, etc., including an elevator, or other conveyance device, such as an escalator, associated with a display screen, print media, or the like that displays deal service content. For example, the deal service content may be in the form of an interactive, or non-interactive, application on a display screen, such as a display screen of a computer device connected to the display screen either locally, or over a network. In another embodiment, the promoter entity 2220 is a retail or wholesale establishment, such as a grocery store or department store, associated with an advertisement module (meaning, promotions communication portal) that displays deal service content (meaning, deal service application). For example, the advertisement module may be associated with a self-checkout display, or other in-store module (such as the displays often seen at cash registers with displays, which may advantageously be interactive, permitting touch screen entry by the user). In certain embodiments, as an individual is engaged in a checkout transaction, a device prompts or allows the individual to access or view a deal service application contained on or within the device, such as by selecting an icon on a screen. In some embodiments, the promoter entity is an individual or business entity associated with a billboard (meaning, promotions communication portal) that displays deal service content (meaning, deal service application). The embodiments described above are intended as examples only, and the promoter entity 2220, promotions communication portal/device 2222 and deal service application 2223 may take on any suitable or desirable form, or may be used in any suitable or desirable context.
The promotions communication portal/device 2222 and/or deal service application 2223 may include functionality or promote functionality allowing for data related to a consumer's attention to or solicitation of deals or services promoted by the promotions communication device to be transferred to a deal manager system 2210. Such transfer may be facilitated, for example, by entering a promotional code by a consumer or the promoter entity 2220, such as a code that identifies a particular promoter entity 2220, either locally, or at a remote location. In certain embodiments, transfer of transactional data is facilitated by connecting the promotions communication portal 22 to the deal manager system 2210, such as over a network.
In certain embodiments, the deal manager system comprises one or more computer servers, processors, I/O devices, or other computing functionality. The promotions communication portal and/or deal service application may provide the transaction data to the deal manager system 2210 over a network, such as the Internet, or a telephone network, or through some other transmission medium, whether electronic or physical, such as the postal service. The deal manager system 2210 may be configured such that transactional data from the promotions communication portal 2222 is stored in a transaction data database 2214. Transaction data may include, for example, date and/or time information associated with a deal service transaction.
The deal manager system 2210 includes a promotion compensation module 2212. The promotion compensation module 2212 may include one or more processors and/or memory devices, and may be in data communication with the transaction data database 2214. In certain embodiments, the promotion compensation module 2212 includes data associated with payment preferences or methods associated with one or more promoter entities. Payment preferences or methods may include, for example, designation of a bank account for direct-deposit, or payment by check or cash, or other method of payment.
In certain embodiments, the deal manager 2210 and/or transaction data module 2214 include data that allows for distinguishing between different promoter entity types. For example, the deal manager 2210 may include functionality to distinguish between taxi drivers, limo drivers, and/or other FHV drivers. In certain embodiments, the deal manager 2210 includes functionality to distinguish between drivers in a certain geographic area, or drivers in service a certain time. Such functionality may advantageously allow for communication or interaction with selective groups of promoters.
The promotion compensation module 2212 facilitates the transfer of compensation or other benefit to the promoter entity 2220, or to an account or entity associated with, or designated by, the promoter entity. Example types of benefits may include money payments, “in-kind” transfers, or a voucher, or other type of benefit or combination of benefits) For example, the promotion compensation module may transfer compensation to the promoter entity automatically or otherwise based on transactional information received from the promotions communication portal 2222. Compensation may include any combination of money, vouchers, awards, recognition, or any other form of consideration or compensation. In certain embodiments, when a consumer conducts a transaction in connection with, or based on, the promotions communication portal 2222, the promotion compensation module 2212 receives data associated with such transaction from the transaction data database 2214, and, based at least partly on such transaction, transfers, or causes the transfer of, compensation to the promoter entity 2220. In certain embodiments, compensation is transferred by mail, such as in the form of a check.
In an embodiment, the deal manager 2310 is a computing system responsible for managing deals. The deal manager 2310 may advantageously provide interfaces for vendors to define deals and may accept deal definitions created by vendors. The deal manager 2310 may also assist in the publication of deals to one or more promoters 2320, 2322. The deal manager 2310 may also receive information relating to the acceptance of a deal, for example by a consumer 2350. In certain embodiments, when deal manager 10 receives information from a promoter, for example, promoter A 2320, that a deal service transaction has taken place, the deal manager 2310 may facilitate the transfer of compensation to the promoter and/or an employer entity associated with the promoter based at least in part on the transaction information. For example, a promoter may receive compensation a per-transaction basis.
The system 2300 includes one or more promoters (for example, promoter A and promoter B) engaged in promotional activities related to deal services provided through the deal manager 2310. As described herein, promoters may be individuals, businesses, or any other type of entity. Once a promoter has registered with the deal manager 2310, such as through an online registration process (see
In certain embodiments, a promoter can promote deal services provided through the deal manager 2310 to one or more consumers 2350. For example, a promoter may be a driver of an FHV, and a consumer 2350 may be a passenger of the FHV 60. In certain embodiments, the promoter 2320 promotes deal services to the consumer 2350, for example, while the consumer 2350 is a passenger in an FHV 26 driven by the promoter 2320. When the promoter 2320 is successful in promoting deal services, that is, the consumer 2350 engages in a transaction in connection with promotional efforts of the promoter 2320, then the promoter and/or the promoter's employer or affiliated company, may receive compensation from the deal manager 2310. A transaction may be connected to a promoter's promotional efforts if, for example, the consumer 2350 inputs a code uniquely identifiable with the promoter 2320 when making the transaction. Other information may also demonstrate a connection between the promoter's efforts and a transaction, such as a network address of a device used in the transaction, a time-stamp of the transaction, a location of the transaction, or other information. Certain embodiments provide a system 2300 that permits access by vendors to people such taxi drivers, limo drivers, doormen, and/or others that provide recommendations for venues such as shows, clubs and restaurants.
In certain embodiments, the consumer 2350 may download a deal service application from the deal manager 2310 to an electronic device 2352, which may be a mobile device. Such a download may be considered a transaction for purposes of prompting compensation of the promoter 2320. In certain embodiments, downloading of the deal service application may be done in connection with entering a code or other identifier associated with the promoter, thereby linking the consumer 2350 to the promoter 2320. In certain embodiments, future transactions using the downloaded application may also prompt compensation of the promoter 2320 and/or an employer 2340. For example, employer 2340 may be a company owning or leasing one or more FHV's. Compensation of the promoter 2320 in connection with use of the downloaded application may continue indefinitely, or for a certain period of time. For example, the promoter 2320 may be able to receive compensation in connection with use of the downloaded application, or for transactions associated with the promoter's identifier, while the promoter's registration information is current or valid with respect to the promoter database 2312. In certain embodiments, when promoter 2320 switches company/employer or geographic affiliation, the promoter's registration information may become invalid, and further transactions will not result in any compensation being paid to the promoter.
The system 2300 may be configured such that the promoter 2320 is notified, for example, via text message, email, or other mechanism, when the consumer 2350 conducts a transaction using the downloaded application or in connection with the promoter's identifier. Such notification may provide incentive or encouragement for the promoter to engage in continued promotional activities. As described in greater detail above in connection with
In addition to, or in alternative to, promoting the downloading of deal service applications, the promoter 2320 may be compensated for various other promotional efforts. For example, the promoter 2320 may be the driver of an FHV 26 that contains a promotions communication portal/device, as described above in connection with
The system 2300 may include one or more additional promoters and/or FHV's (for example, promoter B 22, FHV 28), which may or may not be associated with promoter A, FHV 26, and/or promoter A's employer. Promoter database 2314 may include registration information related to both promoter A and promoter B and may advantageously include functionality to compare performance, such as the number of associated transactions, between a large number of promoters stored in the promoter database 2312. In certain embodiments, the promoter database 2314 may include functionality to sort promoter performance by venue. For example, promoter database 2312 may include functionality to provide a list of top performers with respect to deals offered by a specific vendor. Such information may be of interest to the venue for promotional reasons.
As described above, deal manager 2310 includes a promoter database 2312 that includes various information related to one or more promoters, such as promoters who are registered with the deal manager 2310 as participating promoters. The system 2300 may provide a means for a promoter to register with the deal manager 2310 in order to facilitate receiving compensation from deal manager 2310 for promotional activities, among other things. The promoter database may include such information as registration information (described in greater detail below with reference to
The system 2300 may be configured such that transaction data stored by the deal manager 2310 may be provided to one or more entities, such as, for example, a vendor 2330, or an employer or potential employer 2340. For example, the deal manager 2310 may provide transaction data to venue 2330, possibly in response to a data request. The venue 2330 may provide promotional materials or secondary incentives to the deal manager 2310 based on the data, for example, to be conveyed to a subset of the promoters (taxi and limo drivers, for example) who have been especially helpful in receiving a relatively large number of purchases by the venue. Secondary incentives may include some type of compensation, such as a voucher for use in connection with the venue 2330, or some type of award or recognition. In an embodiment, the data received by the venue 2330 does not contain personal identification information relating to promoters. For example, the data may merely comprise general notice of promotional activity of registered promoters, such as information related to top performers among the registered promoters. In certain embodiments, the deal manager 2310 stores information relating to one or more vendors, the deal manager 2310 including functionality to separate information relating to promoters and information relating to vendors.
The system 2300 may advantageously allow for indirect communication between vendors 2330 and promoters 2320, 2322, while maintaining complete confidentiality of the promoters. In certain embodiments, the system 2300 does not provide a mechanism by which vendors can reach out to promoters directly or discover names, addresses, or other personal information of promoters.
Likewise, the employer (such as a taxi fleet operator) may receive transaction data, for example, through a network 2360, either on a periodic basis or in response to a request or other event. For example, an employer may wish to convey employment materials to one or more promoters by transferring such material to the deal manager 2310, and the deal manager 2310 transferring the material to one or more registered promoters. In certain embodiments, the registration information contained in the promoter database provides information for use by the deal manager 2310 in contacting registered promoters. The vendor may send materials, via the deal manager 2310, to specific subsets of promoters. For example, a vendor may wish to send materials to promoters (as opposed to sending material only to deal presenters in particular FHVs) that fit specific criteria, such as being in a particular place at a particular time, or the like. Such information may be available in promoter database 2314.
In certain embodiments, the deal manager 2310 transfers information using a mass-communication mechanism, such as a blast email or text message, to all or a selected subset of the registered promoters. For example, the deal manager 2310 may use a mass-communication mechanism to convey information or material to promoters that was provided by a venue 2330 or employer entity 2340. The subset could be drivers who will be working on a particular night, drivers working in a particular territory, or drivers available at a particular time.
Once the promoter identifier has been generated, it is provided, electronically or otherwise, to the promoter. This step is performed at block 2430. For example, the promoter identifier may be provided via email or text message, or may be printed on physical business cards which are provided to the promoter (see
At block 2440, the data manager system receives a request from a customer to download a mobile application associated with a deal program. In certain embodiments, the deal manager system is configured to receive along with the request a promoter code input. For example, a customer may enter the promoter code in connection with the download request. In an embodiment, a promoter code field is automatically populated based on driver schedule information, or other information indicating the identity of the promoter driver (such as the driver's login at the start of his shift). For example, an electronic device of the driver may communicate wirelessly with a point-of-sale device or application to identify the driver. Upon receiving the request, a controller of the deal manager system facilitates the download of the mobile application from the deal manager system to a customer device over a network.
At block 2450, based on the promoter code included with the download request, the deal manager system determines a fee or other compensation (such as free tickets or vouchers) to be paid to the promoter associated with the promoter code, and provides the fee payment to the promoter through some means. In certain embodiments, the promoter registration information provides payment preference information upon which the payment transfer is based. For example, the deal manager system may wire or otherwise transfer a money payment to an account identified by the promoter, or payment may be transferred to the promoter's employer, who may further direct the payment, or a portion thereof, to the promoter through the employee pay check. The fee payment may serve as compensation for promotion by the promoter of one or more deals or services to the customer.
In response to the received promotional offer data, the deal manager may generate a promotion offer, or deal, at block 2530. The deal or promotional offer may include some of the promotional offer data. In certain embodiments, the deal manager may provide access to consumers to exclusive deals unavailable with other deal sources. In addition, the promotional offer may include a consumer category. The consumer category may describe the type of customer that may be interested in purchasing the deal. For example, a consumer category may be “affluent traveler,” “businessman,” “family,” “adult entertainment,” “frequent diner.” Upon receiving the promotional offer data, the deal manager system may be configured to query the vendor, or a local database, to determine whether the promotional offer is the best currently available offer offered by the vendor. For example, the deal manager may provide notification to the vendor if it is determined that the deal is not the best current offer available to advertise, and may encourage the vendor to provide an alternative deal. At block 2540, the promotional offer publishes. Once the promotional offer publishes, such as on an in-vehicle deal presenter, as described above with respect to
In response to the received promotional offer data, the deal manager may generate a promotion offer, or deal, at block 2520. The deal or promotional offer may include some of the promotional offer data. In certain embodiments, the deal manager may provide access to consumers to exclusive deals unavailable with other deal sources. In addition, the promotional offer may include a consumer category. The consumer category may describe the type of customer that may be interested in purchasing the deal. For example, a consumer category may be “affluent traveler,” “businessman,” “family,” “adult entertainment,” “frequent diner.” Upon receiving the promotional offer data, the deal manager system may be configured to query the vendor, or a local database, to determine whether the promotional offer is the best currently available offer offered by the vendor. For example, the deal manager may provide notification to the vendor if it is determined that the deal is not the best current offer available to advertise, and may encourage the vendor to provide an alternative deal. Once the promotional offer publishes, such as on an in-vehicle deal presenter, as described above with respect to
At block 2550, the deal manager receives an acceptance of a deal in the form of a solicitation from a consumer. The solicitation may include information associating the solicitation with a specific promoter identifier. At block 2560, the deal manager processes payment information of the consumer and generates and sends a voucher to the consumer related to the deal at block 2570. Transmission of the voucher may be contingent on successful processing of the payment information. The payment information may include data related to the amount paid and the account number of the payment instrument.
At block 2580, the deal manager calculates a benefit to be provided to the promoter. In certain embodiments, the compensation is of the form of a money payment, such as, for example, a small percentage (advantageously between 0.01% and 2%) or a flat payment in an amount between $0.01-0.49, $0.50-0.99, $1.00-5.00, or higher. The calculated value may diminish as the time since the consumer was contacted increases, such that over the course of a year, the value may be, for example, reduced to zero. In certain embodiments, recurrent contact with the consumer increases the benefit value, or prevents the benefit value from decreasing.
In some embodiments, a promoter may register with a deal manager. Registration may facilitate compensation of a promoter for promotional services provided. Various types of information related to the promoter may be required, or desired, in association with registration of the promoter. Examples, as shown, include name, physical address, email address, phone number, gender, date of birth, employer, login password. After registering, a promoter may be able to login to a server managed by the deal manager to perform various tasks, enter or revise or update previously submitted information, or view content provided on the server. For example, server content may include promotional material related to promoter compensation and/or various deals and promotions directed to all promoters or to particular categories of promoters, such as drivers, or to subcategories of drivers, for example, all drivers that are currently located in a particular geographical area.
In some embodiments, the data entered into the user interface by the promoter may be used by the deal manager system to generate one or more identifiers associated with the promoter. The term “identifier,” is used herein according to its broad and ordinary meaning and may include, for example, a unique code comprising one or more alphanumeric characters.
At some point, promoter 2720 may leave the employ of employer A. For example, promoter 2720 may leave employer A and become employed by employer B (illustrated by line 2702). In certain embodiments, the promoter's registration is portable in the sense that, in certain circumstances, the promoter 2720 can maintain its registration and relationship with the deal manager system 2710 when changing employment positions. That is, it is not necessary for the promoter 2720 to re-register with the deal manager system 2710. In certain embodiments, in order for the promoter's registration to be maintained through a change of employment, employer B must also have a relationship with the deal manager 2710, for example, as a participating company or entity. In certain embodiments, as long as employer B is a current/active owner or operator in the deal service program and maintains deal presenter devices in at least some FHV's owned by the employer.
The promoter 2720 may leave employer A or B and work independently of an employer (as illustrated by arrows 2704 and 2706), or work for an employer that does not have a relationship with the deal manager 2710. In certain embodiments, the promoter 2720 may still be able to maintain its registration. Furthermore, in certain embodiments, the promoter 2720 may relocate to a geographic region that is outside the scope of the promoter's employer's relationship with the deal manager 2710. However, the promoter 2720, depending on the embodiment, may still maintain its registration with the deal manager 2710 and exploit the deal manager's associated compensation program as a revenue stream. In this sense, the portability aspect of certain embodiments effectively allows a promoter to maintain a side-business comprising its promotional activities and income associated with its status as a registered promoter and presence in the promoter database 2714. When the promoter changes employment from employer A 2740 to employer B 2745 (illustrated by arrow 2702), the promoter's registration information contained in the promoter database may be updated by the deal manager 2710 to remove or modify information relating to the association between the promoter 2720 and employer A. Furthermore, the promoter's registration information may be updated to reflect an association between the promoter 2820 and employer B 2745. In certain embodiments, other registration information is unaltered by the change in employment.
Distribution of a card or the like may provide a mechanism for a promoter to communicate its identifier to a consumer. However, any suitable means for communicating the identifier may be implemented. For example, a promoter may transmit the identifier via some wireless connection protocol or media, such as BlueTooth, WiFi, RFID, infrared, inductive coupling, or the like. Such transmission may be from a card, phone, or may be from an intelligent system component that is able to identify that the promoter is operating the FHV. Text messages and/or emails, which may contain a website link, may also provide a means to communicate the identifier.
The application may present the interface 2905 shown in
In certain embodiments, it may not be required to enter the promoter code in order to complete the transaction. However, if the code is not entered, the associated promoter may not be compensated as in the case where the code is properly entered. In certain embodiments, it is unnecessary for the consumer to enter a promoter code in such an electronic device, as information associated with the device provides adequate identification of the associated promoter. Various other way for inputting promoter identification may be used other than that depicted in
The system 3100 includes a business or other entity of some kind that may have interest in transaction data associated with deal service promoters. For example, the business 3140 may be a hotel, casino, or other company or entity. The system 3100 is configured such that the vendor 3140 receives, possibly in response for a request, transaction data associated with one or more of the promoters 3120 that are registered with the deal manager 3110. As discussed above, transaction data may provide information related to the performance of promoters registered with the deal manager 3110. Such data may be transferred to the vendor 3140 without disclosing personal identities of promoters, and may include general information relating to the performance of one or more of the promoters. Furthermore, the survey questions/data may be transmitted between the deal manager and the vendor 3140 related to promoter input vis-à-vis the vendor or other vendors or topics.
In response to receiving the transaction data, the vendor 3140 may wish to provide benefits, or perks, of some kind and/or promotional materials to some or all of the promoters 3120. For example, the vendor 3140 may wish to provide benefits or materials to a subset of the promoters 3121, such as a subset of promoters that, by some defined standard, have been relatively successful in their promotional activities. In order to facilitate the conveyance of such materials, the business 3140 may provide such to the deal manager 3110. Particularly, the vendor 3140 may provide materials or information to the promoter contacting module 3116. Upon receipt of such materials, benefits, or information, the promoter contacting module 3116 may convey the same, or some portion thereof, to one or more of the promoters 3120 in accordance with the desires of the vendor. Therefore, the deal manager 3110 may serve as an intermediary with respect to communication between a business 3140 and one or more promoters 3120. In such a system, anonymity of promoters may be maintained with respect to the vendor 3140. Anonymity may be desirable in order to maintain equality among vendors with respect to ability to communicate with promoters. Through anonymity, hiring, compensation of, and evaluation of, promoters may be more likely to be based on merit/performance. Further, while the vendor does not have access to the names of the promoters (taxi drivers, for example) the vendor does have access to a group of drivers having the characteristics that the vendor wants to reach (for example, location near vendor, high producer promoters, promoters who have been successful promoting that vendor).
Following registration of the promoter, at block 3240, the method includes receiving a request to download a deal service application, such as by a consumer, wherein the request includes communication of the promoter's identifier. For example, the consumer may have input the identifier in response to information or prompting received from the promoter. In certain embodiments, the identifier is not included with the download request, but is included at a later point, such as after the application has been opened or launched on an electronic device of the consumer. Therefore, it should be understood that various aspects of the steps shown in
Once the identifier has been received by the deal manager system, compensation is transferred in some manner to the promoter in consideration for its promotional activity related to the download of the application. At block 3250, the application if provided for download. After downloading the application, the consumer may proceed to purchase one or more deals, or conduct one or more transactions using the application, for which it may be desirable to compensate the promoter. In connection with such a purchase, blocks 3270, 3280, and 3290 illustrate steps of receiving a deal acceptance, processing payment information associated with the purchase, and generating and sending a voucher associated with the deal to the consumer.
In certain embodiments, the promoter may be compensated for one or more additional transactions carried out by the consumer using the application. Therefore, the steps 3260, 3270, 3280, and 3290 provide a loop for processing such future transactions and providing compensation therefore.
In Operation
In certain embodiments, one or more of the systems and/or methods described above may operate as follows: A taxi driver may provide registration information to a deal manager system for the purposes of becoming registered as a promoter of deal services with the system. In certain embodiments, registration of the driver may only be permitted if the driver, or his or her employer, has a preexisting business relationship with the deal manager system.
In response to receiving the registration information, the driver may be entered in a registered promoters database. Furthermore, the deal manager system may generate an identifier associated with the driver, and provide the identifier to the driver. In certain embodiments, the deal manager system provides the identifier together with a collection of materials, such as in a start-up kit. The kit may include physical distribution cards or leaflets on which the driver's identifier is displayed. In certain embodiments, the start-up kit is virtual, or electronic, and may be available on a webpage of the deal manager system.
The driver may promote deal services provided through the deal manager to passengers of his or her taxi cab. For example, the driver may verbally encourage passengers to utilize the deal services, or may provide promotional materials to them, such as the card displaying the driver's identifier. A passenger consumer may make a purchase or download a deal service application in response to the driver's promotional efforts. In connection with such purchase or download, the consumer may have the opportunity to input the driver's identifier, thereby associating the driver with the purchase or download. The driver may encourage the consumer to input the identifier in order to create such an association.
When the deal manager system processes the purchase or download, the association between the driver/promoter and the passenger/consumer may prompt the deal manager to provide notice and/or compensation/recognition to the driver. This notice/compensation may encourage the driver in his or her promotional efforts and may incentivize the driver to engage in further efforts.
The deal manager may maintain data associated with registered promoters providing information relating to the nature of one or more of the registered promoters' promotional activities. This data may be useful to vendors or other entities. For example, a vendor may wish to provide vouchers or promotional material to promoters based on such data. It may be desirable for the deal manager to allow the vendor to provide materials to promoters without personally identifying and/or contacting the promoters. Therefore, the deal manager system may receive the materials from the vendor and provide them to all, or a subset of, the registered promoters. For example, a “top performers” subset, or a temporally (for example, within two hours of a show time) or geographically limited group of the registered promoters may receive certain materials from a vendor.
The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “for example,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Conjunctive language such as the phrase “at least one of X, Y and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be either X, Y or Z. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y and at least one of Z to each be present.
While certain example embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the disclosure. Thus, nothing in the foregoing description is intended to imply that any particular element, feature, characteristic, step, module, or block is necessary or indispensable. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the methods and systems described herein may be made without departing from the spirit of the inventions disclosed herein. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of certain of the inventions disclosed herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2870018 | Williams | Jan 1959 | A |
| 3589486 | Kelch | Jun 1971 | A |
| 3667307 | Kelch | Jun 1972 | A |
| 3675504 | Schuh | Jul 1972 | A |
| 3698627 | Kelch et al. | Oct 1972 | A |
| 3736408 | Kienzle et al. | May 1973 | A |
| 3764782 | Kelch et al. | Oct 1973 | A |
| 3809312 | Warrick et al. | May 1974 | A |
| 3860806 | Fichter et al. | Jan 1975 | A |
| 3860807 | Fichter et al. | Jan 1975 | A |
| 3931508 | Kelch | Jan 1976 | A |
| 3937933 | Warkentin | Feb 1976 | A |
| 3946213 | Kepper | Mar 1976 | A |
| 3953720 | Kelch | Apr 1976 | A |
| 4001560 | Larsen | Jan 1977 | A |
| 4021645 | Saufferer et al. | May 1977 | A |
| 4024384 | Tateishi et al. | May 1977 | A |
| 4039780 | Kelch et al. | Aug 1977 | A |
| 4045656 | Scott | Aug 1977 | A |
| 4056709 | Scholl et al. | Nov 1977 | A |
| 4081663 | Ahlberg | Mar 1978 | A |
| 4095737 | Schuh et al. | Jun 1978 | A |
| 4118775 | Boyce | Oct 1978 | A |
| 4160155 | Steele et al. | Jul 1979 | A |
| 4167040 | Heritier et al. | Sep 1979 | A |
| 4205388 | Steiner | May 1980 | A |
| 4208664 | Mattori | Jun 1980 | A |
| 4209688 | Kelch | Jun 1980 | A |
| 4212069 | Baumann | Jul 1980 | A |
| 4217484 | Gerst | Aug 1980 | A |
| 4240146 | Iles | Dec 1980 | A |
| 4280180 | Eckert et al. | Jul 1981 | A |
| 4360875 | Behnke | Nov 1982 | A |
| 4389563 | Ricard | Jun 1983 | A |
| 4409685 | Ricard | Oct 1983 | A |
| 4436423 | Kumar et al. | Mar 1984 | A |
| 4482965 | Tateishi et al. | Nov 1984 | A |
| 4539644 | Adams et al. | Sep 1985 | A |
| 4570228 | Ahlberg | Feb 1986 | A |
| 4574189 | Adams et al. | Mar 1986 | A |
| 4578760 | Adams et al. | Mar 1986 | A |
| 4580039 | Adams | Apr 1986 | A |
| 4658707 | Hawkins et al. | Apr 1987 | A |
| 4713753 | Boebert et al. | Dec 1987 | A |
| 4736423 | Matyas | Apr 1988 | A |
| 4740900 | Adams | Apr 1988 | A |
| 4789774 | Koch et al. | Dec 1988 | A |
| 4800502 | Stewart et al. | Jan 1989 | A |
| 4860124 | Adams | Aug 1989 | A |
| 4882570 | Martinez | Nov 1989 | A |
| 4888798 | Earnest | Dec 1989 | A |
| 4897874 | Lidinsky et al. | Jan 1990 | A |
| 4926476 | Covey | May 1990 | A |
| 4939652 | Steiner | Jul 1990 | A |
| 4965833 | McGregor et al. | Oct 1990 | A |
| 4998205 | Ricard | Mar 1991 | A |
| 5008827 | Sansone et al. | Apr 1991 | A |
| 5010571 | Katznelson | Apr 1991 | A |
| 5043562 | Hautvast et al. | Aug 1991 | A |
| 5058162 | Santon et al. | Oct 1991 | A |
| 5121097 | Van Zeggeren | Jun 1992 | A |
| 5123045 | Ostrovsky et al. | Jun 1992 | A |
| 5155747 | Huang | Oct 1992 | A |
| 5187646 | Koch | Feb 1993 | A |
| 5218638 | Matsumoto et al. | Jun 1993 | A |
| 5241594 | Kung | Aug 1993 | A |
| 5247575 | Sprague et al. | Sep 1993 | A |
| 5274561 | Adams et al. | Dec 1993 | A |
| 5297206 | Orton | Mar 1994 | A |
| 5303163 | Ebaugh et al. | Apr 1994 | A |
| 5319613 | Adams | Jun 1994 | A |
| 5319705 | Halter et al. | Jun 1994 | A |
| 5337357 | Chou et al. | Aug 1994 | A |
| 5341429 | Stringer et al. | Aug 1994 | A |
| 5369702 | Shanton | Nov 1994 | A |
| 5386369 | Christiano | Jan 1995 | A |
| 5400403 | Kaliski et al. | Mar 1995 | A |
| 5410598 | Shear | Apr 1995 | A |
| 5414772 | Naccache et al. | May 1995 | A |
| 5416840 | Cane et al. | May 1995 | A |
| 5428555 | Starkey et al. | Jun 1995 | A |
| 5448641 | Pintsov et al. | Sep 1995 | A |
| 5454101 | MacKay et al. | Sep 1995 | A |
| 5490077 | Freytag | Feb 1996 | A |
| 5499295 | Cooper | Mar 1996 | A |
| 5504814 | Miyahara | Apr 1996 | A |
| 5509070 | Schull | Apr 1996 | A |
| 5511122 | Atkinson | Apr 1996 | A |
| 5557796 | Fehskens et al. | Sep 1996 | A |
| 5563946 | Cooper et al. | Oct 1996 | A |
| 5598470 | Cooper et al. | Jan 1997 | A |
| 5606508 | Thiel | Feb 1997 | A |
| 5615264 | Kazmierczak et al. | Mar 1997 | A |
| 5623136 | Schmid et al. | Apr 1997 | A |
| 5629856 | Ricard | May 1997 | A |
| 5634012 | Stefik et al. | May 1997 | A |
| 5646387 | Schmid et al. | Jul 1997 | A |
| 5646992 | Subler et al. | Jul 1997 | A |
| 5664948 | Dimitriadis et al. | Sep 1997 | A |
| 5699415 | Wagner | Dec 1997 | A |
| 5708709 | Rose | Jan 1998 | A |
| 5715164 | Liechti et al. | Feb 1998 | A |
| 5742807 | Masinter | Apr 1998 | A |
| 5754938 | Herz et al. | May 1998 | A |
| 5765152 | Erickson | Jun 1998 | A |
| 5778348 | Manduley et al. | Jul 1998 | A |
| 5801614 | Kokubu | Sep 1998 | A |
| 5809145 | Slik et al. | Sep 1998 | A |
| 5809234 | Le | Sep 1998 | A |
| 5812959 | Froeberg et al. | Sep 1998 | A |
| 5822428 | Gardner | Oct 1998 | A |
| 5828738 | Spaeth | Oct 1998 | A |
| 5842131 | Yamane | Nov 1998 | A |
| 5842186 | Kulik | Nov 1998 | A |
| 5892900 | Ginter et al. | Apr 1999 | A |
| 5897626 | Pomerantz | Apr 1999 | A |
| 5898777 | Tycksen et al. | Apr 1999 | A |
| 5917434 | Murphy | Jun 1999 | A |
| 5920868 | Fowlow et al. | Jul 1999 | A |
| 5924057 | Kell | Jul 1999 | A |
| 5982887 | Hirotani | Nov 1999 | A |
| 5991402 | Jia et al. | Nov 1999 | A |
| 5999622 | Yasukawa et al. | Dec 1999 | A |
| 6028510 | Tamam et al. | Feb 2000 | A |
| 6060993 | Cohen | May 2000 | A |
| 6081204 | Lavoie et al. | Jun 2000 | A |
| 6087965 | Murphy | Jul 2000 | A |
| 6109520 | Ricard | Aug 2000 | A |
| 6122591 | Pomerantz | Sep 2000 | A |
| 6212525 | Guha | Apr 2001 | B1 |
| 6225890 | Murphy | May 2001 | B1 |
| 6236330 | Cohen | May 2001 | B1 |
| 6246933 | Baque | Jun 2001 | B1 |
| 6249772 | Walker et al. | Jun 2001 | B1 |
| 6253129 | Jenkins et al. | Jun 2001 | B1 |
| 6253649 | Shinjo | Jul 2001 | B1 |
| 6269343 | Pallakoff | Jul 2001 | B1 |
| 6275768 | Zobell et al. | Aug 2001 | B1 |
| 6330499 | Chou et al. | Dec 2001 | B1 |
| 6339745 | Novik | Jan 2002 | B1 |
| 6347739 | Tamam | Feb 2002 | B1 |
| 6366207 | Murphy | Apr 2002 | B1 |
| 6388579 | Adcox et al. | May 2002 | B1 |
| 6442553 | Take | Aug 2002 | B1 |
| 6456207 | Yen | Sep 2002 | B1 |
| 6466921 | Cordery et al. | Oct 2002 | B1 |
| 6474552 | Ricard | Nov 2002 | B1 |
| 6487717 | Brunemann et al. | Nov 2002 | B1 |
| 6546006 | Fraser | Apr 2003 | B1 |
| 6565443 | Johnson et al. | May 2003 | B1 |
| 6587781 | Feldman et al. | Jul 2003 | B2 |
| 6609103 | Kolls | Aug 2003 | B1 |
| 6611755 | Coffee et al. | Aug 2003 | B1 |
| 6677858 | Faris et al. | Jan 2004 | B1 |
| 6686834 | Tamam et al. | Feb 2004 | B1 |
| 6702674 | De Bruin et al. | Mar 2004 | B1 |
| 6710721 | Holowick | Mar 2004 | B1 |
| 6722331 | Koehler et al. | Apr 2004 | B2 |
| 6736317 | McDonald et al. | May 2004 | B1 |
| 6754636 | Walker et al. | Jun 2004 | B1 |
| 6754637 | Stenz | Jun 2004 | B1 |
| 6756913 | Ayed | Jun 2004 | B1 |
| 6772331 | Hind et al. | Aug 2004 | B1 |
| 6773477 | Lindsay | Aug 2004 | B2 |
| 6782241 | Kobayashi | Aug 2004 | B2 |
| 6807534 | Erickson | Oct 2004 | B1 |
| 6812851 | Dukach et al. | Nov 2004 | B1 |
| 6839840 | Cooreman | Jan 2005 | B1 |
| 6857067 | Edelman | Feb 2005 | B2 |
| 6930596 | Kulesz et al. | Aug 2005 | B2 |
| 6931309 | Phelan et al. | Aug 2005 | B2 |
| 6941197 | Murakami et al. | Sep 2005 | B1 |
| 7010685 | Candelore | Mar 2006 | B1 |
| 7010697 | Byrne et al. | Mar 2006 | B2 |
| 7039603 | Walker et al. | May 2006 | B2 |
| 7085775 | Short et al. | Aug 2006 | B2 |
| 7093137 | Sato et al. | Aug 2006 | B1 |
| 7093282 | Hillhouse | Aug 2006 | B2 |
| 7100195 | Underwood | Aug 2006 | B1 |
| 7103583 | Baum et al. | Sep 2006 | B1 |
| 7124099 | Mesaros | Oct 2006 | B2 |
| 7124437 | Byrne et al. | Oct 2006 | B2 |
| 7127411 | Ho | Oct 2006 | B2 |
| 7130584 | Hirvonen | Oct 2006 | B2 |
| 7130831 | Howard et al. | Oct 2006 | B2 |
| 7163459 | Tanskanen | Jan 2007 | B2 |
| 7181419 | Mesaros | Feb 2007 | B1 |
| 7188089 | Goldthwaite et al. | Mar 2007 | B2 |
| 7203666 | Gravell et al. | Apr 2007 | B1 |
| 7236956 | Ogg et al. | Jun 2007 | B1 |
| 7266695 | Nakayama | Sep 2007 | B2 |
| 7278031 | Best | Oct 2007 | B1 |
| 7378982 | Mohamed | May 2008 | B2 |
| 7437756 | Bleumer | Oct 2008 | B2 |
| 7449988 | Hata | Nov 2008 | B2 |
| 7472172 | Anderson et al. | Dec 2008 | B2 |
| 7512968 | Stephens et al. | Mar 2009 | B2 |
| 7551593 | Haller et al. | Jun 2009 | B2 |
| 7562818 | Bierbaum et al. | Jul 2009 | B1 |
| 7565529 | Beck et al. | Jul 2009 | B2 |
| 7567940 | Engelberg et al. | Jul 2009 | B1 |
| 7577617 | Reisinger | Aug 2009 | B1 |
| 7598889 | Maeda et al. | Oct 2009 | B2 |
| 7646740 | Crolley et al. | Jan 2010 | B2 |
| 7647024 | Wang et al. | Jan 2010 | B2 |
| 7689468 | Walker et al. | Mar 2010 | B2 |
| 7689469 | Mesaros | Mar 2010 | B1 |
| 7693662 | Yamada | Apr 2010 | B2 |
| 7693748 | Mesaros | Apr 2010 | B1 |
| 7721108 | Pailles et al. | May 2010 | B2 |
| 7738569 | Quinn et al. | Jun 2010 | B2 |
| 7739205 | Reisinger | Jun 2010 | B1 |
| 7743427 | Byrne et al. | Jun 2010 | B2 |
| 7769694 | Schwartz et al. | Aug 2010 | B2 |
| 7769700 | D'Amico et al. | Aug 2010 | B1 |
| 7797679 | Tysowski et al. | Sep 2010 | B2 |
| 7811172 | Asher et al. | Oct 2010 | B2 |
| 7812711 | Brown et al. | Oct 2010 | B2 |
| 7813715 | McKillop et al. | Oct 2010 | B2 |
| 7817991 | Hinckley et al. | Oct 2010 | B2 |
| 7853600 | Herz et al. | Dec 2010 | B2 |
| 7904063 | Steelberg et al. | Mar 2011 | B1 |
| 7907901 | Kahn et al. | Mar 2011 | B1 |
| 7912020 | Khasawneh et al. | Mar 2011 | B2 |
| 7913297 | Wyld | Mar 2011 | B2 |
| 7925656 | Liu et al. | Apr 2011 | B2 |
| 7926056 | Lier et al. | Apr 2011 | B2 |
| 7932892 | Chen et al. | Apr 2011 | B2 |
| 7941831 | Mandhana et al. | May 2011 | B2 |
| 7983616 | Wang et al. | Jul 2011 | B2 |
| 8036822 | Ho | Oct 2011 | B2 |
| 8065718 | Grove et al. | Nov 2011 | B2 |
| 8139820 | Plante et al. | Mar 2012 | B2 |
| 8170524 | Abbot et al. | May 2012 | B2 |
| 8200624 | Clegg et al. | Jun 2012 | B2 |
| 8239092 | Plante et al. | Aug 2012 | B2 |
| 8243423 | Ranta et al. | Aug 2012 | B2 |
| 8248245 | Talach et al. | Aug 2012 | B2 |
| 8474050 | Casimere et al. | Jun 2013 | B2 |
| 8489895 | Tan, Jr. | Jul 2013 | B2 |
| 8499356 | Byrne et al. | Jul 2013 | B2 |
| 8533494 | Harada | Sep 2013 | B2 |
| 8566651 | Liu et al. | Oct 2013 | B2 |
| 8568224 | Itkis et al. | Oct 2013 | B1 |
| 8630897 | Prada Gomez | Jan 2014 | B1 |
| 9037852 | Pinkus et al. | May 2015 | B2 |
| 9157748 | Millspaugh | Oct 2015 | B2 |
| 9646326 | Goralnick | May 2017 | B2 |
| 10776837 | Roivainen | Sep 2020 | B2 |
| 10957227 | Delorean | Mar 2021 | B2 |
| 11238498 | Knowles et al. | Feb 2022 | B2 |
| 20010042045 | Howard et al. | Nov 2001 | A1 |
| 20020023027 | Simonds | Feb 2002 | A1 |
| 20020026321 | Faris et al. | Feb 2002 | A1 |
| 20020049683 | Ricard | Apr 2002 | A1 |
| 20020052751 | Ebata | May 2002 | A1 |
| 20020065836 | Sasaki | May 2002 | A1 |
| 20020072963 | Jonge | Jun 2002 | A1 |
| 20020087500 | Berkowitz et al. | Jul 2002 | A1 |
| 20020091473 | Gardner et al. | Jul 2002 | A1 |
| 20020107027 | O'Neil | Aug 2002 | A1 |
| 20020111154 | Eldering | Aug 2002 | A1 |
| 20020120590 | Richard | Aug 2002 | A1 |
| 20020136407 | Denning et al. | Sep 2002 | A1 |
| 20020156699 | Gray | Oct 2002 | A1 |
| 20020164962 | Mankins et al. | Nov 2002 | A1 |
| 20020170962 | Besling | Nov 2002 | A1 |
| 20020174355 | Rajasekaran et al. | Nov 2002 | A1 |
| 20020186144 | Meunier | Dec 2002 | A1 |
| 20030022719 | Donald et al. | Jan 2003 | A1 |
| 20030032460 | Cannon et al. | Feb 2003 | A1 |
| 20030034873 | Chase et al. | Feb 2003 | A1 |
| 20030037237 | Abgrall et al. | Feb 2003 | A1 |
| 20030061080 | Ross | Mar 2003 | A1 |
| 20030068999 | Casali et al. | Apr 2003 | A1 |
| 20030079122 | Asokan et al. | Apr 2003 | A1 |
| 20030084332 | Krasinski et al. | May 2003 | A1 |
| 20030139941 | Matsumoto | Jul 2003 | A1 |
| 20030144906 | Fujimoto et al. | Jul 2003 | A1 |
| 20030169162 | Hyman | Sep 2003 | A1 |
| 20030177020 | Okamura | Sep 2003 | A1 |
| 20030177373 | Moyer et al. | Sep 2003 | A1 |
| 20030216960 | Postrel | Nov 2003 | A1 |
| 20030217270 | Nakayama | Nov 2003 | A1 |
| 20030220835 | Barnes | Nov 2003 | A1 |
| 20030222134 | Boyd | Dec 2003 | A1 |
| 20040064415 | Abdallah et al. | Apr 2004 | A1 |
| 20040078118 | Binder | Apr 2004 | A1 |
| 20040078141 | Kittell et al. | Apr 2004 | A1 |
| 20040093280 | Yamaguchi | May 2004 | A1 |
| 20040093312 | Cordery et al. | May 2004 | A1 |
| 20040112959 | Jun | Jun 2004 | A1 |
| 20040119589 | French | Jun 2004 | A1 |
| 20040143378 | Vogelsang | Jul 2004 | A1 |
| 20040162802 | Jonas | Aug 2004 | A1 |
| 20040176081 | Bryham | Sep 2004 | A1 |
| 20040177109 | Lee | Sep 2004 | A1 |
| 20040192351 | Duncan | Sep 2004 | A1 |
| 20040210757 | Kogan et al. | Oct 2004 | A1 |
| 20040219933 | Faith | Nov 2004 | A1 |
| 20040225440 | Khatwa et al. | Nov 2004 | A1 |
| 20040225557 | Phelan et al. | Nov 2004 | A1 |
| 20040253923 | Braley et al. | Dec 2004 | A1 |
| 20050131597 | Raz et al. | Jun 2005 | A1 |
| 20050190619 | Wakiyama | Sep 2005 | A1 |
| 20050209970 | Shiba et al. | Sep 2005 | A1 |
| 20050216134 | Katrak et al. | Sep 2005 | A1 |
| 20050229012 | Douceur et al. | Oct 2005 | A1 |
| 20060033840 | Diehl et al. | Feb 2006 | A1 |
| 20060034201 | Umeda et al. | Feb 2006 | A1 |
| 20060036501 | Shahbazi et al. | Feb 2006 | A1 |
| 20060069749 | Herz et al. | Mar 2006 | A1 |
| 20060089912 | Spagna et al. | Apr 2006 | A1 |
| 20060095329 | Kim | May 2006 | A1 |
| 20060131401 | Do | Jun 2006 | A1 |
| 20060135120 | Likourezos | Jun 2006 | A1 |
| 20060143455 | Gitzinger | Jun 2006 | A1 |
| 20060164257 | Giubbini | Jul 2006 | A1 |
| 20060168580 | Harada et al. | Jul 2006 | A1 |
| 20060182055 | Coffee et al. | Aug 2006 | A1 |
| 20060200430 | Kim | Sep 2006 | A1 |
| 20060206433 | Scoggins | Sep 2006 | A1 |
| 20060242058 | Torto | Oct 2006 | A1 |
| 20060259790 | Asokan et al. | Nov 2006 | A1 |
| 20060267860 | Rinaldo et al. | Nov 2006 | A1 |
| 20060276960 | Adamczyk et al. | Dec 2006 | A1 |
| 20060282649 | Malamud et al. | Dec 2006 | A1 |
| 20070032195 | Kurisko et al. | Feb 2007 | A1 |
| 20070075874 | Shah et al. | Apr 2007 | A1 |
| 20070082614 | Mock | Apr 2007 | A1 |
| 20070109106 | Maeda et al. | May 2007 | A1 |
| 20070123166 | Sheynman et al. | May 2007 | A1 |
| 20070125843 | Byerly | Jun 2007 | A1 |
| 20070126601 | Park | Jun 2007 | A1 |
| 20070179910 | Ferraro | Aug 2007 | A1 |
| 20070200663 | White et al. | Aug 2007 | A1 |
| 20070208864 | Flynn et al. | Sep 2007 | A1 |
| 20070213047 | Kolker | Sep 2007 | A1 |
| 20070226777 | Burton et al. | Sep 2007 | A1 |
| 20070257813 | Vaswani et al. | Nov 2007 | A1 |
| 20070257815 | Gunderson et al. | Nov 2007 | A1 |
| 20080018730 | Roth | Jan 2008 | A1 |
| 20080040210 | Hedley | Feb 2008 | A1 |
| 20080045234 | Reed | Feb 2008 | A1 |
| 20080048886 | Brown et al. | Feb 2008 | A1 |
| 20080057868 | Chang | Mar 2008 | A1 |
| 20080082397 | Dennison et al. | Apr 2008 | A1 |
| 20080082403 | Adegoke et al. | Apr 2008 | A1 |
| 20080102793 | Venkatesan et al. | May 2008 | A1 |
| 20080113618 | De et al. | May 2008 | A1 |
| 20080114707 | Steiner | May 2008 | A1 |
| 20080122606 | Bradley | May 2008 | A1 |
| 20080126665 | Burr et al. | May 2008 | A1 |
| 20080147268 | Fuller | Jun 2008 | A1 |
| 20080162260 | Rohan et al. | Jul 2008 | A1 |
| 20080166968 | Tang et al. | Jul 2008 | A1 |
| 20080195428 | Osullivan | Aug 2008 | A1 |
| 20080235517 | Ohmori et al. | Sep 2008 | A1 |
| 20080235811 | Yan | Sep 2008 | A1 |
| 20080248748 | Sangster et al. | Oct 2008 | A1 |
| 20080270204 | Poykko et al. | Oct 2008 | A1 |
| 20080285626 | Ma et al. | Nov 2008 | A1 |
| 20080287062 | Claus et al. | Nov 2008 | A1 |
| 20080294312 | Oconnor et al. | Nov 2008 | A1 |
| 20080319604 | Follmer et al. | Dec 2008 | A1 |
| 20080319666 | Petrov et al. | Dec 2008 | A1 |
| 20090009321 | McClellan et al. | Jan 2009 | A1 |
| 20090024419 | McClellan et al. | Jan 2009 | A1 |
| 20090030885 | Depasquale et al. | Jan 2009 | A1 |
| 20090034591 | Julian et al. | Feb 2009 | A1 |
| 20090061769 | Zimbric et al. | Mar 2009 | A1 |
| 20090079555 | Aguirre et al. | Mar 2009 | A1 |
| 20090083833 | Ziola et al. | Mar 2009 | A1 |
| 20090096573 | Graessley | Apr 2009 | A1 |
| 20090098855 | Fernandez et al. | Apr 2009 | A1 |
| 20090111378 | Sheynman et al. | Apr 2009 | A1 |
| 20090112723 | Gottesman et al. | Apr 2009 | A1 |
| 20090118002 | Lyons | May 2009 | A1 |
| 20090156123 | Kim | Jun 2009 | A1 |
| 20090156241 | Staffaroni et al. | Jun 2009 | A1 |
| 20090157255 | Plante | Jun 2009 | A1 |
| 20090169006 | Zick et al. | Jul 2009 | A1 |
| 20090186577 | Ross et al. | Jul 2009 | A1 |
| 20090207014 | Ayed | Aug 2009 | A1 |
| 20090210343 | Griffin | Aug 2009 | A1 |
| 20090234745 | Ramer et al. | Sep 2009 | A1 |
| 20090254259 | The | Oct 2009 | A1 |
| 20090254270 | Yu | Oct 2009 | A1 |
| 20090270036 | Michaud | Oct 2009 | A1 |
| 20090271289 | Klinger et al. | Oct 2009 | A1 |
| 20090281818 | Li et al. | Nov 2009 | A1 |
| 20090286479 | Thoresson et al. | Nov 2009 | A1 |
| 20090325491 | Bell et al. | Dec 2009 | A1 |
| 20090326991 | Wei et al. | Dec 2009 | A1 |
| 20100022217 | Ketari | Jan 2010 | A1 |
| 20100027414 | Hamachi | Feb 2010 | A1 |
| 20100030582 | Rippel et al. | Feb 2010 | A1 |
| 20100036717 | Trest | Feb 2010 | A1 |
| 20100037063 | Chontos et al. | Feb 2010 | A1 |
| 20100045452 | Periwal | Feb 2010 | A1 |
| 20100063857 | Malik | Mar 2010 | A1 |
| 20100077115 | Rofougaran | Mar 2010 | A1 |
| 20100094780 | Trzcinski | Apr 2010 | A1 |
| 20100125510 | Smith et al. | May 2010 | A1 |
| 20100167643 | Hirsch | Jul 2010 | A1 |
| 20100167646 | Alameh et al. | Jul 2010 | A1 |
| 20100194549 | Tonokawa et al. | Aug 2010 | A1 |
| 20100199325 | Raleigh | Aug 2010 | A1 |
| 20100217507 | Braunberger et al. | Aug 2010 | A1 |
| 20100227549 | Kozlay | Sep 2010 | A1 |
| 20100241857 | Okude et al. | Sep 2010 | A1 |
| 20100246824 | Julian et al. | Sep 2010 | A1 |
| 20100250060 | Maeda et al. | Sep 2010 | A1 |
| 20100255782 | Klemmensen | Oct 2010 | A1 |
| 20100259058 | Knighton et al. | Oct 2010 | A1 |
| 20100265034 | Cap et al. | Oct 2010 | A1 |
| 20100299207 | Harlev | Nov 2010 | A1 |
| 20100299212 | Graylin et al. | Nov 2010 | A1 |
| 20100318578 | Treu et al. | Dec 2010 | A1 |
| 20100330908 | Maddern et al. | Dec 2010 | A1 |
| 20100332312 | Klinger et al. | Dec 2010 | A1 |
| 20110009107 | Guba et al. | Jan 2011 | A1 |
| 20110012720 | Hirschfeld | Jan 2011 | A1 |
| 20110022474 | Jain | Jan 2011 | A1 |
| 20110022477 | Hatridge | Jan 2011 | A1 |
| 20110022764 | Ohkubo et al. | Jan 2011 | A1 |
| 20110047062 | Kerschner | Feb 2011 | A1 |
| 20110053552 | Kim et al. | Mar 2011 | A1 |
| 20110055309 | Gibor | Mar 2011 | A1 |
| 20110057815 | King et al. | Mar 2011 | A1 |
| 20110077056 | Park et al. | Mar 2011 | A1 |
| 20110093340 | Kramer et al. | Apr 2011 | A1 |
| 20110099040 | Felt et al. | Apr 2011 | A1 |
| 20110112770 | Kuramori | May 2011 | A1 |
| 20110119491 | Nocera | May 2011 | A1 |
| 20110124321 | Sagong et al. | May 2011 | A1 |
| 20110131153 | Grim et al. | Jun 2011 | A1 |
| 20110153453 | Ghafoor et al. | Jun 2011 | A1 |
| 20110153495 | Dixon et al. | Jun 2011 | A1 |
| 20110185435 | Chang | Jul 2011 | A1 |
| 20110213618 | Hodge | Sep 2011 | A1 |
| 20110215900 | Corradino et al. | Sep 2011 | A1 |
| 20110307282 | Camp et al. | Dec 2011 | A1 |
| 20110313880 | Paul | Dec 2011 | A1 |
| 20110320259 | Roumeliotis et al. | Dec 2011 | A1 |
| 20120053805 | Dantu | Mar 2012 | A1 |
| 20120054498 | Rickman | Mar 2012 | A1 |
| 20120072267 | Gutierrez et al. | Mar 2012 | A1 |
| 20120074927 | Ramirez | Mar 2012 | A1 |
| 20120109796 | Mashal et al. | May 2012 | A1 |
| 20120130627 | Islam et al. | May 2012 | A1 |
| 20120137126 | Matsuoka et al. | May 2012 | A1 |
| 20120041675 | Juliver et al. | Jul 2012 | A1 |
| 20120172136 | House et al. | Jul 2012 | A1 |
| 20120185302 | Kim et al. | Jul 2012 | A1 |
| 20120203441 | Higgins et al. | Aug 2012 | A1 |
| 20120226390 | Adams et al. | Sep 2012 | A1 |
| 20120226748 | Bosworth et al. | Sep 2012 | A1 |
| 20120233246 | Guemez | Sep 2012 | A1 |
| 20120303533 | Pinkus et al. | Nov 2012 | A1 |
| 20120323692 | Shutter | Dec 2012 | A1 |
| 20120323792 | Peterson et al. | Dec 2012 | A1 |
| 20120330741 | Cruz | Dec 2012 | A1 |
| 20130006722 | Ziomkowski et al. | Jan 2013 | A1 |
| 20130013412 | Altman et al. | Jan 2013 | A1 |
| 20130054281 | Thakkar et al. | Feb 2013 | A1 |
| 20130054282 | Pinkus et al. | Feb 2013 | A1 |
| 20130054361 | Rakshit | Feb 2013 | A1 |
| 20130060721 | Pinkus et al. | Mar 2013 | A1 |
| 20130061044 | Pinkus et al. | Mar 2013 | A1 |
| 20130066688 | Pinkus | Mar 2013 | A1 |
| 20130085817 | Pinkus | Apr 2013 | A1 |
| 20130104220 | Lee | Apr 2013 | A1 |
| 20130145459 | Furuichi et al. | Jun 2013 | A1 |
| 20130166387 | Hoffberg | Jun 2013 | A1 |
| 20130218647 | Kroll et al. | Aug 2013 | A1 |
| 20130246181 | Lobsenz | Sep 2013 | A1 |
| 20130253999 | Pinkus et al. | Sep 2013 | A1 |
| 20130332075 | Wang et al. | Dec 2013 | A1 |
| 20140039784 | Millspaugh | Feb 2014 | A1 |
| 20140040016 | Amla et al. | Feb 2014 | A1 |
| 20140067195 | James et al. | Mar 2014 | A1 |
| 20140067488 | James et al. | Mar 2014 | A1 |
| 20140067489 | James et al. | Mar 2014 | A1 |
| 20140067490 | James et al. | Mar 2014 | A1 |
| 20140067491 | James et al. | Mar 2014 | A1 |
| 20140081764 | James | Mar 2014 | A1 |
| 20150310510 | Kelly | Oct 2015 | A1 |
| 20150332516 | Pinkus et al. | Nov 2015 | A1 |
| 20160370202 | James et al. | Dec 2016 | A1 |
| 20160371754 | James et al. | Dec 2016 | A1 |
| 20160373528 | Pinkus et al. | Dec 2016 | A1 |
| 20160379421 | James et al. | Dec 2016 | A1 |
| 20170024936 | Pinkus | Jan 2017 | A1 |
| 20170032422 | Pinkus et al. | Feb 2017 | A1 |
| 20190026749 | Gao et al. | Jan 2019 | A1 |
| 20190035167 | Pinkus | Jan 2019 | A1 |
| 20190043089 | Pinkus et al. | Feb 2019 | A1 |
| 20190213801 | Pinkus et al. | Jul 2019 | A1 |
| 20200014757 | Pinkus et al. | Jan 2020 | A1 |
| 20200035042 | Pinkus | Jan 2020 | A1 |
| 20200211142 | James et al. | Jul 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2261370 | Aug 2000 | CA |
| 2938649 | Aug 2007 | CN |
| 201229596 | Apr 2009 | CN |
| 101488784 | Jul 2009 | CN |
| 101834903 | Sep 2010 | CN |
| 101834903 | Sep 2010 | CN |
| 3636353 | Nov 1987 | DE |
| 3736258 | May 1989 | DE |
| 3922373 | Jan 1991 | DE |
| 10120781 | May 2003 | DE |
| 102005052872 | Jul 2007 | DE |
| 202008005583 | Jul 2008 | DE |
| 0261433 | Mar 1988 | EP |
| 0265708 | May 1988 | EP |
| 0313882 | May 1989 | EP |
| 0406663 | Nov 1992 | EP |
| 0600818 | Jun 1994 | EP |
| 1358748 | Nov 2003 | EP |
| 1455487 | Sep 2004 | EP |
| 1887770 | Feb 2008 | EP |
| 1975899 | Oct 2008 | EP |
| 2073160 | Jun 2009 | EP |
| 2751785 | Jul 2014 | EP |
| 2494909 | Mar 2013 | GB |
| 06-012419 | Jan 1994 | JP |
| 6-12419 | Jan 1994 | JP |
| 2002-063690 | Feb 2002 | JP |
| 2002063690 | Feb 2002 | JP |
| 2002312811 | Oct 2002 | JP |
| 2003-115061 | Apr 2003 | JP |
| 2003115061 | Apr 2003 | JP |
| 2004-280329 | Oct 2004 | JP |
| 2004280329 | Oct 2004 | JP |
| 2009145080 | Jul 2009 | JP |
| 2009198418 | Sep 2009 | JP |
| 950014892 | Dec 1995 | KR |
| 20030017805 | Mar 2003 | KR |
| 20060098940 | Sep 2006 | KR |
| 20070075874 | Jul 2007 | KR |
| 20080005800 | Jan 2008 | KR |
| 100863420 | Oct 2008 | KR |
| 20090047144 | May 2009 | KR |
| 20090081136 | Jul 2009 | KR |
| 20100120898 | Nov 2010 | KR |
| 10-2012-0040478 | Apr 2012 | KR |
| 20120040478 | Apr 2012 | KR |
| 10-2012-0050023 | May 2012 | KR |
| 20120050023 | May 2012 | KR |
| 44193 | Feb 2005 | RU |
| 9952084 | Oct 1999 | WO |
| 0217567 | Feb 2002 | WO |
| WO 2002017567 | Feb 2002 | WO |
| 02102019 | Dec 2002 | WO |
| 2004047046 | Jun 2004 | WO |
| 2004047046 | Jun 2004 | WO |
| 2006119854 | Nov 2006 | WO |
| 2007118221 | Oct 2007 | WO |
| 2008082779 | Jul 2008 | WO |
| 2008157618 | Dec 2008 | WO |
| 2009129957 | Oct 2009 | WO |
| 2010010409 | Jan 2010 | WO |
| WO 2010010409 | Jan 2010 | WO |
| 2011038269 | Mar 2011 | WO |
| 2011056044 | May 2011 | WO |
| 2011067741 | Jun 2011 | WO |
| WO 2011067741 | Jun 2011 | WO |
| 2011085145 | Jul 2011 | WO |
| 2012051359 | Apr 2012 | WO |
| WO 2012051359 | Apr 2012 | WO |
| 2012162100 | Nov 2012 | WO |
| 2013049408 | Apr 2013 | WO |
| WO 2013049408 | Apr 2013 | WO |
| 2014036330 | Mar 2014 | WO |
| 2014036331 | Mar 2014 | WO |
| 2014036332 | Mar 2014 | WO |
| 2014036333 | Mar 2014 | WO |
| 2014036335 | Mar 2014 | WO |
| WO 2014036330 | Mar 2014 | WO |
| WO 2014036331 | Mar 2014 | WO |
| WO 2014036332 | Mar 2014 | WO |
| WO 2014036335 | Mar 2014 | WO |
| 2013033468 | May 2014 | WO |
| 2013033470 | May 2014 | WO |
| Entry |
|---|
| Deaton, Jamie Page, “How Taxi Meters Work”, Title page <http://auto.howstuffworks.com/taxi-meter.htm> (<http://web.archive.org/web/20110423034037/http://auto.howstuffworks.com/taxi-meter.htm> captured on Apr. 23, 2011 using Wayback Machine) (Year: 2011). |
| Deaton, Jamie Page, “How Taxi Meters Work”, Common Fares page <http://auto.howstuffworks.com/taxi-meter2.htm> (<http://web.archive.org/web/20110427093054/http://auto.howstuffworks.com/taxi-meter2.htm> captured on Apr. 27, 2011 using Wayback Machine) (Year: 2011). |
| Allen, Ben, “Another Look at Xtify”, Jun. 24, 2010, 6 pages, http://www.locationawhere.com/24/06/2010/companies/xtify. |
| Baker, Rosie “London Cabs get Digital Screen Network”, MarketingWeek, Sep. 1, 2011, 1 page, http://www.marketingweek.co.uk/sectors/travel-and-leisure/london-cabs-get-digital-screen-network/3029764.article. |
| California Public Utilities Commission, “Passenger Carriers Questions and Answers”, as captured Feb. 26, 2011 in 4 pages, http://web.archive.org/web/20110226110944/http://www.cpuc.ca.gov/PUC/transportation/FAQs/psgfaqs.htm. |
| “MTData Handbook”, Premier Cabs, Revision 1.0, Dec. 2009, © 2009 Mobile Tracking and Data Pty. Ltd., pp. 49. |
| NYC Taxi & Limousine Commission, “Current Licensees”, as captured Jul. 19, 2012 in 3 pages, http://web.archive.org/web/20120719230728/http://www.nyc.gov/html/tlc/html/industry/current_licensees.shtml. |
| New York City Taxi & Limousine Commission, “Passenger Information | Taxicab Rate of Fare”, as captured Aug. 4, 2011 in 3 pages, http://web.archive.org/web/20110804040339/http://www.nyc.gov/html/tlc/html/passenger/taxicab_rate.shtml. |
| Trademark Electronic Search System (TESS), Android, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), American Express, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Blackberry, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Bluetooth, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Discover, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Falconview, Printed Sep. 5, 2013, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Flamingo, Printed Sep. 5, 2013, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Google, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), IBM, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), MacIntosh, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Mastercard, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Perl, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Python Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), QR Code, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Typed Drawing Linux, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Typed Drawing Windows XP, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Unix, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Visa, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Trademark Electronic Search System (TESS), Windows Vista, Printed Feb. 6, 2017, United States Patent and Trademark Office. |
| Official Communication in Pakistani Application No. 317/2012, dated Apr. 11, 2013. |
| International Search Report and Written Opinion in International Application No. PCT/US2012/38422, dated Aug. 17, 2012. |
| International Preliminary Report on Patentability in International Application No. PCT/US2012/38422, dated Dec. 5, 2013. |
| International Search Report and Written Opinion in International Application No. PCT/US2013/057405, dated Nov. 27, 2013. |
| International Preliminary Report and Written Opinion in International Application No. PCT/US2013/057405, dated Mar. 12, 2015. |
| International Search Report and Written Opinion in International Application No. PCT/US2013/057406, dated Nov. 27, 2013. |
| International Preliminary Report and Written Opinion in International Application No. PCT/US2013/057406, dated Mar. 12, 2015. |
| International Search Report and Written Opinion in International Application No. PCT/US2013/057407, dated Nov. 27, 2013. |
| International Preliminary Report and Written Opinion in International Application No. PCT/US2013/057407, dated Mar. 12, 2015. |
| International Search Report and Written Opinion in International Application No. PCT/US2013/057408, dated Nov. 27, 2013. |
| International Preliminary Report and Written Opinion in International Application No. PCT/US2013/057408, dated Mar. 12, 2015. |
| International Search Report and Written Opinion in International Application No. PCT/US2013/057411, dated Dec. 2, 2013. |
| International Preliminary Report and Written Opinion in International Application No. PCT/US2013/057411, dated Mar. 12, 2015. |
| “Pusar Technology Systems, Inc., Model 2030, Copyrights 2004”, https://www.taxidepot.com/taxiproducts/9tx5n06w6uyz3vrlpi32c7zals5c9b, Downloaded Feb. 1, 2023, 2004. |
| Bryant, Eric D., et al., “A Survey of Anti-Tamper Technologies”, Crosstalk The Journal of Defense Software Engineering, Nov. 2004, 12-16. |
| Islam, Md. Tofiqul, “Design and Fabrication of Fare Meter of Taxicab Using Microcontroller”, Proceedings of the International Conference on Mechanical Engineering 2005 (ICME) 28-30, Dec. 2005, Dhaka, Bangladesh. |
| Rukhande, Smita , et al., “Implementation of GPS Enabled Car Pooling System”, International Journal of Advances in Engineering & Technology, vol. 1, Issue 5, 2011, 318-328. |
| Centrodyne, Silent 620 Electronic Taximeter, https://centrodyne.com/index.php/en/products/taximeters/silent-620, Downloaded Jan. 27, 2023. |
| Dial-A-Ride Guide, Valley Metro, May 2010, in 10 pages. |
| Keinzle Argo Taxi International, Taximeter Kienzle Argo 1155 Product Sheet, 2 pages, www.kati.de. |
| Taximeter (EM-1), Qingdao Turina Electronic Co., Ltd., https://summerlee.en.ec21.com/EM_1_Taximeter--760735_3609479.html, Downloaded Jan. 23, 2023. |
| Taximeter (OM-1), Qingdao Turina Electronic Co., Ltd., https://summerlee.en.ec21.com/OM_1_Taximeter--760735_3137680.html, Downloaded Jan. 23, 2023. |
| Taximeter (TM-4), Qingdao Turina Electronic Co. Ltd., https://summerlee.en.ec21.com/TM_4_Taximeter--760735_4461770.html, Downloaded Jan. 23, 2023. |
| Taximeter Taxi Meter (TM-2); Qingdao Turina Electronic Co., Ltd .; https://summerlee.en.ec21.com/TM_2--760735_7967492.html, Downloaded Jan. 27, 2023. |
| The Philadelphia Parking Authority—Taxicab and Limousine Regulations; PPA Regs, pp. 1-74, Jul. 29, 2008 (Year: 2008). |
| “Centrodyne, Silent 610 Electronic Taximeter”, https://centrodyne.com/index.php/en/products/taximeters/silent-610, Downloaded Jan. 27, 2023. |
| “Centrodyne, Silent 620 Electronic Taximeter”, http://www.cnetrodyne.com/tax1page4.htm printed May 4, 2011 in 1 page. |
| “Centrodyne, Smart Features”, httQ:/iwww.centrodyne.com/taxli;;age6.htm printed May 4, 2011 in 1 page. |
| “Current Licensees”, NYC Taxi & Limousine Commission, as captured Jul. 19, 2012 in 3 pages. |
| “Lexmark International Inc. v. Static Control Components, Inc.”, U.S. Sixth Circuit No. 03-5400 Decided Oct. 26, 2004. |
| “Passenger Carriers Questions and Answers”, California Public Utilities Commission, as captured Feb. 26, 2011, 4 pages. |
| “Passenger Information | Taxicab Rate of Fare”, NYC Taxi & Limousine Commission, as captured Aug. 4, 2011 in 3 pages. |
| “Pulsar Technology Systems, Inc., Model 2030, Copyrights 2004”, https://www.taxidepot.com/taxiproducts/9tx5n06w6uyz3vrlpi32c7zals5c9b, Downloaded Feb. 1, 2023, 2004. |
| “Pulsar Technology Systems, Inc., Model 2030R, Copyrights 2004”, https://www.taxisource.net/index.php?route=product/product&product_id=50, Downloaded Feb. 1, 2023, 2004. |
| Arieff, Allison , “All Tomorrow's Taxis”, The New York Times Company, Jan. 13, 2011. |
| Baker, Rosie , “London Cabs Get Digital Screen Network”, https://www.marketingweek.com/london-cabs-get-digital-screen-network/, Sep. 2011. |
| Bryant, Eric D., et al., “A Survey of Anti-Tamper Technologies”, Crosstalk The Journal of Defense Software Engineering, Nov. 12-16, 2004. |
| Cagalj, Mario , et al., “Key agreement in peer-to-peer wireless networks”, Proceedings of the IEEE, vol. 94, No. 2, Feb. 2006. |
| Cassias , et al., “Vehicle Telematics: A Literature Review”, Technical Report, Oct. 30, 2007. |
| Deaton, Jamie Page, “How Taxi Meters Work”, HowStuffWorks https://auto.howstuffworks.com/taxi-meter.htm/printable (Accessed Sep. 9, 21). |
| Deaton, Jamie , “How Taxi Meters Work”, <http://auto.howstuffworks.com/taxi-meter.htm> (<http://web.archive.org/web/20110423034037/http://auto.howstuffworks.com/taxi-meter.htm> captured on Apr. 23, 2011 using Wayback Machine) (Year: 2011), 2011. |
| Deaton, Jamie , “How Taxi Meters Work”, Common Fares page <http://auto.howstuffworks.com/taxi-meter2.htm> (<http://web.archive.org/web/20110427093054/http://auto.howstuffworks.com/taxi-meter2.htm> captured on Apr. 27, 2011 using Wayback Machine) (Year: 2011), 2011. |
| Dillow, Clay , “Nevada is the First State to Pass Driverless Car Legislation, Paving the Way for Autonomous Autos”, https://www.popsci.com/cars/article/2011-06/nevada-passes-driverless-car-legislation-paving-way-autonomous-autos/, Downloaded Sep. 7, 21, Jun. 24, 2011. |
| Dodge, Martin , et al., “The automatic management of drivers and driving spaces”, Elsevier Geoforum 38 (2007), 2007, 264-275. |
| Future Technology Devices Intl , “FTDI Chip, USB-Key Datasheet, Version 1.00”, Jul. 17, 2008. |
| Gehrmann, Christian , et al., “Manual Authentication for Wireless Devices”, RSA Laboratories CryptoBytes vol. 7, No. 1 Spring 2004, 2004. |
| Harris, Lee A., “Taxicab Economics: The Freedome to Contract for a Ride”, 1 Geo, J.L. & Pub. Pol'y, 2003, 195-222. |
| Islam, Md. Tofiqul, “Design and Fabrication of Fare Meter of Taxicab Using Microcontroller”, Proceedings of the International Conference on Mechanical Engineering 2005 (ICME) Dec. 28-30, 2005, Dhaka, Bangladesh. |
| Jantarang , et al., “A Low Cost Real-Time Intelligent Taximeter Sensor”, Mahanakorn University of Technology, pp. 4, Bangkok, Thailand, 2002. |
| Rawley, Evan , “Information, Knowledge, and Asset Ownership in Taxicab Fleets”, Columbia Business School Summer Conference, Jun. 2009. |
| Number | Date | Country | |
|---|---|---|---|
| 20210209646 A1 | Jul 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15969672 | May 2018 | US |
| Child | 17074377 | US | |
| Parent | 15224338 | Jul 2016 | US |
| Child | 15969672 | US | |
| Parent | 13427695 | Mar 2012 | US |
| Child | 15224338 | US |
