Patent Description:
The present disclosure relates to charging batteries of electric and/or hybrid vehicles. More particularly, the present disclosure relates to systems and methods for charging vehicles that are part of a fleet of electric and/or hybrid vehicles.

Individual vehicles that are part of a fleet of vehicles can be charged at a vehicle charging facility during periods of low vehicle demand. Charging each of the vehicles within a fleet of electric vehicles can be complex. In order to meet the charging needs of the fleet, the vehicle charging facility may have a vehicle charging station for each of the vehicles, which can cause the vehicle charging facility to have large current draws. Alternatively, the vehicle charging facility can have a limited number of vehicle charging stations. Each of the vehicles can be driven to one of the charging stations for battery charging and be driven away from the charging station when battery charging is complete. This process can be complex and requires humans to drive the vehicles to and from the charging stations. <CIT> discloses an automatic guided vehicle and its charging control method, whereby the recovery work of an automatic guided vehicle having its completely discharged battery is automatically performed to resolve and prevent traffic snarl and reduce the charging time or the charging frequency of the battery. <CIT> discloses an electric vehicle charger comprising an electric power supply, a power coupling element connected with the electric power supply to transfer electric energy derived from the electric power supply to an electric vehicle, a motorized cart having the electric power supply mounted thereon for movement of the electric power supply from a first location to a second location, and a control and communication system connected with the motorized cart so that the electric vehicle charger can move from the first location to the second location by remote control and/or commands from the control and communication system. <CIT> discloses a base charging system configured to provide a charging service to one or more charge receiving vehicles. The base charging system comprises a database, a communications module and a business module. The business module is configured to determine a charging price. One or more charge receiving vehicles is configured to communicate a vehicle payment price for a charging service to the communication module and further configured to receive the charging service from the base station. If the charging service is offered and accepted the charging service is provided. <CIT>discloses mobile battery charging device comprising:a drive system structured to propel the mobile battery charging device;a charging interface structured to engage a charging port of a vehicle that is one of a fleet of vehicles; and a controller structured to:receive information indicative of a status of a battery system of each vehicle, receive a location of a vehicle of the fleet; and command the drive system to move the battery charging device to engage the charging interface with the charging port of the vehicle and to charge the battery of the vehicle.

According to one aspect of the present invention there is provided a mobile battery charging device as defined in claim <NUM>.

According to another aspect of the invention there is provided a method as defined in claim <NUM>.

Preferred features of the invention are recited in the dependent claims.

One embodiment relates to an apparatus. The apparatus includes a vehicle controller and a mobile battery charging device. The controller is structured to communicate information indicative of a status of the battery system of the vehicle over a network. The mobile battery charging device includes a drive system, a charging interface, and a mobile battery charging device controller. The drive system is structured to propel the mobile battery charging device. The charging interface is structured to engage the battery charging port of the vehicle. The mobile battery charging device controller is structured to: receive the information of the state of charge of the battery system of the vehicle; determine a position of the vehicle; and command the drive system to move the mobile battery charging device to engage the charging interface with the battery charging port of the vehicle to charge the battery system of the vehicle.

In some embodiments, the drive system is structured to propel the battery charging device along a mounted track. In some embodiments, the vehicle is parked such that the charging port of the vehicle is in proximity of the overhead track.

Another embodiment relates to an apparatus. The apparatus includes a drive system, a charging interface, and a controller. The drive system is structured to propel a mobile battery charging device. The charging interface is structured to engage a charging port of a vehicle that is one of a fleet of vehicles. The controller is structured to: receive information indicative of a status of a battery system of each vehicle of the fleet of vehicles; determine a charging priority for each of the vehicles; determine a location of the vehicle having the battery system with a highest charging priority; and
command the drive system to move the battery charging device to engage the charging interface with the charging port of the vehicle having the battery with the highest charging priority and to charge the battery of the vehicle.

In some embodiments, the controller is structured to determine the charging priority based on at least one of a state of charge of the battery system, an amount of charge required for the battery system to complete the upcoming mission, and a charging time of the battery system.

In some embodiments, the drive system is structured to propel the battery charging device along a mounted track. In some embodiments, the vehicle is parked in proximity of the track.

Another embodiment relates to a method. The method includes receiving, by a controller, information indicative of a status of a battery system of each vehicle of a fleet of vehicles. The status of the battery system includes one or more of a state of charge (SOC) of the battery system, an amount of charge required for the battery system to complete an upcoming mission, and a charging time of the battery system. The method includes determining, by the controller, a charging priority for each of the vehicles. The method includes determining, by the controller, a location of the vehicle having the battery system with a highest charging priority. The method includes commanding, by the controller, a drive system of a mobile battery charging device to move the battery charging device to engage the charging interface with the charging port of the vehicle having the battery with the highest charging priority and to charge the battery of the vehicle.

Following below are more detailed descriptions of various concepts related to, and implementations of, methods, apparatuses, and systems for charging the batteries of a fleet of electric vehicles, hybrid vehicles, or a combination of electric and hybrid vehicles. The methods, apparatuses, and systems can include a mobile battery charging device that can sequentially charge the batteries of multiple vehicles during a charging time period. The various concepts introduced above and discussed in greater detail below may be implemented in any number of ways, as the concepts described are not limited to any particular manner of implementation. Examples of specific implementations and applications are provided primarily for illustrative purposes.

The systems, apparatuses, and methods of the present disclosure include a mobile battery charging device that can sequentially charge the batteries of multiple vehicles belonging to a fleet of vehicles during a charging time period. In the illustrated embodiments, the charging time period is longer than an amount of time required to charge all of the batteries of the vehicles belonging to the fleet of vehicles. The fleet of vehicles is charged at a charging facility.

In the illustrated embodiments, each of the vehicles includes at least a vehicle controller and a battery charging port coupled to a battery system of the vehicle. The vehicle controller is configured to communicate information indicative of a state of charge (SOC) of a battery or a battery system of the vehicle over a network. A mobile battery charging device within the charging facility can receive the information indicative of the state of charge of the battery system of the vehicle over the network. The mobile battery charging device includes a drive system configured to propel the battery charging device, a charging interface configured to engage the battery charging port of the vehicle, and a controller. The controller is configured to receive the information indicative of the state of charge of the battery system of the vehicle, determine a position of the vehicle, and command the drive system to move the battery charging device to align the charging interface with the battery charging port of the vehicle to charge the battery system of the vehicle.

