System and method for tracking light electric vehicle rentals

Abstract

To provide a tracking system and method for automatically determining when a ride on a vehicle is terminated by using a variety of signal inputs and accurately charging a user for utility charges for a time that the vehicle was used.SOLUTION: In a method, a user reserves a vehicle using a mobile terminal (310), and starts a ride or reservation by a mobile application (320). The mobile application transmits to a server a message that a ride is started later on, the server then starts a ride timer and receives an input signal from a plurality of terminals including the vehicle being used, a user terminal associated with the user, or a vehicle near the vehicle being used (330). The user transmits to the server a temporary stop instruction with a temporary stop button on the mobile application, and the user temporarily stops riding (340). The server causes the mobile application to display warning to stop a ride within a prescribed period of time, stops a ride when the vehicle is in an idle state for a prescribed time, and calculates ride costs (360).SELECTED DRAWING: Figure 3

Description

[Background technology]

[0001] Ride-sharing of light electric vehicles (e.g., scooters, bicycles, mopeds) is becoming popular for short urban trips. The types of light electric vehicle renters vary widely, and their interactions with ride-sharing vehicles vary. Riders sometimes forget to end their trip, and this human error can result in late fees. This results in a poor user experience. Summary of the Invention

[0002] Accurate tracking of vehicle rental status is important for both riders and ride-sharing companies. Charging riders for unused rides can be frustrating, leading to low repeat ridership and complaints. On the other hand, failing to charge riders for unused or reserved rides can hurt profits. This problem is compounded in automated, computer-driven systems where hundreds, thousands, or even tens of thousands of rides can occur per day in a city or around the world.

[0003] Some systems require the user to manually complete the ride termination process, while others set a maximum ride time, such as 1.5 hours, with a timer that automatically ends the ride after 2 hours if the user forgets to end the ride via a smartphone app or other means. Other possible reasons for a user failing to end a ride include the vehicle being in a no-parking zone, the smartphone running out of battery, or a loss of internet connection. In this case, the user will be charged for 1.5 hours even if they only used the vehicle for a portion of that time. Charging for the full 1.5 hours could result in credit card billing failures due to higher than expected payments, or an increased risk of users canceling charges due to errors or dissatisfied requests for refunds. If a user fails to end a ride, it also prevents other users from using the vehicle during that time.

[0004] The system disclosed herein ensures fair treatment of users by providing accurate billing, which can lead to improved customer satisfaction, increased ridership, and reduced uncollected revenue, refunds, penalties, and customer service inquiries. Additional benefits include accurate and quick trip termination by detecting the vehicle's speed, location, and time of day. Faster trip termination also allows light electric vehicles to be available to other users sooner. Embodiments are applicable to a variety of vehicles, including bicycles, scooters, and mopeds.

[0005] In a first example, the system can detect the end of a ride without manual user input from various hardware and software inputs from a computer on the kei vehicle, the user device, nearby kei vehicles, ride time, Bluetooth connection status, and other inputs. The system may use these inputs to determine whether the kei vehicle has been idle for a certain period of time, is not in operation, or is separated from the user's user device. The user device may be equipped with an app that periodically sends its operational status to a server. The kei vehicle may similarly send its operational status to a server. The system may use various inputs, including heuristics, to accurately and automatically predict or determine whether a ride has ended. This allows the user to end their ride simply by exiting the vehicle without manual input.

[0006] In one example, the system can detect when a ride has reached its maximum 1.5-hour limit and infer that this is a false alarm, since rides longer than 1.5 hours are extremely rare. This allows the system to charge only for the time between the time the rider starts the ride and the time the vehicle goes idle. If the rider is actually using the light vehicle, the system can automatically safely end the ride (to avoid sudden stops while driving). This reduces electricity consumption by allowing the light vehicle to enter a lower-power standby state more quickly, and ensures that the vehicle can be retrieved before it goes offline.

[0007] This Summary is provided to introduce selected, simplified versions of concepts that are more fully described below in the Detailed Description. This Summary is not intended to identify key or essential features of the claimed subject matter or to narrow the scope of the claimed subject matter. [Brief explanation of the drawings]

[0008] Non-limiting and non-exhaustive examples are described with reference to the following figures: [Figure 1A] 1 illustrates different types of light electric vehicles in accordance with one or more embodiments. [Figure 1B] FIG. 1 is a diagram showing an outline of elements constituting a light electric vehicle. [Figure 2] FIG. 1 illustrates a ride termination system associated with a light vehicle. [Figure 3] FIG. 1 illustrates an example of a computer-implemented method for tracking ride bookings and completions through payments. [Figure 4] FIG. 10 is a diagram illustrating an example of a ride summary. [Figure 5] FIG. 1 illustrates a system of a computer device coupled or associated with power hierarchy management of secondary batteries of a light electric vehicle. DETAILED DESCRIPTION OF THE INVENTION

