阅读说明：本技术 向箱供电系统和方法 (System and method for supplying power to a tank ) 是由 凯文·詹姆斯·罗兹 于 2020-09-14 设计创作，主要内容包括：本文提供了向箱供电系统和方法。一种示例系统包括：车辆的人机界面；所述车辆的向箱供电系统；以及控制器,所述控制器具有处理器和存储器,所述处理器执行存储在所述存储器中的指令以：确定对车辆的向箱供电系统的致动；确定在从所述致动延伸到终止事件的使用时段期间所述车辆的所述向箱供电系统的使用参数；生成包括指示所述使用参数的信息的消息；以及将所述消息传输到接收方。(Systems and methods for supplying power to a tank are provided herein. An example system includes: a human-machine interface of the vehicle; a tank power supply system of the vehicle; and a controller having a processor and a memory, the processor executing instructions stored in the memory to: determining actuation of a vehicle to a tank power supply system; determining a usage parameter of the tank power supply system of the vehicle during a usage period extending from the actuation to a termination event; generating a message including information indicating the usage parameter; and transmitting the message to a recipient.)

1. A method, the method comprising:

determining actuation of a vehicle to a tank power supply system;

determining a usage parameter of the tank power supply system of the vehicle during a usage period extending from the actuation to a termination event;

generating a message including information indicating the usage parameter; and

transmitting the message to a recipient.

2. The method of claim 1, further comprising identifying location information of the vehicle and including the location information in the message.

3. The method of claim 1, further comprising determining a first selection of a recording feature that activates recording of the usage parameter during the time period and a second selection of the recording feature that terminates recording of the usage parameter.

4. The method of claim 1, wherein the usage parameters include at least power usage.

5. The method of claim 1, wherein the message comprises an invoice including an invoicing amount for the usage parameter.

6. The method of claim 5, wherein the invoice amount is determined by multiplying power usage by an energy cost factor, further wherein the energy cost factor is determined during charging of the vehicle.

7. The method of claim 5, further comprising:

providing an invoice template through a human-computer interface of the vehicle;

receiving an invoicing item using the invoice template; and

populating the invoice with the invoicing item and the invoicing amount.

8. The method of claim 1, further comprising applying a power constraint parameter to adjust the system supplying power to the tank.

9. The method of claim 8, further comprising automatically disabling the box power supply system when the power constraint parameter has been exceeded.

10. The method of claim 9, further comprising receiving an override command to reactivate the tank power supply system after the automatic deactivation of the tank power supply system.

11. A method, the method comprising:

receiving an actuation of a recording feature provided on a human-machine interface of a vehicle;

determining a usage parameter of the vehicle to a tank power supply system during a usage period extending from the actuation to a termination event;

providing an invoice template to a user through the human-computer interface;

receiving an invoicing item from the invoice template;

converting the usage parameters into an invoicing amount; and

generating an invoice including the invoicing item and the invoicing amount.

12. The method of claim 11, further comprising applying a power constraint parameter to adjust the system supplying power to the tank.

13. The method of claim 12, further comprising automatically disabling the box power supply system when the power constraint parameter has been exceeded.

14. The method of claim 13, further comprising receiving an override command to reactivate the box power supply system after the automatic deactivation.

15. A system, the system comprising:

a human-machine interface of the vehicle;

a tank power supply system of the vehicle; and

a controller comprising a processor and a memory, the processor executing instructions stored in the memory to:

determining actuation of a vehicle to a tank power supply system;

determining a usage parameter of the tank power supply system of the vehicle during a usage period extending from the actuation to a termination event;

generating a message including information indicating the usage parameter; and

transmitting the message to a recipient.

Technical Field

The present disclosure relates to a tank power supply (PttB) system and method that allows a user to control and track the use of the PttB system in a vehicle.

Background

The adoption of motorized vehicles is currently expanding to include larger platforms that include trucks. This has driven the development of Power-to-the-box (pttb) features within vehicles that will allow drivers to supply Power to worksites, camps, tailgates, etc. through receptacles or ports mounted in the truck cargo bed. One of the most demanding applications involves field contractors who utilize electricity for commercial purposes.

Disclosure of Invention

