Data transmission strategy adjustment method and system based on start-stop state of electric two-wheeled vehicle

Abstract

The invention discloses a data transmission strategy adjustment method and system based on the start-stop state of an electric two-wheeled vehicle, and relates to the technical field of electric two-wheeled vehicle data acquisition, and the method comprises the steps: detecting the current vehicle state, and enabling the long connection communication between the electric two-wheeled vehicle and a cloud platform to carry out the real-time data transmission under the vehicle driving state; and if the vehicle is in the shutdown state, activating a vehicle low-power-consumption monitoring mode, and selecting a corresponding connection communication strategy for data transmission between the electric two-wheeled vehicle and the cloud platform according to the classification condition of the to-be-transmitted electric vehicle message. According to the method, a message type-communication connection type dynamic mapping rule is established, so that the energy efficiency of the whole vehicle is greatly optimized, the loss of a vehicle-mounted battery is reduced, the data transmission reliability of the electric two-wheeled vehicle is remarkably improved, the transmission cost is reduced, the scene adaptation capability is enhanced, and reliable data transmission can be completed in a driving state or a shutdown state.

Description

Technical Field

[0001] This invention relates to the field of data acquisition technology for electric two-wheeled vehicles, and in particular to a method and system for adjusting data transmission strategies based on the start-stop status of electric two-wheeled vehicles. Background Technology

[0002] With the technological development of electric two-wheelers, dynamic management and safety monitoring of vehicles have become core requirements. To achieve real-time perception of key information such as vehicle location, battery status, and vehicle posture, relevant technical solutions have been widely applied. The core of these solutions is to complete the collection and reporting of vehicle operation data through communication between the on-board terminal and the base station, providing data support for vehicle safety supervision and fault early warning.

[0003] However, current mainstream vehicle condition monitoring technologies still have many technical shortcomings that urgently need to be addressed, as follows: 1. There is a significant lack of timeliness in the data. Traditional monitoring solutions can only provide a single summary report of the vehicle's status before shutdown after the vehicle is powered off, failing to effectively capture and provide real-time feedback on abnormal events during the shutdown period. High-risk anomalies during shutdown, such as sudden spikes or drops in battery temperature or unauthorized vehicle movement, are often difficult for regulators to detect in a timely manner due to the lack of continuous monitoring and reporting mechanisms, easily leading to safety hazards such as battery thermal runaway and vehicle theft. Furthermore, vehicles cannot maintain network connectivity after shutdown and cannot maintain long-term communication with base stations, relying on user-initiated connection activation.

[0004] 2. There is a serious waste of connection resources and power. To achieve continuous online vehicle monitoring, some solutions employ a persistent connection to maintain communication between the vehicle terminal and the base station. However, in this mode, the device continuously consumes power to communicate with the base station. Actual testing shows that this process causes an additional 3% to 8% battery power consumption. In scenarios where the vehicle is parked for extended periods, this power loss can lead to excessive battery depletion, shortening battery life and potentially preventing the vehicle from starting.

[0005] 3. Insufficient scene adaptability, and delayed response to high-priority events. Existing technologies use the same transmission channel and priority strategy for different types of transmission messages. In this indiscriminate transmission mode, high-priority dynamic alarm events are easily overwhelmed by a large amount of static data, which consumes transmission resources. Actual tests show that the reporting delay of such high-priority events can generally reach 120 seconds, which seriously affects the response efficiency of emergency events and weakens the security protection capability of the monitoring system.

[0006] The aforementioned shortcomings make it difficult for existing vehicle condition monitoring technologies to simultaneously address the requirements of monitoring integrity, low power consumption, and high-priority event response speed. They cannot meet the practical application demands for full-cycle, high-efficiency, and accurate monitoring of vehicles. Therefore, there is an urgent need for an adaptable solution that can address the issue of high-efficiency data reporting in the off state of electric two-wheeled vehicles. Summary of the Invention

[0007] As mentioned above, the shutdown scenario of two-wheeled vehicles has three main characteristics: "low frequency, single interaction, and no persistent connection." These characteristics align perfectly with the technical features of short-connection communication (single interaction, low resource consumption) and fundamentally conflict with the continuous resource consumption characteristics of long-connection communication. To address these problems and technical needs, the inventors have proposed a data transmission strategy adjustment method and system based on the start-stop state of electric two-wheeled vehicles, establishing a dynamic mapping rule between message type and communication connection type. The technical solution of this invention is as follows: In a first aspect, this application provides a method for adjusting a data transmission strategy based on the start-stop state of an electric two-wheeled vehicle, the method comprising the following steps: The current vehicle status is detected. If the vehicle is in motion, the electric two-wheeler and the cloud platform enable long-term communication for real-time data transmission. If the vehicle is powered off, the low-power monitoring mode is activated, and the electric two-wheeler and the cloud platform select the appropriate connection and communication strategy for data transmission based on the classification of the electric vehicle messages to be transmitted.

[0008] The further technical solution involves, based on the classification of the electric vehicle messages to be transmitted, the electric two-wheeler and the cloud platform selecting appropriate connection and communication strategies for data transmission, including: Parse the electric vehicle message to be transmitted; When the electric vehicle message to be transmitted is a static message, the electric two-wheeler and the cloud platform use short connection communication to transmit data in a single transaction. When the electric vehicle message to be transmitted is a periodic message, the electric two-wheeler and the cloud platform use hybrid connection communication to transmit data. When the electric vehicle message to be transmitted is an event message, the electric two-wheeler and the cloud platform enable long-connection communication for real-time data transmission. Hybrid connection communication refers to the dynamic switching between long and short connection communication.

[0009] The further technical solution is that the periodic message is defined as status information sent at a given time interval, including battery level and vehicle location; When the electric vehicle message to be transmitted is a periodic message, the electric two-wheeler and the cloud platform use hybrid connection communication for data transmission, including: If the given time interval for querying the periodic message exceeds the set periodic threshold, the electric two-wheeler and the cloud platform will use short connection communication to transmit data once. Otherwise, the electric two-wheeler and the cloud platform will use a long-term connection for real-time data transmission.

[0010] The further technical solution is that static messages are defined as inherent vehicle information, including vehicle ID, model, and firmware version; An event message is defined as real-time information triggered when a specific event occurs, including vehicle collision alarms, vehicle tipping alarms, and battery temperature change alarms.

[0011] A further technical solution is that the method also includes: When electric two-wheeled vehicles and cloud platforms use long-connection communication for real-time data transmission, a heartbeat mechanism is used to maintain the connection. If a vehicle has no data transmission for a certain period of time, the long-connection communication will be temporarily closed.

[0012] A further technical solution is that the method also includes: When an electric two-wheeled vehicle transmits static messages to the cloud platform, the lightweight and efficient transmission protocol TinyFLET is used to compress the static messages.

[0013] A further technical solution is that the method also includes: When the vehicle is in motion, the main battery of the electric vehicle charges the supercapacitor emergency module. When the vehicle is powered off, the electric vehicle owner's battery is disconnected and automatically switched to power supply by the supercapacitor emergency module to ensure that the event message is reported completely.

[0014] The further technical solution is that, in low-power monitoring mode, the main controller of the electric two-wheeler is woken up by the vibration sensor, tilt sensor and BMS temperature gradient detection module installed on the vehicle, so as to perform the steps of selecting the appropriate connection communication strategy between the electric two-wheeler and the cloud platform for data transmission based on the classification of the electric vehicle message to be transmitted.

[0015] A further technical solution is that the method also includes: On the cloud platform, the size of the periodic threshold is dynamically modified and sent to the electric two-wheeler.

[0016] Secondly, this application also provides a data transmission strategy adjustment system based on the start-stop state of an electric two-wheeled vehicle, including an electric two-wheeled vehicle and a cloud platform, both of which perform the data transmission strategy adjustment method as described in the first aspect.

[0017] This method achieves significant breakthroughs in energy efficiency, data transmission reliability, and scenario adaptability of vehicle-mounted monitoring terminals through collaborative optimization of software and hardware. The specific beneficial technical effects are as follows: 1. Significantly optimized energy efficiency, reducing onboard battery wear. The communication decision-making method that dynamically enables short or long connections based on message type (static / periodic / event-based) effectively solves the problem of excessive battery consumption in traditional long-connection solutions, significantly extending the range of two-wheeled vehicles and battery life during vehicle inactivity. Short-connection sessions reduce the time and energy consumption of handshaking between the vehicle and the cloud platform, further reducing power consumption during communication.

[0018] 2. Data transmission reliability is significantly improved, and transmission costs are reduced. The success rate of transmitting event-triggered critical messages using long-lived connection communication is significantly improved, ensuring that critical information such as vehicle anomalies can accurately reach the cloud platform. Upon receiving the information, the platform can quickly notify maintenance personnel for timely handling. The hybrid connection strategy for periodic messages allows for the selection of long and short connection communication as needed, avoiding the waste of resources from repeated connections when the transmission interval is long.