[0009] In the following detailed description, reference is made to the accompanying drawings, which form a part hereof, and in which specific embodiments are shown by way of illustration. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the disclosure. The examples may be used as methods, systems, or apparatuses. Thus, the examples may be implemented in hardware, entirely in software, or combining software and hardware aspects. Therefore, the following embodiments should not be construed in a limiting sense, and the scope of the present disclosure is defined by the appended claims and their equivalents.

[0010] Light electric vehicles (scooters, bicycles, etc.) may be connected to a system that includes a backend and a network of user computer terminals, each of which may be connected to each other via various networks connected to the Internet.

[0011] Described herein are methods and systems for terminating a ride in a vehicle, such as a light electric vehicle or automobile.

[0012] In one example, a server may receive input that a user is reserving a ride. At this time, the server may start a ride timer. The server also receives multiple inputs corresponding to the ride, including the speed of the ride and location information of the ride. The server determines whether the multiple inputs satisfy multiple conditions, including whether the inputs received from the ride indicate that the ride moved within a predetermined time and whether the ride traveled more than a predetermined distance within the predetermined time. If the multiple inputs satisfy the multiple conditions, the server may stop the ride timer. The server may calculate a ride cost, where the ride cost comprises the duration of the ride minus the predetermined time. The server may send the ride cost to an application on the user terminal. The ride cost may be displayed by the application on the user terminal.

[0013] Although aspects of the present disclosure describe light electric vehicles, other vehicles can also benefit from the systems and methods for ride termination, such as mopeds, skateboards, cars, skates, and other vehicles can also benefit from aspects herein.

[0014] 1A illustrates an exemplary environment 100 in which embodiments of the present disclosure may be implemented. As illustrated, the environment 100 includes at least one electric scooter 110, at least one electric bicycle 120, and a rechargeable battery kiosk 130. The electric scooter 110 and the electric bicycle 120 are examples of light electric vehicles. Embodiments herein also apply to other types of light electric vehicles and larger vehicles.

[0015] The environment 100 may include a network service that receives information from the electric scooter 110 or the electric bicycle 120 (also referred to herein as light electric vehicles) through a network communication channel (e.g., one or more networks, the Internet, etc.). This information may enable a user using a client application (e.g., a mobile application running on a mobile device) executing on a computer terminal to locate, request, and / or reserve (e.g., rent or borrow) one or more light electric vehicles. This information may also enable a user to locate, request, and / or reserve secondary batteries for the light electric vehicles. In some examples, a secondary battery may be used in more than one type of light electric vehicle. For example, the same secondary battery may be used in the electric scooter 110 and the electric bicycle 120.

[0016] In some embodiments, the network service may include one or more computer systems and servers that are remote from the user and the light electric vehicle. The one or more computer systems may include application programming interfaces (APIs) that enable the computer systems to send, receive, and otherwise interact with the computer terminal, the light electric vehicle 110, 120, or the rechargeable battery kiosk 130. For example, a mobile device application may have an interface that allows it to access information on the mobile device, such as using APIs related to location information (e.g., GPS), accelerometer, and location information determined from the data. This allows the mobile device application to send and receive data through the network communication interface or use other features of the mobile device.

[0017] For example, a client application executed by a user on a computer terminal receives information about the location of one or more light electric vehicles by the network service over a network communication channel. The current location of each light electric vehicle may be provided on a user interface of the client application. Additionally or alternatively, location information about the location of one or more light electric vehicles may be communicated between multiple light electric vehicles and / or multiple client applications executing on one or more computer terminals.

[0018] In one embodiment, the user interface of the client application includes a map displaying the measured current location of the user and / or the measured current location of the light electric vehicle. In some embodiments, the measured current location of the user and / or the measured current location of the light electric vehicle is derived at least in part based on Global Positioning System (GPS) data (or other location information) received by the network service over a network communication channel.

[0019] The user interface of the client application may display the location information of the user and the light electric vehicle with different icons (or other similar notations). When the location information is displayed, the user may select an icon representing a type of light electric vehicle (e.g., an icon representing an electric scooter 110 or an icon representing an electric vehicle 120). The user interface of the client application may then generate or determine (e.g., provide route guidance for) a route from the user's current location to the selected light electric vehicle. Selecting an icon may allow the user to reserve (e.g., hold) the light electric vehicle (to ensure that the light electric vehicle is available at the determined location when the user arrives) and rent and / or borrow the light electric vehicle for a certain period of time.

