Multifunctional management monitoring system for two-wheeled electric vehicle

Abstract

The invention provides a multifunctional management and monitoring system for a two-wheeled electric vehicle. The multifunctional management and monitoring system comprises a vehicle-mounted intelligent equipment end, a cloud management platform and a supervision platform interface module, the vehicle-mounted intelligent equipment end is installed on a two-wheeled electric vehicle and comprises a vehicle center control module, a Beidou positioning module, a camera module, a battery monitoring module, a vehicle controller linkage module, a communication module and a local storage module. The vehicle sink central controller is in communication connection with the Beidou positioning module, the camera module, the battery monitoring module, the vehicle controller linkage module, the communication module and the local storage module, and the track data packet, the evidence index packet and the battery safety data are uploaded to the cloud management platform through the communication module; a configuration strategy and an instruction issued by the cloud management platform and the supervision platform interface module are received; according to the invention, the problems proposed in the background technology are solved.

Description

Technical Field

[0001] This invention relates to the field of electric vehicle management, and more particularly to a multi-functional management and monitoring system for two-wheeled electric vehicles. Background Technology

[0002] With the widespread adoption of two-wheeled electric vehicles (including electric bicycles and electric motorcycles) in urban commuting, food delivery, shared mobility, and short-distance logistics, the resulting traffic safety, fire safety, and urban governance issues are becoming increasingly prominent. Management departments typically need to conduct data-driven monitoring of vehicle operation behavior, violation evidence collection, accident tracing, and vehicle and battery safety risks. Meanwhile, vehicle owners and operators also need to manage vehicle anti-theft, trajectory playback, and anomaly alarms in real time. However, current two-wheeled electric vehicle management mainly relies on scattered locators, recorders, or single alarm devices. 1. Positioning devices often only report the "current location" and lack a verifiable, retransmittable, and continuous trajectory recording mechanism. They are prone to losing key trajectories when the network or power is interrupted, making them difficult to use for regulatory verification and accident tracing. 2. Most dashcams rely on local storage and lack structured evidence indexes that are linked to vehicle identity, time, location, and operating status, making it difficult to form a closed loop of "event-evidence-disposal"; 3. Common solutions for battery safety only perform simple temperature measurement or single threshold alarm, lacking hierarchical strategies and linkage with vehicle control, and even more so lacking interlocking condition restrictions, which may lead to problems such as false triggering or unsafe handling. 4. Local regulatory platforms typically require structured data such as vehicle statistics, battery life and safety, and traffic violation alerts, but existing devices lack a unified data organization, interface integration, and auditable mechanism.

[0003] Therefore, it is necessary to provide a new multi-functional management and monitoring system for two-wheeled electric vehicles to solve the above-mentioned technical problems. Summary of the Invention

[0004] To address the aforementioned technical problems, this invention provides a multi-functional management and monitoring system for two-wheeled electric vehicles, which solves the problems mentioned in the background section.

[0005] The multi-functional management and monitoring system for two-wheeled electric vehicles provided by this invention includes an on-board intelligent device terminal, a cloud management platform, and a monitoring platform interface module; The vehicle-mounted intelligent device is installed on the two-wheeled electric vehicle and includes a vehicle central control unit, a Beidou positioning module, a camera module, a battery monitoring module, a vehicle controller linkage module, a communication module, and a local storage module. The vehicle central control unit is communicatively connected to the Beidou positioning module, camera module, battery monitoring module, vehicle controller linkage module, communication module, and local storage module, for the following purposes: The system collects location information output by the BeiDou positioning module and generates a trajectory data packet containing a timestamp to record the vehicle's driving trajectory and route. The camera module is controlled to record continuously, and when a preset event is triggered, an index package of illegal / risk evidence associated with the vehicle's identity, time, location, and operating status is generated. The battery temperature data output by the battery monitoring module is collected and a graded alarm strategy is executed. When the safety interlock conditions are met, the power limiting and power failure protection actions are triggered through the vehicle controller linkage module. The communication module uploads the trajectory data packet, evidence index packet, and battery safety data to the cloud management platform, and receives configuration strategies and instructions from the interface modules of the cloud management platform and the monitoring platform. The cloud management platform is used to store, statistically analyze, send alarms and manage events for data uploaded from in-vehicle intelligent devices. It also outputs vehicle statistics, battery life and safety information, traffic violation information and reminders to the local regulatory platform through the regulatory platform interface module, and provides local interactive information services.

