Patent Grant
11985579
The present disclosure relates to over-the-air provisioning of electric vehicle operational settings.
Electric vehicles often include devices and components necessary or desirable for operation such as for the generation, management, storage and consumption of energy. Electric vehicle components and devices can include batteries and battery management systems. The devices and components of electric vehicles may operate in a variety of manners, according to a variety of settings, for example manufacturing settings. The operational settings of various electric vehicle devices and components are often static. Thus, changing, updating or altering an electric vehicle's operational settings can be challenging if not impossible, for example, requiring the purchase and installation of new, replacement and/or additional components in order to effectuate different operational settings. Furthermore, the operational settings of a vehicle's components may not allow the components to function with other components having different operational settings. This may limit the options of available components that may be used in a vehicle, for example making it difficult or impossible to replace an original vehicle battery with a battery from a different manufacturer. As such, systems and methods to allow for the simple, efficient and quick updating and/or altering of electric vehicle operational settings are desirable.
Various embodiments of systems, methods and devices within the scope of the appended claims each have several aspects, no single one of which is solely responsible for the desirable attributes described herein. Without limiting the scope of the appended claims, the description below describes some prominent features.
Details of one or more embodiments of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that relative dimensions of the following figures may not be drawn to scale.
The present disclosure provides a system for over-the-air provisioning of a vehicle's operational settings. The system may include, for example, a server, remote to the vehicle, and including operational settings data. The server may be configured to: receive a request for operational settings data; and in response to receiving said request, transmit operational settings data to the vehicle; and one or more components of the vehicle configured to operate according to one or more operational settings. The one or more components may include a transceiver configured to communicate wirelessly with the server to send requests to the server and to receive operational settings data from the server; a memory including executable software instructions, the memory configured to update the instructions in response to receiving operational settings data from the server; and a processor configured to execute the software instructions to cause the component to function according to the one or more operational settings corresponding to the operational settings data received from the server.
In some embodiments, the server may be configured to receive the request for operational settings data from a user or from the vehicle.
In some embodiments, the server is further configured to: receive a request from a user for operational settings options; and in response to receiving said request, transmit operational settings options to the user.
In some embodiments, the one or more components of the vehicle include one or more of an energy storage device, an energy generation system, a vehicle management system, a motor or a component interface device.
In some embodiments, the server is configured to, in response to receiving, at the server, the request for operational settings data, determine whether operational settings data are available.
In some embodiments, the server is configured to, in response to receiving, at the server, the request for operational settings data, determine a status of current operational settings data of the vehicle.
In some embodiments, the system may further include a third-party server remote to the vehicle and remote to the server. The third-party server may include operational settings data and the server configured to communicate wirelessly with the third-party server to send and receive data.
In some embodiments, the server is configured to record download event information to a history log.
The present disclosure provides a method for over-the-air provisioning of a vehicle's operational settings. The method may include, for example, receiving, at a server remote to the vehicle, a request for operational settings data; in response to receiving said request, transmitting operational settings data from the server to the vehicle; receiving, at a component of the vehicle, the operational settings data; storing, in a memory of the component, the operational settings data, the operational settings data including executable software instructions; and executing, at a processor of the component, the executable software instructions of the operational settings data to cause the component to operate according to an operational setting corresponding to the operational settings data.
In some implementations, receiving the request for operational settings data at the server includes receiving the request from the vehicle or a user.
In some implementations, the method can further include receiving, at the server, a first request from a user for operational settings options; and in response to receiving said first request, transmitting to the user, operational settings options from the server to the user.
In some implementations, the method can further include in response to receiving, at the server, the request for operational settings data, determining whether operational settings data are available.
In some implementations, the method can further include in response to receiving, at the server, the request for operational settings data, determining a status of current operational settings data of the vehicle.
In some implementations, determining the status of the operational settings data of the vehicle includes querying the vehicle for data relating to its current operational settings data; determining operational settings data that are accessible to the server and available for the vehicle; and comparing the operational settings data accessible to the server with the current operational settings data of the vehicle.
In some implementations, determining the status of the operational settings data of the vehicle includes accessing a history log of download event information to determine the current operational settings data of the vehicle; determining operational settings data that are accessible to the server and available for the vehicle; and comparing the operational settings data accessible to the server with the current operational settings data of the vehicle.
The present disclosure provides a method for over-the-air provisioning of a vehicle's operational settings. The method can include, for example, detecting, by a first component of the vehicle, a second component of the vehicle; determining, by the first component, an operational incompatibility between the first and second components; transmitting, by the first component, a request for operational settings data to a server remote to the vehicle; receiving, from the server, operational settings data at the first component; updating executable software instructions of the first component according to the operational settings data; and executing the updated executable software instructions to cause the first component to operate according to an operational setting corresponding to the operational settings data to render the first component compatible with the second component.
In some implementations, the first component of the vehicle includes one or more of an energy storage device, an energy generation system, a vehicle management system, a motor or a component interface device.
In some implementations, the method can further include in response to receiving, at the server, the request for operational settings data, determining, by the server, whether operational settings data are available.
In some implementations, the method can further include in response to receiving, at the server, the request for operational settings data, determining, by the server, a status of current operational settings data of the vehicle.
In some implementations, determining the status of the operational settings data of the vehicle includes querying the vehicle for data relating to its current operational settings data; determining operational settings data that are accessible to the server and available for the vehicle; and comparing the operational settings data accessible to the server with the current operational settings data of the vehicle.
The present disclosure provides a system for over-the-air provisioning of a vehicle's operational settings. The system can include, for example, a roller configured to contact a wheel of the vehicle, the roller configured to rotate in response to a rotation of the wheel when the roller is in contact with the wheel; an actuator configured to apply a first force to the roller to cause the roller to contact the wheel of the vehicle with a second force; a generator rotatably coupled with the roller and configured to generate an electrical output in response to a rotation of the roller; and an interface device in communication with the actuator. The interface device may include a transceiver configured to communicate wirelessly with a remote server to receive operational settings data from the server; a memory including executable software instructions and configured to update the software instructions in response to receiving operational settings data from the server; and a processor configured to execute the software instructions to cause the actuator to operate according to the operational settings data received from the server.
In some embodiments, the operational settings data includes operational settings for adjusting the first force, and the actuator can be configured to adjust the first force applied to the roller according to the operational settings data.
In some embodiments, the operational settings include conditions for adjusting the first force, and the conditions can include an air pressure of the wheel, a vertical motion of the wheel, a velocity of the vehicle, a rotational velocity of the wheel, an acceleration of the vehicle, or an amount of electrical output generated at the generator.
In some embodiments, the actuator is configured to increase, according to the operational settings data, the first force applied to the roller in response to a vertical motion of the wheel exceeding a threshold.
In some embodiments, the actuator is configured to increase, according to the operational settings data, the first force applied to the roller in response to an air pressure of the wheel falling below a threshold.
In some embodiments, the actuator is configured to increase, according to the operational settings data, the first force applied to the roller in response to an electrical output of the generator falling below a threshold.
In some embodiments, the operational settings data includes operational settings for changing a position of the roller, and the actuator can be configured to change the position of the roller according to the operational settings data.
In some embodiments, the operational settings include conditions for adjusting the position of the roller, and the conditions can include an air pressure of the wheel, a vertical motion of the wheel, a velocity of the vehicle, a rotational velocity of the wheel, an acceleration of the vehicle, or an amount of electrical output generated at the generator.
In some embodiments, the roller positions include an extended position in which the roller is in contact with the wheel, and a retracted position in which the roller is a distance from the wheel.
In some embodiments, the actuator is configured to transition the roller, according to the operational settings data, to a retracted position in response to a vertical motion of the wheel exceeding a threshold.
In some embodiments, the actuator is configured to transition the roller, according to the operational settings data, to a retraced position in response to an air pressure of the wheel falling below a threshold.
In some embodiments, the actuator is configured to transition the roller, according to the operational settings data, to a retraced position in response to an electrical output of the generator falling below a threshold.
In some embodiments, the actuator applies the first force to the roller via one or more of a flexible arm, a mechanical spring, a gas spring, a piston, a suspension system, a shaft, a strut, hydraulics, pneumatics, a lever, a gear, or a pulley.
The present disclosure provides a method for over-the-air provisioning of a vehicle's operational settings. The method can include, for example, rotating a roller in response to a rotation of a wheel of the vehicle when the roller is in contact with the wheel; applying, via an actuator, a first force to the roller to cause the roller to contact the wheel of the vehicle with a second force; generating, via a generator rotatably coupled with the roller, an electrical output in response to a rotation of the roller; receiving, at an interface device of the vehicle, operational settings data from a remote server; storing, in a memory of the interface device, the operational settings data, the operational settings data including executable software instructions; and executing, at a processor of the interface device, the executable software instructions of the operational settings data to cause the actuator to operate according to the operational settings data received from the server.
In some implementations, the operational settings data includes operational settings for adjusting the first force, and the method can further include adjusting, via the actuator, the first force applied to the roller according to the operational settings data.
In some implementations, the operational settings include conditions for adjusting the first force, and the conditions can include an air pressure of the wheel, a vertical motion of the wheel, a velocity of the vehicle, a rotational velocity of the wheel, an acceleration of the vehicle, or an amount of electrical output generated at the generator.
In some implementations, the operational settings data includes operational settings for changing a position of the roller, the method can further include changing, via the actuator, the position of the roller according to the operational settings data.
In some implementations, the operational settings include conditions for adjusting the position of the roller, and the conditions can include an air pressure of the wheel, a vertical motion of the wheel, a velocity of the vehicle, a rotational velocity of the wheel, an acceleration of the vehicle, or an amount of electrical output generated at the generator.
In some implementations, the roller positions include an extended position in which the roller is in contact with the wheel, and a retracted position in which the roller is a distance from the wheel.
The present disclosure provides a device for over-the-air provisioning of a vehicle's operational settings. The device can include, for example, a transceiver configured to communicate wirelessly with a remote server to receive operational settings data from the server; a memory including executable software instructions and configured to update the software instructions in response to receiving operational settings data from the server; and a processor configured to execute the software instructions to cause an actuator to operate according to the operational settings data received from the server. The actuator can be configured to apply a first force, according to the operational settings data, to a roller to cause the roller to contact a wheel of the vehicle with a second force. The roller can be configured to rotate in response to a rotation of the wheel when the roller is in contact with the wheel. The actuator can be configured to transition the roller, according to the operational settings data, from a first position to a second position.
In some implementations, the operational settings data includes one or more conditions for adjusting the first force, and the processor can be further configured to execute the updated software instructions to cause the actuator to adjust the first force applied to the roller according to the one or more conditions of the operational settings data.
In some implementations, the one or more conditions include an air pressure of the wheel, a vertical motion of the wheel, a velocity of the vehicle, a rotational velocity of the wheel, an acceleration of the vehicle, or an amount of electrical output generated by a generator in response to a rotation of the roller.
In some implementations, the processor is further configured to execute the updated software instructions to cause the actuator to increase, according to the operational settings data, the first force applied to the roller in response to a vertical motion of the wheel exceeding a threshold.
In some implementations, the processor is further configured to execute the updated software instructions to cause the actuator to increase, according to the operational settings data, the first force applied to the roller in response to an air pressure of the wheel falling below a threshold.
In some implementations, the processor is further configured to execute the updated software instructions to cause the actuator to increase, according to the operational settings data, the first force applied to the roller in response to an electrical output generated by a generator falling below a threshold.
In some implementations, the operational settings data includes one or more conditions for changing a position of the roller, wherein the processor is further configured to execute the updated software instructions to cause the actuator to change the position of the roller according to the one or more conditions of the operational settings data.
In some implementations, the operational settings include conditions for adjusting the position of the roller, wherein the one or more conditions include an air pressure of the wheel, a vertical motion of the wheel, a velocity of the vehicle, a rotational velocity of the wheel, an acceleration of the vehicle, or an amount of electrical output generated by a generator in response to a rotation of the roller.
In some implementations, the roller positions include an extended position in which the roller is in contact with the wheel, and a retracted position in which the roller is a distance from the wheel.
In some implementations, the processor is further configured to execute the updated software instructions to cause the actuator to transition the roller, according to the operational settings data, to a retracted position in response to a vertical motion of the wheel exceeding a threshold.
In some implementations, the processor is further configured to execute the updated software instructions to cause the actuator to transition the roller, according to the operational settings data, to a retraced position in response to an air pressure of the wheel falling below a threshold.
In some implementations, the processor is further configured to execute the updated software instructions to cause the actuator to transition the roller, according to the operational settings data, to a retraced position in response to an electrical output generated by a generator falling below a threshold.
In some implementations, the actuator is configured to apply the first force to the roller via one or more of a flexible arm, a mechanical spring, a gas spring, a piston, a suspension system, a shaft, a strut, hydraulics, pneumatics, a lever, a gear, or a pulley.
Disclosed herein is a vehicle management system for over-the-air provisioning of a vehicle's operational settings. The vehicle management system may comprise: a transceiver, a computer readable storage medium having program instructions embodied therewith, and a processor. The transceiver can be configured to communicate wirelessly with a remote server to receive operational settings data from the server. The computer readable storage medium can be configured to update the program instructions according to operational settings data received from the server. The processor can be configured to execute the updated program instructions to cause the vehicle management system to operate according to an operational setting corresponding to the operational settings data received from the server. In some implementations, when operating according to the operational setting, the vehicle management system is configured to: communicate a signal to a switch to cause the switch to transition between an open state and a closed state to control an energy flow between a first energy storage device and a second energy storage device. In some implementations, in the closed state the switch is configured to electrically couple the first energy storage device to the second energy storage device to allow an energy to transfer from the first energy storage device to the second energy storage device.
In some implementations, the first energy storage device includes a capacitor.
In some implementations, the second energy storage device includes a battery.
In some implementations, when operating according to the operational setting, the vehicle management system is further configured to: communicate the signal to the switch to cause the switch to transition between the open state and the closed state once in substantially real time as the operational settings data are received from the server.
In some implementations, when operating according to the operational setting, the vehicle management system is further configured to: communicate the signal to the switch to cause the switch to transition between the open state and the closed state every time one or more conditions occurs.
In some implementations, when operating according to the operational setting, the vehicle management system is further configured to: communicate the signal to the switch to cause the switch to transition between the open state and the closed state based at least in part on one or more of a geographic location of the vehicle, a distance travelled by the vehicle, or a distance between the vehicle and a desired destination.
In some implementations, the system may further comprise a voltage sensor in electrical communication with the first or second energy storage device. The voltage sensor can be configured to detect a voltage level of the first or second energy storage device.
In some implementations, when operating according to the operational setting, the vehicle management system is further configured to: communicate the signal to the switch to cause the switch to transition to the closed state, in response to determining that the voltage level in the second energy storage device is below a low threshold level; and cause the switch to transition to the open state, in response to determining that the voltage level in the second energy storage device is above a high threshold level.
In some implementations, when operating according to the operational setting, the vehicle management system is further configured to: communicate the signal to the switch to cause the switch to transition to the closed state, in response to determining that the voltage level in the first energy storage device is above a high threshold level, and cause the switch to transition to the open state, in response to determining that the voltage level in the first energy storage device is below a low threshold level.
In some implementations, when operating according to the operational setting, the vehicle management system is further configured to communicate the signal to the switch to cause the switch to transition to the closed state, in response to determining that a voltage differential between the first and second energy storage device is above a threshold level.
In some implementations, the system can further comprise a current sensor in electrical communication with the second energy storage device and configured to detect a current or amperage conducted from the second energy storage device to a load.
In some implementations, when operating according to the operational setting, the vehicle management system is further configured to communicate the signal to the switch to cause the switch to transition to the closed state when a current or amperage conducted from the battery to the load exceeds a threshold level.
Disclosed herein is a computing system for over-the-air provisioning of a vehicle's operational settings. The computing system can comprise: a computer readable storage medium having program instructions embodied therewith; and one or more processors configured to execute the program instructions. The one or more processors can be configured to execute the program instructions to cause the computing system to receive information relating to an operation or status of the vehicle and in response to receiving said information, wirelessly transmit operational settings options to a user. The one or more processors can be configured to execute the program instructions to cause the computing system to receive, from the user, a selection of one or more of the operational settings options. The one or more processors can be configured to execute the program instructions to cause the computing system to in response to receiving a user selection, wirelessly transmit, to the vehicle, operational settings data corresponding to the one or more operational settings selected by the user, wherein the operational settings data are configured, when executed, to cause the vehicle to operate according to the one or more operational settings selected by the user.
In some implementations, the one or more processors are further configured to execute the program instructions to cause the computing system to maintain a history log including information relating to transmitting the operational settings data to the vehicle.
In some implementations, the one or more processors are further configured to execute the program instructions to cause the computing system to update generate a charge to the user in response to transmitting the operational settings data to the vehicle.
In some implementations, wirelessly transmitting operational settings options to the user includes transmitting the operational settings options to a mobile device via a text message.
In some implementations, wirelessly transmitting operational settings options to the user includes transmitting the operational settings options to a control dashboard of the vehicle.
In some implementations, receiving the selection of one or more of the operational settings options from the user includes receiving a text message from a mobile device.
In some implementations, the information relating to the operation or status of the vehicle includes one or more of a charge level of a battery of the vehicle, an estimated remaining operating time of the vehicle, an estimated remaining operating distance of the vehicle, a distance travelled by the vehicle, a distance between the vehicle and a desired destination, a geographic location of the vehicle, or a geographic location of a desired destination.
In some implementations, the operational settings data are configured, when executed, to cause an energy generation system of the vehicle to operate according to the one or more operational settings selected by the user.
In some implementations, the operational settings data are configured, when executed, to cause an energy management system of the vehicle to operate according to the one or more operational settings selected by the user.
Disclosed herein is an energy system for storing and providing energy to a vehicle. The energy system may comprise: a capacitor storage device, and an energy storage device. The capacitor storage device can be configured to receive a first portion of energy from an energy source. The capacitor storage device can be configured to store the first portion energy as an electric field of the capacitor storage device. The capacitor storage device can be configured to convey the first portion energy to a battery storage device or to an electrical load of the vehicle. The energy storage device can be configured to receive a second portion of energy from an energy source. The energy storage device can be configured to store the second portion of energy. The energy storage device can be configured to convey the second portion energy to the battery storage device or to the electrical load of the vehicle. The energy storage device can have a higher amp-hour rating than the capacitor storage device. The energy storage device can have a lower voltage rating than the capacitor storage device.
In some implementations, the energy storage device includes one or more cells electrically connected in parallel.
In some implementations, the capacitor storage device includes one or more cells electrically connected in series.
In some implementations, the energy storage device has a higher C rating than the capacitor storage device.
In some implementations, the energy storage device is configured to discharge a greater continuous current or burst current than the capacitor storage device.
In some implementations, the energy storage device includes one or more capacitors.
In some implementations, the energy storage device includes one or more batteries.
In some implementations, the energy storage device is removably electrically coupled with the battery via a mechanical connection.
In some implementations, the energy storage device is coupled with the battery via a friction fit.
Disclosed herein is a system for managing energy storage. The system can comprise a capacitor storage device, a battery, a switch, and a controller. The capacitor storage device can be configured to receive a first portion of energy from an energy source. The capacitor storage device can be configured to store the first portion energy as an electric field of the capacitor storage device. The battery can be configured to electrically couple to the capacitor storage device. The battery can be configured to receive energy from the capacitor storage device via one or more diodes biased toward the battery. The switch can be configured to transition between an open state and a closed state. The switch can be configured to electrically couple the battery to the ultracapacitor when in the closed state to conduct an energy between the ultracapacitor and the battery. The switch can be configured to electrically disconnect the battery from the ultracapacitor when in the open state to prevent conducting an energy between the ultracapacitor and the battery. The controller may be in electrical communication with the switch and may be configured to cause the switch to transition between the open state and the closed state.
In some implementations, the energy source includes is one or more solar panels or solar cells.
In some implementations, the energy source includes a turbine.
In some implementations, the energy source includes is a generator.
In some implementations, the energy source includes is a charging station.
In some implementations, the energy source is disposed on a housing of a vehicle.
Overview
Example systems and methods for over-the-air provisioning of a vehicle's operational settings are described herein. A system for over-the-air provisioning of a vehicle's operational settings can include a server remote to the vehicle which can include or have access to operational settings data. The server can transmit (e.g., wirelessly) the operational settings data to the vehicle. Operational settings data can affect how a vehicle or its components function.
Various methods exist for transmitting operational settings data to a vehicle (e.g., from a remote server). Operational settings data can be transmitted to the vehicle in response to a request (e.g., from the vehicle or its components, or from a user), automatically such as on a periodic basis, anytime operational settings data (updated or new) are available for the vehicle or anytime updated or new operational settings data are required or desired for improving performance of a vehicle or its components.
Various example systems and methods for over-the-air provisioning of an electric vehicle's operational settings are described herein, for example, with reference to the figures. The various systems, methods and their implementations are given as examples and are not meant to be limiting of the present disclosure.
In some implementations, Vehicle Components may refer to any of the components of a vehicle such as an energy storage device (e.g., battery, capacitor), an energy generation system (e.g., a generator), a motor, a vehicle management system, a component interface device, driven masses, rollers, flexible arms, suspension systems (e.g., of driven masses and/or rollers), etc. The vehicle components may operate according to operational settings and may be provisioned over-the-air.
In some implementations, Operational Settings may refer to any of the various settings according to which a vehicle or its components may operate.
In some implementations, (Operational) Settings Data may refer to data for provisioning the operational functionality of a vehicle or its components. Settings data may include executable software instructions or files including the same. In some embodiments, operational settings data can include program instructions that when executed cause a vehicle component to perform one or more operations one time (e.g., a one-time operation). In some embodiments, operational settings data can include program instructions that when executed cause a vehicle component to perform one or more operations a multiple times, repeatedly, indefinitely, every time one or more conditions occurs, or the like. In some embodiments, operational settings data may include program instructions that when executed cause a vehicle component to perform one or more operations immediately (e.g., in substantially real-time as when the settings data are received at the component). In some embodiments, operational settings data may include program instructions that when executed cause a vehicle component to perform one or more operations at a future time (e.g., at a time after the settings data are received at the component).
In some implementations, Operational Settings Options may refer to any of the various operational settings that may be available to a vehicle for download and which a user may review and select.
In some implementations, Operational Settings Server (OSS) may refer to a server, remote to a vehicle, that may communicate with the vehicle. The OSS may be configured to store various operational setting data that can be downloaded to a vehicle.
In some implementations, User may refer to a person or entity that may be associated with a vehicle and may communicate with the OSS for requesting operational settings data to be downloaded to the vehicle.
In some implementations, Vehicle Management System may refer to a system or device for controlling or managing the operational functionality of a vehicle or its components. The vehicle management system may communicate with the OSS and may manage the provisioning of the vehicle such as requesting, downloading, storing operational settings data. The vehicle management system may comprise and/or may be referred to herein as a battery management system. The vehicle management system may include a processor or other similar computing device.
In some implementations, Component Interface Device may refer to a device or system electrically coupled to two or more components of a vehicle that may act as an interface between the components to allow the components to operate with each other in the vehicle. In some embodiments, the component interface device may be provisioned (e.g., over-the-air) with operational settings data.
Example Systems for Over-the-Air Provisioning
In some embodiments, the one or more energy storage devices 102 may include one or more capacitor modules in combination with one or more batteries. For example, the one or more energy storage devices 102 may include one or more capacitor modules installed alongside one or more batteries may be connected in series or in parallel. For example, a capacitor module may be connected in series or parallel with a battery when supplementing the voltage in the battery or when charging the battery. Therefore, the battery and the capacitor modules may provide voltage support to each other. As such, the capacitor modules may provide supplemental energy when the battery are discharged or be used in place of the battery altogether.
In some embodiments, the capacitor modules provide a burst of energy on demand to the battery and/or to the motor. For example, the capacitor modules are coupled to the vehicle (or another) controller that monitors a charge level of the battery and/or an energy demand of the motors. The controller may control coupling of the capacitor modules to the battery to charge the battery with the burst of energy from the capacitor modules when the charge level of the battery falls below a threshold value or may couple the capacitor modules to the battery to supplement an output energy of the battery.
The energy storage devices 125a, 125b can include capacitors, batteries, or the like. The switch(es) 127 can electrically couple the energy storage devices 125 to each other. The switch(es) 127 can electrically couple the energy storage devices 125 to a load. The switch(es) 127 may be configured to transition between states to allow or prevent a flow of energy therethrough.
The vehicle management system 121 may be electrically coupled to the component interface device 123 which in turn may be electrically coupled to one or more energy storage devices 125a, 125b and/or switches 127. In some implementations, vehicle management system 121 may be directly electrically coupled to one or more energy storage devices 125a, 125b and/or switches 127. The electrical coupling between the components, as described, may facilitate the communication of data between the components which may affect how the components function and function together. In some embodiments, the components may be electrically coupled via wires. In some embodiments, the components may be electrically coupled wirelessly.
The vehicle management system 121 may control operation of the one or more energy storage devices 125a, 125b. For example, the vehicle managements system 121 may determine and/or control the conditions under which the energy storage device 125 is charged, discharged, the rate of charging or discharging, the maximum or minimum charge held by the energy storage device, and may coordinate charging and discharging between multiple energy storage devices 125. The vehicle management system 121 may control operation of the energy storage devices 125 according to operational settings, such as according to operational settings data provisioned to the vehicle management system 121 over-the-air.
The vehicle management system 121 may control operation of the switch(es) 127. The vehicle management system 121 may control operation of the switch(es) 127 according to operational settings, such as according to operational settings data provisioned to the switch(es) 127 over-the-air. For example, the vehicle management system 121 may control when the switch(es) 127 transition between states to control whether the switch(es) 127 allow energy to pass through or prevent energy from passing therethrough. Accordingly, the vehicle management system 121 may control or adjust an electrically coupling between components by controlling the switch(es) 127. For example, the vehicle management system 121 may control whether the energy storage devices 125 are electrically coupled to each other by controlling transitioning of the switch(es) 127 between operative states. As another example, the vehicle management system 121 may control whether the energy storage devices 125 are electrically coupled to a load by controlling transitioning of the switch(es) 127 between operative states.
Advantageously, operational settings data used to control the energy storage devices 125 and/or switch(es) 127 may be provisioned (e.g., over-the-air to the vehicle management system 131 and/or component interface device 133). Provisioning the operational settings data may allow the operational settings to be updated such as periodically, automatically, in response to a request, and/or on demand. Updating the operational settings (e.g., via over-the-air provisioning) of the various components can improve operational efficiency and/or performance of the system by dynamically adjusting operational settings according to real-time needs and conditions. For example, operational settings data can be provisioned over-the-air to update operational settings to improve performance based on changes in energy levels of the energy storage devices 125, energy requirements of a load, operating conditions, such as temperature, geographic location, geographic destination, estimated time and/or distance to destination, or the like.
The vehicle management system 121, the energy storage devices 125a, 125b, and switch(es) 127 may each include parameters, for example, operational settings data included on the component that may be executed by a computing device to control operation of the respective components. The operational settings included on each respective component (vehicle management system 121, energy storage device 125) may have been encoded during manufacturing (e.g., manufacturer's settings) or may have been configured during an initial configuration of the component. In some embodiments, the operational settings of the vehicle management system 121, energy storage device 125, and/or and switch(es) 127 may be static and it may be impossible or difficult to change the operational settings of said components. In some embodiments, the operational settings of the components such as the vehicle management system 121, energy storage device 125, or and switch(es) 127 may be quickly updated, for example via over-the-air provisioning as described herein. In some embodiments, the components such as the vehicle management system 121, energy storage device 125, or and switch(es) 127 may only operate with certain other components (e.g., types, makes, models) based on the configuration of the operational settings. For example, the operational settings of a component may be required to be compatible with operational settings of other components for the components to function together.
A component interface device 123 may facilitate the interaction between a vehicle management system 121 and other components such as an energy storage device 125 and/or switch 127, for example in embodiments where the operational settings of the vehicle management system 121, energy storage device 125, and/or switch 127 are static and/or are not initially configured for compatible functionality with one another.
The component interface device 123 may include parameters, for example, operational settings data included on the component interface device 123 that may be executed by a computing device to control operation of the component interface device 123.
The component interface device 123 may be configured to detect an energy storage device 125 as well as a type, make or model of the energy storage device 125. For example, the component interface device 123 may be configured to determine whether the energy storage device is a battery or a capacitor as well as other characteristics of the energy storage device (e.g., make or model). The component interface device 123 may be configured to detect and determine characteristics of the vehicle management system 121. The component interface device 123 may be configured to detect and determine characteristics of the switch(es) 127.
The component interface device 123 may be configured to determine (e.g., type or characteristics of) the operational settings data included on the energy storage device 125, the vehicle management system 121, and/or the switch(es) 127, for example by parsing the operational settings data of the other components or detecting an identifier of the operational settings data such as an operational settings data tag or header included in the operational settings data and containing information relating to the characteristics of the operational settings data. The component interface device 123 may be configured to facilitate an operational compatibility between the vehicle management system 121, energy storage device 125, and/or switch(es) 127 for example in embodiments where the operational settings data of the vehicle management system 121, energy storage device 125, and/or switch(es) 127 would not otherwise be compatible.
As an example of facilitating an operational compatibility, the component interface device 123 may receive an electrical communication (e.g., via wires or wirelessly) from the vehicle management system 121, for example, including data relating to instructions to control an operation of the energy storage device 125. The component interface device 123 may determine (or may have previously determined) the operational settings data of the energy storage device 125. If the operational settings data of the energy storage device 125 is not compatible with the operational settings data of the vehicle management system 121 (e.g., such that the energy storage device 125 would not “understand” the instructions and/or data communicated from the vehicle management system 121), the component interface device 123 may “translate” the data communicated from the vehicle management system 121 to a form that is compatible with the operational settings data of the energy storage device 125, for example, by generating new data and/or altering the data received from the vehicle management system 121. The component interface device 123 may be configured to perform similar operations of translating data communicated from the energy storage device 125 to the vehicle management system 121.
The component interface device 123 may control the interacting between two components based on operational settings data of the component interface device 123. For example, the component interface device 123 may interface a vehicle management system 121 with a certain energy storage device 125a according a first operational settings data of the component interface device 123. A second energy storage device 125b may be added to the vehicle which may replace or supplement energy storage device 125b. The component interface device 123 may not be configured according to the first operational settings data to facilitate operational compatibility between the vehicle management system 121 and the energy storage device 125b. However, the component interface device 123 may be provisioned (e.g., over-the-air as described herein) with second operational settings data which may configure the component interface device 123 to facilitate operational compatibility between the vehicle management system 121 and the energy storage device 125b.
The example components discussed above with reference to
The driven mass(es) 136 can include one or more rollers, one or more fifth wheels, and/or one or more turbines, such as a water or wind turbine. In some implementations, a roller, a driven mass, a fifth wheel, and/or a turbine may include similar structural and/or operational features. In some implementations, the terms “roller”, “driven mass”, “fifth wheel”, and/or “turbine” may be used interchangeably.
The vehicle management system 131 is in communication with the component interface device 133. The component interface device 133 is in communication with one or more driven masses 136, the roller(s) 138, the gearbox 132, and the suspension system 134. In some implementations, the vehicle management system 131 is in direct communication with the one or more driven masses 136, the roller(s) 138, the gearbox 132, and the suspension system 134. In some embodiments, the vehicle management system 131 and/or component interface device 133 may be provisioned (e.g., over-the-air) with operational settings data to control an operation of the one or more driven masses 136, the one or more rollers 138, the gearbox 132, and/or the suspension system 134.
As an example, the vehicle management system 131 and/or component interface device 133 may control, according to operational settings data, a position of the driven mass(es) 136 relative to a ground surface and/or a position of the roller(s) 138 relative to a wheel of the vehicle. As another example, the vehicle management system 131 and/or component interface device 133 may control, according to operational settings data, a force with which the driven mass(es) 136 are applied to a ground surface and/or a force with which the roller(s) 138 are applied to a wheel such as via one or more actuators. Adjusting (e.g., increasing) a force with which the driven mass(es) 136 and/or roller(s) are applied to a ground surface and/or a wheel of the vehicle may improve contact of the driven mass(s) 136 and/or rollers with the ground and/or wheel, such as on uneven terrain.
As another example, the vehicle management system 131 and/or component interface device 133 may control, according to operational settings data, the gearbox 132. The gearbox may rotatably couple the driven mass(es) 136 and/or roller(s) 138 to a generator. The gearbox 132 may include one or more gears of various diameters. The vehicle management system 131 and/or component interface device 133 may control a ratio of rotation between a driven mass 136 and/or roller 138 rotatably coupled to the gearbox 132 and a generator rotatably coupled to the gearbox 132. The operational settings according to which the vehicle management system 131 and/or component interface device 133 controls the gearbox 132 may determine the conditions under which the gearbox 132 adjusts a ratio of rotation.
As another example, the vehicle management system 131 and/or component interface device 133 may control, according to operational settings data, the suspension system 134. The suspension system 134 may house the driven mass(es) 136 and/or roller(s) 138. The suspension system 134 may be independent of a suspension system of the vehicle. The suspension system 134 may operate to transition the driven mass(es) 136 and/or roller(s) 138 between engaged/disengaged states and/or extended/retracted states. In some implementations, the engaged state and the extended state may include similar operational features. In some implementations, the disengaged state and the retracted state may include similar operational features. In some implementations, the term “engaged state” and the term “extended state” may be used interchangeably. In some implementations, the term “disengaged state” and the term “retracted state” may be used interchangeably. The vehicle management system 131 and/or component interface device 133 may control whether the suspension system 134 transitions between states. The operational settings according to which the vehicle management system 131 and/or component interface device 133 controls the suspension system 134 may determine the conditions under which the suspension system 134 transitions between states.
Advantageously, operational settings data used to control the driven mass(es) 136, roller(s) 138, gearbox 132, and/or suspension system 134 may be provisioned (e.g., over-the-air to the vehicle management system 131 and/or component interface device 133). Provisioning the operational settings data may allow the operational settings to be updated such as periodically, automatically, in response to a request, and/or on demand. Updating the operational settings (e.g., via over-the-air provisioning) of the various components can improve operational efficiency and/or performance of the system by dynamically adjusting operational settings according to real-time needs and conditions. For example, operational settings data can be provisioned over-the-air to update operational settings to improve performance based on changes in a terrain surface on which the vehicle travels, changes in wheels used on the vehicle, changes in a pressure of the vehicle wheels and/or driven mass(es) 136, or the like.
In some embodiments, the energy source 155 can include a power grid or Mains electricity. In some embodiments the energy source 155 can include an energy generation or regeneration system. For example, the energy source 155 can include one or more of: a generator, a driven mass, a fifth wheel, a roller, a turbine such as a water and/or wind turbine, a regenerative braking system, a solar power generation system such as solar panels or solar cells. In some implementations, the energy source 155 may be included within a vehicle. For example, the energy source 155 may include an on-board power generation system disposed within and/or on a vehicle and that is mobile with the vehicle. In some implementations, the energy source 155 may be separate from a vehicle. For example, the energy source 155 may be stationary or in a fixed location such as a charging station.
The energy storage device 141 can be electrically coupled to the energy source 155 via an electrical interface 153a. For example, the energy storage device 141 can be removably coupled (electrically, physically) with the energy source 155 via the electrical interface 153a. The electrical interface 153a can include a plug and/or a socket such as a standard 110 volt outlet wall socket configured to receive an electrical plug. The energy storage device 141 can be electrically coupled with the energy source 155 via one or more electrical wires, cables, or cords. The energy storage device 143 can be electrically coupled to the energy source 155 via an electrical interface 153b in a same or similar manner as described above with respect to energy storage device 141 and electrical interface 153a.
The energy storage device 141 can be electrically coupled with the energy source 155 via a diode 158a. The diode 158a can be biased toward the capacitor module and configured to allow an energy (e.g., a current or amperage) to flow from the energy source 155 to the energy storage device 141. The diode 158a may prevent an energy from flowing from the energy storage device 141 to the energy source 155. Advantageously, the diode 158a may facilitate retaining an energy at the energy storage device 141 when the energy storage device 141 has a higher energy level (e.g., higher voltage) than the energy source energy source 155, such as during a power outage and/or when a power generation system is not producing energy. In some embodiments, more than one diode may be disposed between the energy source 155 and the energy storage device 141. The energy storage device 143 can be electrically coupled with the energy source 155 via a diode 158b in a same or similar manner as described above with respect to energy storage device 141 and diode 158a.
The energy storage device 141 can include one or more capacitors, ultracapacitors, and/or supercapacitors. A plurality of capacitors in the energy storage device 141 can be electrically connected in series and/or parallel. In some embodiments, the energy storage device 141 can be configured to store up to 400 volts of electrical energy. For example, the energy storage device 141 may store about 100 to 200 volts, about 200 to 300 volts, or about 300 to 400 volts. In some embodiments, the energy storage device 141 can be configured to store less than 100 volts such as about 50 volts or about 25 volts.
The switch 146a can include one or more of an electrical switch, a relay, or the like. The switch 146a can operate according to one or more states including an open state and a closed state. In the closed state, the switch 146a can conduct energy (e.g., current or amperage) such as from the energy storage device 141 to the energy storage device 145. In the open state, the switch 146a may not conduct energy (e.g., from the energy storage device 141 to the energy storage device 145). The switch 146a may transition between the open and closed states. In some embodiments, the switch 146a transitions between the open and closed states automatically, such as in response to a signal from the vehicle management system 140.
The switch 146a is electrically coupled with the energy storage device 145. As shown, the switch 146a is electrically coupled to the energy storage device 145 via diode 148a. In some embodiments, the energy system 150 may not include diode 148a.
In some embodiments, the energy storage device 145 may be electrically coupled to the switch 146a (and/or energy storage device 141) via one or more electrical wires, cables, cords, or the like, which may be configured to withstand high voltages (e.g., 400 volts) and/or high amperage (e.g., 400 amperes). The energy storage device 145 may be electrically coupled to the energy storage device 141 via one or more electrical connectors, such as a plug, a socket, or the like. The energy storage device 145 and the energy storage device 141 may be removably coupled via the electrical connectors.
When the switch is in the closed state, energy may transfer from the energy storage device 141 to the energy storage device 145, such as via the diode 148a. The energy storage device 141 can be electrically connected with the energy storage device 145 in series and/or parallel. When a voltage differential between energy storage device 141 and the energy storage device 145 exceeds a certain threshold, energy may be amenable to flow from the energy storage device 141 to the energy storage device 145. For example, in some embodiments, the diode 148a may be configured with a certain resistance preventing current from passing through the diode 148a until a threshold voltage across the diode 148a is achieved. As the voltage differential across the diode 148a (e.g., between the energy storage device 141 and energy storage device 145) increases, the diode 148a may “open” to allow a current to pass in a single direction through the diode 148a.
The switch 146b may include similar or the same operational and/or structural features as described above with respect to switch 146a. The energy storage device 143 may transfer energy to the energy storage device 145 via the switch 146b in a same or similar manner as described above with respect to energy storage device 141 transferring energy to energy storage device 145 via switch 146a.
The energy storage device 145 can include one or more batteries such as lithium ion batteries, lithium polymer batteries, and/or batteries that include one or more other materials for storing energy, such as zinc, carbon, magnesium, manganese, mercury, alkaline, silver, nickel, metal hydride, cadmium, lead, and the like. In some embodiments, the energy storage device 145 can include a battery field. In some embodiments, the energy storage device 145 can include. In some embodiments, energy storage device 145 can be configured to store up to 400 volts of electrical energy. For example, the energy storage device 145 may store about 100 to 200 volts, about 200 to 300 volts, or about 300 to 400 volts. In some embodiments, the energy storage device 145 can be configured to store less than 100 volts such as about 50 volts or about 25 volts. In some embodiments, the energy storage device 145 may comprise a plurality of batteries, such as a battery field. The plurality of batteries may be electrically connected to one another in series and/or in parallel.
In some implementations, the energy storage device 145 is electrically coupled with energy storage device 147. In some implementations, the energy storage device 145 is directly electrically coupled to the load 157.
In some implementations, the energy storage device 145 may be structurally and/or functionally similar or the same as energy storage device 147. In some implementations, the energy storage device 145 may be structurally and/or operationally different from energy storage device 147. For example, energy storage device 145 and energy storage device 147 each be configured to store a different amount of energy (e.g., voltage). As another example, energy storage device 145 and energy storage device 147 can each be configured with a different specific power (e.g., power density), specific energy (e.g., energy density), charge time, charging rate, life cycle, and/or internal resistance. As another example, energy storage device 145 may be a different type of device or component than energy storage device 147. In some embodiments, energy storage device 145 is a capacitor and energy storage device 147 is a battery. In some embodiments, energy storage device 145 is a first type of battery and energy storage device 147 is a second type of battery. In some embodiments, energy storage device 145 and energy storage device 147 include various types of lithium ion batteries and/or lithium polymer batteries. In some embodiments, the energy storage devices 145, 147 include various materials for storing energy, such as zinc, carbon, magnesium, manganese, mercury, alkaline, silver, nickel, metal hydride, cadmium, lead, and the like.
In some embodiments, energy storage device 141 and/or 143 has a smaller specific energy than energy storage device 145 or energy storage device 147. In some embodiments, energy storage device 145 has a smaller specific energy than energy storage device 147. In some embodiments, energy storage device 141 and/or 143 has a greater specific power than energy storage device 145 or energy storage device 147. In some embodiments, energy storage device 145 has a greater specific power than energy storage device 147.
In one example implementation, the energy storage device 141 and/or 143 charges quickly (e.g., quicker than energy storage devices 145 and/or 147) and stores the energy as an electric field. The energy storage device 141 and/or 143 then conveys energy to the energy storage device 145 (which may charge quicker than energy storage device 147), and which stores the energy conveyed from the energy storage device 141 and/or 143. The energy storage device 145 can convey energy to the energy storage device 147 where energy is stored before being provided to the load 157.
Advantageously, the energy storage device 145 may facilitate a transfer of energy from the energy storage device 141 and/or 143 to the energy storage device 147 by providing an “intermediate” storage device that is more amenable to receiving energy from the energy storage device 141 and/or 143.
In some implementations, the energy storage device 141 may be electrically coupled to the load 157. For example, the energy storage device 141 may be coupled to the load 157 via one or more of switch 146c and/or diode 148c. In some implementations, the energy storage device 143 may be electrically coupled to the load 157. For example, the energy storage device 143 may be coupled to the load 157 via one or more of switch 146d and/or diode 148d. Switch(es) 146c and/or 146d may include operational and/or structural features similar to those discussed above with respect to switch(es) 146a and/or 146b. For example, the energy storage device(s) 141, 143 may transfer energy to the load 157 via switch(es) 146c and/or 146d. Diode(s) 148c and/or 148d may include operational and/or structural features similar to those discussed above with respect to diode(s) 148a and/or 148b. For example, the energy storage device(s) 141, 143 may transfer energy to the load 157 via diode(s) 148c and/or 148d. In some implementations, the energy storage device 141 may transfer energy to the energy storage device 145 at a same time as transferring energy to the load 157. In some implementations, the energy storge device 143 may transfer energy to the energy storage device 145 at a same time as transferring energy to the load 157.
The energy storage device 147 can be electrically coupled to the load 157. The load 157 may include a device or component configured to consume energy. The load 157 may draw energy from the energy storage device 147 as the load 157 operates. For example, the load 157 may demand current or amperage from the energy storage device 147 depending on the energy requirements of the load 157. As the load 157 draws current or amperage from the energy storage device 147, a voltage level of the energy storage device 147 may reduce. As the load 157 requires more energy, more current or amperage may be transferred from the energy storage device 147 to the load 157 resulting in greater voltage loss at the energy storage device 145. In some embodiments, the load 157 may include a vehicle, such as a car, truck, golf cart, tractor, tractor-trailer, or the like. For example, the load 157 may be a motor of a vehicle.
As shown in this example embodiment, the energy system 150 further includes a vehicle management system 140. The vehicle management system 140 may include similar structural and/or operational features to vehicle management system 121 and/or vehicle management system 131 described herein. The vehicle management system 140 may be implemented in a vehicle and may be in communication (e.g., wired and/or wireless) with one or more components of the vehicle. The vehicle management system 140 may control operation or functionality of the vehicle or various components thereof. The vehicle management system 140 can include one or more memory or storage devices configured to store executable instructions (e.g., software instructions) that when executed perform one or more operations. The vehicle management system 140 can include one or more hardware processors configured to execute instructions to cause the vehicle management system 140 and/or other components of the energy system 150 to perform one or more operations.
In some embodiments, the vehicle management system 140 can optionally include a voltage sensor 142 and/or a current sensor 144. In some embodiments, the vehicle management system 140 may optionally be in communication with a voltage sensor and/or a current sensor remote to the vehicle management system 140. The voltage sensor 142 can be configured to determine voltage levels and/or differentials at the energy source 155, energy storage device 141, 143, 145, and/or 147, and/or at the load 157. The current sensor 144 can be configured to determine an electrical current or amperage flowing through the energy system 150 such as from the energy source to energy storage device 141 and/or 143, from energy storage device 141 and/or 143 to energy storage device 145, from energy storage device 141 and/or 143 to the load 157, from energy storage device 145 to energy storage device 147 and/or the load 157, or from energy storage device 147 to the load 157.
The vehicle managements system 140 may be in communication with the energy source 155, energy storage device(s) 141, 143, 145, and/or 147, switch(es) 146a, 146b, 146c, and/or 146d, and/or the load 157. The vehicle management system 140 may communicate with one or more components of the energy system 150 via a wired and/or wireless connection. For example, the vehicle management system 140 may be remote to one or more components of the energy system 150 and may communicate with the other components over a wireless network to control one or more operations of the components. The vehicle management system 140 may control the operation of the components based at least in part on information from the voltage sensor 142, the current sensor 144, and/or according to one or more operational settings.
The vehicle management system 140 may control operation of the energy system 150, or components thereof, such as switch(es) 146a, 146b, 146c, and/or 146d, to control a flow of energy in the energy system such as between energy storage devices. For example, the vehicle management system 140 may communicate a signal to the switch 146a to transition to a closed state in which the energy storage device 141 is in electrical communication with the energy storage device 145 and configured to transmit energy to the energy storage device 145. As another example, the vehicle management system 140 may communicate a signal to the switch 146a to transition to an open state in which the energy storage device 141 is not in electrical communication with the energy storage device 145 and in which energy does not flow from the energy storage device 141 to the energy storage device 145. The vehicle management system 140 may control energy flow from the energy storage device 141 to the energy storage device 145 (e.g., by controlling switch operation) based at least in part on information from the voltage sensor 142, the current sensor 144, and/or according to one or more operational settings. The vehicle management system 140 may similarly control operation of switch(es) 146b, 146c, and/or 146d.
The vehicle management system 140 may be in communication with a server (e.g., OSS) remote to the vehicle management system 140 and/or remote to the vehicle. The vehicle management system 140 may receive from a remote server operational settings data which may include one or more executable software instructions that when executed by a hardware processor are configured to control an operation of the vehicle management system 140 and/or an operation of one or more of the components in communication with the vehicle management system 140.
In one example implementation, the vehicle management system 140 receives operational settings data from a remote server relating to controlling a switch such as any of switches 146a, 146b, 146c, and/or 146d (e.g., transitioning between open and closed states). In some embodiments, the vehicle management system 140 can receive operational settings data that when executed cause the vehicle management system 140 to perform an operation immediately (e.g., at a substantially same time as when the vehicle management system 140 receives the operational settings data). For example, the vehicle management system 140 may generate and transmit a signal to the switch 146a to cause the switch 146a to transition between an open and closed state immediately after receiving and executing operational settings data. In some embodiments, the vehicle management system 140 can receive operational settings data that when executed cause the vehicle management system 140 to perform an operation at a future time (e.g., at a time that is after the vehicle management system 140 receives the operational settings data). For example, the vehicle management system 140 may receive and execute operational settings data that causes the vehicle management system 140 to generate and transmit a signal to the switch 146a to cause the switch 146a to transition between an open and closed state whenever certain conditions are satisfied for an indefinite amount of time moving forward (e.g., until the vehicle management system 140 receives updated operational settings data). For example, the operational settings data, when executed, may cause the vehicle management system to cause the switch 146a to transition between an open and closed state whenever the vehicle has travelled a certain distance, when a voltage of one or more energy storage devices reaches a threshold value, when a load of the vehicle (e.g., a motor) is demanding a certain current draw from an energy storage device, when an energy generation system of the vehicle is operating or producing a threshold amount of energy, or the like.
Example Energy Storage Devices
The energy storage device 141 may include one or more capacitors such as ultracapacitor(s) and/or supercapacitor(s). The energy storage device 141 may include one or more batteries, such as a lithium-ion battery, lithium-polymer battery, alkaline battery, lead-acid battery, or the like. In some implementations, the energy storage device 143 may be a same or similar type of device as the energy storage device 141 and/or may include similar operational ratings. In some implementations, the energy storage device 143 may be a different type of device than energy storage device 141 and/or may include different operational ratings. The energy storage device 143 may optionally be electrically coupled with the energy storage device 141 such as in series and/or parallel. In some implementations, the energy storage device 143 may not be directly electrically coupled with the energy storage device 141.
The energy storage device 143 may be removably mechanically and/or electrically coupled with the energy system 150 and/or components thereof, such as the energy source 155, energy storage device 141, energy storage device 145, energy storge device 147, etc. The energy storage device 143 may be removable electrically coupled with the energy system 150 via a mechanical connection. For example, the energy storage device 143 may establish an electrical connection with the energy system 150 a via friction fit.
The energy storage device 143 may have a high amp-hour rating. For example, the energy storage device 143 may have an amp-hour rating of less than 10 Ah, less than 25 Ah, less than 50 Ah, less than 75 Ah, or less than 100 Ah. The energy storage device 143 may have a higher amp-hour rating than the energy storage device 141. The energy storage device 143 may have low voltage rating. For example, the energy storage device 143 may have a voltage rating of less than 1V, less than 5V, less than 10V, less than 20V, or the like. The energy storage device 143 may have a lower voltage rating than the energy storage device 141. In some implementations, the energy storage device 143 may have a same or similar watt-hour rating as the energy storage device energy storage device 141, where watt-hour rating is equal to the amp-hour rating multiplied by the voltage rating. The following table is provided as a non-limiting example of one implementation:
As shown in the example above, the energy storage device 141 may have a voltage rating of 36V, an amp-hour rating of 20 Ah, and a watt-hour rating of 720 Wh. The energy storage device 143 may also have a watt-hour rating of 720 Wh with a voltage rating of 12V, an amp-hour rating of 60 Ah. In some implementations, the energy storage device 143 may have a different watt-hour rating than the energy storage device 141.
Advantageoulsy, the energy storage device 141 and the energy storage device 143 can provide a large voltage and a large current to the energy storage device 145. For example, the energy storage device 141 may be configured with a large voltage rating (e.g., relative to the energy storage device 143) and the energy storage device 143 may be configured with a large amp-hour rating (e.g., relative to the energy storage device 141). Advantageously, the energy storage device 143 increases the amount of amperage provided to the energy storage device 145 without unnecessarily increasing voltage which may be costly and require large amounts of space. For example, with reference to the example table provided above, energy storage device 141 may be electrically coupled to energy storage device 145 and can provide 20 Ah and 36V thereto. If a user desires to increase the amperage provided to the energy storage device 145 by an additional 60 Ah, rather than purchase and install three additional energy storage devices similar to energy storage device 141 (e.g., 3×20 Ah=60 Ah), the user would only have to purchase and install the single energy storage device 143 to obtain the desired additional 60 Ah. In some implementations, a user may combine a plurality of energy storage devices 143 to achieve a desired amp-hour rating.
The energy storage device 143 may include one or more cells. A cell may be an anode and cathode separated by an electrolyte used to produce a voltage and current. The cells may be arranged in series and/or parallel. In some implementations, the cells of energy storage device 143 may be arranged in parallel which may yield a relatively high amp-hour rating of the energy storage device 143 and a relatively low voltage rating of the energy storage device 143. The energy storage device 141 may include one or more cells. The cells may be arranged in series and/or parallel. In some implementations, the cells of energy storage device 141 may be arranged in series which may yield a relatively high voltage rating of the energy storage device 141 and a relatively low amp-hour rating of the energy storage device 141.
The energy storage device 143 may have a high C rating. For example, the energy storage device 143 may have a C rating of less than 5 C, less than 10 C, less than 20 C, less than 30 C, less than 40 C, less than 50 C, less than 100 C, or less than 150 C. The energy storage device 143 may have a higher C rating than the energy storage device 141. A high C rating may facilitate faster charge and/or discharge times of the energy storage device 143. For example, the energy storage device 143 may be configured to discharge a large amount of current while maintaining a substantially constant voltage. The energy storage device 143 may have a high maximum current output where maximum current output is equal to C rating multiplied by amp-hour rating. The energy storage device 143 may have a high continuous charge/discharge current, and/or a high burst charge/discharge current.
The energy storage device 143 may have a high E rating. The energy storage device 143 may have a higher E rating than the energy storage device 141. The energy storage device 143 may have a high specific power. The energy storage device 143 may have a higher specific power than the energy storage device 141.
The energy storage device 143 may be electrically coupled with the energy storage device 145 via one or more high voltage wires or cables configured to a hold a large voltage. The energy storage device 143 may be electrically coupled with the energy storage device 145 via one or more low voltage wires or cables and/or which may be configured to conduct a large current.
In some embodiments, the vehicle component 200 may comprise a component interface device. In some embodiments, the component interface device may facilitate an operational compatibility between two or more components, for example as described with reference to
In some embodiments, a vehicle may comprise multiple components that include structural and/or operational features similar to those show in example vehicle component 200. For example, a battery of a vehicle as well as a vehicle management system of a vehicle as well as a component interface device may all include structural and/or operational features for communicating with a server and receiving and storing operational setting data as described herein. In some embodiments, components of a vehicle with structural and/or operational features for over-the-air provisioning may each communicate with a server independently from all other components of the vehicle or may communicate in a coordinated manner such that their communication is organized or controlled, for example, by the vehicle managements system. In some embodiments, components of a vehicle with structural and/or operational features for over-the-air provisioning may each communicate with a unique server or with the same server.
The vehicle component 200 can include a transceiver 205, a wireless communicator 210, a processor 215, a storage medium 220 and a memory 225. The transceiver 205 may be connected to the wireless communicator 210 which can comprise an antenna or other similar device for facilitating communicating data to and from a remote server (e.g., OSS described herein). As used herein, phrases referring to communicating with the vehicle (such as sending requests from a vehicle to a server or receiving settings data from a server) may comprise communicating with a component of the vehicle such as example component 200.
The transceiver 205 can be connected to a processor 215 that can control the operation of the vehicle component 200, including the operation of the transceiver 205. The storage medium 220, which may be removable, read-only, or read/write media and may be magnetic-based, optical-based, semiconductor-based media, or a combination of these, may store operating system software for the vehicle component 200 and may also store at least some settings data. The memory 225 may store additional, information, such as applications that may be loaded into the vehicle component 200. In addition, some or all of the settings data for the vehicle component 200 may be stored in the memory 225. Both the memory 225 and the storage medium 220 can be connected to the processor 215. The processor 215 may operate in accordance with executable software, applications, or other instructions stored in the memory 225 and/or the storage medium 220.
In some implementations, memory 225 and/or storage medium 220 may store pre-configured instructions for executing operational settings in a vehicle. In some implementations, the memory 225 and/or storage medium 220 may store instructions for executing an application or program to allow a user to interact with the component 200, for example to request or select operational settings. In some implementations, the memory 225 and/or storage medium 220 may store instructions for communicating with a remote server, for example to retrieve settings data therefrom or to send requests thereto.
The vehicle 325 (and/or user 340) may communicate data (e.g., via a wireless communication path) to the OSS 305. For example, the vehicle 325 (and/or user 340) may send requests to the OSS 305 for operational settings data. The requests can include general requests for operational settings data and/or requests for specific operational settings data. The user 340 may send requests to the OSS 305 for operational settings options. The vehicle 325 (and/or user 340) may send information relating to operational settings data currently included in the vehicle to inform the OSS 305 of the operational settings data possessed by the vehicle such as which settings data or which versions of settings data are possessed by the vehicle.
In some embodiments, the vehicle 325 (and/or user 340) may communicate data (e.g., via a wireless communication path) to the OSS 305 relating to an operation or status of the vehicle. For example, the vehicle 325 may communicate to the OSS 305 information relating to a charge status of the vehicle, a charges status of one or more energy storage devices of the vehicle, a geographical location of the vehicle, a geographic location of a desired destination, an estimated time and/or distance the vehicle may continue to operate (e.g., with a certain charge status), a distance travelled by the vehicle, or the like.
The OSS 305 may communicate data (e.g., via a wireless communication path) to the vehicle 325 (and/or user 340). For example, the OSS 305 may send operational settings data to the vehicle 325 to control one or more operations of the vehicle (e.g., energy status, energy generation status, or the like). The OSS 305 may send data relating to operational settings options to a user 340 for example to provide information to the user 340 relating to which operational settings are available for download to the vehicle 325 so that the user 340 may select which operational settings to download to the vehicle 325. In some embodiments, the OSS 305 may communicate with a user 340 via one or more of a phone, a computing device, a tablet, a vehicle navigation system or control system, or the like. For example, the OSS 305 may transmit a text message to a phone of a user 340. As another example, the OSS 305 may transmit a message to a control dashboard of a vehicle to be read by a user. As another example, the OSS 305 may communicate an email to a user 340 (e.g., to notify the user that the OSS 305 and/or billing server 335 has charged the user). In some implementations, the vehicle 325 (e.g., a vehicle management system of the vehicle) may communicate to the OSS 305 a charge status of the vehicle, a geographic location of the vehicle, and/or a desired geographic destination.
Operational settings data may be stored on an operational settings server (OSS) 305 and transmitted (e.g., via wireless communication) to the vehicle 325. When operational settings are downloaded from the OSS 305, the OSS 305 can collect download event information and send it to a transaction manager 330. The download event information can include the time of the download, the settings data that was downloaded, the reason for the download, the vehicle and/or user associated with the download etc. The transaction manager 330 can combine the download event information with other information, such as operational settings pricing structure and developer data for the downloaded operational settings, to produce usage records. The transaction manager 330 can send the usage records to a billing server 335, which may perform billing services, such as generating invoices. In some embodiments, the billing server 335 may issue a charge to a user according to the operational settings data transmitted from the OSS 305 to a vehicle associated with the user. For example, the billing server 335 (and/or the OSS 305) may charge a user depending on the number and/or types of operational settings data downloaded from the OSS 305 to a vehicle related to the user (e.g., associated with an account of the user). In addition, the billing server 335 may allow an operational settings developer, and/or a third party associated with the OSS 305 to run a report and find out how many users have downloaded and/or are subscribing to a particular service offering or operational setting.
The OSS 305 may be associated with a particular operator or with a third party. In some implementations, the OSS 305 may be operated by a third party that offers the operational settings for a variety of vehicle and/or vehicle component types, for example according to different manufacturers according to their respective various requirements and specifications. In some implementations, the OSS 305 may be operated by multiple third parties that each provide unique operational settings, for example each according to a different vehicle type and/or vehicle component or component type.
In some embodiments, the OSS 305 may offer pass-through access to third party operational settings data, such that the operational settings are stored and managed on a server associated with the third party. In some embodiments, most or all of the available applications may be stored and managed on the OSS 305. The operator of the OSS 305 may have agreements with the third parties to offer the operational settings and to provide for payment to the third parties.
Example Operational Settings of an Electric Vehicle
A vehicle or its components may operate according to various operational settings. Operational settings data (e.g., executable software instructions) may be downloaded to a vehicle component and may affect the how the component functions or operates. Examples are provided of various operational settings that may pertain to the various components of a vehicle.
Operational settings data may affect how an energy storage device, such as a battery of a vehicle operates. For example, operational settings data can affect the rate at which a battery charges or discharges, the maximum or minimum voltage (e.g., energy charge) that a battery may hold, whether a battery is charged or not charged, the conditions under which a battery is charged, when to start or stop charging a battery and the like. Operational settings data can affect where energy is stored, for example in vehicles including more than one energy storage device such as multiple batteries, multiple capacitors or batteries and capacitors. For example, according to one operational setting a vehicle may store energy in a first battery before storing energy in a second battery and vice versa according to a different operational setting. As another example, according to one operational setting, a vehicle may store energy in a capacitor before storing energy in a battery and vice versa according to a different operational setting. As another example, according to one operational setting, one energy storage device (e.g., capacitor) may receive and store energy until a certain threshold is reached that is defined by the operational setting before discharging energy into another energy storage device.
Operational settings data may affect how an energy generation system of a vehicle operates. For example, operational settings data can affect a rate at which an energy generation system generates energy, when it generates energy, when it starts or stops generating energy, where to store or transfer generated energy and the like. For example, according to one operational setting, an energy generation system may generate energy only when the vehicle is accelerating (positive acceleration or negative acceleration) and according to another operational setting, an energy generation system may generate energy only when the vehicle is experiencing constant velocity and zero acceleration.
Operational settings data may affect how a motor of a vehicle operates. For example, operational settings data can affect a rate at which the motor consumes energy, the sources from which the motor draws energy such as from a battery or a capacitor, and the like. As an example, according to one operational setting, the motor may draw energy at a certain rate from a first energy storage device under certain conditions and may draw energy at a certain rate from a second energy storage device under different conditions.
Operational settings data may affect how a vehicle management system of a vehicle operates. For example, operational settings data can affect how a vehicle management system interacts with and/or controls other components of a vehicle. As an example, according to one operational setting, the vehicle management system may manage a vehicle's energy (e.g., generation, storage, consumption) in one way and in a different way according to a different operational setting. In some embodiments, a vehicle management system may control energy flow between components of a vehicle (e.g., between a capacitor and a battery) via a switch according to operational settings data. In some embodiments, the operational settings data for controlling operation of the switch may include any number of criteria and/or conditions for operating the switch (e.g., transition between open and closed stated). Criteria and/or conditions can include battery voltage, capacitor voltage, battery amperage (e.g., delivered to a load), capacitor amperage (e.g., receive from an energy source), or the like. In some embodiments, the operational settings data for controlling operation of the switch may include logic based on levels, changes, rates of change, changes in rate of change, etc., present values and/or historical values of any of the preceding example criteria or conditions. In some embodiments, criteria and/or conditions of an operational setting can include geographical location of the vehicle, a distance travelled by the vehicle, a distance between the vehicle and a desired destination, or the like. As an example, a vehicle management system may cause a switch to transition to a closed state to allow energy to flow between energy storage devices every time the vehicle travels a certain distance (e.g., 10 miles, 30 miles, 100 miles, or the like).
Example Implementation
In an example implementation, the vehicle 325 may communicate to the OSS 305 that the vehicle 325 is 10 miles from a desired destination (e.g., home) and that a battery of the vehicle has sufficient energy to continue to power the vehicle at a current operational status for 5 more miles before discontinuing operation due to low charge. In response, the OSS 305 can transmit a communication to the user 340 (e.g., via a text message to a phone of the user, via a message to a control dashboard of the vehicle 325, or the like) to notify the user 340 that they are 10 miles away from a destination and that the battery of the vehicle 325 only has sufficient charge to operate the vehicle 325 for another 5 miles. The OSS 305 may provide operational settings options to the user 340 which can include, for example, an option to flow energy into a battery to charge the battery to increase the range of the vehicle (e.g., from 5 to greater than 10 miles) so that the vehicle may reach the desired destination, an option to enter a power saving mode, an option to initiate operation of a power generation system (e.g., rollers in extended position) to generate energy to be slowed into the battery, or the like. In some implementations, the operational settings options may be simplified to be easy to understand by a user 340. For example, the operational settings options may be a question such as “Do you want to extend vehicle range by an additional 10 miles?” In some implementations, the operational settings options may not reflect entirely the operational settings data that would correspond thereto. For example, a user 340, when reviewing operational settings options, may not care about every detail of the operational settings data that would be necessary to effectuate the operational settings options. In some implementations, the OSS 305 may determine the operational settings data that correspond most accurately to the selected operational settings options to most effectively implement the selected options. The user 340 may communicate a selected operational settings option to the OSS 305 (e.g., via text message or the like). In response to receiving the user's 340 selected option, the OSS 305 may generate operational settings data corresponding to the selected option to transmit to the vehicle 325 to cause the vehicle to operate according to the selected operational setting. For example, the OSS 305 may transmit operational settings data to the vehicle 325 to cause a vehicle management system to electrically connect a capacitor module to a battery (e.g., via a switch) to flow energy from the capacitor to the battery and/or to cause an energy generation system (e.g., roller(s). driven mass(es)) to transition to an extended position to generate energy to be flowed into the battery.
Operational settings data may affect operational compatibility between various components of a vehicle. For example, operational settings data may configure one component to interface (e.g., electrically couple and communicate) with another component. For example, operational settings data may allow a vehicle management system to interface with any of the other components. As an example, a new component that is installed or included in the vehicle may operate according to manufacturer's specifications and may as a result not function properly (or at all) with other components of the vehicle. The new component or other components of the vehicle may download operational settings data to allow the new component to interface with the other components of the vehicle.
Operational settings data may affect how one or more driven masses operate. Operational settings data may control operation of a driven mass based on one or more factors, including for example, the amount of energy being generated by rotation of the driven mass, the velocity of the vehicle, the air pressure of the driven mass, a motion of the driven mass (e.g., vertical motion caused by uneven terrain), a geographic location of the vehicle, a distance travelled, by the vehicle, a desired destination, and the like. As an example, operational settings data may control the circumstances under which a driven mass is in an extended position (e.g., in contact with the ground) or in a retracted position (e.g., not in contact with the ground). For example, according to certain operational settings data, a driven mass may be in an extended position when the vehicle is traveling in excess of a threshold velocity. As another example, operational settings data may control the conditions under which a driven mass transitions between an extended or retracted position, such as based on whether a threshold amount of energy is being generated by rotation of the driven mass. As another example, operational settings data may control the force with which a driven mass is exerted onto a ground surface. For example, according to certain operational settings data, a driven mass may be applied to a ground surface with greater force (e.g., when a ground surface is uneven) to ensure continual contact with the ground surface, and may be applied to the ground surface with less force (e.g., when the ground surface is flat). The force with which a driven mass is applied to the ground, and/or position of the driven mass may be adjusted or controlled according to the operational settings data by one or more structural features of (e.g., associated with) the driven mass, including, for example, flexible arms, mechanical springs, gas springs, pistons, suspension systems, shafts, struts, hydraulics, pneumatics, levers, gears, pulleys, actuators, hinges, pivots, joints, or the like.
Operational settings data may affect how one or more rollers operate. Operational settings data may control operation of rollers based on one or more factors, including for example, the amount of energy being generated by rotation of the roller, the velocity of the vehicle, the air pressure of a wheel with which a roller is in contact, a motion of a wheel with which the roller is in contact (e.g., vertical motion caused by uneven terrain), a geographic location of the vehicle, a distance travelled, by the vehicle, a desired destination, and the like. As an example, operational settings may control the circumstances under which a roller is in an extended position (e.g., in contact with a wheel of a vehicle) or in a retracted position (e.g., not in contact with the wheel). For example, according to certain operational settings data, a roller may be in an extended position when the vehicle is traveling in excess of a threshold velocity. As another example, operational settings data may control the conditions under which a roller transitions between an extended or retracted position, such as based on whether a threshold amount of energy is being generated by rotation of the roller. As another example, operational settings data may control the force with which a roller is exerted onto a wheel. For example, according to certain operational settings data, a roller may be applied to a wheel with greater force such as when a ground surface is uneven and the wheel is experiencing significant vertical motion to ensure continual contact with the wheel throughout a range of vertical motion, and may be applied to the wheel with less force such as when the ground surface is flat and the wheel is experiencing minimal vertical motion. As another example, the force with which a roller is applied to a wheel and/or position of the roller may be adjusted based on the wheel air pressure (e.g., increase force to ensure roller contacts wheel when wheel air pressure is low, or transition to retracted position when substantial contact between roller and wheel cannot be achieved due to low wheel air pressure, and the like). The force with which a roller is applied to the wheel, and/or position of the roller may be adjusted or controlled according to the operational settings data by one or more structural features of (e.g., associated with) the roller, including, for example, flexible arms, mechanical springs, gas springs, pistons, suspension systems, shafts, struts, hydraulics, pneumatics, levers, gears, pulleys, actuators, hinges, pivots, joints, or the like.
Operational settings data may affect how an autonomous driving system of a vehicle operates. For example, a remote server may periodically update an autonomous driving system (e.g., with the most recent algorithms, data, or the like) by provisioning the vehicle with the latest operational settings data relating to the autonomous driving system. Advantageously, complex operational systems of the vehicle (e.g., autonomous driving systems) may remain up-to-date by fast and simple provisioning of operational settings data without the need for costly and lengthy hardware updates. Operational settings data may similarly affect other systems of the vehicle such as navigational systems.
In certain embodiments, one or all of the components of a vehicle may not be configured for over-the-air provisioning. In such embodiments, a component interface device may advantageously be used to facilitate operational compatibility between components, for example rather than directly provisioning the components themselves. For example, a component interface device may be installed in a vehicle and may be provisioned (e.g., over-the-air) with various operational settings data as required or desired to configure the component interface device to integrate and operate with other components of the vehicle and to facilitate operational compatibility between any of the other components in the vehicle such as between a vehicle management system and an energy storage device.
In some embodiments, a component interface device may be used when the other components of the vehicle are configured for over-the-air provisioning.
Advantageously, provisioning vehicle components may reduce the need for costly, technical or otherwise challenging servicing of the vehicle (e.g., mechanical or electrical fixes) to allow for a new component to integrate in a vehicle such as when a new battery is installed. Provisioning may also allow for components to be installed in a vehicle that would otherwise not be able to integrate and function in said vehicle. For example, by provisioning vehicle components with operational settings data, components from various manufacturers that would otherwise not be capable of functioning together, may be integrated into a vehicle and operate according to a desired manner.
Operational settings data may affect functionality of other computer-based components of a vehicle, such as navigation, stereo, driver assistance systems and the like. Operational settings data may comprise software patches or fixes such as for disabled vehicle components or vehicle components that are not functioning correctly.
Example Methods for Over-the-Air Provisioning
At block 403, the server may check if operational settings data is available. For example, the vehicle may have requested any available updated settings data and the server, at block 403, may check if any updated settings data is available or if the vehicle has the most updated settings data already. If settings data is available, the server may proceed to block 405 and if not, may proceed to block 401.
At block 405, the server may send operational settings data to the vehicle or component thereof, such as a vehicle management system or a component interface device. The settings data may be sent to the vehicle over a wireless communications path. In some embodiments, the operational settings data sent at block 405 may include all settings data available on the server or a subset thereof, such as specific operational settings data in response to a request for specific operational settings data.
At block 501, the server may optionally receive a request from a user for operational settings options. For example, a user may desire to view one or more operational settings available for a vehicle or components of a vehicle.
At block 502, the server may optionally receive information relating to a vehicle operation and/or status. In some embodiments, the server may receive said information from vehicle management system. For example, a vehicle management system may transmit to the server, a status of current operational settings data of the vehicle, a charge status of the vehicle, an energy generation status of the vehicle, operating conditions of the vehicle, estimated remaining battery life or operating time of the vehicle, or the like.
At block 503, the server may send data relating to operational settings options to the user. This may allow a user to view one or more operational settings that are available for download to the vehicle from the server. The server may communicate the operational settings options to the user via one or more of a text message, email message, interne message, or the like.
At block 505, the server may receive a selection of an operational setting from the user. For example, the user, after having reviewed available operational settings, may select one or more of the available settings and send a request to the server to download to the vehicle said operational setting(s).
At block 507, the server may send, to a vehicle, operational settings data corresponding to the option selected by the user.
At block 509, the server may optionally update one or more of a history log, a user account, and/or billing records. For example, in response to sending the operational settings data to the vehicle, the server may record to a history log the details of the transaction (e.g., time, which settings were downloaded, etc.) and may generate a charge to the user for the transaction.
At block 601, a processor of vehicle component (e.g., vehicle management system or a component interface device) may monitor the components of a vehicle. For example, the processor of a particular vehicle component (e.g., vehicle management system or a component interface device) may be in communication with other components of the vehicle. The processor may monitor the components of the vehicle to detect whether vehicle components have been added to the vehicle (e.g., established a new communication with the processor) and/or removed from the vehicle (e.g., terminated an existing communication with the processor).
At block 602, the processor may determine if a new vehicle component has been detected. For example, the processor may detect when a vehicle battery has been replaced with a different vehicle battery (e.g., a new battery of the same type as the old battery or a new battery of a different type than the old battery). As another example, the processor may detect a component that has never before been included in the vehicle, such as a second additional battery, where the vehicle has only ever had one battery, or some other additional energy storage device such as an ultracapacitor. If the processor detects a new component, the processor may proceed to block 603.
At block 603, the processor may determine whether operational settings data is required or desired for the component detected at block 602 to operate properly within the vehicle. For example, the new component or other components of the vehicle may require a more up-to-date version of operational settings and/or new operational settings data for the new component to function properly or optimally with the vehicle and the vehicle's other components. If settings data is not required or desired, the processor may return to block 601 and if settings data is required or desired for the new component or other components, the processor may continue to block 605.
At block 605, the processor may send a request (e.g., to a remote server) for the operational settings data that is required and/or desired. The processor may communicate with the server via a wireless communications path. In response to the request, the remote server may send the operational settings data to the vehicle as described elsewhere herein, for example according to the examples provided. In some embodiments, the operational settings data may be sent to the component of the requesting processor (e.g., vehicle management system, component interface device) and/or to another component such as the new component, for example, if the new component is configured for over-the-air provisioning.
At block 703, the server may determine whether operation settings are available for the vehicle. For example, the server may determine whether a more up-to-date version of the vehicles current operational settings data are available for the vehicle and/or may determine whether new operational settings data are available for the vehicle. The server may compare the vehicle's current operational settings with all operational settings included in the server or accessible by the server or a subset thereof. If the server includes or has access to more or different operational settings than what are currently included in the vehicle, this may indicate that new and/or more up-to-date operational settings are available for the vehicle that may be desirable and/or required for the vehicle or its components to operate (e.g., optimally). If, at block 703, the server determines that operational settings are not available, the server may return to block 701, and otherwise may proceed to block 705.
At block 705, the server may send operational settings data to the vehicle. The operational settings data may include a more up-to-date version of the vehicle's current settings data and/or may include settings data that are new to the vehicle. The server may send the settings data to the vehicle via a wireless communications path as described elsewhere herein.
The fifth wheel 802 is coupled to a drive shaft (herein referred to as the “shaft”) 806. As the fifth wheel 802 rotates, the shaft 806 also rotates at a same, similar, or corresponding rate as the fifth wheel 802. In some embodiments, the fifth wheel 802 and the shaft 806 may be coupled such that the shaft 806 rotates at a greater or reduced rate as compared to the fifth wheel 802. In some embodiments, the shaft 806 is coupled to a support structure 807. The support structure 807 may be attached to the frame or body of the vehicle 800 and allow for the fifth wheel 802 to be extended or retracted as needed while supported by the vehicle 800. Two sprockets or gears 808a and 808b are disposed on the shaft 806 such that when the shaft 806 rotates, the sprockets 808a and 808b also rotate. In some embodiments, the sprockets 808a and 808b and the shaft 806 may be coupled such that the sprockets 808a and 808b rotate at a greater or reduced rate as compared to the shaft 806.
The sprockets 808a and 808b engage with a chain, belt, gearing, pulley, or similar device 804a and 804b, respectively. The chains 804a and 804b cause one or more devices (not shown in this figure) coupled via the chains 804a and 804b to rotate at a rate that corresponds to the rate of rotation of the sprockets 808a and 808b. In some embodiments, the one or more devices coupled to the sprockets 808a and 808b via the chains, gearing, pulley, or similar device 804a and 804b are components of or otherwise coupled to the OBCS 810. For example, the devices to which the sprockets 808a and 808b are coupled via the chains (and so forth) 804a and 804b provide power (for example, by way of kinetic energy) to the OBCS 810 to enable the OBCS 810 to charge the vehicle 800 while the vehicle 800 is in motion. Thus, in some embodiments, the devices to which the sprockets 808a and 808b are coupled via the chains 804a and 804b may include generators, alternators, or similar mechanical to electrical energy conversion devices, as described in further detail below. In some embodiments, the small motor described above may act as a fail over motor to drive the shaft driving the generators 902a and 902b should one of the chains 804a and 804b fail.
In some embodiments, the vehicle 800 includes multiple fifth wheels 802, sprockets 808, and/or chains 804 coupling the sprockets 808 to one or more devices. The one or more fifth wheels 802 and the corresponding one or more sprockets 808 may rotate with one or more corresponding shafts 806. In some embodiments, each fifth wheel 802 is mounted via its respective shaft 806 to its own support structure 807. In some embodiments, each fifth wheel 802, when additional fifth wheels 802 exist, is coupled to its own energy conversion device(s) through one or more sprockets 808 and chains 804 that rotate with the corresponding shaft 806 of the additional fifth wheels 802. By including additional fifth wheels 802, more mechanical energy may be converted to electrical energy for supply by the OBCS 810 as compared to with a single fifth wheel 802.
As described above, the fifth wheel 802 is designed to rotate when the vehicle 800 is in motion and the fifth wheel 802 is extended and/or otherwise in contact with the ground or road surface (or otherwise being driven while the vehicle is in motion). When the fifth wheel 802 rotates, that rotation causes the shaft 806 to rotate, causing the sprockets 808a and 808b to also rotate. Accordingly, the chains 804a and 804b coupled to the sprockets 808a and 808b move or rotate around the sprockets 808a and 808b, respectively. The movement of the chains 804a and 804b while the vehicle 800 is in motion and the fifth wheel 802 is in contact with the ground causes the pulleys 904a and 904b of the rotors of the generators 902a and 902b, respectively, to rotate. As described above, the rotation of the pulleys 904 of the generators 902 causes the rotors of the generators 902 to rotate to cause the generators 902 to generate the electrical energy output via the cable, where the electrical energy output corresponds to the mechanical rotation of the pulleys 904. Thus, rotation of the fifth wheel 802 causes the generators 902a and 902b to generate electrical energy outputs. In some embodiments, the generators 902a and 902b (in combination and/or individually) may generate electrical energy outputs at greater than 400 VAC (for example in a range between 120 VAC and 480 VAC) delivering up to or more than 120 kW of power to the OBCS 810. In some embodiments, the power output of the generators 902a and 902b, in combination and/or individually, may range between 1.2 kilowatts (kW) and 120 kW, for example 1.2 kW, 3.3 kW, 6.6 kW, 22 kW, 26 kW, 62.5 kW, and 120 kW, and so forth. In some embodiments, the generators 902a and 902b provide up to or more than 150 kW of power. The power provided by the generators may be adjusted by adjusting the particular generators used or by otherwise limiting an amount of power being delivered from the OBCS 810 to the battery (or similar charge storage devices), as needed.
In some embodiments, the fifth wheel 802 may be designed to be smaller in diameter than the other wheels of the vehicle 800. By making the fifth wheel 802 smaller in diameter than the other wheels of the vehicle 800, the fifth wheel 802 may rotate more revolutions per distance traveled than the other wheels of the vehicle. Accordingly, the fifth wheel 802 rotates at a faster RPM than the other wheels of the vehicle. The shaft 806, coupled to the fifth wheel 802, has a smaller diameter than the fifth wheel 802. The sprockets 808a and 808b coupled to the shaft 806 have a larger diameter than the shaft 806 but a smaller diameter than the fifth wheel 802. In some embodiments, the diameters of the various components (for example, the fifth wheel 802, the shaft 806 and/or the sprockets 808a and 808) may be varied to further increase the rate of rotation (or rotational speed) of the corresponding components. In some embodiments, the diameter of the fifth wheel 802 may be reduced further as compared to the other wheels of the vehicle. In some embodiments, gearing between the fifth wheel 802 and the shaft 806 and/or between the shaft 806 and the sprockets 808a and 808b may further increase the difference in the rotational rates or speeds of the various components as compared to a wheel of the vehicle 800.
As shown in
In some embodiments, the sprockets 808a and 808b may have a diameter that is approximately half the diameter of the fifth wheel 802. For example, a ratio of the diameter of the fifth wheel 802 to the sprockets 808a and 808b may be approximately 2:1 such that the sprockets 808a and 808b rotate at approximately twice the rotational speed or RPMs as the fifth wheel 802. More specifically, the diameter of the sprockets 808a and 808b may be between 3″ and 5″, where the diameter is one of 3″, 4″, and 5″. Similarly, the sprockets 808a and 808b may have a larger diameter than the pulleys 904a and 904b; for example, the pulleys 904a and 904b may have diameters of less than 5″ (more specifically, one or more of 1″, 2″, 3″, 4″, and 5″, inclusive). The resulting rotation of the pulleys 904a and 904b occurs at sufficiently high, sustained speeds or RPMs that the corresponding generators 902a and 902b generate electrical power at levels sufficient to energy the OBCS 810 to charge the battery of the vehicle 800 while the vehicle 800 is in motion.
As the rotors for the generators 902a and 902b rotate, they induce a magnetic field within windings in stator coils of the generators 902a and 902b. The magnetic field generated within the coils may be controlled (for example, increased or decreased) by changing a number of coils in each of the generators 902a and 902b, thus changing the sizing of the generators 902a and 902b. The energy generated by the generators 902a and 902 may be varied (for example, increased or decreased) by introducing and/or changing a number of capacitors or other components utilized in conjunction with the generators 902a and 902b (for example, within the generators 902a and 902b or in series downstream of the generators 902a and 902b), and/or by using a permanent magnet coil in the generators 902. The magnetic field generated within the coils may be directly related to the energy (for example, a current) generated by the generators 902a and 902b. In some embodiments, the magnetic field is related to the torque on the generator such that as the torque on the generator increases, the magnetic field rises. As such, to reduce wear and tear on components in the vehicle 800 and to optimize voltage generation, the magnetic field is managed as described herein. In some embodiments, when the fifth wheel 802 comprises the small motor as described above, the small motor is an AC or DC motor and acts as a fail over device that is coupled directly to the rotors of the generators 902 such that the small motor is able to drive the generator should the pulley 804, the fifth wheel 802, or other device coupling the fifth wheel 802 to the generators 902 fail.
In some embodiments, the extending and retracting of the fifth wheel 802 may occur based on communications with a controller that monitors the state of charge of a battery and/or demand from a motor. For example, when the controller determines that the battery requires a charge or the motor demands electricity (for example, the vehicle 800 is accelerating), the controller issues a signal to a fifth wheel 802 control system that causes the fifth wheel 802 to be extended to be in contact with the ground or road surface while the vehicle 800 is in motion. Once the fifth wheel 802 reaches an RPM of at least 1000 RPM, the rate of rotation (for example, the RPMs) of the fifth wheel 802 may be controlled and/or monitored such that the battery is charged such that the charge of the battery is maintained or increased or such that the motor is provided with sufficient energy to drive the vehicle 800. For example, if the controller determines that the battery needs to be charged while the vehicle 800 is in motion, the controller may issue the signal to charge the battery to the fifth wheel 802 system. This signal may cause the fifth wheel 802 system to extend the fifth wheel 802 to contact the ground or road surface. When the fifth wheel 802 reaches 1000 RPM while the vehicle 800 is moving, the generators 902a and 902b generate sufficient electrical energy to charge the battery at a rate greater than it is being discharged by the motor to move the vehicle 800 or to feed the motor at a level sufficient to fully drive the vehicle 800. As the controller monitors the charge of the battery or the demand from the motor, when the charge level or the charge state of the battery or the motor demand reaches a second threshold, the controller may issue a second signal to stop charging the battery or stop feeding the motor. This second signal may cause the fifth wheel 802 to be retracted or otherwise disconnect the feed of electricity from the battery or the motor.
In some embodiments, retracting the fifth wheel 802 occurs in a controlled matter. In some embodiments, the fifth wheel 802 continues to rotate when it is initially retracted and no longer in contact with the ground or road surface. As such, the generators 902a and 902b coupled to the fifth wheel 802 continue to generate electrical energy while the fifth wheel 802 continues to rotate based on its inertia. The controller may issue the second signal before the battery is fully charged so as to not waste any energy generated by the generators 902a and 902b. In some embodiments, energy generated by the generators 902a and 902b may be offloaded from the vehicle 800, for example to a land-based grid or energy storage device (for example, a home battery, and so forth).
In some embodiments, the controlled deceleration of the rotation of the fifth wheel 802 when the fifth wheel 802 is retracted occurs due to a brake or similar component that causes the fifth wheel 802 to stop rotating in a controlled manner. In some embodiments, the brake may include a physical brake or other slowing techniques. In some embodiments, the braking of the fifth wheel 802 is regenerative to provide energy to the battery or the motor while the fifth wheel 802 is braking.
In some embodiments, as described above, the fifth wheel 802 extends in response to the first signal from the controller requesting that the battery of the vehicle 800 be charged. As noted above, the fifth wheel 802 may have a mass that allows the fifth wheel 802 to continue to rotate under inertia, etc., when the fifth wheel 802 is retracted and no longer in contact with the ground or road surface while the vehicle 800 is in motion. In some embodiments, the fifth wheel 802 is coupled to the flywheel or similar component that spins under the inertia, etc., after the fifth wheel 802 is retracted from the ground or road surface. Based on the inertia of the fifth wheel 802 or the flywheel or similar component, mechanical energy may be generated from the movement of the vehicle 800 and stored for conversion to electricity (for example, by the generators 902a and 902b, etc.).
Once the fifth wheel 802 is extended to contact the ground or road surface, the fifth wheel 802 begins rotating when the vehicle 800 is moving. Due to the smaller size of the fifth wheel 802, as described above, the fifth wheel 802 rotates with more RPMs than the other wheels of the vehicle 800. While the fifth wheel 802 rotates, the sprockets 808a and 808b described above also rotate, causing the generators 902a and 902b to generate electrical energy. The continued reduction in diameters of components between the other wheels of the vehicle 800 and the pulleys 904 of the generators 902 ensures that the generators 902 rotate at a sufficiently fast rate (RPMs) that they generate power to supply to the OBCS 810, as described herein. The electrical energy is fed to the OBCS 810, which charges the vehicle 800 via the charging port of the vehicle 800, or directly to the motor. The fifth wheel 802 is retracted in response to the second signal from the controller, and may or may not continue to rotate and generate electricity under its inertia.
As described above, due to the mass and other properties of the fifth wheel 802 or the flywheel or similar components, the fifth wheel 802 or the fly wheel or similar components may continue to rotate or otherwise maintain some mechanical energy though the fifth wheel 802 is no longer in contact with the ground or road surface while the vehicle 800 is moving. In some embodiments, the fifth wheel 802, once it reaches the 1000 RPMs described above, is able to maintain its rotation even though the fifth wheel 802 is no longer being “driven” by the ground or road surface when the vehicle 800 is moving. As such, the generators 902a and 902b are able to continue to generate electrical energy for charging the battery or feeding the motor of the vehicle 800 via the OBCS 810. In some embodiments, the fifth wheel 802 or the flywheel or similar components may continue to generate mechanical energy that is converted to electrical energy by the generators 902a and 902b until the fifth wheel 802 or flywheel or similar components are stopped using the brake or similar components, as described above, or until the fifth wheel 802 or flywheel or similar components stop rotating due to friction. In some embodiments, the fifth wheel 802 or flywheel may be replaced with a geared motor or similar component that is smaller in diameter than the other wheels of the vehicle.
In some embodiments, the fifth wheel 802 may be configured to not be in contact with the ground (for example in a position stored upward from the ground) as the vehicle accelerates (for example from rest) to reduce the drag on the vehicle as the vehicle accelerates and so to minimize the energy reduction in an energy storage device (e.g., ultracapacitor, battery) required for acceleration of the vehicle. The fifth wheel 802 may be configured to drop, for example automatically, to contact the ground to begin generating energy as discussed herein when the vehicle is not accelerating (for example from rest), for example when the vehicle has reached a substantially constant, non-zero velocity for example 25 miles per hour. The fifth wheel may be configured to automatically raise (to avoid contact with the ground to reduce drag on the vehicle) when the vehicle is accelerating and/or when the vehicle's acceleration is above a certain threshold, when the vehicle is accelerating within certain velocities and/or when the vehicle is moving within threshold velocities. The fifth wheel may be configured to automatically drop (to contact the ground to generate energy) when the vehicle is not accelerating, and/or when the vehicle's acceleration is below a certain threshold and/or when the vehicle is moving within threshold velocities.
The alternate system 1000 further may include the fifth wheel 802 configured to rotate or spin on the shaft 806. As described above, the rotation of the fifth wheel 802 causes the shaft 806 to rotate and further causes the sprocket 808 and chain 804 to rotate. The chain 804 is coupled to a second shaft 704, for example via a second pulley or sprocket 709 rotated by the chain 804. In some embodiments, the shaft 806 is coupled to the second shaft 704 via another means, for example a direct coupling, a geared coupling, and so forth. In some embodiments, the sprockets 808 and 709 (or similar components) and so forth may be sized to allow for balancing of rotational speeds between the various components. For example, the sprockets 808 on the shaft 806 and corresponding sprockets or gearing on the second shaft 704 are sized to balance rotations between the fifth wheel 802 and the generation unit 1010. In some embodiments, the sizing for the sprockets 808 and 709 (and similar components) is selected to control the electricity generated by the generation unit 1010.
The generation unit 1010 may be electrically coupled to a capacitor (for example, one of the capacitor modules), the battery, the motor, and/or a cut-off switch. The cut-off switch may disconnect the output of the generation unit 1010 from the capacitor, the battery, and/or the motor such that electrical energy generated by the generation unit 1010 may be transferred to the battery, the capacitor module, or to the motors as needed. In some embodiments, the cut-off switch can be controlled by an operator or the controller of the vehicle 800 or the second controller of the OBCS 810. For example, the controller of the vehicle 800 or the OBCS 810 may receive, identify, and/or determine an interrupt signal to initiate the dump. In response to the interrupt signal, the controller may disconnect the output of the generation unit 1010 from the battery, the capacitor module, and/or the motor. Disconnecting the output of the generation unit 1010 from the capacitor, the battery, and/or the motor may ensure that any residual electrical energy in one or more components of the OBCS 810 (for example, the generation unit 1010) is transferred or “dumped” to the battery and/or the capacitor module and therefore control a supply of back-up high voltage. In some embodiments, during the dump, the output of the generation unit 1010 may be connected to a dump load or similar destination when disconnected from the capacitor module, the battery, and/or the motor to prevent damage to any coupled electrical components. In some embodiments, the dump load may comprise a back-up battery, capacitor, or similar energy storage device. In some embodiments, the voltage dump may occur for a period of time and/or at periodic intervals defined by one or more of a time for example since a previous dump, a distance traveled by the vehicle for example since the previous dump, a speed of the vehicle for example since the previous dump, and a power generated and/or output by the generation unit 1010, for example since the previous dump. After the dump is complete (for example, the period of time expires), then the controller may disconnect the dump load from the generation unit output (for example, at a generation unit terminal) and reconnect the battery, the capacitor module, and the motor.
In some embodiments, the voltage dump may comprise opening a contactor that is positioned downstream of the generation unit 1010 or the generators 902. Opening the contactor may disconnect the generation unit 1010 or the generators 902 from the downstream components (for example, the load components for the generation unit 1010 or the generators 902). In some embodiments, the controls for initiating and/or deactivating the dump are conveniently located for the vehicle operator to access or coupled to the controller for the vehicle 800.
In some embodiments, the generation unit 1010 outputs the generated electrical energy in pulses or with a constant signal. For example, the operator or the controller of the vehicle 800 or the second controller of the OBCS 810 In some embodiments, the generation unit 1010 is switchable between outputting the electrical energy in pulses or in the constant signal. The operator may control whether the output is pulsed or constant or the OBCS 810 may automatically control whether the output is pulsed or constant without operator intervention based on current demands of the vehicle 800 and so forth. In some embodiments, when the output is pulsed, the operator and/or the OBCS 810 can control aspects of the pulsed signal, including a frequency of the pulse, an amplitude of the pulse, a duration of each pulse, and so forth. Similarly, when the output is constant, the operator and/or the OBCS 810 may control aspects of the constant signal, including a duration of the signal and an amplitude of the signal.
In some embodiments, the operator of the vehicle 800 can control the height of the fifth wheel 802. For example, the operator determines when to lower the fifth wheel 802 so that it is in contact with the road or a road surface, thereby causing the fifth wheel 802 to rotate. The operator may have controls for whether the fifth wheel 802 is in a raised position, where it is not in contact with the road, or in a lowered position, where it is in contact with the road. Additionally, or alternatively, the operator may have options to control specifics of the raised or lowered position, for example how low to position the fifth wheel 802. Such controls may allow the operator to control the amount of force that the fifth wheel 802 provides on the road or road surface, which may impact the electrical energy generated by the OBCS 810. For example, when the fifth wheel 802 is pressing down on the road surface with a large amount of force, then this force may create more resistance against the fifth wheel 802 rotating when the vehicle 800 is moving, thereby reducing the electrical energy generated by the OBCS 810. On the other hand, when the force on the fifth wheel 802 is small amount of force, then the fifth wheel 802 may lose contact with the road or road surface depending on variations in the road surface, thereby also reducing the electrical energy generated by the OBCS 810. Thus, the controls may provide the operator with the ability to tailor the downward force exerted by the fifth wheel 802 on the road based on road conditions and based on the need for power. In some embodiments, the OBCS 810 may automatically control the force of the fifth wheel 802 on the road to maximize electrical energy generation based on monitoring of the road surface and electrical energy being generated.
Additionally, the operator of the vehicle 800 may choose to extend the fifth wheel 802 so that it contacts the road or retract the fifth wheel 802 so that it does not contact the road based on draft or drag conditions. For example, if the drag increases or is expected to increase based on various conditions, the operator may choose to retract the fifth wheel 802 or keep the fifth wheel 802 retracted. If the drag decreases or is expected to decrease based on conditions, then the operator may choose to extend the fifth wheel 802 or keep it extended. In some embodiments, the OBCS 810 may automatically extend and/or retract the fifth wheel 802 based on drag or potential drag conditions without the operator's involvement.
In some embodiments, the controller may enable retraction and/or extension of one or more of the multiple fifth wheels 802. Such control of the fifth wheels 802 may be based on an analysis of charge remaining in the energy storage components of the electric powered devices and/or a speed or other conditions of power generation using the fifth wheels 802. In some instances, the controller may determine that one or more of the fifth wheels should be extended to generate power based on the movement and/or other conditions of the electric powered device.
In some instances, the fifth wheel 802 is coupled to a gearbox allowing one or more ratios of rotating components to be adapted to the movement of the electric powered device or vehicle. The gearbox may allow the ratios of rotating components to be adjusted to change the amount of power generated by the fifth wheels 802, where the gearbox can allow for increased power generation as needed depending on various conditions.
In some instances, the fifth wheel 802 may be coupled to a gearbox allowing one or more ratios of rotating components to be adapted to the movement of the vehicle, enabling the OBCS 810 and/or an operator to mechanically control and/or adjust rates at which electricity is generated by generators coupled to the fifth wheel(s) 802. For example, the gearbox can enable changing of ratios between the rotation of the fifth wheel(s) 802 of the vehicle based on a speed at which the vehicle is traveling or a grade on which the vehicle is traveling, thereby impacting rotations of the generator and electricity produced by the generator. For example, if the vehicle is traveling slowly or up-hill, or traveling against a current, or into a headwind, the gearbox can be adjusted such that the ratio of the generator and the fifth wheels 802 are closer to each other. If the vehicle is traveling quickly or down-hill, or with a current, or with a tail-wind, the gearbox can be adjusted such that the ratio of the generator and the fifth wheels 802 are such that a single rotation of the fifth wheel 802 results in multiple rotations of the generator via the gearbox, and so forth.
With continued reference to
The shaft 1204 may be operably coupled to a generator 1206. The generator 1206 may be configured to generate energy (e.g., an electrical output) in response to mechanical movement such as the rotation of the shaft 1204. The generator 1206 may be electrically coupled to the vehicle and may provide generated energy to the vehicle, for example to a motor of the vehicle and/or to an energy storage device of the vehicle that includes one or more batteries and/or capacitors (e.g., ultracapacitors) or one or more hypercapacitors.
The roller(s) 1302 may be configured to be in physical contact with a sidewall of the wheel 1301 at any distance away from a center axis of the wheel. For example, the roller(s) 1302 may be in physical contact with a sidewall of the wheel 1301 close to the center axis of the wheel or far from a center axis of the wheel. The roller(s) 1302 may rotate at a greater rotational velocity when in physical contact with the sidewall of the wheel 1301 far from a center axis of the wheel 1301 than when in physical contact with the sidewall of the wheel 1301 near a center axis of the wheel 1301.
With continued reference to
The shaft 1304 may be operably coupled to a generator 1306. The generator 1306 may be configured to generate energy (e.g., an electrical output) in response to mechanical movement such as the rotation of the shaft 1304. The generator 1306 may be electrically coupled to the vehicle and may provide generated energy to the vehicle, for example to a motor of the vehicle and/or to an energy storage device of the vehicle that includes one or more batteries and/or capacitors (e.g., ultracapacitors) or one or more hypercapacitors.
The rotational inertia of the rollers 1302 in the example embodiment of
In some implementations, the rotational inertia of the rollers 1302 can change automatically for example in response to an energy demand of the motor of the vehicle, a rotational velocity of the wheel, and/or desired braking etc. In some implementations, the rotational inertia of the rollers can change in response to a manual user input. The rotational inertia of the roller 1302 can be changed by changing a state of the roller 1302, the shaft 1304 (or other coupling device), and/or changing a state of the generator 1306. In some implementations, a gearbox may change the rotational inertia of the roller 1302 by changing a gear ratio between the roller 1302 and the generator 1306.
The energy source 1401 can include an energy generation or regeneration system. In some implementations, the energy source 1401 can include a solar power generation system. The energy source 1401 can include one or more solar panels and/or solar cells configured to generate an electrical voltage and/or current in response to exposure to light. In some implementations, the energy source 1401 may be included within a vehicle. For example, the energy source 1401 may include an on-board power generation system disposed within and/or on a vehicle and that is mobile with the vehicle. In some implementations, the energy source 1401 may be separate from a vehicle. For example, the energy source 1401 may be stationary or in a fixed location such as a charging station.
The electrical interface 1402 can include a plug configured to mechanically and/or electrically couple the energy source 1401 to the energy storage device 1403. The energy storage device 1403 may be removably coupled to the energy source 1401 via the electrical interface 1402.
The diode 1404A can include one or more diodes configured to conduct an electrical current in one direction. The diode 1404A can be biased toward the energy source 1403. The diode 1404A may be configured to conduct an electrical current from the energy source 1401 to the energy storage device 1403. The diode 1404A may be configured to prevent an electrical current from passing from the energy storage device 1403 to the energy source 1401. The diode 1404A may act as an insulator and prevent an electrical current from passing until a voltage across the diode 1404A exceeds a threshold. The diode 1404A may open to allow a current to pass in response to a voltage across the diode 1404A exceeding a threshold.
The energy storage device 1403 can include one or more devices configured to store energy such as a voltage. The energy storage device 1403 can include one or more capacitors, such as ultracapacitors and/or supercapacitors. The energy storage device 1403 may be configured to receive energy from the energy source 1401 via the electrical interface 1402 and/or the diode 1404A.
The switch 1406 can include one or more electrical switches, relays, circuits, or the like. The switch 1406 may be configured to transition between open and closed states. In a closed state, the switch 1406 may be configured to conduct an electrical current. In a closed state, the switch 1406 may be configured to prevent an electrical current from passing.
The diode 1404B may include similar structural and/or operational features as any of the other diodes shown and/or described herein, such as diode 1404A.
The energy storage device 1405 may receive energy from the energy storage device 1403 via the switch 1406 and/or diode 1404B. The energy storage device 1405 can include one or more devices configured to store energy such as a voltage. The energy storage device 1405 can include one or more batteries. The energy storage device 1405 can include a battery field or battery array. The energy storage device 1405 can include one or more lithium batteries, such as lithium ion batteries, lithium polymer batteries, or the like.
The load 1407 may receive energy from the energy storage device 1405. The load 1407 can include a device configured to consume energy or power. The load 1407 can include a motor of a vehicle.
The vehicle 1450 may include one or more energy storage devices such as capacitors and/or batteries. The vehicle 1450 may be configured to receive energy from the solar charging station 1451. For example, the vehicle 1450 may receive energy from the solar panels 1459 and/or from an energy storage device of the solar charging station 1451. The vehicle 1450 may be configured to store energy from the solar charging station 1451 in a capacitor storage device of the vehicle 1450 such as an ultracapacitor or supercapacitor. The vehicle 1450 may transfer energy from a capacitor storage device to a battery storage device of the vehicle 1450 and/or to a load of the vehicle 1450. Advantageously, the vehicle 1450 may be configured to receive a large amount of energy from the solar charging station 1451 in a short amount of time to store in an electric field of a capacitor storage device which may reduce charge times of the vehicle 1450.
The vehicle 1460 may include one or more energy storage devices such as capacitors and/or batteries. The vehicle 1460 may be configured to receive energy from the solar panels 1461. The vehicle 1460 may be configured to store energy from the solar panels 1461 in a capacitor storage device of the vehicle 1460 such as an ultracapacitor or supercapacitor. The vehicle 1460 may transfer energy from a capacitor storage device to a battery storage device of the vehicle 1460 and/or to a load of the vehicle 1460. Advantageously, the vehicle 1460 may be configured to receive a large amount of energy from the solar panels 1461 in a short amount of time to store in an electric field of a capacitor storage device which may reduce charge times of the vehicle 1460.
In some embodiments the energy source 1501 can include an energy generation or regeneration system. For example, the energy source 1501 can include one or more turbines. A turbine can include one or more blades, fans, vanes, and/or rotors. A turbine can include one or more generators. A turbine can be configured to generate energy, such as an electrical current and/or voltage in response to a rotation of the turbine. A turbine can be configured to rotate in response to a fluid flow across the turbine such as a water flow and/or air flow. In some implementations, the energy source 1501 may be included within a vehicle. For example, the energy source 1501 may include an on-board power generation system disposed within and/or on a vehicle and that is mobile with the vehicle. In some implementations, the energy source 1501 may be separate from a vehicle. For example, the energy source 1501 may be stationary or in a fixed location such as a charging station.
The energy storage device 1503 can include one or more devices configured to store energy such as a voltage. The energy storage device 1503 can include one or more capacitors, such as ultracapacitors and/or supercapacitors. The energy storage device 1503 may be configured to receive energy from the energy source 1501 via the electrical interface 1502 and/or the diode 1504A.
The energy storage device 1505 may receive energy from the energy storage device 1503 via the switch 1506 and/or diode 1504B. The energy storage device 1505 can include one or more devices configured to store energy such as a voltage. The energy storage device 1505 can include one or more batteries. The energy storage device 1505 can include a battery field or battery array. The energy storage device 1505 can include one or more lithium batteries, such as lithium ion batteries, lithium polymer batteries, or the like.
The load 1507 may receive energy from the energy storage device 1505. The load 1507 can include a device configured to consume energy or power. The load 1507 can include a motor of a vehicle.
The vehicle 1520 may include one or more energy storage devices such as capacitors and/or batteries. The vehicle 1520 may be configured to receive energy from the turbine charging station 1521. For example, the vehicle 1520 may receive energy from the turbine 1529, generator, and/or from an energy storage device of the turbine charging station 1521. The vehicle 1520 may be configured to store energy from the turbine charging station 1521 in a capacitor storage device of the vehicle 1450 such as an ultracapacitor or supercapacitor. The vehicle 1520 may transfer energy from a capacitor storage device to a battery storage device of the vehicle 1520 and/or to a load of the vehicle 1520. Advantageously, the vehicle 1520 may be configured to receive a large amount of energy from the turbine charging station 1521 in a short amount of time to store in an electric field of a capacitor storage device which may reduce charge times of the vehicle 1520.
The vehicle 1550 may include a generator 1552. The generator 1552 may generate energy in response to a rotation of the turbine 1551. The vehicle 1550 may include one or more energy storage devices such as energy storage device 1553 and energy storage device 1555. Energy storage device 1553 can include one or more capacitors such as ultracapacitors and/or supercapacitors. Energy storage device 1555 can include one or more batteries. The energy storage device 1553 may be configured to receive and store energy from the generator 1552. The energy storage device 1553 may transfer energy to the energy storage device 1555 and/or to the motor 1557. Advantageously, the energy storage device 1553 may be configured to receive a large amount of energy from the generator 1552 in a short amount of time to store in an electric field of the energy storage device 1553 which may reduce charge times of the vehicle 1550.
The vehicle 1560 may include a generator 1562. The generator 1562 may generate energy in response to a rotation of the turbine 1561. The vehicle 1560 may include one or more energy storage devices such as energy storage device 1563 and energy storage device 1565. Energy storage device 1563 can include one or more capacitors such as ultracapacitors and/or supercapacitors. Energy storage device 1565 can include one or more batteries. The energy storage device 1563 may be configured to receive and store energy from the generator 1562. The energy storage device 1563 may transfer energy to the energy storage device 1565 and/or to the motor 1567. Advantageously, the energy storage device 1563 may be configured to receive a large amount of energy from the generator 1562 in a short amount of time to store in an electric field of the energy storage device 1563 which may reduce charge times of the vehicle 1560.
The vehicle 1570 may include a generator 1572. The generator 1572 may generate energy in response to a rotation of the turbine 1571. The vehicle 1570 may include one or more energy storage devices such as energy storage device 1573 and energy storage device 1575. Energy storage device 1573 can include one or more capacitors such as ultracapacitors and/or supercapacitors. Energy storage device 1575 can include one or more batteries. The energy storage device 1573 may be configured to receive and store energy from the generator 1572. The energy storage device 1573 may transfer energy to the energy storage device 1575 and/or to the motor 1577. Advantageously, the energy storage device 1573 may be configured to receive a large amount of energy from the generator 1572 in a short amount of time to store in an electric field of the energy storage device 1573 which may reduce charge times of the vehicle 1570.
As used herein, “system,” “instrument,” “apparatus,” and “device” generally encompass both the hardware (for example, mechanical and electronic) and, in some implementations, associated software (for example, specialized computer programs for graphics control) components.
It is to be understood that not necessarily all objects or advantages may be achieved in accordance with any particular embodiment described herein. Thus, for example, those skilled in the art will recognize that certain embodiments may be configured to operate in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other objects or advantages as may be taught or suggested herein.
Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors including computer hardware. The code modules may be stored on any type of non-transitory computer-readable medium or computer storage device, such as hard drives, solid state memory, optical disc, and/or the like. The systems and modules may also be transmitted as generated data signals (for example, as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and may take a variety of forms (for example, as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage such as, for example, volatile or non-volatile storage.
Many other variations than those described herein will be apparent from this disclosure. For example, depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (for example, not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, for example, through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. In addition, different tasks or processes can be performed by different machines and/or computing systems that can function together.
The various illustrative logical blocks, modules, and algorithm elements described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and elements have been described herein generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
The various features and processes described herein may be used independently of one another, or may be combined in various ways. All possible combinations and sub-combinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
The various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a general purpose processor, a digital signal processor (“DSP”), an application specific integrated circuit (“ASIC”), a field programmable gate array (“FPGA”) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor can include electrical circuitry configured to process computer-executable instructions. In another embodiment, a processor includes an FPGA or other programmable devices that performs logic operations without processing computer-executable instructions. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor may also include primarily analog components. For example, some, or all, of the signal processing algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.
The elements of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module stored in one or more memory devices and executed by one or more processors, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art. An example storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The storage medium can be volatile or nonvolatile. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. 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 or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, and so forth, may be either X, Y, or Z, or any combination thereof (for example, X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
Unless otherwise explicitly stated, articles such as “a” or “an” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.
All of the methods and processes described herein may be embodied in, and partially or fully automated via, software code modules executed by one or more general purpose computers. For example, the methods described herein may be performed by the computing system and/or any other suitable computing device. The methods may be executed on the computing devices in response to execution of software instructions or other executable code read from a tangible computer readable medium. A tangible computer readable medium is a data storage device that can store data that is readable by a computer system. Examples of computer readable mediums include read-only memory, random-access memory, other volatile or non-volatile memory devices, CD-ROMs, magnetic tape, flash drives, and optical data storage devices.
It should be emphasized that many variations and modifications may be made to the herein-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The section headings used herein are merely provided to enhance readability and are not intended to limit the scope of the embodiments disclosed in a particular section to the features or elements disclosed in that section. The foregoing description details certain embodiments. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the systems and methods can be practiced in many ways. As is also stated herein, it should be noted that the use of particular terminology when describing certain features or aspects of the systems and methods should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the systems and methods with which that terminology is associated.
Those of skill in the art would understand that information, messages, and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
This application is a divisional of U.S. patent application Ser. No. 17/950,712, filed Sep. 22, 2022, which is a continuation-in-part of U.S. patent application Ser. No. 17/870,667, filed Jul. 21, 2022 which is a continuation-in-part of U.S. patent application Ser. No. 17/541,159, filed Dec. 2, 2021, which is a continuation of U.S. patent application Ser. No. 17/332,088, filed May 27, 2021, now issued as U.S. Pat. No. 11,222,750, which claims benefit of priority to U.S. Provisional Patent Application No. 63/164,474, filed Mar. 22, 2021. U.S. patent application Ser. No. 17/950,712, filed Sep. 22, 2022, is a continuation-in-part of U.S. patent application Ser. No. 17/872,887, filed Jul. 25, 2022, which is a continuation of U.S. patent application Ser. No. 17/666,266, filed Feb. 7, 2022, now issued as U.S. Pat. No. 11,432,123, which is a continuation-in-part of U.S. patent application Ser. No. 17/410,272, filed Aug. 24, 2021, now issued as U.S. Pat. No. 11,289,974, which claims benefit of priority to U.S. Provisional Patent Application No. 63/140,805, filed Jan. 23, 2021, and which is a continuation-in-part of U.S. patent application Ser. No. 17/332,824, filed May 27, 2021, which claims benefit of priority to U.S. Provisional Patent Application No. 63/164,474, filed Mar. 22, 2021, and which claims benefit of priority to U.S. Provisional Patent Application No. 63/140,805, filed Jan. 23, 2021, and which is a continuation-in-part of U.S. Patent Application No. 17/141,518, filed Jan. 5, 2021, now issued as U.S. Pat. No. 11,133,729, which is a continuation-in-part of U.S. patent application Ser. No. 16/847,538, filed Apr. 13, 2020, which claims benefit of priority and is related to U.S. Provisional Patent Application No. 62/858,902, filed Jun. 7, 2019, U.S. Provisional Patent Application No. 62/883,523, filed Aug. 6, 2019, and U.S. Provisional Patent Application No. 62/967,406, filed Jan. 29, 2020. The disclosure of each of the aforementioned applications is incorporated herein in its entirety for all purposes. Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 CFR 1.57.
| Number | Name | Date | Kind |
|---|---|---|---|
| 1751577 | Cole | Mar 1930 | A |
| 2451965 | Longenecker | Oct 1948 | A |
| 2660443 | Miller | Nov 1953 | A |
| 3859589 | Rush | Jan 1975 | A |
| 3891044 | Tiede | Jun 1975 | A |
| 3943370 | Watanabe | Mar 1976 | A |
| 3961678 | Hirano et al. | Jun 1976 | A |
| 3978936 | Schwartz | Sep 1976 | A |
| 4214160 | Fies et al. | Jul 1980 | A |
| 4314160 | Boodman et al. | Feb 1982 | A |
| 4364448 | Ikuma | Dec 1982 | A |
| 4404513 | Campen | Sep 1983 | A |
| 4476947 | Rynbrandt | Oct 1984 | A |
| 4539496 | Thomas et al. | Sep 1985 | A |
| 4579188 | Facer | Apr 1986 | A |
| 5045646 | Musachio | Sep 1991 | A |
| 5078227 | Becker | Jan 1992 | A |
| 5086857 | Dale | Feb 1992 | A |
| 5105776 | Tsuchiya | Apr 1992 | A |
| 5316101 | Gannon | May 1994 | A |
| 5412293 | Minezawa et al. | May 1995 | A |
| 5491390 | McGreen | Feb 1996 | A |
| 5671821 | McGreen | Sep 1997 | A |
| 5680907 | Weihe | Oct 1997 | A |
| 5710504 | Pascual et al. | Jan 1998 | A |
| 5735363 | Horovitz et al. | Apr 1998 | A |
| 5767663 | Lu | Jun 1998 | A |
| 5921334 | Al-Dokhi | Jul 1999 | A |
| 5992553 | Morrison | Nov 1999 | A |
| 6064178 | Miller | May 2000 | A |
| 6065557 | von Keyserling | May 2000 | A |
| 6220381 | Damron et al. | Apr 2001 | B1 |
| 6390215 | Kodama | May 2002 | B1 |
| 6502842 | Ko | Jan 2003 | B2 |
| 6531838 | Parks | Mar 2003 | B2 |
| 6703716 | Chiu | Mar 2004 | B2 |
| 6717280 | Bienville | Apr 2004 | B1 |
| 6987327 | Lucatero | Jan 2006 | B1 |
| 7183746 | Carter | Feb 2007 | B1 |
| 7239887 | Sandhu | Jul 2007 | B1 |
| 7279799 | McCauley | Oct 2007 | B1 |
| 7514803 | Wilks | Apr 2009 | B2 |
| 7547980 | Harrison | Jun 2009 | B2 |
| 7628236 | Brown | Dec 2009 | B1 |
| 7753010 | Rutledge | Jul 2010 | B2 |
| 7913783 | Elmaleh | Mar 2011 | B2 |
| 8063609 | Salasoo et al. | Nov 2011 | B2 |
| 8089168 | Chevrette | Jan 2012 | B2 |
| 8206263 | Tsuchikawa | Jun 2012 | B2 |
| 8347999 | Koelsch et al. | Jan 2013 | B2 |
| 8573346 | Duignan | Nov 2013 | B2 |
| 8643201 | Scott | Feb 2014 | B2 |
| 8712620 | Jackson | Apr 2014 | B2 |
| 8723344 | Dierickx | May 2014 | B1 |
| 8796987 | Scheucher | Aug 2014 | B2 |
| 8872368 | Kim et al. | Oct 2014 | B1 |
| 8907631 | Gurries | Dec 2014 | B1 |
| 8928281 | Murase et al. | Jan 2015 | B2 |
| 9104537 | Penilla | Aug 2015 | B1 |
| 9236761 | Strothmann | Jan 2016 | B2 |
| 9242698 | Frieden | Jan 2016 | B2 |
| 9288270 | Penilla | Mar 2016 | B1 |
| 9321357 | Caldeira et al. | Apr 2016 | B2 |
| 9376971 | Luther | Jun 2016 | B2 |
| 9415660 | Koelsch | Aug 2016 | B2 |
| 9457666 | Caldeira et al. | Oct 2016 | B2 |
| 9838869 | Bye | Dec 2017 | B1 |
| 9981553 | Schafer et al. | May 2018 | B2 |
| 10077056 | Fields et al. | Sep 2018 | B1 |
| 10077752 | Lee et al. | Sep 2018 | B1 |
| 10157050 | Kotani | Dec 2018 | B2 |
| 10293702 | Tu et al. | May 2019 | B2 |
| 10513180 | Quill | Dec 2019 | B2 |
| 10586024 | Patton | Mar 2020 | B1 |
| 10599155 | Konrardy | Mar 2020 | B1 |
| 10664917 | Wasserman | May 2020 | B1 |
| 10787089 | Macaluso | Sep 2020 | B1 |
| 10795380 | Patton | Oct 2020 | B1 |
| 10797564 | Griggs | Oct 2020 | B1 |
| 10850713 | O'Hara | Dec 2020 | B2 |
| 10889186 | Schutt | Jan 2021 | B2 |
| 10903679 | Schmalzrieth et al. | Jan 2021 | B2 |
| 11007878 | Kamino et al. | May 2021 | B2 |
| 11072254 | Macaluso | Jul 2021 | B1 |
| 11117481 | Macaluso | Sep 2021 | B2 |
| 11130415 | Macaluso | Sep 2021 | B2 |
| 11133729 | Macaluso | Sep 2021 | B2 |
| 11222750 | Macaluso | Jan 2022 | B1 |
| 11289974 | Macaluso | Mar 2022 | B2 |
| 11299054 | Macaluso | Apr 2022 | B2 |
| 11318856 | Macaluso | May 2022 | B2 |
| 11322311 | Macaluso | May 2022 | B2 |
| 11431225 | Macaluso | Aug 2022 | B2 |
| 11432123 | Macaluso | Aug 2022 | B2 |
| 11458853 | Macaluso | Oct 2022 | B2 |
| 11472306 | Macaluso | Oct 2022 | B1 |
| 11548399 | Macaluso | Jan 2023 | B1 |
| 11551486 | Everett | Jan 2023 | B1 |
| 11577606 | Macaluso | Feb 2023 | B1 |
| 11587740 | Macaluso | Feb 2023 | B2 |
| 11618332 | Macaluso | Apr 2023 | B1 |
| 11628724 | Macaluso | Apr 2023 | B1 |
| 11738641 | Macaluso | Aug 2023 | B1 |
| 11837411 | Macaluso | Dec 2023 | B2 |
| 11897355 | Macaluso | Feb 2024 | B2 |
| 11919387 | Macaluso | Mar 2024 | B1 |
| 20030071464 | Chiu | Apr 2003 | A1 |
| 20030139859 | Hanada | Jul 2003 | A1 |
| 20030184258 | VonderHaar | Oct 2003 | A1 |
| 20040012205 | Sua-An | Jan 2004 | A1 |
| 20040262062 | Berbari et al. | Dec 2004 | A1 |
| 20050093370 | Amano et al. | May 2005 | A1 |
| 20050224263 | Vasilantone | Oct 2005 | A1 |
| 20060238258 | D'Amore | Oct 2006 | A1 |
| 20070013244 | Kinkaid | Jan 2007 | A1 |
| 20070024266 | Yurgil | Feb 2007 | A1 |
| 20070075677 | Alvarez-Troncoso | Apr 2007 | A1 |
| 20070090702 | Schiller | Apr 2007 | A1 |
| 20070187957 | Harrison | Aug 2007 | A1 |
| 20070208468 | Sankaran et al. | Sep 2007 | A1 |
| 20080066979 | Carter | Mar 2008 | A1 |
| 20080215700 | Pillar et al. | Sep 2008 | A1 |
| 20080223637 | Bartilson | Sep 2008 | A1 |
| 20080289890 | Stoltzfus | Nov 2008 | A1 |
| 20080297109 | Sandberg et al. | Dec 2008 | A1 |
| 20090033254 | Nagashima et al. | Feb 2009 | A1 |
| 20090079417 | Mort et al. | Mar 2009 | A1 |
| 20090145674 | Lee | Jun 2009 | A1 |
| 20090168305 | Fleig et al. | Jul 2009 | A1 |
| 20090194998 | Lin | Aug 2009 | A1 |
| 20090230766 | Miyama | Sep 2009 | A1 |
| 20090250276 | Goodwin et al. | Oct 2009 | A1 |
| 20090256450 | Chevrette | Oct 2009 | A1 |
| 20100019718 | Salasoo et al. | Jan 2010 | A1 |
| 20100116574 | Gilmore | May 2010 | A1 |
| 20100117600 | Fazakas | May 2010 | A1 |
| 20100270810 | Liebermann et al. | Oct 2010 | A1 |
| 20100327600 | Koelsch | Dec 2010 | A1 |
| 20110014501 | Scheucher | Jan 2011 | A1 |
| 20110025068 | Campbell | Feb 2011 | A1 |
| 20110089760 | Castelaz et al. | Apr 2011 | A1 |
| 20110100735 | Flett | May 2011 | A1 |
| 20110106329 | Donnelly et al. | May 2011 | A1 |
| 20110140518 | Hattori | Jun 2011 | A1 |
| 20110163717 | Gale | Jul 2011 | A1 |
| 20110189507 | Reis | Aug 2011 | A1 |
| 20110200193 | Blitz et al. | Aug 2011 | A1 |
| 20110302078 | Failing | Dec 2011 | A1 |
| 20110320074 | Erlston et al. | Dec 2011 | A1 |
| 20120012406 | Stoicoviciu | Jan 2012 | A1 |
| 20120037438 | Schultz | Feb 2012 | A1 |
| 20120054095 | Lesandro | Mar 2012 | A1 |
| 20120068537 | Hintz et al. | Mar 2012 | A1 |
| 20120237799 | Jiang | Sep 2012 | A1 |
| 20120309455 | Klose et al. | Dec 2012 | A1 |
| 20130015668 | Chang et al. | Jan 2013 | A1 |
| 20130067253 | Tsuda | Mar 2013 | A1 |
| 20130081886 | Jaberian | Apr 2013 | A1 |
| 20130096759 | Breton et al. | Apr 2013 | A1 |
| 20130119665 | Berbari | May 2013 | A1 |
| 20130257144 | Caldeira et al. | Oct 2013 | A1 |
| 20130257145 | Caldeira et al. | Oct 2013 | A1 |
| 20130266826 | Cowperthwaite | Oct 2013 | A1 |
| 20130332014 | Jackson | Dec 2013 | A1 |
| 20140001905 | Schawitsch | Jan 2014 | A1 |
| 20140091573 | Berbari | Apr 2014 | A1 |
| 20140132155 | Strothmann | May 2014 | A1 |
| 20140197780 | Imamura | Jul 2014 | A1 |
| 20140210398 | Powell | Jul 2014 | A1 |
| 20140244082 | Caron | Aug 2014 | A1 |
| 20140266004 | Andrews, Jr. | Sep 2014 | A1 |
| 20140266070 | Kurtzman | Sep 2014 | A1 |
| 20140283092 | Mowatt | Sep 2014 | A1 |
| 20140285209 | Stichowski et al. | Sep 2014 | A1 |
| 20140350764 | Arai et al. | Nov 2014 | A1 |
| 20140368041 | Tu et al. | Dec 2014 | A1 |
| 20150008867 | Smychkovich | Jan 2015 | A1 |
| 20150014991 | Al Jaeedi et al. | Jan 2015 | A1 |
| 20150089981 | Renfro | Apr 2015 | A1 |
| 20150210287 | Penilla | Jul 2015 | A1 |
| 20150222553 | Macdonald | Aug 2015 | A1 |
| 20150249362 | Bridgelall et al. | Sep 2015 | A1 |
| 20150260835 | Widmer et al. | Sep 2015 | A1 |
| 20150262154 | Wolfson | Sep 2015 | A1 |
| 20150304406 | Penilla | Oct 2015 | A1 |
| 20150343909 | Hikiri | Dec 2015 | A1 |
| 20150347121 | Harumoto | Dec 2015 | A1 |
| 20150363855 | Wu | Dec 2015 | A1 |
| 20160034952 | Parkin | Feb 2016 | A1 |
| 20160071338 | McQuade | Mar 2016 | A1 |
| 20160089981 | Kodawara | Mar 2016 | A1 |
| 20160111907 | Lynds | Apr 2016 | A1 |
| 20160164373 | Liao et al. | Jun 2016 | A1 |
| 20160189311 | Erickson | Jun 2016 | A1 |
| 20160236578 | Liao | Aug 2016 | A1 |
| 20160243960 | Wood | Aug 2016 | A1 |
| 20160297317 | Huang et al. | Oct 2016 | A1 |
| 20160298589 | Setterberg | Oct 2016 | A1 |
| 20160348788 | Lemmers | Dec 2016 | A1 |
| 20170025857 | Matthews | Jan 2017 | A1 |
| 20170036551 | Wu | Feb 2017 | A1 |
| 20170063124 | Yu et al. | Mar 2017 | A1 |
| 20170077534 | Guidry et al. | Mar 2017 | A1 |
| 20170117720 | Yung | Apr 2017 | A1 |
| 20170131999 | Dolby et al. | May 2017 | A1 |
| 20170142766 | Kim | May 2017 | A1 |
| 20170176540 | Omi | Jun 2017 | A1 |
| 20170191459 | Zhang | Jul 2017 | A1 |
| 20170363433 | Tennent | Dec 2017 | A1 |
| 20170366017 | Clay et al. | Dec 2017 | A1 |
| 20180009329 | Tellez | Jan 2018 | A1 |
| 20180083469 | Bauer et al. | Mar 2018 | A1 |
| 20180154779 | Chol | Jun 2018 | A1 |
| 20180156144 | Inoue | Jun 2018 | A1 |
| 20180166750 | Chang | Jun 2018 | A1 |
| 20180204173 | Painter | Jul 2018 | A1 |
| 20180204253 | Painter | Jul 2018 | A1 |
| 20180204281 | Painter | Jul 2018 | A1 |
| 20180205242 | Kelly-Morgan et al. | Jul 2018 | A1 |
| 20180215272 | Vitullo et al. | Aug 2018 | A1 |
| 20180254732 | Smolenaers | Sep 2018 | A1 |
| 20180312159 | Jent, II | Nov 2018 | A1 |
| 20180328745 | Nagy | Nov 2018 | A1 |
| 20180351397 | Aharoni | Dec 2018 | A1 |
| 20180370537 | Wu | Dec 2018 | A1 |
| 20190001804 | Wilhide | Jan 2019 | A1 |
| 20190004580 | Wilhide | Jan 2019 | A1 |
| 20190044359 | Gordon et al. | Feb 2019 | A1 |
| 20190077254 | Stanley | Mar 2019 | A1 |
| 20190103639 | Guglielmo et al. | Apr 2019 | A1 |
| 20190108010 | Tillman | Apr 2019 | A1 |
| 20190140245 | Mensch | May 2019 | A1 |
| 20190176802 | Kim | Jun 2019 | A1 |
| 20190184843 | Jung et al. | Jun 2019 | A1 |
| 20190199104 | Shim | Jun 2019 | A1 |
| 20190202429 | Richter | Jul 2019 | A1 |
| 20190212997 | Sangameswaran et al. | Jul 2019 | A1 |
| 20190217720 | Treharne et al. | Jul 2019 | A1 |
| 20190245375 | Schmalzrieth et al. | Aug 2019 | A1 |
| 20190292973 | Jiang et al. | Sep 2019 | A1 |
| 20190329650 | Quill | Oct 2019 | A1 |
| 20190351895 | Ben-Ari | Nov 2019 | A1 |
| 20190351899 | Adam | Nov 2019 | A1 |
| 20190351948 | Derissaint | Nov 2019 | A1 |
| 20190359080 | Hellgren | Nov 2019 | A1 |
| 20190362922 | Bae et al. | Nov 2019 | A1 |
| 20190383627 | Nangeroni et al. | Dec 2019 | A1 |
| 20200006716 | Wagoner | Jan 2020 | A1 |
| 20200039379 | Schlosser | Feb 2020 | A1 |
| 20200094695 | Bowman | Mar 2020 | A1 |
| 20200098032 | August | Mar 2020 | A1 |
| 20200101858 | Kuroda | Apr 2020 | A1 |
| 20200136414 | Patsos | Apr 2020 | A1 |
| 20200174780 | Gintz | Jun 2020 | A1 |
| 20200184591 | Balu | Jun 2020 | A1 |
| 20200186620 | Golgiri et al. | Jun 2020 | A1 |
| 20200202645 | Gintz | Jun 2020 | A1 |
| 20200203986 | Barreau | Jun 2020 | A1 |
| 20200207209 | Engel | Jul 2020 | A1 |
| 20200238929 | Wippler | Jul 2020 | A1 |
| 20200241555 | Dogishi | Jul 2020 | A1 |
| 20200244088 | Will et al. | Jul 2020 | A1 |
| 20200249822 | Penilla | Aug 2020 | A1 |
| 20200258325 | Maria | Aug 2020 | A1 |
| 20200295412 | Chen | Sep 2020 | A1 |
| 20200324763 | Switkes et al. | Oct 2020 | A1 |
| 20200353839 | Tarchinski et al. | Nov 2020 | A1 |
| 20200381784 | Yamamoto | Dec 2020 | A1 |
| 20200384873 | Macaluso | Dec 2020 | A1 |
| 20200384879 | Ebisu et al. | Dec 2020 | A1 |
| 20200393259 | Gantt, Jr. | Dec 2020 | A1 |
| 20210001737 | Hoess et al. | Jan 2021 | A1 |
| 20210046833 | Macaluso | Feb 2021 | A1 |
| 20210046841 | Cun | Feb 2021 | A1 |
| 20210065073 | Maeda et al. | Mar 2021 | A1 |
| 20210080943 | Iwamoto | Mar 2021 | A1 |
| 20210110323 | Munoz et al. | Apr 2021 | A1 |
| 20210152665 | Hart | May 2021 | A1 |
| 20210167988 | Harata et al. | Jun 2021 | A1 |
| 20210173411 | Rao et al. | Jun 2021 | A1 |
| 20210181736 | Reda | Jun 2021 | A1 |
| 20210183175 | Dunger | Jun 2021 | A1 |
| 20210188101 | Abu Qahouq | Jun 2021 | A1 |
| 20210188115 | Kazuno | Jun 2021 | A1 |
| 20210197687 | Searcy | Jul 2021 | A1 |
| 20210224148 | Liu | Jul 2021 | A1 |
| 20210229687 | Hashimoto et al. | Jul 2021 | A1 |
| 20210276443 | Namiki | Sep 2021 | A1 |
| 20210284043 | Wang | Sep 2021 | A1 |
| 20210312544 | Inoue et al. | Oct 2021 | A1 |
| 20210313121 | Macaluso | Oct 2021 | A1 |
| 20210334913 | Klein | Oct 2021 | A1 |
| 20210405996 | Takatsuna et al. | Dec 2021 | A1 |
| 20220016941 | Sams | Jan 2022 | A1 |
| 20220028625 | Macaluso | Jan 2022 | A1 |
| 20220028627 | Macaluso | Jan 2022 | A1 |
| 20220050143 | Maeda et al. | Feb 2022 | A1 |
| 20220052582 | Giannotta | Feb 2022 | A1 |
| 20220068570 | Macaluso | Mar 2022 | A1 |
| 20220097560 | Sakurai | Mar 2022 | A1 |
| 20220109314 | Pena | Apr 2022 | A1 |
| 20220111758 | Ijaz et al. | Apr 2022 | A1 |
| 20220167134 | Macaluso | May 2022 | A1 |
| 20220179641 | Harata et al. | Jun 2022 | A1 |
| 20220179644 | Harata et al. | Jun 2022 | A1 |
| 20220242261 | Tong | Aug 2022 | A1 |
| 20220244736 | Konrardy | Aug 2022 | A1 |
| 20220253301 | Harata | Aug 2022 | A1 |
| 20220261836 | Kinomura | Aug 2022 | A1 |
| 20220301775 | Macaluso | Sep 2022 | A1 |
| 20220314837 | Gupta | Oct 2022 | A1 |
| 20220334818 | McFarland, Jr. | Oct 2022 | A1 |
| 20220334822 | Sakakibara et al. | Oct 2022 | A1 |
| 20220340035 | Kim | Oct 2022 | A1 |
| 20220360141 | Macaluso | Nov 2022 | A1 |
| 20220360959 | Macaluso | Nov 2022 | A1 |
| 20220374027 | Watts et al. | Nov 2022 | A1 |
| 20220379743 | Salter | Dec 2022 | A1 |
| 20220392336 | Gaither | Dec 2022 | A1 |
| 20220399581 | Wood | Dec 2022 | A1 |
| 20230005305 | Sakurai et al. | Jan 2023 | A1 |
| 20230026897 | Macaluso | Jan 2023 | A1 |
| 20230029080 | Hashimoto | Jan 2023 | A1 |
| 20230038222 | Howell | Feb 2023 | A1 |
| 20230038656 | Salter | Feb 2023 | A1 |
| 20230068432 | Upadhyay et al. | Mar 2023 | A1 |
| 20230077434 | Penilla | Mar 2023 | A1 |
| 20230100927 | Macaluso | Mar 2023 | A1 |
| 20230109674 | Macaluso | Apr 2023 | A1 |
| 20230123166 | Deighton | Apr 2023 | A1 |
| 20230125192 | Macaluso | Apr 2023 | A1 |
| 20230142500 | Marzoughi et al. | May 2023 | A1 |
| 20230143096 | Macaluso | May 2023 | A1 |
| 20230150380 | Macaluso | May 2023 | A1 |
| 20230154692 | Macaluso | May 2023 | A1 |
| 20230155401 | Kuranuki et al. | May 2023 | A1 |
| 20230171574 | Macaluso | Jun 2023 | A1 |
| 20230187145 | Macaluso | Jun 2023 | A1 |
| 20230187757 | Pouyadou | Jun 2023 | A1 |
| 20230223818 | Macaluso | Jul 2023 | A1 |
| 20230261509 | Dalal et al. | Aug 2023 | A1 |
| 20230286400 | Macaluso | Sep 2023 | A1 |
| 20230302962 | Couture et al. | Sep 2023 | A1 |
| 20230336055 | Macaluso | Oct 2023 | A1 |
| 20240087810 | Macaluso | Mar 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 2019025 | Dec 1990 | CA |
| 202100372 | Apr 2022 | CH |
| 102310746 | Jan 2012 | CN |
| 202151998 | Feb 2012 | CN |
| 202294336 | Jul 2012 | CN |
| 102963263 | Mar 2013 | CN |
| 108473063 | Aug 2013 | CN |
| 105804956 | Jul 2016 | CN |
| 106846153 | Jun 2017 | CN |
| 106846153 | Jun 2017 | CN |
| 107117038 | Sep 2017 | CN |
| 108749633 | Nov 2018 | CN |
| 109017323 | Dec 2018 | CN |
| 107117038 | Sep 2019 | CN |
| 110549902 | Dec 2019 | CN |
| 110633815 | Dec 2019 | CN |
| 110633815 | Dec 2019 | CN |
| 107804326 | Jan 2020 | CN |
| 110889601 | Mar 2020 | CN |
| 110889601 | Mar 2020 | CN |
| 213082896 | Apr 2021 | CN |
| 112977043 | Jun 2021 | CN |
| 113479111 | Oct 2021 | CN |
| 215398141 | Jan 2022 | CN |
| 219007578 | May 2023 | CN |
| 102017008723 | May 2018 | DE |
| 102017008723 | May 2018 | DE |
| 102019220366 | Jun 2021 | DE |
| 102011018457 | Jan 2022 | DE |
| 1 253 698 | Oct 2002 | EP |
| 3246776 | Nov 2020 | EP |
| 3839723 | Jun 2021 | EP |
| 3839724 | Jun 2021 | EP |
| 2325201 | Nov 1998 | GB |
| 2002-257026 | Sep 2002 | JP |
| 2003-278633 | Oct 2003 | JP |
| 2011-132873 | Jul 2011 | JP |
| 2015-027164 | Feb 2015 | JP |
| 2016-170600 | Sep 2016 | JP |
| 2016170600 | Sep 2016 | JP |
| 6687274 | Apr 2020 | JP |
| 6687274 | Apr 2020 | JP |
| 3234064 | Sep 2021 | JP |
| 102266609 | Jun 2021 | KR |
| 102266609 | Jun 2021 | KR |
| 2629820 | Sep 2017 | RU |
| 2643016 | Jan 2018 | RU |
| WO 09149769 | Dec 2009 | WO |
| WO 10133863 | Nov 2010 | WO |
| WO 11148531 | Dec 2011 | WO |
| WO-2013051118 | Apr 2013 | WO |
| WO 17030354 | Feb 2017 | WO |
| WO 17213079 | Dec 2017 | WO |
| WO-2017213079 | Dec 2017 | WO |
| WO 18046979 | Mar 2018 | WO |
| WO 18083279 | May 2018 | WO |
| WO-2018083279 | May 2018 | WO |
| WO 19117894 | Jun 2019 | WO |
| WO 19145777 | Aug 2019 | WO |
| WO 19219997 | Nov 2019 | WO |
| WO 19240783 | Dec 2019 | WO |
| WO-2019240783 | Dec 2019 | WO |
| WO 20191367 | Sep 2020 | WO |
| WO-2021187071 | Sep 2021 | WO |
| WO 22015017 | Jan 2022 | WO |
| WO-2022132807 | Jun 2022 | WO |
| WO 22219510 | Oct 2022 | WO |
| WO-2022257769 | Dec 2022 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20230143096 A1 | May 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62858902 | Jun 2019 | US | |
| 62883523 | Aug 2019 | US | |
| 62967406 | Jan 2020 | US | |
| 63140805 | Jan 2021 | US | |
| 63164474 | Mar 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17950712 | Sep 2022 | US |
| Child | 18150522 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17666266 | Feb 2022 | US |
| Child | 17872887 | US | |
| Parent | 17870667 | Jul 2022 | US |
| Child | 17950712 | Sep 2022 | US |
| Parent | 17332088 | May 2021 | US |
| Child | 17541159 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17872887 | Jul 2022 | US |
| Child | 17950712 | US | |
| Parent | 17410272 | Aug 2021 | US |
| Child | 17666266 | US | |
| Parent | 17332824 | May 2021 | US |
| Child | 17410272 | US | |
| Parent | 17141518 | Jan 2021 | US |
| Child | 17332824 | US | |
| Parent | 16847538 | Apr 2020 | US |
| Child | 17141518 | US | |
| Parent | 17541159 | Dec 2021 | US |
| Child | 17870667 | US |