[0019] 3. Enhanced ability to adapt to different scenarios It supports key sensor-triggered wake-up function (such as displacement vibration). When a sudden temperature change of key components such as batteries is detected, the message is automatically upgraded to a high-priority event message to take priority in preempting transmission resources and achieve accurate and intelligent vehicle monitoring. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of a data transmission strategy adjustment system based on the start-stop status of an electric two-wheeled vehicle in one embodiment; Figure 2 This is a flowchart illustrating a data transmission strategy adjustment method based on the start-stop state of an electric two-wheeled vehicle in one embodiment. Figure 3 This is a flowchart illustrating the dynamic mapping steps of message type-communication connection type in one embodiment; Figure 4 This is a complete flowchart of the data transmission strategy adjustment method in another embodiment; Figure 5 This is a structural block diagram of a data transmission strategy adjustment device in one embodiment; Figure 6 This is a structural block diagram of the second communication connection selection module in one embodiment; Figure 7 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0022] The data transmission strategy adjustment method based on the start-stop state of an electric two-wheeled vehicle provided in this application embodiment can be applied to, for example... Figure 1 The data transmission strategy adjustment system shown includes an electric two-wheeler and a cloud platform. The onboard terminal 102 of the electric two-wheeler communicates with the server 104 of the cloud platform via a network. The data storage system can store data that the server 104 needs to process, such as message information reported by the electric two-wheeler 102 and the two-wheeler's status information. The data storage system can be integrated onto the server 104 or placed on other network servers. The server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0023] In one embodiment, such as Figure 2 As shown, a method for adjusting the data transmission strategy based on the start-stop state of an electric two-wheeled vehicle is provided, which can be applied to... Figure 1 The system shown is used as an example for illustration, including the following steps: Step 202: Detect the current vehicle status. Specifically, the on-board terminal of the electric two-wheeler can collect information from the vehicle's sensor array and battery BMS, and combine these two types of information to determine whether the vehicle is in a powered-off state or in a driving state.

[0024] The sensor array typically includes vibration sensors (for monitoring vehicle collisions), temperature sensors (for monitoring charger temperature), an anti-theft alarm, an inertial measurement unit (IMU) or tilt sensor (for monitoring vehicle roll), and radar (for detecting approaching personnel), thus determining whether the vehicle is stationary. BMS information typically includes voltage (individual cell voltage, total voltage, minimum / maximum voltage, etc.), charging or discharging current, temperature (individual cell temperature, average temperature, or maximum / minimum temperature), and state of charge (SOC). In this embodiment, when the on-board terminal detects that the battery voltage is below the safety threshold of 48V, and the vehicle is completely stationary and maintains a stable posture for a certain period (e.g., 60 seconds), the vehicle is considered to be in a powered-off state; otherwise, the vehicle is in motion.

[0025] Step 204: If the vehicle is in motion, the electric two-wheeler and the cloud platform enable long-connection communication for real-time data transmission. Specifically, a customized lightweight long-connection protocol is used to achieve rapid connection establishment between the vehicle terminal and the cloud platform: First, the vehicle terminal initiates a connection request via the network. After receiving the request, the cloud platform connection node completes device authentication within a short time. After successful authentication, a unique long-connection identifier (ConnID) is assigned, and a connection establishment success response is returned to the vehicle terminal. Thereafter, electric vehicle data can be reported to the cloud platform in real time.

[0026] Step 206: If the vehicle is powered off, activate the vehicle's low-power monitoring mode and, based on the classification of the electric vehicle messages to be transmitted, select the appropriate connection and communication strategy between the electric two-wheeler and the cloud platform for data transmission. Specifically, after the vehicle is powered off, the on-board terminal automatically switches to low-power monitoring mode and achieves accurate transmission of different types of messages through on-demand wake-up and classification communication strategies.

[0027] Among them, electric vehicle messages in the IoT device interconnection scenario of two-wheeled vehicles can be divided into static messages, periodic messages, and event messages; connection communication strategies are generally divided into long connection communication and short connection communication.

[0028] The aforementioned data transmission strategy adjustment method overcomes the limitations of traditional single connection strategies by employing a dynamic adaptation mechanism that combines real-time transmission with long-term connections in the driving state and low-power classified communication in the power-off state. This achieves multi-dimensional optimization in energy efficiency control, transmission quality, scenario coverage, and data security. 1) Precise energy efficiency control significantly extends the vehicle's battery life. While the vehicle is in motion, real-time data transmission is achieved via a long connection, eliminating the need for frequent connection establishment between the electric two-wheeler and the cloud platform. When the vehicle is powered off, a low-power monitoring mode is activated, resulting in significantly reduced power consumption compared to traditional standby with a long connection after power-off. This solves the problem of power depletion during static operation caused by traditional solutions and prevents the vehicle from failing to start due to excessive battery wear. 2) Graded transmission quality assurance balances real-time performance and reliability. Long-connection communication while the vehicle is in motion improves real-time performance, meeting dynamic monitoring requirements. When the vehicle is powered off, different transmission strategies are selected based on message type, ensuring no delay or loss of critical data and covering the entire application lifecycle, thus resolving the disconnection problem caused by traditional solutions. This method not only addresses the pain points of insufficient real-time performance while in motion and high energy consumption and disconnection during power-off operations caused by traditional solutions, but also provides technical support for the intelligent management of electric two-wheelers.

[0029] Step 206 mentions a low-power monitoring mode, which is triggered when the vehicle is powered off. In this mode, only the IoT communication module, alarm, key sensor groups (such as vibration and tilt sensors), and some BMS modules (such as the temperature gradient detection module) are operational. In one possible implementation, in low-power monitoring mode, the main controller of the electric two-wheeler (located in the vehicle terminal) can be woken up by the vibration sensor, tilt sensor, and BMS temperature gradient detection module installed on the vehicle. This allows the electric two-wheeler to perform the step of selecting the appropriate connection and communication strategy between the electric two-wheeler and the cloud platform for data transmission based on the classification of the electric vehicle message to be transmitted.

[0030] In this embodiment, the wake-up function triggered by key sensors (such as displacement vibration) is supported. The wake-up sensitivity can be flexibly adjusted according to different vehicle models and usage scenarios. This avoids invalid wake-up caused by slight vibrations and can accurately detect abnormal actions such as vehicle theft and illegal displacement, thereby achieving on-demand wake-up and energy-saving monitoring.

[0031] To achieve the core requirement of step 206, a dynamic mapping rule between message type and communication connection type needs to be established. This rule is generated based on the adaptation analysis of static messages, periodic messages, event messages, and long / short connections. The characteristics of these two connection types are shown in Table 1. Table 1 Characteristics of Long Connections / Short Connections

[0032] In one embodiment, such as Figure 3 As shown, step 206 includes: Step 302: Parse the electric vehicle message to be transmitted. The definitions of each message and examples for two-wheeled vehicle scenarios are shown in Table 2. Table 2 Message Type Definitions (Combined with Two-Wheeled Vehicle IoT Scenarios)

[0033] The parsing process can be based on a closed-loop logic of flag bit pre-definition → message preprocessing → flag bit extraction → type output, ensuring parsing accuracy and efficiency. In one possible implementation, after the vehicle terminal transmits the original message through the electric vehicle bus (such as CAN bus) or communication network module (such as IoT communication module), it verifies the message integrity, such as checking whether the message header, trailer, and check bits are complete. Then, based on the preset protocol format, it locates and extracts the message type flag bit field located in the high bits (set differently for the three types of messages). Next, for the initially determined message type, it further parses the auxiliary flag bits located in the low bits to complete the message type confirmation and supplement attribute information to avoid misjudgment. Finally, after completing the type determination, it outputs the clear message type and associated attributes, and triggers the corresponding subsequent processing logic.

[0034] Optionally, if the vehicle terminal does not detect the message data that needs to be transmitted within a certain period of time, it will enter a deep sleep state and wait for the next wake-up.

[0035] Step 304: When the electric vehicle message to be transmitted is a static message, the electric two-wheeler and the cloud platform enable short connection communication for single data transmission.

[0036] Combining the information in Tables 1 and 2, it can be concluded that static messages are suitable for short-connection communication because: static messages are sent very infrequently (only during vehicle initialization, restart, or firmware updates) and contain small amounts of data (only fixed information). The "use and close" characteristic of short connections avoids long-term occupation of server resources, and the connection overhead (three-way handshake + four-way handshake) of each transmission has minimal impact on overall performance. In this embodiment, the application scenario is: when an electric two-wheeled vehicle first connects to the cloud platform, a static message containing the vehicle ID and model is sent; subsequent transmissions do not require frequent sending, making short connections more resource-efficient.