[0006] Preferably, the vehicle central control unit adopts an adaptive sampling and network disconnection retransmission mechanism for trajectory data packets. The adaptive sampling includes at least: sampling in the driving state according to a first sampling period, sampling at a reduced frequency according to a second sampling period when the speed is low or the stationary state, and sampling at a higher frequency according to a third sampling period when a preset event is triggered. When the network is down, the trajectory data packets are cached in the local storage module according to their sequence number. After the network is restored, they are retransmitted in sequence and carry verification information for cloud deduplication and integrity verification.

[0007] Preferably, the camera module's loop recording adopts a segmented storage mechanism, whereby the vehicle central control unit divides the video into multiple video segments according to a preset duration and stores them in a loop, overwriting each other. When the preset event triggering conditions are met, the vehicle control center locks the video segments or fragments corresponding to the preset duration before and after the event to prevent them from being overwritten.

[0008] Preferably, the evidence index package includes at least: a unique vehicle identifier, event type, event start and end times, event location, vehicle speed and heading, corresponding video segment identifier and segment offset information, a hash value for integrity verification, and signature or timestamp verification information for tamper-proof verification.

[0009] Preferably, the in-vehicle intelligent device adopts an evidence upload strategy of "upload index first, and obtain video on demand": Vehicle Hub Central Control prioritizes uploading the evidence index package to the cloud management platform; When the cloud management platform generates an evidence collection request based on regulatory spot checks, event review, or authorized evidence collection needs, it requests the corresponding video segments or fragments from VehicleHub Control via downlink commands. VehicleHub Control then uploads the requested video segments or fragments accordingly.

[0010] Preferably, the graded alarm strategy includes at least a first-level warning, a second-level alarm, and a third-level danger threshold control: when the battery temperature reaches the first threshold, a first-level warning is triggered and reported; when the battery temperature reaches the second threshold or the abnormality persists for a preset duration, a second-level alarm is triggered and a reminder is pushed to the vehicle owner and the monitoring terminal. When the battery temperature reaches the third threshold or meets the combined conditions of abnormal temperature and current / voltage, a level 3 hazard is triggered and a handling record is generated.

[0011] Preferably, the vehicle controller linkage module sets safety interlock conditions before performing power limiting and power failure protection actions. The safety interlock conditions include at least any two of the following: cloud policy allows the execution of protection actions, vehicle speed is lower than a preset safety threshold, vehicle physical button confirmation, and vehicle owner confirmation. When the interlock conditions are met, the vehicle control center sends control commands to the vehicle controller linkage module and records the control commands, the interlock condition status, and the action execution results as auditable logs and uploads them to the cloud management platform.

[0012] Preferably, the data output by the regulatory platform interface module includes at least: Vehicle statistics include vehicle registration information, online rate, active mileage, and regional distribution; Battery life and safety information, including battery temperature alarm records, handling results, and battery health status trend information; Traffic violation information and violation reminders include the type of incident, time and location, evidence index identifier, and processing status; Local interactive information is limited to specific areas based on geofencing or administrative regions, and publication and reach logs are recorded.

