WO2016133516A1

WO2016133516A1 - Provider offer

Info

Publication number: WO2016133516A1
Application number: PCT/US2015/016537
Authority: WO
Inventors: Chandra Kamalakantha; Parag Doshi
Original assignee: Hewlett Packard Enterprise Development Lp
Priority date: 2015-02-19
Filing date: 2015-02-19
Publication date: 2016-08-25

Abstract

Example implementations relate to a provider offer. For example, computing device may include a processor. The processor may receive a request for a particular product or service, wherein the request is associated with an account of a user. The processor may identify providers of the particular product or service located within a particular distance from a location of the user, wherein the providers are identified according to preferences specified by the user in the account. The processor may send the request to the providers and notify the user of at least one offer from at least one of the providers, wherein the at least one offer specifies a price offered by the at least one of the providers. The processor may receive, from the user, an acceptance of one of the at least one offer.

Description

PROVIDER OFFER

BACKGROUND

[0001] The use of global positioning systems for navigation is prevalent. For example, a driver may input a desired destination in a globai positioning system in the driver's vehicle, and the global positioning system may provide directions for a route to the inputted destination. The global positioning system may track the vehicle's position as the vehicle follows the route and may adjust the route if the driver deviates from the original route.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Some examples of the present application are described with respect to the following figures:

[0003] FIG. 1 is a block diagram of an example computing device for requesting provider offers;

[0004] FIG. 2 is a flowchart of an example method for requesting provider offers; and

[0005] FIG. 3 is a block diagram of an example system for requesting providers.

DETAILED DESCRIPTION

[0006] As described above, a global positioning system (GPS) may be used to access directions to a particular destination. For example, a driver may input a particular destination into a GPS, and the GPS may provide directions from the driver's current location to the inputted destination.

However, while a driver is driving, the driver's vehicle may become low on fuel, and the driver may wish to locate a nearby fueling station to refuel the vehicle.

[0007] A location-based fuel auctioning system as described herein may be used to send requests for fuel provider offers based on a user's location and/or user preferences specified in an account associated with the user. The requests may be sent from a driver's computing device (e.g., in-vehicle computing device, mobile device, etc.) to one or more fuel providers that may respond to the request with a fuel provider offer associated with a fuel sale. For example, in response to a request, a fuel provider may offer a driver a discounted fuel price in order to attract business from the driver. The request may be sent over a network via a central server (e.g., cloud-based server) to a computing device of a fuel provider. A fuel provider may view offers from other fuel providers and may adjust their offer accordingly in order to make the offer more appealing to the driver. The offers from fuel providers may be sent, via the central server, to the driver's computing device, and the driver may select a particular offer to accept. The acceptance is sent to the selected fuel provider, and the agreed-upon offer may be given to the driver when the driver arrives at the selected fuel provider.

[0008] While the examples disclosed herein describe fuel sales, one of ordinary skill in the art will appreciate that the techniques disclosed herein may extend to other products and/or services available for sale. For example, a user may wish to purchase a particular product and may request offers from various sellers of the product. The central server may receive the request from a user's computing device and may identify providers that offer the product for sale, have the product in stock, fit the user's specified preferences, and/or are located within a particular distance from the user. The central server may send the request to the identified providers, and the providers may submit offers relating to the product, bidding with each other in the process. The offers are sent from the providers to the user via the central server, and the user may select an offer to accept. For ease of explanation, the examples described herein relate to requests for fuel. However, the techniques described in these examples may apply to any products and/or services.

[0009] A request for fuel may be sent to the central server from a computing device of a user. The user's computing device may be any suitable computing device capable of communicating with the central server, such as an in-vehicle computing device, a mobile device (e.g., a mobile phone, tablet, etc.), and the like. In some examples, the user may access the central server using an application on the user's computing device (e.g., dedicated application, web browser, etc.). The user's computing device may include a GPS to manage the location of the user's computing device and any additional locations to which the user may wish to navigate. In some examples, the user's computing system may be integrated with a mapping service (e.g., a third-party map service) that may aid in navigation, provide routes, accommodate for current traffic conditions, and the like, in some examples, a user may subscribe to the services provided by the central server and register the user's computing device with the central server. For example, a user may create an account associated with the central server, allowing the user to access the services provided by the central server. The user may create the account in any suitable manner, such as using the user's computing device (e.g., in-vehicle computing device, mobile device, etc.). in some examples, the user may specify and adjust preferences in the user's account (e.g., during registration or anytime thereafter), such as preferred fuel providers, desired characteristics of fuei providers (e.g., sells food and/or drinks, has clean bathrooms, etc.), any loyalty programs to which the user subscribes, and the like.

