Propulsion battery mount systems and methods

Systems and methods related to propulsion battery mount assemblies for micro-mobility transit vehicles are disclosed. For example, in an embodiment the battery mount assembly includes a mounting rail having a first side comprising a contoured surface configured to align with a complementary contoured surface of a frame of a micro-mobility transit vehicle and a second side comprising a battery mounting surface opposite the first side and configured to receive a first securing assembly and a second securing assembly entirely disposed thereon and separately spaced to receive a battery pack therebetween. The battery mount assembly may be installed on the frame of a micro-mobility transit vehicle to assist in expedient replacement of battery packs that electrically power the micro-mobility transit vehicle.

TECHNICAL FIELD

One or more embodiments of the present disclosure relate generally to powering electric vehicles and more particularly to systems and methods for providing propulsion battery mount assemblies for electric vehicles.

BACKGROUND

Contemporary transportation services may incorporate a variety of different types of vehicles, including motorized or electric kick scooters, bicycles, and/or motor scooters generally designed to transport one or two people at once (collectively, micro-mobility transit vehicles). Such micro-mobility transit vehicles provide an additional dimension of transportation flexibility, particularly when such vehicles are incorporated into a dynamic transportation matching system that links requestors or riders to transit vehicles for use. Servicing a relatively extensive fleet of micro-mobility transit vehicles can present significant and cumbersome capital investment and labor (e.g., time and cost) burden to a fleet manager/servicer.

Therefore, there is a need in the art for systems and methods to reduce fleet servicer burdens associated with servicing micro-mobility fleet vehicles, particularly in the context of a dynamic transportation matching system providing transportation services incorporating such micro-mobility fleet vehicles.

SUMMARY

Techniques are disclosed for systems and methods related to propulsion battery mount assemblies for micro-mobility transit vehicles. In an example embodiment, a battery mount assembly for a micro-mobility transit vehicle includes a mounting rail. The mounting rail may include a first side having a contoured surface configured to align with a complementary contoured surface of a frame of the micro-mobility transit vehicle. The mounting rail may further include a second side having a battery mounting surface opposite the first side and configured to receive a first securing assembly and a second securing assembly entirely disposed thereon and separately spaced to receive a battery pack assembly therebetween.

In various embodiments, a method for assembling a battery mount assembly is disclosed. The method may include mounting a first securing assembly on a first portion of a battery mounting surface of a mounting rail of the propulsion battery pack assembly. The method may further include mounting a second securing assembly on a second portion of the battery mounting surface of the mounting rail. The method may further include latching a first and second end of a battery pack assembly into the first securing assembly and the second securing assembly, respectively, such that a battery pack assembly may be disposed on an intermediate portion of the battery mounting surface defined between the first portion and the second portion and securely latched by the securing assemblies.

According to one or more embodiments, a method for using a battery mount assembly is disclosed. The method may include determining, by a battery charge reading device installed on a micro-mobility transit vehicle (e.g., in a battery pack assembly), that a charge of a battery is below a predetermined threshold. The method may further include displaying, on a user interface of a device associated with the micro-mobility transit vehicle (e.g., mobile device, cockpit assembly of the vehicle, battery light emitting diode (LED) indicator, fleet operator user interface) an indication that the charge of the battery is below the predetermined threshold. The battery pack assembly may be replaced with a charged battery pack assembly. In some cases, a battery of the battery pack assembly may be replaced with a charged battery.

DETAILED DESCRIPTION

In accordance with various embodiments of the present disclosure, propulsion battery mount assemblies for micro-mobility transit vehicles and related methodologies are provided to reduce burdens associated with servicing micro-mobility transit vehicles (e.g., electric kick scooters, bicycles, motor scooters, and/or other vehicles generally designed to transport one or two people at once). For example, a battery mount assembly may include a mounting rail, where the mounting rail has a first side with a contoured surface to align (e.g., conform to, match, suit, fit, integrate) with a complementary contoured surface of a frame of a micro-mobility transit vehicle. The mounting rail may further have a second side with a battery mounting surface opposite the first side and configured to receive a first securing assembly and a second securing assembly entirely disposed thereon and separately spaced to receive a battery pack assembly therebetween. The configuration of such securing assemblies on the battery mounting surface of the mounting rail eliminates overhang of the securing assemblies, which helps to prevent vandalism and may lead to overall reduced capital investment expenditures related to maintaining an operational fleet of such transit vehicles.

In various embodiments, a method for assembling a battery mount assembly includes mounting a first securing assembly on a first portion of a battery mounting surface of a mounting rail of the propulsion battery pack assembly and mounting a second securing assembly on a second portion of the battery mounting surface of the mounting rail. The method may further include latching a first and second end of a battery pack assembly into the first securing assembly and the second securing assembly, respectively, such that a battery pack assembly may be disposed on an intermediate portion of the battery mounting surface defined between the first portion and the second portion. In some embodiments, the method may include aligning a contoured surface of a first side of the mounting rail with a complementary contoured surface of a tube of a frame of a micro-mobility transit vehicle and installing the mounting rail on the tube of the frame of the micro-mobility transit vehicle. The battery pack assembly may be electrically coupled to a propulsion system of the micro-mobility transit vehicle to provide electric powered assistance to a rider of the micro-mobility transit vehicle.

According to one or more embodiments, a method for using a battery mount assembly is disclosed. The method may include determining, by a charge reading device installed on a micro-mobility transit vehicle, that a charge of a battery of the battery pack assembly is below a predetermined threshold indicating that the battery requires a charge or replacement. The method may further include displaying, on a user interface of a device associated with the micro-mobility transit vehicle (e.g., a rider's mobile device, a cockpit assembly of the vehicle, battery light emitting diode (LED) indicator, etc.) an indication that the charge of the battery is below the predetermined threshold. The battery pack assembly may be replaced with a charged battery pack assembly, or a battery of the battery pack assembly may be replaced with a charged battery according to various embodiments.

FIG.1illustrates a block diagram of a portion of a dynamic transportation matching system (e.g., system100) including a transit vehicle110in accordance with an embodiment of the disclosure. In the embodiment shown inFIG.1, system100includes transit vehicle110and user device130. In general, transit vehicle110may be a passenger vehicle designed to transport a single user (e.g., a micro-mobility transit vehicle) or a group of people (e.g., a typical car or truck). Although transit vehicle110is primarily described herein as an electric powered bicycle, transit vehicle110may be implemented as a motorized or electric kick scooter, a motor scooter designed to transport one or perhaps two people at once typically on a paved road, or a typical automobile configured to transport up to 4, 7, or 10 people at once, or according to a variety of different transportation modalities (e.g., transportation mechanisms). Transit vehicles similar to transit vehicle110may be owned, managed, and/or serviced primarily by a manager/servicer providing transit vehicle110for rental and use by the public as one or more types of transportation modalities offered by a dynamic transportation matching system, for example, or may be owned, managed, and/or serviced by a private owner using the dynamic transportation matching system to match their vehicle to a transportation request, such as with ridesharing or ridesourcing applications typically executed on a mobile user device, such as user device130as described herein. User device130may be a smartphone, tablet, near field communication (NFC) or radio-frequency identification (RFID) enabled smart card, or other personal or portable computing and/or communication device that may be used to facilitate rental and/or operation of transit vehicle110.

As shown inFIG.1, transit vehicle110may include one or more of a controller112, a user interface113, an orientation sensor114, a gyroscope/accelerometer116, a global navigation satellite system receiver (GNSS)118, a wireless communications module120, a camera148, a propulsion system122, an air quality sensor150, and other modules126. Operation of transit vehicle110may be substantially manual, autonomous, and/or partially or completely controlled by user device130, which may include one or more of a user interface132, a wireless communications module134, a camera138, and other modules136. In other embodiments, transit vehicle110may include any one or more of the elements of user device130. In some embodiments, one or more of the elements of system100may be implemented in a combined housing or structure that can be coupled to or within transit vehicle110and/or held or carried by a user of system100.

Controller112may be implemented as any appropriate logic device (e.g., processing device, microcontroller, processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), memory or data storage device, memory reader, or other device or combinations of devices) that may be adapted to execute, store, and/or receive appropriate instructions, such as software instructions implementing a control loop for controlling various operations of transit vehicle110and/or other elements of system100, for example. Such software instructions may also implement methods for processing images and/or other sensor signals or data, determining sensor information, providing user feedback (e.g., through user interface113or132), querying devices for operational parameters, selecting operational parameters for devices, or performing any of the various operations described herein (e.g., operations performed by logic devices of various devices of system100).