Systems and methods for supplying power to a tank are provided herein. An example system includes: a human-machine interface of the vehicle; a tank power supply system of the vehicle; and a controller having a processor and a memory, the processor executing instructions stored in the memory to: determining actuation of a vehicle to a tank power supply system; determining a usage parameter of the tank power supply system of the vehicle during a usage period extending from the actuation to a termination event; generating a message including information indicating the usage parameter; and transmitting the message to a recipient.

Drawings

Specific embodiments are described with reference to the accompanying drawings. The use of the same reference numbers may indicate similar or identical items. Various embodiments may utilize elements and/or components other than those shown in the figures, and some elements and/or components may not be present in various embodiments. Elements and/or components in the drawings have not necessarily been drawn to scale. Throughout this disclosure, singular and plural terms may be used interchangeably, depending on the context.

FIG. 1 shows an illustrative architecture in which techniques and structures for providing the systems and methods disclosed herein may be implemented.

Fig. 2 is a flow chart of an example method of the present disclosure.

Fig. 3 is a flow chart of another example method of the present disclosure.

FIG. 4 illustrates an example Graphical User Interface (GUI) that can be utilized in accordance with embodiments of the present disclosure.

FIG. 5 illustrates an example Graphical User Interface (GUI) that may be utilized to provide invoice templates in accordance with embodiments of the present disclosure.

Detailed Description

Overview

The systems and methods disclosed herein are configured to allow a user of the PttB system to track and control the use of the PttB system of the vehicle. PttB system power usage events can be tracked, analyzed, recorded, and invoiced. Power usage events may be measured and converted to cost values using energy cost factors. According to some embodiments, power usage events may be recorded and converted into line entries of an invoice. In this manner, a user may use the systems and methods disclosed herein to create an invoice that includes PttB usage, as well as other work cost items such as a bill of materials.

According to some embodiments, the systems and methods herein may provide automated PttB control features, where PttB usage may be controlled based on usage limitations. For example, the PttB system may be automatically shut down when power usage exceeds an allowable limit.

The systems and methods herein allow PttB users to measure, record, and invoice the energy consumed by external devices in the PttB system. For example, upon arrival at a job site, a driver of a vehicle configured with the PttB system disclosed herein may activate their PttB system and press a button or other recording feature to "start work". In other embodiments, tracking may be based on activation of (e.g., drawing power from) the PttB system without requiring a user to activate the recording feature. The recording feature may be actuated through a Graphical User Interface (GUI) provided on a Human Machine Interface (HMI) of the vehicle, such as an infotainment system.

The controller of the vehicle may create a new work file to which the controller will record the time, date, location, and other relevant information of the work at hand. The controller may also begin measuring and recording the energy available from the PttB system. During operation, the driver may use a power drill, table saw, planer, or other tool that consumes energy from the PttB system. The controller of the vehicle may record the power drawn in order to determine the total energy consumed for a given job or other period of use.

At the end of the job, the driver may select to "end the job". At this point, the controller of the vehicle may generate an invoice that includes the total kWh kilowatt-hours of energy consumed during the job by multiplying the kWh number of energy used by some energy cost factor, denoted $/Wh. This cost factor may be detected and recorded when the vehicle is charging based on the smart grid signal, or may be directly input by the driver. This may also include a cost factor based on fuel consumed during operation of the PttB system (e.g., measuring fuel levels before and after PttB usage).

The driver may then add this cost to a column-by-column invoice for the project that the driver will provide to their customer or hiring party and allow the driver to accurately interpret the energy costs incurred during the project.

As a non-limiting example, the contractor contracts with the customer for the project. During this work, the contractor uses $50 lumber and $10 nails. Tracking power usage of the contractor's PttB system. At the end of the project, the contractor ends the PttB work and is informed that it has used $5 of energy based on having used 20kWh from the PttB system, at a cost of $ 0.20/kWh. This $5 may be added to the final total cost of the project along with materials and labor. The controller of the vehicle may complete the file initiated at the start of the job. This ensures not only that customers can be provided with a clear and fair estimate of project costs, but also that contractors can recoup the costs of energy they use and have previously paid for when they charge their vehicles.

