A vehicle control method and vehicle
By identifying the type of vehicle control command and selecting the optimal communication mode for transmission, the problems of high latency and low reliability in remote vehicle control command transmission are solved, achieving more efficient remote vehicle control command transmission.
Patent Information
- Application Number
- CN202611488861.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-23
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, the transmission latency of remote vehicle control commands between mobile terminals and vehicles is too high or the command transmission fails, resulting in low reliability of remote vehicle control. This is mainly because different communication modes work independently and fail to perform unified scheduling based on the communication status between the user and the vehicle.
The system identifies the type of vehicle control command via a remote terminal, uses a preset channel capability mapping relationship to determine whether the command type belongs to the command set supported by the first communication mode, and selects the optimal communication mode for command transmission based on the current communication status. This includes pre-wake-up of the vehicle terminal, detection of the availability of the target communication mode, and a switching mechanism to ensure that the command type matches the communication mode.
It improves the reliability and success rate of remote vehicle control command transmission, reduces transmission latency, and enhances the immediacy and reliability of remote vehicle control.
Smart Images

Figure CN123123850A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle control technology, and in particular to a vehicle control method and a vehicle. Background Technology
[0002] With the development of vehicle networking technology, remotely controlling vehicles via mobile terminals has become a common need for users.
[0003] In existing technologies, mobile terminals and vehicle-mounted terminals can transmit vehicle control commands through different communication modes. Each communication mode works independently, and the system usually sends commands according to the default communication mode or the communication mode manually selected by the user, without judging the compatibility between the command type and the current communication mode.
[0004] However, since different communication modes support different command ranges, this method is prone to causing the type of command issued by the user to be incompatible with the communication mode, which in turn leads to high transmission latency of vehicle control commands or even failure to issue commands, resulting in low reliability of remote vehicle control. Summary of the Invention
[0005] This application addresses, to at least some extent, one of the technical problems in the related art.
[0006] In a first aspect, embodiments of this application provide a vehicle control method, which is applied to a remote terminal, the remote terminal being connected to an in-vehicle terminal through at least a first communication mode and a second communication mode.
[0007] The method includes the following steps: The system receives vehicle control commands issued by the user, identifies the command type of the vehicle control command, and determines whether the command type belongs to the first command set supported by the first communication mode based on the preset channel capability mapping relationship. The channel capability mapping relationship is used to characterize the support relationship between the command type and the communication channel. The communication range of the first communication mode is smaller than the communication range of the second communication mode. If the instruction type does not belong to the first instruction set, then the second communication mode is determined as the target communication mode for communicating with the vehicle terminal. If the instruction type belongs to the first instruction set, obtain the communication status of the current first communication mode and the communication status of the second communication mode, and determine the target communication mode for communicating with the vehicle terminal based on the instruction type, the communication status of the first communication mode and the communication status of the second communication mode.
[0008] Based on the above control method, in this embodiment, after receiving a vehicle control command, the remote terminal first identifies the command type. For commands that do not belong to the first command set, it directly determines the second communication mode with a wider communication range as the target communication mode. For commands that belong to the first command set, it makes a fusion decision based on the command type and the real-time status of the two communication modes to determine the target communication mode. This not only makes full use of the communication advantages of the first communication mode when it is available, but also automatically switches to the second communication mode when it is unavailable. This ensures that the channel selection matches the command type and real-time communication conditions, avoiding excessive command transmission delays or delivery failures due to improper channel selection, and effectively improving the reliability and execution success rate of remote vehicle control command transmission.
[0009] In some embodiments, determining whether an instruction type belongs to the first instruction set supported by the first communication mode is based on a preset channel capability mapping relationship, including: If the instruction type is only supported for transmission by the second communication mode, then the instruction type is determined not to belong to the first instruction set; If an instruction type is supported for transmission by both the first and second communication modes, then the instruction type is determined to belong to the first instruction set.
[0010] Based on the above control method, the embodiments of this application define the determination rule for the classification of instruction types. This determination rule uses whether the instruction type can be supported for transmission by the first communication mode as the sole criterion to classify the instructions into two categories. This ensures that each vehicle control instruction is clearly classified into the range of channels that can support its transmission before it is issued. This not only ensures a strict match between channel selection and instruction type, avoiding instruction execution failure due to insufficient channel capacity, but also reserves the space for flexible channel selection for instructions that can be supported for transmission by multiple channels, further improving the reliability and success rate of remote vehicle control instruction transmission.
[0011] In some embodiments, the communication state of the first communication mode includes the connection state of the first communication mode; the communication state of the second communication mode includes the communication quality of the second communication mode. Based on the instruction type, the communication status of the first communication mode, and the communication status of the second communication mode, the target communication mode for communicating with the vehicle terminal is determined, including: If the instruction type belongs to the first instruction set and the first communication mode connection status is connected, the first communication mode is determined as the target communication mode; If the first communication mode is disconnected and the communication quality of the second communication mode meets the preset transmission conditions, the second communication mode is determined as the target communication mode.
[0012] Based on the above control method, in this embodiment, when the first communication mode is connected, it is directly determined as the target communication mode. Since the communication range of this mode is small, the command can be transmitted through a shorter path, improving the immediacy of the command response. When the first communication mode is disconnected and the second communication mode meets the preset transmission conditions, the second communication mode is determined as the target communication mode. Thus, when the first communication mode is unavailable, the command can be issued by using the second communication mode with a larger communication range. This ensures reliable delivery of the command while taking into account the response speed, thereby improving the success rate and immediacy of remote vehicle control command issuance as a whole.
[0013] In some embodiments, the method further includes: After determining the target communication mode, compare the target communication mode with the current communication mode; If the target communication mode is the same as the current communication mode, the vehicle control command is directly sent to the vehicle terminal through the target communication mode. If the target communication mode is different from the current communication mode, the vehicle control command is sent to the vehicle terminal through the target communication mode.
[0014] Based on the above control method, in this embodiment of the application, after determining the target communication mode, the target communication mode is first compared with the current communication mode, and when the target communication mode is different from the current communication mode, the target communication mode is switched to, so that the vehicle control command can be sent to the vehicle terminal through the current optimal communication mode, avoiding the response delay caused by the transmission of the command along the communication mode with higher latency, and further improving the immediacy of the remote vehicle control command issuance.
[0015] In some embodiments, if the target communication mode is different from the current communication mode, the method further includes: Maintain the connection of the current communication mode, send a probe command to the target communication mode, and confirm whether the target communication mode is available based on the response to the probe command; If the target communication channel is available, disconnect the current communication mode and send vehicle control commands to the vehicle terminal through the target communication mode; Otherwise, maintain the current communication mode and issue vehicle control commands to the vehicle terminal through the current communication mode.
[0016] Based on the above control method, in this embodiment of the application, the current communication mode is disconnected and the vehicle control command is sent through the target communication mode only after the target communication mode is confirmed to be available. This achieves a smooth transition of communication mode switching, avoids the loss or failure of vehicle control command due to the unavailability or abnormal response of the new communication mode during the switching process, and further improves the reliability of remote vehicle control command sending.
[0017] In some embodiments, a response confirmation target communication mode based on a probe command is available, including: The response latency of the probe command is obtained and compared with a preset latency threshold. If the response delay is less than the preset delay threshold, the target communication mode is confirmed to be available. Otherwise, if the target communication mode is confirmed to be unavailable, maintain the current communication mode and send vehicle control commands to the vehicle terminal through the current communication mode.
[0018] Based on the above control method, this embodiment uses the response delay of the probe command as a criterion, comparing the response delay with a preset delay threshold. The target communication mode is confirmed to be usable only if the response delay is less than the preset delay threshold; otherwise, it is unusable. Since the response delay directly reflects the connectivity and timeliness of the current link of the target communication mode, confirming usability before switching ensures that the switched communication mode is truly usable, avoiding transmission failure due to misjudgment that commands are sent to a communication mode with a poor link or slow response.
[0019] In some embodiments, the method further includes: If the instruction type belongs to the first instruction set, the connection status of the first communication mode is detected in real time to see if it has changed. If so, start timing and continuously monitor the connection status of the first communication mode within the preset anti-shake duration; If the connection status of the first communication mode has been restored to the state before the change before the timer reaches the preset anti-shake duration, the current communication mode is maintained to send vehicle control commands to the vehicle terminal. If the connection status of the first communication mode remains unchanged after the preset anti-shake duration is reached, the target communication mode is re-determined based on the instruction type, the communication status of the first communication mode, and the communication status of the second communication mode.
[0020] Based on the above control method, this application embodiment defines an anti-jitter mechanism for channel switching. This anti-jitter mechanism filters connection state changes using a preset anti-jitter duration through a time window, distinguishing between brief fluctuations and continuous changes in the connection state of the first communication mode. This avoids frequent switching of communication modes due to instantaneous jitter and ensures timely re-decision when the channel state changes significantly, thereby further improving the stability and reliability of remote vehicle control command issuance in a dynamically changing communication environment.
[0021] In some embodiments, the method further includes: After sending a vehicle control command to the vehicle terminal through the target communication mode, if no command execution response is received from the vehicle terminal within the preset response time, the vehicle control command is resent within the target communication mode. If the number of times the vehicle control command is resent within the target communication mode reaches the preset retry count and no command execution response is received, and the command type belongs to the first command set, switch to another communication channel that is not the current target communication mode to resend the vehicle control command. If no execution response is received after switching channels and re-issuing the command, the pre-wake-up of the vehicle terminal will be triggered again, and the vehicle control command will be re-sent through the target communication mode. If no response is received after issuing the vehicle control command again, a command failure message will be generated.
[0022] Based on the above control method, this application embodiment defines a recovery mechanism after command issuance failure. This recovery mechanism employs a three-level recovery approach, progressively addressing the possible causes of failure: retrying on the same channel, retrying by switching channels, and retrying after a pre-wake-up. It provides a clear failure message when all recovery methods fail, transforming recoverable, transient command transmission failures into successful transmission and execution. Furthermore, it provides clear feedback when recovery is truly impossible, which helps to further improve the success rate of remote vehicle control command execution and enhance the user experience.
[0023] In some embodiments, the method further includes: In response to the detected user vehicle control intent trigger event, the vehicle terminal is pre-wake-up; This includes pre-wake-up of the vehicle terminal, including: Send a wake-up command to the vehicle terminal; After receiving the wake-up response from the vehicle terminal in response to the wake-up command, a long connection is established with the vehicle terminal, and the vehicle terminal is placed in the ready state. Before receiving a vehicle control command from the user, keep the vehicle terminal in a ready state.
[0024] Based on the above control method, the embodiments of this application define a specific implementation method for pre-wake-up of the vehicle terminal. This pre-wake-up method realizes the forwarding of the wake-up process and the continuous maintenance of the ready state through three stages: wake-up confirmation, long connection establishment and ready maintenance. This ensures that the vehicle terminal is in a ready state to receive and execute commands at any time before the user actually issues the command, thereby eliminating the first command wake-up waiting delay caused by the vehicle terminal's sleep state and improving the immediacy of remote vehicle control command response.
[0025] In some embodiments, maintaining the vehicle terminal in a ready state includes: The preset keep-alive window duration is determined based on the trigger duration of the user's vehicle control intent-triggered event; Based on a preset heartbeat interval, continuously send keep-alive heartbeats to the vehicle terminal within a preset keep-alive window duration; If no vehicle control command is received from the user within the preset keep-alive window period, the vehicle terminal will return from the ready state to the sleep state.
[0026] Based on the above control method, the embodiments of this application define a specific implementation method for maintaining the ready state of the vehicle terminal. This keep-alive method adaptively matches the keep-alive window duration with the user's actual operation time window, reliably maintains readiness within the window using a heartbeat mechanism, and releases it in a timely manner after the window expires. This can eliminate secondary waiting caused by insufficient keep-alive and avoid energy waste caused by unlimited keep-alive. It improves the immediacy of remote vehicle control command response while reducing system energy consumption.
[0027] Secondly, embodiments of this application provide a vehicle control system, including: The pre-wake-up module is used to pre-wake up the vehicle's onboard terminal when a user's intent to control the vehicle is detected. The instruction matching module is used to identify the instruction type of the vehicle control instruction after receiving the vehicle control instruction issued by the user, and determine whether the instruction type belongs to the first instruction set based on the preset channel capability mapping relationship. The first communication determination module is used to determine the second communication mode as the target communication mode when the instruction type does not belong to the first instruction set; The status acquisition module is used to acquire the communication status of the current first communication mode and the communication status of the second communication mode when the instruction type belongs to the first instruction set. The channel decision module is used to determine the target communication mode for communicating with the vehicle terminal based on the instruction type, the communication status of the first communication mode, and the communication status of the second communication mode.
[0028] Thirdly, embodiments of this application provide a vehicle including a controller for executing the control method described in the first aspect above.
[0029] Fourthly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the control method described in the first aspect above.
[0030] As can be seen from the above technical solutions, additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description
[0031] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 This is a flowchart illustrating the control method according to an embodiment of this application; Figure 2 This is a flowchart illustrating the communication mode decision method of the control method according to an embodiment of this application; Figure 3 This is a flowchart illustrating the transmission failure retry method of the control method according to an embodiment of this application; Figure 4 This is a structural block diagram of the control system according to an embodiment of this application; Figure 5 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application.
[0032] In the above figures: 100. Pre-wake-up module; 200. Command matching module; 300. First communication determination module; 400. Status acquisition module; 500. Channel decision module; 50. Bus; 51. Processor; 52. Memory; 53. Communication interface. Detailed Implementation
[0033] To make the objectives, technical solutions, and advantages of this application clearer, the application is described and illustrated below with reference to 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. All other embodiments obtained by those skilled in the art based on the embodiments provided in this application without inventive effort are within the scope of protection of this application.
[0034] Obviously, the accompanying drawings described below are merely some examples or embodiments of this application. Those skilled in the art can apply this application to other similar scenarios based on these drawings without any inventive effort. Furthermore, it is understood that although the efforts made in this development process may be complex and lengthy, for those skilled in the art related to the content disclosed in this application, any changes to design, manufacturing, or production based on the technical content disclosed in this application are merely conventional technical means and should not be construed as insufficient disclosure of the content of this application.
[0035] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment that is mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments without conflict.
[0036] Unless otherwise defined, the technical or scientific terms used in this application shall have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms “a,” “an,” “an,” “the,” and similar words used in this application do not indicate quantity limitation and may indicate singular or plural. The terms “comprising,” “including,” “having,” and any variations thereof used in this application are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units not listed, or may include other steps or units inherent to these processes, methods, products, or devices. The terms “connected,” “linked,” “coupled,” and similar words used in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. “Multiple” used in this application refers to two or more. “And / or” describes the relationship between related objects, indicating that three relationships may exist; for example, “A and / or B” can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following objects are in an "or" relationship. The terms "first," "second," and "third" used in this application are merely to distinguish similar objects and do not represent a specific ordering of the objects.
[0037] With the development of vehicle networking technology, remote vehicle control via mobile terminals, such as unlocking doors, controlling windows, and adjusting air conditioning, has become a common function of vehicles.
[0038] In existing remote vehicle control solutions, there are typically two communication modes between the mobile terminal and the vehicle: one is a cellular network-based remote communication mode, where control commands issued by the mobile terminal are forwarded by the vehicle networking service platform to the in-vehicle wireless terminal, which then sends them to the vehicle's electronic control unit for execution, suitable for long-distance scenarios; the other is a Bluetooth-based near-field communication mode, where the mobile terminal directly connects to the vehicle's Bluetooth module via Bluetooth, sending control commands directly to the vehicle's electronic control unit for execution at close range. These two communication modes are set up independently within the system, each completing command transmission independently, without any coordination or scheduling mechanism between them. Furthermore, the system typically only establishes the corresponding communication connection and triggers the in-vehicle wireless terminal to wake from sleep mode after the user officially issues the control command.
[0039] However, precisely because the two communication modes are independent and do not communicate with each other, the system cannot uniformly schedule the communication mode for command transmission based on the communication status between the user and the vehicle. For example, when the user gradually approaches the vehicle from a distance, the system still uses the cellular remote channel to transmit commands and cannot utilize the lower latency near-field channel to complete the transmission. Alternatively, when the cellular network signal fluctuates, the system cannot adaptively adjust the communication mode, and the command can only wait on the original channel until it times out. This results in high latency in vehicle control command transmission or even failure to send commands, leading to low reliability of remote vehicle control.
[0040] Therefore, how to uniformly coordinate and schedule different communication modes to adaptively select the optimal communication channel based on the communication status between the user and the vehicle, and avoid high transmission latency or command failure due to improper channel selection, has become a key technical issue for improving the immediacy and reliability of remote vehicle control.
[0041] Therefore, this application provides a vehicle control method, which is applied to a remote terminal, the remote terminal being connected to an on-board terminal through at least a first communication mode and a second communication mode.
[0042] In this context, a remote terminal refers to a user-side terminal device used to initiate remote vehicle control. For example, a mobile phone with a vehicle control application installed has a multi-modal channel management module deployed on the application side for unified scheduling of various communication modes.
[0043] An in-vehicle terminal refers to an in-vehicle wireless terminal used to communicate with remote terminals. It is typically an in-vehicle telematics box (TBOX). Its main functions are to collect vehicle data, communicate in real-time with the vehicle-to-everything (V2X) service platform (TSP), report data, and assist in human-vehicle interaction. Vehicle control commands are ultimately relayed by the in-vehicle terminal to the vehicle's electronic control unit (ECU) for execution. It should be noted that in existing technologies, the in-vehicle terminal remains in a dormant state to conserve vehicle power, only waking up upon receiving a user's vehicle control command.
[0044] The first communication mode refers to the near-field direct communication mode with a relatively small communication range. For example, near-field direct communication between a mobile terminal and a vehicle-mounted Bluetooth module. This mode does not require relaying through a vehicle-to-everything (V2X) service platform, has low latency, and does not rely on cellular networks, but the communication distance is usually limited, for example, within 30 meters.
[0045] The second communication mode refers to a long-range communication mode with a larger communication range, such as long-range communication based on 4G / 5G cellular networks. This mode is relayed through the cloud of the vehicle network service platform, has a wide coverage, and is applicable to long-distance communication scenarios.
[0046] In this embodiment, each communication mode has its own corresponding communication channel. For example, in the first communication mode, the remote terminal and the vehicle's infotainment system communicate through the first communication channel; in the second communication mode, the remote terminal and the vehicle's infotainment system communicate through the second communication channel. Selecting the corresponding target communication mode means selecting the corresponding communication channel.
[0047] Figure 1 This is a flowchart of a control method according to an embodiment of this application, such as... Figure 1 As shown, the method includes the following steps: S1: In response to the detected user vehicle control intent trigger event, pre-wake up the vehicle terminal.
[0048] In this embodiment, the user vehicle control intent trigger event refers to a behavior or state change that can characterize a user's potential intention to remotely control the vehicle. For example, a user opening a vehicle control app, entering a vehicle control page, clicking the vehicle control function preview entry, or browsing vehicle status information within the app. The purpose of this trigger event is to identify the user's potential intention to control the vehicle before the user formally issues a specific control command, thereby providing a trigger basis for pre-wake-up.
[0049] Pre-wake-up refers to the process by which a remote terminal actively triggers the transition of the vehicle terminal from a dormant state to a ready state before the user officially issues a vehicle control command. It should be noted that in existing technologies, the vehicle terminal is usually a vehicle telematics box (TBOX), which remains in a dormant state for a long time to save vehicle power and is only woken up after receiving a user's vehicle control command.
[0050] In one embodiment of this application, the remote terminal detects the user's intent to control the vehicle by triggering an event in one of the following ways.
[0051] The remote terminal monitors page navigation events in the vehicle control application. When a user enters the vehicle control page from the application's homepage, it is determined that the user's intention to control the vehicle has been triggered. This method triggers the event close to the vehicle control operation, resulting in the highest accuracy of pre-wake-up.
[0052] The remote terminal monitors the user's clicks on the vehicle control function preview button, and a click on this button is considered a trigger event. This method allows for greater lead time, but may generate a small number of invalid wake-ups due to users only viewing information.
[0053] The remote terminal makes a comprehensive judgment based on factors such as the duration of the user's stay in the vehicle control application and their swiping actions.
[0054] It should be noted that the above implementation methods can be used in combination. For example, opening the application can be used as a weak trigger for early wake-up, and entering the vehicle control page can be used as a strong trigger for confirmed wake-up. Combining these methods can further advance the wake-up timing and control the power consumption caused by invalid wake-ups.
[0055] S2: Receives vehicle control commands issued by the user, identifies the command type, and determines whether the command type belongs to the first command set supported by the first communication mode based on a preset channel capability mapping relationship. The channel capability mapping relationship is used to characterize the support relationship between command types and communication channels. The communication range of the first communication mode is smaller than that of the second communication mode.
[0056] In this embodiment, the vehicle control command refers to the command issued by the user through the vehicle control application on a remote terminal to control a certain function of the vehicle. Examples include unlocking / locking, starting the vehicle, locating the vehicle, opening the trunk, controlling the air conditioning, heating the steering wheel, and heating the seats.
[0057] Command type refers to the classification of vehicle control commands according to their functional attributes, such as unlocking / locking, vehicle starting, vehicle locating, rear door access, cabin comfort, energy control, etc.
[0058] Channel capability mapping refers to pre-configured mapping data used to characterize the support relationship between each instruction type and the first and second communication modes, usually stored in the form of an instruction type-channel support table.
[0059] In one embodiment of this application, the first communication mode is Bluetooth near-field communication mode, and the supported command types are shown in Table 1. The second communication mode is cellular remote communication mode, and the supported command types are shown in Table 2. The command type-channel support table corresponding to Bluetooth near-field communication mode and cellular remote communication mode is shown in Table 3.
[0060] Table 1. Bluetooth Near Field Communication Mode Command Type Support Table
[0061] Table 2. Supported Command Types for Cellular Remote Communication Modes
[0062] Table 3 Command Type - Channel Support Table
[0063] S3: If the instruction type does not belong to the first instruction set, then the second communication mode is determined as the target communication mode for communicating with the vehicle terminal.
[0064] In this embodiment, the target communication mode refers to the communication mode ultimately selected by the remote terminal to issue current vehicle control commands to the vehicle terminal. When it is determined that the command type does not belong to the first command set, it indicates that the command type is a command not supported by the first communication mode, such as cabin comfort commands like air conditioning control, steering wheel heating, and seat heating. In this case, the second communication mode with a wider communication range is determined as the target communication mode.
[0065] For example, in an underground parking garage, a user's mobile phone is connected to the vehicle via Bluetooth. The user clicks "steering wheel heating" on the application. The application recognizes that the command type is cabin comfort type. After querying the channel capability mapping relationship, it determines that it does not belong to the first command set. Therefore, instead of using the currently connected Bluetooth channel, the command is sent to the vehicle network service platform via the cellular network. The vehicle network service platform then forwards the command to the vehicle telematics processor to execute the steering wheel heating, thus avoiding the problem of the command being mistakenly sent to the Bluetooth channel and unable to be executed.
[0066] S4: If the instruction type belongs to the first instruction set, obtain the communication status of the current first communication mode and the communication status of the second communication mode, and determine the target communication mode for communicating with the vehicle terminal based on the instruction type, the communication status of the first communication mode and the communication status of the second communication mode.
[0067] In this embodiment, the communication status of the first communication mode refers to whether the first communication mode is currently connected and its connection quality, such as whether Bluetooth is connected and its signal strength. The communication status of the second communication mode refers to the current communication quality of the second communication mode, such as cellular network signal strength, packet loss rate, and latency. The purpose of obtaining these statuses is that when the instruction type belongs to the first instruction set, it means that both communication modes can support the instruction, and in this case, a better channel needs to be selected based on the actual communication conditions.
[0068] Specifically, the connection status of the first communication mode can be obtained in real time through the Bluetooth connection callback interface of the remote terminal operating system. The communication quality of the second communication mode can be evaluated by collecting cellular network signal strength, measuring round-trip latency by sending probe messages to the vehicle-to-everything (V2X) service platform, and statistically analyzing command packet loss rate. The decision-making process can be implemented as a lookup-based rule matching, or as selecting the communication mode with the highest score after weighted scoring of each dimension's status. This weighted scoring method can further incorporate the relative distance between the user and the vehicle as a weighting factor, making the decision more closely aligned with actual usage scenarios.
[0069] In this embodiment, the remote terminal pre-wakes up the vehicle terminal when it detects the intention to control the vehicle, ensuring that the vehicle terminal is ready before the vehicle control command arrives, thus eliminating the wake-up wait for the first command. After receiving the vehicle control command, the remote terminal first identifies the command type and performs pre-matching based on the channel capability mapping relationship, forcing commands that only support remote transmission to be diverted to the second communication mode, avoiding command failure due to entering a channel that does not support its transmission. For commands that can be supported by both modes, a fusion decision is made by combining the real-time communication status of the two communication modes, realizing the coordinated scheduling of the two communication modes and improving the immediacy and reliability of remote vehicle control.
[0070] In some embodiments, the method for determining whether an instruction type belongs to the first instruction set supported by the first communication mode based on a preset channel capability mapping relationship includes the following steps.
[0071] If an instruction type is only supported for transmission by the second communication mode, then the instruction type is determined not to belong to the first instruction set.
[0072] If an instruction type is supported for transmission by both the first and second communication modes, then the instruction type is determined to belong to the first instruction set.
[0073] Understandably, in this embodiment, the instruction type is categorized into two classes based on whether the instruction type is supported only by the second communication mode. This ensures that each type of instruction is clearly assigned to its executable channel range before being issued. For instructions that can only be transmitted by the second communication mode, they are determined not to belong to the first instruction set and are thus forcibly assigned to the second communication mode in subsequent steps, preventing remote-specific instructions from failing to execute due to mistakenly entering the first communication mode. For instructions supported by both modes, they are determined to belong to the first instruction set, allowing such instructions to enter the fusion decision-making process based on the real-time status of the dual channels, thus preserving the space for channel selection.
[0074] The judgment rule has a unique standard and unambiguous results, which not only ensures a strict match between command type and channel capacity, but also retains the flexibility of channel selection for commands that can be transmitted through multiple channels, which is conducive to improving the success rate and reliability of vehicle control command execution.
[0075] Specifically, when a remote terminal queries the channel capability mapping relationship, a whitelist approach can be used. A whitelist of supported commands for the first communication mode is pre-established. If the current command type is not in this whitelist, it is determined that it does not belong to the first command set. Alternatively, a blacklist approach can be used. A blacklist of commands supported only by the second communication mode is pre-established. If the current command type is in this blacklist, it is determined that it does not belong to the first command set. Different implementation methods can be selected based on the convenience of data maintenance. When used in combination, both the whitelist and blacklist can be maintained simultaneously for two-way verification to improve accuracy.
[0076] Specifically, when pre-constructing the channel capability mapping table, two support flags can be configured for each instruction type in the table, indicating whether the first communication mode and the second communication mode are supported, respectively. The condition for determining that an instruction does not belong to the first instruction set is configured as "the first communication mode support flag is negative and the second communication mode support flag is positive"; the condition for determining that an instruction belongs to the first instruction set is configured as "both the first communication mode support flag and the second communication mode support flag are positive".
[0077] This dual-flag structure can also be extended to support abnormal instruction types that are "neither supported". When a remote terminal looks up a table, if it finds that both flags of an instruction type are negative, it can directly prompt the user that the instruction is currently unavailable and intercept invalid transmission in advance.
[0078] In this embodiment, when maintaining the mapping table, the platform uniformly configures two flag bits and sends them to the remote terminal when adding a new instruction type. The remote terminal automatically refreshes its local mapping table after a version upgrade.
[0079] In this embodiment, the rules for determining the attribution of instruction types are further defined. For instruction types that are supported for transmission only by the second communication mode, it is directly determined that they do not belong to the first instruction set. In subsequent steps, the second communication mode is used as the target communication mode to send such instructions, thus avoiding instruction transmission failure. For instruction types that are supported for transmission by both the first and second communication modes, they are determined to belong to the first instruction set. This allows such instructions to enter the fusion decision-making process based on the real-time status of the two communication modes. This process can fully utilize the communication advantages of the first communication mode when it is currently available, and automatically switch to the second communication mode when it is unavailable to ensure that the instructions can be reached.
[0080] In some embodiments, reference Figure 2 The communication status of the first communication mode includes the connection status of the first communication mode. The communication status of the second communication mode includes the communication quality of the second communication mode.
[0081] In this embodiment of the application, the connection status of the first communication mode refers to the status indicator of whether the first communication mode has established a connection with the vehicle terminal, including connected and not connected.
[0082] The second communication mode's communication quality refers to the current data transmission capability level of the cellular network, which can be characterized by indicators such as signal strength, network latency, and packet loss rate.
[0083] The method for determining the target communication mode for communicating with the vehicle terminal based on the instruction type, the communication state of the first communication mode, and the communication state of the second communication mode includes the following steps.
[0084] If the instruction type belongs to the first instruction set and the first communication mode connection status is connected, the first communication mode is determined as the target communication mode.
[0085] If the first communication mode is disconnected and the communication quality of the second communication mode meets the preset transmission conditions, the second communication mode is determined as the target communication mode.
[0086] In this embodiment, the preset transmission conditions refer to pre-set quality thresholds or combinations of conditions used to determine whether the second communication mode is sufficient to complete the instruction issuance. For example, signal strength greater than a preset threshold, network type 4G / 5G, and packet loss rate lower than a preset threshold.
[0087] In some embodiments, the method for determining the target communication mode for communicating with the vehicle terminal based on the instruction type, the communication state of the first communication mode, and the communication state of the second communication mode further includes the following steps.
[0088] If the first communication mode is disconnected and the communication quality of the second communication mode does not meet the preset transmission conditions, it is determined that there is no target communication mode that meets the requirements for transmitting vehicle control commands. A channel unavailable prompt message is generated and output to the interactive interface of the remote terminal to prompt the user to move closer to the vehicle to an area where the communication quality of the second communication mode meets the preset transmission conditions or to an area where the first communication mode is connected.
[0089] In some embodiments, while outputting prompt information, the connection status of the first channel and the communication quality of the second communication mode are continuously monitored. Once either one meets the transmission requirements, the channel decision is automatically re-executed and the vehicle control command is issued.
[0090] In this embodiment, when the instruction type belongs to the first instruction set and the first channel connection status is connected, the first communication mode is directly determined as the target communication mode. This allows the instruction to be sent via the first communication mode when it is available, making full use of its faster instruction response, which helps to shorten the response time between instruction issuance and execution and improve the immediacy of vehicle control instructions. When the first channel connection status is not connected, it is further determined whether the communication quality of the second communication mode meets the preset transmission conditions. Only when the conditions are met is the second communication mode determined as the target communication mode. This allows for automatic switching to the second communication mode as a fallback when the first communication mode is unavailable, ensuring that the instruction can still be delivered to the vehicle terminal via the second communication mode. At the same time, it avoids blindly issuing instructions when the communication quality of the second communication mode does not meet the conditions, which could lead to instruction failure.
[0091] In some embodiments, the method further includes the following steps.
[0092] After determining the target communication mode, compare the target communication mode with the current communication mode.
[0093] In this embodiment of the application, the current communication mode refers to the communication mode that the remote terminal is actually using or has already established a connection with before determining the target communication mode.
[0094] If the target communication mode is the same as the current communication mode, the vehicle control command is sent directly to the vehicle terminal through the target communication mode.
[0095] If the target communication mode is different from the current communication mode, maintain the connection of the current communication mode, send a probe command to the target communication mode, and disconnect the current communication mode after confirming that the target communication mode is available based on the response of the probe command, and send vehicle control commands to the vehicle terminal through the target communication mode.
[0096] In this embodiment of the application, the probe command refers to a test command used to verify whether the target communication mode is available. It is usually a basic command supported by Bluetooth or cellular, such as reading status, ping, etc.
[0097] Specifically, the method for comparing the target communication mode with the current communication mode includes the following steps: The remote terminal maintains a current communication mode state variable, initially set to either the first or second communication mode. After each fusion decision generates a target communication mode, this state variable is compared with the target value.
[0098] For example, the remote terminal is currently in cellular remote communication mode. When the user issues a "find car" command, the fusion decision determines that the target communication mode is Bluetooth near-field communication mode, which is different from the current communication mode. The remote terminal maintains its cellular connection and sends a probe command through the Bluetooth channel. After receiving a response from the Bluetooth channel and confirming its availability, it disconnects the cellular connection and issues a horn and flashing light command to find the car through the Bluetooth channel. The command transmission link remains active throughout the entire switching process.
[0099] In another scenario, the remote terminal is currently in Bluetooth near-field communication mode. The user continues to issue "find car" commands. At this time, the target communication mode is still Bluetooth near-field communication mode, which is the same as the current communication mode. The remote terminal directly issues commands through the Bluetooth channel without any switching operation.
[0100] In this embodiment, the channel switching execution method after the target communication mode is determined is further defined. First, the target communication mode is compared with the current communication mode. If they are the same, the vehicle control command is directly sent through the target communication mode without any switching action, avoiding unnecessary channel switching operations and their associated overhead, allowing the command to be sent and executed via the shortest path. If they are different, the connection of the current communication mode is maintained, and the vehicle control command is sent through the target communication mode only after confirming that the target communication mode is available. This avoids command loss due to channel interruption during switching, and also prevents commands from being sent to an unavailable new channel through detection and confirmation, thereby improving the success rate of remote vehicle control command execution.
[0101] In some embodiments, the method for confirming the availability of a target communication pattern based on a response to a probe command includes the following steps.
[0102] The response latency of the probe command is obtained and compared with the preset latency threshold.
[0103] If the response delay is less than the preset delay threshold, the target communication mode is confirmed to be available.
[0104] Otherwise, if the target communication mode is confirmed to be unavailable, maintain the current communication mode and send vehicle control commands to the vehicle terminal through the current communication mode.
[0105] In this embodiment, the response latency refers to the time elapsed from when the remote terminal sends a probe command to when it receives a probe response from the target communication mode. It can comprehensively reflect the current link connectivity and response timeliness of the target communication mode.
[0106] The preset latency threshold is a pre-set upper limit used to determine whether the target communication mode is available. For example, it can be set to 200 milliseconds. When the response latency is less than this threshold, the target channel link is considered to be in good condition and capable of reliably carrying vehicle control commands.
[0107] Specifically, the preset latency threshold can be set in one of the following ways: A threshold is set based on the typical round-trip delay of the probe under normal connection conditions in the first communication mode, so that the threshold is slightly higher than the normal value and significantly lower than the deterioration value.
[0108] Alternatively, by combining the statistical distribution of historical detection latency, such as taking the high percentile of recent multiple detection latency, adaptive updates can be made to adapt to the differences in Bluetooth module performance of different car models and different mobile phones.
[0109] It should be noted that the response latency calculation is completed locally on the remote terminal, without the need for additional support from the vehicle terminal. The calculation only involves the difference between the two timestamps, and the overhead is negligible.
[0110] The response latency of a remote terminal to a probe command includes one of the following: The timestamp calculation method is used. When sending a probe command, the sending timestamp is recorded, and when a response is received, the receiving timestamp is recorded. The difference between the two is the response latency.
[0111] Alternatively, a polling timing method can be used to periodically send detection commands and calculate the average response delay of multiple detections. Using the average delay as a criterion, the random fluctuations of a single measurement can be filtered out.
[0112] For example, a remote terminal switches from cellular remote communication mode to Bluetooth near-field communication mode, sends a probe command to the Bluetooth channel, and records the sending timestamp; upon receiving a probe response from the Bluetooth channel, it records the receiving timestamp, calculates the response latency to be 150 milliseconds, which is less than the preset latency threshold of 200 milliseconds, confirming that Bluetooth near-field communication mode is available, then disconnects the cellular connection and sends a vehicle-finding command through the Bluetooth channel. In another scenario, the probe response latency is calculated to be 350 milliseconds, which is not less than the preset latency threshold. The remote terminal confirms that Bluetooth near-field communication mode is unavailable, maintains the current cellular communication mode, and sends a vehicle-finding command through the cellular channel. The command sending is not interrupted due to the switching failure.
[0113] In this embodiment, the response delay of the detection command is compared with a preset delay threshold. Only when the response delay is less than the threshold is the service confirmed and the switch is executed, ensuring that the vehicle control command is transmitted with low latency after the switch. When the response delay reaches the threshold, the current communication mode is maintained and the command continues to be sent, so that the command sending path does not degrade in the case of switch failure. This avoids the user experience deterioration caused by switching to a poor channel and ensures the continuity of vehicle control services when the switch fails.
[0114] In some embodiments, the method further includes: Real-time detection of whether the connection status of the first communication mode changes.
[0115] In this embodiment of the application, real-time detection refers to the remote terminal continuously monitoring the connection status of the first communication mode through the connection status callback mechanism of the operating system's Bluetooth protocol stack.
[0116] Specifically, the remote terminal registers Bluetooth connection status callbacks. When a connection is established or disconnected, the system asynchronously pushes an event, and the remote terminal records the latest status accordingly. The real-time nature of the detection is guaranteed by the operating system's Bluetooth protocol stack; the remote terminal does not need to poll, thus incurring no additional power consumption. The callback event carries both the connection handle and the disconnection reason code, which can be used to distinguish between normal and abnormal disconnections.
[0117] If so, start timing and continuously monitor the connection status of the first communication mode within the preset anti-shake duration.
[0118] In this embodiment, the preset anti-shake duration refers to a pre-configured confirmation time window used to distinguish between instantaneous jitter and stable changes. Its value is usually much larger than the typical duration of Bluetooth instantaneous jitter (such as signal blockage or reconnection handshake) and much smaller than the time scale of stable state changes caused by actual user movement, so that a state recovery jump within the window is judged as jitter, and a state remaining unchanged when the window ends is judged as a real change.
[0119] Specifically, the preset anti-shake duration can be implemented as a fixed configuration value or as an adaptive value. In practical applications, it can be dynamically adjusted according to the historical jitter frequency of recent connection status. For example, when jitter is frequent, the window can be appropriately extended to improve the judgment strictness, and when the status is stable, the window can be appropriately shortened to improve the response speed.
[0120] Timing can be achieved through a local timer on a remote terminal or a delayed task queue; both only require checking the current state once when the window expires.
[0121] If the connection status of the first communication mode has returned to the state before the change before the preset anti-shake duration is reached, the current communication mode is maintained and vehicle control commands are sent to the vehicle terminal.
[0122] If the connection status of the first communication mode remains unchanged after the preset anti-shake duration is reached, the target communication mode is re-determined based on the instruction type, the communication status of the first communication mode, and the communication status of the second communication mode.
[0123] For example, when a user is inside a vehicle and the remote terminal is connected to the vehicle's Bluetooth module, the user passes through an area with electromagnetic interference. A brief fluctuation in the Bluetooth signal causes a momentary disconnection followed by immediate recovery. The remote terminal detects the change in connection status from connected to disconnected, starts a timer, and continues monitoring for a preset anti-shake duration. If the connection status recovers to connected within the anti-shake duration, the remote terminal determines this change to a momentary fluctuation, maintains the current Bluetooth near-field communication, continues sending commands, and does not perform a channel switch.
[0124] In another scenario, when a user gets out of the car with their phone and moves away from the vehicle, the Bluetooth connection remains disconnected. Even after the stabilization period expires, the connection status remains unconnected. The remote terminal determines this change as a real and continuous change, re-acquires the communication status, and redetermines the target communication mode based on the command type. For example, it switches the target communication mode to cellular remote communication mode to ensure that subsequent commands can still be sent normally.
[0125] In this embodiment, by introducing a combination of timing and continuous detection to determine the change in the connection state of the first channel, instantaneous jitter is distinguished from the actual state change. This avoids invalid and frequent switching caused by signal jitter and ensures timely re-decision when the channel state changes. As a result, the stability and reliability of remote vehicle control commands are further improved in a dynamically changing communication environment.
[0126] In some embodiments, reference Figure 3 The method also includes the following steps.
[0127] After sending a vehicle control command to the vehicle terminal via the target communication mode, if no command execution response is received from the vehicle terminal within the preset response time, the vehicle control command is resent within the target communication mode.
[0128] In this embodiment, the preset response time refers to the maximum time from the issuance of the command to the waiting period for the vehicle terminal to return an execution response; if the timeout occurs, it is determined as no response. The command execution response refers to the confirmation message returned by the vehicle terminal after executing the vehicle control command, indicating that the command has been received and executed.
[0129] Specifically, the remote terminal starts a timer, and if no response is received before the timeout, the command is resent.
[0130] Understandably, this step aims to address transient failures, such as brief network fluctuations or packet loss. In such cases, the failure is temporary and can be resolved by retransmitting through the same channel.
[0131] If the number of times the vehicle control command is resent within the target communication mode reaches the preset retry count and no command execution response is received, and the command type belongs to the first command set, the vehicle control command is resent through another communication channel that is not the current target communication mode.
[0132] In this embodiment, the preset number of retries is the maximum number of retries allowed within the same channel.
[0133] Understandably, the purpose of this step is to use another available channel to complete the command delivery when the current communication mode continues to malfunction. In this case, if multiple retries on the same channel fail, it indicates that the current communication mode may be continuously faulty, while the other communication mode may be normal.
[0134] If no execution response is received after switching channels and re-issuing the command, the vehicle terminal will be pre-wake up again, and the vehicle control command will be re-issued through the target communication mode.
[0135] Understandably, the purpose of this step is to resolve unresponsiveness caused by the vehicle terminal going into sleep mode. If switching channels still fails in this situation, it may be because the vehicle terminal is in sleep mode; waking it up will restore communication.
[0136] If no response is received after issuing the vehicle control command again, a command failure message will be generated.
[0137] In this embodiment of the application, the failure message is a prompt displayed to the user indicating that the vehicle control command failed to be executed successfully, such as "Command execution failed, please try again or approach the vehicle".
[0138] For example, a user issues a "start air conditioning" command in an underground parking lot. The remote terminal issues the command via the cellular channel. If no response is received within 5 seconds, the remote terminal determines that the command has failed and reissues the command via the cellular channel (first retry). If there is still no response, it is reissued again (second retry). Since the air conditioning control command is only supported by the second communication mode and does not belong to the first command set, it cannot switch to the Bluetooth channel. The remote terminal skips the channel switching retry and directly re-triggers the pre-wake-up of the vehicle terminal. After waiting for the vehicle to wake up and re-establish the connection, it issues the air conditioning command again via the cellular channel. If there is still no response, a failure message "Command execution failed, please retry or approach the vehicle" is generated and displayed to the user.
[0139] In this embodiment, after a failure is determined by a preset response time, the system first retryes within the same channel in the target communication mode, so that transient failures such as network jitter can be recovered with minimal cost within the original channel. When the retry limit for the same channel is reached and the command type can be switched, the system retryes across channels, so that persistent channel anomalies can be recovered by changing channels. At the same time, setting a threshold for command types avoids unnecessary switching of remote dedicated commands. If the cross-channel retry still fails, the vehicle terminal is pre-waked up again to ensure that a complete recovery opportunity is still obtained in abnormal vehicle scenarios. If all three levels of recovery fail, a failure prompt is generated, which significantly improves the success rate of remote vehicle control and the reliability of failure feedback.
[0140] In some embodiments, the method for pre-wake-up of the vehicle terminal includes the following steps.
[0141] Send a wake-up command to the vehicle terminal.
[0142] In this embodiment, the wake-up command refers to a trigger message used to trigger the vehicle-mounted terminal to exit sleep mode, and its implementation relies on the remote wake-up capability of the vehicle-mounted terminal. During sleep mode, the vehicle-mounted wireless terminal maintains low-power listening and can receive wake-up messages via SMS or data channels.
[0143] Specifically, the actual link to the vehicle terminal is that the remote terminal sends the wake-up request to the vehicle network service platform, and the vehicle network service platform sends the wake-up command to the target vehicle wireless terminal according to the vehicle VIN address through the SMS gateway or data push channel.
[0144] After receiving the wake-up response from the vehicle terminal in response to the wake-up command, a long connection is established with the vehicle terminal, and the vehicle terminal is placed in a ready state.
[0145] In this embodiment of the application, the wake-up response refers to the response message returned by the vehicle terminal to the vehicle network service platform after it has exited hibernation and completed initialization, which is then forwarded to the remote terminal by the vehicle network service platform.
[0146] A connection refers to a TCP (Transmission Control Protocol) connection maintained between a remote terminal and an in-vehicle terminal via a vehicle network service platform, which is not released during multiple command exchanges.
[0147] Specifically, the long connection is established by the vehicle wireless terminal actively initiating TCP connection registration with the vehicle networking service platform after being woken up. The vehicle networking service platform binds the connection to the corresponding vehicle chassis number and notifies the remote terminal. Subsequent vehicle control commands from the remote terminal reuse the registered connection channel, without the need to re-establish the connection for each command.
[0148] In this embodiment of the application, the long connection establishment process also includes an authentication step: the vehicle network service platform and the vehicle wireless terminal exchange authentication information to prevent unauthorized terminals from impersonating and accessing the network.
[0149] Before receiving a vehicle control command from the user, keep the vehicle terminal in a ready state.
[0150] For example, a user opens the remote terminal application and enters the vehicle control page on the subway. After detecting the user's intention to control the vehicle, the remote terminal sends a pre-wake-up signal to the vehicle-to-everything (V2X) service platform. The V2X service platform then sends a wake-up signal to the vehicle's onboard wireless terminal via SMS. After being woken up, the onboard wireless terminal establishes a long TCP connection with the remote terminal and returns a ready state to the remote terminal. The remote terminal then puts the onboard wireless terminal into a ready state and maintains it. After the user gets off the subway and walks near the vehicle, they click the "Find Vehicle" button on the application. Since the onboard wireless terminal is still in a ready state, the remote terminal directly sends a vehicle-finding command through the established long connection, without needing to go through the wake-up process again; the command is executed immediately.
[0151] In this embodiment, the pre-wake-up method achieves reliable forwarding of the wake-up process and continuous maintenance of the ready state through three stages: wake-up confirmation, long connection establishment, and ready maintenance. This ensures that the pre-wake-up result is real and usable, and that the ready state covers the moment when the user actually issues the command. It can eliminate the wake-up waiting delay of the first command and the secondary waiting of ready timeout, and improve the immediacy of remote vehicle control command response.
[0152] In some embodiments, the method for maintaining the vehicle terminal in a ready state includes the following steps.
[0153] The preset keep-alive window duration is determined based on the trigger duration of the user's vehicle control intent event.
[0154] In this embodiment of the application, the trigger duration refers to the duration after the user's intention to control the vehicle is triggered, that is, the time during which the user stays on the vehicle-related interface and continuously expresses the intention to control the vehicle.
[0155] The preset keep-alive window duration refers to the maximum time limit for allowing the vehicle terminal to remain in a ready state.
[0156] Specifically, the remote terminal records the timestamp of the triggered event, calculates the difference between the current time and the timestamp, and maps it to the keep-alive window duration according to preset rules.
[0157] Specifically, the preset keep-alive window duration can be set in one of the following ways: The fixed experience value method directly adopts a preset fixed keep-alive window duration (e.g., 120 seconds), which is much longer than the typical time for users to browse the vehicle control page (e.g., 10 to 30 seconds), and can cover the normal operation time of the vast majority of users.
[0158] The adaptive approach personalizes the keep-alive time based on the user's usual usage habits. For example, it analyzes the distribution of operation time from entering the vehicle control page to issuing a command in the user's historical vehicle control operations, and selects the value that covers most of the user's operation time as the keep-alive window duration. The calculation principle is: statistically analyze the user's historical operation time sample, and select the quantile value that covers a preset proportion of the sample as the keep-alive window duration, so that the window matches the user's actual operation habits.
[0159] The dynamic calculation method calculates the duration from the occurrence of the current event to the current moment in real time, and adds the reserved margin to determine the keep-alive window duration.
[0160] Based on a preset heartbeat interval, keep-alive heartbeats are continuously sent to the vehicle terminal within a preset keep-alive window duration.
[0161] In this embodiment of the application, keep-alive heartbeat refers to a lightweight liveness maintenance message that is periodically sent to maintain the ready state of the vehicle terminal. Its function is to enable the vehicle wireless terminal to periodically reset the local idle sleep timer.
[0162] The preset heartbeat interval refers to the transmission period between two adjacent heartbeats. Its value is determined by the principle that it must be much smaller than the idle sleep determination time of the vehicle wireless terminal, so that the vehicle wireless terminal can receive at least one heartbeat in any sleep determination period, thereby ensuring that the sleep timer is continuously reset.
[0163] If no vehicle control command is received from the user within the preset keep-alive window period, the vehicle terminal will return from the ready state to the sleep state.
[0164] In this embodiment, the keep-alive window duration is determined based on the trigger duration of the user's vehicle control intention event, allowing the maintenance period of the ready state to dynamically expand and contract according to the user's actual vehicle control tendency. The closer the user's behavior is to actual vehicle control, the longer the maintenance time is obtained. By continuously sending keep-alive heartbeats at preset heartbeat intervals within the window, the periodic reset of the vehicle terminal's sleep timer by the heartbeats ensures that the ready state is continuously maintained within the window, guaranteeing that the vehicle terminal is still in an executable state when the user issues commands, and eliminating the need for secondary wake-up waiting due to browsing timeout. By releasing the connection and allowing the vehicle terminal to return to sleep when no command is received after the window expires, the maintenance cost is strictly constrained within the time range within which the user may control the vehicle, improving the immediacy of remote vehicle control command response while reducing system energy consumption.
[0165] It should be noted that the steps shown in the above flowchart or the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here. For example, step S3 may be executed after step S2, or it may be executed concurrently with S2.
[0166] This embodiment also provides a vehicle control system for implementing the above embodiments and preferred embodiments, which will not be repeated hereafter. As used below, the terms "module," "unit," "subunit," etc., can refer to a combination of software and / or hardware that performs a predetermined function. Although the system described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.
[0167] Figure 4 This is a structural block diagram of the control system according to an embodiment of this application, such as... Figure 4 As shown, the system includes at least a pre-wake-up module 100, an instruction matching module 200, a first communication determination module 300, a status acquisition module 400, and a channel decision module 500.
[0168] The pre-wake-up module 100 is used to pre-wake up the vehicle's on-board terminal when a user's intent to control the vehicle is detected.
[0169] The instruction matching module 200 is used to identify the instruction type of the vehicle control instruction after receiving the vehicle control instruction issued by the user, and determine whether the instruction type belongs to the first instruction set based on the preset channel capability mapping relationship.
[0170] The first communication determination module 300 is used to determine the second communication mode as the target communication mode when the instruction type does not belong to the first instruction set.
[0171] The status acquisition module 400 is used to acquire the communication status of the current first communication mode and the communication status of the second communication mode when the instruction type belongs to the first instruction set.
[0172] The channel decision module 500 is used to determine the target communication mode for communicating with the vehicle terminal based on the instruction type, the communication status of the first communication mode, and the communication status of the second communication mode.
[0173] It should be noted that the aforementioned units can be either functional modules or program modules, and can be implemented through software or hardware. For modules implemented in hardware, these modules can reside in the same processor; or they can be located in different processors in any combination.
[0174] This application also provides a vehicle, including a controller with a communication connection. The controller is used to execute the control method described in the above embodiments.
[0175] A controller is typically an integrated electronic control module containing a microprocessor, memory, input / output interfaces, and other components. It can receive data from various sensors and systems in real time and make corresponding control decisions based on preset algorithms and logic. Controllers are generally installed in the vehicle's cockpit or engine compartment to ensure a relatively safe location that facilitates electrical connections with other vehicle systems.
[0176] The vehicle provided in this embodiment is used to execute the control method described above, and therefore can achieve the same effect as the implementation method described above.
[0177] The beneficial effects of the above embodiments can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.
[0178] In addition, combined Figure 1 The vehicle control method described in this application embodiment can be implemented by an electronic device. Figure 5 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application.
[0179] The electronic device may include a processor 51 and a memory 52 storing computer program instructions.
[0180] Specifically, the processor 51 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.
[0181] Memory 52 may include a large-capacity storage device for data or instructions. For example, and not limitingly, memory 52 may include a hard disk drive (HDD), a floppy disk drive, a solid-state drive (SSD), flash memory, an optical disk drive, a magneto-optical disk drive, magnetic tape, or a Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 42 may include removable or non-removable (or fixed) media. Where appropriate, memory 42 may be internal or external to a data processing device. In a particular embodiment, memory 42 is non-volatile memory. In a particular embodiment, memory 42 includes read-only memory (ROM) and random access memory (RAM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), an electrically alterable read-only memory (EAROM), or flash memory, or a combination of two or more of these. Where appropriate, the RAM can be Static Random-Access Memory (SRAM) or Dynamic Random-Access Memory (DRAM). DRAM can be Fast Page Mode Dynamic Random-Access Memory (FPMDRAM), Extended Data Out Dynamic Random-Access Memory (EDODRAM), Synchronous Dynamic Random-Access Memory (SDRAM), etc.
[0182] The memory 52 can be used to store or cache various data files that need to be processed and / or used for communication, as well as possible computer program instructions executed by the processor 51.
[0183] The processor 51 implements any of the vehicle control methods described in the above embodiments by reading and executing computer program instructions stored in the memory 52.
[0184] In some embodiments, the electronic device may further include a communication interface 53 and a bus 50. For example, Figure 5 As shown, the processor 51, memory 52, and communication interface 53 are connected through bus 50 and complete communication with each other.
[0185] The communication interface 53 is used to enable communication between the various modules, units, and / or devices in the embodiments of this application. The communication interface 53 can also enable data communication with other components such as external devices, image / data acquisition devices, databases, external storage, and image / data processing workstations.
[0186] The electronic device can execute the vehicle control method in the embodiments of this application based on the acquired computer program instructions.
[0187] 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.
[0188] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. 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 patent application should be determined by the appended claims.
Claims
1. A vehicle control method applied to a remote terminal, wherein the remote terminal is connected to an on-board terminal via at least a first communication mode and a second communication mode, characterized in that, The method includes: The system receives vehicle control commands issued by the user, identifies the command type of the vehicle control commands, and determines whether the command type belongs to the first command set supported by the first communication mode based on a preset channel capability mapping relationship. The channel capability mapping relationship is used to characterize the support relationship between the command type and the communication channel. The communication range of the first communication mode is smaller than the communication range of the second communication mode. If the instruction type does not belong to the first instruction set, then the second communication mode is determined as the target communication mode for communicating with the vehicle terminal; If the instruction type belongs to the first instruction set, obtain the communication status of the current first communication mode and the communication status of the second communication mode, and determine the target communication mode for communicating with the vehicle terminal based on the instruction type, the communication status of the first communication mode and the communication status of the second communication mode.
2. The control method according to claim 1, characterized in that, The step of determining whether the instruction type belongs to the first instruction set supported by the first communication mode based on a preset channel capability mapping relationship includes: If the instruction type is only supported for transmission by the second communication mode, then the instruction type is determined not to belong to the first instruction set; If the instruction type is supported for transmission by both the first communication mode and the second communication mode, then the instruction type is determined to belong to the first instruction set.
3. The control method according to claim 2, characterized in that, The communication status of the first communication mode includes the connection status of the first communication mode; the communication status of the second communication mode includes the communication quality of the second communication mode. The step of determining the target communication mode for communicating with the vehicle terminal based on the instruction type, the communication state of the first communication mode, and the communication state of the second communication mode includes: If the instruction type belongs to the first instruction set and the first communication mode connection status is connected, the first communication mode is determined as the target communication mode; If the first communication mode is disconnected and the communication quality of the second communication mode meets the preset transmission conditions, the second communication mode is determined as the target communication mode.
4. The control method according to any one of claims 1 to 3, characterized in that, The method further includes: After determining the target communication mode, the target communication mode is compared with the current communication mode; If the target communication mode is the same as the current communication mode, the vehicle control command is directly sent to the vehicle terminal through the target communication mode. If the target communication mode is different from the current communication mode, the vehicle control command is sent to the vehicle terminal through the target communication mode.
5. The control method according to claim 4, characterized in that, If the target communication mode is different from the current communication mode, it also includes: Maintain the connection of the current communication mode, send a probe command to the target communication mode, and confirm whether the target communication mode is available based on the response to the probe command; If the target communication channel is available, disconnect the current communication mode and send the vehicle control command to the vehicle terminal through the target communication mode; Otherwise, maintain the current communication mode and send the vehicle control command to the vehicle terminal through the current communication mode.
6. The control method according to claim 3, characterized in that, The method further includes: If the instruction type belongs to the first instruction set, the connection status of the first communication mode is detected in real time to see if it changes. If so, start timing and continuously detect the connection status of the first communication mode within the preset anti-shake duration; If the first communication mode connection state has been restored to the state before the timer reaches the preset anti-shake duration, the current communication mode is maintained to send the vehicle control command to the vehicle terminal. If the connection status of the first communication mode remains unchanged after the timing reaches the preset anti-shake duration, the target communication mode is re-determined based on the instruction type, the communication status of the first communication mode, and the communication status of the second communication mode.
7. The control method according to claim 1, characterized in that, The method further includes: After sending the vehicle control command to the vehicle terminal through the target communication mode, if no command execution response is received from the vehicle terminal within a preset response time, the vehicle control command is resent within the target communication mode. If the number of times the vehicle control command is resent within the target communication mode reaches the preset retry count and no command execution response is received, and the command type belongs to the first command set, the vehicle control command is resent through another communication channel that is not the current target communication mode. If no execution response is received after switching channels and re-issuing the command, the vehicle terminal will be pre-wake up again, and the vehicle control command will be re-issued through the target communication mode. If no response is received after reissuing the vehicle control command, a failure message will be generated.
8. The control method according to claim 1, characterized in that, The method further includes: In response to a detected user vehicle control intent trigger event, the vehicle terminal is pre-wake-up; The pre-wake-up process for the vehicle-mounted terminal includes: Send a wake-up command to the vehicle terminal; After receiving the wake-up response from the vehicle terminal in response to the wake-up command, a long connection is established with the vehicle terminal, and the vehicle terminal is placed in a ready state. Before receiving the vehicle control command issued by the user, the vehicle terminal is kept in the ready state.
9. The control method according to claim 8, characterized in that, Maintaining the vehicle terminal in the ready state includes: Based on the trigger duration of the user's vehicle control intention trigger event, the preset keep-alive window duration is determined; Based on a preset heartbeat interval, the keep-alive heartbeat is continuously sent to the vehicle terminal within the preset keep-alive window duration; If no vehicle control command is received from the user within the preset keep-alive window period, the vehicle terminal will return from the ready state to the sleep state.
10. A vehicle, characterized in that, include: A controller for performing the control method as described in any one of claims 1 to 9.
