A cross-system vehicle control method and device, computer equipment and storage medium

Abstract

The application belongs to the technical field of vehicle control and relates to a cross-system vehicle control method and device, computer equipment and a storage medium.The method comprises the following steps: setting a C++ public protocol layer, defining a unified message format and data type specification by the C++ public protocol layer;setting a system adaptation layer, which is used for integrating the message format and the data type specification into different operating systems and adapting to different operating systems;setting a communication layer, which is used for connecting with a vehicle, transmitting a user's control instruction to the vehicle and feeding back state information of the vehicle to the user; and setting an application layer, which provides an interactive interface of the user and the vehicle and vehicle state feedback.A set of unified rules and data formats are defined, so that different operating systems (iOS, Android and Hongmeng) can understand and process instructions and data interacting with a vehicle running program in the same way.

Description

Technical Field

[0001] This invention relates to the field of vehicle control technology, and in particular to a cross-system vehicle control method, device, computer equipment, and storage medium. Background Technology

[0002] Today, smartphone users are distributed across different operating system platforms, such as iOS, Android, and HarmonyOS. It's common for car owners to use phones with different operating systems. To provide a consistent vehicle control experience, users should be able to easily control their vehicles regardless of which operating system they use. For example, in a family, some members might use iPhones while others use Android phones, and both might want to remotely control their family vehicle, such as remotely starting the air conditioning or checking the vehicle's status.

[0003] Currently, vehicle control framework solutions on the market are all based on separate solutions for each system, with no interrelation between them. This inevitably increases development costs significantly, and handling the protocols of different systems makes inconsistencies more likely to arise.

[0004] Although there are currently multi-system control methods for vehicles, it is difficult to ensure logical consistency across different systems, which greatly increases the cost of development and maintenance. Summary of the Invention

[0005] To address the aforementioned technical problems, this invention provides a cross-system vehicle control method, employing the following technical solution, including:

[0006] Set up a C++ common protocol layer, which defines a unified message format and data type specification;

[0007] A system adaptation layer is set up, which is used to integrate the message format and the data type specification into different operating systems and adapt them for different operating systems.

[0008] A communication layer is set up, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user;

[0009] An application layer is set up, which provides the user interface for interacting with the vehicle and provides vehicle status feedback.

[0010] Preferably, the step of setting up a C++ common protocol layer, wherein the C++ common protocol layer defines a unified message format and data type specification, specifically includes:

[0011] Define a unified message format;

[0012] Standardize data types;

[0013] Set up data encryption and security mechanisms.

[0014] Preferably, the system adaptation layer is set up to integrate the message format and data type specifications into different operating systems. The specific steps for adapting to different operating systems include:

[0015] Integrate the message format and data type specifications into the iOS operating system to achieve iOS operating system adaptation;

[0016] Integrate the message format and data type specifications into the Android operating system to perform Android operating system adaptation;

[0017] The message format and data type specifications are integrated into the HarmonyOS operating system for HarmonyOS adaptation.

[0018] Preferably, the step of setting a communication layer, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user, specifically includes:

[0019] Configure a Bluetooth communication module, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user;

[0020] Configure a WiFi communication module, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user;

[0021] A 4G / 5G communication module is configured to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user.

[0022] Preferably, the step of setting up an application layer, wherein the application layer provides an interactive interface between the user and the vehicle and vehicle status feedback, specifically includes:

[0023] Set up the user interface for interacting with the vehicle;

[0024] Configure the interaction logic between the user and the vehicle.

[0025] Preferably, the step of defining a unified message format specifically includes:

[0026] Determine the message structure;

[0027] Design message encoding rules.

[0028] Preferably, the steps for standardizing data types specifically include:

[0029] Define basic data types;

[0030] Define composite data types.

[0031] To address the aforementioned technical problems, the present invention also provides a cross-system vehicle control device, which employs the following technical solution, including:

[0032] The C++ Common Protocol Layer module is used to set up the C++ Common Protocol Layer, which defines a unified message format and data type specification.

[0033] The system adaptation layer module is used to set up the system adaptation layer, which is used to integrate the message format and the data type specification into different operating systems and adapt to different operating systems.

[0034] The communication layer module is used to set up the communication layer, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user.

[0035] The application layer module is used to set up the application layer, which provides the user interface for interacting with the vehicle and provides vehicle status feedback.

[0036] To address the aforementioned technical problems, the present invention also provides a computer device that employs the technical solution described below, comprising a memory and a processor, wherein the memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the steps of the aforementioned cross-system vehicle control method.