[0037] Optionally, short-connection communication with static messages also needs to ensure that the message is sent successfully (e.g., via ACK confirmation) to avoid data loss due to connection closure.

[0038] Step 306: When the electric vehicle message to be transmitted is a periodic message, the electric two-wheeler and the cloud platform enable hybrid connection communication for data transmission.

[0039] Hybrid connection communication refers to the dynamic switching between long and short connection communication. The standard for dynamic switching can be based on the specific size of a given time interval, i.e., whether the periodic message needs to be transmitted at high frequency or low frequency. Further analysis results will be given in the following content.

[0040] Step 308: When the electric vehicle message to be transmitted is an event message, the electric two-wheeler and the cloud platform enable long-connection communication for real-time data transmission.

[0041] Combining the information in Tables 1 and 2, it can be concluded that long-connection communication is suitable for event messages because: event trigger messages have extremely high real-time requirements (e.g., collision alarms need to immediately notify the platform, and user unlocking commands need to be executed immediately). The bidirectional real-time communication characteristics of long connections can ensure low-latency message transmission (the server can actively send commands to the vehicle terminal, and the vehicle terminal can also immediately report the event), avoiding delayed event reporting caused by the connection establishment time of short connections (e.g., waiting for connection establishment after a collision before reporting may miss the optimal processing time). In this embodiment, the application scenario is as follows: when an electric two-wheeler is collided with, the vehicle terminal immediately reports a "collision event" via a long connection, and the cloud platform can quickly notify maintenance personnel upon receiving the report; when a user unlocks the vehicle with their mobile phone, the cloud platform immediately sends an "unlocking command" via a long connection, and the vehicle terminal unlocks immediately upon receiving the command, thereby improving the user experience.

[0042] In this embodiment, using preset flag bits for each message as the core anchor point, a closed-loop four-step process is employed to achieve rapid and accurate parsing of electric vehicle message types. Based on this, differentiated connection communication strategies are matched for different message types: 1) Significantly Improved Energy Efficiency: Static and periodic messages utilize short and hybrid connections to avoid the continuous resource consumption of long connections, significantly reducing standby power consumption in electric two-wheelers, minimizing battery wear, and meeting the low-power requirements of onboard equipment; 2) Enhanced Transmission Reliability: Dynamic event messages communicate via long connections, ensuring real-time and complete transmission of high-risk event data, reducing the risk of message loss, and improving the timeliness of safety monitoring; 3) Optimized Resource Utilization: Differentiated connection strategies enable "on-demand connection establishment," avoiding resource waste caused by a single connection method, reducing both the power and computing resource consumption of the electric two-wheeler and the connection management pressure on the cloud platform. The overall solution, through the coordinated optimization of parsing logic and communication strategies, perfectly adapts to the core requirements of low power consumption, high real-time performance, and high reliability of electric two-wheeler onboard monitoring systems.

[0043] Regarding step 306, the analysis above has shown that periodic messages with different transmission frequencies are adapted to different connection strategies. In one possible implementation, the specific implementation process of step 306 includes: querying a given time interval of the periodic message; if the interval exceeds a set period threshold (e.g., the interval duration is greater than 5 minutes), the message is considered to be a low-frequency periodic message, and the electric two-wheeler and the cloud platform use short connection communication for single data transmission; if the interval does not exceed the set period threshold (e.g., the interval duration is less than or equal to 5 minutes), the message is considered to be a high-frequency periodic message, and the electric two-wheeler and the cloud platform use long connection communication for real-time data transmission.

[0044] Combining the information in Tables 1 and 2, it can be concluded that high-frequency periodic messages are suitable for long-connection communication because periodic messages are sent at medium to high frequencies (e.g., once every minute / hour) and require regular transmission. The persistent connection characteristic of long connections reduces the connection overhead for each transmission (no need to repeatedly establish TCP connections), improving transmission efficiency. Especially for the periodic status reporting of two-wheeled vehicles (e.g., battery level, vehicle location), long connections ensure timely data transmission and do not increase device power consumption due to frequent connections (two-wheeled vehicle devices usually rely on batteries, and reducing the number of connections can extend battery life). Low-frequency periodic messages are suitable for short-connection communication, which uploads infrequently used data to the cloud platform through a single connection, and immediately releases connection resources after transmission, avoiding power consumption caused by continuous connection occupation. In this embodiment, the application scenario is: after the electric vehicle is turned off, it reports location and battery information every half hour. In this case, short-connection communication is preferred because short connections only wake up modules (e.g., GPS and key sensors) when reporting data, and immediately go into sleep mode after transmission, maximizing battery life.

[0045] Optionally, the size of the periodic threshold can be dynamically modified on the cloud platform according to the actual application situation and then distributed to the electric two-wheeler.

[0046] In this embodiment, under the IoT scenario of electric two-wheeled vehicles, static messages use short-connection communication, periodic messages use either long or short-connection communication depending on the period length, and real-time event messages, due to their high real-time requirements, must use long-connection communication, thereby achieving a balance between resource optimization and performance assurance. The final established dynamic mapping rules between message type and communication connection type are shown in Table 3: Table 3 Dynamic Mapping Rules for Message Types and Communication Connection Types

[0047] Based on steps 202-206 of the data transmission strategy adjustment method described above, this embodiment further optimizes long-connection communication. In one possible implementation, when the electric two-wheeled vehicle and the cloud platform enable long-connection communication for real-time data transmission (involving the high-frequency periodic messages in steps 204 and 306 and step 308), the two can maintain the connection using a heartbeat mechanism. That is, the vehicle terminal periodically sends small-volume heartbeat messages to confirm the connection status with the cloud platform and prevent the platform server from actively closing the connection. Simultaneously, when the vehicle has no data transmission for a certain period (e.g., when parked in a parking lot at night), long-connection communication can be temporarily disabled to balance real-time performance and resource consumption.

[0048] Based on steps 202-206 of the data transmission strategy adjustment method described above, this embodiment further optimizes short-connection communication. Specifically, when the electric two-wheeled vehicle transmits static messages to the cloud platform, differential compression technology (transmitting only changes) is used to compress the static messages to adapt to low-power vehicle scenarios. In one possible implementation, differential compression technology can be implemented through the incremental transmission strategy of the lightweight and efficient transmission protocol TinyFLET. The specific compression process generally includes: a preprocessing stage (classifying data in the static message), an encoding stage (replacing field IDs, compressing values, and adding verification), and message transmission.

[0049] Optionally, a customized packet splitting strategy can be used for transmission. The core requirements of this strategy are a single packet size ≤ 128 bytes and a packet splitting interval ≥ 15 seconds, which can reduce transmission bandwidth usage and battery power consumption. After static messages are differentially compressed using TinyFLET, only the fields that have changed with historical snapshots (such as coordinate increments and status change values) are transmitted, significantly reducing the data volume. Setting the maximum single packet size to 128 bytes not only reserves sufficient space for the compressed message but also handles situations where multiple fields change simultaneously in extreme scenarios, avoiding frequent packet splitting due to insufficient single packet capacity, thus balancing compression efficiency and transmission stability. Since the core content of static messages changes very infrequently, and some fields even remain unchanged for a long time, static messages have a higher tolerance for transmission latency compared to the real-time requirements of dynamic event messages. Setting a packet splitting interval of more than 15 seconds can avoid high-frequency transmission of slowly changing data, reducing unnecessary communication interactions, lowering power consumption from the transmission frequency, and alleviating the pressure on vehicle battery wear.

[0050] like Figure 1 The data transmission strategy adjustment system shown adopts a hybrid power supply system, including the main and auxiliary batteries of the electric vehicle and a supercapacitor emergency module. This embodiment further includes step 208: when the vehicle is in motion, the main battery of the electric vehicle charges the supercapacitor emergency module. When the vehicle is powered off, the main battery of the electric vehicle is de-energized and automatically switches to power supply from the supercapacitor emergency module, ensuring complete reporting of event messages. The supercapacitor emergency module includes a supercapacitor energy storage unit, a bidirectional DC / DC energy management module, and an intelligent power monitoring and switching module. The bidirectional DC / DC energy management module is connected to the high-voltage battery bus and the supercapacitor respectively, realizing bidirectional energy flow control. When the vehicle is running normally, it converts battery energy into a voltage suitable for charging the supercapacitor; when the main battery is disconnected, it operates in reverse, converting the supercapacitor energy into the voltage required by the system.

[0051] Optionally, during supercapacitor power supply, the IoT communication module receives the highest priority power supply to ensure the reporting of critical data.