In addition, a non-transitory medium may be provided for storing machine readable instructions for loading into and execution by controller112. In these and other embodiments, controller112may be implemented with other components where appropriate, such as volatile memory, non-volatile memory, one or more interfaces, and/or various analog and/or digital components for interfacing with devices of system100. For example, controller112may be adapted to store sensor signals, sensor information, parameters for coordinate frame transformations, calibration parameters, sets of calibration points, and/or other operational parameters, over time, for example, and provide such stored data to a user via user interface113or132. In some embodiments, controller112may be integrated with one or more other elements of transit vehicle110, for example, or distributed as multiple logic devices within transit vehicle110and/or user device130.

In some embodiments, controller112may be configured to substantially continuously monitor and/or store the status of and/or sensor data provided by one or more elements of transit vehicle110and/or user device130, such as the position and/or orientation of transit vehicle110and/or user device130, for example, and the status of a communication link established between transit vehicle110and/or user device130. Such communication links may be established and then provide for transmission of data between elements of system100substantially continuously throughout operation of system100, where such data includes various types of sensor data, control parameters, and/or other data.

User interface113of transit vehicle110may be implemented as one or more of a display, a touch screen, a keyboard, a mouse, a joystick, a knob, a steering wheel, a yoke, and/or any other device capable of accepting user input and/or providing feedback to a user. In various embodiments, user interface113may be adapted to provide user input (e.g., as a type of signal and/or sensor information transmitted by wireless communications module134of user device130) to other devices of system100, such as controller112. User interface113may also be implemented with one or more logic devices (e.g., similar to controller112) that may be adapted to store and/or execute instructions, such as software instructions, implementing any of the various processes and/or methods described herein. For example, user interface132may be adapted to form communication links, transmit and/or receive communications (e.g., infrared images and/or other sensor signals, control signals, sensor information, user input, and/or other information), for example, or to perform various other processes and/or methods described herein.

In one embodiment, user interface113may be adapted to display a time series of various sensor information and/or other parameters as part of or overlaid on a graph or map, which may be referenced to a position and/or orientation of transit vehicle110and/or other elements of system100. For example, user interface113may be adapted to display a time series of positions, headings, and/or orientations of transit vehicle110and/or other elements of system100overlaid on a geographical map, which may include one or more graphs indicating a corresponding time series of actuator control signals, sensor information, and/or other sensor and/or control signals. In some embodiments, user interface113may be adapted to accept user input including a user-defined target heading, waypoint, route, and/or orientation, for example, and to generate control signals to cause transit vehicle110to move according to the target heading, route, and/or orientation. In other embodiments, user interface113may be adapted to accept user input modifying a control loop parameter of controller112, for example.

Orientation sensor114may be implemented as one or more of a compass, float, accelerometer, and/or other device capable of measuring an orientation of transit vehicle110(e.g., magnitude and direction of roll, pitch, and/or yaw, relative to one or more reference orientations such as gravity and/or Magnetic North), camera148, and/or other elements of system100, and providing such measurements as sensor signals and/or data that may be communicated to various devices of system100. Gyroscope/accelerometer116may be implemented as one or more electronic sextants, semiconductor devices, integrated chips, accelerometer sensors, accelerometer sensor systems, or other devices capable of measuring angular velocities/accelerations and/or linear accelerations (e.g., direction and magnitude) of transit vehicle110and/or other elements of system100and providing such measurements as sensor signals and/or data that may be communicated to other devices of system100(e.g., user interface132, controller112).

GNSS receiver118may be implemented according to any global navigation satellite system, including a GPS, GLONASS, and/or Galileo based receiver and/or other device capable of determining absolute and/or relative position of transit vehicle110(e.g., or an element of transit vehicle110) based on wireless signals received from space-born and/or terrestrial sources (e.g., eLoran, and/or other at least partially terrestrial systems), for example, and capable of providing such measurements as sensor signals and/or data (e.g., coordinates) that may be communicated to various devices of system100. In some embodiments, GNSS118may include an altimeter, for example, or may be used to provide an absolute altitude.

Wireless communications module120may be implemented as any wireless communications module configured to transmit and receive analog and/or digital signals between elements of system100. For example, wireless communications module120may be configured to receive control signals and/or data from user device130and provide them to controller112and/or propulsion system122. In other embodiments, wireless communications module120may be configured to receive images and/or other sensor information (e.g., still images or video images) and relay the sensor data to controller112and/or user device130. In some embodiments, wireless communications module120may be configured to support spread spectrum transmissions, for example, and/or multiple simultaneous communications channels between elements of system100. Wireless communication links formed by wireless communications module120may include one or more analog and/or digital radio communication links, such as WiFi, Bluetooth, NFC, RFID, and others, as described herein, and may be direct communication links established between elements of system100, for example, or may be relayed through one or more wireless relay stations configured to receive and retransmit wireless communications. In various embodiments, wireless communications module120may be configured to support wireless mesh networking, as described herein.

In some embodiments, wireless communications module120may be configured to be physically coupled to transit vehicle110and to monitor the status of a communication link established between transit vehicle110and/or user device130. Such status information may be provided to controller112, for example, or transmitted to other elements of system100for monitoring, storage, or further processing, as described herein. In addition, wireless communications module120may be configured to determine a range to another device, such as based on time of flight, and provide such range to the other device and/or controller112. Communication links established by communication module120may be configured to transmit data between elements of system100substantially continuously throughout operation of system100, where such data includes various types of sensor data, control parameters, and/or other data, as described herein.