[0013] The beneficial effects of this invention are: 1. Integrate BeiDou trajectory / route data, video evidence collection, battery temperature safety monitoring, and vehicle control into the vehicle-mounted central control unit to achieve data consistency, event traceability, and closed-loop processing; 2. By using a structured event package mechanism (time, location, vehicle identity, video clip index, and operational status), evidence collection for illegal activities becomes more reliable and management becomes more efficient. 3. Through multi-level battery temperature warning and configurable protection strategies, the risk of battery thermal damage is significantly reduced and the ability to trace accidents is improved; 4. Through standardized interfaces and strategic reporting, achieve data-driven supervision of local regulatory platforms that is connectable, statistically accurate, capable of issuing alerts, and allows for accountability. 5. Through the local interaction module, the system not only meets regulatory and security needs, but can also be expanded to the local service ecosystem, thereby improving urban governance and public service capabilities. Attached Figure Description

[0014] Figure 1 This is a schematic diagram of the overall system architecture.

[0015] Figure 2 This is a hardware block diagram of an in-vehicle intelligent device.

[0016] Figure 3 The flowchart shows the process of trajectory sampling, packaging, caching, and retransmission.

[0017] Figure 4 Flowchart for video loop segmentation and event-triggered locking, evidence index package generation and reporting. Detailed Implementation

[0018] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0019] Please refer to the following: Figure 1 , Figure 2 , Figure 3 as well as Figure 4 ,in Figure 1 This is a schematic diagram of the overall system architecture. Figure 2 This is a hardware block diagram of an in-vehicle intelligent device. Figure 3 The flowchart shows the process of trajectory sampling, packaging, caching, and retransmission. Figure 4 Flowchart for video loop segmentation and event-triggered locking, evidence index package generation and reporting.

[0020] In the specific implementation process, such as Figures 1-4 As shown, it includes an in-vehicle intelligent device terminal, a cloud management platform, and a monitoring platform interface module; wherein, the in-vehicle intelligent device terminal is installed on the two-wheeled electric vehicle and includes a vehicle central control unit, a Beidou positioning module, a camera module, a battery monitoring module, a vehicle controller linkage module, a communication module, and a local storage module; the vehicle central control unit communicates with the Beidou positioning module, camera module, battery monitoring module, vehicle controller linkage module, communication module, and local storage module respectively, for: The system collects location information output by the BeiDou positioning module and generates a trajectory data packet containing a timestamp to record the vehicle's driving trajectory and route. The camera module is controlled to record continuously, and when a preset event is triggered, an index package of illegal / risk evidence associated with the vehicle's identity, time, location, and operating status is generated. The camera module's loop recording uses a segmented storage mechanism. The vehicle control center divides the video into multiple video segments according to a preset duration and stores them in a loop, overwriting each other. When a preset event trigger condition is met, the vehicle control center locks the video segments or fragments corresponding to the preset duration before the event and the preset duration after the event, so that they are not overwritten.

[0021] The battery temperature data output by the battery monitoring module is collected and a graded alarm strategy is executed. When the safety interlock conditions are met, the power limiting and power failure protection actions are triggered through the vehicle controller linkage module. The vehicle control module uploads trajectory data packets, evidence index packets, and battery safety data to the cloud management platform and receives configuration strategies and instructions from the interface modules of the cloud management platform and the supervision platform. The vehicle control module adopts an adaptive sampling and network disconnection retransmission mechanism for trajectory data packets. The adaptive sampling includes at least: sampling in the driving state according to the first sampling period, sampling at a reduced frequency according to the second sampling period when the speed is low or the stationary state, and sampling at a higher frequency according to the third sampling period when a preset event is triggered. When the network is down, the trajectory data packets are cached in the local storage module according to their sequence number. After the network is restored, they are retransmitted in sequence and carry verification information for cloud deduplication and integrity verification.

[0022] Before the vehicle controller linkage module executes power limiting and power failure protection actions, it sets safety interlock conditions. The safety interlock conditions include at least two of the following: cloud policy allows the execution of protection actions, vehicle speed is lower than a preset safety threshold, on-board physical button confirmation, and vehicle owner confirmation. When the interlock conditions are met, the vehicle control center sends control commands to the vehicle controller linkage module and records the control commands, the interlock condition status, and the action execution results as auditable logs and uploads them to the cloud management platform.