[0052] In this embodiment, when the electric vehicle's main battery is disconnected, the supercapacitor emergency module achieves continuous power supply for more than 120 seconds through a rapid switching and stable voltage boosting mechanism, ensuring complete reporting of emergency events. This solution solves the problem of data timeliness in traditional vehicle monitoring systems, providing a solid guarantee for the safe operation of electric vehicles.

[0053] In practical applications, the hardware configuration of the data transmission strategy adjustment system provided in this embodiment includes: a main controller using the ESP32-C6 model (integrated WiFi 6 / BLE 5.3); a 6-axis inertial measurement unit (IMU) using the BMI270 model; and an IoT communication module using the Quectel BC66 (NB-IoT, PSM mode power consumption 1.7μA). For the key steps of the system's software implementation, please refer to [link / reference needed]. Figure 4 As shown, it specifically includes: Step 402: Detect the current vehicle status. In practice, when the vehicle terminal detects that the battery voltage is lower than the safety threshold of 48V, the vehicle is completely stationary (sensed by the vehicle sensors) and maintains a stable posture for a certain period of time (e.g., 60 seconds), the vehicle is considered to be in a powered-off state; otherwise, the vehicle is in a driving state.

[0054] Step 404: If the vehicle is in motion, the electric two-wheeler and the cloud platform enable long-term communication for real-time data transmission.

[0055] Step 406: If the vehicle is powered off, activate the vehicle low-power monitoring mode, and based on the classification of the electric vehicle messages to be transmitted, the electric two-wheeler and the cloud platform select the appropriate connection and communication strategy for data transmission. This step specifically includes: Parsing the electric vehicle message to be transmitted: When the message is a static message, the electric two-wheeler and the cloud platform use short connection communication for single data transmission; when the message is a periodic message, the electric two-wheeler and the cloud platform use hybrid connection communication for data transmission, where hybrid connection communication refers to the dynamic switching between long and short connection communication; when the message is an event message, the electric two-wheeler and the cloud platform use long connection communication for real-time data transmission.

[0056] Preferably, when the electric two-wheeler transmits static messages to the cloud platform, the lightweight and efficient transmission protocol TinyFLET is used to compress the static messages, and the packet splitting strategy is set as follows: single packet size ≤ 128 bytes, packet interval ≥ 15 seconds, to adapt to the low-power vehicle scenario; and the short-connection communication of static messages must also ensure successful message transmission (e.g., through ACK confirmation) to avoid data loss due to connection closure. When the electric two-wheeler and the cloud platform use long-connection communication for real-time data transmission, the two can use a heartbeat mechanism to maintain the connection; at the same time, when the vehicle has no data transmission for a certain period of time (e.g., parked in a parking lot at night), the long-connection communication can be temporarily closed to balance real-time performance and resource consumption.

[0057] Step 408: When the vehicle is in motion, the electric vehicle's main battery charges the supercapacitor emergency module. When the vehicle is powered off, the electric vehicle's main battery is de-energized, and the system automatically switches to power supply from the supercapacitor emergency module to ensure complete event reporting.

[0058] In practice, the state-aware programming code in step 402 is as follows: Pythondef detect_shutdown(): if voltage<48V and speed == 0 and gyro_stable_time>60s: enter_low_power_mode() / / Activate low power monitoring The programming code for the message classification logic in step 406 is as follows: Cenum PacketType classify_packet() {if (packet.source == ID) return STATIC; / / Static packet if (packet.event_id&0x80) return EVENT; / / Bitwise operation to check the highest bit of the event ID; if this bit is set to 1, it is determined to be an emergency event packet if (packet.interval>300) return PERIODIC_LONG; / / Period > 5min is determined to be a low-frequency periodic packet; the period threshold can be dynamically adjusted by issuing commands through the cloud platform} The programming code for selecting the message type and corresponding connection strategy in step 406 is as follows: Java public void executeTransmission(Packet packet) { switch(packet.type) { case STATIC: ShortLink.send(packet); / / Single short connection powerOffNetworkModule(); / / Turn off the network module after reporting to save power break; case EVENT: LongLink.keepAlive(); / / Maintain long connection LongLink.push(packet); / / Ensure critical data can be reliably transmitted to the cloud platform in real time}} Finally, it should be noted that the cloud platform uses big data analytics to summarize and aggregate the reported data, and then extracts useful information from the data and provides datasets for AI training. This application will not go into detail about this.

[0059] Comparative experiments have verified that using this method reduces the standby power consumption of the vehicle to 0.12W when it is powered off, a reduction of over 90% compared to the traditional solution (≥1.5W). Battery degradation after 30 days of inactivity can be controlled to within 2%, effectively solving the problem of excessive battery degradation in traditional long-connection solutions and significantly extending the range of two-wheeled vehicles and battery life during inactivity. The short-connection session establishment time is compressed to 0.8s, a 46.7% efficiency improvement compared to the standard TCP handshake process (≥1.5s), reducing the time and energy consumption of handshakes between the vehicle and the cloud platform, further reducing power consumption during communication.

[0060] The transmission success rate of event-triggered critical messages has been improved to 99.2%, which is 14.2 percentage points higher than the traditional solution (85%). This ensures that critical information such as vehicle abnormal events can accurately reach the cloud platform, and the platform can quickly notify maintenance personnel to handle the situation in a timely manner.

[0061] The differential data compression technology equipped with Tiny FLET significantly reduces the size of vehicle static messages, significantly improving transmission efficiency while ensuring data integrity. The amount of data reported at one time can be reduced by 67%, while reducing the energy consumption of vehicle-side data transmission, thus balancing transmission efficiency and device battery life.

[0062] Based on the temperature change monitoring mechanism built into the BMS, when the temperature change rate of critical components such as batteries is detected to be Δ≥3℃ / min, the message will be automatically upgraded to a high-priority event message, giving priority to the transmission resources, avoiding delays in high-priority alarms, and ensuring that high-risk events such as battery thermal runaway can be identified and handled in a timely manner.

[0063] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0064] Based on the same inventive concept, this application also provides a data transmission strategy adjustment device for implementing the data transmission strategy adjustment method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more data transmission strategy adjustment device embodiments provided below can be found in the limitations of the data transmission strategy adjustment method described above, and will not be repeated here.

[0065] In one embodiment, such as Figure 5 As shown, a data transmission strategy adjustment device based on the start-stop state of an electric two-wheeled vehicle is provided, comprising: a vehicle state perception module, a first communication connection selection module, and a second communication connection selection module, wherein: The vehicle status perception module is used to detect the current vehicle status. Specifically, the on-board terminal of the electric two-wheeler can collect information from the vehicle's sensor array and battery BMS, and combine these two types of information to determine whether the vehicle is in a powered-off state or in a driving state.

[0066] The sensor array typically includes vibration sensors (for monitoring vehicle collisions), temperature sensors (for monitoring charger temperature), an anti-theft alarm, an inertial measurement unit (IMU) or tilt sensor (for monitoring vehicle roll), and radar (for detecting approaching personnel), thus determining whether the vehicle is stationary. BMS information typically includes voltage (individual cell voltage, total voltage, minimum / maximum voltage, etc.), charging or discharging current, temperature (individual cell temperature, average temperature, or maximum / minimum temperature), and state of charge (SOC). In this embodiment, when the on-board terminal detects that the battery voltage is below the safety threshold of 48V, and the vehicle is completely stationary and maintains a stable posture for a certain period (e.g., 60 seconds), the vehicle is considered to be in a powered-off state; otherwise, the vehicle is in motion.

[0067] The first communication connection selection module is used to enable real-time data transmission between the electric two-wheeler and the cloud platform via a long-connection communication while the vehicle is in motion. Specifically, a customized lightweight long-connection protocol is adopted to achieve rapid connection establishment between the vehicle terminal and the cloud platform: First, the vehicle terminal initiates a connection request through the network. After receiving the request, the cloud platform connection node completes device authentication within a short time. After successful authentication, a unique long-connection identifier (ConnID) is assigned, and a connection establishment success response is returned to the vehicle terminal. Thereafter, electric vehicle data can be reported to the cloud platform in real time.

[0068] The second communication connection selection module is used to activate the vehicle's low-power monitoring mode when the vehicle is powered off, and select the appropriate connection communication strategy between the electric two-wheeler and the cloud platform for data transmission based on the classification of the electric vehicle messages to be transmitted. Specifically, after the vehicle is powered off, the on-board terminal automatically switches to low-power monitoring mode, and achieves accurate transmission of different types of messages through on-demand wake-up and classification communication strategies.

[0069] Among them, electric vehicle messages in the IoT device interconnection scenario of two-wheeled vehicles can be divided into static messages, periodic messages, and event messages; connection communication strategies are generally divided into long connection communication and short connection communication.