Propulsion system122may be implemented as one or more motor-based propulsion systems, and/or other types of propulsion systems that can be used to provide motive force to transit vehicle110and/or to steer transit vehicle110. In some embodiments, propulsion system122may include elements that can be controlled (e.g., by controller112and/or user interface113) to provide motion for transit vehicle110and to provide an orientation for transit vehicle110. In various embodiments, propulsion system122may be implemented with a portable power supply, such as a battery and/or a combustion engine/generator and fuel supply.

For example, in some embodiments, such as when propulsion system122is implemented by an electric motor (e.g., as with many micro-mobility transit vehicles), transit vehicle110may include a battery mount assembly125having securing assemblies configured to couple (e.g., latch) a battery pack assembly124to a mounting rail installed on transit vehicle110. Battery pack assembly124may be implemented to include one or more battery cells (e.g., lithium ion battery cells) and be configured to provide electrical power to propulsion system122to propel transit vehicle110, for example, as well as to various other elements of system100, including controller112, user interface113, and/or wireless communications module120. In some embodiments, battery pack assembly124may be implemented with its own safety measures, such as thermal interlocks and a fire-resistant enclosure, for example, and may include one or more logic devices, sensors, and/or a display to monitor and provide visual feedback of a charge status of the battery (e.g., a charge percentage, a low charge indicator, etc.).

Other modules126may include other and/or additional sensors, actuators, communications modules/nodes, and/or user interface devices, for example, and may be used to provide additional environmental information related to operation of transit vehicle110, for example. In some embodiments, other modules126may include a humidity sensor, a wind and/or water temperature sensor, a barometer, an altimeter, a radar system, a proximity sensor, a visible spectrum camera or infrared camera (with an additional mount), and/or other environmental sensors providing measurements and/or other sensor signals that can be displayed to a user and/or used by other devices of system100(e.g., controller112) to provide operational control of transit vehicle110and/or system100. In further embodiments, other modules126may include a light, such as a headlight or indicator light, and/or an audible alarm, both of which may be activated to alert passersby to possible theft, abandonment, and/or other critical statuses of transit vehicle110. In particular, and as shown inFIG.1, other modules126may include camera148and/or air quality sensor150.

Camera148may be implemented as an imaging device including an imaging module including an array of detector elements that can be arranged in a focal plane array. In various embodiments, camera148may include one or more logic devices (e.g., similar to controller112) that can be configured to process imagery captured by detector elements of camera148before providing the imagery to communications module120. More generally, camera148may be configured to perform any of the operations or methods described herein, at least in part, or in combination with controller112and/or user interface113or132.

In various embodiments, air quality sensor150may be implemented as an air sampling sensor configured to determine an air quality of an environment about transit vehicle110and provide corresponding air quality sensor data. Air quality sensor data provided by air quality sensor150may include particulate count, methane content, ozone content, and/or other air quality sensor data associated with common street level sensitivities and/or health monitoring typical when in a street level environment, such as that experienced when riding on a typical micro-mobility transit vehicle, as described herein.

Transit vehicles implemented as micro-mobility transit vehicles may include a variety of additional features designed to facilitate transit management and user and environmental safety. For example, as shown inFIG.1, transit vehicle110may include one or more of docking mechanism140, operator safety measures142, vehicle security device144, and/or user storage146, as described in more detail herein.

In particular, in some embodiments, operator safety measures142may be implemented as one or more of a headlight, a taillight, ambient lighting, a programmable lighting element (e.g., a multi-color panel, strip, or array of individual light elements, such as addressable light emitting diodes (LEDs), recessed and/or directional lighting, actuated lighting (e.g., articulated lighting coupled to an actuator), and/or other lighting coupled to and/or associated with transit vehicle110and controlled by controller112. In other embodiments, operator safety measures142may include a speaker or other audio element configured to generate an audible alarm or sound to warn a rider or passersby of a detected safety concern, for example, or to inform a rider of a potential safety concern. More generally, operator safety measures142may be any electronic, mechanical, or electromechanical device or subsystem configured to increase the safety of a rider and/or mitigate potential harm to a rider under nominal operating conditions.

User interface132of user device130may be implemented as one or more of a display, a touch screen, a keyboard, a mouse, a joystick, a knob, a steering wheel, a yoke, and/or any other device capable of accepting user input and/or providing feedback to a user. In various embodiments, user interface132may be adapted to provide user input (e.g., as a type of signal and/or sensor information transmitted by wireless communications module134of user device130) to other devices of system100, such as controller112. User interface132may also be implemented with one or more logic devices (e.g., similar to controller112) that may be adapted to store and/or execute instructions, such as software instructions, implementing any of the various processes and/or methods described herein. For example, user interface132may be adapted to form communication links, transmit and/or receive communications (e.g., infrared images and/or other sensor signals, control signals, sensor information, user input, and/or other information), for example, or to perform various other processes and/or methods described herein.

In one embodiment, user interface132may be adapted to display a time series of various sensor information and/or other parameters as part of or overlaid on a graph or map, which may be referenced to a position and/or orientation of transit vehicle110and/or other elements of system100. For example, user interface132may be adapted to display a time series of positions, headings, and/or orientations of transit vehicle110and/or other elements of system100overlaid on a geographical map, which may include one or more graphs indicating a corresponding time series of actuator control signals, sensor information, and/or other sensor and/or control signals. In some embodiments, user interface132may be adapted to accept user input including a user-defined target heading, waypoint, route, and/or orientation, for example, and to generate control signals to cause transit vehicle110to move according to the target heading, route, and/or orientation. In other embodiments, user interface132may be adapted to accept user input modifying a control loop parameter of controller112, for example.

Wireless communications module134may be implemented as any wireless communications module configured to transmit and receive analog and/or digital signals between elements of system100. For example, wireless communications module134may be configured to transmit control signals from user interface132to wireless communications module120or144. In some embodiments, wireless communications module134may be configured to support spread spectrum transmissions, for example, and/or multiple simultaneous communications channels between elements of system100. In various embodiments, wireless communications module134may be configured to monitor the status of a communication link established between user device130and/or transit vehicle110(e.g., including packet loss of transmitted and received data between elements of system100, such as with digital communication links), and/or determine a range to another device, as described herein. Such status information may be provided to user interface132, for example, or transmitted to other elements of system100for monitoring, storage, or further processing, as described herein. In various embodiments, wireless communications module134may be configured to support wireless mesh networking, as described herein.

Other modules136of user device130may include other and/or additional sensors, actuators, communications modules/nodes, and/or user interface devices used to provide additional environmental information associated with user device130, for example. In some embodiments, other modules136may include a humidity sensor, a wind and/or water temperature sensor, a barometer, a radar system, a visible spectrum camera, an infrared camera, a GNSS receiver, and/or other environmental sensors providing measurements and/or other sensor signals that can be displayed to a user and/or used by other devices of system100(e.g., controller112) to provide operational control of transit vehicle110and/or system100or to process sensor data to compensate for environmental conditions. As shown inFIG.1, other modules136may include camera138.

Camera138may be implemented as an imaging device including an imaging module including an array of detector elements that can be arranged in a focal plane array. In various embodiments, camera138may include one or more logic devices (e.g., similar to controller112) that can be configured to process imagery captured by detector elements of camera138before providing the imagery to communications module120. More generally, camera138may be configured to perform any of the operations or methods described herein, at least in part, or in combination with controller138and/or user interface113or132.

In general, each of the elements of system100may be implemented with any appropriate logic device (e.g., processing device, microcontroller, processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), memory or data storage device, memory reader, or other device or combinations of devices) that may be adapted to execute, store, and/or receive appropriate instructions, such as software instructions implementing a method for providing sensor data and/or imagery, for example, or for transmitting and/or receiving communications, such as sensor signals, sensor information, and/or control signals, between one or more devices of system100.