In the illustrated embodiments, the charging facility includes parking indicators to assist the operator(s) of the vehicles belonging to the fleet of vehicles to park the vehicles in positions that allow the vehicles to be charged by the mobile battery charging device. In some embodiments, the mobile battery charging device charges the battery systems of the vehicles based on an order in which the vehicles are parked along a path defined by the parking indicators. As the mobile battery charging device approaches a next vehicle along the path, the mobile battery charging device can receive information indicative of the SOC of the battery system and/or an amount of charge required for the vehicle to complete its next mission. The mobile battery charging device charges the battery system of the vehicle according to the SOC and/or the amount of charge required for the vehicle to complete its next mission.

In some embodiments, the mobile battery charging device can receive information indicative of the SOC and/or an amount of charge required for the vehicle to complete its next mission from each of the vehicles belonging to the fleet of vehicles. The mobile battery charging device can determine a priority structure for charging the vehicles based on the SOC each of the battery systems of the vehicles, the amount of charge required for each of the vehicles to complete its upcoming mission, and/or a charging time for each of the battery systems of the vehicles. The mobile battery charging device then charges the battery systems of the vehicles according to the priority structure.

Referring to the figures generally, the various embodiments disclosed herein relate to systems, apparatuses, and methods for charging a fleet of vehicles with a mobile charging device including positioning the vehicles so that the vehicles can be accessed by the mobile charging device, transmitting information indicative of the state of charge (SOC) of the battery systems of the each of the vehicles to mobile charging device, and charging each of the vehicles with the mobile charging device.

<FIG> illustrates a fleet of vehicles <NUM> and a charging facility <NUM> according to an embodiment. The fleet of vehicles <NUM> includes a plurality of vehicles <NUM> that can include electric vehicles, hybrid vehicles, or a combination of electric and hybrid vehicles. In some embodiments, the fleet of vehicles <NUM> can include busses, cars (e.g., rental cars, taxis, ridesharing cars, delivery cars, etc.), line-haul trucks, mid-range trucks (e.g., delivery trucks, pickup trucks, etc.), and refuse vehicle trucks. The fleet of vehicles <NUM> is deployed for missions and then returns to the charging facility <NUM>. In some embodiments, the missions can include a predetermined time period, a prescheduled route, or a schedule of routes that each vehicle <NUM> may follow (e.g., city/regional bus routes, school bus routes, delivery routes, etc.). In some embodiments, the missions can be scheduled on an on-demand basis, such that the vehicles <NUM> travel route(s) scheduled on-demand and return the charging facility <NUM> after a predetermined time period or after the route(s) have been completed.

The charging facility <NUM> includes a mobile battery charging device <NUM> that can charge the plurality of vehicles <NUM> during a long parking session in which the available charging time is less than an amount of time required for the mobile battery charging device <NUM> to charge all of vehicles <NUM> in the fleet of vehicles <NUM>. For example, the fleet of vehicles <NUM> can be deployed on missions during the day and return to the charging facility <NUM> at the end of the day and be parked in the charging facility <NUM> overnight.

As shown in <FIG>, each of the vehicles <NUM> includes an engine system <NUM>, a battery system <NUM>, a vehicle controller <NUM>, position sensors <NUM>, battery sensors <NUM>, vehicle subsystems <NUM>, and an operator input/output (I/O) device <NUM>. The battery system <NUM> is structured to provide power to the engine system <NUM> and the vehicle subsystems <NUM>. The battery system <NUM> includes at least one battery <NUM> and a charging port <NUM> coupled to the at last one battery <NUM>. The charging port <NUM> is structured for engagement with the mobile battery charging device <NUM>. In some embodiments, the charging port <NUM> can include at least one conductive element mounted on the vehicle <NUM> that can engage a pantograph. In embodiments in which the pantograph is mounted above the vehicle <NUM>, the charging port <NUM> can be positioned on or proximate a roof of the vehicle <NUM>. In other embodiments, the charging port <NUM> can include a socket structured to receive a plug.

The vehicle subsystems <NUM> may include components including electrically driven vehicle components (e.g., HVAC system, lights, pumps, fans, etc.). The vehicle subsystems <NUM> may also include any powered component used to reduce exhaust emissions or to monitor components used to reduce exhaust emissions, such as selective catalytic reduction (SCR) catalyst, a diesel oxidation catalyst (DOC), a diesel particulate filter (DPF), a diesel exhaust fluid (DEF) doser with a supply of diesel exhaust fluid, a plurality of sensors for monitoring the aftertreatment system (e.g., a nitrogen oxide (NOx) sensor, temperature sensors, etc.), and/or still other components.

As shown in <FIG>, the charging facility <NUM> includes the mobile battery charging device <NUM>. In some embodiments, the charging facility <NUM> may include a system of tracks <NUM> on which the mobile battery charging device <NUM> can travel. In some embodiments, the system of tracks <NUM> are overhead-mounted tracks. The system of tracks <NUM> can define a path of the mobile battery charging device <NUM> from a starting point to an ending point. The charging facility <NUM> can include a plurality of parking indicators <NUM> indicating where operators should park the vehicles <NUM> such that the charging ports <NUM> of each of the vehicles <NUM> are positioned to engage the mobile battery charging device <NUM>. In some embodiments, the parking indicators <NUM> can include a stripe or other indicator painted on a floor of the charging facility. In some embodiments, the parking indicators <NUM> are positioned to facilitate parking the vehicles <NUM> in one or more lines in a side-by-side and/or an end-to-end configuration. The parking indicators <NUM> can define a path of the mobile battery charging device <NUM> from a starting point to an ending point. In some embodiments, the parking indicators <NUM> can include sensors <NUM> that can sense a position of the vehicle <NUM> and communicate with the vehicle controller <NUM> over the network to provide information indicative of the vehicle <NUM> position to the vehicle controller <NUM>. For example, the sensors <NUM> can include a proximity and/or a weight sensor structured to communicate wirelessly with the controller of the vehicle <NUM>. As is described in greater detail below, the vehicle controller <NUM> can be structured to receive information indicative of a position of the vehicle <NUM> from the parking indicators <NUM>. The vehicle controller <NUM> can be structured to send a notification to an operator of the vehicle <NUM> in response to determining, based on the information indicative of the position of the vehicle <NUM>, that the vehicle <NUM> is correctly positioned for battery charging.