[0070] The aforementioned data transmission strategy adjustment device overcomes the limitations of traditional single-connection strategies by employing a dynamic adaptation mechanism that combines real-time transmission with long-term connections during operation and low-power classified communication during shutdown. This achieves multi-dimensional optimization in energy efficiency control, transmission quality, scenario coverage, and data security: 1) Precise energy efficiency control significantly extends the vehicle's battery life. 2) Graded transmission quality assurance balances real-time performance and reliability. This device not only addresses the pain points of insufficient real-time performance during operation and high energy consumption and disconnection during shutdown caused by traditional solutions, but also provides technical support for the intelligent management of electric two-wheeled vehicles.

[0071] The second communication connection selection module mentions a low-power monitoring mode, which is triggered when the vehicle is powered off. In this mode, only the IoT communication module, alarm, key sensor groups (such as vibration and tilt sensors), and some BMS modules (such as the temperature gradient detection module) are operational. In one possible implementation, in low-power monitoring mode, the main controller of the electric two-wheeler (located in the vehicle terminal) can be woken up by the vibration sensor, tilt sensor, and BMS temperature gradient detection module installed on the vehicle. This allows the electric two-wheeler to perform the step of selecting the appropriate connection communication strategy between the electric two-wheeler and the cloud platform for data transmission based on the classification of the electric vehicle message to be transmitted.

[0072] In this embodiment, the wake-up function triggered by key sensors (such as displacement vibration) is supported. The wake-up sensitivity can be flexibly adjusted according to different vehicle models and usage scenarios. This avoids invalid wake-up caused by slight vibrations and can accurately detect abnormal actions such as vehicle theft and illegal displacement, thereby achieving on-demand wake-up and energy-saving monitoring.

[0073] To fulfill the core requirements of the second communication connection selection module, a dynamic mapping rule between message type and communication connection type needs to be established. This rule is generated based on the adaptation analysis of static messages, periodic messages, event messages, and long / short connections. The characteristics of these two connection types are shown in Table 1 above, and will not be elaborated here.

[0074] In one embodiment, such as Figure 6As shown, the second communication connection selection module includes: a message parsing unit, a static message connection selection unit, a periodic message connection selection unit, and an event message connection selection unit, wherein: The message parsing unit is used to parse the electric vehicle message to be transmitted. The definitions of each message and examples for two-wheeled vehicle scenarios are shown in Table 2 above, and will not be repeated here.

[0075] The parsing process can be based on a closed-loop logic of flag bit pre-definition → message preprocessing → flag bit extraction → type output, ensuring parsing accuracy and efficiency. In one possible implementation, after the vehicle terminal transmits the original message through the electric vehicle bus (such as CAN bus) or communication network module (such as IoT communication module), it verifies the message integrity, such as checking whether the message header, trailer, and check bits are complete. Then, based on the preset protocol format, it locates and extracts the message type flag bit field located in the high bits (set differently for the three types of messages). Next, for the initially determined message type, it further parses the auxiliary flag bits located in the low bits to complete the message type confirmation and supplement attribute information to avoid misjudgment. Finally, after completing the type determination, it outputs the clear message type and associated attributes, and triggers the corresponding subsequent processing logic.

[0076] Optionally, if the vehicle terminal does not detect the message data that needs to be transmitted within a certain period of time, it will enter a deep sleep state and wait for the next wake-up.

[0077] The static message connection selection unit is used to enable short-connection communication for single data transmission between the electric two-wheeler and the cloud platform when the electric vehicle message to be transmitted is a static message. Analysis of Tables 1 and 2 shows that static messages are suitable for short-connection communication because: static messages are sent very infrequently (only during vehicle initialization, restart, or firmware updates) and have a small data volume (containing only fixed information). The "use and close" characteristic of short connections avoids long-term occupation of server resources, and the connection overhead (three-way handshake + four-way handshake) for each transmission has minimal impact on overall performance. In this embodiment, the application scenario is: when the electric two-wheeler first connects to the cloud platform, it sends a static message containing the vehicle ID and model; subsequent frequent transmissions are unnecessary, and short connections save resources.

[0078] Optionally, short-connection communication with static messages also needs to ensure that the message is sent successfully (e.g., via ACK confirmation) to avoid data loss due to connection closure.

[0079] The periodic message connection selection unit is used to enable hybrid connection communication for data transmission between the electric two-wheeler and the cloud platform when the electric vehicle message to be transmitted is a periodic message. Hybrid connection communication refers to the dynamic switching between long and short connection communication. The standard for dynamic switching can refer to the specific size of a given time interval, i.e., whether the periodic message requires high-frequency or low-frequency transmission. Further analysis will be provided later.

[0080] The event message connection selection unit is used to enable long-connection communication for real-time data transmission between the electric two-wheeler and the cloud platform when the electric vehicle message to be transmitted is an event message. Analysis of Tables 1 and 2 shows that long-connection communication is suitable for event messages because: event-triggered messages have extremely high real-time requirements (e.g., collision alarms need to immediately notify the platform, and user unlocking commands need to be executed immediately). The bidirectional real-time communication characteristics of long connections ensure low-latency message transmission (the server can actively send commands to the vehicle terminal, and the vehicle terminal can also immediately report the event), avoiding delayed event reporting caused by the connection establishment time of short connections (e.g., waiting for connection establishment after a collision before reporting may miss the optimal processing time). In this embodiment, the application scenario is: when the electric two-wheeler is collided with, the vehicle terminal immediately reports a "collision event" via a long connection, and the cloud platform can quickly notify maintenance personnel upon receiving the report; when the user unlocks the vehicle with their mobile phone, the cloud platform immediately sends an "unlocking command" via a long connection, and the vehicle terminal unlocks immediately upon receiving the command, thereby improving the user experience.

[0081] In this embodiment, using the preset flag bits of each message as the core anchor point, a closed-loop four-step process is established to achieve rapid and accurate parsing of electric vehicle message types. Based on this, differentiated connection and communication strategies are matched for different message types: 1) significantly improved energy efficiency; 2) enhanced transmission reliability; 3) optimized resource utilization. The overall solution, through the coordinated optimization of parsing logic and communication strategies, perfectly meets the core requirements of low power consumption, high real-time performance, and high reliability of electric two-wheeled vehicle onboard monitoring systems.

[0082] For the periodic message connection selection unit, it has been previously analyzed that periodic messages with different transmission frequencies are adapted to different connection strategies. In one possible implementation, the specific implementation process of the periodic message connection selection unit includes: querying a given time interval of the periodic message; if the interval exceeds a set period threshold (e.g., the interval duration is greater than 5 minutes), the message is considered to be a low-frequency periodic message, and the electric two-wheeler and the cloud platform use short connection communication for single data transmission; if the interval does not exceed the set period threshold (e.g., the interval duration is less than or equal to 5 minutes), the message is considered to be a high-frequency periodic message, and the electric two-wheeler and the cloud platform use long connection communication for real-time data transmission.

[0083] Combining the information in Tables 1 and 2, it can be concluded that high-frequency periodic messages are suitable for long-connection communication because periodic messages are sent at medium to high frequencies (e.g., once every minute / hour) and require regular transmission. The persistent connection characteristic of long connections reduces the connection overhead for each transmission (no need to repeatedly establish TCP connections), improving transmission efficiency. Especially for the periodic status reporting of two-wheeled vehicles (e.g., battery level, vehicle location), long connections ensure timely data transmission and do not increase device power consumption due to frequent connections (two-wheeled vehicle devices usually rely on batteries, and reducing the number of connections can extend battery life). Low-frequency periodic messages are suitable for short-connection communication, which uploads infrequently used data to the cloud platform through a single connection, and immediately releases connection resources after transmission, avoiding power consumption caused by continuous connection occupation. In this embodiment, the application scenario is: after the electric vehicle is turned off, it reports location and battery information every half hour. In this case, short-connection communication is preferred because short connections only wake up modules (e.g., GPS and key sensors) when reporting data, and immediately go into sleep mode after transmission, maximizing battery life.

[0084] Optionally, the size of the periodic threshold can be dynamically modified on the cloud platform according to the actual application situation and then distributed to the electric two-wheeler.

[0085] In this embodiment, under the IoT scenario of electric two-wheeled vehicles, static messages use short-connection communication, periodic messages use either long or short-connection communication depending on the period length, and real-time event messages, due to their high real-time requirements, must use long-connection communication, thereby achieving a balance between resource optimization and performance assurance. The final dynamic mapping rules between message type and communication connection type are shown in Table 3 above, and will not be elaborated further here.