[0020] Each light electric vehicle and / or network service includes a location tracking system that tracks, receives, and / or measures the current location of each light electric vehicle while it is in use. In some embodiments, the location tracking system tracks the location information of the light electric vehicle in real time or substantially real time. In other embodiments, the location tracking system measures the location information of the light electric vehicle periodically (e.g., every minute, every five minutes, every ten minutes, etc.). These periodic intervals may be referred to as heartbeats. In still other embodiments, the location tracking system may track the location information of the light electric vehicle in real time or substantially real time when the light electric vehicle is being rented or in use by a user, or may periodically track the location information of the light electric vehicle when the light electric vehicle is reserved or not in use. The location information may be exchanged directly between the light electric vehicle and the network service, or there may be any peer-to-peer exchange. For example, information of a first electric vehicle may be transmitted to a second electric vehicle, and the second electric vehicle may transmit the location information of the first electric vehicle and / or the location information of the second electric vehicle to the network service. Additionally or alternatively, the location information may be transmitted to the network service through a client application running on a computer terminal, for example, the location information may be transmitted from the electric vehicle to the client terminal and then transmitted from the client terminal to the network service.

[0021] One or more computer systems of the network service may include a matching system. The matching system receives, manages, or otherwise processes various requests from users. The requests may include requests for light electric vehicle rentals and requests for light electric vehicle reservations. For example, when a request for vehicle rental is received from a client application running on a user's computer terminal, the matching system may communicate with a location tracking system to determine which electric vehicle should be matched or assigned to the requesting user. Additionally or alternatively, the matching system may be used by a vehicle provider to retrieve and locate one or more light electric vehicles.

[0022] The network service's one or more computer systems may include a database that stores information about each light electric vehicle and each electric vehicle's current location, number of rides, and revenue. The network service's one or more computer systems may include a payment system that processes user payment information. For example, when a user rents and uses a light electric vehicle, the user may be charged a usage fee based on the duration of use and / or distance traveled. When the user finishes using the light electric vehicle (e.g., by arriving at a destination, check-in point, or rechargeable battery kiosk 130), the payment system may automatically end the ride and process the user's payment information.

[0023] As described above, the environment 100 includes one or more light electric vehicles, including, but not limited to, electric scooters 110 and electric bicycles 120. In some embodiments, the electric scooter 110 includes vehicle elements (e.g., wheels, axles, baseboard, handlebars, braking mechanism, etc.), one or more electric motors, a control system, sensors, a speaker, and / or lighting, which may be powered by a secondary battery. The secondary battery may be secured to the electric scooter 110 by a battery holster.

[0024] Similarly, in some embodiments, the electric bicycle 120 may include vehicle elements (e.g., wheels, axles, chains, gears, bicycle seat, handlebars, bicycle frame, braking mechanism, etc.), one or more electric motors, a control system, sensors, speakers, and / or lighting, which may also be powered by secondary batteries. The sensors may include positional elements (e.g., GPS), a speedometer, an accelerometer, or pressure sensors in the grips or seat.

[0025] In FIG. 1B, a block diagram of an electric scooter 110 is shown. In various aspects, the electric scooter 110 may include a battery, a drivetrain, and a head unit. The battery may be used to power both the drivetrain and the head unit of the electric scooter 110. The head unit may include a processor and a communications link. As described herein, the processor may play a role in determining whether a ride has ended. For example, the processor may send and receive various signals to and from a user terminal, another light electric vehicle, or a server. As described in detail throughout this specification, signals are associated with booking and ending a ride.

[0026] As described herein, the communication link may be capable of communicating through various communication channels, such as 3G, 4G, 5G, LTE, Bluetooth, Wi-Fi, etc. The processor and / or communication link may select and / or restrict or limit the use of one or more communication channels. By way of example, a communication channel may be used based on detecting a computer terminal that is available to receive communications through the associated communication channel.

[0027] 2 illustrates a ride-stop system 200 for a light electric vehicle 210. In addition to the light electric vehicle 210, the system 200 may include a network 220, a light electric vehicle 230 (which may be in close proximity to the light electric vehicle 210), a computer terminal 240, and a server 250. The light electric vehicle 210 and the light electric vehicle 230 may have components and functionality similar to those illustrated for the light electric vehicles 110, 120, and the secondary battery kiosk 130 in FIGS. 1A and 1B. The light electric vehicle 210 may wirelessly communicate with the network 220, the light electric vehicle 230, and / or the computer terminal 240 through a communication channel (as described herein) using a communication link (e.g., communication link 174). As described herein, information about the light electric vehicle 210 may be requested or desired by the network 220 (also referred to herein as a network service) and / or the computer terminal 240 (as it may be relevant to a potential user of the light electric vehicle 210).

