Automatic tracking of resource usage by vehicles

A unified system integrates resource management operators using a multi-resource interface provider and contract certificate to efficiently track and pay for vehicle resources like electricity and road usage, addressing inefficiencies in conventional systems.

JP2024166157APending Publication Date: 2024-11-28INTEGRITY SECURITY SERVICES LLC
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
JP2024079823
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-17
Filing Date
2024-05-16
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

Conventional systems for tracking vehicle resource consumption require separate and inefficient infrastructure for each type of resource, necessitating multiple interfaces and logins, which is costly and cumbersome for users.

Method used

A unified system that integrates multiple resource management operators through a multi-resource interface provider, using a contract certificate to consolidate and track various resources like electricity and road usage in a single account, enabling secure and efficient tracking and payment.

Benefits of technology

The system allows for seamless tracking and payment of multiple vehicle resources using a single interface, reducing costs, bandwidth, and security risks while enhancing user convenience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024166157000001_ABST
    Figure 2024166157000001_ABST
Patent Text Reader

Abstract

To provide systems for tracking the usage of multiple resources by a vehicle.SOLUTION: A system 100 includes: a first resource management operator (RMO) 120 that tracks the usage of electricity as a first resource by a vehicle 110 and that generates a first resource usage record that includes information from a certificate; a second RMO that tracks the road usage as the usage of a second resource by the vehicle; and a multi-resource interface provider (MRIP) 130 that provides a communication channel between the first RMO and the second RMO. The MRIP is configured to: obtain the first resource usage record; generate therefrom a revised first resource usage record including certificate information; and provide the created record to the second RMO. The second RMO generates a multi-resource usage record using combined data from the created record and the tracked data about the usage of the second resource.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application claims the benefit of and priority to U.S. Provisional Application No. 63 / 502,837, filed May 17, 2023, which is incorporated by reference herein in its entirety.

[0002] The present invention relates to systems, devices, computer applications, and methods for automatically tracking resource consumption activity associated with a vehicle. [Background technology]

[0003] Vehicles, such as cars, trucks, airplanes (including unmanned aerial vehicles), ships, etc., consume various resources, such as gasoline, electricity, oil, road usage (e.g., time and / or distance spent on a particular road, such as a toll road, which may reflect, among other things, the consumption of traffic capacity and roadway life resources), parking space, storage space, communication resources, etc. For example, an electric vehicle consumes electricity when charging, such as at a public charging station. In another example, an electric vehicle also consumes toll road resources when traveling on a toll road.

[0004] Current conventional systems and techniques use separate and distinct infrastructures, devices, and processes to track resources consumed by vehicles. In some systems, resource tracking information may be used in compensating resource suppliers. Such conventional systems and techniques are inefficient and expensive because they each require their own infrastructure, such as servers, communication channels, on-board transponders or similar devices (e.g., electronic toll collection devices such as EZPass® transponders), websites, mobile applications, etc., and much of the infrastructure for a given resource is duplicated with the infrastructure used for another resource. Conventional resource usage tracking systems and techniques are also disadvantageous and inefficient for users, because they require users to learn and utilize multiple interfaces, logins, devices, etc. for each different type of vehicle-related resource.

[0005] It would therefore be desirable to provide improved systems, methods, and techniques for safely and easily tracking multiple resources consumed by a vehicle in a single, unified manner.The various embodiments described herein address the above and other shortcomings associated with conventional resource usage tracking systems and techniques. Summary of the Invention

[0006] This summary is intended to merely introduce a simplified overview of some aspects of one or more implementations of the present disclosure. Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. This summary is not an extensive overview and is not intended to identify key or critical elements of the present teachings or to delineate the scope of the present disclosure. Rather, its purpose is merely to present one or more concepts in a simplified form as a prelude to the detailed description that follows.

[0007] In one aspect, a system for tracking usage of multiple resources by vehicles associated with a contract certificate is disclosed. The system includes a first resource management operator that tracks usage of a first resource (e.g., electricity) by the vehicles associated with the contract certificate and generates a first resource usage record, the first resource usage record including information from the contract certificate. The system also includes a second resource management operator that tracks usage of a second resource (e.g., road usage) by the vehicles associated with the contract certificate. The system further includes a multi-resource interface provider operatively connected with the first resource management operator and the second resource management operator. The multi-resource interface provider performs operations including obtaining the first resource usage record from the first resource management operator, generating a revised first resource usage record from data of the first resource usage record, the revised first resource usage record being in a format usable by the second resource management operator, the revised first resource usage record including information from the contract certificate, and providing the revised first resource usage record to the second resource management operator. The second resource management operator performs operations including identifying data regarding usage of the second resource (e.g., road usage) by the vehicle based on information from the contract certificate, combining data from the revised first resource usage record with the identified data regarding usage of the second resource by the vehicle associated with the contract certificate, generating a multi-resource usage record using the combined data, and providing information from the multi-resource usage record to a user associated with the vehicle.

[0008] In another aspect of the system, the multi-resource interface provider performs operations including creating a contract certificate and providing the contract certificate to a second resource management operator. The second resource management operator also performs operations including providing the contract certificate to the vehicle. In an additional sub-aspect, the second resource management operator performs operations including associating the contract certificate with a transponder associated with the vehicle.

[0009] In another aspect of the system, the contract certificate is stored by the vehicle.

[0010] In another aspect of the system, the contract certificate is stored by a transponder associated with the vehicle.

[0011] In two other aspects of the system, the first resource is at least one of a power resource, a road use resource, or a Department of Transportation (DOT) resource, and / or the second resource is at least one of a power resource, a road use resource, or a Department of Transportation (DOT) resource.

[0012] In another aspect of the system, the operation for generating a revised first resource usage record from data of the first resource usage record includes including data from the contract certificate in the revised first resource usage record.

[0013] In another aspect of the system, generating the revised first resource usage record from data in the first resource usage record includes converting data from the first resource usage record into a format usable by the second resource management operator.

[0014] In a second aspect, a system is disclosed for managing data from a first resource management operator that tracks usage of a first resource (e.g., electricity) by vehicles associated with a contract certificate. The system includes a second resource management operator that tracks usage of a second resource (e.g., road usage) by vehicles associated with the contract certificate, and a multi-resource interface provider operatively connected to the first resource management operator and the second resource management operator. The multi-resource interface provider performs operations including obtaining a first resource usage record from the first resource management operator, the first resource usage record including information from the contract certificate, generating a revised first resource usage record from data of the first resource usage record, the revised first resource usage record being in a format usable by the second resource management operator and including the information from the contract certificate, and providing the revised first resource usage record to the second resource management operator. The second resource management operator performs operations including identifying data regarding usage of the second resource (e.g., road usage) by the vehicle based on information from the contract certificate, combining data from the revised first resource usage record (e.g., electricity) with the identified data regarding usage of the second resource by the vehicle associated with the contract certificate, generating a multi-resource usage record using the combined data, and providing information from the multi-resource usage record to a user associated with the vehicle.