The mobile battery charging device <NUM> includes a charging interface <NUM> and a device body <NUM>. The device body <NUM> includes a drive system <NUM>, a mobile battery charging device controller <NUM>, and sensors <NUM>. The charging interface <NUM> is coupled to an electric power grid through the charging facility <NUM> (e.g., via electric wiring within the charging facility <NUM>). The charging interface <NUM> includes a charging port <NUM> and charging interface drive system <NUM> such that the charging interface <NUM> is movable relative to the device body <NUM>. The charging interface drive system <NUM> is structured to position the charging interface <NUM> and the charging port <NUM> of the mobile battery charging device <NUM> proximate the charging ports <NUM> on the vehicles <NUM>. The charging port <NUM> is structured to engage the charging ports <NUM> of the vehicles <NUM>. In the illustrated embodiment, the charging interface drive system <NUM> is structured to extend and retract the charging interface <NUM>. In other embodiments, the charging interface drive system <NUM> can be structured to perform other types of motions (e.g., diagonal and/or rotational motion). In some embodiments, the charging interface <NUM> is a fast-charging device such as a pantograph. The tips of the pantograph that are structured to engage the charging port <NUM> (e.g., one or more conductive elements such as rails, rods, etc.) of the vehicle <NUM> form the charging port <NUM>. In embodiments in which the charging interface <NUM> is a pantograph mounted to the system of tracks <NUM>, the pantograph can extend to engage conductive the element positioned on or proximate a roof of each of the vehicles <NUM> without requiring human intervention. The pantograph can transmit electricity to the conductive element to charge the battery system <NUM> on the vehicle <NUM>. In other embodiments, the charging interface <NUM> can be an extendible structure and the charging port <NUM> can be a plug.

The drive system <NUM> is structured to move the mobile battery charging device <NUM> along the fleet of vehicles <NUM> to charge each of the vehicles <NUM> parked within the charging facility <NUM>. In embodiments in which the charging facility <NUM> includes the system of tracks <NUM>, the drive system <NUM> can include a plurality of wheels and a motor structured to travel along the tracks <NUM>. In other embodiments in which the charging facility includes the plurality of tracks <NUM>, the plurality of tracks <NUM> and the drive system <NUM> can form a conveyor system. In locations in which the charging facility <NUM> does not include the plurality of tracks <NUM>, the drive system <NUM> can include a plurality of wheels and a motor structured to travel along the ground.

The sensors <NUM> can be positioned on the device body <NUM>, the charging interface <NUM>, or a combination of the device body <NUM> and the charging interface <NUM>. The sensors <NUM> can be structured to detect a position of the vehicles <NUM>, the charging ports <NUM>, or both the position of the vehicles <NUM> and the charging ports <NUM>. As described in greater detail below, the mobile battery charging device controller <NUM> is structured to receive information indicative of the position of the vehicle <NUM> and/or the charging ports <NUM> and position the charging interface <NUM> so that the charging interface <NUM> can engage the charging port <NUM> with the charging port <NUM> of the vehicle <NUM>.

Components of the vehicle <NUM> and the mobile battery charging device <NUM> may communicate with each other or components of other devices using any type and any number of wired or wireless connections. For example, a wired connection may include a serial cable, a fiber optic cable, a CAT5 cable, or any other form of wired connection. Wireless connections may include the Internet, Wi-Fi, cellular, radio, Bluetooth, ZigBee, etc. In one embodiment, a controller area network (CAN) bus provides the exchange of signals, information, and/or data. The CAN bus includes any number of wired and wireless connections. Because the vehicle controller <NUM> is communicably coupled to the systems and components in the vehicle <NUM> of <FIG>, the vehicle controller <NUM> is structured to receive data regarding one or more of the components shown in the vehicles <NUM> in <FIG>. For example, the data may include operation data regarding the battery system <NUM>, a position of the vehicle <NUM>, etc. acquired by one or more sensors, such as the sensors <NUM>, <NUM>. As another example, the data may include an output to the operator I/O device <NUM>. As an example, the vehicle controller <NUM> may output a notification through the operator I/O device <NUM> to the operator of the vehicle <NUM> indicating that the vehicle <NUM> is correctly positioned for charging. The vehicle controller <NUM> is structured to communicate with the mobile battery charging device controller <NUM>. For example, the vehicle controller <NUM> may send information indicative of a health of the battery system <NUM>, information indicative of a location of the vehicle <NUM>, and information indicative of an identity of the vehicle <NUM> to the mobile battery charging device controller <NUM>. The function and structure of the vehicle controller <NUM> is described in greater detail in <FIG>.

The sensors <NUM>, <NUM> may be positioned and/or structured to monitor characteristics of various components of the vehicle <NUM>. The position sensor <NUM> is structured to facilitate monitoring the position of the vehicle <NUM> within the charging facility <NUM>. The battery sensor <NUM> is structured to facilitate determining a state of charge (SOC) of the battery <NUM>. In embodiments in which the battery system <NUM> includes more than one battery <NUM>, the battery system <NUM> may include more than one battery sensor <NUM>.

Because the mobile battery charging device controller <NUM> is communicably coupled to the systems and components in the mobile battery charging device <NUM> of <FIG>, the mobile battery charging device controller <NUM> is structured to receive data regarding one or more of the components shown in the mobile battery charging device <NUM> in <FIG>. For example, the data may include a position of the mobile battery charging device <NUM>, a position of the charging interface <NUM> and/or the charging port <NUM>, etc. acquired by one or more sensors, such as the sensors <NUM>. The mobile battery charging device controller <NUM> is structured to communicate with the controllers <NUM> of each of the vehicles <NUM>. For example, the mobile battery charging device controller <NUM> may receive information indicative of a health of the battery system <NUM>, a location of the vehicle <NUM>, and information indicative of an identity of the vehicle <NUM> from one or more of the vehicle controllers <NUM>. The function and structure of the mobile battery charging device controller <NUM> is described in greater detail in <FIG>.

The sensors <NUM> may be positioned and/or structured to monitor operating characteristics of various components of the mobile battery charging device <NUM>. The sensors <NUM> may include a first position sensor structured to facilitate monitoring the position of the mobile battery charging device <NUM>. The sensors <NUM> may include a second position sensor structured to facilitate determining a position of the charging interface <NUM> and/or the charging port <NUM> relative to the device body <NUM>.

Referring now to <FIG>, a schematic diagram of the vehicle controller <NUM> of each of the vehicles <NUM> the fleet of vehicles <NUM> of <FIG> is shown according to an embodiment. As shown in <FIG>, the vehicle controller <NUM> includes a processing circuit <NUM> having a processor <NUM> and a memory device <NUM>, a positioning circuit <NUM>, a battery status determination circuit <NUM>, and a communications interface <NUM>. Generally, the vehicle controller <NUM> is structured to determine the SOC of the battery or batteries <NUM> in the battery system <NUM>, determine a SOC of the battery system <NUM>, and send a battery status of the battery system <NUM> to the mobile battery charging device <NUM>, and facilitate correct positioning of the vehicle <NUM> for charging. The battery status of the battery system <NUM> includes one or more of the SOC of the battery system <NUM>, an amount of charge required for the battery system <NUM> to complete upcoming mission, and a charging time of the battery system <NUM>.