In addition, one or more non-transitory mediums may be provided for storing machine readable instructions for loading into and execution by any logic device implemented with one or more of the devices of system100. In these and other embodiments, the logic devices may be implemented with other components where appropriate, such as volatile memory, non-volatile memory, and/or one or more interfaces (e.g., inter-integrated circuit (I2C) interfaces, mobile industry processor interfaces (MIPI), joint test action group (JTAG) interfaces (e.g., IEEE 1149.1 standard test access port and boundary-scan architecture), and/or other interfaces, such as an interface for one or more antennas, or an interface for a particular type of sensor).

Sensor signals, control signals, and other signals may be communicated among elements of system100and/or elements of other systems similar to system100using a variety of wired and/or wireless communication techniques, including voltage signaling, Ethernet, WiFi, Bluetooth, Zigbee, Xbee, Micronet, Near-field Communication (NFC) or other medium and/or short range wired and/or wireless networking protocols and/or implementations, for example. In such embodiments, each element of system100may include one or more modules supporting wired, wireless, and/or a combination of wired and wireless communication techniques, including wireless mesh networking techniques. In some embodiments, various elements or portions of elements of system100may be integrated with each other, for example, or may be integrated onto a single printed circuit board (PCB) to reduce system complexity, manufacturing costs, power requirements, coordinate frame errors, and/or timing errors between the various sensor measurements.

Each element of system100may include one or more batteries, capacitors, or other electrical power storage devices, for example, and may include one or more solar cell modules or other electrical power generating devices. In some embodiments, one or more of the devices may be powered by a power source for transit vehicle110, using one or more power leads. Such power leads may also be used to support one or more communication techniques between elements of system100.

InFIG.2, a requestor may use user device130ato receive an input with a request for transportation with one or more transit vehicles155,110,157,159and/or public transportation vehicles210a-b. For example, the transportation request may be a request to reserve one of transit vehicles155,110,157,159. The transportation request may be transmitted to management system240over WAN250, allowing management system240to poll status of transit vehicles155,110,157, and159to select one of transit vehicles155,110,157, and159to fulfill the transportation request; receiving a fulfillment notice from management system240and/or from the selected transit vehicle, and receiving navigation instructions to proceed to or otherwise meet with the selected transit vehicle. A similar process may occur using user device130b, but where the transportation request enables a transit vehicle over a local communication link256, as shown.

Management system240may be implemented as a server with controllers, user interfaces, communications modules, and/or other elements similar to those described with respect to system100ofFIG.1, but with sufficient processing and storage resources to manage operation of dynamic transportation matching system200, including monitoring statuses of transit vehicles155,110,157, and159, as described herein. In some embodiments, management system240may be implemented in a distributed fashion and include multiple separate server embodiments linked communicatively to each other direction and/or through WAN250. WAN250may include one or more of the Internet, a cellular network, and/or other wired or wireless WANs. WAN communication links252may be wired or wireless WAN communication links, and mesh network communication links254may be wireless communication links between and among transit vehicles155,110,157, and159, as described herein.

User device130ainFIG.2includes a display of user interface132that shows a planned route for a user attempting to travel from an origination point260to a destination272using different transportation modalities (e.g., a planned multimodal route), as depicted in a route/street map286rendered by user interface132. For example, management system240may be configured to monitor statuses of all available transportation modalities (e.g., including transit vehicles and public transportation vehicles) and provide a planned multimodal route from origination point260to destination272. Such a planned multimodal route may include, for example, a walking route262from origination point260to a bus stop264, a bus route266from bus stop264to a bus stop268(e.g., using one or more of transit vehicles210aor210b), and a micromobility route270(e.g., using one or more of micromobility transit vehicles110c,110e, and110g) from bus stop268to destination272. Also shown rendered by user interface132are a present location indicator280(indicating a present absolute position of user device130aon street map286), a navigation destination selector/indicator282(e.g., configured to allow a user to input a desired navigation destination), and a notice window284(e.g., used to render vehicle status data or other information, including user notices and/or alerts, as described herein). For example, a user may use navigation destination selector/indicator282to provide and/or change destination272, as well as change any portion (e.g., leg, route, etc.) or modality of the multimodal route from origination point260to destination272. In some embodiments, notice window284may display instructions for traveling to a next waypoint along the determined multimodal route (e.g., directions to walk to a bus stop, directions to ride a micromobility transit vehicle to a next stop along the route, etc.).

In various embodiments, management system240may be configured to provide or suggest an optimal multimodal route to a user (e.g., initially and/or while traversing a particular planned route), and a user may select or make changes to such a route through manipulation of user device130a, as shown. For example, management system240may be configured to suggest a quickest route, a least expensive route, a most convenient route (to minimize modality changes or physical actions a user must take along the route), an inclement weather route (e.g., that keeps the user protected from inclement weather a maximum amount of time during route traversal), or some combination of those that is determined as best suited to the user, such as based on various user preferences. Such preferences may be based on prior use of system200, prior user trips, a desired arrival time and/or departure time (e.g., based on user input or obtained through a user calendar or other data source), or specifically input or set by a user for the specific route, for example, or in general. In one example, origination point260may be extremely congested or otherwise hard to access by a ride-share transit vehicle, which could prevent or significantly increase a wait time for the user and a total trip time to arrive at destination272. In such circumstances, a planned multimodal route may include directing the user to walk and/or take a scooter/bike to an intermediate and less congested location to meet a reserved ride-share vehicle, which would allow the user to arrive at destination272quicker than if the ride-share vehicle was forced to meet the user at origination point260. It will be appreciated that numerous different transportation-relevant conditions may exist or dynamically appear or disappear along a planned route that may make it beneficial to use different modes of transportation to arrive at destination272efficiently, including changes in traffic congestion and/or other transportation-relevant conditions that occur mid-route, such as an accident along the planned route. Under such circumstances, management system240may be configured to adjust a modality or portion of the planned route dynamically in order to avoid or otherwise compensate for the changed conditions while the route is being traversed.

FIG.3Aillustrates a diagrams of micro-mobility transit vehicle110, which may be integrated with mobile mesh network provisioning systems in accordance with an embodiment of the disclosure. For example, transit vehicle110ofFIG.3Amay correspond to a motorized bicycle for use that is integrated with the various elements of system100and may be configured to participate in dynamic transportation matching system200ofFIG.2. As shown, transit vehicle110includes controller/user interface/wireless communications module112(e.g., which may be integrated with a rear fender of transit vehicle110), propulsion system122configured to provide motive power to at least one of the wheels (e.g., a rear wheel322) of transit vehicle110, battery mount assembly125configured to couple battery pack assembly124to a frame of transit vehicle110to power propulsion system122and/or other elements of transit vehicle110, docking mechanism140(e.g., a spade lock assembly) for docking transit vehicle110at a docking station, user storage146implemented as a handlebar basket, and vehicle security device (e.g., an embodiment of vehicle security device144ofFIG.1), which may incorporate one or more of a locking cable144a, a pin144bcoupled to a free end of locking cable144a, a pin latch/insertion point144c, a frame mount144d, and a cable/pin holster144e, as shown (collectively, vehicle security device144). In some embodiments, controller/user interface/wireless communications module112may alternatively be integrated on and/or within a handlebar enclosure.