[0037] To address the aforementioned technical problems, the present invention also provides a computer-readable storage medium, which employs the technical solution described below. The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the aforementioned cross-system vehicle control method.

[0038] Compared with the prior art, the present invention has the following main advantages:

[0039] (1) The communication methods cover a wide range of applications, and can simultaneously meet the usage scenarios of Wi-Fi, 4G network, Bluetooth, etc., giving users more choices and adapting to more usage scenarios.

[0040] (2) The scheme defines a set of unified rules and data formats, enabling different operating systems (iOS, Android, HarmonyOS) to understand and process instructions and data that interact with the vehicle's operating program in the same way.

[0041] (3) Compared with the traditional vehicle control framework, this solution has a unified protocol layer that covers three common protocols: ICCOA, ICCE, and 3C, making it more widely applicable. Attached Figure Description

[0042] To more clearly illustrate the solutions in this invention, the accompanying drawings used in the description of the embodiments of this invention will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0043] Figure 1 This is a flowchart of an embodiment of the cross-system vehicle control method of the present invention;

[0044] Figure 2 This is a schematic diagram of the structure of one embodiment of the cross-system vehicle control device of the present invention;

[0045] Figure 3 This is a schematic diagram of the structure of an embodiment of the computer device of the present invention. Detailed Implementation

[0046] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains; the terminology used herein in the specification is for the purpose of describing particular embodiments only and is not intended to limit the invention; the terms "comprising" and "having," and any variations thereof, in the specification, claims, and foregoing drawings are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the specification, claims, or foregoing drawings are used to distinguish different objects and not to describe a particular order.

[0047] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0048] To enable those skilled in the art to better understand the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings.

[0049] It should be noted that the cross-system vehicle control method provided in the embodiments of the present invention is generally executed by a server / terminal device, and correspondingly, the cross-system vehicle control device is generally set in the server / terminal device.

[0050] It should be understood that the number of terminal devices, networks, and servers is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be used.

[0051] Example 1

[0052] Please refer to Figure 1 A flowchart of an embodiment of the cross-system vehicle control method of the present invention is shown. The cross-system vehicle control method includes the following steps:

[0053] Step S1: Set up the C++ common protocol layer, which defines a unified message format and data type specification.

[0054] The C++ common protocol layer is the foundation of cross-system vehicle control methods. Its main purpose is to define a unified message format and data type, so that different operating systems (iOS, Android, HarmonyOS) can understand and process the instructions and data interacting with the vehicle's operating program in the same way, ensuring the consistency and security of data transmission between different systems.

[0055] The C++ common protocol layer can involve, but is not limited to, ICCOA, ICCE, and 3C protocols, and adapts to each protocol, including message format, data type specifications, encryption, authentication, etc.

[0056] ICCE Protocol:

[0057] ICCE (Intelligent Car Connectivity Industry Ecosystem Alliance) is an open platform jointly created by leading Chinese smart terminal and automotive manufacturers (led by Huawei). After nearly three years of development, it has become the largest industry alliance in China's connected car industry. The alliance has established two major technical standard systems: car keys and mobile phone-vehicle interconnection, and has released eight technical standards. To date, 12 OEMs and more than 20 models have commercially or are about to commercially use ICCE digital car keys, and more than 350 models are based on the ICCE open mobile phone-vehicle interconnection standard. ICCE uses a symmetric key system.

[0058] ICCOA Protocol:

[0059] The ICCOA (Intelligent Car Connectivity Open Alliance) is an open interface standard jointly developed by the International Chamber of Commerce and the Open Alliance (led by Xiaomi, Oppo, and Vivo). Its main purpose is to promote global trade and investment, and to facilitate data interaction and information sharing between different systems. The ICCOA standard provides a digital car key solution, including car key functionality and vehicle remote control capabilities, applicable to various brands and models of vehicles. Officially released and implemented on September 1, 2023, the new standard (ICCOA DK2.0) features significant upgrades and innovations compared to the first version (ICCOA DK1.2), such as added support for NFC and wearable devices.

[0060] 3C Protocol:

[0061] The 3C agreement here refers to China Compulsory Certification (CCC), or 3C certification for short. It is a product conformity assessment system implemented by the Chinese government in accordance with relevant WTO agreements and international rules to protect the safety of consumers and animals, the environment, and national security. The 3C certification mark is a basic safety certification. It aims to fundamentally resolve long-standing issues in China's product certification system, such as conflicting regulations, redundant reviews, duplicate fees, and the blurring of lines between certification and enforcement, through a comprehensive solution that includes a unified catalog, unified standards, technical regulations, conformity assessment procedures, a unified certification mark, and unified fee standards. It also seeks to establish technical regulations, standards, and conformity assessment procedures consistent with international rules, thereby promoting trade facilitation and liberalization.