Referring now to <FIG>, a schematic diagram of the controller <NUM> of the mobile battery charging device <NUM> of <FIG> is shown according to an embodiment. As shown in <FIG>, the mobile battery charging device controller <NUM> includes a processing circuit <NUM> having a processor <NUM> and a memory device <NUM>, a battery charging circuit <NUM> and a communications interface <NUM>. Generally, the mobile battery charging device controller <NUM> is structured to receive, from each of the vehicles <NUM>, information indicative of an identity of the vehicle <NUM>, information indicative of a position of the vehicle <NUM>, information indicative of a status of the battery system <NUM> of the vehicle <NUM>, and control the mobile battery charging device <NUM> to travel to the vehicle <NUM> and charge the battery system <NUM> of the vehicle <NUM>. The battery status of the battery system <NUM> includes one or more of the SOC of the battery system <NUM>, an amount of charge required for the battery system <NUM> to complete upcoming mission, and a charging time of the battery system <NUM>. In some embodiments, the mobile battery charging device controller <NUM> is structured to determine a charging priority for each of the vehicles <NUM> based on the battery status (e.g., SOC of the battery system <NUM> of each vehicle <NUM>, the amount of battery charge required for the next mission of each vehicle <NUM>, and/or a charging time for the battery system <NUM>) of each of the vehicles <NUM>. The mobile battery charging device controller <NUM> is structured to determine the priority structure based on the charging priorities of each of the vehicles <NUM>. The mobile battery charging device controller <NUM> is structured to control the mobile battery charging device <NUM> to travel to the vehicles <NUM> and charge the vehicles <NUM> according to the priority structure. In some embodiments, the mobile battery charging device controller <NUM> is also structured to receive an amount of battery charge required for an upcoming mission of the vehicle <NUM>. In such an embodiment, the mobile battery charging device controller <NUM> is structured to determine the priority structure based on the charging priorities of each of the vehicles <NUM>.

In one configuration, the positioning circuit <NUM>, the battery status determination circuit <NUM>, and the battery charging circuit <NUM> are embodied as machine or computer-readable media that is executable by a processor, such as processor <NUM> or processor <NUM>. As described herein and amongst other uses, the machine-readable media facilitates performance of certain operations to enable reception and transmission of data. For example, the machine-readable media may provide an instruction (e.g., command, etc.) to, e.g., acquire data. In this regard, the machine-readable media may include programmable logic that defines the frequency of acquisition of the data (or, transmission of the data). The computer readable media may include code, which may be written in any programming language including, but not limited to, Java or the like and any conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program code may be executed on one processor or multiple remote processors. In the latter scenario, the remote processors may be connected to each other through any type of network (e.g., CAN bus, etc.).

In another configuration, the positioning circuit <NUM>, the battery status determination circuit <NUM>, and the battery charging circuit <NUM> are embodied as hardware units, such as electronic control units. As such, the positioning circuit <NUM>, the battery status determination circuit <NUM>, and the battery charging circuit <NUM> may be embodied as one or more circuitry components including, but not limited to, processing circuitry, network interfaces, peripheral devices, input devices, output devices, sensors, etc. In some embodiments, the positioning circuit <NUM>, the battery status determination circuit <NUM>, and the battery charging circuit <NUM> may take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (IC), discrete circuits, system on a chip (SOCs) circuits, microcontrollers, etc.), telecommunication circuits, hybrid circuits, and any other type of "circuit. " In this regard, the positioning circuit <NUM>, the battery status determination circuit <NUM>, and the battery charging circuit <NUM> may include any type of component for accomplishing or facilitating achievement of the operations described herein. For example, a circuit as described herein may include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, and so on). The positioning circuit <NUM>, the battery status determination circuit <NUM>, and the battery charging circuit <NUM> may also include programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like. The positioning circuit <NUM>, the battery status determination circuit <NUM>, and the battery charging circuit <NUM> may include one or more memory devices for storing instructions that are executable by the processor(s) of the positioning circuit <NUM>, the battery status determination circuit <NUM>, and the battery charging circuit <NUM>. The one or more memory devices and processor(s) may have the same definition as provided herein with respect to the memory device <NUM> and processor <NUM> or the memory device <NUM> and processor <NUM>. In some hardware unit configurations, the positioning circuit <NUM>, the battery status determination circuit <NUM>, and the battery charging circuit <NUM> may be geographically dispersed throughout separate locations in the vehicle and/or the mobile battery charging device <NUM>. Alternatively and as shown, the positioning circuit <NUM>, the battery status determination circuit <NUM>, and the battery charging circuit <NUM> may be embodied in or within a single unit/housing, which is shown as the vehicle controller <NUM> and the mobile battery charging device controller <NUM>.

In the example shown, the vehicle controller <NUM> includes the processing circuit <NUM> having the processor <NUM> and the memory device <NUM>. The processing circuit <NUM> may be structured or configured to execute or implement the instructions, commands, and/or control processes described herein with respect to the positioning circuit <NUM> and the battery status determination circuit <NUM>. The depicted configuration represents the positioning circuit <NUM> and the battery status determination circuit <NUM> as machine or computer-readable media. However, as mentioned above, this illustration is not meant to be limiting as the present disclosure contemplates other embodiments where the positioning circuit <NUM> and the battery status determination circuit <NUM> or at least one circuit of the positioning circuit <NUM> and the battery status determination circuit <NUM> is configured as a hardware unit. All such combinations and variations are intended to fall within the scope of the present disclosure.

In the example shown, the mobile battery charging device controller <NUM> includes the processing circuit <NUM> having the processor <NUM> and the memory device <NUM>. The processing circuit <NUM> may be structured or configured- to execute or implement the instructions, commands, and/or control processes described herein with respect to the battery charging circuit <NUM>. The depicted configuration represents the battery charging circuit <NUM> as machine or computer-readable media. However, as mentioned above, this illustration is not meant to be limiting as the present disclosure contemplates other embodiments where the battery charging circuit <NUM> is configured as a hardware unit. All such combinations and variations are intended to fall within the scope of the present disclosure.