In some embodiments, vehicle security device144may be implemented as a wheel lock configured to immobilize rear wheel322of transit vehicle110, such as by engaging pin144bwith spokes of rear wheel322. In the embodiment shown inFIG.3A, vehicle security device144may be implemented as a cable lock configured to engage with a pin latch on a docking station, for example, or to wrap around and/or through a secure pole, fence, or bicycle rack and engage with pin latch144c. In various embodiments, vehicle security device144may be configured to immobilize transit vehicle110by default, thereby requiring a user to transmit a request to management system240(e.g., via user device130) to use transit vehicle110before attempting to use transit vehicle110. The request may identify transit vehicle110based on an identifier (e.g., a QR code, a barcode, a serial number, etc.) presented on transit vehicle110(e.g., such as by a user interface on a rear fender of transit vehicle110). Once the request is approved (e.g., payment is processed), management system240may transmit an unlock signal to transit vehicle110(e.g., via network250). Upon receiving the unlock signal, transit vehicle110(e.g., controller112of transit vehicle110) may release vehicle security device144and unlock rear wheel322of transit vehicle110.

In various embodiments, transit vehicle110may also be implemented with various vehicle light assemblies to increase visibility, to provide ambient lighting, and/or to provide lighted beaconing. As shown inFIG.3A, transit vehicle110may include a seat post clamp assembly379configured to adjust between an open and closed position such that a seat post extending from a seat post tube of the frame of transit vehicle110may be adjusted in height and securely locked into a desired position.

In various embodiments, micro-mobility transit vehicle110may be implemented with a battery mount assembly125configured to receive a modular battery pack assembly configured to propel micro-mobility transit vehicles110via electric power provided to the propulsion system122of micro-mobility transit vehicle110. As described herein, such battery mount assembly125may include various features designed to ease battery replacement, increase durability, and provide additional functionality to reduce service burdens. As such, the battery mount assembly125embodiments discussed herein may assist in forming a reliable and robust propulsion system and/or propulsion control system for micro-mobility transit vehicles.

FIG.3Billustrates a docking station300for docking transit vehicles (e.g., transit vehicles110ofFIG.3A.) in accordance with embodiments of the disclosure. As shown inFIG.3B, docking station300may include multiple bicycle docks, such as docks302a-e. For example, a single transit vehicle (e.g., any one of electric bicycles110a-d) may dock in each of docks302a-eof docking station300. Each of docks302a-emay include a lock mechanism for receiving and locking docking mechanism140of electric bicycles110a-d. In some embodiments, once a transit vehicle is docked in a bicycle dock, the dock may be electronically and/or communicatively coupled to the transit vehicle (e.g., to controllers and/or wireless communications modules integrated within cockpit enclosures112a-dof transit vehicles110a-d) via a communication link such that the transit vehicle may be charged by the dock and the transit vehicle and the dock may communicate with each other via the communication link (e.g., similar to communications over mobile mesh network260), as described herein.

For example, a requestor may use user device130ato reserve a transit vehicle docked to one of bicycle docks302a-eby transmitting a reservation request to management system240. Once the reservation request is processed, management system240may transmit an unlock signal to a docked transit vehicle and/or one of docks302a-evia network250and/or mobile mesh network260. One of docks302a-emay automatically unlock an associated lock mechanism to release the transit vehicle based, at least in part, on such unlock signal. In some embodiments, each of docks302a-emay be configured to charge batteries (e.g., components of battery assemblies124a-c) of electric bicycles110a-dwhile electric bicycles110a-dare docked at docks302a-e. As shown inFIG.3B, battery assemblies124a-cmay be secured to transit vehicles110a,110b, and110dvia battery mount assemblies125a-c. In some embodiments, docking station300may also be configured to transmit status information associated with docking station300(e.g., a number of transit vehicles docked at docking station300, charge statuses of docked transit vehicles, and/or other fleet status information) to management system240.

FIG.3Cillustrates a block diagram of an example system305for determining a state of charge of a battery of a micro-mobility transit vehicle110to perform needed maintenance on the micro-mobility transit vehicle110according to embodiments of the disclosure. For brevity, micro-mobility transit vehicle110may be referred to as “transit vehicle110” in some instances. In an example embodiment dock computing device311may be, may be part of, or may include dock300ofFIG.3B.

Battery pack assembly124may be configured with one or more applications, devices, and/or modules that may perform one or more of the steps described herein. The battery pack assembly124may include a battery enclosure341that houses a battery pack computing device313, a battery315, and an activation button317. The battery315may be a single battery or may be multiple batteries connected together to provide a battery source for a motor included in the transit vehicle110that when provided power allows for electrical-assistance for the transit vehicle110. The activation button317when pressed may enable the electrical-assistance for the personal mobility vehicle.

The battery charge module319may be hardware, firmware, and/or software configured to provide a state of charge of the battery315included in the battery pack computing device313. For example, the battery charge module319may provide a reading of a voltage value for the battery315. In some implementations, the voltage value for the battery315may be compared with a fully charged voltage value for the battery315to determine (calculate) a percentage of charge remaining for the battery315. The percentage of charge remaining for the battery315may be compared to a threshold value to determine one or more of if the battery315should be recharged, if the battery315has enough charge to complete a trip for the transit vehicle110, and if the battery pack assembly124should be swapped with another battery pack that includes a fully charged battery.

In some implementations, the determining (calculating) of a percentage of charge remaining for the battery315and/or the comparing of the percentage of charge remaining for the battery315to the threshold value may be performed by the battery pack application321. In some implementations, the battery pack computing device313may provide the battery reading(s) to the transit vehicle computing device309. In some implementations, the transit vehicle computing device309may determine (calculate) the percentage of charge remaining for the battery315and/or may compare the percentage of charge remaining for the battery315to the threshold value. In some implementations, the transit vehicle computing device309may provide the battery reading(s) to the management system240to determine (calculate) the percentage of charge remaining for the battery315and/or to compare the percentage of charge remaining for the battery315to the threshold value.

In some implementations, the battery pack computing device313may provide the battery reading(s) to the dock computing device311. In some implementations, the dock computing device311may determine (calculate) the percentage of charge remaining for the battery315and/or may compare the percentage of charge remaining for the battery315to the threshold value. In some implementations, the dock computing device311may provide the battery reading(s) to the management system240to determine (calculate) the percentage of charge remaining for the battery315and/or to compare the percentage of charge remaining for the battery315to the threshold value.