[0023] The cloud management platform is used to store, statistically analyze, send alarms and manage events for data uploaded from in-vehicle intelligent devices. It also outputs vehicle statistics, battery life and safety information, traffic violation information and reminders to the local regulatory platform through the regulatory platform interface module, and provides local interactive information services.

[0024] The in-vehicle intelligent device adopts an evidence upload strategy of "upload index first, and obtain video on demand": Vehicle Hub Central Control prioritizes uploading the evidence index package to the cloud management platform; When the cloud management platform generates an evidence collection request based on regulatory spot checks, event review, or authorized evidence collection needs, it requests the corresponding video segments or fragments from VehicleHub Control via downlink commands. VehicleHub Control then uploads the requested video segments or fragments accordingly.

[0025] The tiered alarm strategy includes at least a first-level warning, a second-level alarm, and a third-level hazard threshold control: when the battery temperature reaches the first threshold, a first-level warning is triggered and reported; when the battery temperature reaches the second threshold or continues to be abnormal for a preset duration, a second-level alarm is triggered and a reminder is pushed to the vehicle owner and the regulatory end. When the battery temperature reaches the third threshold or meets the combined conditions of abnormal temperature and current / voltage, a level 3 hazard is triggered and a handling record is generated.

[0026] The data output by the regulatory platform's interface module should include at least the following: Vehicle statistics include vehicle registration information, online rate, active mileage, and regional distribution; Battery life and safety information, including battery temperature alarm records, handling results, and battery health status trend information; Traffic violation information and violation reminders include the type of incident, time and location, evidence index identifier, and processing status; Local interactive information is limited to specific areas based on geofencing or administrative regions, and publication and reach logs are recorded.

[0027] Example 1 I. System Composition and Numbering Definition like Figure 1 As shown, the system in this embodiment includes: In-vehicle intelligent device terminal; cloud management platform; regulatory platform interface module; local regulatory platform like Figure 2 As shown, the in-vehicle intelligent device terminal includes at least: Vehicle Central Control: Main control MCU / SoC, RTC, encryption unit, interface and power management; Beidou positioning module: outputs positioning / velocity / heading / accuracy / time; Camera module: Outputs video stream; Battery monitoring module: BMS or acquisition board, outputting T / V / I / SOC / SOH / fault codes; Vehicle controller linkage module: connects to the motor controller or power failure relay / power limiting interface; Communication module: Any or a combination of NB-IoT / 4G / 5G; Local storage modules: eMMC / TF card / EEPROM, used for track caching, logs and video fragmentation.

[0028] II. Interface and Data Channel Definitions for Vehicle Central Control System The interface of the vehicle central control system in this embodiment can be configured as follows (which can be replaced with equivalent configurations): (1) Positioning interface: UART (NMEA / binary protocol), baud rate 9600~115200; (2)BMS Interface: CAN (500 kbps) or UART / RS485, periodically outputting battery data frames; (3)Camera Interface: USB / UVC, MIPI or SPI (low resolution), outputting H.264 / H.265 encoded streams or raw frames; (4)Controller Linkage Interface: CAN controls torque / speed limit parameters; or GPIO drives a relay to cut off power; (5)Communication Protocol: Upstream: MQTT (publishing tracks / events / batteries by topic) or HTTPS (REST); Downstream: MQTT subscribes to policies / forensic requests / regulatory instructions.