[0062] In this embodiment, the electronic device (e.g., server / terminal device) on which the cross-system vehicle control method runs can receive cross-system vehicle control requests via wired or wireless connections. It should be noted that the aforementioned wireless connection methods may include, but are not limited to, 3G / 4G / 5G connections, WiFi connections, Bluetooth connections, WiMAXX connections, Zigbee connections, UWB (ultra-wideband) connections, and other currently known or future-developed wireless connection methods.

[0063] In this embodiment, step S1, setting up a C++ common protocol layer, whereby the C++ common protocol layer defines a unified message format and data type specification, may specifically include the following steps:

[0064] S11 defines a unified message format.

[0065] In this embodiment, step S11, defining a unified message format, may specifically include the following steps:

[0066] S111, determine the message structure.

[0067] A unified message format can be defined according to different protocols. The message structure includes a header (such as message type, length, checksum, and other metadata), a message body (such as control commands, vehicle status, etc.), and a trailer (such as a terminator). Additional fields can also be added as needed.

[0068] For example, message types can be divided into different types such as starting the vehicle, stopping the vehicle, adjusting the speed, and obtaining the vehicle status.

[0069] S112, Design message encoding rules.

[0070] For example, a unified encoding method (such as UTF-8) can be used to encode messages to ensure that messages can be correctly parsed across different systems.

[0071] As the foundation of the entire architecture, the C++ common protocol layer's primary task is to define a unified message format. This format should cover key components such as message headers, message bodies, and checksums to ensure message integrity and consistency during transmission across different systems. The message header contains basic information such as message type, destination address, and source address; the message body encapsulates corresponding data based on specific control commands or status feedback; and the checksum is used to verify message integrity and prevent data tampering during transmission.

[0072] S12, Standardized data type.

[0073] Determine the data types used in cross-platform communication, such as the representation and byte order of integers, floating-point numbers, strings, etc.

[0074] In this embodiment, step S12, standardizing the data type, may specifically include the following steps:

[0075] S121 defines basic data types.

[0076] Such as integer (int), floating-point (float / double), boolean (bool), etc.

[0077] S122, Define a composite data type.

[0078] Structures such as structs and enumerations are used to represent complex vehicle states or control commands.

[0079] To ensure correct data parsing and processing across different systems, the C++ common protocol layer also needs to standardize data types. This includes basic data types such as integers, floating-point numbers, strings, and booleans, as well as definitions for vehicle control-specific data types (such as vehicle speed, steering angle, and accelerator pedal position). Standardizing data types can effectively prevent parsing errors or data loss caused by data type mismatches.

[0080] It is important to note that data type consistency must be ensured. The same data type should have the same memory layout and representation across different systems.

[0081] S13, set up data encryption and security mechanisms.

[0082] In this embodiment, step S13, setting the data encryption and security mechanism, may specifically include the following steps:

[0083] S131, Select encryption algorithm.

[0084] Choose an appropriate encryption algorithm (such as AES, RSA, etc.) to encrypt messages according to security requirements to ensure communication security.

[0085] S132, Design the key management mechanism.

[0086] Ensure the secure storage and updating of keys to prevent key leakage.

[0087] S133, perform data integrity verification.

[0088] For example, a hash function (such as SHA-256) can be used to hash the message and generate a message digest, which can be used to verify the integrity of the message.

[0089] S134, perform authentication.

[0090] Implement an identity verification mechanism to prevent unauthorized control of the vehicle.

[0091] Given that vehicle control commands involve user privacy and vehicle safety, the C++ public protocol layer also needs to establish data encryption and security mechanisms. This includes using encryption algorithms to encrypt the transmission of sensitive data, and ensuring that only authorized users can send control commands through authentication, access control, and other means. The introduction of data encryption and security mechanisms provides reliable security for cross-system vehicle control.

[0092] Step S2: Set up a system adaptation layer. The system adaptation layer is used to integrate the message format and the data type specification into different operating systems and adapt them for different operating systems.

[0093] The system adaptation layer solves the compatibility issues between different operating systems, enabling applications to run smoothly on different platforms such as iOS, Android, and HarmonyOS.

[0094] The system adaptation layer sits between the upper-layer application and the lower-layer system, responsible for adapting the interfaces of different systems and exposing unified methods. The upper-layer application only needs to call the unified interface provided by the system adaptation layer, without needing to know the specific implementation of the lower-layer system.