[0028] As shown, there may be various network communication paths by which light electric vehicle 210 transmits information to network 220. For example, information may be transmitted directly from light electric vehicle 210 to network 220 through a communication channel. In other embodiments, light electric vehicle 210 may transmit communications or information indirectly to network 220. For example, indirect communication may include information being transmitted from light electric vehicle 210 to computer terminal 240 through a communication channel, and the information may be relayed from computer terminal 240 to network 220 if a communication channel exists between computer terminal 240 and network 220. As another example of indirect communication, light electric vehicle 210 may transmit information to nearby light electric vehicle 230. Light electric vehicle 230 may then relay the information to computer terminal 240 and / or network 220 if a communication channel exists between light electric vehicle 230 and computer terminal 240 and / or network 220. If light electric vehicle 230 relays information to computer terminal 240, the information may also be relayed from computer terminal 240 to network 220 if there is a communications channel connecting computer terminal 240 and network 220. In either manner, communications to network 220 may be directed through network 220 to any terminal or server.

[0029] Furthermore, the client communication path by which light electric vehicle 210 transmits information to computer terminal 240 may vary. For example, information may be transmitted directly from light electric vehicle 210 to computer terminal 240 through a communication channel. In other embodiments, light electric vehicle 210 may transmit communication or information indirectly to computer terminal 240. For example, indirect communication may include information being transmitted from light electric vehicle 210 through a communication channel to network 220, and the information may be relayed from network 220 to computer terminal 240 if a communication channel exists between computer terminal 240 and network 220. As another example of indirect communication, light electric vehicle 210 may transmit information to light electric vehicle 230. Light electric vehicle 230 may then relay the information to computer terminal 240 and / or network 220 if a communication channel exists between light electric vehicle 230 and computer terminal 240 and / or network 220. When light electric vehicle 230 relays information to network 220, the information may be relayed from network 220 to computer terminal 240 when a communication channel exists between computer terminal 240 and network 220.

[0030] While FIG. 2 shows light electric vehicle 210 and light electric vehicle 230, it should be understood that information may be relayed to multiple other light electric vehicles in a peer-to-peer network. In some examples, information may be shared among multiple light electric vehicles until received at a desired location or terminal (e.g., network 220 and / or computer terminal 240). For example, information about a first vehicle may be sent to a second vehicle, and then to a third vehicle, and so on, until the information is received by a vehicle capable of transmitting the information to computer terminal 240 and / or network 220. In other examples in which light electric vehicle 210 transmits information to light electric vehicle 230, light electric vehicle 230 may transmit information related to light electric vehicle 210 in addition to information related to light electric vehicle 230 and / or information received from other light electric vehicles (such that information for multiple light electric vehicles may be communicated). Information for multiple light electric vehicles may be shared on a peer-to-peer network.

[0031] FIG. 3 illustrates an example flow 300 for an automatic stopping process. In this embodiment, a user may use a mobile device to reserve a ride (step 310). The mobile device may include an application corresponding to a ride-sharing service for personal rides, such as scooters, cars, or motorcycles. The user may initiate the ride or reservation, for example, by clicking a button on the mobile application. The mobile application may then send a message to server 250 that the ride has begun (step 320). Server 250 may then start a ride timer starting at 00:00:00. In step 330, the server may receive input signals from multiple devices, including the vehicle being boarded, a user device associated with the user, or vehicles near the vehicle being boarded, as shown in FIG. 2. The signal inputs may include the vehicle's speed, obtained from a speedometer on the vehicle, or a GPS signal, obtained from the vehicle or the user device. Further signal inputs may include the vehicle's current location, also obtained from a GPS or similar location service. Additional inputs may include, for example, movement detected by one or more accelerometers on the user terminal or vehicle, input from a throttle or brake on the vehicle, detected movement from pressure sensors on parts of the vehicle that the user is in contact with, such as grips, seats, etc. Additional inputs may include geomagnetic sensors to indicate direction, Hall effect sensors to detect whether the vehicle is locked, gyroscopes to sense the orientation of the vehicle, and proximity sensors to detect whether the vehicle is in use.

[0032] The illustrated embodiment includes a loop 340 that allows the user to pause the ride, for example, by pressing a pause button on the mobile device application and receiving a pause instruction from the server. This allows the user to continue the reservation while stopping, for example, to buy coffee or meet up with a friend. This embodiment allows the vehicle to enter a low-power state in which it sends heartbeats to the server 250 less frequently or stops sending heartbeats entirely. Alternative embodiments may continue to send signals to the server 250. During the pause, the server 250 may charge the user a reduced fare or the regular fare. In either case, the server 250 will not terminate the ride during the pause unless, for example, the pause exceeds a predetermined time, e.g., 30 minutes. In some embodiments, the user may be able to select the length of the pause, for example, in 10-minute increments up to one hour. The server 250 remains paused for that period of time.