[0086] Based on the data transmission strategy adjustment device described above, this embodiment further optimizes long-connection communication. In one possible implementation, when the electric two-wheeled vehicle and the cloud platform enable long-connection communication for real-time data transmission (involving the first communication connection selection module, the high-frequency periodic message and event message connection selection unit of the periodic message connection selection unit), the two can maintain the connection using a heartbeat mechanism. That is, the vehicle terminal periodically sends small-volume heartbeat messages to confirm the connection status with the cloud platform and prevent the platform server from actively closing the connection. Simultaneously, when the vehicle has no data transmission for a certain period (e.g., parked in a parking lot at night), long-connection communication can be temporarily disabled to balance real-time performance and resource consumption.

[0087] Based on the data transmission strategy adjustment device described above, this embodiment further optimizes short-connection communication. Specifically, when the electric two-wheeled vehicle transmits static messages to the cloud platform, differential compression technology (transmitting only changes) is used to compress the static messages to adapt to low-power vehicle scenarios. In one possible implementation, differential compression technology can be implemented through the incremental transmission strategy of the lightweight and efficient transmission protocol TinyFLET. The specific compression process generally includes: a preprocessing stage (classifying data in the static message), an encoding stage (replacing field IDs, compressing values, and adding verification), and message transmission.

[0088] Optionally, a customized packet splitting strategy can be used for transmission. The core requirements of this strategy are a single packet size ≤ 128 bytes and a packet splitting interval ≥ 15 seconds, which can reduce transmission bandwidth usage and battery power consumption. After static messages are differentially compressed using TinyFLET, only the fields that have changed with historical snapshots (such as coordinate increments and status change values) are transmitted, significantly reducing the data volume. Setting the maximum single packet size to 128 bytes not only reserves sufficient space for the compressed message but also handles situations where multiple fields change simultaneously in extreme scenarios, avoiding frequent packet splitting due to insufficient single packet capacity, thus balancing compression efficiency and transmission stability. Since the core content of static messages changes very infrequently, and some fields even remain unchanged for a long time, static messages have a higher tolerance for transmission latency compared to the real-time requirements of dynamic event messages. Setting a packet splitting interval of more than 15 seconds can avoid high-frequency transmission of slowly changing data, reducing unnecessary communication interactions, lowering power consumption from the transmission frequency, and alleviating the pressure on vehicle battery wear.

[0089] The data transmission strategy adjustment device in this embodiment also includes a hybrid power supply management module. This module is used to charge the supercapacitor emergency module from the electric vehicle's main battery in the hybrid power supply system when the vehicle is in motion. It is also used to automatically switch power supply to the supercapacitor emergency module when the vehicle is powered off, ensuring complete reporting of event messages. The supercapacitor emergency module includes a supercapacitor energy storage unit, a bidirectional DC / DC energy management module, and an intelligent power monitoring and switching module. The bidirectional DC / DC energy management module is connected to the high-voltage battery bus and the supercapacitor, respectively, to achieve bidirectional energy flow control. When the vehicle is running normally, it converts battery energy into a voltage suitable for charging the supercapacitor. When the main battery is disconnected, it operates in reverse, converting the supercapacitor energy into the voltage required by the system.

[0090] Optionally, during supercapacitor power supply, the IoT communication module receives the highest priority power supply to ensure the reporting of critical data.

[0091] In this embodiment, when the electric vehicle's main battery is disconnected, the supercapacitor emergency module achieves continuous power supply for more than 120 seconds through a rapid switching and stable voltage boosting mechanism, ensuring complete reporting of emergency events. This solution solves the problem of data timeliness in traditional vehicle monitoring systems, providing a solid guarantee for the safe operation of electric vehicles.

[0092] The data transmission strategy adjustment device provided in this embodiment is the first to achieve an "on-demand connection" architecture in the off state of a two-wheeled vehicle. Actual testing shows that the data transmission success rate is increased to 99.2% (compared to <85% for traditional solutions), monthly communication traffic is reduced by 76%, and battery life is extended by 3-8 months. The core technology has passed EMC Level 3 certification for vehicle-mounted equipment and is suitable for wide voltage platforms (36V-72V DC) such as electric bicycles and motorcycles.

[0093] Each module in the aforementioned data transmission strategy adjustment device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0094] In one embodiment, a computer device is provided, which may be a vehicle-mounted terminal, and its internal structure diagram may be as follows: Figure 7 As shown, the computer device includes a main controller, memory, and communication interface connected via a system bus. The main controller provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores data such as vehicle status information, various message information, and instructions issued by an external cloud platform. The communication interface allows for wireless communication with an external cloud platform, which can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When executed by the main controller, the computer program implements a data transmission strategy adjustment method based on the start-stop status of the electric two-wheeled vehicle.

[0095] Those skilled in the art will understand that Figure 7 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0096] In one embodiment, a computer device is provided, including a memory and a main controller, wherein the memory stores a computer program, and the main controller executes the computer program to perform the following steps: Step 502: Detect the current vehicle status. Specifically, the on-board terminal of the electric two-wheeler can collect information from the vehicle's sensor array and battery BMS, and combine these two types of information to determine whether the vehicle is in a powered-off state or in a driving state.

[0097] The sensor array typically includes vibration sensors (for monitoring vehicle collisions), temperature sensors (for monitoring charger temperature), an anti-theft alarm, an inertial measurement unit (IMU) or tilt sensor (for monitoring vehicle roll), and radar (for detecting approaching personnel), thus determining whether the vehicle is stationary. BMS information typically includes voltage (individual cell voltage, total voltage, minimum / maximum voltage, etc.), charging or discharging current, temperature (individual cell temperature, average temperature, or maximum / minimum temperature), and state of charge (SOC). In this embodiment, when the on-board terminal detects that the battery voltage is below the safety threshold of 48V, and the vehicle is completely stationary and maintains a stable posture for a certain period (e.g., 60 seconds), the vehicle is considered to be in a powered-off state; otherwise, the vehicle is in motion.

[0098] Step 504: If the vehicle is in motion, the electric two-wheeler and the cloud platform enable long-connection communication for real-time data transmission. Specifically, a customized lightweight long-connection protocol is used to achieve rapid connection establishment between the vehicle terminal and the cloud platform: First, the vehicle terminal initiates a connection request via the network. After receiving the request, the cloud platform connection node completes device authentication within a short time. After successful authentication, a unique long-connection identifier (ConnID) is assigned, and a connection establishment success response is returned to the vehicle terminal. Thereafter, electric vehicle data can be reported to the cloud platform in real time.

[0099] Step 506: If the vehicle is powered off, activate the vehicle's low-power monitoring mode and, based on the classification of the electric vehicle messages to be transmitted, select the appropriate connection and communication strategy between the electric two-wheeler and the cloud platform for data transmission. Specifically, after the vehicle is powered off, the on-board terminal automatically switches to low-power monitoring mode and achieves accurate transmission of different types of messages through on-demand wake-up and classified communication strategies.

[0100] Among them, electric vehicle messages in the IoT device interconnection scenario of two-wheeled vehicles can be divided into static messages, periodic messages, and event messages; connection communication strategies are generally divided into long connection communication and short connection communication.

[0101] The aforementioned data transmission strategy adjustment method overcomes the limitations of traditional single-connection strategies by employing a dynamic adaptation mechanism that combines real-time transmission with long-term connections during operation and low-power classified communication during shutdown. This achieves multi-dimensional optimization in energy efficiency control, transmission quality, scenario coverage, and data security: 1) Precise energy efficiency control significantly extends the vehicle battery's range; 2) Graded transmission quality assurance balances real-time performance and reliability. This method not only addresses the pain points of insufficient real-time performance during operation and high energy consumption and disconnection during shutdown caused by traditional solutions, but also provides technical support for the intelligent management of electric two-wheeled vehicles.

[0102] Step 506 mentions a low-power monitoring mode, which is triggered when the vehicle is powered off. In this mode, only the IoT communication module, alarm, key sensor groups (such as vibration and tilt sensors), and some BMS modules (such as the temperature gradient detection module) are operational. In one possible implementation, in low-power monitoring mode, the main controller of the electric two-wheeler (located in the on-board terminal) can be woken up by the vibration sensor, tilt sensor, and BMS temperature gradient detection module installed on the vehicle. This allows the electric two-wheeler to perform the step of selecting the appropriate connection and communication strategy between the electric two-wheeler and the cloud platform for data transmission based on the classification of the electric vehicle message to be transmitted.

[0103] In this embodiment, the wake-up function triggered by key sensors (such as displacement vibration) is supported. The wake-up sensitivity can be flexibly adjusted according to different vehicle models and usage scenarios. This avoids invalid wake-up caused by slight vibrations and can accurately detect abnormal actions such as vehicle theft and illegal displacement, thereby achieving on-demand wake-up and energy-saving monitoring.