[0015] In another aspect of the system, the multi-resource interface provider performs operations including creating a contract certificate and providing the contract certificate to a second resource management operator. The second resource management operator also performs operations including providing the contract certificate to the vehicle. In an additional sub-aspect, the second resource management operator performs operations including associating the contract certificate with a transponder associated with the vehicle.

[0016] In another aspect of the system, the contract certificate is stored by the vehicle.

[0017] In another aspect of the system, the contract certificate is stored by a transponder associated with the vehicle.

[0018] In two other aspects of the system, the first resource is at least one of a power resource, a road use resource, or a Department of Transportation (DOT) resource, and / or the second resource is at least one of a power resource, a road use resource, or a Department of Transportation (DOT) resource.

[0019] In another aspect of the system, the operation for generating a revised first resource usage record from data of the first resource usage record includes including data from the contract certificate in the revised first resource usage record.

[0020] In another aspect of the system, generating the revised first resource usage record from data in the first resource usage record includes converting data from the first resource usage record into a format usable by the second resource management operator.

[0021] It is contemplated that combinations of the above elements with those herein are possible, unless otherwise inconsistent. [Brief description of the drawings]

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain its principles.

[0023] [Figure 1] 1 is a block diagram illustrating an example system for tracking vehicle-related resource usage consistent with an embodiment of the present invention.

[0024] [Diagram 2] 4A-4C illustrate information from an example multi-resource usage record, consistent with embodiments of the present invention.

[0025] [Diagram 3] FIG. 1 is a block diagram of an example computing system that may be used to host and implement systems, functions, operations and methods consistent with implementations of the present invention.

[0026] [Figure 4] 5 is a flowchart illustrating an example process for generating revised resource usage records for use in a multi-resource tracking record, consistent with embodiments of the present invention.

[0027] [Diagram 5] 5 is a flowchart illustrating an example process for generating a multi-resource tracking record consistent with embodiments of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0028] Reference will now be made in detail to the present embodiments of the invention, examples of which are illustrated in the accompanying drawings.

[0029] Various embodiments and implementations consistent with the present invention provide systems, components, methods, and computer program products for automated tracking of two or more resource consumption activities (e.g., charging, gasoline usage, road usage (e.g., as measured by road tolls), etc.) performed by a vehicle (gas or self-propelled electric vehicle, unmanned aerial vehicle, etc.) between multiple parties, such as resource suppliers (e.g., gas station operators, charging station operators, toll road operators, etc.) and resource users (e.g., electric vehicle owners, gasoline car owners). Various embodiments may use verified credentials (e.g., digital certificates, etc.) to implement secure resource usage tracking functionality. In various embodiments, tracking functionality for resource consumption activities may include functionality for, among other things, collecting, calculating, storing, and / or communicating resource usage, and optionally for payment and settlement of consumed resources.

[0030] FIG. 1 is a block diagram illustrating an example of a system 100 for tracking vehicle-related resource usage consistent with an embodiment of the present invention. It should be noted that the labels "first," "second," and "third" used in FIG. 1 and elsewhere herein with respect to resource management operators are for purposes of explanation and distinction, and are not intended to indicate any particular order or priority or functionality. Focusing first on the communication path illustrated by the solid arrow labeled 500, which represents an embodiment of modifying and technically improving the infrastructure (e.g., computer) of a resource management operator (RMO) (such as the second resource management operator 140) to add new functionality described herein, creating a new Multi-Resource Interface Provider (MRIP) 130, which is a new entity with new technical functionality and may be embodied as a computing system (e.g., a server computer) configured to perform the operations and functions described herein. In some embodiments, an RMO such as road usage RMO 140 may be a technically modified and improved toll management provider, similar to EZPass® or FasTrak®, where the improvement may include functionality and devices to manage and track electricity usage (e.g., charging) by electric vehicles 110 in addition to toll road usage. The improvement may also include new interface capabilities, such as new application programming interfaces (APIs) that enable a second RMO 140 to receive and process data (e.g., in the form of revised resource usage records 145) reflecting the use of a different resource (e.g., electricity) by the same particular vehicle 110.

[0031] In this example, a user or owner 105 of an electric vehicle (EV) 110 sets up an account for toll road usage tracking with an improved second resource management operator 140 and receives a transponder 148 installed on the EV 110. The owner 105 may also request charging power usage tracking and obtain a contract certificate 146 (e.g., from or through the improved road usage RMO 140). In various implementations, the contract certificate 146 is associated, linked, bound, or cryptographically bound to the transponder 148. In various implementations, the system 100 can use the contract certificate 146 and / or information therein to provide a common link, identifier, key, index, etc. between the various RMOs (e.g., 120, 140, 150) and the MRIP 130, such that the RMOs and / or MRIP 130 can consolidate, manage, track, and otherwise process resource usage data associated with a particular vehicle 110 and / or transponder 148.

[0032] In various embodiments, the contract certificate 146 is a digital certificate that the road usage RMO 140 obtains from the multi-resource interface provider 130. In some embodiments, the multi-resource interface provider 130 may create the contract certificate 146. In some other embodiments, the multi-resource interface provider 130 may request and obtain the contract certificate 146 from a security certificate management system (SCMS) (not shown).

[0033] In various embodiments, the contract certificate 146 may be associated with the transponder 148 and / or the EV 110 when transferred from the second resource management operator 140 to the EV owner 105. In some embodiments, the contract certificate 146 may be uniquely or solely associated with the transponder 148 and / or the EV 100, and thus information from the contract certificate 146 (e.g., serial number, unique identifier string, etc.) may be used to unambiguously identify the transponder 148 and / or the EV 110 and unambiguously identify data (e.g., resource usage data) attributable to the transponder 148 and / or the EV 110. In some embodiments, the contract certificate 146 may be installed or stored on the EV and used by (e.g., communicated from) the EV 110. In some embodiments, the owner 105 may install the contract certificate 146. In additional or alternative embodiments, the contract certificate 146 may be installed or stored on the transponder 148 and used (e.g., communicated from) the transponder 148.