In some implementations, the battery pack computing device313may provide the battery reading(s) to the management system240to determine (calculate) the percentage of charge remaining for the battery315and/or to compare the percentage of charge remaining for the battery315to the threshold value.

The battery pack computing device313may include a battery pack application321, a motor control module323, and communication modules325. The communication modules325may include a Bluetooth module327, a Universal Serial Bus (USB) module329, a WiFi module331, a network communication module333, and a transceiver module335.

The motor control module323may be hardware, firmware, and/or software configured to provide one or more controls (e.g., control signals) for the motor included in the transit vehicle110(e.g., part of propulsion system122of transit vehicle110) that when provided power can allow for electrical-assistance for the transit vehicle110. The battery pack application321may be implemented in hardware, firmware, and/or software. The battery pack computing device313may run (execute) the battery pack application321as described herein to implement the controls and communications for the battery pack assembly124.

The transit vehicle computing device309may be configured with one or more applications, devices, and/or modules that may perform one or more of the steps described herein. According to some embodiments, the transit vehicle computing device309may be a tablet computer or mobile computing device. In some examples, the transit vehicle computing device309may be a device suitable for temporarily mounting on a transit vehicle110(e.g., for use by a requestor and/or provider for a transportation matching application, a navigation application, and/or any other application suited for the use of requestors and/or providers). Additionally, or alternatively, the transit vehicle computing device309may be a device suitable for permanently mounting on or coupling to a transit vehicle110that has a transit vehicle application installed on the computing device (e.g., a transit vehicle computing device309) to provide transportation services to transportation requestors and/or to communicate with the management system240.

The dock computing device311may be configured with one or more applications, devices, and/or modules that may perform one or more of the steps described herein. For example, the dock computing device311may include a dock application, a dock interface module, and communication modules. The communication modules may include a Bluetooth module, a WiFi module, a network communication module, and a transceiver module. The dock interface may be hardware, firmware, and/or software configured to implement and control a dock interface. The dock application may be implemented in hardware, firmware, and/or software. The dock computing device311may run (execute) the dock application as described herein to implement the controls, interfaces, and communications for the dock computing device311.

The transit vehicle computing device309, the dock computing device311, and the battery pack computing device313may be any suitable type of computing device as described herein. For example, the transit vehicle computing device309may be mounted on or otherwise coupled to a micro-mobility transit vehicle110as shown, for example, inFIG.3A(i.e., controller112).

The management system240may be configured with one or more applications, devices, repositories, and/or modules that may perform one or more of the steps described herein. The management system240may include a micro-mobility transit vehicle database, a micro-mobility transit vehicle management module, a transit vehicle blocker module, a dynamic transportation matching system application, and communication modules. The communication modules may include a WiFi module, a network communication module, and a transceiver module.

The management system240may represent any computing system and/or set of computing systems capable of matching transportation requests. As described, the management system240may be in communication with the transit vehicle computing device309. In some implementations, the management system240may be in communication with more than one (e.g., two or more) transit vehicle computing devices coupled to respective transit vehicles. In these implementations, the management system240may also be in communication with more than one (e.g., two or more) battery pack computing devices coupled to the respective transit vehicles. As described, the management system240may be in communication with the dock computing device311. In some implementations, the management system240may be in communication with more than one (e.g., two or more) dock computing devices.

The WiFi modules discussed in reference toFIG.3C, including WiFi module331, may be hardware, firmware, and/or software configured to implement WiFi communications with (between) WiFi enabled devices. Each WiFi module may interface with a WiFi antenna included in the system or device that includes the WiFi module.

The Bluetooth modules discussed in reference toFIG.3C, including Bluetooth module327may be hardware, firmware, and/or software configured to implement Bluetooth communications with (between) Bluetooth enabled devices. The transceiver modules discussed in reference toFIG.3C, including transceiver module335, may include hardware and/or software and may be configured to implement wireless communications with (between) computing devices and systems that are wirelessly interfaced with or connected to a cellular telecommunications network.

The network communication modules discussed in reference toFIG.3C, including network communication module333, may be hardware, firmware, and/or software configured to implement wired and/or wireless communications with (between) computing devices and systems connected to or interfaced with a network (e.g., network250). The USB modules discussed in reference toFIG.3C, including USB module329may be hardware, firmware, and/or software configured to implement USB communications with (between) USB enabled devices.

The battery pack computing device313may interact/interface with the transit vehicle computing device309, the dock computing device311, and/or a management system240. In some implementations, the battery pack computing device313may establish direct communications with the transit vehicle computing device309. In some implementations, the battery pack computing device313may establish direct communications with the dock computing device311. In some implementations, the battery pack computing device313may establish communications with the management system240by way of network250.

The transit vehicle computing device309may interact/interface with the dock computing device311, the battery pack computing device313, and/or the management system240. In some implementations, the transit vehicle computing device309may establish direct communications with the battery pack computing device313. In some implementations, the transit vehicle computing device309may establish direct communications with the dock computing device311. In some implementations, the transit vehicle computing device309may establish communications with the dock computing device311by way of a network250. The transit vehicle computing device309may establish communications with the management system240by way of the network250.

The dock computing device311may interact/interface with the management system240, the transit vehicle computing device309, and/or the battery pack computing device313. In some implementations, the dock computing device311may establish direct communications with the battery pack computing device313. In some implementations, the dock computing device311may establish direct communications with the transit vehicle computing device309. In some implementations, the dock computing device311may establish communications with the transit vehicle computing device309by way of the network250. The dock computing device311may establish communications with the management system240by way of the network250.

In some implementations, the battery pack computing device313using one or more communication modules325may establish communications with the transit vehicle computing device309by way of one or more of communication modules325. In some implementations, the transit vehicle110may not be parked and/or locked in a dock and may be considered dockless. In some implementations, the transit vehicle110may be parked and/or locked in a dock. A battery pack application321may send battery information to the transit vehicle computing device309. The transit vehicle computing device309may provide the battery information to the management system240by way of the network250.

The battery pack computing device313may use one or more communication modules325to establish communications with the transit vehicle computing device309by way of one or more communication modules325. For example, the battery pack computing device313may establish direct wireless communication with the transit vehicle computing device309using Bluetooth communication protocols. For example, the battery pack computing device313may establish direct wireless communication with the transit vehicle computing device309using, for example, WiFi communication protocols. For example, the battery pack computing device313may establish direct communication with the transit vehicle computing device309using Universal Serial Bus (USB) communication protocols. In some implementations, the battery pack computing device313may establish communication with the management system240by way of the network250using communication protocols implemented between network communication modules.

In some implementations, the battery pack computing device313, using one or more communication modules325, may establish communications with the dock computing device311. In these implementations, the transit vehicle110may be docked (parked and/or locked) in a dock as shown, for example, inFIG.3B. In some implementations, referring toFIG.3B, a battery pack application321may send battery information by way of the communicative connection between the battery pack computing device313and the dock computing device311. A dock application of dock computing device311may provide the battery information to the management system240by way of the network250.

In one or more embodiments, the transit vehicle computing device309may determine a state of charge of the battery315included in the battery pack assembly124based on information and data received from the battery pack computing device313. The transit vehicle computing device309may provide the state of charge of the battery315to the management system240. The management system240may store the state of charge of the battery315in a transit vehicle status database.

