# US 2019/0318426 A1 · Vehicle fuel as a service

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0318426 A1
- Document ID: US20190318426A1
- Status: Published application
- Kind: A1
- Application number: 16/386,165
- Filed: 2019-04-16
- Published: 2019-10-17
- Earliest claimed: 2018-04-16
- Assignees: Ationet LLC
- Applicants: Ationet LLC
- Inventors: Gaston FAVEREAU; Pablo C. GUALDI
- Web page: https://patentgrep.com/patent/US20190318426A1

## CPC

- G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
- G06F 16/903: Querying (for retrieval from the web G06F16/953)
- G06Q 20/023: {the neutral party being a clearing house}
- G06Q 20/145: {Payments according to the detected use or quantity}
- G06Q 20/18: involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
- G06Q 20/227: {characterised in that multiple accounts are available, e.g. to the payer}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 50/06: Energy or water supply
- G07F 13/025: {wherein the volume is determined during delivery}
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})

## Abstract

Multiple fuel suppliers and fuel demand consumers provide profile information to an accounts/profile database. Oil suppliers associated with one or more fuel suppliers also provide profile information to the accounts/profile database. Fuel suppliers upload supply posts and demand consumers upload demand posts and a fuel clearinghouse services fulfill demand posts with supply posts based on preferences and restrictions, including contractual restrictions based on the profiles in the accounts/profile database. Upon fulfillment, payment is effected, contracts, such as purchase orders are automatically generated, and usage is monitored until a fulfilled supply post is exhausted. Post, preference, and usage data are centralized and subject to analytics including machine learning analytics, and reports are displayed on portals.

## Claims

### Claim 1

A system to provide vehicle fuel as a service, comprising:
a processor configured to execute computer-readable instructions;
a memory communicatively coupled to the process and configured to store computer-readable instructions;
a post database configured to store fuel supply posts and demand posts, the supply and demand posts including post information comprised of at least of a fuel amount, a fuel price and a time window;
a supply posting software module resident in the memory configured to receive fuel supply posts and to store the received fuel supply posts in the post database, and configured to display selected demand posts;
a demand posting software module resident in the memory configured to receive demand posts and to store the received demand posts in the post database, and configured to display selected supply posts; and
a clearinghouse software module resident in the memory configured to retrieve an unfulfilled supply post from the post database, and to select at least one demand post based at least on some information of the unfulfilled supply post, and to send the selected supply post to the demand posting software module for display and to send the at least one demand post to the supply posting software module.

### Claim 2 (depends on 1)

The system of claim 1, further comprising of an account/profile data store configured to store profiles comprised of preferences and restrictions of at least one demand consumer or fuel supplier, and wherein the clearinghouse software module is configured to select the at least one demand post based at least on one profile.

### Claim 3 (depends on 2)

The system of claim 2, wherein the account/profile data store is configured to store profiles comprised of preferences and restrictions of at least one oil company, the oil company associated with at least one fuel supplier, and wherein the clearinghouse software module is configured to select the at least one demand post based at least on one profile of the oil company.

### Claim 4 (depends on 2)

The system of claim 2, wherein the clearinghouse software module is configured to select a plurality of demand posts based at least on one profile, and to rank a plurality of demand posts based on a predetermined ordering criteria.

### Claim 5 (depends on 1)

The system of claim 1, wherein a supply post or a demand post or both comprise of a fulfillment preference, and wherein the clearinghouse software module is configured to select the at least one demand post based at least on a profile of an oil company.

### Claim 6 (depends on 5)

The system of claim 5, wherein the fulfillment preference is any one of:
time shifting;
demand shifting; or
fuel shifting.

### Claim 7 (depends on 1)

The system of claim 1, wherein the information of the unfulfilled supply post information comprises a fulfillment criteria, the clearinghouse software module is comprised of a plurality of bidding submodules resident in the memory storing rules to select posts and the clearinghouse software, and wherein the clearinghouse software module is configured to selects a submodule corresponding to a fulfillment criteria of a supply post, and the clearinghouse software module selects a demand post based at least on the rules stored in the selected bidding submodule.