In the case of a larger project that may require several days to complete rather than ending a given project file at the end of the day, the driver may pause the project at the end of the day and resume the project the next day it returns to work on the project. If a user engages in several projects at different locations over a period of time, multiple files may be stored on the vehicle. In this way, the total energy cost for a given project may be accurately invoiced, even over extended periods of days or weeks.

Illustrative embodiments

Turning now to the drawings, FIG. 1 shows an illustrative architecture 100 in which the techniques and structures of the present disclosure may be implemented. The illustrative architecture 100 may include a vehicle 102, a PttB system 104, a controller 106, a Human Machine Interface (HMI)108, a service provider 110, and a network 112.

The network 112 may include any one or combination of a number of different types of networks, such as a wired network, the internet, a wireless network, and other private and/or public networks. In some cases, the network 112 may include cellular, Wi-Fi, or Wi-Fi direct.

Generally, the vehicle 102 may include a truck that includes the PttB system 104, but other vehicle types may also include the PttB system. In some embodiments, the PttB system 104 includes one or more ports 114. These ports 114 may vary in configuration, but may include Universal Serial Bus (USB) ports, 110 volt ports, 220 volt ports, or any other port configuration desired by a user. One or more devices 116 that require electrical power may be connected to the ports 114 of the PttB system 104. It will be appreciated that the PttB system 104 may deliver electrical power from a power source 118 of the vehicle 102. The power source 118 may include a battery dedicated to the PttB system 104, or a battery typically used by other components of the vehicle 102.

The PttB system 104 may be coupled to a controller 106. In general, as will be discussed in greater detail herein, the controller 106 may be configured to track usage of the PttB system 104 and provide other PttB system functions, such as automatic PttB system control.

In some embodiments, the controller 106 may include a processor 120 and a memory 122. The memory 122 stores instructions that are executed by the processor 120 to perform aspects of the PttB system tracking and/or control disclosed herein. When referring to operations performed by the controller 106, it will be understood that this includes the processor 120 executing instructions.

The controller 106 may include any controller within the vehicle 102. For example, controller 106 may be the same controller used to control the functions of HMI 108. The controller 106 may be a dedicated controller integrated into the PttB system 104. In another embodiment, the controller 106 may include a controller positioned in any portion of the vehicle 102. In yet another embodiment, the controller 106 may comprise a mobile device of the user, such as the mobile device 124. In general, the mobile device 124 may install and execute an application that receives PttB data from the controller 106 (or service provider 110 in some embodiments). The tracking, analysis, and invoicing features disclosed herein may occur on the mobile device 124. It will be appreciated that the PttB system functions disclosed herein relating to the tracking, invoicing and control of the PttB system may be performed entirely at the vehicle level, entirely at the service provider level, at the mobile device level, or cooperatively between any of these components.

In some embodiments, the power usage of the PttB system 104 may be tracked and reported based on the controller 106 receiving a signal indicative of the power output by the PttB system 104. For example, when a user plugs a device into the PttB system 104 and draws power, the controller 106 may sense this power draw through the PttB system 104 and begin tracking power usage. As described above, sensing the use of the PttB system 104 may result in the creation of a new file, such as a log file, to store the usage parameters of the PttB system 104. Instead of using files, the usage parameters of the PttB system 104 may be transmitted directly to the mobile device 124 and/or the service provider 110.

In general, the usage parameters of the PttB system 104 may include power draw/consumption/usage/output as determined during a usage period. The usage period may include a single power draw event or multiple power events that are spread out over a time range from when the PttB system 104 is first activated until a termination event. As will be discussed in greater detail herein, the termination event may include a user deactivating a logging feature provided through HMI 108. The usage period may also include tracking usage of the PttB system 104 from a point in time when the recording feature is activated, such as a button press, until a second point in time when the same (or a different) button is pressed to deactivate the recording feature.

In general, the controller 106 may track usage parameters of the PttB system 104 and store the usage parameters in the memory 122. The usage parameters may include the power output of the PttB system 104 in terms of raw power data, average values, accumulated values, etc. In some embodiments, the controller 106 may identify location information of the vehicle 102. The location information may include, for example, Global Positioning System (GPS) data obtained from a connected vehicle system, such as a navigation system (not shown). These position data may be included in the PttB system data (e.g., usage parameters) tracked by the controller 106. Thus, the controller 106 may be configured to identify the location information of the vehicle 102 and include the location information in the message. In one embodiment, location information may be added to the invoice.