[0029] III. Implementation of Track and Route Recording (corresponding to Figure 3 ) 3.1 Definition of Track Points and Time Benchmark The vehicle aggregation central control takes the time synchronization of the Beidou positioning module as the main and the RTC as the auxiliary to generate a unified timestamp t s . Each track point P shall at least contain: t s : UTC or local time zone timestamp (milliseconds or seconds) lat, lon: Latitude and longitude (fixed-point with 1e-7 or 1e-6) spd: Speed (km / h or m / s) hdg: Heading (0~359) acc: Positioning accuracy / confidence fix: Positioning status 3.2 Adaptive Sampling Strategy As Figure 3 shown, three-level sampling is adopted: The first sampling period T_run: When the vehicle is in a driving state (spd >= V0, e.g., 3 km / h), the sampling period is 1~5 s; The second sampling period T_idle: When the vehicle is at low speed or stationary (spd < V0), the sampling period is 10~60 s; The third sampling period T_evt: When an event occurs (see 4.2 / 5.2), high-frequency sampling is entered, the period is 1 s, and the tracks for N seconds before and after the event are locked (e.g., 30 s before and 60 s after).

[0030] 3.3 Packing, Compression and Verification Track points are packed according to a time window (e.g., one packet every 60 s): track_pkg={vehicle_id,seq,start_ts,end_ts,points[],crc} seq: Packet sequence number increments; used for sorting and deduplication during network outage retransmission. points[]: Differential coding (Δlat, Δlon, Δts) can be used to reduce bandwidth. crc: CRC32 or other checksum 3.4 Offline caching and retransmission mechanism When the communication module is unable to upload: The trajectory packet is written to a queue file (e.g., track_queue.dat) in the local storage module, recording the sequence number (seq) and offset. After the network is restored: Retransmit packets in sequence according to their sequence number (seq); the cloud performs deduplication of vehicle_id+seq; and requests retransmission of packets that fail CRC verification.

[0031] IV. Camera Loop Slicing and Illegal / Risk Evidence Collection (corresponding) Figure 4 ) 4.1 Video Segmentation and Loop Recording The camera module outputs a video stream, which is then stored in a cyclical manner by the vehicle's central control system. Segment duration T_seg: for example, 60s (configurable from 30 to 300s). Segment naming: seg_{vehicle_id}_{start_ts}.mp4 Index table: seg_index records seg_id, start_ts, duration, codec, resolution, file_path, and sha256. Circular overwrite: When storage space is insufficient, delete the oldest and unlocked fragment. 4.2 Event Triggering Conditions The triggering condition must include at least one of the following: (1) Overspeed trigger: spd>V_limit, where V_limit is issued by the cloud platform 200 and supports speed limits in different regions / time periods; (2) Geofencing trigger: Vehicles enter / leave the monitored fence (key intersections, restricted areas, schools, hospitals, etc.); (3) Abnormal vibration / collision trigger: Fault signal from sensor (which may be integrated with accelerometer) or controller side, which meets the threshold (e.g., |a|>A_th or lasts for Nms); (4) Regulatory evidence collection instruction trigger: The regulatory platform interface 300 issues the evidence_request instruction, specifying a time window or region.

[0032] Video clips before and after the event is triggered and locked: pre_time: e.g., 20~60s post_time: e.g., 20~120s Locking method: Mark the corresponding segment with locked=1 to prevent overwriting, and if necessary, extract the segment to generate an independent file clip_xxx.mp4.

[0033] 4.3 Data Structure of the Evidence Index Package Each event generates one evidence index package evi_idx: vehicle_id: Unique vehicle identifier event_type: Event type (overspeed / geofence / shock / regulator, etc.) t_start, t_end: Start and end times of the event lat,lon: Location of the event (can be the trigger point or the average of the interval) spd,hdg: Running status at the time of triggering seg_id: Video segment identifier offset_start, offset_end: The offset of the clip within the segment or the clip file ID. hash: Calculates the SHA-256 hash for a file segment or clip. sig: Vehicle Central Control uses the device's private key to sign the above fields (e.g., ECC / RSA), or uses a platform-issued key for HMAC. nonce: Random number / serial number, used to prevent replay. 4.4 Reporting strategy of "upload index first, retrieve video on demand" Under normal circumstances, the vehicle-mounted terminal only uploads evi_idx (tens to hundreds of bytes); the cloud-based 200 system then issues evidence collection requests based on the event level, regulatory spot checks, or manual review. Evidence request: get_video{vehicle_id,seg_id,offset_start,offset_end} The vehicle-mounted device then uploads the corresponding segment (either a cut file or a segmented byte stream). V. Battery Temperature Grading Alarm and Interlock Linkage 5.1 Data Acquisition and Status Quantities Battery monitoring module periodic output: Temperature T (multiple points are possible: T1..Tn, take the maximum value Tmax) Voltage V, Current I SOC, SOH (optional) Vehicle central control calculation: Temperature rise rate dT / dt (optional).