[0034] In the example of FIG. 1, when the EV 110 is driven through a road usage monitoring station, such as a toll booth (not shown) when entering or exiting a road, the transponder 148 communicates with the monitoring station (e.g., toll booth), which in turn can communicate road usage information to the computer and other infrastructure of the road usage (second) RMO 140. In various implementations, the road usage information includes date information, time information, transponder (148) identification information, contract certificate (146) information, road usage information (e.g., distance driven), and / or location information. In various embodiments, the road usage (second) RMO 140 tracks (e.g., collects, processes, records, and / or stores, etc.) the usage of road resources by the EV 110 (and / or the user 105), and may optionally calculate fees applicable to the distance of road used, communicate road resource usage, etc. In some embodiments, the second RMO 140 may internally generate, create, provide, communicate, and / or store road resource usage records (not shown in the example of FIG. 1). In various implementations, the road resource usage record includes information from the EV 110, the transponder 148, and / or the certificate 146 that enables identification of the owner 105. In various implementations, the road resource usage record may be similar to the power resource usage records 117, 125 described below. In some embodiments, the road resource usage record may aggregate or consolidate road usage data from several different sources, for example, from several monitoring stations or toll booths.

[0035] Somewhat similarly, when the EV 110 is charged with electricity from the charging station 115, the EV 110 (or in some embodiments the transponder 148) communicates the contract certificate 146 (and / or information therefrom) to or through the computer and other infrastructure of the charging station 115 and / or the first resource management operator (RMO) 120, which in this example is a charging station operator (CSO), which may also be referred to as a charge point operator (CPO). In an embodiment, the information from the contract certificate 146 informs and provides secure authorization to the charging station 115 and the first RMO 120 regarding the identity of the vehicle 110, the transponder 148, and / or the owner 105 consuming or using power from the charging station 115. In some embodiments, the information is about the amount of electricity used as well as the amount of electricity consumed. Optionally, the information from the contract certificate 146 can also identify a previously established account of the owner 105 that tracks (e.g., processes, records, stores, etc.) power resource usage, etc., and optionally a monetary charge for the electricity.

[0036] In the illustrated example, charging station 115 may create a power resource usage record 117 that is communicated to charging station RMO 120. In various embodiments, resource usage record 117 includes data representing the amount of electricity used to charge EV 110, information from certificate 146 associated with (e.g., identifying) EV 110, transponder 148, and / or owner 105, and / or optionally a monetary charge for the electricity used. The information from certificate 146 may include information (e.g., ID number, etc.) that identifies or uniquely identifies EV 110, transponder 148, and / or owner 104. In some embodiments, communication between charging station RMO 120 and MRIP 130 may follow an EV roaming charging protocol, such as the Open Charge Point Interface (OCPI) protocol, Open Exchange Protocol (OICP), OCHP, eMIP, etc.

[0037] In various embodiments, the charging station RMO 120 can track (e.g., collect, process, record, and / or store, etc.) the EV 110's (and / or user 105's) usage of electrical resources, and optionally calculate applicable charges for the amount of electricity used, communicate the electrical usage, etc. As shown in the example of FIG. 1 , the first RMO 120 can generate, create, provide, and / or communicate an electrical resource usage record 125 for the MRIP 130. In various implementations, the resource usage record 125 includes information from the EV 110, the transponder 148, and / or the certificate 146 that enables identification of the owner 105. In various implementations, the resource usage record 125 can be similar to or the same as the resource usage record 117. In some embodiments, the resource usage record 125 may aggregate or consolidate data from several different EVs 110 and / or from several different charging stations 115 and / or from several different resource usage records 117 into a single resource usage record 125 that includes power resource usage information from multiple sources. In some embodiments, communication between the charging stations RMO 120 and the MRIP 130 may follow an EV roaming charging protocol such as the Open Charge Point Interface (OCPI) protocol, the Open Exchange Protocol (OICP), OCHP, eMIP, or the like.

[0038] The novel multi-resource interface provider 130 can function to process, route, convert, transform and forward information between two or more different resource operators (e.g., the second RMO 140 and the first RMO 120 and the third RMO 150) that are technically unable to communicate directly with each other, such that the usage of two or more resources (e.g., toll roads and electricity) can be consolidated and tracked in a single account, which can be maintained by one of the resource operators, e.g., the road usage RMO 140 in the example of FIG. 1. The MRIP 130 and / or the improved road usage RMO 140 embody new devices and novel technical features that enable communication, tracking, management and optional payment for the usage of multiple resources associated with the vehicle 110. They also provide novel technical means for the user 105 to view, track, manage and optionally pay for the usage of multiple resources associated with the vehicle 110 using a single device, a single interface and a single account hosted, e.g., at a single website of the second resource management operator 140 or the MRIP 130. This new system offers several technical advantages over conventional systems that require a user to use several different devices (e.g., first RMO 140 and second RMO 120) to view, track, manage, and optionally pay for the usage of multiple resources (e.g., road usage resources and power resources) associated with a vehicle 110. These technical advantages include using less memory (one account to store resource usage data instead of two or more), using less bandwidth (one login / one communication session instead of two or more), using fewer devices (one operator device to manage multiple resources instead of two or more), using less time (one login / one communication session instead of two or more), being more secure (one account / one login / one communication session instead of two or more), etc.

[0039] As shown in the example of FIG. 1, the MRIP 130 can receive or otherwise obtain a resource usage record 125 from the charging station RMO 120, which can include, among other things, information describing the amount of electrical resources used by the EV 110 for charging, and information from a certificate 146 associated with the EV 110.

[0040] MRIP 130 may process resource usage records 125 and use information therefrom to generate or create revised resource usage records 145 in a format usable by the second RMO 140, which MRIP 130 provides to (e.g., transmits, routes, or makes accessible to) the second RMO 140. For example, MRIP 125 may reformat, convert, transform, merge, or otherwise process information from resource usage records 125 to generate a different revised resource usage record 145 configured as expected by and / or compatible with the second RMO 140. For example, MRIP 130 may generate revised resource usage records 145 that are in a format required by an interface, such as an application programming interface (API), of the second RMO 140. In various embodiments, revised resource usage record 145 includes at least properly formatted information describing the amount of power resources used by EV 110 and properly formatted information from a contract certificate 146 associated with EV 110. In some implementations, revised resource usage record 145 may include all or a portion of the information found in resource usage records 117 and / or 125.