The processors <NUM>, <NUM> may be implemented as one or more general-purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a digital signal processor (DSP), a group of processing components, or other suitable electronic processing components. In some embodiments, the one or more processors may be shared by multiple circuits (e.g., the positioning circuit <NUM> and the battery status determination circuit <NUM>) may comprise or otherwise share the same processor which, in some embodiments, may execute instructions stored, or otherwise accessed, via different areas of memory. Alternatively or additionally, the one or more processors may be structured to perform or otherwise execute certain operations independent of one or more co-processors. In other embodiments, two or more processors may be coupled via a bus to enable independent, parallel, pipelined, or multi-threaded instruction execution. All such variations are intended to fall within the scope of the present disclosure. The memory devices <NUM>, <NUM> (e.g., RAM, ROM, Flash Memory, hard disk storage, etc.) may store data and/or computer code for facilitating the various processes described herein. The memory devices <NUM>, <NUM> may be communicably connected to the processors <NUM>, <NUM>, respectively, to provide computer code or instructions to the processor <NUM> for executing at least some of the processes described herein. Moreover, the memory devices <NUM>, <NUM> may be or include tangible, non-transient volatile memory or non-volatile memory. Accordingly, the memory devices <NUM>, <NUM> may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described herein.

The communications interfaces <NUM>, <NUM> may include wired or wireless interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with various systems, devices, or networks. For example, the communications interfaces <NUM>, <NUM> may include an Ethernet card and port for sending and receiving data via an Ethernet-based communications network and/or a Wi-Fi transceiver for communicating via a wireless communications network. The communications interfaces <NUM>, <NUM> may be structured to communicate via local area networks or wide area networks (e.g., the Internet, etc.) and may use a variety of communications protocols (e.g., IP, LON, Bluetooth, ZigBee, radio, cellular, near field communication, etc.).

The communications interface <NUM> of the vehicle controller <NUM> may facilitate communication between and among the vehicle controller <NUM> and one or more components of the vehicle <NUM> (e.g., components of the battery system <NUM>, the operator I/O device <NUM>, the sensors <NUM>,<NUM>, the parking indicators <NUM> etc.) and the mobile battery charging device controller <NUM>. The communications interface <NUM> of the mobile battery charging device controller <NUM> may facilitate communication between and among the mobile battery charging device controller <NUM> and one or more components of the mobile battery charging device <NUM> (e.g., components of the drive system <NUM>, the charging interface <NUM>, the sensors <NUM>, etc.), and the vehicle controller <NUM>. Communication between and among the controllers <NUM>, <NUM> and the components of the vehicle <NUM> or the mobile battery charging device <NUM>, respectively, may be via any number of wired or wireless connections (e.g., any standard under IEEE <NUM>, etc.). For example, a wired connection may include a serial cable, a fiber optic cable, a CAT5 cable, or any other form of wired connection. In comparison, a wireless connection may include the Internet, Wi-Fi, cellular, Bluetooth, ZigBee, radio, etc. In one embodiment, a controller area network (CAN) bus provides the exchange of signals, information, and/or data. The CAN bus can include any number of wired and wireless connections that provide the exchange of signals, information, and/or data. The CAN bus may include a local area network (LAN), or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The positioning circuit <NUM> of the vehicle controller <NUM> is structured to receive information indicative of a position of the vehicle <NUM> from the sensors <NUM>, <NUM> of the vehicle <NUM> or the sensors <NUM> of the parking indicators <NUM>. The positioning circuit <NUM> is structured to determine a position of the vehicle <NUM> relative to the parking indicators <NUM> based on the information indicative of the position of the vehicle <NUM>. In response to determining that the position of the vehicle <NUM> is acceptable, the positioning circuit <NUM> is structured to notify the operator that the vehicle <NUM> is in an acceptable position via the operator I/O device <NUM>. In some embodiments, the notification may be a visual indication such as a light or a message on a dashboard of the vehicle <NUM>. In some embodiments, the notification may be an auditory notification. In some embodiments, in response to determining that the position of the vehicle <NUM> is unacceptable, the positioning circuit <NUM> is structured to notify the operator that the vehicle <NUM> is in an unacceptable position via the operator I/O device <NUM>. In some embodiments, the notification may be a visual indication such as a light or a message on a dashboard of the vehicle <NUM>. In some embodiments, the notification may be an auditory notification. In some embodiments, the notification may include instructions for correctly positioning the vehicle <NUM>. In some embodiments, in response to determining that the position of the vehicle <NUM> is unacceptable, the positioning circuit <NUM> is structured not to send any notifications to the operator of the vehicle <NUM> (e.g., the absence of the notification indicates that the vehicle <NUM> position is unacceptable).

The battery status determination circuit <NUM> of the vehicle controller <NUM> is structured to receive information indicative of the SOC of each of the one or more batteries <NUM> in the battery system <NUM> from the battery sensor(s) <NUM>. The battery status determination circuit <NUM> is structured to determine the SOC of each of the one or more batteries <NUM>. The battery status determination circuit <NUM> is structured to determine the SOC of the battery system <NUM> based on the SOCs of each of the one or more batteries <NUM>. The battery status determination circuit <NUM> is structured to send the information indicative of the SOC battery system <NUM> to the mobile battery charging device controller <NUM>. In some embodiments, the battery status determination circuit <NUM> is structured to predict an upcoming charge requirement of the battery system <NUM> based on an upcoming mission of the vehicle <NUM>. For example, the battery status determination circuit <NUM> may be structured to retrieve each of the routes that will be travelled by the vehicle <NUM> on the next mission from the memory device <NUM>. The battery status determination circuit <NUM> may be structured to determine the upcoming charge requirement based on the amount of battery charge required for the vehicle <NUM> to complete the upcoming mission. In some embodiments, the battery status determination circuit <NUM> is structured to consider on-route charging opportunities when determining the amount of battery charge required for the vehicle <NUM> to complete the upcoming mission. In some embodiments, the amount of charge can be a percentage of the total storage capacity of the battery system <NUM>. In some embodiments, the battery status determination circuit <NUM> is structured to determine a charge time for the battery system <NUM>. In some embodiments, the battery status determination circuit <NUM> is structured to determine the charge time based on the SOC of the battery system <NUM>. In some embodiments, the battery status determination circuit <NUM> is structured to determine the charge time based on the SOCs and the upcoming charge requirements of the battery system <NUM>. In some embodiments, the battery status determination circuit <NUM> is structured to consider on-route charging opportunities when determining the amount of battery charge required for the vehicle <NUM> to complete the upcoming mission.

The battery status determination circuit <NUM> is structured to send information indicative of the identity of the vehicle <NUM>, the battery status of the battery system <NUM>, the upcoming charge requirement, and/or the information indicative of the position of the vehicle <NUM> to the controller <NUM> of the mobile battery charging device <NUM>.