[0010] A provider may be any provider of any suitable type of product and/or service. In some examples, a fuel provider may be a provider of any suitable type of fuel, such as gasoline station, electric charging station, and the like. The central server may send requests for fuel to fuei provider computing devices. A fuel provider computing device may be any suitable computing device capable of communicating with the central server, such as a desktop computing device, a point-of-sale register, a mobile device, and the like. A fuel provider may subscribe to the services provided by the central server and may specify preferences associated with fuei requests. For example, when a fuel request is received, the fuel provider computing device may automatically respond to the request with an offer that may be based on the preferences specified by the fuel provider. For example, when a request is received, the provider computing device may determine, based on the specified preferences, whether to provide an offer in response and what type of offer to provide. The provider computing device may also receive offers from other fuel providers and may use that information to adjust their own offer. In some examples, an offer in response to a fuel request may be provided manually (e.g., by an employee of the fuel provider).

[0011] A request for fuel may be sent from a user's computing device in any suitable manner. In some examples, the request for fuel may be automatically sent in response to a vehicle's telematics detecting that the fuel level has reached a particular threshold amount, where the vehicle's telematics may be in communication with the user's computing device. In some examples, the request for fuel may be sent in response to a user input initiating the request through the user's computing device. In some examples, a vehicle may be equipped with a plug-in sensor that may sense the fuel level in the vehicle, and the fuel level may be communicated to the user's computing device such that when the fuel level reaches a particular threshold level, the fuel request may be sent to fuel providers via the central server. The request for fuel may include the location of the user's computing device.

[0012] Once the fuel request is sent from the user's computing device to the central server, the central server may access the account associated with the user's computing device, inciuding accessing the preferences specified by the user in the user's account. The central server may use the preferences as well as the location of the user's computing device to identify fuel providers within a particular distance from the user's location and meeting the criteria specified by the user's preferences. In some examples, the fuel providers identified may be fuel providers along or near a route that a user is taking to a particular destination.

[0013] The request for fuel may be broadcast to the identified fuel providers (e.g., based on the user's location, preferences, etc.). The request for fuel may be broadcast to fuel providers in real-time. A fuel provider receiving the request may also receive offers from other fuel providers in response to the request, and the fuel provider (e.g., the fuel provider computing device) may submit an offer based on the request and based on the other offers from other fuel providers. As such, an offer made by a fuel provider may be based on bidding between the various fuel providers identified. In some examples, a fuel provider may decide not to submit an offer in response to the request for fuel (e.g., based on the fuel provider's specified preferences) and/or in response to other offers from other fuel providers.

[0014] When the central server receives offers from at least a portion of the identified fuel providers, the offers are sent to the user's computing device via the central server. The offers may include any information associated with the offer for the sale of fuel and any terms associated with the offer for the sale of fuel. For example, the offer may specify a discounted price for fuel, may specify a minimum and/or maximum purchase amount, may specify additional products available (e.g., a free drink), may request that the user become a loyalty member, may specify an expiration date and/or time, and the like. In some examples, the offers may be provided to the user in a particular order (e.g., based on the cost of fuel specified in the offer, based on a user's previous buying pattern, etc.). In some examples, the offers may be displayed visually and/or presented audibly through the user's computing device (e.g., in-vehicle computing device, mobile device, etc.).

[0015] A user may use the user's computing device to select a particular offer that the user wishes to accept. The user's acceptance may be sent from the user's computing device to the corresponding fuel provider via the central server such that the fuel provider that submitted the selected offer may be notified of the acceptance. In some examples, the fuel providers whose offers were not accepted may be notified that their offer was not selected.

[0016] Referring now to the figures, FIG. 1 is a block diagram of an example computing device 100 for requesting provider offers. Computing device 100 may be a server (e.g., a cloud-based server) that may receive a product and/or service request (e.g., fuel) from a user's computing device, broadcast the request to one or more providers, receive offers from one or more providers, and provide the offers to the user via the user's computing device.

[0017] Computing device 100 may be, for example, a web-based server, a local area network server, a cloud-based server, a notebook computer, a desktop computer, an all-in-one system, a tablet computing device, a mobile phone, an electronic book reader, a printing device, or any other electronic device suitable for requesting provider offers. Computing device 100 may include a processor 102 and a machine-readable storage medium 104.

Computing device 100 may receive a request for a particular product and/or service from a user and may broadcast the request to one or more providers that may each return an offer in response to the request.