[0041] The road usage (second) RMO 140 may reformat, convert, transform, merge, or otherwise process the revised resource usage record 145 and use information therefrom in combination with information from the road usage (second) RMO 140 regarding road resource usage by the same vehicle 110, transponder 148, and / or owner 105 associated with the same contract certificate 146 to generate or create a multi-resource usage record 142. For example, the road usage RMO 140 may use information from the contract certificate 146 associated with the EV 110 (present in the revised resource usage record 145 received from the MRIP 130) to identify stored road resource usage data for an otherwise associated vehicle 110 that corresponds to the contract certificate 146. More specifically, with respect to the example of FIG. 1 , the road usage (second) RMO 140 can use information from the contract certificate 146 to identify the correct user account and the correct toll road resource utilization information stored therein that corresponds to the same user's power resource utilization information from the revised resource usage record 145.

[0042] The road usage RMO 140 can then combine the power resource usage information from the revised resource usage record 145 (e.g., obtained and tracked by the first RMO 120) with road resource usage information obtained from monitoring stations such as toll booths (not shown; EZPass® toll booths are a well-known example) to generate a single multi-resource usage record 142. The road usage RMO 140 can then provide the multi-resource usage record 142 to the owner / user 105 associated with the vehicle 110 and contract certificate 146, such as by displaying information from the multi-resource usage record 142 on a website, printing it, emailing it to the owner / user 105, etc. An example of at least some of the information included in the multi-resource usage record 142 is shown in FIG. 2.

[0043] As illustrated in the embodiment of FIG. 1, the system 100 automatically tracks two or more of the resource consumption activities (e.g., toll road resource consumption and electricity consumption) associated with a vehicle (e.g., EV 110) and the novel multi-resource usage record 142 stores and documents those resource consumption activities in a single source.

[0044] Some embodiments consistent with the example of FIG. 1 may also optionally include payments in exchange for various resource tracking services, devices, and / or digital assets, such as contract certificates 146. For example, the EV owner 105 may initially pay money to the second resource management operator 140 in exchange for a transponder 148 and / or contract certificate 146, e.g., when setting up a user account with the second resource management operator 140. The EV owner 105 may then periodically remit money to pay for resources and services used by the EV 110, such as road usage (e.g., as measured by tolls) and charging. In some such embodiments, the multi-resource usage record 142 may include information regarding the amount of debt for each resource.

[0045] In some such embodiments, the second resource management operator 140 may distribute money (which may be a portion of the money received from the owner 105) to the appropriate entities to compensate them for the resources and services provided in the system 100. For example, the second RMO 140 may initially distribute money to the MRIP 130 upon user account setup in exchange for, among other things, the contract certificate 146. The second RMO 140 may also distribute money periodically to the toll road operator (not shown) and the MRIP 130 for ongoing services and resource usage. For example, a portion of the money provided to the MRIP 130 periodically may compensate the MRIP 130 for the services and infrastructure that provide links to resource providers such as the charging station RMO 120 and / or the charging station 115, and a portion may be used to pay for the charging power resources used by the EVs 110.

[0046] As described above, the MRIP 130 may periodically distribute money to the first RMO 120 to pay for the electricity and services used to charge the EVs 110. The money may be a portion of the money received from the second resource management operator 140.

[0047] Continuing to refer to FIG. 1 , focusing here on the communication path indicated by the dashed arrow labeled 600. This represents an embodiment that changes the infrastructure of a third resource management operator 150, in this example a Department of Transportation (DOT) RMO, to add new functionality as described herein, among other things. The Department of Transportation may be managed by a government agency, such as a state in the United States. The dashed lines are used to help distinguish between path 600 and path 500. In some embodiments, the DOT RMO 150 may be technically modified and improved to include functionality, digital assets, and devices (e.g., computers) that manage the tracking of electricity usage (e.g., charging) by the electric vehicle 110 in addition to tracking the use of state-provided resources, such as vehicle registration, driver license privileges, safety and emissions inspection resources and services, state road usage (e.g., road taxes), state infrastructure usage (e.g., vehicle property taxes), etc. In one such embodiment, a user or owner 105 of an electric vehicle (EV) 110 sets up an account associated with obtaining a driver's license 151 (or other state-provided resource such as registration of the EV 110) using the improved DOT RMO 150. The account can include a payment method such as a credit card on file. The owner 105 also chooses to automatically track his or her power resource usage along with his or her DOT resource usage via a DOT account, which is a new technical capability provided by the system 100. Upon setting up the account, the owner 105 receives the license 151 and the contract certificate 146 described above that enables resource usage tracking. In various such implementations, this contract certificate 146 is associated, linked, bound, or cryptographically bound to the license 151.

[0048] In some embodiments, the contract certificate 146 is a digital certificate that the DOT RMO 150 obtains from the MRIP 130 and then sends to the owner 105, as represented along the dashed communication path 600 at the top of FIG. 1. In other embodiments, the DOT RMO 150 may provide a link or the like to the owner 105 so that the owner can download or otherwise obtain the contract certificate 146 directly from the MRIP 130, as represented by the center left-right communication paths 600 of FIG. 1. In still other embodiments, the MRIP 130 is implemented as a "white label" backend to the DOT RMO 150's front-end website or other infrastructure, and the owner 105 interacts with, for example, a web page or the like that appears to be the DOT RMO 150's website, but is actually provided transparently by the MRIP 130, via the DOT RMO 150's website, or the like. In such an embodiment, from the user 105's perspective, the contract certificate 146 appears to originate from the DOT RMO 150, but is actually originated from the MRIP 130.

[0049] As mentioned above, in various embodiments, the agreement certificate 146 may be installed or stored on the EV and used by (eg, communicated from) the EV 110.

[0050] When the EV 110 charges electricity from the charging station 115, the EV communicates the contract certificate 146 (and / or information therefrom) to the computers and other infrastructure of the charging station 115 and / or the first RMO 120, and the charging power resource usage is obtained by the MRIP 130, e.g., via the first RMO 120, as described above. In some white label implementations, the first RMO 120 may actually submit resource usage records 125 to the DOT RMO 150, but the resource usage records 125 are processed by the MRIP 130, which serves as a backend to the DOT RMO 150.