[0104] To achieve the core requirement of step 506, it is necessary to establish a dynamic mapping rule between message type and communication connection type. This rule is generated based on the adaptation analysis of static messages, periodic messages, event messages and long connections / short connections. The characteristics of these two connection types are shown in Table 1 above, and will not be repeated here.

[0105] In one embodiment, when the main controller executes the computer program, step 506 further performs the following steps: Step 602: Parse the electric vehicle message to be transmitted. The definitions of each message and examples for two-wheeled vehicle scenarios are shown in Table 2 above, and will not be repeated here.

[0106] The parsing process can be based on a closed-loop logic of flag bit pre-definition → message preprocessing → flag bit extraction → type output, ensuring parsing accuracy and efficiency. In one possible implementation, after the vehicle terminal transmits the original message through the electric vehicle bus (such as CAN bus) or communication network module (such as IoT communication module), it verifies the message integrity, such as checking whether the message header, trailer, and check bits are complete. Then, based on the preset protocol format, it locates and extracts the message type flag bit field located in the high bits (set differently for the three types of messages). Next, for the initially determined message type, it further parses the auxiliary flag bits located in the low bits to complete the message type confirmation and supplement attribute information to avoid misjudgment. Finally, after completing the type determination, it outputs the clear message type and associated attributes, and triggers the corresponding subsequent processing logic.

[0107] Optionally, if the vehicle terminal does not detect the message data that needs to be transmitted within a certain period of time, it will enter a deep sleep state and wait for the next wake-up.

[0108] Step 604: When the electric vehicle message to be transmitted is a static message, the electric two-wheeler and the cloud platform use short-connection communication for single data transmission. Combining the information in Tables 1 and 2, it can be concluded that static messages are suitable for short-connection communication because: static messages are sent very infrequently (only during vehicle initialization, restart, or firmware updates) and have a small data volume (containing only fixed information). The "use and close" characteristic of short connections avoids long-term occupation of server resources, and the connection overhead (three-way handshake + four-way handshake) for each transmission has minimal impact on overall performance. In this embodiment, the application scenario is: when the electric two-wheeler first connects to the cloud platform, it sends a static message containing the vehicle ID and model; subsequent frequent transmissions are unnecessary, and short connections save resources.

[0109] Optionally, short-connection communication with static messages also needs to ensure that the message is sent successfully (e.g., via ACK confirmation) to avoid data loss due to connection closure.

[0110] Step 606: When the electric vehicle message to be transmitted is a periodic message, the electric two-wheeler and the cloud platform use hybrid connection communication for data transmission. Hybrid connection communication refers to the dynamic switching between long and short connection communication. The standard for dynamic switching can refer to the specific size of a given time interval, i.e., whether the periodic message requires high-frequency or low-frequency transmission. Further analysis will be provided later.

[0111] Step 608: When the electric vehicle message to be transmitted is an event message, the electric two-wheeler and the cloud platform enable long-connection communication for real-time data transmission. Combining Tables 1 and 2, it can be concluded that long-connection communication is suitable for event messages because: event-triggered messages have extremely high real-time requirements (e.g., collision alarms need to immediately notify the platform, and user unlocking commands need to be executed immediately). The bidirectional real-time communication characteristics of long connections can ensure low-latency message transmission (the server can actively send commands to the vehicle terminal, and the vehicle terminal can also immediately report the event), avoiding delayed event reporting due to the connection establishment time of short connections (e.g., waiting for connection establishment after a collision before reporting may miss the optimal processing time). In this embodiment, the application scenario is: when the electric two-wheeler is collided with, the vehicle terminal immediately reports a "collision event" via a long connection, and the cloud platform can quickly notify maintenance personnel upon receiving the report; when the user unlocks the vehicle with their mobile phone, the cloud platform immediately sends an "unlocking command" via a long connection, and the vehicle terminal unlocks immediately upon receiving the command, thereby improving the user experience.

[0112] In this embodiment, using the preset flag bits of each message as the core anchor point, a closed-loop four-step process is established to achieve rapid and accurate parsing of electric vehicle message types. Based on this, differentiated connection and communication strategies are matched for different message types: 1) significantly improved energy efficiency; 2) enhanced transmission reliability; 3) optimized resource utilization. The overall solution, through the coordinated optimization of parsing logic and communication strategies, perfectly meets the core requirements of low power consumption, high real-time performance, and high reliability of electric two-wheeled vehicle onboard monitoring systems.

[0113] Regarding step 606, the analysis above has shown that periodic messages with different transmission frequencies are adapted to different connection strategies. In one possible implementation, the specific implementation process of step 606 includes: querying a given time interval of the periodic message; if the interval exceeds a set period threshold (e.g., the interval duration is greater than 5 minutes), the message is considered to be a low-frequency periodic message, and the electric two-wheeler and the cloud platform use short connection communication for single data transmission; if the interval does not exceed the set period threshold (e.g., the interval duration is less than or equal to 5 minutes), the message is considered to be a high-frequency periodic message, and the electric two-wheeler and the cloud platform use long connection communication for real-time data transmission.

[0114] Combining the information in Tables 1 and 2, it can be concluded that high-frequency periodic messages are suitable for long-connection communication because periodic messages are sent at medium to high frequencies (e.g., once every minute / hour) and require regular transmission. The persistent connection characteristic of long connections reduces the connection overhead for each transmission (no need to repeatedly establish TCP connections), improving transmission efficiency. Especially for the periodic status reporting of two-wheeled vehicles (e.g., battery level, vehicle location), long connections ensure timely data transmission and do not increase device power consumption due to frequent connections (two-wheeled vehicle devices usually rely on batteries, and reducing the number of connections can extend battery life). Low-frequency periodic messages are suitable for short-connection communication, which uploads infrequently used data to the cloud platform through a single connection, and immediately releases connection resources after transmission, avoiding power consumption caused by continuous connection occupation. In this embodiment, the application scenario is: after the electric vehicle is turned off, it reports location and battery information every half hour. In this case, short-connection communication is preferred because short connections only wake up modules (e.g., GPS and key sensors) when reporting data, and immediately go into sleep mode after transmission, maximizing battery life.

[0115] Optionally, the size of the periodic threshold can be dynamically modified on the cloud platform according to the actual application situation and then distributed to the electric two-wheeler.

[0116] In this embodiment, under the IoT scenario of electric two-wheeled vehicles, static messages use short-connection communication, periodic messages use either long or short-connection communication depending on the period length, and real-time event messages, due to their high real-time requirements, must use long-connection communication, thereby achieving a balance between resource optimization and performance assurance. The final dynamic mapping rules between message type and communication connection type are shown in Table 3 above, and will not be elaborated further here.

[0117] Based on steps 502-506 described above, this embodiment further optimizes the long-connection communication. In one possible implementation, when the electric two-wheeler and the cloud platform use long-connection communication for real-time data transmission (involving the high-frequency periodic messages in steps 504 and 606 and step 608), the two can maintain the connection using a heartbeat mechanism. That is, the vehicle terminal periodically sends small-volume heartbeat messages to confirm the connection status with the cloud platform, thus preventing the platform server from actively closing the connection. Simultaneously, when the vehicle has no data transmission for a certain period (e.g., when parked in a parking lot at night), long-connection communication can be temporarily disabled to balance real-time performance and resource consumption.

[0118] Based on steps 502-506 described above, this embodiment further optimizes short-connection communication. Specifically, when the electric two-wheeled vehicle transmits static messages to the cloud platform, differential compression technology (transmitting only changes) is used to compress the static messages to adapt to low-power vehicle scenarios. In one possible implementation, differential compression technology can be implemented through the incremental transmission strategy of the lightweight and efficient transmission protocol TinyFLET. The specific compression process generally includes: a preprocessing stage (classifying data in the static message), an encoding stage (replacing field IDs, compressing values, and adding verification), and message transmission.

[0119] Optionally, a customized packet splitting strategy can be used for transmission. The core requirements of this strategy are a single packet size ≤ 128 bytes and a packet splitting interval ≥ 15 seconds, which can reduce transmission bandwidth usage and battery power consumption. After static messages are differentially compressed using TinyFLET, only the fields that have changed with historical snapshots (such as coordinate increments and status change values) are transmitted, significantly reducing the data volume. Setting the maximum single packet size to 128 bytes not only reserves sufficient space for the compressed message but also handles situations where multiple fields change simultaneously in extreme scenarios, avoiding frequent packet splitting due to insufficient single packet capacity, thus balancing compression efficiency and transmission stability. Since the core content of static messages changes very infrequently, and some fields even remain unchanged for a long time, static messages have a higher tolerance for transmission latency compared to the real-time requirements of dynamic event messages. Setting a packet splitting interval of more than 15 seconds can avoid high-frequency transmission of slowly changing data, reducing unnecessary communication interactions, lowering power consumption from the transmission frequency, and alleviating the pressure on vehicle battery wear.