### Claim 8 (depends on 7)

The system of claim 7, wherein a bidding submodules are any one of a:
bidding submodule; and
reverse auction submodule.

### Claim 9 (depends on 1)

The system of claim 1, comprising a contract generator module resident in the memory, configured to generate a contract based on a demand post and supply post, wherein the clearinghouse software module is configured to provide a demand post and the selected supply post to the contract generator module, and the contract generator module generates a contract based on a received demand post and a received supply post.

### Claim 10 (depends on 9)

The system of claim 9 wherein the contract generator module sends the generated contract to the posts database and marks the received demand post and supply post as fulfilled.

### Claim 11 (depends on 10)

The system of claim 10, comprising a usage monitoring module resident in the memory configured to receive fuel usage data from a plurality of client fuel mobile applications, to aggregate the received fuel usage data, to detect when fuel usage as exhausted a fulfilled supply post, and to notify at least one fuel provider when a fulfilled supply post is exhausted.

### Claim 12 (depends on 11)

The system of claim 11, comprising a software portal resident in the memory configured to retrieve information from any one of posts from the posts database and fuel usage data from the usage monitoring module, and to display at least some of the retrieved information.

### Claim 13 (depends on 12)

The system of claim 12, comprising a reporting module resident in the memory and accessible by the software portal configured to receive custom query information and wherein the retrieved information is based at least on the received custom query information.

### Claim 14 (depends on 12)

The system of claim 12, wherein the software portal is configured only to display retrieved information in which a user using the software portal has been a party to.

### Claim 15

A method to aggregate and analyze vehicle fuel usage data, comprising:
retrieving from a post database a plurality of fulfilled supply posts;
receiving at a usage monitor fuel usage data from a plurality of client mobile applications, the usage data indicating usage of fuel corresponding to the retrieved fulfilled supply posts;
retrieving from an accounts/profile database profile information regarding fulfillment preferences of at least one demand consumer corresponding to the fulfilled supply post;
performing machine learning analytics on data from the retrieved posts, the received usage data and the fulfillment preferences; and
generating usage patterns based at least on the performed machine learning analytics.

### Claim 16 (depends on 15)

The method of claim 15, comprising generating a recommendation to change at least one fulfillment preference of at least one demand consumer based at least on the performed machine learning analytics.

### Claim 17 (depends on 15)

The method of claim 15, wherein the accounts/profile database includes a profile storing at least one restriction for at least one oil company associated with at least one fuel provider, and wherein the performed machine learning analytics is based at least on the at least one restriction for the at least one oil company.

### Claim 18 (depends on 15)

The method of claim 15, comprising detecting a likelihood of fraud or theft based at least on the performed machine learning analytics.

### Claim 19 (depends on 15)

The method of claim 15 comprising: displaying a generated usage pattern on a software portal, wherein the software portal is configured only to display retrieved information in which a user using the software portal has been a party to.

### Claim 20

A method to provide fuel as a service, comprising:
receiving a supplier registration by a fuel supplier, the supplier registration comprising a profile including preferences of the fuel supplier;
receiving a consumer registration by a demand consumer, the consumer registration including preferences of the demand consumer;
receiving an oil company registration by an oil company associated with the fuel supplier, the oil company registration comprising a profile including preferences of the oil company;
receiving a supply post from the fuel supplier, the supply post comprising at least a quantity of fuel and a fulfillment criterion;
receiving a demand post from the demand consumer, the demand post comprising at least a quantity of fuel;
selecting a bidding submodule based at least on the fulfillment criterion;
determining at the bidding submodule whether to fulfill the received demand post with the received supply post based at least on a combination of the fuel supplier, demand consumer, and oil company profiles;
generating a contract to fulfill the received demand post with the received supply post;
confirming a payment for the quantity of fuel in the supply post from the demand consumer; and
notifying the fuel supplier to release fuel corresponding to the supply post to the demand consumer.