In some embodiments, the PttB system data tracked/recorded by controller 106 may be provided as messages displayable through HMI 108. In some cases, the message may be provided to the mobile device 124. Example messages may include calculations for power consumption/usage as described above. For example, a measure of power usage of the PttB system 104 may be captured in kWh. In some embodiments, kWh may be converted to a monetary value. In other embodiments, the message may include raw power usage data. In various embodiments, the message may include the monetary value of the raw power usage data, or both. The message may include data displayed on HMI 108. In other embodiments, the message may include an invoice automatically populated with the monetary value of the raw power usage data, or both. Some embodiments include providing an invoice template through HMI 108 to allow a user of vehicle 102 to track job site events. The worksite event may include the monetary value of the usage parameters of the PttB system 104, as well as row entries for other billable items such as hours, building materials, etc. In general, the message may include an invoice containing an invoicing amount for the usage parameters.

The invoicing amount may correspond to a currency conversion from a usage parameter to a monetary value. As described above, the controller 106 may convert the usage parameters of the PttB system 104 to monetary values by obtaining and applying an energy cost factor to the usage parameters. The energy cost factor may be obtained by the controller 106 based on the most recent charging event. For example, the vehicle 102 has recently been recharged at a cost of $ 1.50/kWh. In another embodiment, if the vehicle 102 uses an internal combustion engine to charge a battery used by the PttB system 104, the controller 106 may calculate a monetary value based on the fuel consumption and the current fuel cost. In the case where the vehicle 102 uses hybrid power, the controller 106 may calculate a monetary value from an accumulation of both electrical power usage and fuel consumption.

According to some embodiments, once the invoices are created, they may be transmitted to the service provider 110 for retention. In various instances, the service provider 110 may comprise a work unit or an employer of the user of the vehicle 102. Additionally, while the invoicing features disclosed herein have been discussed as being performed on a vehicle level, the invoicing features may alternatively be created at the service provider 110.

In various embodiments, the controller 106 may cause an invoice template to be provided by the HMI 108 of the vehicle, receive an invoicing item using the invoice template, and populate the invoice with the invoicing item and the invoicing amount.

According to some embodiments, the PttB system 104 usage parameters may be used to automate control of the PttB system 104. In various embodiments, the controller 164 may apply the power constraint parameters to adjust the PttB system 104. In one embodiment, the power constraint parameter may include a threshold or limit related to the amount of accumulated power that may be output by the PttB system 104 over a period of time or at each location. For example, a user may limit the total power output of the PttB system 104 to prevent excessive or excessive usage of the PttB system 104. In one example, an employer may limit the total power output of the PttB system 104 over an eight hour period to prevent unauthorized or excessive use by a user of the vehicle 102. An employer may desire to reduce the likelihood that a user of the vehicle will use the PttB system 104 to power a device such as a radio or television. These costs may be inadvertently transferred to the hiring party's customers through invoices as disclosed herein as an excess charge for electricity usage. Thus, in some cases, it may be desirable to limit the total power output of the PttB system 104. Such limits may be referred to as power constraint parameters. In various embodiments, the total power output of the PttB system 104 may be based on a predetermined agreement between the employer and the customer. The total power output of the PttB system 104 may be limited based on historical usage parameters of the PttB system 104 determined over time. When the power output of the PttB system 104 meets or exceeds this limit, the controller 106 may automatically disable the PttB system 104 if the applied power constraint parameter has been exceeded. The controller 106 may also allow the PttB system 104 to be reactivated upon receipt of an override command. For example, the controller 106 may be programmed to receive an override command that allows a user to override after a deactivation event. In one example, a user may obtain an override command, such as a sequence of numbers from their employer. The numerical sequence may be generated by the controller 106 upon request by an employer (through administrator functions), or through the use of the service provider 110. For example, an employer may activate an override command process at the service provider 110. The service provider 110 may generate and transmit an override command to the controller 106 and the user's mobile device 124. The user may enter an override command into HMI 108 and reactivate PttB system 104. In other embodiments, an override command may be transmitted to the controller 106, and the controller 106 may automatically reactivate the PttB system 104 in response.