In various embodiments, transit vehicle computing device309may include a blocker module configured to use the state of charge of the battery315of the transit vehicle110to determine if the transit vehicle110is available for use. In some implementations, the blocker module may decide to block use of the transit vehicle110until the battery315(and in some implementations the battery pack assembly124) can be swapped out with another battery or charged. The blocker module may update the micro-mobility transit vehicle database entry in the transit vehicle status database via communication with management system240to indicate that the transit vehicle110is not available for use in completing a trip. The management system240may access the transit vehicle status database when determining an availability and location of transit vehicle110for possible use in completing a trip.

FIG.4illustrates a flow diagram of a process400for assembling and installing a battery mount assembly125in accordance with one or more embodiments of the disclosure. It should be appreciated that any step, sub-step, sub-process, or block of process400may be performed in an order or arrangement different from the embodiments illustrated byFIG.4. For example, in other embodiments, one or more blocks may be omitted from or added to the process. For illustrative purposes, process400is described in reference toFIGS.5A-5Ibut the following description of process400may generally be applied to the additional figures of the disclosure. It is noted that “first,” “second,” etc. may be used for explanatory purposes as labels for nouns that they precede in the disclosure and do not necessarily imply any type of ordering (e.g., spatial, temporal, logical, cardinal, etc.).

At block402of process400, a first securing assembly512may be mounted on a battery mounting surface502of a mounting rail500. Example mounting rails500and501according to various embodiments of the present disclosure are illustrated inFIGS.5A and5B. In the embodiment shown inFIG.5A, mounting rail500includes battery mounting surface502, mounting through-holes506a-c, securing assembly mounting interfaces504aand504b, contoured surface508, scalloped notches (one of which is labeled scalloped notch504), and channels503. In the embodiment shown inFIG.5B, mounting rail501includes battery mounting surface502, mounting through-holes506a-c, securing assembly mounting interfaces504aand504b, contoured surface508, and channels503. Although reference is primarily made to mounting rail500with respect to various steps and processes described in the disclosure, the steps and processes may generally apply with respect to mounting rail501.

As shown in the embodiment ofFIG.5A, mounting surface502may have a first portion510a, second portion510c, and an intermediate portion510bbetween the first portion510aand second portion510c. Mounting surface502may be on a side of mounting rail500opposite to a side of contoured surface508. In various embodiments, mounting rail500may extend substantially longitudinally along contoured surface508. Channels503may be longitudinally defined in mounting surface502. In some embodiments, channels503may be protective conduits for wires that extend between securing assemblies disposed on mounting surface502. For example, wires extending from a second securing assembly may be disposed within channels503and electrically couple to a first securing assembly to provide power to the first securing assembly to operate a latch of the first securing assembly as further discussed below. In various embodiments, channels503may be used as water conduits that allow water (e.g., rain water) to run off the mounting surface502and away from a battery pack assembly124.

As shown inFIG.5C, first portion510aof mounting surface502may extend laterally such that first securing assembly512may be entirely disposed on first portion510aduring the mounting performed at block402. In this regard, the surface defined by first portion510amay be shaped to receive first securing assembly512such that first securing assembly512does not extend beyond bounds defined by first portion510a. Securing assembly mounting interface504amay be configured to receive fasteners514aand514bof first securing assembly512to securely mount first securing assembly512to first portion510a. In this regard, fasteners514aand514bmay be inserted through slot505provided in a mounting plate522of first securing assembly512to secure mounting plate522, and consequently first securing assembly512, to first portion510aof mounting surface502.

As further shown inFIG.5C, first securing assembly512may include a printed circuit board516. Printed circuit board516may include various electronic components such as a controller configured to electromechanically control a latch518of first securing assembly512. For example, latch518may be an electromechanical latch comprising various components and configured to latch and release a battery pack assembly into first securing assembly512. Printed circuit board516may further include a communications module configured to receive a wireless communication comprising instructions for the controller to latch or release latch518. In one embodiment, the communication module may be configured to receive a wireless communication such as a near-field communication (NFC) tap, Bluetooth communication, ZigBee communication, WiFi communication, and/or infrared communication from a mobile device to control operation of latch518. In further embodiments, the communication module may be configured to receive wireless communications originating from a fleet service operating server such as management system240. In an example use case, a technician may perform an NFC tap (or other wireless communication) to first securing assembly518, where the NFC tap may include an encrypted key that may be decrypted by the communication module and read by the controller to latch or release latch518.

First securing assembly512may further include a cover plate520configured to couple to mounting plate522and enclose internal components of first securing assembly512such as latch518and printed circuit board516in a space defined therebetween.

At block404of process400, a second securing assembly524may be mounted on the battery mounting surface502of the mounting rail500. For example, as shown inFIG.5D, second portion510cof mounting surface502may extend laterally such that second securing assembly524may be entirely disposed on second portion510cduring the mounting step performed at block404. In this regard, the surface defined by second portion510cmay be shaped to receive second securing assembly524such that second securing assembly524does not extend beyond bounds defined by second portion510c.

Securing assembly mounting interface504bshown inFIGS.5A and5Bmay be configured to receive fasteners of second securing assembly524to securely mount second securing assembly524to second portion510c. For example, the fasteners may be inserted through slots provided in a mounting plate526of second securing assembly524to secure mounting plate526, and consequently second securing assembly524, to second portion510cof mounting surface502.

Second securing assembly524may include a wiring harness530configured to electrically couple a battery pack assembly124to a propulsion system122of the micro-mobility transit vehicle110via one or more wires532that may extend into a frame of the micro-mobility transit vehicle110and connect to the electric-powered propulsion system122. For example, electrical interface534may be configured to receive a complementary battery electrical interface of the battery pack assembly124to provide an electrical connection between the battery pack assembly124, one or more wires, and the propulsion system122.

Second securing assembly524may include a cover plate528configured to couple to a mounting plate526of second securing assembly524and enclose internal components of second securing assembly524. Second securing assembly524may include a latch in some cases. For example, the latch of second securing assembly524may be similar to latch518in that it may be an electromechanical latch configured to latch and release a battery pack assembly into second securing assembly524.

At block406of process400, mounting rail500may be installed on a frame of the micro-mobility transit vehicle110. Although installing the mounting rail500on the frame of the micro-mobility transit vehicle110is discussed at block406, installing the mounting rail500on the frame of the micro-mobility transit vehicle110may generally be performed at any time prior to latching in the battery pack assembly124to the securing assemblies512and524. However, various techniques for installing the mounting rail500to the frame of the micro-mobility transit vehicle110allow for installation after latching the battery pack assembly124to the securing assemblies512and524, for example, such as when an adhesive is used to install the mounting rail on the frame of the micro-mobility transit vehicle110.