[0051] In some embodiments, the MRIP 130 can generate or create a revised resource usage record 155 of the power resource usage and provide it to the DOT RMO 150. The DOT RMO 150 can then use information from the revised resource usage record 155 to create or update the multi-resource usage record 142, which is provided to or otherwise made accessible to the owner 105. For example, the DOT RMO 150 can combine the power resource usage information from the revised resource usage record 155 (e.g., if obtained and tracked by the MRIP 130) with the DOT resource usage information of the EV 110 (e.g., registration information, emissions information, license information, etc.) into a single multi-resource usage record 142, which may be displayed on a DOT website or printed and sent to the owner 105, as represented by the dashed communication path 600 at the top of FIG. 1. The improvements and new features of the third RMO 150 are similar to those of the second RMO 140, as previously described. In various implementations, there may be various types of resource management operators, for example, DOT (third) RMO 150 may be one particular instance of a resource management operator, road usage (second) RMO 140 (e.g., an improved EZPass® RMO) may be another particular instance of a resource management operator, and similarly, as discussed above, charging station RMO 120 may be another particular instance of a resource management operator.

[0052] In other embodiments, instead of creating a revised resource usage record 155 for power resource usage and providing it to the DOT RMO 150, the MRIP 130 may receive or obtain a resource usage record 155 including data regarding DOT resource usage from the DOT RMO 150 and use it to create a multi-resource usage record 142 that is provided or otherwise made accessible to the owner 105, as represented by the center dashed communication path in FIG. 1. In such an embodiment, the multi-resource usage record 142 provided to the owner 105 along the communication path 600 may include information regarding DOT resource usage, power resource usage, and roadway resource usage, or a combination of at least two of these. The same multi-resource usage record 142 may also include information from the contract certificate 146.

[0053] Similar to the embodiments described above in connection with solid communication path 500, some embodiments associated with dashed communication path 600 may also optionally include payment for resource usage and / or payment in exchange for various resource tracking services, devices, and / or digital assets. In some such embodiments, money received from owner 105 for resources used by vehicle 110 is distributed by MRIP 130 to other components of system 100. In other such embodiments, a portion of money received from owner 105 is distributed by DOT RMO 150 to MRIP 130, which further distributes a portion of money to other components of system 100. These distributions are similar to the distributions described in connection with solid communication path 500.

[0054] In various implementations, the road usage (second) RMO 140, the MRIP 130, the charging station (first) RMO 120, the DOT (third) RMO 150, and / or the charging station 115 may be implemented in part or in whole using one or more computing systems executing software or firmware instructions, such as a server (e.g., having at least one processor and associated memory and communication devices) or other computer. The computing system may be configured to implement the processes, operations, and functions described herein, for example, using instructions and communication hardware. In various implementations, the communication paths 500 and 600 may include one or more networks, which may be or may include digital networks (e.g., the Internet), cellular networks, wireless networks, and other networks.

[0055] Those skilled in the art will recognize that the components, connections, processes, data, operations, and implementation details shown and described in FIG. 1 are examples presented for brevity and clarity of description. This example is not intended to be limiting, and many implementations are possible, so other components, processes, implementation details, and variations can be used without departing from the principles of the invention. For example, while the system 100 is shown with the charging station RMO 120, other implementations may omit the charging station RMO 115, such that the charging station 120 interacts directly with the MRIP 130. In another example, the functions of the second resource management operator 140 and the MRIP 130 may be implemented combined with a single computing system, instead of two entities as shown. As yet another example, the vehicle 110 may be a gasoline vehicle, and the charging station 115 may be a gas station that functions and interacts with the system 100 in a manner similar to that described for the charging station 115, but for tracking and managing gasoline resources instead of electric resources. Other variations are possible.

[0056] 2 illustrates information 200 from an example multi-resource usage record 142, consistent with an embodiment of the present invention. In the example of FIG. 2, the information 200 is formatted in a manner that may be displayed, physically or electronically, on a web page (e.g., on a web page from the website of the first road usage RMO 140, DOT RMO 150, or MRIP 130 that is visible to the owner 105 after logging into their account) or in a report sent to the owner 105.

[0057] As shown in this example, the first left-most column indicates dates on which the EV 110, including the transponder 148 and certificate 146, used resources tracked by the system 100. The second column from the left indicates the resources used by the EV 110 on each date.

[0058] The third column indicates the identity of the transponder (e.g., transponder 148) that used the resource and / or the contract certificate (e.g., certificate 146) of the EV 110. The fourth column indicates the entity that provided the resource that was used.

[0059] The fifth column 220, "miles / kWh," indicates the amount of the resource used by the EV 110. Columns six through nine contain information detailing the date, time, and location where the EV 110 used the toll road resource. Column ten indicates the plaza or address of each toll or power resource transaction.

[0060] The eleventh column 250 “Amount” and the twelfth column 260 “Balance” are optional columns used in embodiments to track the amount charged for each resource transaction and the current monetary balance in the owner's 105 account.

[0061] For an example of a road resource usage transaction, see the third line 231 of information for March 6, 2023 from the multi-resource usage record shown in display 200 of FIG. 2. Line 231 tracks information about road resource usage, for example, by EV 110, and records that a transponder (e.g., 148) (reference 201) with identifier "36000A" used 6 miles of a Virginia Department of Transportation (reference 211) toll road (reference 221), specifically the Dars Toll Road (reference 241). While this example is for a toll road, other implementations may track usage of non-toll roads, for example, non-toll roads that have transponder readers located at their entrances and exits.

[0062] For an example of an electrical power resource usage transaction, see the fourth line 232 of information from the multi-resource usage record 142 shown in display 200 of FIG. 2 for March 7, 2023. Line 232 tracks information about electrical power resource usage and records that an electric vehicle (e.g., 110) associated or correlated with a transponder (e.g., transponder 148) having identifier "36000A" (Reference 202) used an ACME charging station (Reference 212) to charge 17 kWh of electrical power (Reference 222), and that the address of the ACME charging station was 12 Main St. in Fairfax, Virginia (Reference 242).

[0063] In various embodiments, including the example of FIG. 1 , the EV 110 does not interact with the charging station 115 via the transponder 148, but instead interacts with the charging station 115 via the contract certificate 146, and the MRIP 130 searches for or otherwise identifies a correlation between the contract certificate 146 and the transponder 148 and provides this information to the road usage RMO 140, which can then use the associated transponder identifier “36000A” (reference numeral 202) in its display of the multi-resource usage record 142. This conversion of the contract certificate identifier to a transponder identifier may be preferred in embodiments where the user 105’s account is traditionally associated with the transponder 148 (e.g., an EZPass® account and transponder). As previously mentioned, in some embodiments, the contract certificate 146 may be cryptographically tied or associated to the transponder 148, and in some such embodiments, the MRIP 130 may use information from the contract certificate 146 to derive or discover the identity of the transponder. In some other embodiments, an identifier in the contract certificate 146 may be used instead of or in addition to the transponder identifier.