Fig. 2 is a flow chart of an example method of the present disclosure. The method comprises a step 202 of determining an actuation of the tank power supply system of the vehicle. This may include sensing that power is being output from the PttB system. In another embodiment, this may include determining a first selection of a recording feature that activates recording of a usage parameter for the power supply system to the cabinet. Activation of the recording feature may include selection of a physical or virtual button on the vehicle HMI. For example, a GUI provided on the HMI can include a virtual button labeled "begin recording".

Next, the method may include a step 204 of determining a usage parameter of the vehicle for powering the tank during a usage period extending from the actuation to the termination event. The usage period may have any duration. The termination event may include expiration of a usage period or a specific termination effected using the second selection of the recording feature described above. Termination of the recording feature may include selection of a physical or virtual button on the vehicle HMI. For example, a GUI provided on the HMI can include a virtual button labeled "stop recording".

Next, the method may comprise a step 206 of generating a message comprising information indicating the usage parameter. The message may include a graphical display of the usage parameters in the form of raw data or graphics. Next, the method can include a step 208 of transmitting the message to a recipient. For example, the message may include a GUI or an invoice. Thus, the transmission may include displaying a GUI on the HMI of the vehicle, or transmitting the invoice to the service provider. In various embodiments, the usage parameters may also be stored locally at the vehicle 102 for future analysis.

Fig. 3 is a flow chart of another example method of the present disclosure. The method may include a step 302 of receiving an actuation of a recording feature provided on a human-machine interface of a vehicle. Again, as one example, this may include the user activating a button provided on the HMI of the vehicle. Alternatively, physical or virtual switches or buttons may be provided on the PttB system. In one example, the PttB system is positioned in the truck cargo bed of a truck. The user may activate the recording feature using a mechanism provided on the PttB system in the truck cargo bed of the truck.

Next, the method includes a step 304 of determining a usage parameter of the vehicle for powering the tank during a usage period extending from the actuation to the termination event. In various embodiments, the method includes step 306: and displaying the invoice template to a user through a human-computer interface. In various embodiments, the method includes a step 306 of receiving an invoicing item from an invoice template, and a step 308 of converting the usage parameter to an invoicing amount. The method may also include a step 310 of generating an invoice including the invoicing item and the invoicing amount.

FIG. 4 shows an example graphical user interface (GUI 400) displayed on HMI 402 of a vehicle. The GUI400 includes a graph 404 of usage parameters of the PttB system. Graph 404 plots the power output of the PttB system over time. Again, the beginning and ending portions of the graph may correspond to activation and deactivation of the recording feature as disclosed herein. For example, the GUI400 may include a first selection in the form of a button 406 and a second selection in the form of a button 408. In some embodiments, a single button may be used. GUI400 may also include a "generate invoice" button 410 that causes an invoice to be created from the collected usage parameters. In various embodiments, GUI400 may include a "pause" button 412 that allows the user to pause the collection of usage parameters. As described above, this feature allows the user to collect usage parameters over several days. The GUI400 may also include a "select customer or work" button 414 that allows the user to select which customer/work to link to the collected usage parameters. When button 414 is selected, a selectable list of customers or jobs may be displayed. When selected, the customer/job may be associated with the collected usage parameters. The usage parameter data 416 may be displayed proximate to or adjacent to the graph 404.

FIG. 5 shows an example graphical user interface (GUI 500) displayed on a HMI 502 of a vehicle. GUI 500 may include an invoice template 504. The invoice template may include a pre-populated field 506 that includes an invoicing amount for the usage parameters. The invoice template may also have an additional field 508 for receiving invoicing items. For example, the user may enter a material cost into one of the additional fields 508. For example, a user may enter invoice items using a virtual keyboard or voice controls made available through the HMI. The controller may then populate the invoice template 504 with the inputs. If the user approves the invoice, the filled invoice may be transmitted to the customer, the employer, and/or the service provider. Invoices may also be stored locally for future use. Customer data may be added in a field located anywhere on the invoice template 504.