[0033] Step 350 illustrates server 250 determining whether signal inputs received from one or more vehicles or mobile applications match predetermined criteria. Embodiments may use a variety of criteria. One criterion may be the identity of the user, for example, whether the user is a customer or an employee. The ride termination algorithm may differ depending on whether the user is a customer or an employee taking a test ride. The algorithm may also differ depending on whether the user is riding individually or in a group, for example, a single user unlocking multiple vehicles for a group. Additional criteria may include whether the most recent heartbeat speed was 0 miles per hour. If the vehicle has been idle for a predetermined time, for example, five minutes, server 250 may instruct the mobile application to display a warning that the ride will be terminated within five minutes. If the vehicle then remains idle for another five minutes, the ride may be terminated. Embodiments may require that the vehicle not travel a predetermined distance, for example, 500 meters, during this time. Server 250 may then terminate the ride after the vehicle meets the criteria, which in this example is 10 minutes. The system may or may not charge the user for this idle time.

[0034] In further embodiments, one or more warning messages may be sent to the user that the suspended ride will be terminated. For example, server 250 may send one or more warnings at regular intervals, and when a maximum time is reached, server 250 may terminate the ride. Alternatively, an application on the user's mobile device may allow the user to extend the suspension time. Server 250 may or may not charge the user for the suspended period.

[0035] Another criterion for terminating a ride may be whether server 250 receives a heartbeat signal from the ride for a certain period of time, e.g., 15 minutes. This may occur, for example, if the ride loses power, experiences a technical failure, or loses network connectivity. Server 250 may terminate a ride if it does not receive a heartbeat signal for the predetermined period of time. Server 250 may or may not charge the user for the predetermined period of time. Server 250 may send an advisory message to the user if it has not received a heartbeat signal by the end of the predetermined period of time. Server 250 may also record the location of the user's terminal via a mobile application even if it loses contact with the ride. Server 250 may store this information in order to locate the lost ride.

[0036] Another useful criterion is the distance between the user's mobile device and the vehicle. If the vehicle is idle and the user's mobile device is located more than a predetermined threshold distance from the vehicle, the system can infer that the user's ride has ended. These criteria may be used alone or in combination with any other criteria. Different cases may be anticipated and treated differently for scooters, motorcycles, mopeds, and cars. Therefore, it is useful to be able to adjust the criteria to suit different situations.

[0037] The system may take into account the remaining battery life of the user's mobile device. For example, if the user's mobile device has low power, say 5%, the mobile device may lose power before the end of the ride, preventing the user from manually ending the ride. The system may allow the user to continue the ride for a predetermined period of time, say 5 minutes, after which the ride will end and the vehicle will be locked.

[0038] The system may also terminate a ride if the vehicle is detected in a no-parking zone. A rider may not realize they have left the vehicle in a no-parking zone and fail to end the ride. In this case, the system may automatically stop the ride when the vehicle is idle in the no-parking zone for a predetermined amount of time.

[0039] In another embodiment, the ride time can be capped at, say, 1.5 hours, after which the ride is automatically stopped.

[0040] The system can stop a ride in a variety of ways. For example, the server 250 may instruct the vehicle to stop at a safe location. The server 250 may gradually reduce the throttle until the vehicle stops. The server 250 may instruct the vehicle to slowly apply the brakes until the vehicle stops. Different types of vehicles may have different stopping procedures. For example, larger vehicles require more caution in collisions compared to lighter vehicles such as scooters. Therefore, larger vehicles may take a longer stopping procedure to avoid sudden changes that could lead to a collision. On the other hand, scooters are less likely to maintain speed in heavy traffic and can stop more quickly.

[0041] The server 250 may then calculate the cost of the trip and perform additional stopping procedures in step S360. These procedures may include determining the time for which a fee is charged, such as whether to include pauses during the trip or idle time at the end of the trip but before stopping the trip. The server may change the vehicle's status in the database from in use to available, and may also change the trip's status from in progress to completed. The server 250 may then generate a message on the user's mobile application containing the fare and a trip summary, e.g., the trip route. The trip cost may be determined based on the total trip time and may include fixed fees such as unlocking fees. The final cost may be a percentage of the trip cost based on the total trip time divided by the total reservation time. Therefore, this percentage may affect not only the fee related to the trip time but also the fixed fee. This cost may also incorporate discounts or promotions that may be applied to the user. The trip summary is like a receipt. Finally, the server may lock the vehicle until it is rented by another user or until it needs to be inspected.

[0042] FIG. 4 illustrates example embodiments of an individual trip summary 400 and a group trip summary 410. Trip summaries 400 and 410 include trip completion indicators 401 and 411, which further include trip routes 402 and 412. Trip summaries 400 and 410 also include trip end notifications 403 and 413, indicating that the system automatically stopped the trip and charged only the trip duration. FIG. 4 also includes trip details 404 and 414, indicating the date and time of the trip, the amount, distance, trip duration, and the number of points earned for the trip. Finally, trip summaries 400 and 410 include a rating system, in this example a five-star rating system 405 and 415.