[0095] In this embodiment, step S2 involves setting a system adaptation layer. This system adaptation layer is used to integrate the message format and data type specifications into different operating systems. Specifically, adapting to different operating systems may include the following steps:

[0096] S21, Integrate the message format and data type specifications into the iOS operating system to perform iOS operating system adaptation.

[0097] Create a C++ adapter layer: Create an Objective-C++ bridging header file. Include C++ header files in the Objective-C++ file to enable interoperability between Objective-C and C++ code.

[0098] Create an interface protocol layer: encapsulate the C++ public protocol layer interface. The interfaces in the C++ public protocol layer are encapsulated into Objective-C++ classes and methods for use by iOS applications.

[0099] Handle iOS-specific UI and event mechanisms. Design and implement the UI interface and event handling logic based on the characteristics of the iOS platform.

[0100] The primary task of the system adaptation layer is to establish interfaces between different operating systems and the C++ common protocol layer. For iOS, Objective-C++ is used as the bridge language. Objective-C++ is a hybrid programming language of Objective-C and C++, capable of calling libraries and functions from both Objective-C and C++. Through Objective-C++, iOS applications can easily call the interfaces defined by the C++ common protocol layer to encapsulate and parse data related to vehicle control.

[0101] S22, Integrate the message format and data type specifications into the Android operating system to perform Android operating system adaptation.

[0102] Create a C++ adapter layer: Create a JNI interface file. Define Java Native Interface (JNI) methods, which can be implemented in C++ code.

[0103] Create an interface protocol layer: Implement JNI methods. Implement the methods defined in the JNI interface file in C++ code to interact with the C++ common protocol layer.

[0104] Integrate Android's unique UI and event mechanisms. Design and implement the UI interface and event handling logic based on the characteristics of the Android platform.

[0105] For the Android system, Java Native Interface (JNI) is used for interaction with C++. JNI is a mechanism provided by Java for interacting with native code (such as C and C++). Through JNI, Android applications can call native methods defined in the C++ public protocol layer to send vehicle control commands and receive status feedback across platforms. The JNI-C++ adaptation method ensures that the Android system can communicate efficiently with the vehicle control system while maintaining its original development framework.

[0106] S23, Integrate the message format and data type specifications into the HarmonyOS operating system to perform HarmonyOS adaptation.

[0107] Similar to the adaptation for iOS and Android operating systems, the HarmonyOS system adaptation also created a C++ adaptation layer and an interface protocol layer.

[0108] Analyze the characteristics of the HarmonyOS platform. Understand the architecture, APIs, and event mechanisms of the HarmonyOS system.

[0109] Design a HarmonyOS adaptation solution. Based on the characteristics of the HarmonyOS platform, design an adaptation solution, including UI design, event handling, and integration methods for the C++ common protocol layer.

[0110] Implement HarmonyOS adaptation code. Write all the adaptation code for the HarmonyOS platform to ensure that applications can run normally on the HarmonyOS system.

[0111] HarmonyOS, Huawei's next-generation smart terminal operating system, requires adaptation methods designed in conjunction with its characteristics and development framework. HarmonyOS supports multiple programming languages ​​(such as C, C++, Java, JavaScript, etc.) and provides a rich set of system APIs. At the system adaptation layer, seamless integration with the C++ common protocol layer can be achieved by encapsulating HarmonyOS-specific API interfaces. This allows applications running on HarmonyOS to easily send vehicle control commands and receive status feedback.

[0112] Step S3: Set up a communication layer, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user.

[0113] The communication layer is responsible for data transmission between the vehicle control system and mobile devices. It establishes the actual connection to the vehicle and transmits data via communication methods such as Bluetooth, WiFi, and 4G / 5G.

[0114] In this embodiment, step S3, setting up a communication layer, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user, may specifically include the following steps:

[0115] S31, Configure a Bluetooth communication module, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user.

[0116] Configure Bluetooth devices. Configure Bluetooth devices on both the vehicle and mobile devices to ensure they can discover each other and establish a connection.

[0117] Implement the Bluetooth communication protocol. Based on Bluetooth communication standards (such as SPP, BLE, etc.), implement the logic for data transmission and reception.

[0118] Handle Bluetooth connection status changes. Monitor changes in Bluetooth connection status, such as connection establishment and disconnection, and take appropriate action.

[0119] Setting a unified key in the Bluetooth communication module facilitates data access across systems.