During charging, the battery status determination circuit <NUM> can be structured to determine that the battery system <NUM> has been charged according to the upcoming charge requirement and/or has been fully charged based on information indicative of the SOC of the battery systems <NUM> received from the battery sensor(s) <NUM>. The battery status determination circuit <NUM> can be structured to send a notification to the battery charging circuit <NUM> of the mobile battery charging device controller <NUM> indicating that the battery system <NUM> has been charged according to the upcoming charge requirement and/or fully charged.

In some embodiments, the battery charging circuit <NUM> is structured to charge the fleet of vehicles <NUM> in a sequential order based on the positions of the vehicles <NUM> in the charging facility <NUM>. In such an embodiment, the mobile battery charging device <NUM> is structured to command the drive system <NUM> to follow a path from a starting point to an ending point and charge the battery systems <NUM> of the vehicles <NUM> as the mobile battery charging device <NUM> encounters each of the vehicles <NUM>. In embodiments in which the drive system <NUM> is structured to travel along the system of mounted tracks <NUM>, the system of mounted tracks <NUM> forms the path. In other embodiments, the mobile battery charging device controller <NUM> can be structured to determine the path based on the positions of parking indicators <NUM> or the path can be programmed into the memory device <NUM> of the mobile battery charging device <NUM>. In some embodiments, the battery charging circuit <NUM> is structured to receive, for each of the vehicles <NUM>, the information indicative of the identity of the vehicle <NUM> and the battery status of the battery system <NUM> of the vehicle <NUM> as the mobile battery charging device <NUM> approaches each vehicle <NUM>. In some embodiments, the battery charging circuit <NUM> is structured to determine the amount of battery charge required for the upcoming mission from the vehicle <NUM>. In some embodiments, the battery charging circuit <NUM> can be structured to retrieve each of the routes that will be travelled by the vehicle <NUM> on the next mission from the memory device <NUM> or another database. The battery charging circuit <NUM> may be structured to determine the upcoming charge requirement based on the amount of battery charge required for the vehicle <NUM> to complete the upcoming mission. In some embodiments, the battery charging circuit <NUM> may be structured to consider on-route charging opportunities in determining the amount of battery charge required for the vehicle <NUM> to complete the upcoming mission. In some embodiments, the amount of charge can be a percentage of the total storage capacity of the battery system <NUM>.

The battery charging circuit <NUM> is structured to determine a relative position of the charging port <NUM> of the vehicle <NUM> and the mobile battery charging device <NUM> based on information received from the sensors <NUM>, <NUM>. The battery charging circuit <NUM> is structured to command the drive system <NUM> of the mobile battery charging device <NUM> to substantially align the mobile battery charging device <NUM> with the charging port <NUM> of the vehicle <NUM>. The battery charging circuit <NUM> is then structured to command the charging device drive system <NUM> to position the charging interface <NUM> proximate the charging port <NUM> of the vehicle <NUM> and engage the charging port <NUM> of the mobile battery charging device <NUM> with the charging port <NUM> of the vehicle <NUM>. The battery charging circuit <NUM> is structured to charge the battery system <NUM> of the vehicle <NUM> based on the battery status of the battery system <NUM>. The battery charging circuit <NUM> can receive a notification from the battery status determination circuit <NUM> of the vehicle <NUM> indicating that the battery system <NUM> has been charged according to the upcoming charge requirement and/or has been fully charged. The battery charging circuit <NUM> is structured to command the charging interface drive system <NUM> to disengage the charging port <NUM> of the mobile battery charging device <NUM> from the charging port <NUM> of the vehicle <NUM>. The battery charging circuit <NUM> is then structured to command the drive system <NUM> to approach the next vehicle <NUM> along the path.

In some embodiments, the battery charging circuit <NUM> is structured to determine a priority structure based on the battery statuses of the battery systems <NUM> of each of the vehicles <NUM>. The battery charging circuit <NUM> is structured to receive the battery statuses of the battery system <NUM>, the information indicative of the identity of the vehicle 18before determining the priority structure. For example, the battery charging circuit <NUM> can be structured to command the drive system <NUM> to travel along the path from the starting point to the ending point and receive the battery statuses of the battery system <NUM> and the information indicative of the identity of the vehicle <NUM> from each of the vehicles <NUM> as the mobile battery charging device <NUM> passes proximate each of the vehicles <NUM>. In another example, the battery charging circuit <NUM> is structured to receive the battery status of the battery system <NUM> and the information indicative of the identity of the vehicle <NUM> from each of the vehicles <NUM> as the vehicles <NUM> enter the charging facility <NUM> or park in the charging facility <NUM>. In some embodiments, the battery charging circuit <NUM> is structured to determine a charge time for each of the battery systems <NUM> of the vehicles <NUM>. In some embodiments, the battery charging circuit <NUM> is structured to determine the charge time based on the SOCs of the battery system <NUM> of each of the vehicles <NUM>. In some embodiments, the battery charging circuit <NUM> is structured to determine the charge time based on the SOCs and the upcoming charge requirements of the battery system <NUM> of each of the vehicles <NUM>. In some embodiments, the battery charging circuit <NUM> is structured to consider on-route charging opportunities when determining the amount of battery charge required for the vehicle <NUM> to complete the upcoming mission.

The battery charging circuit <NUM> is structured to determine the charging priority of each of the vehicles <NUM> based on the battery statuses (e.g., the SOCs of the battery systems <NUM> of each of the vehicles <NUM>, the amount of battery system <NUM> charge required) for the each of the vehicles <NUM> to complete an upcoming mission, and/or the charge times for each of the vehicles <NUM>. The battery charging circuit <NUM> is structured to determine the priority structure of the fleet of vehicles <NUM> based on the charging priorities of each of the vehicles <NUM>. In some embodiments, the battery charging circuit <NUM> is structured to determine the priority structure so that the vehicles <NUM> having the battery systems <NUM> with the lowest SOC, the vehicles <NUM> having the battery systems <NUM> requiring the largest charge to complete the next upcoming mission, and/or the vehicles <NUM> having the battery systems <NUM> that require the longest charge time are charged first. In other embodiments, the battery charging circuit <NUM> is structured to determine the priority structure so that the vehicles <NUM> having the battery systems <NUM> with the highest SOC, the vehicles <NUM> having the battery systems <NUM> requiring the least charge to complete the next upcoming mission, and/or the vehicles <NUM> having the battery systems <NUM> that require the shortest charge time are charged first.