[0064] It should be noted that while this FIG. 2 example of a display 200 of at least a portion of the information from the multi-resource usage record 142 illustrates tracking of two resources, namely road resources and electrical resources, embodiments consistent with the present invention can include other, additional, and / or different resources, such as DOT resources (e.g., licensing resources (e.g., services), vehicle registration resources, vehicle testing resources (e.g., emissions and safety testing), state infrastructure (e.g., roads and bridges) resource usage, etc.); fuel resources, (e.g., gasoline or diesel, which can be tracked in a similar manner to charging); parking space resources; digital asset resources (e.g., software downloaded to the vehicle); and / or other resources consumed by or in connection with the vehicle (e.g., 110).

[0065] Of course, while system 100 of FIG. 1 illustrates devices, systems, processes, operations, and infrastructure for automatically tracking two or three vehicle-related resources: road resources, electrical, and DOT resources, it should also be noted that embodiments consistent with the present invention can include additional, other, or different resources as just described.

[0066] The two right-most columns in FIG. 2, column 250 “Amount” and column 260 “Balance,” are optional and indicate embodiments that, in addition to tracking multiple resource usage, track charges and payments made by users (e.g., owners 105) for resources consumed by or in conjunction with their vehicles (e.g., 110).

[0067] Those skilled in the art will recognize that the information, arrangement, and details shown and described in FIG. 2 are examples presented for simplicity and clarity of explanation. This example is not intended to be limiting, and many implementations are possible, so other data, configurations, implementation details, and variations can be used without departing from the principles of the invention. For example, the display 200 and / or the multi-resource usage record 142 may include only the following columns: resource type (e.g., road use and charging electricity); a transponder / certificate identifier column; and an amount of resource used (e.g., miles or kWh). Other variations are possible.

[0068] 3 is a block diagram of an example computing environment including a computing system 300 that may be used to implement systems, devices, records, processes, operations, and methods consistent with implementations of the present invention. Other components and / or arrangements may also be used. In some implementations, one or more computing systems 300 may be used to partially or fully implement the various components, processes, operations, and data records described in connection with FIGS. 1, 2, 4, and 5, including, among others, the multi-resource interface provider 130, the improved road usage (second) RMO 140, the improved charging station (first) RMO 120, and / or the improved DOT (third) RMO 150. In some implementations, a series of computing systems similar to the computing system 300 may each be customized or configured with dedicated hardware and / or include one or more of the features described herein, and may communicate with each other via a network 335.

[0069] In the example shown in FIG. 3, the computing system 300 includes a number of components, such as a CPU 305, a memory 310, an input / output (I / O) device 325, a hardware security module (HSM) 340, and a storage device 320. The computing system 300 may be implemented in a variety of ways. For example, an implementation as an integrated platform (e.g., a server, a workstation, a personal computer, a laptop, etc.) may include a CPU 305, a memory 310, a non-volatile storage device 320, and an I / O device 325. In such a configuration, the components 305, 310, 320, and 325 may connect and communicate via a local data bus and may access a data repository 330 (e.g., implemented as a separate database system) via an external I / O connection. The I / O component 325 may connect to external devices via a direct communication link (e.g., a hardwired connection or a local wifi connection), via a network such as a local area network (LAN) or a wide area network (WAN such as a cellular network or the Internet), and / or via other suitable connections. System 300 may be stand-alone or may be a subsystem of a larger system.

[0070] CPU 305 may be one or more known processors or processing devices, such as the Core family of microprocessors manufactured by Intel Corporation of Santa Clara, Calif., or the Athlon family of microprocessors manufactured by AMD Corporation of Sunnyvale, Calif. Memory 310 may be one or more high-speed storage devices configured to store instructions and information executed or used by CPU 305 to perform certain functions, methods, and processes related to implementations of the present invention. Storage 320 may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, or other type of storage device or computer-readable medium, including devices such as disk drives and solid-state devices intended for long-term storage, and the like.

[0071] In the illustrated implementation, memory 310 includes one or more instructions, programs or applications 315 that can be loaded from storage device 320 or from a remote system (not shown) and that, when executed by CPU 305, perform various operations, procedures, processes, functions or methods consistent with the present invention, for example as described in connection with Figures 1, 2, 4, and 5. Alternatively, CPU 305 can execute one or more programs that are located remotely from system 300. For example, system 300 can access one or more remote programs via network 335 that, when executed, perform functions, operations and processes associated with implementations of the present invention.

[0072] In one implementation, the memory 310 may include programs 315 for performing the specialized functions and operations described herein with respect to the system for tracking vehicle-related resource usage 100. In some implementations, the memory 310 may also include other programs or applications that implement other methods and processes that provide auxiliary functionality to the present invention.

[0073] Memory 310 may also be configured with other programs (not shown) unrelated to the present invention, and / or an operating system (not shown) that performs certain functions known in the art when executed by CPU 305. By way of example, the operating system may be Microsoft Windows, Unix, Linux, Apple Computer operating system, or other operating system. The choice of operating system, and even the use of an operating system, is not critical to the present invention.

[0074] The HSM 340 may be a device with its own processor that securely generates and / or stores digital security assets (e.g., digital certificates) and / or securely performs various cryptographic and sensitive calculations. The HSM 340 protects digital security assets such as cryptographic keys and digital certificates, and other sensitive data from potential access by attackers. In some implementations, the HSM may be a plug-in card or board that is installed directly into the computing system 300.

[0075] The I / O devices 325 may comprise one or more input / output devices that enable data to be communicated, received, and / or transmitted by the system 300. For example, the I / O devices 325 may include one or more input devices such as a keyboard, touch screen, mouse, etc. that enable input of data from a user. Additionally, the I / O devices 325 may include one or more output devices such as a display screen, CRT monitor, LCD monitor, plasma display, printer, speaker device, etc. that enable data to be output or presented to a user. The I / O devices 325 may also include one or more digital and / or analog communication input / output devices that enable the computing system 300 to communicate, e.g., digitally, with other machines and devices. Other configurations and / or multiples of input and / or output devices may be incorporated into the I / O devices 325.

[0076] In the illustrated implementation, the system 300 is connected to a network 335 (e.g., the Internet, a private network, a virtual private network, a cellular network, or other networks, or a combination thereof), which may connect to various systems and computing machines, such as servers, personal computers, laptop computers, client devices, etc. In general, the system 300 may input data from and output data to external machines and devices via the network 335. In some implementations, the network 335 may be or be part of the communication path 500, 600.