[0034] 5.2 Hierarchical Alarm Strategy (thresholds can be configured by the platform) Define thresholds: T1 < T2 < T3, and optional rate thresholds R1, R2: Level 1 warning: Tmax >= T1 or dT / dt >= R1 Actions: In-vehicle prompt (buzzer / light / APP push) + report alarm_level = 1 Level 2 alarm: Tmax >= T2 or Level 1 duration >= t_hold2 Actions: Strong reminder (owner / monitoring end) + enter key monitoring (sampling frequency increase, longer trajectory / video locking) Level 3 danger: Tmax >= T3 or combined conditions such as (Tmax >= T2 and |I| > I_th) Actions: Generate a disposal record and enter the linkage interlock judgment 5.3 Controller Linkage Interlock Conditions When Level 3 danger is met, the vehicle central control does not immediately cut off power, but judges that at least two of the interlock conditions are met: policy_enable = 1: Cloud / monitoring strategy allows protection actions spd <v_safe：车辆速度低于安全阈值（例如5km h）user_confirm=1: Execute after the vehicle owner or in-vehicle button confirms that the interlock is satisfied. Power limiting: Torque / speed limiting parameters are written to the controller via CAN. Or power failure: drive the relay to disconnect the power output; And write the actions and status to the audit log: act_log={vehicle_id,ts,alarm_level,Tmax,V,I,spd,interlock_flags,action_type,action_result} VI. Cloud Management Platform and Regulatory Output 6.1 Module Division and Database Tables of the Cloud Platform A cloud platform includes at least: Device management: device_registry, auth, key_management, OTA Tracking services: track_ingest, track_store, replay, geofence_engine Evidence services: event_store, evidence_index_store, video_fetch_scheduler Battery safety: battery_alarm_store, soh_trend, risk_rank Push notifications: owner_notify, regulator_notify Local interaction: city_content approval, geofence access, logs The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A multi-functional management and monitoring system for two-wheeled electric vehicles, characterized in that, This includes in-vehicle intelligent device terminals, cloud management platforms, and regulatory platform interface modules; The vehicle-mounted intelligent device is installed on the two-wheeled electric vehicle and includes a vehicle central control unit, a Beidou positioning module, a camera module, a battery monitoring module, a vehicle controller linkage module, a communication module, and a local storage module. The vehicle central control unit is communicatively connected to the Beidou positioning module, camera module, battery monitoring module, vehicle controller linkage module, communication module, and local storage module, for the following purposes: The system collects location information output by the BeiDou positioning module and generates a trajectory data packet containing a timestamp to record the vehicle's driving trajectory and route. The camera module is controlled to record continuously, and when a preset event is triggered, an index package of illegal / risk evidence associated with the vehicle's identity, time, location, and operating status is generated. The battery temperature data output by the battery monitoring module is collected and a graded alarm strategy is executed. When the safety interlock conditions are met, the power limiting and power failure protection actions are triggered through the vehicle controller linkage module. The communication module uploads the trajectory data packet, evidence index packet, and battery safety data to the cloud management platform, and receives configuration strategies and instructions from the interface modules of the cloud management platform and the monitoring platform. The cloud management platform is used to store, statistically analyze, send alarms and manage events for data uploaded from in-vehicle intelligent devices. It also outputs vehicle statistics, battery life and safety information, traffic violation information and reminders to the local regulatory platform through the regulatory platform interface module, and provides local interactive information services.