The battery charging circuit <NUM> is structured to retrieve the identity and location of the highest priority vehicle <NUM> in the priority structure. The battery charging circuit <NUM> is structured to command the drive system <NUM> to travel to the vehicle <NUM> having the highest priority. The battery charging circuit <NUM> is structured to charge the battery system <NUM> of the vehicle <NUM> as described above. The battery charging circuit <NUM> is structured to determine the identity of the vehicle <NUM> having the next highest priority according to the priority structure and travel to and charge the next highest priority vehicle <NUM> as described above until the battery systems <NUM> of all of the vehicles <NUM> in the fleet of vehicles <NUM> have been charged.

<FIG> illustrates an exemplary method <NUM> for charging the fleet of vehicles <NUM> with the mobile battery charging device <NUM> to an example. At process <NUM>, the operator drives one of the vehicles <NUM> of the fleet of vehicles <NUM> into the charging facility <NUM> and parks the vehicle <NUM> proximate one of the parking indicators <NUM>. At process <NUM>, the positioning circuit <NUM> receives information indicative of the position of the vehicle <NUM> relative to the parking indicators <NUM>. For example, the positioning circuit <NUM> can receive the information indicative of the position of the vehicle <NUM> from the sensors <NUM> and/or the sensors <NUM>. At process <NUM>, in response to determining that the position of the vehicle <NUM> relative to the parking indicators <NUM> is acceptable, the positioning circuit <NUM> can notify the operator, via the operator I/O device <NUM>, to indicate that the vehicle <NUM> position is acceptable. At process <NUM>, in response to determining that the position of the vehicle <NUM> relative to the parking indicators <NUM> is unacceptable, the positioning circuit <NUM> can indicate that the position of the vehicle <NUM> relative to the parking indicators <NUM> is unacceptable. For example, the positioning circuit <NUM> can either not send a notification to the user (e.g., the absence of the notification indicates that the vehicle <NUM> position is unacceptable) or can send a notification to the operator via the operator I/O device <NUM> indicating that the vehicle <NUM> position is unacceptable. In some embodiments, the notification may provide instructions on how to reposition the vehicle <NUM>.

At process <NUM>, the battery status determination circuit <NUM> receives information indicative of the battery status of the battery system <NUM> of the vehicle <NUM>. The information indicative of the SOC of each of the one or more batteries <NUM> can be determined by at least one battery sensor <NUM>. The battery status determination circuit <NUM> can determine the SOC of the battery system <NUM> based on the SOCs of the one or more batteries <NUM>. At process <NUM>, the battery status determination circuit <NUM> may determine the amount of battery charge required for the vehicle <NUM> to complete the upcoming mission. For example, the battery status determination circuit <NUM> may retrieve information indicative of the upcoming mission from a networked device and determine the amount of battery charge required for the next mission based on a next route or schedule of routes for the mission and/or on-route charging opportunities during the mission. The battery status determination circuit <NUM> may also determine a charging time for the battery system <NUM> based on the amount of battery charge required for the next mission and the SOC of the battery system <NUM>. At process <NUM>, the battery status determination circuit <NUM> sends the information indicative of the status of the battery system <NUM> and information indicative of the identity of the vehicle <NUM> to the mobile battery charging device controller <NUM>.

At process <NUM>, the battery charging circuit <NUM> commands the drive system <NUM> of the mobile battery charging device <NUM> to follow the path until the mobile battery charging device <NUM> approaches a first vehicle <NUM> along the path. In embodiments in which the drive system <NUM> is structured to travel along the system of mounted tracks <NUM>, the system of mounted tracks <NUM> forms the path. In other embodiments, the mobile battery charging device controller <NUM> can be structured to determine the path based on the parking indicators <NUM> or the path can be programmed into the memory device <NUM> of the mobile battery charging device <NUM>. At process <NUM>, the battery charging circuit <NUM> receives the battery status and information indicative of the identity of the vehicle <NUM>. At process <NUM>, the battery charging circuit <NUM> may determine the amount of battery charge required for the upcoming mission. In some embodiments, the battery charging circuit <NUM> may retrieve the amount of battery charge required for the upcoming mission from a database based on the information indicative of the identity of the vehicle <NUM>. The battery charging circuit <NUM> may determine the amount of battery charge required for the upcoming mission based on the route or route(s) the vehicle <NUM> is scheduled to travel during the upcoming mission. The battery charging circuit <NUM> may also determine a charging time for the battery system <NUM> based on the amount of battery charge required for the next mission and the SOC of the battery system <NUM>. At process <NUM>, the battery charging circuit <NUM> sends the information indicative of the status of the battery system <NUM> and information indicative of the identity of the vehicle <NUM> to the mobile battery charging device controller <NUM>.

At process <NUM>, the battery charging circuit <NUM> determines a relative position of the charging port <NUM> of the vehicle <NUM> and the mobile battery charging device <NUM>. At process <NUM>, the battery charging circuit <NUM> commands the drive system <NUM> of the mobile battery charging device <NUM> to substantially align the mobile battery charging device <NUM> with the charging port <NUM> of the vehicle <NUM>. At process <NUM>, the battery charging circuit <NUM> commands the battery charging interface drive system <NUM> to position the charging interface <NUM> proximate the charging port <NUM> of the vehicle <NUM> and engage the charging port <NUM> of the charging interface <NUM> with the charging port <NUM> of the vehicle <NUM>. At process <NUM>, the battery charging circuit <NUM> charges the battery system <NUM> of the vehicle <NUM> based on the SOC of the battery system <NUM> and/or the charge requirement to complete the upcoming mission. At process <NUM>, the battery status determination circuit <NUM> determines that the battery system <NUM> is sufficiently charged and sends a notification to the battery charging circuit <NUM>. The battery status determination circuit <NUM> can determine that the battery system <NUM> is fully charged based on the information indicative of the SOC of the battery system <NUM> determined by the sensor(s) <NUM>. At process <NUM>, the battery charging circuit <NUM> commands the charging interface drive system <NUM> to disengage the charging port <NUM> of the charging interface <NUM> from the charging port <NUM> of the vehicle <NUM>. At process <NUM>, the battery charging circuit <NUM> commands the drive system <NUM> to approach the next vehicle <NUM> along the path.

<FIG> is a flow diagram of a method <NUM> for determining a priority structure for charging the fleet of vehicles <NUM> with the mobile battery charging device <NUM> and charging the fleet of vehicles <NUM> with the mobile battery charging device <NUM> according to the priority structure according to an embodiment. Processes <NUM> - <NUM> are substantially similar to processes <NUM> - <NUM> of the method <NUM>. Processes <NUM> - <NUM> and are shown in <FIG> but are not discussed in detail herein for the sake of brevity.