[0120] Bluetooth communication modules, as a short-range wireless communication technology, are characterized by low power consumption and ease of pairing and connection. In cross-system vehicle control methods, Bluetooth communication modules can be used to achieve short-range communication between mobile devices and vehicles. Through Bluetooth communication modules, users can quickly connect to the vehicle and send control commands, while simultaneously receiving vehicle status feedback.

[0121] S32, Configure a WiFi communication module, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user.

[0122] Configure the WiFi network. Configure the WiFi network on both the vehicle and your mobile device, ensuring they can connect to the same WiFi hotspot.

[0123] Implement Socket communication. Use Socket programming to transmit data between the vehicle and the mobile device.

[0124] Handle network status changes. Monitor for changes in network status, such as network disconnection or reconnection, and take appropriate action.

[0125] Set a unified key in the WiFi communication module to facilitate data access across systems.

[0126] WiFi communication modules, as a long-range wireless communication technology, offer advantages such as high transmission speed and wide coverage. In cross-system vehicle control methods, WiFi communication modules can be used to enable remote communication between mobile devices and vehicles. Through WiFi communication modules, users can remotely control vehicles from anywhere with WiFi network coverage, greatly enhancing the user experience.

[0127] S33, Configure a 4G / 5G communication module, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user.

[0128] Configure 4G / 5G network. Ensure that both the vehicle and mobile devices can access the 4G / 5G network.

[0129] Implement HTTP / HTTPS communication. Utilize the HTTP / HTTPS protocol to transmit data between the vehicle and mobile devices, ensuring data security.

[0130] Handle network anomalies. Address network latency, packet loss, and other abnormal situations to ensure reliable data transmission.

[0131] A unified key is set in the 4G / 5G communication module to facilitate data access across systems.

[0132] As a type of mobile communication technology, 4G / 5G communication modules feature high-speed data transmission and wide network coverage. In cross-system vehicle control methods, 4G / 5G communication modules can be used to achieve real-time communication between mobile devices and vehicles. Through 4G / 5G communication modules, users can obtain vehicle status information and send control commands anytime, anywhere, improving the real-time performance and convenience of vehicle control.

[0133] Step S4: Set up the application layer, which provides the user interface for interacting with the vehicle and provides vehicle status feedback.

[0134] The application layer provides a user interface and status feedback, enabling users to intuitively control the vehicle and receive vehicle status information.

[0135] In this embodiment, step S4, setting up the application layer, which provides the user's interaction interface with the vehicle and vehicle status feedback, may specifically include the following steps:

[0136] S41 sets up the user interface for interacting with the vehicle.

[0137] Design an intuitive and easy-to-use UI interface based on user needs, including vehicle control buttons, status display areas, etc.

[0138] S42 sets the interaction logic between the user and the vehicle.

[0139] Implement corresponding UI interaction logic based on user actions, such as sending control commands when clicking a button, and receiving vehicle status updates in the UI.

[0140] As the interface between the user and the vehicle control system, the application layer's design directly impacts the user experience and satisfaction. The application page layer is responsible for providing an intuitive and user-friendly interface, enabling users to quickly get started and conveniently control the vehicle. Various control buttons, sliders, switches, and other controls can be designed within the application page layer to send different vehicle control commands. Simultaneously, the application page layer must also display real-time vehicle status information (such as speed, fuel level, and door status) so that users can stay informed about the vehicle's condition.

[0141] In some optional implementations of this embodiment, UI performance can also be optimized. The UI interface can be optimized to improve responsiveness and smoothness.

[0142] In some optional implementations of this embodiment, step S4 may also include setting user access cost reduction strategies. For example, providing a one-click installation / update function. This reduces the cost of installing and updating applications for users. It also ensures multi-platform compatibility, guaranteeing that the application can run normally on different platforms such as iOS, Android, and HarmonyOS without requiring additional configuration or operation from the user. Finally, it provides user guides and help documentation to help users quickly get started and use the application.

[0143] To ensure convenient cross-system vehicle control, the application layer also needs to address user access costs. By adopting a unified user authentication mechanism and data synchronization strategy, seamless switching between devices running different operating systems can be ensured without repeatedly entering authentication information or resetting vehicle control parameters. Furthermore, the application layer can provide comprehensive help documentation and online support services so that users can quickly resolve any issues they encounter during use.

[0144] In this embodiment, the interaction principle between the C++ common protocol layer, system adaptation layer, communication layer, and application layer is as follows:

[0145] The relationship and interaction between the C++ common protocol layer and the system adaptation layer: The relationship between the C++ common protocol layer and the system adaptation layer is mainly reflected in interface docking. The C++ common protocol layer defines a unified message format and data type specification, while the system adaptation layer is responsible for interfacing these specifications with the development frameworks of different operating systems. By encapsulating the interface functions defined by the C++ common protocol layer, the system adaptation layer implements the encapsulation and parsing of cross-platform vehicle control commands. During the interaction, the system adaptation layer converts user operations into message formats conforming to the C++ common protocol layer specification and sends them to the C++ common protocol layer for processing; simultaneously, the system adaptation layer is also responsible for receiving status feedback messages returned by the C++ common protocol layer and converting them into the corresponding operating system's representation for display to the user.

[0146] The relationship and interaction between the C++ common protocol layer and the communication layer: The main connection between the C++ common protocol layer and the communication layer is in data transmission. The C++ common protocol layer defines a unified data format and encryption mechanism, while the communication layer is responsible for transmitting this data to the vehicle control system via different communication methods (such as Bluetooth, WiFi, 4G, etc.). During the interaction, the C++ common protocol layer passes encapsulated control commands or status request messages to the communication layer for transmission; simultaneously, the communication layer is also responsible for receiving status feedback messages returned by the vehicle control system and passing them to the C++ common protocol layer for parsing and processing.

[0147] The connection and interaction between the system adaptation layer and the application layer: The connection between the system adaptation layer and the application layer is mainly reflected in the user interface and data display. The system adaptation layer is responsible for converting the data passed from the C++ common protocol layer into the corresponding operating system's representation and displaying it on the application page layer for users to view and interact with. During the interaction, the application page layer receives user operation commands and passes them to the system adaptation layer for processing; at the same time, the application page layer is also responsible for receiving status feedback data from the system adaptation layer and displaying it to the user in an intuitive way.

[0148] The connection and interaction between the communication layer and the application layer (indirectly through the C++ common protocol layer and system adaptation layer): Although the communication layer and the application layer do not interact directly, they are indirectly connected and interact through the C++ common protocol layer and the system adaptation layer. The communication layer is responsible for sending the control commands passed from the application layer through the system adaptation layer and the C++ common protocol layer to the vehicle control system; at the same time, the communication layer is also responsible for passing the status feedback messages returned by the vehicle control system to the application layer for display through the C++ common protocol layer and the system adaptation layer. This indirect connection and interaction method ensures the stability and reliability of the cross-system vehicle control method.

[0149] The working principle of the cross-system vehicle control method in this embodiment is as follows:

[0150] (1) User operations:

[0151] Users send vehicle control commands or request vehicle status information through controls on the application's page layer (such as buttons, sliders, etc.). These commands are encapsulated into message formats that conform to the C++ common protocol layer specification.

[0152] (2) System adaptation and protocol conversion:

[0153] The system adaptation layer receives operation instructions from the application page layer and converts them into the corresponding operating system's representation (such as Objective-C++ objects under iOS or JNI calls under Android). Then, the system adaptation layer passes these operation instructions to the C++ public protocol layer for further encapsulation and encryption.

[0154] (3) Data transmission:

[0155] The C++ common protocol layer passes the encapsulated control commands or status request messages to the communication layer for transmission. The communication layer selects an appropriate communication method (such as Bluetooth, WiFi, or 4G) based on the current network environment and user needs to transmit the messages to the vehicle control system.

[0156] (4) Vehicle control and handling:

[0157] The vehicle control system receives control commands or status request messages from the communication layer and executes corresponding operations or returns corresponding status information based on the commands. This status information is also encapsulated into a message format conforming to the C++ common protocol layer specification and sent back to the communication layer.

[0158] (5) Data analysis and presentation:

[0159] The communication layer passes the received status feedback messages to the C++ common protocol layer for decryption and parsing. Then, the C++ common protocol layer passes this status information to the system adaptation layer for further format conversion and encapsulation. Finally, the system adaptation layer displays this status information on the application page layer for user viewing.

[0160] (6) Real-time updates and feedback:

[0161] Throughout the process, the application page layer updates and displays the vehicle's status information to the user in real time, allowing the user to understand the vehicle's condition and make corresponding adjustments. Simultaneously, the application page layer also sends control commands to the vehicle control system in real time based on the user's input, enabling convenient vehicle control.

[0162] As can be seen, this embodiment unifies communication standards through the C++ common protocol layer, solves compatibility issues between different systems through the system adaptation layer, realizes the actual connection with the vehicle through the communication layer, and provides user operation interface and status feedback through the application layer. The cross-system vehicle control system can achieve compatibility and interoperability with different operating systems, providing users with a convenient and fast vehicle control experience.

[0163] The beneficial effects of implementing this embodiment are:

[0164] (1) The communication methods cover a wide range of applications, and can simultaneously meet the usage scenarios of Wi-Fi, 4G network, Bluetooth, etc., giving users more choices and adapting to more usage scenarios.

[0165] (2) The scheme defines a set of unified rules and data formats, enabling different operating systems (iOS, Android, HarmonyOS) to understand and process instructions and data that interact with the vehicle's operating program in the same way.

[0166] (3) Compared with the traditional vehicle control framework, this solution has a unified protocol layer that covers three common protocols: ICCOA, ICCE, and 3C, making it more widely applicable.

[0167] This invention can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This invention can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This invention can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0168] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing related hardware with computer-readable instructions. These computer-readable instructions can be stored in a computer-readable storage medium. When executed, the program can include the processes of the embodiments of the above methods. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, optical disk, or read-only memory (ROM), or random access memory (RAM).

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

[0170] Example 2

[0171] Further reference Figure 2 As a response to the above Figure 1 The present invention provides an embodiment of a cross-system vehicle control device, which is implemented in accordance with the method shown. Figure 1 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0172] like Figure 2 As shown, the cross-system vehicle control device 50 described in this embodiment includes: a C++ common protocol layer module 51, a system adaptation layer module 52, a communication layer module 53, and an application layer module 54. Wherein:

[0173] C++ Common Protocol Layer Module 51 is used to set up the C++ Common Protocol Layer, which defines a unified message format and data type specification.

[0174] The system adaptation layer module 52 is used to set up the system adaptation layer, which is used to integrate the message format and the data type specification into different operating systems and adapt to different operating systems.

[0175] The communication layer module 53 is used to set up a communication layer, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user.

[0176] Application layer module 54 is used to set up the application layer, which provides the user interface for interacting with the vehicle and vehicle status feedback.

[0177] The beneficial effects of implementing this embodiment are:

[0178] (1) The communication methods cover a wide range of applications, and can simultaneously meet the usage scenarios of Wi-Fi, 4G network, Bluetooth, etc., giving users more choices and adapting to more usage scenarios.

[0179] (2) The scheme defines a set of unified rules and data formats, enabling different operating systems (iOS, Android, HarmonyOS) to understand and process instructions and data that interact with the vehicle's operating program in the same way.

[0180] (3) Compared with the traditional vehicle control framework, this solution has a unified protocol layer that covers three common protocols: ICCOA, ICCE, and 3C, making it more widely applicable.

[0181] Example 3

[0182] To address the aforementioned technical problems, embodiments of the present invention also provide a computer device. Please refer to [link / reference needed]. Figure 3 , Figure 3 This is a basic structural block diagram of the computer device in this embodiment.

[0183] The aforementioned computer device 6 includes a memory 61, a processor 62, and a network interface 63 that are interconnected via a system bus. It should be noted that the figure only shows a computer device 6 with components 61, 62, and 63; however, it should be understood that it is not required to implement all the shown components, and more or fewer components can be implemented alternatively. Those skilled in the art will understand that the computer device described here is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0184] The aforementioned computer devices can be desktop computers, laptops, handheld computers, and cloud servers, among other computing devices. These devices can facilitate human-computer interaction with users through keyboards, mice, remote controls, touchpads, or voice-activated devices.

[0185] The aforementioned memory 61 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the aforementioned memory 61 may be an internal storage unit of the aforementioned computer device 6, such as the hard disk or memory of the computer device 6. In other embodiments, the aforementioned memory 61 may also be an external storage device of the aforementioned computer device 6, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 6. Of course, the aforementioned memory 61 may also include both the internal storage unit and its external storage device of the aforementioned computer device 6. In this embodiment, the aforementioned memory 61 is typically used to store the operating system and various application software installed on the aforementioned computer device 6, such as computer-readable instructions for cross-system vehicle control methods. In addition, the aforementioned memory 61 can also be used to temporarily store various types of data that have been output or will be output.

[0186] In some embodiments, the processor 62 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. The processor 62 is typically used to control the overall operation of the computer device 6. In this embodiment, the processor 62 is used to execute computer-readable instructions stored in the memory 61 or to process data, for example, to execute the computer-readable instructions of the cross-system vehicle control method described above.

[0187] The network interface 63 may include a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the computer device 6 and other electronic devices.

[0188] The beneficial effects of implementing this embodiment are:

[0189] (1) The communication methods cover a wide range of applications, and can simultaneously meet the usage scenarios of Wi-Fi, 4G network, Bluetooth, etc., giving users more choices and adapting to more usage scenarios.