[0043] 5 illustrates a system diagram of a computer terminal that may be integrated with or otherwise associated with power hierarchy management of a secondary battery of a light electric vehicle. The computer terminal 500 may be integrated with or associated with a light electric vehicle and / or a light electric vehicle head unit and / or power hierarchy management system described herein. In FIG. 5, components (e.g., hardware) of the computer terminal 500 are illustrated, which may be used to implement various aspects of the present disclosure.

[0044] The computer terminal 500 may include at least one processing unit 510 and a system memory 520. The system memory 520 may include, but is not limited to, volatile storage (e.g., random access memory), non-volatile storage (e.g., read-only memory), flash memory, or any combination of these memories. The system memory 520 may further include an operating system 530 and one or more program modules 540 that control the operation of the computer terminal 500. The program modules 540 may be responsible for collecting or determining expected power readings, light electric vehicle information, etc. The system memory 520 may also store and / or provide power hierarchy management 550, which triggers or determines power hierarchy management for the light electric vehicle's battery, as described herein. The system memory 520 may also store various program modules and data files, including operating state information. While executing on the processing unit 510, the program modules 540 may perform the various processes described above.

[0045] Computer terminal 500 may have additional features and functionality. For example, computer terminal 500 may include additional data storage devices (e.g., removable and / or non-removable storage) such as, for example, magnetic disks, optical disks, or tape. These additional storage devices are referred to as removable storage 560 and non-removable storage 570.

[0046] Additionally, embodiments of the present disclosure may be implemented on a single chip containing discrete electronic elements, packaged or integrated electronic chips containing logic gates, or electrical circuits or electronic elements comprising microprocessor-based circuitry, or a single chip containing a microprocessor. For example, embodiments of the present disclosure may be implemented via a system-on-chip (SOC) that integrates each or many of the components shown in Figure 5. Such an SOC device may include one or more processing units, graphics units, communications units, system virtualization units, and various application functions, all integrated (or "burned") onto the chip substrate as a single integrated circuit.

[0047] When operating via a SOC, the functions disclosed herein may be performed via application-specific logic integrated with other components of the computer terminal 500 on a single integrated circuit (chip). The present disclosure may also be implemented using other technologies capable of performing logical operations such as AND, OR, and NOT. Such technologies include, but are not limited to, mechanical, optical, fluidic, and quantum. Additionally, embodiments of the present disclosure may be implemented using a computer terminal associated with or integrated with an electric vehicle and / or any other circuit or system.

[0048] The computer terminal 500 may include one or more communication systems 580 that enable communication between the electric vehicle and a secondary battery, other computer terminals 595, network services, etc. Examples of communication systems 580 include, but are not limited to, wireless communication, wired communication, cellular communication, radio frequency (RF) transmitter, receiver, and / or transmitter circuitry, a controller area network (CAN) bus, a universal serial bus (USB), parallel, serial ports, etc.

[0049] Computer terminal 500 may have one or more input devices and / or one or more output devices, shown as input / output devices 585. These input / output devices 585 may include keyboards, buttons, switches, sound or voice input devices, haptic devices, tactile, pressure and / or swipe input devices, displays, speakers, etc.

[0050] The computer terminal 500 may include one or more sensors 590. The sensors may be used to detect or provide information about the operating status of the computer terminal 500. In other embodiments, the sensors 590 may provide information about the light electric vehicle via diagnostic trouble codes (DTCs) and / or whether the light electric vehicle's brake checker is operating properly and / or is being used correctly (e.g., a sensor transmitting a signal to the CAN bus indicating whether the handlebars and brake levers are properly / fully inserted into the light electric vehicle's brake checker). As mentioned above, the sensors may include a GPS, a speedometer, an accelerometer, or grip or seat pressure sensors.

[0051] The term computer-readable media as disclosed herein may include computer storage media, which may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, and the like.

[0052] System memory 520, removable storage 560, and non-removable storage 570 are all examples of computer storage media (e.g., storage memory). Computer storage media may include RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology accessible by computer terminal 500, CD-ROM, digital versatile disk (DVD) or other optical storage device, magnetic cassette, magnetic tape, magnetic disk drive, or other magnetic storage device, or any other product used to store information. Any of these computer storage media may be part of computer terminal 500. Computer storage media do not include carrier waves or other propagated or modulated data signals.

[0053] Communication media may be embodied by computer-readable instructions, data structures, program modules, or other data in a data signal modulated by a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" may refer to a signal that has one or more characteristics set or changed in such a manner as to decipher information in the signal. By way of example, and not limitation, communication media may include wired media such as wired networks and direct-wired connections, and acoustic, radio frequency (RF), infrared, and other wireless media.