[0018] Processor 102 is a tangible hardware component that may be a central processing unit (CPU), a semiconductor-based microprocessor, and/or other hardware devices suitable for retrieval and execution of instructions stored in machine-readable storage medium 104. Processor 102 may fetch, decode, and execute instructions 106, 108, 1 10, 112, and 114 to control a process of requesting provider offers. As an alternative or in addition to retrieving and executing instructions, processor 102 may include at least one electronic circuit that includes electronic components for performing the functionality of instructions 106, 108, 110, 1 12, 114, or a combination thereof.

[0019] Machine-readable storage medium 104 may be any electronic, magnetic, optical, or other physical storage device that contains or stores executable instructions. Thus, machine-readable storage medium 104 may be, for example, Random Access Memory (RAM), an EPROM, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a storage device, an optical disc, and the like. In some examples, machine-readable storage medium 104 may be a non-transitory storage medium, where the term "non- transitory" does not encompass transitory propagating signals. As described in detail below, machine-readable storage medium 104 may be encoded with a series of processor executable instructions 106, 108, 110, 112, and 114 for receiving a request for a particular product or service, wherein the request is associated with an account of a user; identifying providers of the particular product or service located within a particular distance from a location of the user, wherein the providers are identified according to preferences specified by the user in the account; broadcasting and/or sending the request to the providers; receiving and notifying the user of at least one offer from at least one of the providers, wherein the at least one offer specifies a price offered by the at least one of the providers; receiving an acceptance of one of the at least one offer; and sending the acceptance to the corresponding provider. [0020] Request receipt instructions 106 may manage and control the receipt of requests for products and/or services. A request may be associated with an account of a user. For example, a user's computing device (e.g., in- vehicie computing device, mobile device) may be associated with an account of the user and may send a request for a particular product or service to computing device 100. The request may be received either automatically (e.g., in response to the user's computing device detecting a low fuel level) or may be received in response to a user input initiating the request.

[0021] Provider identification instructions 108 may manage and control the identification of providers that may fulfill the request. For example, the providers identified may include providers of the requested product and/or service located within a particular location from a location of the user and/or the user's computing device. The location of the user and/or the user's computing device may be determined using a GPS associated with the user's computing device. The providers identified may also be based on

preferences specified by the user in the user's account. For example, a user requesting fuel may specify that the user wishes to receive offers from fuel providers that also provide other products and/or services, such as a convenience store for food and/or drinks.

[0022] Broadcast instructions 110 may manage and control the

broadcasting and/or sending of the request to the identified providers. For example, once providers have been identified (e.g., based on the user's location and/or the user's preferences), the request may be broadcast to the identified providers' computing devices.

[0023] Offer instructions 112 may manage and control any offers received from the identified providers. Offer instructions 112 may also send

information about offers from various providers to other providers such that each provider may be competitive in their offer if they wish to do so. For example, offer instructions 112 may receive offers from any number of the identified providers and may send information about any offers received to the identified providers such that the providers may competitively adjust their offers accordingly if they wish. Once the final offers from any of the identified providers have been received, offer instructions 112 may notify the user of the offers and any information associated with the offers (e.g., an expiration time and/or date, an associated minimum and/or maximum purchase, etc.).

[0024] Acceptance instructions 114 may manage and control the receipt of an acceptance of a particular offer by the user and the sending of a notification of the acceptance to the corresponding provider. For example, a user may select an offer from a particular provider, and that provider may be notified of the acceptance.

[0025] FIG. 2 is a flowchart of an example method 200 for requesting provider offers. Method 200 may be implemented using computing device 100 of FIG. 1.

[0026] Method 200 includes, at 202, receiving a request for a particular product or service, the request being associated with an account of a user. The request may be received based on a user input initiating the request or based on telematics associated with the user's vehicle (e.g., based on telematics detecting a low fuel level).

[0027] Method 200 also includes, at 204, determining providers of the requested product or service located within a particular distance from a location of the user, the providers being determined according to preferences specified by the user in the account. For example, a GPS associated with the user's computing device may detect the user's location, and that location, along with any user-specified preferences, may be used to determine relevant providers.

[0028] Method 200 also includes, at 206, notifying the providers of the request. For example, once the relevant providers have been determined, those providers may be notified of the user's request via the providers' computing devices.

[0029] Method 200 also includes, at 208, receiving offers from a subset of the providers in response to being notified of the request, each offer specifying a price offered by a respective provider of the subset of providers. For example, any number of the determined providers may respond to the request by submitting an offer for the sale of the requested product or service at a specified price. [0030] Method 200 also includes, at 210, sending the offers to the user. For example, once the offers from the subset of the providers has been received, those offers may be sent to the user's computing device.