[0077] 3, the data repository 330 is a standalone database external to the system 300. In other implementations, the data repository 330 may be hosted by the system 300. In various implementations, the data repository 330 may manage and store data used to implement systems and methods consistent with the present invention. For example, the data repository 330 may manage and store data used by the vehicle resource usage tracking system 100 (e.g., user account data, data for the multi-resource record 142, etc.).

[0078] Data repository 330 may include one or more databases that store information and are accessed and / or managed via system 300. By way of example, repository 330 may be an Oracle® database, a Sybase® database, or other relational database. However, systems and methods consistent with the present invention are not limited to different data structures or databases, nor are they limited in their use to repository 330, databases, or any particular data structure.

[0079] Those skilled in the art will recognize that the components and implementation details of the system in Figure 3 are examples presented for simplicity and clarity of explanation. Other components and implementation details may be used.

[0080] 4 is a flow chart illustrating an example of a process 400 for generating revised resource usage records for use in a multi-resource tracking record, consistent with an embodiment of the present invention. In the embodiment shown in this example, the process 400 is performed by MRIP 130. In an alternative embodiment, the operations of the process 400 may be performed by an improved resource management operator, such as a road usage (second) RMO 140, a DOT (third) RMO 150, or the like. As previously mentioned, the operations of the process 400 may be embodied in software instructions (e.g., program 315), or the like, and a device that performs (e.g., executes instructions for) the operations of the process 400 may be a computing device 300, or the like.

[0081] 4 , process 400 begins in step 410 with obtaining a first resource usage record, e.g., electricity usage resource record 125, in step 420. In various embodiments, the first resource usage record includes data or information from a certificate associated with the vehicle that charged electricity, e.g., identification information from contract certificate 146 that was downloaded and used by vehicle 110 or its transponder 148 during charging at charging station 115. In various embodiments, the first resource usage record is obtained from or communicated by a first resource management operator, such as charging station RMO 120.

[0082] In step 430, the process 400 generates a revised first resource usage record, e.g., revised electricity usage resource record 145 or 155, in a format usable by a target resource management operator different from the first resource manager. In various embodiments, the revised first resource usage record includes data or information from a certificate associated with the vehicle that charged electricity, e.g., identification information from a contract certificate 146 that was downloaded and used by the vehicle 110 or its transponder 148 during charging at the charging station 115. This included information from the contract certificate may be similar or the same as the contract certificate information that was included in the first resource record obtained in step 420. In various embodiments, the revised first resource usage record (e.g., 145, 155) is generated from the data or information of the first resource usage record obtained in step 420 by reformatting, converting, transforming, modifying, or otherwise processing the information into a format usable by or compatible with the target resource management operator, such as the second RMO 140 or the third RMO 150.

[0083] In step 440, process 400 provides the revised first resource usage record to the target resource management operator, e.g., second RMO 140 or third RMO 150, and then the process ends at 450. In some embodiments, process 400 may provide the revised first resource usage record via an API of the target resource management operator, and step 430 generates the revised first resource usage record in a format usable by that API.

[0084] 5 is a flow chart illustrating an example of a process 500 for generating a multi-resource tracking record 142, consistent with embodiments of the present invention. In the embodiment illustrated in this example, the process 500 may be performed by a resource management operator (e.g., 140, 150). In alternative embodiments, the operations of the process 500 may be performed by a multi-resource interface provider (e.g., 130), or the like. As previously mentioned, the operations of the process 500 may be embodied in software instructions (e.g., program 315), or the like, and a device that performs (e.g., executes instructions for) the operations of the process 500 may be a computing device 300, or the like.

[0085] As shown in the example of Figure 5, process 500 begins at step 510 and begins at step 520 with tracking and storing data reflecting usage of a second resource, e.g., usage of a particular road, by a vehicle (e.g., 110) associated with a contract certificate (e.g., 146). The term "second" resource is used to indicate that it is a different resource than the resource referred to as the "first" resource in Figure 4.

[0086] In step 530, process 500 receives a revised first resource usage record, e.g., revised electricity usage resource record 145 or 155. In various embodiments, the received revised first resource usage record includes data or information from a certificate associated with the vehicle that charged electricity, e.g., identification information from contract certificate 146 that was downloaded and used by vehicle 110 or its transponder 148 during charging at charging station 115. In various embodiments, a multi-resource interface provider (e.g., 130), or another entity having that functionality, can transmit the revised first resource usage record.

[0087] At step 540, process 500 identifies stored data reflecting the vehicle's use of the second resource (e.g., road usage) based on information from the contract certificate received in the revised first resource usage record. In various embodiments, this can be done by using identification information (e.g., unique identifier string, serial number, etc.) included in the revised first resource usage record that uniquely identifies one or more of the certificate (e.g., 146), the vehicle (e.g., 110), or the owner 105, and matching the identification information with previously stored identification information managed by the resource management operator (e.g., 140, 150), which is associated with stored data reflecting the vehicle's use of the second resource (e.g., road usage). In various embodiments, identification information from the contract certificate 146 is stored and used by various entities (e.g., 120, 130, 140, 150) of the system 100 to locate and correlate various types of resource usage information for the vehicle 110, transponder 148, and / or owner 105 associated with the contract certificate 146.

[0088] At step 550, the process 500 generates a multi-resource usage record using or including a combination of data (e.g., both power usage data and road usage data) from the revised first resource usage record (e.g., 145, 155) and from the stored data identified at step 540. In various embodiments, the multi-resource usage record (e.g., 142, 200) may include information that allows the owner / user 105 to recognize, track, and / or manage the usage of resources associated with the vehicle 110, such as entity identification information (e.g., transponder 148 ID number, contract certificate 148 ID number, vehicle 110 ID number, owner 105 name, etc.), resource usage date, resource usage time, amount of resource used, location where resource was used, etc. In some embodiments, the multi-resource usage record (e.g., 142, 200) may also optionally include information specifying the cost of each resource used. As previously mentioned, examples of information that may be in a multi-resource usage record can be found in FIG. 2.

[0089] At step 560, process 400 provides information from the multi-resource usage record to the user (e.g., 105) associated with the vehicle (e.g., 110), and then the process ends at 570. Similar to the operations described above, system 100 can use information from contract certificate 146 to identify the correct user 105 associated with vehicle 110. In some embodiments, the information provided to the user may be a website display or report, etc., including the information shown in FIG.