[0054] Unless the context clearly requires otherwise, words such as "comprises" and "comprises," as used in the specification and claims, are synonymous with "includes" or "comprises," and should be interpreted in an inclusive sense, rather than an exclusive or exhaustive sense. As used herein, "coupled," "connected," or any variation thereof, means any direct or indirect connection or coupling between two or more elements, and the connection or coupling may be physical, logical, or a combination thereof. Furthermore, when used in this application, terms such as "herein," "above," "below," and similar terms refer to this application as a whole, not to a particular point in time. Where the context permits, terms used in the singular and plural forms in the above description may also include the plural and singular, respectively. The term "or," when used in reference to a list of two or more items, encompasses all interpretations of the term: any item in the list, all items in the list, or any combination of items in the list.

[0055] Several embodiments of the disclosed technology have been described above with reference to the figures. A computer terminal on which the described technology may be implemented may include one or more central processing units, memory, input devices (e.g., keyboards and pointing devices), output devices (e.g., displays), storage devices (e.g., disk drives), and network terminals (e.g., network interfaces). Memory and storage devices are computer-readable storage media capable of storing instructions for executing at least a portion of the disclosed technology. Furthermore, data structures and message structures may be stored or transmitted over data transmission media, such as signals over a communications link. Various communications links may be used, such as the Internet, a local area network, a wide area network, or a point-to-point dial-up connection. Thus, computer-readable media may encompass computer-readable storage media (e.g., "non-transitory" media) and computer-readable transmission media.

[0056] As used in this disclosure, "above the threshold" means that the value of the compared item is above another specified value, that the compared item is the maximum value among a specified number of items, or that the value of the compared item is within a specified upper value. As used in this disclosure, "below the threshold" means that the value of the compared item is below another specified value, that the compared item is the minimum value among a specified number of items, or that the value of the compared item is within a specified lower value. As used in this disclosure, "within the threshold" means that the value of the compared item is between two other specified values, that the compared item is the middle value among a specified number of items, or that the value of the compared item is within a specified middle value.

[0057] As used in this disclosure, the term "or" refers to any combination of members of a set. For example, the phrase "A, B, or C" refers to at least one or any combination of A, B, and C, including a plurality of any items, such as A; B; C; A and B; A and C; B and C; A, B, and C; or A and A; B, B, and C; A, A, B, C, and C, etc.

[0058] The description of the above embodiments is not intended to be exhaustive or to limit the present invention to the precise form disclosed above. While specific examples of the technology are described above for illustrative purposes, various modifications within the scope of the technology are possible. For example, while processes or blocks are presented in a specific order, alternative embodiments may perform steps or system blocks in different orders, and some processes or blocks may be removed, moved, added, subdivided, combined, and / or modified to provide alternatives or subcombinations. Each process or block may be implemented in various ways. Also, while processes or blocks are sometimes shown as being performed serially, these processes or blocks may instead be performed or implemented in parallel, or may be performed at different times. Furthermore, specific numerical values ​​set forth in this disclosure are examples only, and alternative implementations may employ different values ​​or ranges.

[0059] The teachings of the techniques provided in this disclosure may be applied to other systems, not necessarily the systems described above. Elements and acts in the various embodiments described above may be combined to provide further implementations of the techniques. Some alternative implementations of the techniques may include fewer elements as well as additional elements than the implementations described above.

[0060] The descriptions and drawings of one or more aspects provided in this application are not intended to limit or restrict the scope of the disclosure in any way. The aspects, examples, and details provided in this application are believed to be effective to occupy the present disclosure and enable others to make and use it in the best mode. The present disclosure should not be construed as limited to any aspect, example, or detail provided in this application. Whether shown and described in combination or separately, various features (both structural and methodological) are intended to be selectively rearranged, included, or omitted to produce embodiments with particular characteristics. Those skilled in the art, armed with the description and drawings of this application, may envision variations, modifications, and alternative embodiments that fall within the broad scope of the general inventive concept embodied in this application without departing from the broader scope of this disclosure.

Claims

