US20110087430A1 - Determining travel routes by using auction-based location preferences - Google Patents
Determining travel routes by using auction-based location preferences Download PDFInfo
- Publication number
- US20110087430A1 US20110087430A1 US12/578,780 US57878009A US2011087430A1 US 20110087430 A1 US20110087430 A1 US 20110087430A1 US 57878009 A US57878009 A US 57878009A US 2011087430 A1 US2011087430 A1 US 2011087430A1
- Authority
- US
- United States
- Prior art keywords
- route
- determining
- auction
- point
- receiving
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/3453—Special cost functions, i.e. other than distance or default speed limit of road segments
- G01C21/3461—Preferred or disfavoured areas, e.g. dangerous zones, toll or emission zones, intersections, manoeuvre types, segments such as motorways, toll roads, ferries
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/3453—Special cost functions, i.e. other than distance or default speed limit of road segments
- G01C21/3476—Special cost functions, i.e. other than distance or default speed limit of road segments using point of interest [POI] information, e.g. a route passing visible POIs
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/3453—Special cost functions, i.e. other than distance or default speed limit of road segments
- G01C21/3484—Personalized, e.g. from learned user behaviour or user-defined profiles
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G01S19/00—Satellite radio beacon positioning systems; Determining position, velocity or attitude using signals transmitted by such systems
- G01S19/38—Determining a navigation solution using signals transmitted by a satellite radio beacon positioning system
- G01S19/39—Determining a navigation solution using signals transmitted by a satellite radio beacon positioning system the satellite radio beacon positioning system transmitting time-stamped messages, e.g. GPS [Global Positioning System], GLONASS [Global Orbiting Navigation Satellite System] or GALILEO
- G01S19/42—Determining position
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06316—Sequencing of tasks or work
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/14—Payment architectures specially adapted for billing systems
- G06Q20/145—Payments according to the detected use or quantity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0283—Price estimation or determination
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/08—Auctions
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
- G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
- G07B15/06—Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems
Definitions
- the present invention relates to a data processing method and system for providing a location preference in a routing algorithm, and more particularly to technique for determining travel routes that include locations as a result of auctions.
- the present invention provides a computer-implemented method of determining a route that includes a location as a result of an auction.
- the method comprises:
- a processor of a computer system determining the route so that a location of the plurality of locations is included along the route, wherein the location is associated with the vendor that wins the auction based on the bid; and presenting the determined route to the user as the recommended route.
- the present invention provides a technique for presenting travel routes to travelers, where the routes are generated so as to include locations associated with vendors that submit winning bids in auctions.
- FIG. 1 is a block diagram of a system for determining a travel route that includes a location based on an auction, in accordance with embodiments of the present invention.
- FIG. 2 is a flowchart of a process for determining a travel route in the system of FIG. 1 , where the travel route includes a location as a result of a real-time auction, in accordance with embodiments of the present invention.
- FIG. 3 is a flowchart of a process for determining a travel route in the system of FIG. 1 , where the travel route includes a location as a result of an auction initiated prior to a request for the travel route, in accordance with embodiments of the present invention.
- FIG. 4 is a flowchart of a process that determines a route according to the process of FIG. 2 or FIG. 3 and that determines additional fee(s) for auction winner(s) based on an actual route taken, in accordance with embodiments of the present invention.
- FIG. 5 is a flowchart of a process that determines a travel route according to the process of FIG. 2 or FIG. 3 and based on a rule that limits distance, in accordance with embodiments of the present invention.
- FIG. 6 is a flowchart of a process that determines a travel route according to the process of FIG. 2 or FIG. 3 and based on a rule that limits the number of recommended routes that pass through a constrained area, in accordance with embodiments of the present invention.
- FIG. 7 is a block diagram of a computer system included in the system of FIG. 1 and that implements the process of FIG. 2 and/or the process of FIG. 3 , in accordance with embodiments of the present invention.
- Embodiments of the present invention provide a preference for a given route to pass by a particular location, based on an auction.
- Multiple vendors and/or other entities bid in an auction to ensure that a route recommended to a user (i.e., traveler) passes by a particular location associated with the winning bidder (i.e., the vendor or other entity that submits the winning bid).
- a route calculation service utilizes an algorithm that takes into account a user's profile information to determine the particular vendors and/or other entities that are permitted to bid in an auction to determine a travel route.
- additional route generation rules may be applied to determine whether the route determined by the auction is actually presented to a user as a recommended route.
- FIG. 1 is a block diagram of a system for determining a travel route that includes a location as a result of an auction won by a bid submitted by a vendor associated with the location, in accordance with embodiments of the present invention.
- an auction has multiple vendors and/or other entities submitting bids for determining a route that includes a location associated with the winning bidder.
- the vendor or other entity submitting a winning bid (e.g., the highest bid) ensures that a travel route recommended to a user passes by a location associated with the vendor or other entity that submitted the winning bid.
- System 100 includes a central computer system 102 , computer systems 104 - 1 . . . 104 -N of auction participants 1 . . .
- System 100 may also include optional user profile data 114 and one or more optional route calculation rules 116 .
- User profile data 114 and route calculation rules 116 may be stored in one or more computer data storage units coupled to central computer system 102 or coupled to a data processing unit (e.g., GPS 112 ) residing in vehicle 108 .
- Computer systems 104 - 1 . . . 104 -N are managed by auction participants 1 . . . N, respectively, where N ⁇ 1.
- the auction participants 1 . . . N are herein also referred to as vendors 1 . . . N.
- the present invention contemplates that the vendors 1 . . . N may include one or more businesses and/or one or more other types of organizational entities.
- computer systems 104 - 1 . . . 104 -N send identifications of vendors 1 . . . N and identifications of multiple locations to central computer system 102 to indicate that vendors 1 . . . N may participate in an auction-based location preference system managed by central computer system 102 .
- Each vendor in vendors 1 . . . N is associated with one or more locations of the aforementioned multiple locations. For example, if Vendor 1 is associated with Location 1 and Vendor 1 is the owner of a grocery store, then Location 1 may be the site of the grocery store.
- RCS 110 receives the identifications of the vendors 1 . . . N and the identifications of the multiple locations from central computer system 102 via network 106 .
- RCS 110 determines a travel route that includes a location associated with a vendor included in vendors 1 . . . N, where the vendor submitted a winning bid in an auction.
- the central computer system 102 receives indications from multiple route calculation services in multiple vehicles (e.g., route calculation service 110 in vehicle 108 and other route calculation services in other vehicles not vehicles not shown in FIG. 1 ) of which vendors have submitted winning bids in auctions and notifies the vendor computer systems of computer systems 104 - 1 . . . 104 -N that are managed by the vendors who submitted winning bids.
- the determination of the travel route may also be based on user profile data 114 and/or route calculation rules 116 . Further descriptions of the functionality of components of system 100 are found in the discussions below relative to FIGS. 2-6 .
- FIG. 2 is a flowchart of a process for determining a travel route in the system of FIG. 1 , where the process includes a location in the travel route as a result of a real-time auction won by a bid submitted by a vendor associated with the location, in accordance with embodiments of the present invention.
- the process of determining a travel route by using a real-time auction in the system of FIG. 1 starts at step 200 .
- RCS 110 receives identifications of vendor(s) and location(s) associated with the vendor(s), where the vendor(s) are potential participants in a real-time auction to determine a travel route. That is, RCS 110 (see FIG.
- the location(s) receives an identification of each vendor who may bid in a real-time auction to ensure that a location associated with the vendor is included in a travel route determined by the RCS.
- the location(s) are associated with the vendor(s) in a one-to-one correspondence.
- the location associated with the vendor is a site (e.g., identified by address or geographic coordinates) at which the vendor conducts business.
- RCS 110 receives a request issued by a user of GPS 112 (see (see FIG. 1 ) for a travel route for vehicle 108 (see FIG. 1 ) to travel from a first geographic location (a.k.a. point A, first point or starting point) to a second geographic location (a.k.a. point B, second point or ending point).
- the request received in step 204 may include, for example, the addresses or geographic coordinates of point A and point B.
- RCS 110 retrieves user profile data from a computer data storage unit, where the user profile data describes the user who issued the request in step 204 .
- the user profile data includes data describing the user's past behavior and may also include predicted future behavior of the user.
- the user profile data may include one or more preferences that a user has for purchasing one or more particular goods and/or one or more particular services, where the preference(s) may be based on, for example, past purchases made by the user and/or user-specified selections of goods and/or services.
- RCS 110 selects a plurality of locations of the locations whose identifications are received in step 202 .
- a routing algorithm implemented by RCS 110 can include one or more locations of the plurality of locations selected in step 208 along a route that conforms to the request received in step 204 .
- a location included along a route is defined as a location that is located at an address on a segment of the route or is located at a nearest distance to the route where the nearest distance does not exceed a predefined distance or a user-specified distance.
- a location included along a route is further defined to be not the starting point of the route and not the ending point of the route.
- RCS 110 initiates an auction.
- the auction is conducted by central computer system 102 (see FIG. 1 ) to determine winning bid(s) and the vendor(s) (i.e., winning vendor(s)) that submit the winning bid(s).
- the winning bid(s) by winning vendor(s) ensure that a route from point A to point B that is to be presented to the user includes location(s) associated with the winning vendor(s).
- the central computer system determines a winning bid as being the highest-valued bid in the auction.
- the central computer system determines multiple winning bids from multiple vendors, where the multiple vendors do not compete with each other in terms of the goods and/or services they offer according to predefined criteria.
- RCS 110 determines a route from point A to point B that conforms to the request received in step 204 and that includes the location(s) associated with the winning vendor(s). The determination of the route in step 212 may also be based on user profile data optionally retrieved in step 206 .
- RCS 110 (see FIG. 1 ) notifies the user if user profile data is a basis for the route determined in step 212 . In another embodiment, the user is not notified if user profile data is a basis for the route determined in step 212 .
- RCS 110 instructs a data processing system (e.g., GPS 112 in FIG. 1 ) residing in vehicle 108 (see FIG. 1 ) that the route determined in step 212 is to be presented to the user as a recommended route.
- the data processing system e.g., GPS 112 in FIG. 1
- step 214 also includes the RCS notifying the user that the recommended route passes by the aforementioned location(s) and that the winning vendor(s) are associated with the location(s).
- the notification to the user may also include an identification of a category of goods and/or services provided by a winning vendor.
- RCS 110 receives a user's request for determining a route from point A to point B (see step 204 ).
- the RCS retrieves the user's profile data (see step 206 ), which indicates that the user likes luxury automobiles. Based on the user's request and the retrieved profile data that indicates that user likes luxury automobiles, the RCS selects Location 1 (i.e., the location of Dealer X) and Location 2 (i.e., the location of Dealer Y), where Dealer X and Dealer Y are luxury automobile dealers (see step 208 ).
- Location 1 or Location 2 may be included along a route from point A to point B, where the route is to be determined by the RCS.
- the RCS invites Dealer X and Dealer Y to participate in an auction (e.g., via web services) to ensure that the route to be determined passes by Location 1 if Dealer X wins the auction or Location 2 if Dealer Y wins the auction (see step 210 ).
- Dealer X bids $1.10 to ensure that the route passes by Location 1
- Dealer Y bids $1.05 to ensure that the route passes by Location 2 .
- Dealer X's bid amount is greater than Dealer Y's bid amount
- the RCS directs a system in the vehicle of the user to display the determined route from point A to point B as a recommended route (see step 214 ).
- the RCS notifies the user that the recommended route passes by Location 1 and that Location 1 is associated with Dealer X. After the user takes the recommended route and actually drives past Location 1 , an entity controlling the RCS and the user are paid for their participation based on the amount bid by Dealer X in the auction.
- multiple routes from point A to point B are presented to the user and the user is compensated (e.g., with a credit to an account) in response to the user selecting the recommended route instead of the other presented routes.
- a user requests a route from point A to point B (see step 204 ) and the user's profile data indicates a preference for luxury automobiles and for visiting coffee shops (see step 206 ).
- the auction (see step 210 ) accepts bids from a first set of luxury automobile dealer vendors and bids from a second set of coffee shop vendors. The result of the auction is that luxury Automobile Dealer 1 (i.e., the luxury automobile dealer that submitted the highest bid among the first set of vendors) is a first winning vendor and Coffee Shop 1 (i.e., the coffee shop vendor that submitted the highest bid among the second set of vendors) is a second winning vendor.
- the RCS determines a route from point A to point B (see step 212 ) that includes Location 1 and Location 2 , where Location 1 is the site at which luxury Automobile Dealer 1 conducts business and where Location 2 is the site of Coffee Shop 1 .
- FIG. 3 is a flowchart of a process for determining a travel route in the system of FIG. 1 , where the process includes a location in the travel route as a result of an auction initiated prior to receiving a request for determining the route (a.k.a. an ahead-of-time auction), in accordance with embodiments of the present invention.
- the process of determining a travel route by using an ahead-of-time auction in the system of FIG. 1 starts at step 300 .
- RCS 110 receives parameters from vendors and bids from vendors for an auction in which the winning bid(s) submitted by winning vendor(s) ensure that a route to be presented to a user includes location(s) associated with the winning vendor(s).
- the location(s) are associated with the vendor(s) in a one-to-one correspondence.
- the location associated with the vendor is a site (e.g., identified by an address or geographic coordinates) at which the vendor conducts business.
- One or more parameters received in step 302 may specify how a particular vendor's bid in the auction varies based on predefined criteria. For example, parameters may specify how a vendor's bid varies by: the time of day at which the route is requested, the value of a particular customer based on the customer's past behavior (e.g., past purchases) or predicted future behavior in the user profile data, and/or events that occurred (or will occur) within a specified time period in an area through which a requested route passes.
- One or more parameters received in step 302 may specify a pre-cached auction bid.
- Multiple vendors may submit pre-cached auction bids that allow the auction to be conducted instantaneously (see step 310 ) in response to receiving the user's request for a route from point A to point B (see step 304 ) and selecting locations that can be included along routes from point A to point B (see step 308 ).
- the parameter(s) specifying a pre-cached auction bid by a vendor includes the vendor's maximum bid amount for auctions to be conducted.
- the parameters include X and N, where the vendor's maximum pre-cached auction bid amount X is submitted for N auctions.
- the parameters include X, N and T, where the vendor's maximum pre-cached auction bid amount X is submitted for N auctions, where there is not less than T time units between successive auctions.
- a vendor may specify parameters that indicate the vendor is willing to bid up to $1.20 20 times for auctions where successive auctions are not less than 20 minutes apart.
- RCS 110 receives a request issued by a user of GPS 112 (see FIG. 1 ) for a travel route for vehicle 108 (see FIG. 1 ) to travel from a first geographic location (a.k.a. point A, first point or starting point) to a second geographic location (a.k.a. point B, second point or ending point).
- the request received in step 304 may include, for example, the addresses or geographic coordinates of point A and point B.
- RCS 110 retrieves user profile data from a computer data storage unit, where the user profile data describes the user who issued the request in step 304 .
- the user profile data includes data describing the user's past behavior and may also include predicted future behavior of the user.
- the user profile data may include one or more preferences that a user has for purchasing one or more particular goods and/or one or more particular services, where the preference(s) may be based on, for example, past purchases made by the user and/or user-specified selections of goods and/or services.
- RCS 110 selects a plurality of locations of the locations associated with the vendors whose bids are received in step 302 .
- a routing algorithm implemented by RCS 110 can include one or more locations of the plurality of locations selected in step 308 along a route that conforms to the request received in step 304 .
- RCS 110 completes the auction by determining the winning bid(s) and the winning vendor(s) that submit the winning bid(s) in the auction.
- the winning bid(s) by winning vendor(s) ensure that a route from point A to point B that is to be presented to the user includes location(s) associated with the winning vendor(s).
- step 312 RCS 110 (see FIG. 1 ) determines a route from point A to point B that conforms to the request received in step 304 and that includes the location(s) associated with the winning vendor(s). The determination of the route in step 312 may also be based on user profile data optionally retrieved in step 306 .
- RCS 110 (see FIG. 1 ) notifies the user if user profile data is a basis for the route determined in step 312 . In another embodiment, the user is not notified if user profile data is a basis for the route determined in step 312 .
- RCS 110 instructs a data processing system (e.g., GPS 112 in FIG. 1 ) residing in vehicle 108 (see FIG. 1 ) that the route determined in step 312 is to be presented to the user as a recommended route.
- the data processing system e.g., GPS 112 in FIG. 1
- an entity controlling the RCS, the user, and/or another party are compensated for their participation based on the amount bid by the winning vendor.
- the process of FIG. 3 ends at step 316 .
- step 314 also includes the RCS notifying the user that the recommended route passes by the aforementioned location(s) and that the winning vendor(s) are associated with the location(s).
- the notification to the user may also include an identification of a a category of goods and/or services provided by a winning vendor.
- a user may pull a route based on explicit user profile data items being specified for a particular trip event that requires a travel route to be determined and recommended. For example, the user may specify a distance over and above the length of the shortest route that the user is willing to travel. As another example, the user may specify service(s) and/or product(s) (e.g., grocery store) the user would like to travel near during a given trip.
- the route determined in step 212 (see FIG. 2 ) or in step 312 may include location(s) selected in step 208 (see FIG. 2 ) or step 308 , respectively, where the location(s) are selected because they provide the service(s) and/or product(s) specified by the user.
- Possible methods for funding and providing incentives for the processes in FIG. 2 and FIG. 3 may include:
- FIG. 4 is a flowchart of a process for determining a surcharge based on an actual route taken subsequent to a presentation of a recommended route in the process of FIG. 2 or FIG. 3 , in accordance with embodiments of the present invention.
- the surcharge determination process of FIG. 4 starts at step 400 .
- step 402 by performing the steps of the process of FIG. 2 or FIG. 3 , RCS 110 (see FIG. 1 ) determines a travel route that includes location(s) associated with winning vendor(s) and the determined travel route is presented to the user as a recommended route.
- step 404 GPS 112 (see FIG. 1 ) located in the user's vehicle 108 (see FIG. 1 ) tracks the actual route taken by the user's vehicle.
- step 406 RCS 110 (see FIG. 1 ) determines whether one or more locations that are included in the recommended route and that are associated with one or more winning vendor(s) are included in the actual route traveled by the user in vehicle 108 (see FIG. 1 ).
- step 406 includes RCS 110 (see FIG. 1 ) determining whether the actual route traveled by vehicle 108 (see FIG. 1 ) is the recommended route determined in step 402 .
- step 406 determines that location(s) associated with winning vendor(s) are located along the actual route taken by vehicle 108 (see FIG. 1 ), then in step 408 RCS 110 (see FIG. 1 ) determines surcharge(s) to be charged to the winning vendor(s) associated with the location(s) that are along the actual route taken by the user's vehicle. For example, if Vendor 1 is a winning vendor that had bid X in the auction initiated in step 210 (see FIG. 2 ) or step 302 (see FIG.
- Vendor 1 pays X+S as a result of Vendor 1 winning the auction and the user's vehicle traveling an actual route that includes the location associated with Vendor 1 .
- step 410 the process of FIG. 4 ends at step 410 .
- RCS 110 determines that no location(s) associated with the winning vendor(s) are along the actual route taken by vehicle 108 (see FIG. 1 )
- the process of FIG. 4 ends at step 410 .
- a rule-based route determination process determines a route according to the process of FIG. 2 through step 212 or the process of FIG. 3 through step 312 , and indicates whether or not the determined route is a recommended route based on the application of a predefined route calculation rule (i.e., based on whether a measurement of the determined route satisfies a predefined rule).
- One or more route calculation rules 116 are received and stored in a computer data storage unit.
- the computer data storage unit may be coupled to GPS 112 (see FIG. 1 ) or computer system 102 (see FIG. 1 ).
- the received route calculation rule(s) 116 indicate that one or more measurements of a recommended route from point A to point B presented in the process of FIG.
- the difference between the measurement of a recommended route and the corresponding measurement of the optimal route, and the corresponding predefined threshold value may be expressed as a number of units of the measurement, a percentage, or a ratio.
- One rule 116 may indicate that the distance of a recommended route must not exceed a distance of a shortest-distance route from point A to point B by more than X % or by more than a distance of X units (e.g., X miles), where X is a predefined value (see the discussion of FIG. 5 presented below).
- Another rule 116 may indicate that the time for traveling the recommended route from point A to point B must not exceed a time for traveling the shortest-time route from point A to point B by more than X % or by more than a time of X units (e.g., X minutes), where X is a predefined value.
- RCS 110 retrieves a rule 116 from the aforementioned computer data storage unit, where the rule states that in order for a determined route to be a recommended route, the difference N between a measurement of the determined route and a corresponding measurement of an optimal route must not exceed threshold value X.
- the optimal route is the route that is optimized according to the corresponding measurement.
- RCS 110 determines the difference N is not greater than threshold value X, then the RCS designates the determined route to be a recommended route, the GPS 112 (see FIG. 1 ) presents (e.g., displays) the recommended route to the user, and the rule-based route determination process ends.
- RCS 110 determines that the difference N is greater than the threshold value X, then the RCS indicates that the determined route is not a recommended route and is not to be presented to the user and the rule-based route determination process ends.
- the rule-based route determination process utilizes a distance limiting rule, as described below relative to FIG. 5 .
- FIG. 5 is a flowchart of a process for determining a travel route according to the process of FIG. 2 or FIG. 3 and based on a rule that limits the distance of the recommended route, in accordance with embodiments of the present invention.
- the process of FIG. 5 begins at step 500 .
- one or more route calculation rules 116 are received and stored in a computer data storage unit.
- the computer data storage unit may be coupled to GPS 112 (see FIG. 1 ) or computer system 102 (see FIG. 1 ).
- the received route calculation rule(s) 116 include a distance-limiting rule that indicates that the length of a recommended route from point A to point B presented in the process of FIG. 2 or FIG. 3 is not permitted to exceed the length of an optimal (i.e., shortest) route from point A to point B by more than X %.
- steps 202 - 212 (see FIG. 2 ) or steps 302 - 312 (see FIG. 3 ) are performed by RCS 110 (see FIG. 1 ) to determine a route from point A to point B.
- RCS 110 retrieves the distance-limiting rule from the aforementioned computer data storage unit. Also in step 506 , RCS 110 (see FIG. 1 ) determines that the length of the route determined in step 504 is N % more than the length of the optimal route from point A to point B.
- step 508 determines in step 508 that N % is not greater than X %, then the No branch of step 508 is taken and step 510 is performed.
- step 510 RCS 110 (see FIG. 1 ) designates the route determined in step 504 as a recommended route.
- step 512 the GPS 112 (see FIG. 1 ) presents (e.g., displays) the recommended route to the user. The process of FIG. 5 ends at step 514 .
- step 516 the RCS indicates that the route determined in step 504 is not a recommended route and is not to be presented to the user. Following step 516 , the process of FIG. 5 ends at step 514 .
- the rule received in step 502 indicates that the length of the recommended route is not permitted to exceed the length of the optimal route by more than a distance X (e.g., X miles) and step 506 determines that the length of the route determined in step 504 is a distance N longer than the length of the optimal route. Furthermore, in this alternate embodiment, step 508 determines whether N>X.
- a distance X e.g., X miles
- FIG. 6 is a flowchart of a process for determining a travel route according to the process of FIG. 2 or FIG. 3 and based on a rule that limits the number of recommended routes that pass through a constrained area.
- the process of FIG. 6 starts at step 600 .
- one or more route calculation rules 116 are received and stored in a computer data storage unit.
- the computer data storage unit may be coupled to GPS 112 (see FIG. 1 ) or computer system 102 (see FIG. 1 ).
- the received route calculation rule(s) 116 include a recommended routes quantity-limiting rule that indicates that the number of recommended routes presented by multiple performances of steps 204 - 214 (see FIG. 2 ) or steps 304 - 314 (see FIG. 3 ), where the recommended routes pass through a constrained area, is not permitted to exceed a predefined predefined number X.
- RCS 110 receives an indication of an area (a.k.a. constrained area) that is constrained according to predefined criteria.
- step 606 the steps 204 - 214 (see FIG. 2 ) or steps 304 - 314 (see FIG. 3 ) are performed and may be repeated until N routes determined by step 212 (see FIG. 2 ) or step 312 (see FIG. 3 ) are recommended and presented in step 214 (see FIG. 2 ) or step 314 (see FIG. 3 ), where N ⁇ 1, and where each of the N recommended routes pass through the constrained area indicated in step 604 .
- step 608 steps 204 - 212 (see FIG. 2 ) or steps 304 - 312 (see FIG. 3 ) are performed to determine an (N+1)-th route that passes through the constrained area whose indication is received in step 604 .
- step 610 If RCS 110 (see FIG. 1 ) determines in step 610 that N+1 is not greater than X, then the No branch of step 610 is taken and step 612 is performed.
- step 612 RCS 110 (see FIG. 1 ) designates the (N+1)-th route determined in step 608 as the (N+1)-th recommended route.
- step 614 the GPS 112 (see FIG. 1 ) presents (e.g., displays) the (N+1)-th recommended route to the user.
- the process of FIG. 6 ends at step 616 .
- step 618 the RCS indicates that the (N+1)-th route determined in step 608 is not a recommended route and is not to be presented to the user.
- step 618 indicates that the (N+1)-th route is not a recommended route and is not to be presented to the user in order to prevent a traffic jam in the constrained area.
- step 618 is replaced with (1) the RCS 110 (see FIG. 1 ) identifying the constrained area as having congested traffic based on the N recommended routes previously presented to users (or based on an indication received by the RCS in a previous step), (2) the RCS determining that the (N+1)-th route passes through the area of congested traffic, and (3) the RCS determining a fee to charge a vendor whose associated location is along the (N+1)-th route. The fee is charged for proposing routes for any additional vehicles to travel through the congested area, thereby promoting environmental stewardship by potentially reducing the number of additional vehicles entering the congested area.
- FIG. 7 is a computer system that is included in the system of FIG. 1 and that implements the process of FIG. 2 and/or the process of FIG. 3 , in accordance with embodiments of the present invention.
- Computer system 700 generally comprises a central processing unit (CPU) 702 , a memory 704 , an input/output (I/O) interface 706 , and a bus 708 . Further, computer system 700 is coupled to I/O devices 710 and a computer data storage unit 712 .
- CPU 702 performs computation and control functions of computer system 700 .
- CPU 702 may comprise a single processing unit, or be distributed across one or more processing units in one or more locations (e.g., on a client and server).
- computer system 700 implements RCS 110 (see FIG. 1 ) and may reside in vehicle 108 (see FIG. 1 ).
- computer system 700 is GPS 112 (see FIG. 1 ).
- Memory 704 may comprise any known computer readable storage medium, which is described below.
- cache memory elements of memory 704 provide temporary storage of at least some program code (e.g., program code 714 ) in order to reduce the number of times code must be retrieved from bulk storage while instructions of the program code are carried out.
- program code 714 program code 714
- memory 704 may reside at a single physical location, comprising one or more types of data storage, or be distributed across a plurality of physical systems in various forms. Further, memory 704 can include data distributed across, for example, a local area network (LAN) or a wide area network (WAN).
- LAN local area network
- WAN wide area network
- I/O interface 706 comprises any system for exchanging information to or from an external source.
- I/O devices 710 comprise any known type of external device, including a display device (e.g., monitor), keyboard, mouse, printer, speakers, handheld device, facsimile, etc. Bus etc.
- Bus 708 provides a communication link between each of the components in computer system 700 , and may comprise any type of transmission link, including electrical, optical, wireless, etc.
- I/O interface 706 also allows computer system 700 to store and retrieve information (e.g., data or program instructions such as program code 714 ) from an auxiliary storage device such as computer data storage unit 712 or another computer data storage unit (not shown).
- Computer data storage unit 712 may comprise any known computer readable storage medium, which is described below.
- computer data storage unit 712 may be a non-volatile data storage device, such as a magnetic disk drive (i.e., hard disk drive) or an optical disc drive (e.g., a CD-ROM drive which receives a CD-ROM disk).
- Memory 704 may include computer program code 714 that provides the logic for determining a travel route that includes a location as a result of an auction (e.g., the process of FIG. 2 or FIG. 3 ). Further, memory 704 may include other systems not shown in FIG. 7 , such as an operating system (e.g., Linux) that runs on CPU 702 and provides control of various components within and/or connected to computer system 700 .
- an operating system e.g., Linux
- Memory 704 , storage unit 712 , and/or one or more other computer data storage units (not shown) that are coupled to computer system 700 may store a database (e.g., central database 104 in FIG. 1 ).
- the database stored by storage unit 712 may include user profile data 114 (see FIG. 1 ) and/or route calculation rules 116 (see FIG. 1 ).
- the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “module” or “system” (e.g., system 100 in FIG. 1 or computer system 700 ). Furthermore, an embodiment of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) (e.g., memory 704 or computer data storage unit 712 ) having computer readable program code (e.g., program code 714 ) embodied or stored thereon.
- computer readable medium(s) e.g., memory 704 or computer data storage unit 712
- computer readable program code e.g., program code 714
- the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
- a computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system, apparatus, device or any suitable combination of the foregoing.
- a non-exhaustive list of more specific examples of the computer-readable storage medium includes: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
- a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with a system, apparatus, or device for carrying out instructions.
- a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electromagnetic, optical, or any suitable combination thereof.
- a computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with a system, apparatus, or device for carrying out instructions.
- Program code (e.g., program code 714 ) embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
- Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java®, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. Instructions of the program code may be carried out entirely on a user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server, where the aforementioned user's computer, remote computer and server may be, for example, computer system 700 or another computer system (not shown) having components analogous to the components of computer system 700 included in FIG. 7 . In the latter scenario, the remote computer may be connected to the user's computer through any type of network (not shown), including a LAN or a WAN, or the connection may be made to an external computer (e.g., through the Internet using an Internet Service Provider).
- an object oriented programming language such as Java®, Smalltalk,
- These computer program instructions may be provided to a processor (e.g., CPU 702 ) of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which are carried out via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- a processor e.g., CPU 702
- These computer program instructions may also be stored in a computer readable medium (e.g., memory 704 or computer data storage unit 712 ) that can direct a computer (e.g., computer system 700 ), other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
- a computer e.g., computer system 700
- other programmable data processing apparatus e.g., computer system 700
- the computer program instructions may also be loaded onto a computer (e.g., computer system 700 ), other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the instructions which are carried out on the computer, other programmable apparatus, or other devices provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- a computer e.g., computer system 700
- other programmable data processing apparatus or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the instructions which are carried out on the computer, other programmable apparatus, or other devices provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- an embodiment of the present invention discloses a process for supporting computer infrastructure, comprising integrating, hosting, maintaining and deploying computer-readable code (e.g., program code 714 ) into a computer system (e.g., computer system 700 ), wherein the code in combination with the computer system is capable of performing a process of determining a travel route that includes a location as a result of an auction.
- computer-readable code e.g., program code 714
- the invention provides a business method that performs the process steps of the invention on a subscription, advertising and/or fee basis. That is, a service provider, such as a Solution Integrator, can offer to create, maintain, support, etc. a process of determining a travel route that includes a location as a result of an auction. In this case, the service provider can create, maintain, support, etc. a computer infrastructure that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement, and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
- a service provider such as a Solution Integrator
- each block in the flowchart or block diagrams may represent a module, segment, or portion of code (e.g., program code 714 ), which comprises one or more executable instructions for implementing the specified logical function(s).
- program code 714 e.g., program code 714
- the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be performed substantially concurrently, or the blocks may sometimes be performed in reverse order, depending upon the functionality involved.
Abstract
Description
- The present invention relates to a data processing method and system for providing a location preference in a routing algorithm, and more particularly to technique for determining travel routes that include locations as a result of auctions.
- With an increased use of Global Positioning System (GPS) units to determine travel routes, travelers are following routes recommended to them, rather than using maps or following familiar paths. Conventional route planning systems determine optimal routes based on different preferred conditions, including minimizing travel time or minimizing the distance traveled. By focusing on optimal route determination, known route planning systems fail to consider non-optimal routes whose presentation to travelers may have value to other parties. Further, the conventional route planning systems fail to account for a dynamic market value associated with presenting a route to a traveler. Thus, there exists a need to overcome at least one of the preceding deficiencies and limitations of the related art.
- In one or more embodiments, the present invention provides a computer-implemented method of determining a route that includes a location as a result of an auction. The method comprises:
- receiving a request from a user for a determination of a route from a first point to a second point;
- selecting a plurality of locations capable of being included along a plurality of routes from the first point to the second point, wherein the selecting the plurality of locations is based on the request;
- initiating an auction among a plurality of vendors that submits a plurality of bids in the auction, wherein the vendors and the bids are associated in a one-to-one correspondence;
- determining that a vendor of the plurality of vendors wins the auction based on a bid of the plurality of bids, wherein the bid is associated with the vendor;
- a processor of a computer system determining the route so that a location of the plurality of locations is included along the route, wherein the location is associated with the vendor that wins the auction based on the bid; and presenting the determined route to the user as the recommended route.
- A system, program product and process for supporting computing infrastructure corresponding to the above-summarized method is also described and claimed herein.
- The present invention provides a technique for presenting travel routes to travelers, where the routes are generated so as to include locations associated with vendors that submit winning bids in auctions.
-
FIG. 1 is a block diagram of a system for determining a travel route that includes a location based on an auction, in accordance with embodiments of the present invention. -
FIG. 2 is a flowchart of a process for determining a travel route in the system ofFIG. 1 , where the travel route includes a location as a result of a real-time auction, in accordance with embodiments of the present invention. -
FIG. 3 is a flowchart of a process for determining a travel route in the system ofFIG. 1 , where the travel route includes a location as a result of an auction initiated prior to a request for the travel route, in accordance with embodiments of the present invention. -
FIG. 4 is a flowchart of a process that determines a route according to the process ofFIG. 2 orFIG. 3 and that determines additional fee(s) for auction winner(s) based on an actual route taken, in accordance with embodiments of the present invention. -
FIG. 5 is a flowchart of a process that determines a travel route according to the process ofFIG. 2 orFIG. 3 and based on a rule that limits distance, in accordance with embodiments of the present invention. -
FIG. 6 is a flowchart of a process that determines a travel route according to the process ofFIG. 2 orFIG. 3 and based on a rule that limits the number of recommended routes that pass through a constrained area, in accordance with embodiments of the present invention. -
FIG. 7 is a block diagram of a computer system included in the system ofFIG. 1 and that implements the process ofFIG. 2 and/or the process ofFIG. 3 , in accordance with embodiments of the present invention. - Embodiments of the present invention provide a preference for a given route to pass by a particular location, based on an auction. Multiple vendors and/or other entities bid in an auction to ensure that a route recommended to a user (i.e., traveler) passes by a particular location associated with the winning bidder (i.e., the vendor or other entity that submits the winning bid). In one embodiment, a route calculation service utilizes an algorithm that takes into account a user's profile information to determine the particular vendors and/or other entities that are permitted to bid in an auction to determine a travel route. In another embodiment, additional route generation rules may be applied to determine whether the route determined by the auction is actually presented to a user as a recommended route.
-
FIG. 1 is a block diagram of a system for determining a travel route that includes a location as a result of an auction won by a bid submitted by a vendor associated with the location, in accordance with embodiments of the present invention. As used herein, an auction has multiple vendors and/or other entities submitting bids for determining a route that includes a location associated with the winning bidder. The vendor or other entity submitting a winning bid (e.g., the highest bid) ensures that a travel route recommended to a user passes by a location associated with the vendor or other entity that submitted the winning bid.System 100 includes acentral computer system 102, computer systems 104-1 . . . 104-N ofauction participants 1 . . . N (i.e., vendors and/or vendors and/or other entities), anetwork 106, and avehicle 108 that includes a software-implemented route calculation service (RCS) 110 and optionally a global positioning system (GPS) 112.System 100 may also include optionaluser profile data 114 and one or more optionalroute calculation rules 116.User profile data 114 androute calculation rules 116 may be stored in one or more computer data storage units coupled tocentral computer system 102 or coupled to a data processing unit (e.g., GPS 112) residing invehicle 108. - Computer systems 104-1 . . . 104-N are managed by
auction participants 1 . . . N, respectively, where N≧1. Theauction participants 1 . . . N are herein also referred to asvendors 1 . . . N. The present invention contemplates that thevendors 1 . . . N may include one or more businesses and/or one or more other types of organizational entities. Via a network (not shown), computer systems 104-1 . . . 104-N send identifications ofvendors 1 . . . N and identifications of multiple locations tocentral computer system 102 to indicate thatvendors 1 . . . N may participate in an auction-based location preference system managed bycentral computer system 102. Each vendor invendors 1 . . . N is associated with one or more locations of the aforementioned multiple locations. For example, ifVendor 1 is associated withLocation 1 andVendor 1 is the owner of a grocery store, thenLocation 1 may be the site of the grocery store. - RCS 110 receives the identifications of the
vendors 1 . . . N and the identifications of the multiple locations fromcentral computer system 102 vianetwork 106. RCS 110 determines a travel route that includes a location associated with a vendor included invendors 1 . . . N, where the vendor submitted a winning bid in an auction. In one embodiment, thecentral computer system 102 receives indications from multiple route calculation services in multiple vehicles (e.g.,route calculation service 110 invehicle 108 and other route calculation services in other vehicles not vehicles not shown inFIG. 1 ) of which vendors have submitted winning bids in auctions and notifies the vendor computer systems of computer systems 104-1 . . . 104-N that are managed by the vendors who submitted winning bids. The determination of the travel route may also be based onuser profile data 114 and/orroute calculation rules 116. Further descriptions of the functionality of components ofsystem 100 are found in the discussions below relative toFIGS. 2-6 . -
FIG. 2 is a flowchart of a process for determining a travel route in the system ofFIG. 1 , where the process includes a location in the travel route as a result of a real-time auction won by a bid submitted by a vendor associated with the location, in accordance with embodiments of the present invention. The process of determining a travel route by using a real-time auction in the system ofFIG. 1 starts atstep 200. Instep 202, RCS 110 (seeFIG. 1 ) receives identifications of vendor(s) and location(s) associated with the vendor(s), where the vendor(s) are potential participants in a real-time auction to determine a travel route. That is, RCS 110 (seeFIG. 1 ) receives an identification of each vendor who may bid in a real-time auction to ensure that a location associated with the vendor is included in a travel route determined by the RCS. The location(s) are associated with the vendor(s) in a one-to-one correspondence. In one embodiment, the location associated with the vendor is a site (e.g., identified by address or geographic coordinates) at which the vendor conducts business. - In
step 204, RCS 110 (seeFIG. 1 ) receives a request issued by a user of GPS 112 (see (seeFIG. 1 ) for a travel route for vehicle 108 (seeFIG. 1 ) to travel from a first geographic location (a.k.a. point A, first point or starting point) to a second geographic location (a.k.a. point B, second point or ending point). The request received instep 204 may include, for example, the addresses or geographic coordinates of point A and point B. - In
step 206, RCS 110 (seeFIG. 1 ) optionally retrieves user profile data from a computer data storage unit, where the user profile data describes the user who issued the request instep 204. The user profile data includes data describing the user's past behavior and may also include predicted future behavior of the user. The user profile data may include one or more preferences that a user has for purchasing one or more particular goods and/or one or more particular services, where the preference(s) may be based on, for example, past purchases made by the user and/or user-specified selections of goods and/or services. - In
step 208, based on the request received instep 204 and based on user profile data if user profile data is retrieved instep 206, RCS 110 (seeFIG. 1 ) selects a plurality of locations of the locations whose identifications are received instep 202. A routing algorithm implemented by RCS 110 (seeFIG. 1 ) can include one or more locations of the plurality of locations selected instep 208 along a route that conforms to the request received instep 204. As used herein, a location included along a route is defined as a location that is located at an address on a segment of the route or is located at a nearest distance to the route where the nearest distance does not exceed a predefined distance or a user-specified distance. A location included along a route is further defined to be not the starting point of the route and not the ending point of the route. - In
step 210, for vendors associated with the locations selected instep 208, RCS 110 (seeFIG. 1 ) initiates an auction. The auction is conducted by central computer system 102 (seeFIG. 1 ) to determine winning bid(s) and the vendor(s) (i.e., winning vendor(s)) that submit the winning bid(s). The winning bid(s) by winning vendor(s) ensure that a route from point A to point B that is to be presented to the user includes location(s) associated with the winning vendor(s). In one embodiment, the central computer system determines a winning bid as being the highest-valued bid in the auction. In another embodiment, the central computer system determines multiple winning bids from multiple vendors, where the multiple vendors do not compete with each other in terms of the goods and/or services they offer according to predefined criteria. - In
step 212, RCS 110 (seeFIG. 1 ) determines a route from point A to point B that conforms to the request received instep 204 and that includes the location(s) associated with the winning vendor(s). The determination of the route instep 212 may also be based on user profile data optionally retrieved instep 206. - In one embodiment, RCS 110 (see
FIG. 1 ) notifies the user if user profile data is a basis for the route determined instep 212. In another embodiment, the user is not notified if user profile data is a basis for the route determined instep 212. - In
step 214, RCS 110 (seeFIG. 1 ) instructs a data processing system (e.g.,GPS 112 inFIG. 1 ) residing in vehicle 108 (seeFIG. 1 ) that the route determined instep 212 is to be presented to the user as a recommended route. In response, the data processing system (e.g.,GPS 112 inFIG. 1 ) presents (e.g., displays) the route determined instep 212 to the user as a recommended route. After the recommended route is presented and in response to the user traveling the recommended route and actually driving past a location associated with a winning vendor, an entity controlling the RCS, the user, and/or another party (e.g., a charitable organization) are organization) are compensated for their participation based on the amount bid by the winning vendor. The process ofFIG. 2 ends atstep 216. - In one embodiment, step 214 also includes the RCS notifying the user that the recommended route passes by the aforementioned location(s) and that the winning vendor(s) are associated with the location(s). The notification to the user may also include an identification of a category of goods and/or services provided by a winning vendor.
- As an example of a portion of the process of
FIG. 2 , RCS 110 (seeFIG. 1 ) receives a user's request for determining a route from point A to point B (see step 204). The RCS retrieves the user's profile data (see step 206), which indicates that the user likes luxury automobiles. Based on the user's request and the retrieved profile data that indicates that user likes luxury automobiles, the RCS selects Location 1 (i.e., the location of Dealer X) and Location 2 (i.e., the location of Dealer Y), where Dealer X and Dealer Y are luxury automobile dealers (see step 208).Location 1 or Location 2 may be included along a route from point A to point B, where the route is to be determined by the RCS. The RCS invites Dealer X and Dealer Y to participate in an auction (e.g., via web services) to ensure that the route to be determined passes byLocation 1 if Dealer X wins the auction or Location 2 if Dealer Y wins the auction (see step 210). In the auction, Dealer X bids $1.10 to ensure that the route passes byLocation 1 and Dealer Y bids $1.05 to ensure that the route passes by Location 2. Since Dealer X's bid amount is greater than Dealer Y's bid amount, Dealer X wins the auction and RCS determines a route from point A to point B that passes byLocation 1. The RCS directs a system in the vehicle of the user to display the determined route from point A to point B as a recommended route (see step 214). The RCS notifies the user that the recommended route passes byLocation 1 and thatLocation 1 is associated with Dealer X. After the user takes the recommended route and actually drivespast Location 1, an entity controlling the RCS and the user are paid for their participation based on the amount bid by Dealer X in the auction. - In a variation of the example presented above with Dealer X and Dealer Y participating in an auction, multiple routes from point A to point B (including the recommended route) are presented to the user and the user is compensated (e.g., with a credit to an account) in response to the user selecting the recommended route instead of the other presented routes.
- In another example, a user requests a route from point A to point B (see step 204) and the user's profile data indicates a preference for luxury automobiles and for visiting coffee shops (see step 206). The auction (see step 210) accepts bids from a first set of luxury automobile dealer vendors and bids from a second set of coffee shop vendors. The result of the auction is that Luxury Automobile Dealer 1 (i.e., the luxury automobile dealer that submitted the highest bid among the first set of vendors) is a first winning vendor and Coffee Shop 1 (i.e., the coffee shop vendor that submitted the highest bid among the second set of vendors) is a second winning vendor. The RCS determines a route from point A to point B (see step 212) that includes
Location 1 and Location 2, whereLocation 1 is the site at whichLuxury Automobile Dealer 1 conducts business and where Location 2 is the site ofCoffee Shop 1. -
FIG. 3 is a flowchart of a process for determining a travel route in the system ofFIG. 1 , where the process includes a location in the travel route as a result of an auction initiated prior to receiving a request for determining the route (a.k.a. an ahead-of-time auction), in accordance with embodiments of the present invention. The process of determining a travel route by using an ahead-of-time auction in the system ofFIG. 1 starts atstep 300. Instep 302, RCS 110 (seeFIG. 1 )FIG. 1 ) receives parameters from vendors and bids from vendors for an auction in which the winning bid(s) submitted by winning vendor(s) ensure that a route to be presented to a user includes location(s) associated with the winning vendor(s). The location(s) are associated with the vendor(s) in a one-to-one correspondence. In one embodiment, the location associated with the vendor is a site (e.g., identified by an address or geographic coordinates) at which the vendor conducts business. - One or more parameters received in
step 302 may specify how a particular vendor's bid in the auction varies based on predefined criteria. For example, parameters may specify how a vendor's bid varies by: the time of day at which the route is requested, the value of a particular customer based on the customer's past behavior (e.g., past purchases) or predicted future behavior in the user profile data, and/or events that occurred (or will occur) within a specified time period in an area through which a requested route passes. - One or more parameters received in
step 302 may specify a pre-cached auction bid. Multiple vendors may submit pre-cached auction bids that allow the auction to be conducted instantaneously (see step 310) in response to receiving the user's request for a route from point A to point B (see step 304) and selecting locations that can be included along routes from point A to point B (see step 308). In one embodiment, the parameter(s) specifying a pre-cached auction bid by a vendor includes the vendor's maximum bid amount for auctions to be conducted. In another embodiment, the parameters include X and N, where the vendor's maximum pre-cached auction bid amount X is submitted for N auctions. In still another embodiment, the parameters include X, N and T, where the vendor's maximum pre-cached auction bid amount X is submitted for N auctions, where there is not less than T time units between successive auctions. For example, a example, a vendor may specify parameters that indicate the vendor is willing to bid up to $1.20 20 times for auctions where successive auctions are not less than 20 minutes apart. - In
step 304, RCS 110 (seeFIG. 1 ) receives a request issued by a user of GPS 112 (seeFIG. 1 ) for a travel route for vehicle 108 (seeFIG. 1 ) to travel from a first geographic location (a.k.a. point A, first point or starting point) to a second geographic location (a.k.a. point B, second point or ending point). The request received instep 304 may include, for example, the addresses or geographic coordinates of point A and point B. - In
step 306, RCS 110 (seeFIG. 1 ) optionally retrieves user profile data from a computer data storage unit, where the user profile data describes the user who issued the request instep 304. The user profile data includes data describing the user's past behavior and may also include predicted future behavior of the user. The user profile data may include one or more preferences that a user has for purchasing one or more particular goods and/or one or more particular services, where the preference(s) may be based on, for example, past purchases made by the user and/or user-specified selections of goods and/or services. - In
step 308, based on the request received instep 304, the parameters received instep 302, and the user profile data if the user profile data is retrieved instep 306, RCS 110 (seeFIG. 1 ) selects a plurality of locations of the locations associated with the vendors whose bids are received instep 302. A routing algorithm implemented by RCS 110 (seeFIG. 1 ) can include one or more locations of the plurality of locations selected instep 308 along a route that conforms to the request received instep 304. - In
step 310, for vendors associated with the locations selected instep 308, RCS 110 (seeFIG. 1 ) completes the auction by determining the winning bid(s) and the winning vendor(s) that submit the winning bid(s) in the auction. The winning bid(s) by winning vendor(s) ensure that a route from point A to point B that is to be presented to the user includes location(s) associated with the winning vendor(s). - In
step 312, RCS 110 (seeFIG. 1 ) determines a route from point A to point B that conforms to the request received instep 304 and that includes the location(s) associated with the winning vendor(s). The determination of the route instep 312 may also be based on user profile data optionally retrieved instep 306. - In one embodiment, RCS 110 (see
FIG. 1 ) notifies the user if user profile data is a basis for the route determined instep 312. In another embodiment, the user is not notified if user profile data is a basis for the route determined instep 312. - In
step 314, RCS 110 (seeFIG. 1 ) instructs a data processing system (e.g.,GPS 112 inFIG. 1 ) residing in vehicle 108 (seeFIG. 1 ) that the route determined instep 312 is to be presented to the user as a recommended route. In response, the data processing system (e.g.,GPS 112 inFIG. 1 ) presents (e.g., displays) the route determined instep 312 to the user as a recommended route. After the recommended route is presented and in response to the user traveling the recommended route and actually driving past a location associated with a winning vendor, an entity controlling the RCS, the user, and/or another party (e.g., a charitable organization) are compensated for their participation based on the amount bid by the winning vendor. The process ofFIG. 3 ends atstep 316. - In one embodiment, step 314 also includes the RCS notifying the user that the recommended route passes by the aforementioned location(s) and that the winning vendor(s) are associated with the location(s). The notification to the user may also include an identification of a a category of goods and/or services provided by a winning vendor.
- In an alternate embodiment, instead of having the RCS 110 (see
FIG. 1 ) push a route, a user may pull a route based on explicit user profile data items being specified for a particular trip event that requires a travel route to be determined and recommended. For example, the user may specify a distance over and above the length of the shortest route that the user is willing to travel. As another example, the user may specify service(s) and/or product(s) (e.g., grocery store) the user would like to travel near during a given trip. The route determined in step 212 (seeFIG. 2 ) or instep 312 may include location(s) selected in step 208 (seeFIG. 2 ) or step 308, respectively, where the location(s) are selected because they provide the service(s) and/or product(s) specified by the user. - Possible methods for funding and providing incentives for the processes in
FIG. 2 andFIG. 3 may include: -
- 1. Based on the winning bid, a fee is charged to the winning vendor whose location is included in the recommended route and the user who is a customer of the vendor is not compensated.
- 2. The user (i.e., the customer of the winning vendor whose location is included in the recommended route) is compensated directly (e.g., with cash, reimbursements for tolls incurred along the route, credits for spending at the vendor's store, etc.).
- 3. Compensation may optionally be given to nonprofit causes, including charities or green initiatives.
-
FIG. 4 is a flowchart of a process for determining a surcharge based on an actual route taken subsequent to a presentation of a recommended route in the process ofFIG. 2 orFIG. 3 , in accordance with embodiments of the present invention. The surcharge determination process ofFIG. 4 starts atstep 400. Instep 402, by performing the steps of the process ofFIG. 2 orFIG. 3 , RCS 110 (seeFIG. 1 ) determines a travel route that includes location(s) associated with winning vendor(s) and the determined travel route is presented to the user as a recommended route. - In
step 404, GPS 112 (seeFIG. 1 ) located in the user's vehicle 108 (seeFIG. 1 ) tracks the actual route taken by the user's vehicle. - In
step 406, RCS 110 (seeFIG. 1 ) determines whether one or more locations that are included in the recommended route and that are associated with one or more winning vendor(s) are included in the actual route traveled by the user in vehicle 108 (seeFIG. 1 ). In one embodiment,step 406 includes RCS 110 (seeFIG. 1 ) determining whether the actual route traveled by vehicle 108 (seeFIG. 1 ) is the recommended route determined instep 402. - If
step 406 determines that location(s) associated with winning vendor(s) are located along the actual route taken by vehicle 108 (seeFIG. 1 ), then instep 408 RCS 110 (seeFIG. 1 ) determines surcharge(s) to be charged to the winning vendor(s) associated with the location(s) that are along the actual route taken by the user's vehicle. For example, ifVendor 1 is a winning vendor that had bid X in the auction initiated in step 210 (seeFIG. 2 ) or step 302 (seeFIG. 3 ) and a surcharge determined instep 408 to be charged toVendor 1 is S, thenVendor 1 pays X+S as a result ofVendor 1 winning the auction and the user's vehicle traveling an actual route that includes the location associated withVendor 1. - Different vendors may be charged the same or different surcharges, where the surcharges are determined in
step 408. - Following
step 408, the process ofFIG. 4 ends atstep 410. Returning to step 406, if RCS 110 (seeFIG. 1 ) determines that no location(s) associated with the winning vendor(s) are along the actual route taken by vehicle 108 (seeFIG. 1 ), then the process ofFIG. 4 ends atstep 410. - A rule-based route determination process determines a route according to the process of
FIG. 2 throughstep 212 or the process ofFIG. 3 throughstep 312, and indicates whether or not the determined route is a recommended route based on the application of a predefined route calculation rule (i.e., based on whether a measurement of the determined route satisfies a predefined rule). One or more route calculation rules 116 (seeFIG. 1 ) are received and stored in a computer data storage unit. The computer data storage unit may be coupled to GPS 112 (seeFIG. 1 ) or computer system 102 (seeFIG. 1 ). The received route calculation rule(s) 116 (seeFIG. 1 ) indicate that one or more measurements of a recommended route from point A to point B presented in the process ofFIG. 2 orFIG. 3 are not permitted to differ from one or more corresponding measurements of an optimal route from point A to point B by more than one or more corresponding predefined threshold values. The difference between the measurement of a recommended route and the corresponding measurement of the optimal route, and the corresponding predefined threshold value may be expressed as a number of units of the measurement, a percentage, or a ratio. - One
rule 116 may indicate that the distance of a recommended route must not exceed a distance of a shortest-distance route from point A to point B by more than X % or by more than a distance of X units (e.g., X miles), where X is a predefined value (see the discussion ofFIG. 5 presented below). Anotherrule 116 may indicate that the time for traveling the recommended route from point A to point B must not exceed a time for traveling the shortest-time route from point A to point B by more than X % or by more than a time of X units (e.g., X minutes), where X is a predefined value. - In the rule-based route determination process, RCS 110 (see
FIG. 1 ) retrieves arule 116 from the aforementioned computer data storage unit, where the rule states that in order for a determined route to be a recommended route, the difference N between a measurement of the determined route and a corresponding measurement of an optimal route must not exceed threshold value X. The optimal route is the route that is optimized according to the corresponding measurement. - If RCS 110 (see
FIG. 1 ) determines the difference N is not greater than threshold value X, then the RCS designates the determined route to be a recommended route, the GPS 112 (seeFIG. 1 ) presents (e.g., displays) the recommended route to the user, and the rule-based route determination process ends. - If RCS 110 (see
FIG. 1 ) determines that the difference N is greater than the threshold value X, then the RCS indicates that the determined route is not a recommended route and is not to be presented to the user and the rule-based route determination process ends. - In one embodiment, the rule-based route determination process utilizes a distance limiting rule, as described below relative to
FIG. 5 . -
FIG. 5 is a flowchart of a process for determining a travel route according to the process ofFIG. 2 orFIG. 3 and based on a rule that limits the distance of the recommended route, in accordance with embodiments of the present invention. The process ofFIG. 5 begins atstep 500. Instep 502, one or more route calculation rules 116 (seeFIG. 1 ) are received and stored in a computer data storage unit. The computer data storage unit may be coupled to GPS 112 (seeFIG. 1 ) or computer system 102 (seeFIG. 1 ). The received route calculation rule(s) 116 (seeFIG. 1 ) include a distance-limiting rule that indicates that the length of a recommended route from point A to point B presented in the process ofFIG. 2 orFIG. 3 is not permitted to exceed the length of an optimal (i.e., shortest) route from point A to point B by more than X %. - In
step 504, steps 202-212 (seeFIG. 2 ) or steps 302-312 (seeFIG. 3 ) are performed by RCS 110 (seeFIG. 1 ) to determine a route from point A to point B. - In
step 506, RCS 110 (seeFIG. 1 ) retrieves the distance-limiting rule from the aforementioned computer data storage unit. Also instep 506, RCS 110 (seeFIG. 1 ) determines that the length of the route determined instep 504 is N % more than the length of the optimal route from point A to point B. - If RCS 110 (see
FIG. 1 ) determines instep 508 that N % is not greater than X %, then the No branch ofstep 508 is taken and step 510 is performed. Instep 510, RCS 110 (seeFIG. 1 ) designates the route determined instep 504 as a recommended route. Instep 512, the GPS 112 (seeFIG. 1 ) presents (e.g., displays) the recommended route to the user. The process ofFIG. 5 ends atstep 514. - Returning to step 508, if RCS 110 (see
FIG. 1 ) determines that N % is greater than X %, then instep 516 the RCS indicates that the route determined instep 504 is not a recommended route and is not to be presented to the user. Followingstep 516, the process ofFIG. 5 ends atstep 514. - In an alternate embodiment, the rule received in
step 502 indicates that the length of the recommended route is not permitted to exceed the length of the optimal route by more than a distance X (e.g., X miles) and step 506 determines that the length of the route determined instep 504 is a distance N longer than the length of the optimal route. Furthermore, in this alternate embodiment,step 508 determines whether N>X. -
FIG. 6 is a flowchart of a process for determining a travel route according to the process ofFIG. 2 orFIG. 3 and based on a rule that limits the number of recommended routes that pass through a constrained area. The process ofFIG. 6 starts atstep 600. Instep 602, one or more route calculation rules 116 (seeFIG. 1 ) are received and stored in a computer data storage unit. The computer data storage unit may be coupled to GPS 112 (seeFIG. 1 ) or computer system 102 (seeFIG. 1 ). The received route calculation rule(s) 116 (seeFIG. 1 ) include a recommended routes quantity-limiting rule that indicates that the number of recommended routes presented by multiple performances of steps 204-214 (seeFIG. 2 ) or steps 304-314 (seeFIG. 3 ), where the recommended routes pass through a constrained area, is not permitted to exceed a predefined predefined number X. - In
step 604, RCS 110 (seeFIG. 1 ) receives an indication of an area (a.k.a. constrained area) that is constrained according to predefined criteria. - In
step 606, the steps 204-214 (seeFIG. 2 ) or steps 304-314 (seeFIG. 3 ) are performed and may be repeated until N routes determined by step 212 (seeFIG. 2 ) or step 312 (seeFIG. 3 ) are recommended and presented in step 214 (seeFIG. 2 ) or step 314 (seeFIG. 3 ), where N≧1, and where each of the N recommended routes pass through the constrained area indicated instep 604. - In
step 608, steps 204-212 (seeFIG. 2 ) or steps 304-312 (seeFIG. 3 ) are performed to determine an (N+1)-th route that passes through the constrained area whose indication is received instep 604. - If RCS 110 (see
FIG. 1 ) determines instep 610 that N+1 is not greater than X, then the No branch ofstep 610 is taken and step 612 is performed. Instep 612, RCS 110 (seeFIG. 1 ) designates the (N+1)-th route determined instep 608 as the (N+1)-th recommended route. Instep 614, the GPS 112 (seeFIG. 1 ) presents (e.g., displays) the (N+1)-th recommended route to the user. The process ofFIG. 6 ends atstep 616. - Returning to step 610, if RCS 110 (see
FIG. 1 ) determines that N+1 is greater than X, then instep 618 the RCS indicates that the (N+1)-th route determined instep 608 is not a recommended route and is not to be presented to the user. In one embodiment,step 618 indicates that the (N+1)-th route is not a recommended route and is not to be presented to the user in order to prevent a traffic jam in the constrained area. Followingstep 618, the process ofFIG. 6 ends atstep 616. - In an alternate embodiment,
step 618 is replaced with (1) the RCS 110 (seeFIG. 1 ) identifying the constrained area as having congested traffic based on the N recommended routes previously presented to users (or based on an indication received by the RCS in a previous step), (2) the RCS determining that the (N+1)-th route passes through the area of congested traffic, and (3) the RCS determining a fee to charge a vendor whose associated location is along the (N+1)-th route. The fee is charged for proposing routes for any additional vehicles to travel through the congested area, thereby promoting environmental stewardship by potentially reducing the number of additional vehicles entering the congested area. -
FIG. 7 is a computer system that is included in the system ofFIG. 1 and that implements the process ofFIG. 2 and/or the process ofFIG. 3 , in accordance with embodiments of the present invention.Computer system 700 generally comprises a central processing unit (CPU) 702, amemory 704, an input/output (I/O)interface 706, and abus 708. Further,computer system 700 is coupled to I/O devices 710 and a computerdata storage unit 712.CPU 702 performs computation and control functions ofcomputer system 700.CPU 702 may comprise a single processing unit, or be distributed across one or more processing units in one or more locations (e.g., on a client and server). In one embodiment,computer system 700 implements RCS 110 (seeFIG. 1 ) and may reside in vehicle 108 (seeFIG. 1 ). In one embodiment,computer system 700 is GPS 112 (seeFIG. 1 ). -
Memory 704 may comprise any known computer readable storage medium, which is described below. In one embodiment, cache memory elements ofmemory 704 provide temporary storage of at least some program code (e.g., program code 714) in order to reduce the number of times code must be retrieved from bulk storage while instructions of the program code are carried out. Moreover, similar toCPU 702,memory 704 may reside at a single physical location, comprising one or more types of data storage, or be distributed across a plurality of physical systems in various forms. Further,memory 704 can include data distributed across, for example, a local area network (LAN) or a wide area network (WAN). - I/
O interface 706 comprises any system for exchanging information to or from an external source. I/O devices 710 comprise any known type of external device, including a display device (e.g., monitor), keyboard, mouse, printer, speakers, handheld device, facsimile, etc. Bus etc.Bus 708 provides a communication link between each of the components incomputer system 700, and may comprise any type of transmission link, including electrical, optical, wireless, etc. - I/
O interface 706 also allowscomputer system 700 to store and retrieve information (e.g., data or program instructions such as program code 714) from an auxiliary storage device such as computerdata storage unit 712 or another computer data storage unit (not shown). Computerdata storage unit 712 may comprise any known computer readable storage medium, which is described below. For example, computerdata storage unit 712 may be a non-volatile data storage device, such as a magnetic disk drive (i.e., hard disk drive) or an optical disc drive (e.g., a CD-ROM drive which receives a CD-ROM disk). -
Memory 704 may includecomputer program code 714 that provides the logic for determining a travel route that includes a location as a result of an auction (e.g., the process ofFIG. 2 orFIG. 3 ). Further,memory 704 may include other systems not shown inFIG. 7 , such as an operating system (e.g., Linux) that runs onCPU 702 and provides control of various components within and/or connected tocomputer system 700. -
Memory 704,storage unit 712, and/or one or more other computer data storage units (not shown) that are coupled tocomputer system 700 may store a database (e.g.,central database 104 inFIG. 1 ). The database stored bystorage unit 712 may include user profile data 114 (seeFIG. 1 ) and/or route calculation rules 116 (seeFIG. 1 ). - As will be appreciated by one skilled in the art, the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “module” or “system” (e.g.,
system 100 inFIG. 1 or computer system 700). Furthermore, an embodiment of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) (e.g.,memory 704 or computer data storage unit 712) having computer readable program code (e.g., program code 714) embodied or stored thereon. - Any combination of one or more computer readable medium(s) (e.g.,
memory 704 and computer data storage unit 712) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system, apparatus, device or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer-readable storage medium includes: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with a system, apparatus, or device for carrying out instructions. - A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electromagnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with a system, apparatus, or device for carrying out instructions.
- Program code (e.g., program code 714) embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
- Computer program code (e.g., program code 714) for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java®, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. Instructions of the program code may be carried out entirely on a user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server, where the aforementioned user's computer, remote computer and server may be, for example,
computer system 700 or another computer system (not shown) having components analogous to the components ofcomputer system 700 included inFIG. 7 . In the latter scenario, the remote computer may be connected to the user's computer through any type of network (not shown), including a LAN or a WAN, or the connection may be made to an external computer (e.g., through the Internet using an Internet Service Provider). - Aspects of the present invention are described herein with reference to flowchart illustrations (e.g.,
FIGS. 2-6 ) and/or block diagrams of methods, apparatus (systems) (e.g.,FIG. 1 andFIG. 7 ), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions (e.g., program code 714). These computer program instructions may be provided to a processor (e.g., CPU 702) of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which are carried out via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. - These computer program instructions may also be stored in a computer readable medium (e.g.,
memory 704 or computer data storage unit 712) that can direct a computer (e.g., computer system 700), other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks. - The computer program instructions may also be loaded onto a computer (e.g., computer system 700), other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the instructions which are carried out on the computer, other programmable apparatus, or other devices provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- Any of the components of an embodiment of the present invention can be deployed, managed, serviced, etc. by a service provider that offers to deploy or integrate computing infrastructure with respect to the process of determining a travel route that includes a location as a result of an auction. Thus, an embodiment of the present invention discloses a process for supporting computer infrastructure, comprising integrating, hosting, maintaining and deploying computer-readable code (e.g., program code 714) into a computer system (e.g., computer system 700), wherein the code in combination with the computer system is capable of performing a process of determining a travel route that includes a location as a result of an auction.
- In another embodiment, the invention provides a business method that performs the process steps of the invention on a subscription, advertising and/or fee basis. That is, a service provider, such as a Solution Integrator, can offer to create, maintain, support, etc. a process of determining a travel route that includes a location as a result of an auction. In this case, the service provider can create, maintain, support, etc. a computer infrastructure that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement, and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
- The flowcharts in
FIGS. 2-6 and the block diagrams inFIG. 1 andFIG. 7 illustrate the the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code (e.g., program code 714), which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be performed substantially concurrently, or the blocks may sometimes be performed in reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. - While embodiments of the present invention have been described herein for purposes of illustration, many modifications and changes will become apparent to those skilled in the art. Accordingly, the appended claims are intended to encompass all such modifications and changes as fall within the true spirit and scope of this invention.
Claims (20)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/578,780 US20110087430A1 (en) | 2009-10-14 | 2009-10-14 | Determining travel routes by using auction-based location preferences |
US14/799,662 US9909885B2 (en) | 2009-10-14 | 2015-07-15 | Determining a travel route |
US15/813,307 US20180073878A1 (en) | 2009-10-14 | 2017-11-15 | Determining a travel route |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/578,780 US20110087430A1 (en) | 2009-10-14 | 2009-10-14 | Determining travel routes by using auction-based location preferences |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/799,662 Division US9909885B2 (en) | 2009-10-14 | 2015-07-15 | Determining a travel route |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110087430A1 true US20110087430A1 (en) | 2011-04-14 |
Family
ID=43855508
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/578,780 Abandoned US20110087430A1 (en) | 2009-10-14 | 2009-10-14 | Determining travel routes by using auction-based location preferences |
US14/799,662 Active 2030-01-23 US9909885B2 (en) | 2009-10-14 | 2015-07-15 | Determining a travel route |
US15/813,307 Abandoned US20180073878A1 (en) | 2009-10-14 | 2017-11-15 | Determining a travel route |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/799,662 Active 2030-01-23 US9909885B2 (en) | 2009-10-14 | 2015-07-15 | Determining a travel route |
US15/813,307 Abandoned US20180073878A1 (en) | 2009-10-14 | 2017-11-15 | Determining a travel route |
Country Status (1)
Country | Link |
---|---|
US (3) | US20110087430A1 (en) |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110166958A1 (en) * | 2010-01-05 | 2011-07-07 | International Business Machines Corporation | Conducting route commerce from a central clearinghouse |
US20130013180A1 (en) * | 2011-07-07 | 2013-01-10 | International Business Machines Corporation | Context-based traffic flow control |
US8478603B2 (en) | 2009-06-24 | 2013-07-02 | International Business Machines Corporation | Method and system for monitoring and reporting to an operator greenhouse gas emission from a vehicle |
US8650093B2 (en) | 2011-07-05 | 2014-02-11 | Sidekick Technology LLC | Used automobile transaction facilitation for a specific used automobile |
US8744925B2 (en) | 2011-07-05 | 2014-06-03 | Sidekick Technology Inc. | Automobile transaction facilitation based on customer selection of a specific automobile |
US8812352B2 (en) | 2009-10-14 | 2014-08-19 | International Business Machines Corporation | Environmental stewardship based on driving behavior |
US9039535B2 (en) | 2011-10-17 | 2015-05-26 | International Business Machines Corporation | Tool employing dynamic competition levels for improved performance |
US9058604B2 (en) | 2010-03-23 | 2015-06-16 | Amazon Technologies, Inc. | Converged web-identity and mobile device based shopping |
US9141984B2 (en) | 2011-07-05 | 2015-09-22 | Sidekick Technology LLC | Automobile transaction facilitation using a manufacturer response |
US20160162989A1 (en) * | 2014-12-06 | 2016-06-09 | David John Cole | Mobile opportunistic trading markets |
US20170330394A1 (en) * | 2012-08-14 | 2017-11-16 | Ebay Inc. | Method and system of bidding in a vehicle |
US9909885B2 (en) | 2009-10-14 | 2018-03-06 | International Business Machines Corporation | Determining a travel route |
US9940663B2 (en) * | 2013-08-15 | 2018-04-10 | Frank Daly Ward | Indoor location mapping and wayfinding system |
US9965768B1 (en) | 2011-05-19 | 2018-05-08 | Amazon Technologies, Inc. | Location-based mobile advertising |
US20190120654A1 (en) * | 2017-10-20 | 2019-04-25 | Paypal, Inc. | Load balancing for map application route selection and output |
US10373205B2 (en) | 2016-07-26 | 2019-08-06 | Wrapify, Inc. | System and method for estimating visual impressions of vehicles configured with external graphic messaging |
CN110853163A (en) * | 2019-10-28 | 2020-02-28 | 北京中交国通智能交通系统技术有限公司 | AI and vehicle road cooperation based vehicle path identification charging system and method |
US10878441B2 (en) | 2018-11-07 | 2020-12-29 | International Business Machines Corporation | Adjusting route parameters using a centralized server |
WO2021043176A1 (en) * | 2019-09-02 | 2021-03-11 | 中兴通讯股份有限公司 | Method for sending rcs service message, device, client, and server |
US11507857B2 (en) | 2019-10-01 | 2022-11-22 | TeleLingo | Systems and methods for using artificial intelligence to present geographically relevant user-specific recommendations based on user attentiveness |
USRE49334E1 (en) | 2005-10-04 | 2022-12-13 | Hoffberg Family Trust 2 | Multifactorial optimization system and method |
US11702081B2 (en) * | 2019-02-14 | 2023-07-18 | Honda Motor Co., Ltd. | System and method for road condition monitoring |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140278838A1 (en) * | 2013-03-14 | 2014-09-18 | Uber Technologies, Inc. | Determining an amount for a toll based on location data points provided by a computing device |
CN109064571A (en) * | 2018-08-02 | 2018-12-21 | 石家庄铁道大学 | A kind of net based on communication equipment about vehicle pricing system |
CN110896520B (en) * | 2018-09-12 | 2021-02-26 | 北京聚利科技有限公司 | Path identification method and system, road side identification equipment and vehicle-mounted equipment |
CN109636275A (en) * | 2018-11-27 | 2019-04-16 | 深圳市关运通科技有限公司 | A kind of intelligent transport charging method and device |
Citations (96)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4336522A (en) * | 1979-10-15 | 1982-06-22 | Graham Kenneth G | Vehicle seat-occupancy recorder |
US5086389A (en) * | 1990-05-17 | 1992-02-04 | Hassett John J | Automatic toll processing apparatus |
US5489777A (en) * | 1990-12-26 | 1996-02-06 | Denver Seminary | Apparatus for remote analysis of vehicle emissions using reflective thermography |
US5532690A (en) * | 1995-04-04 | 1996-07-02 | Itt Corporation | Apparatus and method for monitoring and bounding the path of a ground vehicle |
US5583765A (en) * | 1994-08-23 | 1996-12-10 | Grumman Aerospace Corporation | Remote system for monitoring the weight and emission compliance of trucks and other vehicles |
US5694322A (en) * | 1995-05-09 | 1997-12-02 | Highwaymaster Communications, Inc. | Method and apparatus for determining tax of a vehicle |
US5717389A (en) * | 1994-01-28 | 1998-02-10 | Detemobil Deutsche Telekom Mobilnet Gmbh | Method of determining toll charges for vehicles using a traffic route |
US5825007A (en) * | 1996-05-06 | 1998-10-20 | Jesadanont; Mongkol | Automatic non-computer network no-stop collection of expressway tolls by prepaid cards and method: pay according to category of vehicle and the distance it travels |
US5864831A (en) * | 1993-02-17 | 1999-01-26 | Daimler Benz Ag | Device for determining road tolls |
US5892463A (en) * | 1996-09-05 | 1999-04-06 | Mitsubishi Denki Kabushiki Kaisha | Mobile navigation system |
US5920057A (en) * | 1993-06-22 | 1999-07-06 | Vos Verkehrs-Optimierungs-System Gmbh & Co. Kg | Process and device for measuring the occupancy in passenger transportation means |
US6018699A (en) * | 1996-06-04 | 2000-01-25 | Baron Services, Inc. | Systems and methods for distributing real-time site specific weather information |
US6078895A (en) * | 1997-08-20 | 2000-06-20 | Samsung Electronics Co., Ltd. | Technique for showing running time by sections on tollway |
US6104299A (en) * | 1997-01-09 | 2000-08-15 | Schlumberger Systemes | Device for monitoring pollution caused by motor vehicles in an urban area |
US6234390B1 (en) * | 1996-07-26 | 2001-05-22 | Sachsenring Automobiltechnick Ag | Process for acquiring and/or paying a fee for exhaust pollutants and a motor vehicle with an exhaust pollutant set which operates using this process |
US20010037174A1 (en) * | 2000-04-04 | 2001-11-01 | Dickerson Stephen L. | Communications and computing based urban transit system |
US20010056396A1 (en) * | 2000-06-27 | 2001-12-27 | Tadashi Goino | Auction methods, auction systems and servers |
US6356838B1 (en) * | 2000-07-25 | 2002-03-12 | Sunil Paul | System and method for determining an efficient transportation route |
US20020049630A1 (en) * | 1999-04-28 | 2002-04-25 | Yasuyuki Furuta | Charging system |
US20020065604A1 (en) * | 2000-11-30 | 2002-05-30 | Toyota Jidosha Kabushiki Kaisha | Route guide apparatus and guidance method |
US6405132B1 (en) * | 1997-10-22 | 2002-06-11 | Intelligent Technologies International, Inc. | Accident avoidance system |
US20020072963A1 (en) * | 1999-03-09 | 2002-06-13 | Jonge Wiebren De | Traffic information & pricing (TIP) system |
US6411889B1 (en) * | 2000-09-08 | 2002-06-25 | Mitsubishi Denki Kabushiki Kaisha | Integrated traffic monitoring assistance, and communications system |
US20020084917A1 (en) * | 2000-12-28 | 2002-07-04 | Hauptman Benjamin J. | Method and apparatus for reducing traffic congestion |
US20020103769A1 (en) * | 2001-01-29 | 2002-08-01 | International Business Machines Corporation | System and method for automatically adjusting merchandise pricing at a service-oriented interface terminal based upon the quantity of users present at the terminal |
US20020115410A1 (en) * | 1999-11-25 | 2002-08-22 | Fujitsu Limited | Portable terminal |
US6525673B1 (en) * | 1999-08-30 | 2003-02-25 | Bernard Feldman | Expressway control system |
US20030037538A1 (en) * | 2001-08-16 | 2003-02-27 | Rendahl Craig S. | Catalytic converter function detection |
US20030040944A1 (en) * | 2001-08-22 | 2003-02-27 | Hileman Ryan M. | On-demand transportation system |
US20030065630A1 (en) * | 2001-10-02 | 2003-04-03 | International Business Machines Corporation | Adjusting an amount owed for fueling based on vehicle characteristics |
US20030110075A1 (en) * | 2001-12-12 | 2003-06-12 | Pioneer Corporation | Toll collection system, its mobile terminal and toll processing apparatus, terminal processing program for the mobile terminal, and record medium recording the terminal processing program |
US20030115095A1 (en) * | 2001-12-18 | 2003-06-19 | Fujitsu Limited | Toll road toll paying method and apparatus using a portable terminal, and a storage medium thereof |
US6604045B2 (en) * | 2001-11-01 | 2003-08-05 | Nissan Motor Co., Ltd. | Navigation system, data server, traveling route establishing method and information providing method |
US6603405B2 (en) * | 2000-12-05 | 2003-08-05 | User-Centric Enterprises, Inc. | Vehicle-centric weather prediction system and method |
US20030191568A1 (en) * | 2002-04-09 | 2003-10-09 | Breed David S. | Method and system for controlling a vehicle |
US6661352B2 (en) * | 1999-08-11 | 2003-12-09 | Mark Iv Industries Limited | Method and means for RF toll collection |
US20030233321A1 (en) * | 2001-11-30 | 2003-12-18 | Scolini Anthony J. | Integrated invoice solution |
US6693555B1 (en) * | 2001-12-11 | 2004-02-17 | Koninklijke Philips Electronics N.V. | Automatic setting of variable speed limit |
US6696981B1 (en) * | 1999-04-05 | 2004-02-24 | Honda Giken Koyo Kabushiki Kaisha | Apparatus for managing entry and exit of a shared vehicle |
US20040039517A1 (en) * | 2000-09-06 | 2004-02-26 | Alfred Biesinger | Integrated traffic monitoring system |
US6700504B1 (en) * | 2000-11-01 | 2004-03-02 | Navigation Technologies Corp. | Method and system for safe emergency vehicle operation using route calculation |
US20040049424A1 (en) * | 2002-06-21 | 2004-03-11 | Murray Thomas A. | System and method for facilitating ridesharing |
US20040075582A1 (en) * | 2002-10-21 | 2004-04-22 | Terry Bergan | Variable speed limit system |
US20040093264A1 (en) * | 2002-11-07 | 2004-05-13 | Tessei Shimizu | Eco-driving diagnostic system and method, and business system using the same |
US6738697B2 (en) * | 1995-06-07 | 2004-05-18 | Automotive Technologies International Inc. | Telematics system for vehicle diagnostics |
US20040119609A1 (en) * | 2001-03-07 | 2004-06-24 | Lawrence Solomon | Traffic control system with road tariff depending on the congestion level |
US20040167861A1 (en) * | 2003-02-21 | 2004-08-26 | Hedley Jay E. | Electronic toll management |
US20040212518A1 (en) * | 2003-02-26 | 2004-10-28 | Koji Tajima | System for notifying tool charge information |
US20050003802A1 (en) * | 2003-07-02 | 2005-01-06 | Joseph Joseph | System for managing traffic patterns using cellular telephones |
US20050001739A1 (en) * | 1999-08-24 | 2005-01-06 | Terumasa Sudou | Road traffic weather-monitoring system and self-luminous road sign system |
US6843101B2 (en) * | 2000-10-09 | 2005-01-18 | Hoek Bertil | CO2 sensor |
US20050024189A1 (en) * | 2000-09-26 | 2005-02-03 | Weber James R. | Action recommendation system for a mobile vehicle |
US20050049781A1 (en) * | 2003-08-28 | 2005-03-03 | General Motors Corporation | Method and system for providing a carpool service using a telematics system |
US20050168351A1 (en) * | 2004-01-26 | 2005-08-04 | Denso Corporation | Device and system for toll payment |
US20050179563A1 (en) * | 2005-03-14 | 2005-08-18 | Kelley Kalon L. | Motor vehicle occupancy signaling system |
US20050187820A1 (en) * | 2004-02-23 | 2005-08-25 | Krishna Mohan | Participating in an incentive program using a portable memory device |
US6959282B2 (en) * | 1998-10-09 | 2005-10-25 | Toyota Jidosha Kabushiki Kaisha | Charging device for transferring information relating to the collection of a toll on a moving body |
US20050246190A1 (en) * | 2002-07-20 | 2005-11-03 | Richard Sandor | Systems and methods for trading emission reductions |
US20050256762A1 (en) * | 2000-03-27 | 2005-11-17 | Yair Dar | Vehicle related services system and methodology |
US20050278214A1 (en) * | 2002-10-25 | 2005-12-15 | Yoshiaki Takida | Toll road charge collection system using artificial satellite, charge collecting machine, and charge collecting method |
US20060015394A1 (en) * | 2004-07-15 | 2006-01-19 | Sorensen Roger G | Licensed driver detection for high occupancy toll lane qualification |
US7003398B2 (en) * | 2004-02-24 | 2006-02-21 | Avaya Technology Corp. | Determining departure times for timetable-based trips |
US20060099964A1 (en) * | 2004-11-05 | 2006-05-11 | Ebay Inc. | System and method for location based content correlation |
US7053792B2 (en) * | 2000-09-29 | 2006-05-30 | Aisin Seiki Kabushiki Kaisha | Monitoring system for automatic charging apparatus for vehicle |
US20060136291A1 (en) * | 2001-02-15 | 2006-06-22 | Hitachi, Ltd. | Vehicle managing method |
US20060155486A1 (en) * | 2004-10-07 | 2006-07-13 | Walsh Alicia M | Computer-implemented system and method for analyzing mixtures of gases |
US20060173579A1 (en) * | 2001-02-07 | 2006-08-03 | Desrochers Eric M | Air quality monitoring systems and methods |
US7127413B1 (en) * | 1998-01-23 | 2006-10-24 | Toyota Jidosha Kabushiki Kaisha | Charge processing device charge processing system and charge processing card |
US20060255967A1 (en) * | 2005-04-22 | 2006-11-16 | Woo Henry S Y | Open road vehicle emissions inspection |
US20060278705A1 (en) * | 2003-02-21 | 2006-12-14 | Accenture Global Services Gmbh | Electronic Toll Management and Vehicle Identification |
US20070050279A1 (en) * | 2005-08-26 | 2007-03-01 | Palo Alto Research Center Incorporated | Reverse bidding for trip services |
US20070061057A1 (en) * | 2005-08-26 | 2007-03-15 | Palo Alto Research Center Incorporated | Vehicle network advertising system |
US20070063858A1 (en) * | 2005-09-20 | 2007-03-22 | Tzong-Sheng Lee | Multi-function wireless detecting device |
US20070083322A1 (en) * | 2005-10-11 | 2007-04-12 | Van Ee Jonathan H | Freeway optimization program |
US20070100687A1 (en) * | 2003-11-26 | 2007-05-03 | Matsushita Electric Industrial Co., Ltd. | Vehicle management system |
US20080004926A1 (en) * | 2006-06-30 | 2008-01-03 | Microsoft Corporation | Methods and architectures for context-sensitive reminders and service facilitation |
US20080086310A1 (en) * | 2006-10-09 | 2008-04-10 | Kent Campbell | Automated Contextually Specific Audio File Generator |
US20080091341A1 (en) * | 2006-06-27 | 2008-04-17 | Microsoft Corporation | Route monetization |
US20090157307A1 (en) * | 2007-12-14 | 2009-06-18 | Microsoft Corporation | Additional content based on intended travel destination |
US20090157540A1 (en) * | 2007-12-14 | 2009-06-18 | Microsoft Corporation | Destination auctioned through business of interest |
US20090240584A1 (en) * | 2008-03-18 | 2009-09-24 | Ajaindra Prakash Singh | Method and system for conducting online cash deposit auctions for transacting assets and other goods and services |
US20090327148A1 (en) * | 2008-06-27 | 2009-12-31 | Microsoft Corporation | Mechanisms and architecture for mobile opportunistic commerce |
US20100057532A1 (en) * | 2008-09-03 | 2010-03-04 | Sanguinetti Thomas V | System and method for delivering relevant business information to customer and for tracking customer responses |
US20100205060A1 (en) * | 2009-02-09 | 2010-08-12 | Yahoo! Inc. | Context-sensitive route generation system |
US20100217525A1 (en) * | 2009-02-25 | 2010-08-26 | King Simon P | System and Method for Delivering Sponsored Landmark and Location Labels |
US7797267B2 (en) * | 2006-06-30 | 2010-09-14 | Microsoft Corporation | Methods and architecture for learning and reasoning in support of context-sensitive reminding, informing, and service facilitation |
US20100332315A1 (en) * | 2009-06-26 | 2010-12-30 | Microsoft Corporation | Generation of impression plans for presenting and sequencing advertisement and sales opportunities along potential routes |
US20110112908A1 (en) * | 2004-12-31 | 2011-05-12 | Google Inc., a California corporation | Transportation Routing |
US8073460B1 (en) * | 2007-03-08 | 2011-12-06 | Amazon Technologies, Inc. | System and method for providing advertisement based on mobile device travel patterns |
US20120078743A1 (en) * | 2010-09-23 | 2012-03-29 | Epona Llc | System and Method for Coordinating Transport of Cargo |
US8219115B1 (en) * | 2008-05-12 | 2012-07-10 | Google Inc. | Location based reminders |
US8332270B2 (en) * | 2009-02-19 | 2012-12-11 | Qualcomm Incorporated | System and method for utilizing a wireless communications device |
US20130080307A1 (en) * | 2005-10-04 | 2013-03-28 | Steven M. Hoffberg | Multifactorial optimization system and method |
US8428859B2 (en) * | 2007-12-14 | 2013-04-23 | Microsoft Corporation | Federated route production |
US8447661B2 (en) * | 2005-11-04 | 2013-05-21 | Microsoft Corporation | Query analysis for geographic-based listing service |
US8666376B2 (en) * | 2005-09-14 | 2014-03-04 | Millennial Media | Location based mobile shopping affinity program |
Family Cites Families (77)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080161989A1 (en) | 1995-06-07 | 2008-07-03 | Automotive Technologies International, Inc. | Vehicle Diagnostic or Prognostic Message Transmission Systems and Methods |
DE19634340A1 (en) | 1996-08-24 | 1998-02-26 | Bosch Gmbh Robert | Method and recipient of information for road use fees and recipients |
US8060308B2 (en) | 1997-10-22 | 2011-11-15 | Intelligent Technologies International, Inc. | Weather monitoring techniques |
JP2000172892A (en) | 1998-12-08 | 2000-06-23 | Omron Corp | Vehicle charge calculating system |
JP2001101561A (en) | 1999-09-29 | 2001-04-13 | Koito Ind Ltd | Pollutant quantity estimating device, pollutant quantity predicting device, and road traffic controller using them |
CA2388260C (en) | 1999-10-19 | 2009-01-27 | American Calcar Inc. | Technique for effective navigation based on user preferences |
JP2001283377A (en) | 2000-03-29 | 2001-10-12 | Omron Corp | Information processor and its method |
JP2002032893A (en) | 2000-07-18 | 2002-01-31 | Mitsubishi Heavy Ind Ltd | Road traffic amount control method, and system therefor |
US7600683B2 (en) | 2000-08-10 | 2009-10-13 | Paul A. Firestone | System and method for identifying vehicles and collecting fees for vehicle uses of land-ways, sea-ways and air-ways |
WO2002037433A2 (en) | 2000-11-01 | 2002-05-10 | International Carbon Bank And Exchange | Method and system for banking and exchanging emission reduction credits |
US7080030B2 (en) | 2001-02-28 | 2006-07-18 | Digonex Technologies, Inc. | Digital online exchange |
NL1017529C2 (en) | 2001-03-07 | 2002-09-10 | Xello Beheer B V | Device and method for route registration of a vehicle with a mobile telephone. |
US7308358B2 (en) | 2002-03-07 | 2007-12-11 | Increment P Corporation | Navigator, navigation system, navigation method, data processing apparatus, data processing method, program thereof, and recording medium thereof |
US7337196B2 (en) | 2002-08-22 | 2008-02-26 | International Business Machines Corporation | Record relationship processing |
US7899615B2 (en) | 2002-10-21 | 2011-03-01 | Johnson Controls Technology Company | Point of interest display system |
US7215255B2 (en) | 2003-01-21 | 2007-05-08 | Bernard Grush | Method and apparatus for a satellite positioning-based metering system for use in transport-related applications |
US7415418B2 (en) | 2003-02-10 | 2008-08-19 | South Dakota School Of Mines And Technology | Method and apparatus for generating standardized environmental benefit credits |
US20040236475A1 (en) | 2003-02-27 | 2004-11-25 | Mahesh Chowdhary | Vehicle safety management system that detects frequent lane change violations |
EP1519288A1 (en) | 2003-09-25 | 2005-03-30 | Nagravision S.A. | Car-pooling system and process and communication device for carrying out the process |
JP2005274213A (en) * | 2004-03-23 | 2005-10-06 | Denso Corp | Route setting device, map display device and navigation system |
US7057501B1 (en) | 2004-04-23 | 2006-06-06 | Darryl Davis | Tailgate warning and reporting system |
US7407097B2 (en) | 2004-05-10 | 2008-08-05 | Rent A Toll, Ltd. | Toll fee system and method |
US7375648B1 (en) | 2004-10-28 | 2008-05-20 | Efkon Usa, Inc. | Vehicle occupancy identification system |
US9189895B2 (en) | 2005-06-01 | 2015-11-17 | Allstate Insurance Company | Motor vehicle operating data collection and analysis |
US7327238B2 (en) | 2005-06-06 | 2008-02-05 | International Business Machines Corporation | Method, system, and computer program product for determining and reporting tailgating incidents |
US7640192B1 (en) | 2005-06-16 | 2009-12-29 | Amdocs Software Systems Limited | Method and computer program product for dynamic pricing |
US7385525B2 (en) | 2005-07-07 | 2008-06-10 | Mark Iv Industries Corporation | Dynamic timing adjustment in an electronic toll collection system |
GB0520576D0 (en) | 2005-10-10 | 2005-11-16 | Applied Generics Ltd | Using traffic monitoring information to provide better driver route planning |
US20070135990A1 (en) | 2005-12-08 | 2007-06-14 | Seymour Shafer B | Navigation route information for traffic management |
US8235627B2 (en) | 2005-12-08 | 2012-08-07 | Ellis Mark T | System and method for detecting and remediating contamination |
US7791108B2 (en) | 2006-01-25 | 2010-09-07 | Nxp B.V. | Nanowire tunneling transistor |
US9052214B2 (en) | 2006-05-22 | 2015-06-09 | Volkswagen Ag | Navigation system for a motor vehicle, method for operating a navigation system and motor vehicle including a navigation system |
US7689355B2 (en) | 2006-05-04 | 2010-03-30 | International Business Machines Corporation | Method and process for enabling advertising via landmark based directions |
US20070271034A1 (en) | 2006-05-17 | 2007-11-22 | Perry Patrick E | Adaptive route planning for gps-based navigation |
US7388501B2 (en) | 2006-05-19 | 2008-06-17 | Mark Iv Industries Corp | Method of enabling two-state operation of electronic toll collection system |
US7320430B2 (en) | 2006-05-31 | 2008-01-22 | International Business Machines Corporation | Variable rate toll system |
US8666801B2 (en) | 2006-06-06 | 2014-03-04 | ErgonoTech, Inc. | Long-range location-specific menu-driven mobile payment platform mounted on vehicle dashtop |
US20070299607A1 (en) | 2006-06-27 | 2007-12-27 | Verizon Laboratories Inc. | Driving directions with landmark data |
US20080021723A1 (en) | 2006-07-24 | 2008-01-24 | Devarakonda Murali K | Shared multi-tenant commuting management |
US20080033644A1 (en) | 2006-08-03 | 2008-02-07 | Bannon Sean A | Navigation Routing System Having Environmentally Triggered Routing |
US7554435B2 (en) | 2006-09-07 | 2009-06-30 | Nissan Technical Center North America, Inc. | Vehicle on-board unit |
US20080148816A1 (en) | 2006-12-22 | 2008-06-26 | Groves Bruce D | Air monitoring system and method |
US7786897B2 (en) | 2007-01-23 | 2010-08-31 | Jai Pulnix, Inc. | High occupancy vehicle (HOV) lane enforcement |
WO2008100489A2 (en) | 2007-02-12 | 2008-08-21 | Sean O'sullivan | Shared transport system and service network |
US7668643B2 (en) | 2007-03-30 | 2010-02-23 | O2Micro International Ltd. | Method and system for automatically inspecting and registering automotive exhaust emission data |
US20090018902A1 (en) | 2007-07-09 | 2009-01-15 | Jannine Miller | Commuter credits system and method |
GB0713336D0 (en) | 2007-07-10 | 2007-08-22 | Hw Comm Ltd | Occupancy declaration/verification for passenger transport conveyances |
US8577703B2 (en) | 2007-07-17 | 2013-11-05 | Inthinc Technology Solutions, Inc. | System and method for categorizing driving behavior using driver mentoring and/or monitoring equipment to determine an underwriting risk |
US7580808B2 (en) | 2007-09-11 | 2009-08-25 | Gm Global Technology Operations, Inc. | Onboard trip computer for emissions subject to reduction credits |
DE102007058163A1 (en) | 2007-09-28 | 2009-04-23 | Continental Automotive Gmbh | Tachograph, toll-on-board unit, indicating instrument and system |
US20090106095A1 (en) | 2007-10-22 | 2009-04-23 | Hand Held Products, Inc. | Navigator With Dataform Decoder |
EP2218061B1 (en) | 2007-11-24 | 2014-11-05 | Routerank Ltd | Personalized real-time location-based travel management |
US20090210242A1 (en) * | 2008-02-19 | 2009-08-20 | Microsoft Corporation | Load balance payment |
US20090210261A1 (en) | 2008-02-20 | 2009-08-20 | Rearden Commerce, Inc. | System and Method for Multi-Modal Travel Shopping |
CA2717164A1 (en) | 2008-03-01 | 2009-09-11 | International Road Technologies, Inc. | Systems and methods for obtaining emissions offset credits |
US20090222338A1 (en) | 2008-03-03 | 2009-09-03 | Hamilton Ii Rick A | Monitoring and Rewards Methodologies for "Green" Use of Vehicles |
US8121780B2 (en) | 2008-05-18 | 2012-02-21 | Volkswagen Of America, Inc. | Method for offering a user reward based on a chosen navigation route |
WO2009149099A1 (en) | 2008-06-02 | 2009-12-10 | Electronic Transaction Consultants Corporation | Dynamic pricing for toll lanes |
US8108141B2 (en) * | 2008-08-28 | 2012-01-31 | Empire Technology Development Llc | Intelligent travel routing system and method |
US20100070128A1 (en) | 2008-09-15 | 2010-03-18 | Microsoft Corporation | vehicle operation by leveraging traffic related data |
US9037513B2 (en) | 2008-09-30 | 2015-05-19 | Apple Inc. | System and method for providing electronic event tickets |
US8013760B2 (en) | 2008-10-06 | 2011-09-06 | Mark Iv Ivhs, Inc. | High occupancy vehicle status signaling using electronic toll collection infrastructure |
US8065181B2 (en) | 2008-10-16 | 2011-11-22 | Kapsch Trafficcom Ag | System and method for electronic toll collection based on vehicle load |
US7979292B2 (en) | 2008-12-17 | 2011-07-12 | International Business Machines Corporation | Travel fee rate setting based upon travel mode and convenience |
US20100153191A1 (en) | 2008-12-17 | 2010-06-17 | International Business Machines Corporation | Variable toll fee selection from geographic indicia |
US20100153193A1 (en) | 2008-12-17 | 2010-06-17 | International Business Corporation | Variable-rate transport fees based on hazardous travel conditions |
US8200529B2 (en) | 2008-12-17 | 2012-06-12 | International Business Machines Corporation | Random and deterministic travel fees |
US7969325B2 (en) | 2008-12-22 | 2011-06-28 | International Business Machines Corporation | Preemptive variable rate travel fees |
US8055534B2 (en) | 2008-12-22 | 2011-11-08 | International Business Machines Corporation | Variable rate travel fee based upon vehicle occupancy |
US20100161391A1 (en) | 2008-12-22 | 2010-06-24 | International Business Corporation | Variable rate transport fees based on vehicle exhaust emissions |
US8560227B2 (en) | 2009-04-17 | 2013-10-15 | Alpine Electronics, Inc. | Route planning apparatus and method for navigation system |
US8478603B2 (en) | 2009-06-24 | 2013-07-02 | International Business Machines Corporation | Method and system for monitoring and reporting to an operator greenhouse gas emission from a vehicle |
US8374911B2 (en) | 2009-10-01 | 2013-02-12 | International Business Machines Corporation | Vehicle usage-based tolling privacy protection architecture |
US8812352B2 (en) | 2009-10-14 | 2014-08-19 | International Business Machines Corporation | Environmental stewardship based on driving behavior |
US20110087430A1 (en) | 2009-10-14 | 2011-04-14 | International Business Machines Corporation | Determining travel routes by using auction-based location preferences |
US20110087524A1 (en) | 2009-10-14 | 2011-04-14 | International Business Machines Corporation | Determining travel routes by using fee-based location preferences |
US20110166958A1 (en) | 2010-01-05 | 2011-07-07 | International Business Machines Corporation | Conducting route commerce from a central clearinghouse |
-
2009
- 2009-10-14 US US12/578,780 patent/US20110087430A1/en not_active Abandoned
-
2015
- 2015-07-15 US US14/799,662 patent/US9909885B2/en active Active
-
2017
- 2017-11-15 US US15/813,307 patent/US20180073878A1/en not_active Abandoned
Patent Citations (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4336522A (en) * | 1979-10-15 | 1982-06-22 | Graham Kenneth G | Vehicle seat-occupancy recorder |
US5086389A (en) * | 1990-05-17 | 1992-02-04 | Hassett John J | Automatic toll processing apparatus |
US5489777A (en) * | 1990-12-26 | 1996-02-06 | Denver Seminary | Apparatus for remote analysis of vehicle emissions using reflective thermography |
US5864831A (en) * | 1993-02-17 | 1999-01-26 | Daimler Benz Ag | Device for determining road tolls |
US5920057A (en) * | 1993-06-22 | 1999-07-06 | Vos Verkehrs-Optimierungs-System Gmbh & Co. Kg | Process and device for measuring the occupancy in passenger transportation means |
US5717389A (en) * | 1994-01-28 | 1998-02-10 | Detemobil Deutsche Telekom Mobilnet Gmbh | Method of determining toll charges for vehicles using a traffic route |
US5583765A (en) * | 1994-08-23 | 1996-12-10 | Grumman Aerospace Corporation | Remote system for monitoring the weight and emission compliance of trucks and other vehicles |
US5532690A (en) * | 1995-04-04 | 1996-07-02 | Itt Corporation | Apparatus and method for monitoring and bounding the path of a ground vehicle |
US5694322A (en) * | 1995-05-09 | 1997-12-02 | Highwaymaster Communications, Inc. | Method and apparatus for determining tax of a vehicle |
US6738697B2 (en) * | 1995-06-07 | 2004-05-18 | Automotive Technologies International Inc. | Telematics system for vehicle diagnostics |
US5825007A (en) * | 1996-05-06 | 1998-10-20 | Jesadanont; Mongkol | Automatic non-computer network no-stop collection of expressway tolls by prepaid cards and method: pay according to category of vehicle and the distance it travels |
US6018699A (en) * | 1996-06-04 | 2000-01-25 | Baron Services, Inc. | Systems and methods for distributing real-time site specific weather information |
US6234390B1 (en) * | 1996-07-26 | 2001-05-22 | Sachsenring Automobiltechnick Ag | Process for acquiring and/or paying a fee for exhaust pollutants and a motor vehicle with an exhaust pollutant set which operates using this process |
US5892463A (en) * | 1996-09-05 | 1999-04-06 | Mitsubishi Denki Kabushiki Kaisha | Mobile navigation system |
US6104299A (en) * | 1997-01-09 | 2000-08-15 | Schlumberger Systemes | Device for monitoring pollution caused by motor vehicles in an urban area |
US6078895A (en) * | 1997-08-20 | 2000-06-20 | Samsung Electronics Co., Ltd. | Technique for showing running time by sections on tollway |
US6405132B1 (en) * | 1997-10-22 | 2002-06-11 | Intelligent Technologies International, Inc. | Accident avoidance system |
US7127413B1 (en) * | 1998-01-23 | 2006-10-24 | Toyota Jidosha Kabushiki Kaisha | Charge processing device charge processing system and charge processing card |
US6959282B2 (en) * | 1998-10-09 | 2005-10-25 | Toyota Jidosha Kabushiki Kaisha | Charging device for transferring information relating to the collection of a toll on a moving body |
US20020072963A1 (en) * | 1999-03-09 | 2002-06-13 | Jonge Wiebren De | Traffic information & pricing (TIP) system |
US6696981B1 (en) * | 1999-04-05 | 2004-02-24 | Honda Giken Koyo Kabushiki Kaisha | Apparatus for managing entry and exit of a shared vehicle |
US6845362B2 (en) * | 1999-04-28 | 2005-01-18 | Toyota Jidosha Kabushiki Kaisha | Charging system which carries out data processing for fee payment |
US20020049630A1 (en) * | 1999-04-28 | 2002-04-25 | Yasuyuki Furuta | Charging system |
US6661352B2 (en) * | 1999-08-11 | 2003-12-09 | Mark Iv Industries Limited | Method and means for RF toll collection |
US20050001739A1 (en) * | 1999-08-24 | 2005-01-06 | Terumasa Sudou | Road traffic weather-monitoring system and self-luminous road sign system |
US6525673B1 (en) * | 1999-08-30 | 2003-02-25 | Bernard Feldman | Expressway control system |
US20020115410A1 (en) * | 1999-11-25 | 2002-08-22 | Fujitsu Limited | Portable terminal |
US20050256762A1 (en) * | 2000-03-27 | 2005-11-17 | Yair Dar | Vehicle related services system and methodology |
US20010037174A1 (en) * | 2000-04-04 | 2001-11-01 | Dickerson Stephen L. | Communications and computing based urban transit system |
US20010056396A1 (en) * | 2000-06-27 | 2001-12-27 | Tadashi Goino | Auction methods, auction systems and servers |
US7478055B2 (en) * | 2000-06-27 | 2009-01-13 | Tadashi Goino | Auction methods, auction systems and servers |
US6356838B1 (en) * | 2000-07-25 | 2002-03-12 | Sunil Paul | System and method for determining an efficient transportation route |
US20040039517A1 (en) * | 2000-09-06 | 2004-02-26 | Alfred Biesinger | Integrated traffic monitoring system |
US6411889B1 (en) * | 2000-09-08 | 2002-06-25 | Mitsubishi Denki Kabushiki Kaisha | Integrated traffic monitoring assistance, and communications system |
US20050024189A1 (en) * | 2000-09-26 | 2005-02-03 | Weber James R. | Action recommendation system for a mobile vehicle |
US7053792B2 (en) * | 2000-09-29 | 2006-05-30 | Aisin Seiki Kabushiki Kaisha | Monitoring system for automatic charging apparatus for vehicle |
US6843101B2 (en) * | 2000-10-09 | 2005-01-18 | Hoek Bertil | CO2 sensor |
US6700504B1 (en) * | 2000-11-01 | 2004-03-02 | Navigation Technologies Corp. | Method and system for safe emergency vehicle operation using route calculation |
US20020065604A1 (en) * | 2000-11-30 | 2002-05-30 | Toyota Jidosha Kabushiki Kaisha | Route guide apparatus and guidance method |
US6603405B2 (en) * | 2000-12-05 | 2003-08-05 | User-Centric Enterprises, Inc. | Vehicle-centric weather prediction system and method |
US20020084917A1 (en) * | 2000-12-28 | 2002-07-04 | Hauptman Benjamin J. | Method and apparatus for reducing traffic congestion |
US20020103769A1 (en) * | 2001-01-29 | 2002-08-01 | International Business Machines Corporation | System and method for automatically adjusting merchandise pricing at a service-oriented interface terminal based upon the quantity of users present at the terminal |
US20060173579A1 (en) * | 2001-02-07 | 2006-08-03 | Desrochers Eric M | Air quality monitoring systems and methods |
US20060136291A1 (en) * | 2001-02-15 | 2006-06-22 | Hitachi, Ltd. | Vehicle managing method |
US20040119609A1 (en) * | 2001-03-07 | 2004-06-24 | Lawrence Solomon | Traffic control system with road tariff depending on the congestion level |
US20030037538A1 (en) * | 2001-08-16 | 2003-02-27 | Rendahl Craig S. | Catalytic converter function detection |
US20030040944A1 (en) * | 2001-08-22 | 2003-02-27 | Hileman Ryan M. | On-demand transportation system |
US20030065630A1 (en) * | 2001-10-02 | 2003-04-03 | International Business Machines Corporation | Adjusting an amount owed for fueling based on vehicle characteristics |
US6604045B2 (en) * | 2001-11-01 | 2003-08-05 | Nissan Motor Co., Ltd. | Navigation system, data server, traveling route establishing method and information providing method |
US20030233321A1 (en) * | 2001-11-30 | 2003-12-18 | Scolini Anthony J. | Integrated invoice solution |
US6693555B1 (en) * | 2001-12-11 | 2004-02-17 | Koninklijke Philips Electronics N.V. | Automatic setting of variable speed limit |
US20030110075A1 (en) * | 2001-12-12 | 2003-06-12 | Pioneer Corporation | Toll collection system, its mobile terminal and toll processing apparatus, terminal processing program for the mobile terminal, and record medium recording the terminal processing program |
US20030115095A1 (en) * | 2001-12-18 | 2003-06-19 | Fujitsu Limited | Toll road toll paying method and apparatus using a portable terminal, and a storage medium thereof |
US20030191568A1 (en) * | 2002-04-09 | 2003-10-09 | Breed David S. | Method and system for controlling a vehicle |
US20040049424A1 (en) * | 2002-06-21 | 2004-03-11 | Murray Thomas A. | System and method for facilitating ridesharing |
US20050246190A1 (en) * | 2002-07-20 | 2005-11-03 | Richard Sandor | Systems and methods for trading emission reductions |
US20040075582A1 (en) * | 2002-10-21 | 2004-04-22 | Terry Bergan | Variable speed limit system |
US20050278214A1 (en) * | 2002-10-25 | 2005-12-15 | Yoshiaki Takida | Toll road charge collection system using artificial satellite, charge collecting machine, and charge collecting method |
US20040093264A1 (en) * | 2002-11-07 | 2004-05-13 | Tessei Shimizu | Eco-driving diagnostic system and method, and business system using the same |
US20060278705A1 (en) * | 2003-02-21 | 2006-12-14 | Accenture Global Services Gmbh | Electronic Toll Management and Vehicle Identification |
US20040167861A1 (en) * | 2003-02-21 | 2004-08-26 | Hedley Jay E. | Electronic toll management |
US20040212518A1 (en) * | 2003-02-26 | 2004-10-28 | Koji Tajima | System for notifying tool charge information |
US20050003802A1 (en) * | 2003-07-02 | 2005-01-06 | Joseph Joseph | System for managing traffic patterns using cellular telephones |
US20050049781A1 (en) * | 2003-08-28 | 2005-03-03 | General Motors Corporation | Method and system for providing a carpool service using a telematics system |
US20070100687A1 (en) * | 2003-11-26 | 2007-05-03 | Matsushita Electric Industrial Co., Ltd. | Vehicle management system |
US20050168351A1 (en) * | 2004-01-26 | 2005-08-04 | Denso Corporation | Device and system for toll payment |
US20050187820A1 (en) * | 2004-02-23 | 2005-08-25 | Krishna Mohan | Participating in an incentive program using a portable memory device |
US7003398B2 (en) * | 2004-02-24 | 2006-02-21 | Avaya Technology Corp. | Determining departure times for timetable-based trips |
US20060015394A1 (en) * | 2004-07-15 | 2006-01-19 | Sorensen Roger G | Licensed driver detection for high occupancy toll lane qualification |
US20060155486A1 (en) * | 2004-10-07 | 2006-07-13 | Walsh Alicia M | Computer-implemented system and method for analyzing mixtures of gases |
US20060099964A1 (en) * | 2004-11-05 | 2006-05-11 | Ebay Inc. | System and method for location based content correlation |
US20110112908A1 (en) * | 2004-12-31 | 2011-05-12 | Google Inc., a California corporation | Transportation Routing |
US20050179563A1 (en) * | 2005-03-14 | 2005-08-18 | Kelley Kalon L. | Motor vehicle occupancy signaling system |
US20060255967A1 (en) * | 2005-04-22 | 2006-11-16 | Woo Henry S Y | Open road vehicle emissions inspection |
US20070050279A1 (en) * | 2005-08-26 | 2007-03-01 | Palo Alto Research Center Incorporated | Reverse bidding for trip services |
US20070061057A1 (en) * | 2005-08-26 | 2007-03-15 | Palo Alto Research Center Incorporated | Vehicle network advertising system |
US8666376B2 (en) * | 2005-09-14 | 2014-03-04 | Millennial Media | Location based mobile shopping affinity program |
US20070063858A1 (en) * | 2005-09-20 | 2007-03-22 | Tzong-Sheng Lee | Multi-function wireless detecting device |
US20130080307A1 (en) * | 2005-10-04 | 2013-03-28 | Steven M. Hoffberg | Multifactorial optimization system and method |
US20070083322A1 (en) * | 2005-10-11 | 2007-04-12 | Van Ee Jonathan H | Freeway optimization program |
US8447661B2 (en) * | 2005-11-04 | 2013-05-21 | Microsoft Corporation | Query analysis for geographic-based listing service |
US20080091341A1 (en) * | 2006-06-27 | 2008-04-17 | Microsoft Corporation | Route monetization |
US7797267B2 (en) * | 2006-06-30 | 2010-09-14 | Microsoft Corporation | Methods and architecture for learning and reasoning in support of context-sensitive reminding, informing, and service facilitation |
US20080004926A1 (en) * | 2006-06-30 | 2008-01-03 | Microsoft Corporation | Methods and architectures for context-sensitive reminders and service facilitation |
US20080086310A1 (en) * | 2006-10-09 | 2008-04-10 | Kent Campbell | Automated Contextually Specific Audio File Generator |
US8073460B1 (en) * | 2007-03-08 | 2011-12-06 | Amazon Technologies, Inc. | System and method for providing advertisement based on mobile device travel patterns |
US20090157540A1 (en) * | 2007-12-14 | 2009-06-18 | Microsoft Corporation | Destination auctioned through business of interest |
US8428859B2 (en) * | 2007-12-14 | 2013-04-23 | Microsoft Corporation | Federated route production |
US20090157307A1 (en) * | 2007-12-14 | 2009-06-18 | Microsoft Corporation | Additional content based on intended travel destination |
US20090240584A1 (en) * | 2008-03-18 | 2009-09-24 | Ajaindra Prakash Singh | Method and system for conducting online cash deposit auctions for transacting assets and other goods and services |
US8219115B1 (en) * | 2008-05-12 | 2012-07-10 | Google Inc. | Location based reminders |
US8385944B1 (en) * | 2008-05-12 | 2013-02-26 | Google Inc. | Location based reminders |
US20090327148A1 (en) * | 2008-06-27 | 2009-12-31 | Microsoft Corporation | Mechanisms and architecture for mobile opportunistic commerce |
US20100057532A1 (en) * | 2008-09-03 | 2010-03-04 | Sanguinetti Thomas V | System and method for delivering relevant business information to customer and for tracking customer responses |
US20100205060A1 (en) * | 2009-02-09 | 2010-08-12 | Yahoo! Inc. | Context-sensitive route generation system |
US8332270B2 (en) * | 2009-02-19 | 2012-12-11 | Qualcomm Incorporated | System and method for utilizing a wireless communications device |
US20100217525A1 (en) * | 2009-02-25 | 2010-08-26 | King Simon P | System and Method for Delivering Sponsored Landmark and Location Labels |
US20100332315A1 (en) * | 2009-06-26 | 2010-12-30 | Microsoft Corporation | Generation of impression plans for presenting and sequencing advertisement and sales opportunities along potential routes |
US20120078743A1 (en) * | 2010-09-23 | 2012-03-29 | Epona Llc | System and Method for Coordinating Transport of Cargo |
Cited By (55)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
USRE49334E1 (en) | 2005-10-04 | 2022-12-13 | Hoffberg Family Trust 2 | Multifactorial optimization system and method |
US8478603B2 (en) | 2009-06-24 | 2013-07-02 | International Business Machines Corporation | Method and system for monitoring and reporting to an operator greenhouse gas emission from a vehicle |
US8812352B2 (en) | 2009-10-14 | 2014-08-19 | International Business Machines Corporation | Environmental stewardship based on driving behavior |
US9909885B2 (en) | 2009-10-14 | 2018-03-06 | International Business Machines Corporation | Determining a travel route |
US20110166958A1 (en) * | 2010-01-05 | 2011-07-07 | International Business Machines Corporation | Conducting route commerce from a central clearinghouse |
US10366385B1 (en) | 2010-03-23 | 2019-07-30 | Amazon Technologies, Inc. | Mobile payments using point-of-sale infrastructure |
US10339549B1 (en) | 2010-03-23 | 2019-07-02 | Amazon Technologies, Inc. | Transaction bootstrapping to create relationships |
US9058604B2 (en) | 2010-03-23 | 2015-06-16 | Amazon Technologies, Inc. | Converged web-identity and mobile device based shopping |
US9107064B1 (en) | 2010-03-23 | 2015-08-11 | Amazon Technologies, Inc. | Mobile device security |
US9916608B1 (en) | 2010-03-23 | 2018-03-13 | Amazon Technologies, Inc. | User profile and geolocation for efficient transactions |
US9681359B2 (en) | 2010-03-23 | 2017-06-13 | Amazon Technologies, Inc. | Transaction completion based on geolocation arrival |
US10438242B1 (en) | 2010-03-23 | 2019-10-08 | Amazon Technologies, Inc. | Converged web-identity and mobile device based shopping |
US9760885B1 (en) | 2010-03-23 | 2017-09-12 | Amazon Technologies, Inc. | Hierarchical device relationships for geolocation-based transactions |
US9386507B1 (en) | 2010-03-23 | 2016-07-05 | Amazon Technologies, Inc. | Mobile device security |
US9723131B1 (en) | 2010-03-23 | 2017-08-01 | Amazon Technologies, Inc. | Mobile device security |
US9609577B1 (en) | 2010-03-23 | 2017-03-28 | Amazon Technologies, Inc. | Mobile device security |
US9697508B1 (en) | 2010-03-23 | 2017-07-04 | Amazon Technologies, Inc. | Mobile payments using point-of-sale infrastructure |
US9965768B1 (en) | 2011-05-19 | 2018-05-08 | Amazon Technologies, Inc. | Location-based mobile advertising |
US9147216B2 (en) | 2011-07-05 | 2015-09-29 | Sidekick Technology LLC | Automobile transaction facilitation based on customer selection of a specific automobile |
US9123075B2 (en) | 2011-07-05 | 2015-09-01 | Sidekick Technology LLC | Used automobile transaction facilitation for a specific used automobile |
US9626704B2 (en) | 2011-07-05 | 2017-04-18 | Sidekick Technology LLC | Automobile transaction facilitation based on a customer selection of a specific automobile |
US9460467B2 (en) | 2011-07-05 | 2016-10-04 | Sidekick Technology LLC | Used automobile transaction facilitation for a specific used automobile |
US8650093B2 (en) | 2011-07-05 | 2014-02-11 | Sidekick Technology LLC | Used automobile transaction facilitation for a specific used automobile |
US9665897B2 (en) | 2011-07-05 | 2017-05-30 | Sidekick Technology LLC | Automobile transaction facilitation using a manufacturer response |
US9141984B2 (en) | 2011-07-05 | 2015-09-22 | Sidekick Technology LLC | Automobile transaction facilitation using a manufacturer response |
US8744925B2 (en) | 2011-07-05 | 2014-06-03 | Sidekick Technology Inc. | Automobile transaction facilitation based on customer selection of a specific automobile |
US10796362B2 (en) | 2011-07-05 | 2020-10-06 | Sidekick Technology LLC | Used automobile transaction facilitation for a specific used automobile |
US10223722B2 (en) | 2011-07-05 | 2019-03-05 | Sidekick Technology LLC | Automobile transaction facilitation based on a customer selection of a specific automobile |
US10140655B2 (en) | 2011-07-05 | 2018-11-27 | Sidekick Technology LLC | Used automobile transaction facilitation for a specific used automobile |
US10223720B2 (en) | 2011-07-05 | 2019-03-05 | Sidekick Technology LLC | Automobile transaction facilitation using a manufacturer response |
US20130013180A1 (en) * | 2011-07-07 | 2013-01-10 | International Business Machines Corporation | Context-based traffic flow control |
US8909462B2 (en) * | 2011-07-07 | 2014-12-09 | International Business Machines Corporation | Context-based traffic flow control |
US9039535B2 (en) | 2011-10-17 | 2015-05-26 | International Business Machines Corporation | Tool employing dynamic competition levels for improved performance |
US20170330394A1 (en) * | 2012-08-14 | 2017-11-16 | Ebay Inc. | Method and system of bidding in a vehicle |
US10922907B2 (en) | 2012-08-14 | 2021-02-16 | Ebay Inc. | Interactive augmented reality function |
US11610439B2 (en) | 2012-08-14 | 2023-03-21 | Ebay Inc. | Interactive augmented reality function |
US10664900B2 (en) | 2013-08-15 | 2020-05-26 | Frank Daly Ward | Indoor location mapping and wayfinding system |
US11182843B2 (en) | 2013-08-15 | 2021-11-23 | Frank Ward | Indoor location mapping and wayfinding system |
US11651419B2 (en) | 2013-08-15 | 2023-05-16 | Frank Ward | Indoor location mapping and wayfinding system |
US10672063B2 (en) | 2013-08-15 | 2020-06-02 | Frank Daly Ward | Indoor location mapping and wayfinding system |
US10679279B2 (en) | 2013-08-15 | 2020-06-09 | Frank Daly Ward | Indoor location mapping and wayfinding system |
US9940663B2 (en) * | 2013-08-15 | 2018-04-10 | Frank Daly Ward | Indoor location mapping and wayfinding system |
US20160162989A1 (en) * | 2014-12-06 | 2016-06-09 | David John Cole | Mobile opportunistic trading markets |
US10373205B2 (en) | 2016-07-26 | 2019-08-06 | Wrapify, Inc. | System and method for estimating visual impressions of vehicles configured with external graphic messaging |
US11610229B2 (en) | 2016-07-26 | 2023-03-21 | Wrapify, Inc. | System and method for estimating visual impressions of vehicles configured with external graphic messaging |
US20190120654A1 (en) * | 2017-10-20 | 2019-04-25 | Paypal, Inc. | Load balancing for map application route selection and output |
US11391585B2 (en) * | 2017-10-20 | 2022-07-19 | Paypal, Inc. | Load balancing for map application route selection and output |
US20230009813A1 (en) * | 2017-10-20 | 2023-01-12 | Paypal, Inc. | Load balancing for map application route selection and output |
US10670414B2 (en) * | 2017-10-20 | 2020-06-02 | Paypal, Inc. | Load balancing for map application route selection and output |
US11913799B2 (en) * | 2017-10-20 | 2024-02-27 | Paypal, Inc. | Load balancing for map application route selection and output |
US10878441B2 (en) | 2018-11-07 | 2020-12-29 | International Business Machines Corporation | Adjusting route parameters using a centralized server |
US11702081B2 (en) * | 2019-02-14 | 2023-07-18 | Honda Motor Co., Ltd. | System and method for road condition monitoring |
WO2021043176A1 (en) * | 2019-09-02 | 2021-03-11 | 中兴通讯股份有限公司 | Method for sending rcs service message, device, client, and server |
US11507857B2 (en) | 2019-10-01 | 2022-11-22 | TeleLingo | Systems and methods for using artificial intelligence to present geographically relevant user-specific recommendations based on user attentiveness |
CN110853163A (en) * | 2019-10-28 | 2020-02-28 | 北京中交国通智能交通系统技术有限公司 | AI and vehicle road cooperation based vehicle path identification charging system and method |
Also Published As
Publication number | Publication date |
---|---|
US20180073878A1 (en) | 2018-03-15 |
US20150330799A1 (en) | 2015-11-19 |
US9909885B2 (en) | 2018-03-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9909885B2 (en) | Determining a travel route | |
JP6732963B2 (en) | System and method for monitoring on-demand services | |
US11913799B2 (en) | Load balancing for map application route selection and output | |
US11162803B2 (en) | Providing alternative routing options to a rider of a transportation management system | |
US20110087524A1 (en) | Determining travel routes by using fee-based location preferences | |
US8793066B2 (en) | Route monetization | |
US8660894B2 (en) | Advertising proximity route selection | |
US20110166958A1 (en) | Conducting route commerce from a central clearinghouse | |
US20130339173A1 (en) | Consumer-to-Business Exchange Auction | |
WO2016113602A1 (en) | Real-time presenting on-demand service providers and users or customers and facilitating them | |
US20150095197A1 (en) | Systems and methods for minimizing travel costs for use of transportation providers by a user | |
JP6936669B2 (en) | Congestion avoidance support system and congestion avoidance support method | |
US20180276614A1 (en) | System for Inventory Control | |
WO2014126907A1 (en) | Systems and methods for providing an online marketplace for route guidance | |
JP2019520641A (en) | METHOD, APPARATUS AND SYSTEM FOR PROVIDING RANDOM ADDITIONAL DISCOUNTS AFTER Settlement in Electronic Commerce on an Open Market | |
US11710160B2 (en) | Systems and non-transitory computer-readable medium for community merchant cross selling/promoting with shared ecommerce shopping cart for items selected by community residents incented to conduct transactions to incent community donations | |
US7392215B1 (en) | Method of processing bids over a network | |
US10878441B2 (en) | Adjusting route parameters using a centralized server | |
US11823090B2 (en) | Transportation and freight and parking and tolling and curb capacity unit IPO method and system | |
US20140136300A1 (en) | Authorized transaction incented by merchant donation | |
WO2005013074A2 (en) | Systems and methods for airline ticket sales | |
JP2002334241A (en) | Sales support system linked with navigation system and method therefor | |
US20140149218A1 (en) | Promotional item deliveries based on planned/future traveling | |
US20230306468A1 (en) | Cartop Advertisement Vehicle-Based Routing and Matching | |
US20200126121A1 (en) | Surfacing advertisements to purchase tangible products through digital transactions |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BOSS, GREGORY JENSEN;HAMILTON, RICK ALLEN, II;MARTINO, JACQUELYN ANNETTE;AND OTHERS;SIGNING DATES FROM 20091007 TO 20091008;REEL/FRAME:023369/0908 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: AIRBNB, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:056427/0193 Effective date: 20210106 |