[0031] Method 200 also includes, at 212, receiving an acceptance by the user of one of the offers. For example, a user may select a particular offer to accept, and that acceptance may be received from the user's computing device.

[0032] FIG. 3 is a block diagram of an example system 300 for requesting providers. System 300 may include server 302, which may be any suitable server for receiving requests for offers from any number of users via their respective computing devices (e.g., users 304), identifying any number of providers (e.g., providers 306) to which the requests are to be sent, receiving offers from the providers via their respective computing devices in response to the requests, and sending the offers to the requesting user. For example, server 302 may be a computing device such as computing device 100 shown in FIG. 1. In some examples, server 302 may be a web-based server, a local area network server, a cloud-based server, and the like. Server 302 may manage accounts associated with users 304 and providers 306, including managing any preferences specified by users 304 and/or providers 306.

[0033] Examples provided herein (e.g., methods) may be implemented in hardware, software, or a combination of both. Example systems may include a controiler/processor and memory resources for executing instructions stored in a tangible non-transitory medium (e.g., volatile memory, non-volatile memory, and/or machine-readable media). Non-transitory machine-readable media can be tangible and have machine-readable instructions stored thereon that are executable by a processor to implement examples according to the present disclosure.

[0034] An example system can include and/or receive a tangible non- transitory machine-readable medium storing a set of machine-readable instructions (e.g., software). As used herein, the controller/processor can include one or a plurality of processors such as in a parallel processing system. The memory can include memory addressable by the processor for execution of machine-readable instructions. The machine-readable medium can include volatile and/or non-volatile memory such as a random access memory ("RAM"), magnetic memory such as a hard disk, floppy disk, and/or tape memory, a solid state drive ("SSD"), flash memory, phase change memory, and the like.

Claims

Ctaims What is claimed is:

1. A computing device, comprising:

a processor to:

receive a request for a particular product or service, wherein the request is associated with an account of a user;

identify providers of the particular product or service located within a particular distance from a location of the user, wherein the providers are identified according to preferences specified by the user in the account;

send the request to the providers;

notify the user of at least one offer from at least one of the providers, wherein the at least one offer specifies a price offered by the at least one of the providers; and

receive, from the user, an acceptance of one of the at least one offer.

2. The computing device of claim 1 , wherein the request is a fuel request automatically received using telematics from a vehicle associated with the account.

3. The computing device of claim 1 , wherein the request is received from a user input.

4. The computing device of claim 1 , wherein the user is notified of the at least one offer through an in-vehic!e device or a mobile device.

5. The computing device of claim 1 , wherein the at least one offer is provided based on bidding between different providers of the at least one of the providers.

6. The computing device of claim 1 , wherein the processor is further to notify a respective provider of the acceptance.

7. A method, comprising:

receiving, by a computing device, a request for a particular product or service, the request being associated with an account of a user;

determining, by the computing device, providers of the particular product or service located within a particular distance from a location of the user, the providers being determined according to preferences specified by the user in the account;

notifying, by the computing device, the providers of the request;

receiving, by the computing device, offers from a subset of the providers in response to being notified of the request, each offer specifying a price offered by a respective provider of the subset of the providers;

sending, by the computing device, the offers to the user; and receiving, by the computing device, an acceptance by the user of one of the offers.

8. The method of claim 7, wherein the request is a fuel request automatically received using telematics from a vehicle associated with the account.

9. The method of claim 7, wherein the request is received from a user input.

10. The method of claim 7, wherein the offers are received based on bidding between providers of the subset of the providers.

1 1. The method of claim 7, wherein the offers are sent to the user through an in-vehicle device or a mobile device.

12. A non-transitory machine-readable storage medium storing instructions that, if executed by at least one processor of a computing device, cause the computing device to:

broadcast the request to the providers;

receive offers from a subset of the providers in response to the broadcast, each offer specifying a price offered by the corresponding provider of the subset of the providers; and

transmit an acceptance of one of the offers from the user to the corresponding provider.

13. The non-transitory machine-readable storage medium of claim 12, wherein the request is received from a user input or is automatically received using telematics from a vehicle associated with the account.

14. The non-transitory machine-readable storage medium of claim 12, wherein the offers are received based on bidding between providers of the subset of the providers.

15. The non-transitory machine-readable storage medium of claim 12, wherein the instructions further cause the computing device to notify the user of the offers through an in-vehicle device or a mobile device.