A step of receiving, by a server via a wireless network signal, an input indicating that a user is reserving a vehicle via an application operating on a user terminal, wherein the reserved vehicle includes a current location tracking system configured to uniquely match with the user during the reservation; A step of starting, by the server, a boarding timer remote from the vehicle in response to receiving the reservation of the vehicle; A step of receiving, by the server, one or more inputs from the reserved vehicle or a sensor on the user terminal, wherein the application includes a location information interface, and the one or more inputs include vehicle speed data and vehicle location information data; A step of determining, by the server, whether the plurality of inputs meet a plurality of criteria, wherein the plurality of criteria include whether the input received from the reserved vehicle indicates that the reserved vehicle has moved within a predetermined time that can be set and stored in the memory of the server, and whether the reserved vehicle has moved a distance longer than a predetermined distance within the predetermined time; A step of stopping, by the server, the boarding timer when the plurality of inputs meet the plurality of criteria; A step of calculating, by the server, a boarding cost, wherein the boarding cost includes subtracting the predetermined time from the usage time of the reserved vehicle; A step of the server communicating with a network to bill the user based on the usage time or the travel distance; A step of transmitting, by the server, the boarding cost to the application running on the user terminal; A step of displaying, by the application, the boarding cost on the user terminal A method comprising the above steps. The method according to claim 1, wherein the plurality of inputs further include the location of the user terminal. The method according to claim 2, wherein the plurality of criteria further include whether the location of the user terminal is farther than a predetermined threshold distance from the vehicle. A step of receiving, by a server remote from the user terminal via a wireless network, an input indicating the start of boarding of the matching vehicle from a user terminal or a vehicle including a current location tracking system configured to uniquely match with the user. The step of starting, by the server, a boarding timer for the matching vehicle; The step of receiving, by the server, a plurality of inputs including the speed of the vehicle and the position information of the vehicle from sensors on the matching vehicle or the user terminal; The step of determining, by the server, whether the plurality of inputs meet a plurality of criteria; The step of stopping, by the server, the boarding timer for the matching vehicle when the plurality of inputs meet the plurality of criteria; The step of the server communicating with a network to bill a user based on usage time or travel distance; A method, comprising. The step of receiving, by the server, a notification indicating a pause from the user terminal; The step of temporarily stopping, by the server, the boarding timer for the matching vehicle; The method according to claim 4, further comprising. The method according to claim 4, wherein the plurality of inputs further includes whether the matching vehicle is moving. The method according to claim 4, wherein the plurality of criteria includes whether an input received from the matching vehicle indicates that the vehicle has moved within a predetermined time. The method according to claim 7, wherein the plurality of criteria further includes whether the matching vehicle has moved a distance longer than a predetermined distance within the predetermined time. The step of calculating, by the server, a boarding cost, wherein the boarding cost includes subtracting the predetermined time from the usage time of the matching vehicle; The step of transmitting, by the server, the boarding cost to an application running on the user terminal; The step of displaying, by the application, the boarding cost on the user terminal; The method according to claim 7, further comprising. The step of calculating, by the server, a boarding cost, wherein the boarding cost includes subtracting the predetermined time from the usage time of the matching vehicle; The step of transmitting, by the server, the boarding cost to an application running on the user terminal; The step of displaying, by the application, the boarding cost on the user terminal; The method according to claim 8, further comprising. The method according to claim 4, wherein the plurality of inputs further includes the position of the user terminal. **Claim 12**: The method according to claim 11, wherein the plurality of criteria further includes whether a distance between the position of the matching vehicle and the position of the user terminal exceeds a predetermined threshold. **Claim 13**: A system comprising a current location tracking system configured to uniquely match with a user, a plurality of sensors including position information elements, and a communication link a vehicle including; a position information interface, a network communication interface, and an application having a user interface to the system a user terminal including; a server communicating with the matching vehicle and the application, wherein the server is remotely present from the matching vehicle, receives, at the server, an input indicating the start of boarding of the matching vehicle from the position information interface and the network communication interface of the application, starts a boarding timer for the matching vehicle, receives a plurality of inputs including the speed and position of the vehicle from the position information elements and the communication link of the matching vehicle, determines whether the plurality of inputs meet a plurality of criteria, when the plurality of inputs meet the plurality of criteria, stops the boarding timer for the matching vehicle, and is configured to communicate with a network to bill a user based on usage time or travel distance. A system thus configured. **Claim 14**: The system according to claim 13, wherein the server is further configured to receive a pause indication from the user terminal and pause the boarding timer for the matching vehicle. A system thus configured. **Claim 15**: The system according to claim 13, wherein the plurality of inputs further includes whether the matching vehicle is moving. **Claim 16**: The system according to claim 13, wherein the plurality of criteria further includes whether an input received from the matching vehicle indicates that the matching vehicle has moved within a predetermined time. **Claim 17**: The system according to claim 16, wherein the plurality of criteria further includes whether the matching vehicle has moved a distance longer than a predetermined distance within the predetermined time. **Claim 18**: The server is further configured to calculate a boarding cost, the boarding cost including the usage time of the matching vehicle minus the predetermined time. Send the ride cost to the application running on the user terminal, The system according to claim 16, wherein the application is configured to display the ride cost on the user terminal. **Claim 19** The system according to claim 13, wherein the plurality of inputs further includes the position of the user terminal. **Claim 20** The system according to claim 19, wherein the plurality of criteria further includes whether a distance between the position of the matching vehicle and the position of the user terminal exceeds a predetermined threshold.

Images