At process <NUM>, the battery status determination circuit <NUM> receives information indicative of the battery status of the battery system <NUM>. The information indicative of the SOC of each of the one or more batteries <NUM> can be determined by at least one battery sensor <NUM>. The battery status determination circuit <NUM> can determine the SOC of the battery system <NUM> based on the SOCs of the one or more batteries <NUM>. At process <NUM>, the battery status determination circuit <NUM> may determine the amount of battery charge required for the vehicle <NUM> to complete the upcoming mission. In some embodiments, the battery charging circuit <NUM> may retrieve the amount of battery charge required for the upcoming mission from a database based on the information indicative of the identity of the vehicle <NUM>. The battery charging circuit <NUM> may determine the amount of battery charge required for the upcoming mission based on the route or route(s) the vehicle <NUM> is scheduled to travel during the upcoming mission. The battery status determination circuit <NUM> may also determine a charging time for the battery system <NUM> based on the amount of battery charge required for the next mission and the SOC of the battery system <NUM>. At process <NUM>, the battery status determination circuit <NUM> sends the information indicative of the status of the battery system <NUM> and information indicative of the identity of the vehicle <NUM> to the mobile battery charging device controller <NUM>.

At process <NUM>, the battery charging circuit <NUM> determines the priority structure for charging the vehicles <NUM> of the fleet of vehicles <NUM>. In some embodiments, battery charging circuit <NUM> determines the priority structure based on the battery statuses (e.g., the SOCs of the battery systems <NUM>, the amount of charge required for the battery system <NUM> to complete an upcoming mission, and a charge time of the battery systems <NUM>) for each of the vehicles <NUM>. At process <NUM>, the battery charging circuit <NUM> is structured to identify the vehicle <NUM> having the highest priority. At process <NUM>, the charging interface <NUM> commands the drive system <NUM> of the mobile battery charging device <NUM> to travel to the vehicle <NUM> having the highest priority.

At process <NUM>, the battery charging circuit <NUM> determines a relative position of the charging port <NUM> of the vehicle <NUM> and the mobile battery charging device <NUM>. At process <NUM>, the battery charging circuit <NUM> commands the drive system <NUM> of the mobile battery charging device <NUM> to substantially align the mobile battery charging device <NUM> with the charging port <NUM> of the vehicle <NUM>. At process <NUM>, the battery charging circuit <NUM> commands the battery charging interface drive system <NUM> to position the charging interface <NUM> proximate the charging port <NUM> of the vehicle <NUM> and engage the charging port <NUM> of the charging interface <NUM> with the charging port <NUM> of the vehicle <NUM>. At process <NUM>, the battery charging circuit <NUM> charges the battery system <NUM> of the vehicle <NUM> based on the SOC of the battery system <NUM> and/or the charge requirement to complete the upcoming mission. At process <NUM>, the battery status determination circuit <NUM> determines that the battery system <NUM> is sufficiently charged and sends a notification to the battery charging circuit <NUM>. The battery status determination circuit <NUM> can determine that the battery system <NUM> is fully charged based on the information indicative of the SOC of the battery system <NUM> determined by the sensor(s) <NUM>. At process <NUM>, the battery charging circuit <NUM> commands the charging interface drive system <NUM> to disengage the charging port <NUM> of the mobile battery charging device <NUM> from the charging port <NUM> of the vehicle <NUM>. At process <NUM>, the battery charging circuit <NUM> identifies the vehicle <NUM> having the next highest priority. The battery charging circuit <NUM> commands the driving system to approach the next vehicle <NUM> having the next highest priority according to the priority structure.

For the purpose of this disclosure, the term "coupled" means the joining or linking of two members directly or indirectly to one another. Such joining may be stationary or moveable in nature. For example, a propeller shaft of an engine "coupled" to a transmission represents a moveable coupling. Such joining may be achieved with the two members or the two members and any additional intermediate members. For example, circuit A communicably "coupled" to circuit B may signify that circuit A communicates directly with circuit B (i.e., no intermediary) or communicates indirectly with circuit B (e.g., through one or more intermediaries).

While various circuits with particular functionality are shown in <FIG> and <FIG>, it should be understood that the vehicle controller <NUM> or the controller <NUM> of the mobile battery charging device <NUM> may include any number of circuits for completing the functions described herein. For example, the activities and functionalities of the circuits <NUM>, <NUM>, <NUM> may be combined in multiple circuits or as a single circuit. Additional circuits with additional functionality may also be included. Further, the controllers <NUM>, <NUM> may further control other activity beyond the scope of the present disclosure.

As mentioned above and in one configuration, the "circuits" may be implemented in machine-readable medium for execution by various types of processors, such as the processor <NUM> of <FIG> and/or the processor <NUM> of <FIG>. An identified circuit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified circuit need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the circuit and achieve the stated purpose for the circuit. Indeed, a circuit of computer readable program code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within circuits, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.

Claim 1:
A mobile battery charging device (<NUM>) comprising:
a drive system (<NUM>) structured to propel the mobile battery charging device (<NUM>);
a charging interface (<NUM>) structured to engage a charging port (<NUM>) of a vehicle (<NUM>) that is one of a fleet of vehicles; and
a controller (<NUM>) structured to:
receive information indicative of a status of a battery system (<NUM>) of each vehicle of the fleet of vehicles, the status of the battery system of each vehicle of the fleet of vehicles including a state of charge of the battery system and information regarding an amount of charge required for the battery system to complete an upcoming mission, wherein the amount of charge required for the battery system to complete the upcoming mission is a percentage of the total storage capacity of the battery system;
determine a charging priority for each of the vehicles based on the state of charge of the battery system and the amount of charge required for the battery system to complete the upcoming mission;
receive a location of the vehicle having the battery system with a highest charging priority;
command the drive system (<NUM>) to move the battery charging device (<NUM>) to engage the charging interface with the charging port of the vehicle having the battery system with the highest charging priority to charge the battery system of the vehicle based on the charge required for the battery system to complete the upcoming mission;
responsive to charging the battery system of the vehicle based on receiving a notification from the vehicle having the battery system with the highest charging priority receive a location of a second vehicle having a second battery system with a next highest charging priority; and
command the drive system to disengage the charging interface from the charging port and move the mobile battery charging device to engage the charging interface with the charging port of the second vehicle having the second battery system with the next highest charging priority to charge the second battery system of the second vehicle.