2. The multi-functional management and monitoring system for two-wheeled electric vehicles according to claim 1, characterized in that, The vehicle central control system adopts an adaptive sampling and network disconnection retransmission mechanism for trajectory data packets. The adaptive sampling includes at least: sampling in the driving state according to the first sampling period, sampling at a reduced frequency according to the second sampling period when the speed is low or the stationary state, and sampling at a higher frequency according to the third sampling period when a preset event is triggered. When the network is down, the trajectory data packets are cached in the local storage module according to their sequence number. After the network is restored, they are retransmitted in sequence and carry verification information for cloud deduplication and integrity verification.

3. The multi-functional management and monitoring system for two-wheeled electric vehicles according to claim 2, characterized in that, The camera module's loop recording adopts a segmented storage mechanism. The vehicle control center divides the video into multiple video segments according to a preset duration and stores them in a loop. When the preset event triggering conditions are met, the vehicle control center locks the video segments or fragments corresponding to the preset duration before and after the event to prevent them from being overwritten.

4. The multi-functional management and monitoring system for two-wheeled electric vehicles according to claim 3, characterized in that, The evidence index package includes at least: a unique vehicle identifier, event type, event start and end time, event location, vehicle speed and heading, corresponding video segment identifier and segment offset information, a hash value for integrity verification, and signature or timestamp verification information for tamper-proof verification.

5. The multi-functional management and monitoring system for two-wheeled electric vehicles according to claim 4, characterized in that, The in-vehicle intelligent device adopts an evidence upload strategy of "upload index first, and obtain video on demand": Vehicle Hub Central Control prioritizes uploading the evidence index package to the cloud management platform; When the cloud management platform generates an evidence collection request based on regulatory spot checks, event review, or authorized evidence collection needs, it requests the corresponding video segments or fragments from VehicleHub Control via downlink commands. VehicleHub Control then uploads the requested video segments or fragments accordingly.

6. The multi-functional management and monitoring system for two-wheeled electric vehicles according to claim 5, characterized in that, The tiered alarm strategy includes at least a first-level warning, a second-level alarm, and a third-level danger threshold control: when the battery temperature reaches the first threshold, a first-level warning is triggered and reported; when the battery temperature reaches the second threshold or continues to be abnormal for a preset duration, a second-level alarm is triggered and a reminder is pushed to the vehicle owner and the monitoring terminal. When the battery temperature reaches the third threshold or meets the combined conditions of abnormal temperature and current / voltage, a level 3 hazard is triggered and a handling record is generated.

7. The multi-functional management and monitoring system for two-wheeled electric vehicles according to claim 6, characterized in that, Before the vehicle controller linkage module performs power limiting and power failure protection actions, it sets safety interlock conditions. The safety interlock conditions include at least any two of the following: cloud policy allows the execution of protection actions, vehicle speed is lower than a preset safety threshold, vehicle physical button confirmation, and vehicle owner confirmation. When the interlock conditions are met, the vehicle control center sends control commands to the vehicle controller linkage module and records the control commands, the interlock condition status, and the action execution results as auditable logs and uploads them to the cloud management platform.

8. The multi-functional management and monitoring system for two-wheeled electric vehicles according to claim 7, characterized in that, The data output by the regulatory platform interface module includes at least the following: Vehicle statistics include vehicle registration information, online rate, active mileage, and regional distribution; Battery life and safety information, including battery temperature alarm records, handling results, and battery health status trend information; Traffic violation information and violation reminders include the type of incident, time and location, evidence index identifier, and processing status; Local interactive information is limited to specific areas based on geofencing or administrative regions, and publication and reach logs are recorded.

Images