[0090] Those skilled in the art will recognize that the steps, operations, functions, transmitting entities, receiving entities, and details shown in Figures 4 and 5 are examples presented for brevity and clarity of description. Other steps, operations, functions, transmitting entities, receiving entities, details, and variations can be used without departing from the principles of the invention, and these examples are not intended to be limiting, and many different implementations are possible. For example, the order of steps may be changed, some steps may be performed in parallel with other steps, or functions of two or more steps may be combined into a single step. As another example, step 530 may receive multiple revised first resource usage records 145, and step 550 may generate a multi-resource usage record that combines data from the multiple revised first resource usage records 145 with stored data from the hosting RMO (e.g., 140). In yet another example, a revised version of process 500 may be performed by an MRIP 130 that is operable to not perform step 520; receive and store a plurality of revised first resource usage records 145 in step 530; identify all corresponding received revised first resource usage records 145 in step 540; and generate a multi-resource usage record that combines data from all of the identified plurality of revised first resource usage records 145 in step 550. Other variations are possible.

[0091] Although the foregoing embodiments employ specific examples in the areas of electric road vehicles (e.g., electric or hybrid cars and trucks), road resource usage (e.g., toll roads), power utilization, and DOT resource usage for clarity of explanation, the present invention is not limited to these specific examples. For example, various implementations consistent with the present invention may be used with and for a wide variety of vehicles, such as gasoline or diesel fueled road vehicles, water vehicles, recreational vehicles, and aircraft, among others.

[0092] Various operations of the applications described herein may be performed, at least in part, by one or more virtual machines (VMs). In additional or alternative implementations, operations of the applications described herein may be performed, at least in part, by one or more processors that are temporarily (e.g., by software instructions) or permanently configured to perform the associated operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more application operations, functions, and roles described herein.

[0093] Similarly, the processes, functions, and operations described herein may be at least partially processor-implemented, with the particular processor or processors being examples of hardware. For example, at least some of the operations of a function may be performed by one or more processors or processor-implemented modules. Furthermore, the one or more processors may also operate to support execution of related operations in a "cloud computing" environment or as "software as a service" (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including a processor), and these operations are accessible via a network (e.g., the Internet) and one or more appropriate interfaces (e.g., application programming interfaces (APIs)).

[0094] Performance of a particular operation may be distributed among processors that are not only present within a single machine, but are deployed across multiple machines. In some exemplary embodiments, a processor or processor-implemented module may be located in a single geographic location (e.g., in an office environment, a manufacturing environment, or a server farm). In other exemplary embodiments, a processor or processor-implemented module may be distributed across several geographic locations.

[0095] Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

Claims

1. 1. A system for tracking usage of a plurality of resources by a vehicle associated with a certificate of contract, comprising: a first resource management operator that tracks usage of a first resource by the vehicle associated with the contract certificate and generates a first resource usage record, the first resource usage record including information from the contract certificate; a second resource management operator that tracks usage of a second resource by the vehicle associated with the contract certificate; a multi-resource interface provider operatively connected to the first resource management operator and the second resource management operator; The multi-resource interface provider includes: obtaining the first resource usage record from the first resource management operator; generating a revised first resource usage record from data of the first resource usage record, the revised first resource usage record being in a format usable by the second resource management operator and including information from the contract certificate; providing the revised first resource usage record to the second resource management operator; The second resource management operator: identifying data regarding the usage of the second resource by the vehicle based on the information from the contract certificate; combining data from the revised first resource usage record with the identified data regarding the usage of the second resource by the vehicle associated with the contract certificate; generating a multi-resource usage record using the combined data; providing information from the multi-resource usage record to a user associated with the vehicle.

2. The multi-resource interface provider, creating the contract certificate; providing the contract certificate to the second resource management operator; The second resource management operator: The system of claim 1 , further comprising the step of providing the contract certificate to the vehicle.

3. The system of claim 2 , wherein the second resource management operator performs operations further comprising associating the contract certificate with a transponder associated with the vehicle.

4. The system of claim 1 , wherein the contract certificate is stored by the vehicle.

5. The system of claim 1 , wherein the contract certificate is stored by a transponder associated with the vehicle.

6. The system of claim 1 , wherein the first resource is at least one of a division of power resources, road use resources, or transportation resources.

7. The system of claim 1 , wherein the second resource is at least one of a division of power resources, road use resources, or transportation resources.

8. generating the revised first resource usage record from data of the first resource usage record, The system of claim 1 , further comprising the step of including data from the contract certificate in the revised first resource usage record.

9. generating the revised first resource usage record from data of the first resource usage record, 2. The system of claim 1, further comprising the step of: converting data from said first resource usage record into said format usable by said second resource management operator.

10. 1. A system for managing data from a first resource management operator tracking usage of a first resource by a vehicle associated with a certificate of contract, comprising: a second resource management operator that tracks usage of a second resource by the vehicle associated with the contract certificate; a multi-resource interface provider operatively connected to the first resource management operator and the second resource management operator; The multi-resource interface provider includes: obtaining the first resource usage record from the first resource management operator, the first resource usage record including information from the contract certificate; generating a revised first resource usage record from data of the first resource usage record, the revised first resource usage record being in a format usable by the second resource management operator and including information from the contract certificate; providing the revised first resource usage record to the second resource management operator; The second resource management operator: identifying data regarding the usage of the second resource by the vehicle based on the information from the contract certificate; combining data from the revised first resource usage record with the identified data regarding the usage of the second resource by the vehicle associated with the contract certificate; generating a multi-resource usage record using the combined data; providing information from the multi-resource usage record to a user associated with the vehicle.

11. The multi-resource interface provider, creating the contract certificate; providing the contract certificate to the second resource management operator; The second resource management operator: The system of claim 10 , further comprising the step of providing the contract certificate to the vehicle.

12. The system of claim 11 , wherein the second resource management operator performs operations further comprising associating the contract certificate with a transponder associated with the vehicle.

13. The system of claim 10 , wherein the contract certificate is stored by the vehicle.

14. The system of claim 10 , wherein the contract certificate is stored by a transponder associated with the vehicle.

15. The system of claim 10 , wherein the first resource is at least one of a division of power resources, road use resources, or transportation resources.

16. The system of claim 10 , wherein the second resource is at least one of a division of power resources, road use resources, or transportation resources.

17. generating the revised first resource usage record from data of the first resource usage record, The system of claim 10 further comprising including data from the contract certificate in the revised first resource usage record.

18. generating the revised first resource usage record from data of the first resource usage record, 11. The system of claim 10, further comprising converting data from the first resource usage record into the format usable by the second resource management operator.

Citation Information

Cited By

  • Gas turbine engine and fuel cell assembly

    US20240287938A1