Referring now toFIG.5E, mounting rail500may be installed on frame536by inserting fasteners through-holes506a-506cof mounting rail500to be received by complementary threaded holes506d-fof frame536of the micro-mobility transit vehicle110. Contoured surface508of mounting rail500may be configured to align with a complementary contoured surface538of frame536. For example, the contoured surface508and complementary contoured surface538of frame536may be substantially arcuate to facilitate their alignment for installation. In other examples, contoured surface508and complementary contoured surface538may be polygonal. In other words, contoured surface508may take various forms/shapes to suit complementary contoured surface538such that there are zero or minimal gaps between the two surfaces. It is noted that frame536shown inFIG.5Eis only a portion of a frame of a micro-mobility transit vehicle110and is presented for illustrative purposes. For example, frame536may be a component of a frame of the micro-mobility transit vehicle110such as a top tube, down tube, seat tube, heat tube, seat post, seat stay, chain stay, fork, stem, or any other part of the frame suitable to receive mounting rail500. In the example embodiment shown inFIG.5F, mounting rail500is installed on a downtube540of a micro-mobility transit vehicle110, according to various embodiments

In some embodiments, the one or more wires532of wiring harness530of second securing assembly524may be electrically coupled to a propulsion system122of the micro-mobility transit vehicle110. As shown inFIG.5G, the one or more wires532may be electrically coupled to the propulsion system122of the micro-mobility transit vehicle110via a wire544before or after installing the mounting rail500on the frame536of the micro-mobility transit vehicle110according to various embodiments according to one or more embodiments. Wire544may extend into the frame536of the micro-mobility transit vehicle110to connect to the propulsion system122in some embodiments or may extend into a wiring conduit installed on the frame536of the micro-mobility transit vehicle110.

At block408of process400, a first end513of a battery pack assembly124may be latched into the first securing assembly512. For example, as shown inFIG.5H, first end513of battery pack assembly124may be latched into first securing assembly512. In some embodiments, battery pack assembly124may include a battery enclosure341, a battery electrical interface (e.g., electrical interface339ofFIG.3C) to integrate with the electrical interface534of second securing assembly524, and latching interfaces (e.g., latching interfaces339ofFIG.3C) configured to latch into latches of the securing assemblies512and524.

At block410of process400, a second end515of a battery pack assembly124may be latched into the second securing assembly. For example, as shown inFIG.5H, second end515of battery pack assembly124may be latched into second securing assembly524such that battery pack assembly124is latched between first securing assembly512and second securing assembly524.

Battery pack assembly124may be disposed on an intermediate portion510bof the mounting surface502of mounting rail500between first portion510aand second portion510c. As shown in the embodiment ofFIG.5A, intermediate portion510bmay extend laterally less than first portion510aand second portion510c. In various embodiments, battery pack assembly124may be disposed on intermediate portion510such that battery pack assembly124is within bounds defined by lateral extension of intermediation portion510a. In some embodiments, intermediate portion510amay have a scalloped notch on each side (e.g., scalloped notch504depicted inFIG.5A), and battery pack assembly124may be disposed on intermediate portion510such that battery pack assembly124is within bounds defined by an inner edge of each of the scalloped notches defined in mounting surface502. In some cases, battery pack assembly124is disposed on intermediate portion510bwithin bounds of intermediate portion510bto minimize overhang of battery pack assembly124.

At block412of process400, battery pack assembly124may be electrically coupled to the propulsion system122of the micro-mobility transit vehicle110. For example, at block410when the second end515of battery pack assembly124is latched into second securing assembly524, a battery electrical interface of battery pack assembly124may be electrically coupled to electrical interface534of second securing assembly524. As such, the battery of battery pack assembly124may be electrically coupled to the propulsion system122of the micro-mobility transit vehicle110via the connections discussed above. As such, the battery may power micro-mobility transit vehicle110.

In an embodiment shown inFIG.5I, a battery mount assembly125assembled according to various steps of process400may be installed on micro-mobility transit vehicle110.

FIG.6illustrates a flow diagram of a process600for using a battery mount assembly125in accordance with an embodiment of the disclosure. It should be appreciated that any step, sub-step, sub-process, or block of process600may be performed in an order or arrangement different from the embodiments illustrated byFIG.6. For example, in other embodiments, one or more blocks may be omitted from or added to the process. For illustrative purposes, process600is described in reference toFIGS.3C and5A-5Ibut the following description of process600may generally be applied to the additional figures disclosed herein. It is noted that “first,” “second,” etc. may be used as labels for nouns that they precede for explanatory purposes in the disclosure and do not necessarily imply any type of ordering (e.g., spatial, temporal, logical, cardinal, etc.).

At block602, a battery charge of battery315of battery pack assembly124is determined to be below a predetermined threshold. For example, a computing device309of transit vehicle110may use one or more communications modules120of the transit vehicle110to establish a communication with communication modules325of a battery pack computing device313of battery pack assembly124. The computing device309of the transit vehicle110may request a current battery charge state from battery charge module319of the battery pack computing device313. In response to the request for the current battery charge state, the battery pack computing device313may read out a charge from battery charge module319electrically coupled to the battery315. For example, a voltage, charge, and/or current may be read out using the battery charge module319. The battery pack computing device313may provide the read out to the computing device309of the transit vehicle110. The computing device309of the transit vehicle110may determine whether the read out is below a predetermined threshold charge amount indicating that the battery315requires charging or replacement.

In some embodiments, the battery pack computing device313may determine whether the read out is below the predetermined threshold charge amount and provide a result to the computing device309of the transit vehicle110, a dock computing device311, or management system240via the battery pack computing device's313communication modules325. For example, the battery pack computing device313may calculate a battery percentage indicating a current state of the battery315, compare the battery percentage to a threshold percentage such as, for example, 20% to determine whether the current state of the battery315indicates that the battery315requires replacement or charging.

After it is determined that the battery charge is below the predetermined threshold indicating that battery charging or replacement would be required, process600proceeds to block604. At block604, a first end513of the battery pack assembly124is removed from a latch518of a first securing assembly512of a battery mount assembly125. In some embodiments, the latch518of the first securing assembly512may be electromechanically disengaged after a computing device (e.g., on printed circuit board516) of the first securing assembly512receives a wireless communication key such as a signal provided by an NFC tap.

At block606, a second end515of the battery pack assembly124is removed from the latch of a second securing assembly524. In some embodiments, the latch of the second securing assembly524may be electromechanically disengaged after a computing device of the second securing assembly524receives a wireless communication key such as another NFP tap. In other embodiments, the latch of the second securing assembly524may be electromechanically disengaged synchronously with the latch of the first securing assembly512, such as when the first securing assembly512receives the aforementioned wireless communication key.

In various embodiments, the latches of the first securing assembly512and the second securing assembly524may be configured to receive a physical key to mechanically engage and disengage the latching mechanisms thereof.

At block608, a first end of a charged and/or replacement battery pack assembly may be latched into the first securing assembly. In some cases, the charged battery pack assembly may be the same battery pack assembly124that was removed but now has a charge. In other cases, the charged battery pack assembly may be a different battery pack assembly with a charge greater than the charge of the removed battery pack assembly124.

At block610, a second end of the charged battery pack assembly may be latched into the second securing assembly524such that the charged battery pack assembly is disposed between the securing assemblies512and524.

At block612, the charged battery pack assembly may be electrically coupled to a propulsion system122of a micro-mobility transit vehicle110via various wires as discussed with reference to process400.