In the foregoing disclosure, reference has been made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments in which the disclosure may be practiced. It is to be understood that other implementations may be utilized and structural changes may be made without departing from the scope of the present disclosure. References in the specification to "one embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it will be recognized by one skilled in the art that such feature, structure, or characteristic may be used in connection with other embodiments whether or not explicitly described.

Implementations of the systems, apparatus, devices, and methods disclosed herein may include or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory as discussed herein. Implementations within the scope of the present disclosure may also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media storing computer-executable instructions are computer storage media (devices). Computer-readable media carrying computer-executable instructions are transmission media. Thus, by way of example, and not limitation, implementations of the present disclosure can include at least two distinct computer-readable media: computer storage media (devices) and transmission media.

Computer storage media (devices) includes RAM, ROM, EEPROM, CD-ROM, Solid State Drives (SSDs) (e.g., based on RAM), flash memory, Phase Change Memory (PCM), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.

Implementations of the apparatus, systems, and methods disclosed herein may communicate over a computer network. A "network" is defined as one or more data links that enable the transfer of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or any combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmission media can include a network and/or data links which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.

Computer-executable instructions comprise instructions and data which, when executed at a processor, cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions, for example. The computer-executable instructions may be, for example, binary instructions, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.

Those skilled in the art will appreciate that the disclosure may be practiced in network computing environments with many types of computer system configurations, including internal vehicle computers, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablet computers, pagers, routers, switches, various storage devices, and the like. The present disclosure may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by any combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.

Additionally, where appropriate, the functions described herein may be performed in one or more of the following: hardware, software, firmware, digital components, or analog components. For example, one or more Application Specific Integrated Circuits (ASICs) may be programmed to implement one or more of the systems and programs described herein. Certain terms are used throughout the description and claims to refer to particular system components. As one skilled in the art will appreciate, components may be referred to by different names. This document does not intend to distinguish between components that differ in name but not function.

It should be noted that the sensor embodiments discussed above may include computer hardware, software, firmware, or any combination thereof to perform at least a portion of their functions. For example, the sensors may include computer code configured to be executed in one or more processors, and may include hardware logic/circuitry controlled by the computer code. These example devices are provided herein for illustrative purposes and are not intended to be limiting. As known to those skilled in the relevant art, embodiments of the present disclosure may be implemented in other types of devices.

At least some embodiments of the present disclosure have been directed to computer program products that include such logic (e.g., in the form of software) stored on any computer usable medium. Such software, when executed in one or more data processing devices, causes the devices to operate as described herein.

While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the disclosure. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims appended hereto and their equivalents. The foregoing description has been presented for purposes of illustration and description. The foregoing description is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. Further, it should be noted that any or all of the aforementioned alternative implementations may be used in any combination desired to form additional hybrid implementations of the present disclosure. For example, any function described with respect to a particular device or component may be performed by another device or component. In addition, although particular device features have been described, embodiments of the present disclosure may be directed to many other device features. Additionally, although embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the embodiments. Conditional language such as "can," "may," "might," or "may" is generally intended to convey that certain embodiments may include certain features, elements, and/or steps, while other embodiments may not include certain features, elements, and/or steps, unless specifically stated otherwise, or otherwise understood as such in the context of use. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments.

According to one embodiment, the processor is configured to identify location information of the vehicle and include the location information in the message.

According to one embodiment, the processor is configured to determine a first selection of a recording feature that activates recording of a usage parameter during the time period and a second selection of the recording feature that terminates recording of the usage parameter.

According to one embodiment, the message comprises an invoice comprising an invoicing amount for the usage parameter, and wherein the invoicing amount is determined by multiplying power usage by an energy cost factor, further wherein the energy cost factor is determined during charging of the vehicle.

According to one embodiment, the processor is configured to: providing an invoice template through a human-computer interface of the vehicle; receiving an invoice item using the invoice template; and populating the invoice with the invoicing item and the invoicing amount.

According to one embodiment, the processor is configured to: applying power constraint parameters to regulate a system supplying power to the tank; automatically disabling the power supply system to the tank when the applied power constraint parameter has been exceeded; and receiving an override command to reactivate the tank power supply system after the automatic deactivation of the tank power supply system.