[0120] In one embodiment, the main controller, when executing a computer program, also performs the following steps: Step 508: When the vehicle is in motion, the electric vehicle's main battery charges the supercapacitor emergency module. When the vehicle is powered off, the main battery is de-energized, and the system automatically switches to power from the supercapacitor emergency module, ensuring complete event reporting. The supercapacitor emergency module includes a supercapacitor energy storage unit, a bidirectional DC / DC energy management module, and an intelligent power monitoring and switching module. The bidirectional DC / DC energy management module connects to both the high-voltage battery bus and the supercapacitor, enabling bidirectional energy flow control. During normal vehicle operation, it converts battery energy into a voltage suitable for charging the supercapacitor. When the main battery is disconnected, it operates in reverse, converting the supercapacitor energy into the voltage required by the system.

[0121] Optionally, during supercapacitor power supply, the IoT communication module receives the highest priority power supply to ensure the reporting of critical data.

[0122] In this embodiment, when the electric vehicle's main battery is disconnected, the supercapacitor emergency module achieves continuous power supply for more than 120 seconds through a rapid switching and stable voltage boosting mechanism, ensuring complete reporting of emergency events. This solution solves the problem of data timeliness in traditional vehicle monitoring systems, providing a solid guarantee for the safe operation of electric vehicles.

[0123] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor: Step 702: Detect the current vehicle status. Specifically, the on-board terminal of the electric two-wheeler can collect information from the vehicle's sensor array and battery BMS, and combine these two types of information to determine whether the vehicle is in a powered-off state or a driving state. In this embodiment, when the on-board terminal detects that the battery voltage is lower than the safety threshold of 48V, and the vehicle is completely stationary (sensed by the on-board sensors) and maintains a stable posture for a certain period of time (e.g., 60 seconds), the vehicle is considered to be in a powered-off state; otherwise, the vehicle is in a driving state.

[0124] Step 704: If the vehicle is in motion, the electric two-wheeler and the cloud platform enable long-term communication for real-time data transmission.

[0125] Step 706: If the vehicle is powered off, activate the vehicle low-power monitoring mode, and based on the classification of the electric vehicle messages to be transmitted, the electric two-wheeler and the cloud platform select the appropriate connection and communication strategy for data transmission. This step specifically includes: Parsing the electric vehicle message to be transmitted: When the message is a static message, the electric two-wheeler and the cloud platform use short connection communication for single data transmission; when the message is a periodic message, the electric two-wheeler and the cloud platform use hybrid connection communication for data transmission, where hybrid connection communication refers to the dynamic switching between long and short connection communication; when the message is an event message, the electric two-wheeler and the cloud platform use long connection communication for real-time data transmission.

[0126] Preferably, when the electric two-wheeler transmits static messages to the cloud platform, the lightweight and efficient transmission protocol TinyFLET is used to compress the static messages, and the packet splitting strategy is set as follows: single packet size ≤ 128 bytes, packet interval ≥ 15 seconds, to adapt to the low-power vehicle scenario; and the short-connection communication of static messages must also ensure successful message transmission (e.g., through ACK confirmation) to avoid data loss due to connection closure. When the electric two-wheeler and the cloud platform use long-connection communication for real-time data transmission, the two can use a heartbeat mechanism to maintain the connection; at the same time, when the vehicle has no data transmission for a certain period of time (e.g., parked in a parking lot at night), the long-connection communication can be temporarily closed to balance real-time performance and resource consumption.

[0127] In one embodiment, when the computer program is executed by a processor, it also performs the following steps: Step 708: When the vehicle is in motion, the electric vehicle's main battery charges the supercapacitor emergency module. When the vehicle is powered off, the electric vehicle's main battery is de-energized, and the system automatically switches to power supply from the supercapacitor emergency module to ensure complete event reporting.

[0128] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following: First, it detects the current vehicle status. If the vehicle is in motion, the electric two-wheeler and the cloud platform enable long-term communication for real-time data transmission; if the vehicle is powered off, it activates a low-power monitoring mode and, based on the classification of the electric vehicle messages to be transmitted, the electric two-wheeler and the cloud platform select an appropriate connection communication strategy for data transmission.

[0129] In addition, when the computer program is executed by the processor, it also performs the following: When the vehicle is in motion, the electric vehicle's main battery charges the supercapacitor emergency module. When the vehicle is powered off, the electric vehicle's main battery is de-energized, and the system automatically switches to power supply from the supercapacitor emergency module to ensure complete reporting of event messages.

[0130] The solution provided by this computer program product is similar to the solution described in the above method. Therefore, for specific limitations, please refer to the limitations of the data transmission strategy adjustment method above, which will not be repeated here.

[0131] It should be noted that all data involved in this application (including but not limited to data used for analysis, stored data, and displayed data) are information and data that have been authorized by the user or fully authorized by all parties.

[0132] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0133] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0134] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for adjusting data transmission strategies based on the start-stop status of an electric two-wheeled vehicle, characterized in that, The method includes: The current vehicle status is detected. If the vehicle is in motion, the electric two-wheeler and the cloud platform enable long-connection communication for real-time data transmission. If the vehicle is powered off, the low-power monitoring mode is activated, and the electric two-wheeler and the cloud platform select the appropriate connection and communication strategy for data transmission based on the classification of the electric vehicle messages to be transmitted.

2. The data transmission strategy adjustment method according to claim 1, characterized in that, Based on the classification of the electric vehicle messages to be transmitted, the electric two-wheeler and the cloud platform select the appropriate connection and communication strategy for data transmission, including: Parse the electric vehicle message to be transmitted; When the electric vehicle message to be transmitted is a static message, the electric two-wheeler and the cloud platform use short connection communication to perform a single data transmission. When the electric vehicle message to be transmitted is a periodic message, the electric two-wheeler and the cloud platform enable hybrid connection communication for data transmission; When the electric vehicle message to be transmitted is an event message, the electric two-wheeler and the cloud platform enable the long connection communication for real-time data transmission. The hybrid connection communication refers to the dynamic switching between long and short connection communication.

3. The data transmission strategy adjustment method according to claim 2, characterized in that, The periodic message is defined as status information sent at given time intervals, including battery level and vehicle location; When the electric vehicle message to be transmitted is a periodic message, the electric two-wheeler and the cloud platform enable hybrid connection communication for data transmission, including: If the given time interval of the periodic message is queried, and the interval exceeds the set periodic threshold, then the electric two-wheeled vehicle and the cloud platform will use the short connection communication to perform a single data transmission. Otherwise, the electric two-wheeled vehicle and the cloud platform will use the long-connection communication for real-time data transmission.

4. The data transmission strategy adjustment method according to claim 2, characterized in that, The static message is defined as vehicle-specific information, including vehicle ID, model, and firmware version; The event message is defined as real-time information triggered when a specific event occurs, including vehicle collision alarm, vehicle tipping alarm, and battery temperature change alarm.

5. The data transmission strategy adjustment method according to claim 2, characterized in that, The method further includes: When the electric two-wheeled vehicle and the cloud platform use long-connection communication for real-time data transmission, a heartbeat mechanism is used to maintain the connection. If a vehicle has no data transmission for a certain period of time, the long-connection communication will be temporarily closed.

6. The data transmission strategy adjustment method according to claim 2, characterized in that, The method further includes: When the electric two-wheeled vehicle transmits the static message to the cloud platform, the lightweight and efficient transmission protocol TinyFLET is used to compress the static message.

7. The data transmission strategy adjustment method according to claim 2, characterized in that, The method further includes: When the vehicle is in motion, the electric vehicle's main battery charges the supercapacitor emergency module. When the vehicle is powered off, the main battery of the electric vehicle is de-energized and automatically switched to be powered by the supercapacitor emergency module to ensure that the event message is reported completely.

8. The data transmission strategy adjustment method according to claim 1, characterized in that, In the low-power monitoring mode, the main controller of the electric two-wheeler is woken up by the vibration sensor, tilt sensor, and BMS temperature gradient detection module installed on the vehicle, so as to execute the step of the electric two-wheeler and the cloud platform selecting the appropriate connection communication strategy for data transmission based on the classification of the electric vehicle message to be transmitted.

9. The data transmission strategy adjustment method according to claim 3, characterized in that, The method further includes: On the cloud platform, the size of the periodic threshold is dynamically modified and sent to the electric two-wheeler.

10. A data transmission strategy adjustment system based on the start-stop state of an electric two-wheeled vehicle, characterized in that, It includes an electric two-wheeled vehicle and a cloud platform, both of which perform the data transmission strategy adjustment method as described in any one of claims 1-9.

Images