[0190] (2) The scheme defines a set of unified rules and data formats, enabling different operating systems (iOS, Android, HarmonyOS) to understand and process instructions and data that interact with the vehicle's operating program in the same way.

[0191] (3) Compared with the traditional vehicle control framework, this solution has a unified protocol layer that covers three common protocols: ICCOA, ICCE, and 3C, making it more widely applicable.

[0192] Example 4

[0193] The present invention also provides another embodiment, namely, providing a computer-readable storage medium storing computer-readable instructions that can be executed by at least one processor to cause the at least one processor to perform the steps of the cross-system vehicle control method as described above.

[0194] The beneficial effects of implementing this embodiment are:

[0195] (1) The communication methods cover a wide range of applications, and can simultaneously meet the usage scenarios of Wi-Fi, 4G network, Bluetooth, etc., giving users more choices and adapting to more usage scenarios.

[0196] (2) The scheme defines a set of unified rules and data formats, enabling different operating systems (iOS, Android, HarmonyOS) to understand and process instructions and data that interact with the vehicle's operating program in the same way.

[0197] (3) Compared with the traditional vehicle control framework, this solution has a unified protocol layer that covers three common protocols: ICCOA, ICCE, and 3C, making it more widely applicable.

[0198] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods of the various embodiments of the present invention.

[0199] Obviously, the embodiments described above are merely some embodiments of the present invention, not all embodiments. The accompanying drawings show preferred embodiments of the present invention, but do not limit the patent scope of the present invention. The present invention can be implemented in many different forms; rather, these embodiments are provided to provide a more thorough and complete understanding of the disclosure of the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or make equivalent substitutions for some of the technical features. Any equivalent structures made using the content of this specification and drawings, directly or indirectly applied to other related technical fields, are similarly within the patent protection scope of this invention.

Claims

1. A cross-system vehicle control method, characterized in that, Includes the following steps: Set up a C++ common protocol layer, which defines a unified message format and data type specification; A system adaptation layer is set up, which is used to integrate the message format and the data type specification into different operating systems and adapt them for different operating systems. A communication layer is set up, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user; An application layer is set up, which provides the user interface for interacting with the vehicle and provides vehicle status feedback.

2. The cross-system vehicle control method according to claim 1, characterized in that, The steps of setting up the C++ common protocol layer, which defines a unified message format and data type specification, specifically include: Define a unified message format; Standardize data types; Set up data encryption and security mechanisms.

3. The cross-system vehicle control method according to claim 1, characterized in that, The system adaptation layer is configured to integrate the message format and data type specifications into different operating systems. The specific steps for adapting to different operating systems include: Integrate the message format and data type specifications into the iOS operating system to achieve iOS operating system adaptation; Integrate the message format and data type specifications into the Android operating system to perform Android operating system adaptation; The message format and data type specifications are integrated into the HarmonyOS operating system for HarmonyOS adaptation.

4. The cross-system vehicle control method according to claim 1, characterized in that, The steps of setting up a communication layer, which is used to connect with the vehicle, transmit user control commands to the vehicle, and feed back vehicle status information to the user, specifically include: Configure a Bluetooth communication module, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user; Configure a WiFi communication module, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user; A 4G / 5G communication module is configured to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user.

5. The cross-system vehicle control method according to claim 1, characterized in that, The steps of setting up the application layer, which provides the user interface and vehicle status feedback, specifically include: Set up the user interface for interacting with the vehicle; Configure the interaction logic between the user and the vehicle.

6. The cross-system vehicle control method according to claim 2, characterized in that, The steps for defining a unified message format specifically include: Determine the message structure; Design message encoding rules.

7. The cross-system vehicle control method according to claim 2, characterized in that, The steps for standardizing data types specifically include: Define basic data types; Define composite data types.

8. A cross-system vehicle control device, characterized in that, include: The C++ Common Protocol Layer module is used to set up the C++ Common Protocol Layer, which defines a unified message format and data type specification. The system adaptation layer module is used to set up the system adaptation layer, which is used to integrate the message format and the data type specification into different operating systems and adapt to different operating systems. The communication layer module is used to set up the communication layer, which is used to connect with the vehicle, transmit the user's control commands to the vehicle, and feed back the vehicle's status information to the user. The application layer module is used to set up the application layer, which provides the user interface for interacting with the vehicle and provides vehicle status feedback.

9. A computer device comprising a memory and a processor, the memory storing computer-readable instructions, wherein the processor, when executing the computer-readable instructions, implements the steps of the cross-system vehicle control method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions that, when executed by a processor, implement the steps of the cross-system vehicle control method as described in any one of claims 1 to 7.

Images