Remote vehicle control method and device based on a hon gming system, storage medium, and electronic device

Abstract

The application provides a remote vehicle control method and device based on a Hongmeng system, a storage medium and an electronic device, and the method comprises the following steps: receiving a first remote vehicle control request for a first vehicle through a remote vehicle control application of a target mobile terminal, wherein the target mobile terminal runs a Hongmeng operating system, the Hongmeng operating system loads the remote vehicle control application, and the remote vehicle control application is bound to multiple vehicles; identifying a domain control platform type of the first vehicle, wherein the domain control platform type is used for representing a remote vehicle control mode of the first vehicle; and performing a remote vehicle control operation on the first vehicle according to the domain control platform type and the first remote vehicle control request. Through the embodiment, the technical problem that the application development efficiency is low because each domain control platform type develops a remote vehicle control application in the prior art is solved, and the development cost and maintenance difficulty of the remote vehicle control application are reduced.

Description

Technical Field

[0001] This invention relates to the field of vehicle technology, and more specifically, to a remote vehicle control method and device, storage medium, and electronic device based on the HarmonyOS system. Background Technology

[0002] Among related technologies, with the rapid development of the intelligent connected vehicle industry, technologies such as mobile phone vehicle control and vehicle-to-everything (V2X) connectivity are becoming increasingly mature. Huawei's HarmonyOS, as a new generation of intelligent terminal operating system, provides a solid technological foundation for vehicle control applications.

[0003] However, in practical applications, different models of the same car brand (such as SDA and CIIA models) use different vehicle control SDKs (Software Development Kits). These SDKs suffer from inconsistencies in interfaces, data formats, and communication protocols, requiring applications to develop adaptation code for different models, increasing development costs and maintenance complexity. Furthermore, the coexistence of multiple heterogeneous SDKs within the same application presents pressing technical challenges, such as how to achieve unified scheduling and avoid resource management conflicts.

[0004] No efficient and accurate solution has yet been found to address the aforementioned issues in the relevant technologies. Summary of the Invention

[0005] This invention provides a remote vehicle control method and device, storage medium, and electronic device based on the HarmonyOS system to solve technical problems in related technologies.

[0006] According to an embodiment of the present invention, a remote vehicle control method based on the HarmonyOS system is provided, comprising: receiving a first remote vehicle control request for a first vehicle through a remote vehicle control application of a target mobile terminal, wherein the target mobile terminal runs the HarmonyOS operating system, the HarmonyOS operating system loads the remote vehicle control application, and the remote vehicle control application is bound to multiple vehicles; identifying the domain control platform type of the first vehicle, wherein the domain control platform type is used to characterize the remote vehicle control method of the first vehicle; and performing remote vehicle control operations on the first vehicle according to the domain control platform type and the first remote vehicle control request.

[0007] Optionally, performing remote vehicle control operations on the first vehicle according to the domain control platform type and the first remote vehicle control request includes: extracting the first vehicle control SDK identifier from the first remote vehicle control request; searching for a target software development kit (SDK) matching the first vehicle control SDK identifier in the middleware factory module of the remote vehicle control application; calling the SDK interface instance of the first vehicle control SDK; converting the first remote vehicle control request into a specific format request matching the first vehicle control SDK; and performing remote vehicle control operations on the first vehicle using the SDK interface instance and the specific format request.

[0008] Optionally, performing remote vehicle control operations on the first vehicle using the SDK interface instance and the specific format request includes: sending the specific format request to the first vehicle using the SDK interface instance; receiving vehicle control result information returned by the first vehicle based on the specific format request through a callback of the SDK interface instance; converting the internal data format of the vehicle control result information into target result information in the unified user data format of the remote vehicle control application; and displaying the target result information on the remote vehicle control interface of the first vehicle in the remote vehicle control application.

[0009] Optionally, after converting the internal data format of the vehicle control result information into the target result information in the unified user data format of the remote vehicle control application, the method further includes: searching for a second SDK associated with the first vehicle control SDK in the preset event bus of the remote vehicle control application; calling the event transmitter of the HarmonyOS operating system; and using the event transmitter to transmit the target result information to the second SDK.

[0010] Optionally, identifying the domain control platform type of the first vehicle includes at least one of the following: identifying the software-defined vehicle (SDA) domain control platform type of the first vehicle; identifying the CIIA domain control platform type of the first vehicle; identifying the third-party domain control platform type of the first vehicle.

[0011] Optionally, before receiving the first remote vehicle control request for the first vehicle through the remote vehicle control application on the target mobile terminal, the method further includes: launching the remote vehicle control application on the target mobile terminal; loading multiple adapters in the middleware factory module of the remote vehicle control application; registering a vehicle control SDK of a domain control platform type for each of the multiple adapters; and configuring a unified user data format for the remote vehicle control application.

[0012] Optionally, after receiving a first remote vehicle control request for a first vehicle through the remote vehicle control application of the target mobile terminal, the method further includes: receiving a second remote vehicle control request for a second vehicle through the remote vehicle control application of the target mobile terminal; determining the priorities of the first remote vehicle control request and the second remote vehicle control request; if the priority of the first remote vehicle control request is greater than the priority of the second remote vehicle control request, switching the first vehicle control SDK currently running in the remote vehicle control application to a second vehicle control SDK that matches the second vehicle; if the priority of the first remote vehicle control request is less than or equal to the priority of the second remote vehicle control request, refusing to respond to the second remote vehicle control request.

[0013] According to another embodiment of the present invention, a remote vehicle control device based on the HarmonyOS system is provided, comprising: a first receiving module, configured to receive a first remote vehicle control request for a first vehicle through a remote vehicle control application of a target mobile terminal, wherein the target mobile terminal runs the HarmonyOS operating system, the HarmonyOS operating system loads the remote vehicle control application, and the remote vehicle control application is bound to multiple vehicles; an identification module, configured to identify the domain control platform type of the first vehicle, wherein the domain control platform type is used to characterize the remote vehicle control method of the first vehicle; and a control module, configured to perform remote vehicle control operations on the first vehicle according to the domain control platform type and the first remote vehicle control request.

[0014] Optionally, the control module includes: an extraction unit for extracting a first vehicle control SDK identifier from the first remote vehicle control request; a search unit for searching for a target software development kit (SDK) matching the first vehicle control SDK identifier in the middleware factory module of the remote vehicle control application; a calling unit for calling an SDK interface instance of the first vehicle control SDK; a conversion unit for converting the first remote vehicle control request into a specific format request matching the first vehicle control SDK; and a control unit for performing remote vehicle control operations on the first vehicle using the SDK interface instance and the specific format request.

[0015] Optionally, the control unit includes: a sending subunit, configured to send the specific format request to the first vehicle using the SDK interface instance; a receiving subunit, configured to receive vehicle control result information returned by the first vehicle based on the specific format request through a callback of the SDK interface instance; a conversion subunit, configured to convert the internal data format of the vehicle control result information into target result information in the unified user data format of the remote vehicle control application; and a display subunit, configured to display the target result information on the remote vehicle control interface of the first vehicle in the remote vehicle control application.

[0016] Optionally, the control unit further includes: a lookup subunit, used to look up a second SDK associated with the first vehicle control SDK in a preset event bus of the remote vehicle control application after the conversion subunit converts the internal data format of the vehicle control result information into the target result information in the unified user data format of the remote vehicle control application; a retrieval subunit, used to retrieve the event transmitter of the HarmonyOS operating system; and a transmission subunit, used to transmit the target result information to the second SDK using the event transmitter.

[0017] Optionally, the identification module includes at least one of the following: a first identification unit for identifying the software-defined vehicle (SDA) domain control platform type of the first vehicle; a second identification unit for identifying the CIIA domain control platform type of the first vehicle; and a third identification unit for identifying the third-party domain control platform type of the first vehicle.

[0018] Optionally, the device further includes: a startup module, configured to start the remote vehicle control application on the target mobile terminal before the first receiving module receives the first remote vehicle control request for the first vehicle through the remote vehicle control application of the target mobile terminal; a loading module, configured to load multiple adapters in the middleware factory module of the remote vehicle control application; a registration module, configured to register a domain control platform type vehicle control SDK for each of the multiple adapters; and a configuration module, configured to configure a unified user data format for the remote vehicle control application.

[0019] Optionally, the device further includes: a second receiving module, configured to receive a second remote vehicle control request for a second vehicle through the remote vehicle control application of the target mobile terminal after the first receiving module receives a first remote vehicle control request for a first vehicle through the remote vehicle control application of the target mobile terminal; a determining module, configured to determine the priority of the first remote vehicle control request and the second remote vehicle control request; and a processing module, configured to, if the priority of the first remote vehicle control request is greater than the priority of the second remote vehicle control request, switch the first vehicle control SDK currently running in the remote vehicle control application to a second vehicle control SDK matching the second vehicle; and if the priority of the first remote vehicle control request is less than or equal to the priority of the second remote vehicle control request, refuse to respond to the second remote vehicle control request.

[0020] According to another aspect of the embodiments of this application, a storage medium is also provided, the storage medium including a stored program that executes the above steps when the program is run.

[0021] According to another aspect of the embodiments of this application, an electronic device is also provided, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; wherein: the memory is used to store computer programs; and the processor is used to execute the steps in the above method by running the programs stored in the memory.

[0022] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the steps in the above-described method.

[0023] The beneficial effects of this invention are: 1. Unified Interface Standard: Different types of vehicle control SDKs provide services to the outside world through a unified interface, simplifying the development of the application layer; 2. Dynamic adaptation mechanism: The system supports dynamic registration and loading of new SDKs, which is highly extensible and can support new vehicle model SDKs without modifying the application code; 3. Factory Pattern Management: The factory pattern is used to manage SDK instances in a unified manner, which improves the maintainability and scalability of the code; 4. Unified scheduling strategy: An effective scheduling mechanism ensures the coordinated operation of multiple SDKs and avoids resource conflicts; 5. Event-driven architecture: Based on an event bus-based loosely coupled communication mechanism, it improves the system's flexibility and maintainability; 6. Unified data processing: The data conversion layer handles data of different formats in a unified manner, simplifying the data processing logic. Attached Figure Description

[0024] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings: Figure 1 This is a hardware structure block diagram of a mobile phone according to an embodiment of the present invention; Figure 2 This is a flowchart of a remote vehicle control method based on the HarmonyOS system according to an embodiment of the present invention; Figure 3 This is a flowchart of the middleware factory module in an embodiment of the present invention; Figure 4 This is a system architecture diagram of an embodiment of the present invention; Figure 5 This is a flowchart of the vehicle control request processing in an embodiment of the present invention; Figure 6 This is a structural block diagram of a remote vehicle control device based on the HarmonyOS system according to an embodiment of the present invention. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, and not all of them. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present application. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of the present application can be combined with each other.

[0026] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] Example 1 The method embodiment provided in Embodiment 1 of this application can be executed in a mobile phone, tablet, smart terminal, computer, or similar processing device. Taking its operation on a mobile phone as an example, Figure 1 This is a hardware structure block diagram of a mobile phone according to an embodiment of the present invention. For example... Figure 1 As shown, a mobile phone may include one or more ( Figure 1 Only one is shown in the image. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. Optionally, the mobile phone may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile phone described above. For example, the mobile phone may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0028] The memory 104 can be used to store mobile phone programs, such as application software programs and modules, like the mobile phone program corresponding to a remote vehicle control method based on the HarmonyOS system in an embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the mobile phone program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile phone via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0029] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile phone's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0030] This embodiment provides a remote vehicle control method based on the HarmonyOS system. Figure 2 This is a flowchart of a remote vehicle control method based on the HarmonyOS system according to an embodiment of the present invention, such as... Figure 2 As shown, the process includes the following steps: Step S201: Receive a first remote vehicle control request for the first vehicle through the remote vehicle control application of the target mobile terminal, wherein the target mobile terminal runs the HarmonyOS operating system, the HarmonyOS operating system loads the remote vehicle control application, and the remote vehicle control application is bound to multiple vehicles; The target mobile terminal in this embodiment can be a user terminal such as a mobile phone or tablet.

[0031] Step S202: Identify the domain control platform type of the first vehicle, wherein the domain control platform type is used to characterize the remote vehicle control method of the first vehicle; Optionally, identifying the domain control platform type of the first vehicle includes at least one of the following: identifying the software-defined vehicle (SDA) domain control platform type of the first vehicle; identifying the CIIA domain control platform type of the first vehicle; identifying the third-party domain control platform type of the first vehicle.

[0032] Optionally, the domain control platform type of the first vehicle can be identified based on the vehicle identifier or SDK identifier carried in the first remote vehicle control request, or the domain control platform type of the vehicle model can be found by identifying the model of the currently selected vehicle in the remote vehicle control application.

[0033] Step S203: Perform remote vehicle control operation on the first vehicle according to the domain control platform type and the first remote vehicle control request.

[0034] Through the above steps, a first remote vehicle control request for a first vehicle is received through the remote vehicle control application of the target mobile terminal. The target mobile terminal runs the HarmonyOS operating system, which loads the remote vehicle control application, which is bound to multiple vehicles. The domain control platform type of the first vehicle is identified, where the domain control platform type characterizes the remote vehicle control method of the first vehicle. Based on the domain control platform type and the first remote vehicle control request, a remote vehicle control operation is performed on the first vehicle. This integrates the remote vehicle control functions of models developed by the same vehicle manufacturer based on multiple domain control platform types into a single application, achieving unified management and scheduling of multiple heterogeneous vehicle control SDKs. This solves the technical problem of low application development efficiency caused by developing a separate remote vehicle control application for each domain control platform type in the prior art, and reduces the development cost and maintenance difficulty of remote vehicle control applications.

[0035] In one embodiment of this example, performing a remote vehicle control operation on the first vehicle based on the domain control platform type and the first remote vehicle control request includes: extracting a first vehicle control SDK identifier from the first remote vehicle control request; searching for a target software development kit (SDK) matching the first vehicle control SDK identifier in the middleware factory module of the remote vehicle control application; calling an SDK interface instance of the first vehicle control SDK; converting the first remote vehicle control request into a specific format request matching the first vehicle control SDK; and performing a remote vehicle control operation on the first vehicle using the SDK interface instance and the specific format request.

[0036] When an application initiates a vehicle control request, it receives the request through a unified interface layer. The unified scheduling module analyzes the request type, determines the target SDK, and the middleware factory module obtains the corresponding SDK interface instance based on the target SDK name. The adaptation layer then converts the application request into a request in a specific SDK format.

[0037] Figure 3This is a flowchart of the middleware factory module in this embodiment of the invention. The middleware factory module maintains a Map collection, with SDK names as keys and SDK interface instances as values; it provides a registration method to register SDK interface instances to the factory; it provides a retrieval method to retrieve the corresponding interface instance based on the SDK name; and it provides a singleton instance retrieval method to ensure that there is only one factory instance in the entire system. The process includes: system startup, factory singleton initialization getinstance, loading each adapter: SDA adapter registers map.set(sDA'sdalnstance), CIIA adapter registers map.set(CllA',ciialnstance), other adapters register: map.set(key',instance), waiting for application scheduling, the application initiates a vehicle control request, carrying the target SDK name, checking whether the SDK exists in the Map, if it does, factory.getRender(name) returns the interface instance, and the vehicle control operation is executed; otherwise, an error is returned.

[0038] In one example, performing remote vehicle control operation on the first vehicle using the SDK interface instance and the specific format request includes: sending the specific format request to the first vehicle using the SDK interface instance; receiving vehicle control result information returned by the first vehicle based on the specific format request through a callback of the SDK interface instance; converting the internal data format of the vehicle control result information into target result information in the unified user data format of the remote vehicle control application; and displaying the target result information on the remote vehicle control interface of the first vehicle in the remote vehicle control application.

[0039] The SDK executes vehicle control operations and returns results via callbacks. The data conversion layer converts the SDK's returned results into a unified user data format for the application. All types of SDK interface instances ultimately display the same data format on the remote vehicle control interface. The event bus module notifies the application and other related SDKs of the results, and the state management module updates the state information of the relevant SDKs.

[0040] In some implementation scenarios, after converting the internal data format of the vehicle control result information into the target result information in the unified user data format of the remote vehicle control application, the method further includes: searching for a second SDK associated with the first vehicle control SDK in the preset event bus of the remote vehicle control application; calling the event transmitter of the HarmonyOS operating system; and using the event transmitter to transmit the target result information to the second SDK.

[0041] Optionally, the bus task of the preset event bus is to remotely drive the first vehicle to the pick-up location of the target mobile terminal. The preset event bus includes at least: remote start event, map loading event, and autonomous driving event. The second SDK is the map SDK. The first vehicle control SDK transmits the result of the remote start of the vehicle (such as successful start) to the map SDK, and then executes the subsequent pick-up task. The user can view the real-time location of the vehicle on the target mobile terminal.

[0042] In this embodiment, before receiving the first remote vehicle control request for the first vehicle through the remote vehicle control application of the target mobile terminal, the method further includes: starting the remote vehicle control application on the target mobile terminal; loading multiple adapters in the middleware factory module of the remote vehicle control application; registering a vehicle control SDK of domain control platform type for each of the multiple adapters; and configuring a unified user data format for the remote vehicle control application.

[0043] When the system starts, the middleware factory module initializes, and each adapter loads and registers its corresponding vehicle control SDK. In the adaptation layer, each adapter implements the ICarControllerSDKRenderInterface interface to adapt to different SDKs. For example, CarControllerSDASDKRender adapts to the vehicle control functions of the SDA platform, and CarControllerCIIASDKRender adapts to the vehicle control functions of the CIIA platform.

[0044] Figure 4This is a system architecture diagram of an embodiment of the present invention. Functionally, it includes a vehicle control SDK interface layer, a middleware factory module, an adaptation layer, a unified scheduling module, a data conversion layer, an event bus module, and a state management module. The vehicle control SDK interface layer defines a unified SDK interface specification, including standard methods for initialization, rendering, destruction, event listening, and canceling listening. All heterogeneous vehicle control SDKs need to implement this interface. The vehicle control SDK interface layer defines the ICarControllerSDKRenderInterface interface, which includes the following methods: init(): SDK initialization method; render(): vehicle control interface rendering method; destroy(): SDK destruction method; onEvent(): event listening method; offEvent(): Event cancellation listener method; Middleware factory module: a factory class using the singleton pattern, responsible for registering, managing, and distributing various heterogeneous vehicle control SDK instances, providing core functions such as SDK registration, acquisition, and lifecycle management; Adaptation layer: used to implement corresponding adapters for different types of vehicle control SDKs (such as SDA vehicle control, CIIA vehicle control, etc.), converting the interfaces and calling methods of different SDKs into a unified interface specification. The adaptation layer includes SDA platform vehicle controller adapter, CIIA platform vehicle controller adapter, and other vehicle platform adapters; Unified scheduling module: responsible for coordinating the calling order and resource allocation of various heterogeneous vehicle control SDKs. Conflict detection and state synchronization ensure the stable operation of multiple SDKs in the same application environment. Scheduling strategies include priority scheduling, time-slice scheduling, event-driven scheduling, and mutual exclusion scheduling. The data conversion layer is used to uniformly convert data of different formats, transforming the internal data formats of each SDK into a unified application format, simplifying the data processing flow. The event bus module is used as an event transmitter based on the HarmonyOS system, enabling loosely coupled communication between SDKs and between SDKs and applications, supporting event publishing, subscription, and broadcasting mechanisms. The state management module is used to uniformly manage the running status, registration status, and availability status of each SDK, providing status query and status callback mechanisms.

[0045] In one implementation scenario of this embodiment, after receiving a first remote vehicle control request for a first vehicle through the remote vehicle control application of the target mobile terminal, the method further includes: receiving a second remote vehicle control request for a second vehicle through the remote vehicle control application of the target mobile terminal; determining the priorities of the first remote vehicle control request and the second remote vehicle control request; if the priority of the first remote vehicle control request is greater than the priority of the second remote vehicle control request, switching the first vehicle control SDK currently running in the remote vehicle control application to a second vehicle control SDK that matches the second vehicle; if the priority of the first remote vehicle control request is less than or equal to the priority of the second remote vehicle control request, refusing to respond to the second remote vehicle control request.

[0046] Optionally, the priorities of the first remote vehicle control request and the second remote vehicle control request can be determined based on the vehicle and the request type. The priority information includes vehicle priority and request priority. Determining the priorities of the first remote vehicle control request and the second remote vehicle control request includes: determining whether the priority of the first vehicle is greater than the priority of the second vehicle; if the priority of the first vehicle is greater than the priority of the second vehicle, determining that the priority of the first remote vehicle control request is greater than the priority of the second remote vehicle control request; if the priority of the first vehicle is equal to the priority of the second vehicle, determining whether the request priority of the first remote vehicle control request is greater than the request priority of the second remote vehicle control request (e.g., the priority of a remote vehicle lock request is greater than the priority of a remote air conditioner turn-on request); if the request priority of the first remote vehicle control request is greater than the request priority of the second remote vehicle control request, determining that the priority of the first remote vehicle control request is greater than the priority of the second remote vehicle control request; if both vehicle priority and request priority are the same, then they are processed sequentially according to time order.

[0047] This embodiment provides a dynamic adaptation and unified scheduling system and method for heterogeneous vehicle control SDKs based on the HarmonyOS system, which realizes unified management and scheduling of various heterogeneous vehicle control SDKs, improves development efficiency, and reduces maintenance costs.

[0048] Figure 5 This is a flowchart of vehicle control request processing in an embodiment of the present invention, including: S1: When the system starts, the middleware factory module is initialized, and each adapter loads and registers the corresponding vehicle control SDK; S2: When an application initiates a vehicle control request, it receives the request through a unified interface layer; S3: The unified scheduling module analyzes the request type and determines the target SDK; S4: The middleware factory module obtains the corresponding SDK interface instance based on the target SDK name; S5: Transforms application requests into SDK-specific formats using an adaptation layer; S6: The SDK performs vehicle control operations and returns the results via callback; S7: The data conversion layer converts the SDK's returned results into a unified application format; S8: The event bus module notifies the application and other related SDKs of the results; S9: The status management module updates the status information of the relevant SDKs.

[0049] Taking the Changan Qiyuan model as an example, the system first registers the SDA platform vehicle controller and CIIA vehicle controller through the middleware factory module. When a user initiates a vehicle control request, the system automatically selects the appropriate SDK for processing based on the vehicle type information. For vehicles using the SDA platform, CarControllerSDASDKRender is used; for vehicles using the CIIA platform (such as the UNI model), CarControllerCIIASDKRender is used. The adaptation layer converts the unified format request into the format of the corresponding SDK, performs the vehicle control operation, and then converts the result back to the unified format to return it to the application layer. Throughout the process, the unified scheduling module monitors the status of each SDK to avoid conflicts; the event bus module promptly notifies relevant parties of status changes; and the status management module maintains the latest SDK status information.

[0050] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to 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, in essence, 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, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0051] Example 2 This embodiment also provides a remote vehicle control device based on the HarmonyOS system. This device is used to implement the above embodiments and preferred embodiments, and details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0052] Figure 6 This is a structural block diagram of a remote vehicle control device based on the HarmonyOS system according to an embodiment of the present invention, such as... Figure 6 As shown, the device includes: The first receiving module 61 is used to receive a first remote vehicle control request for a first vehicle through a remote vehicle control application of a target mobile terminal, wherein the target mobile terminal runs the HarmonyOS operating system, the HarmonyOS operating system loads the remote vehicle control application, and the remote vehicle control application is bound to multiple vehicles. The identification module 62 is used to identify the domain control platform type of the first vehicle, wherein the domain control platform type is used to characterize the remote vehicle control method of the first vehicle; Control module 63 is used to perform remote vehicle control operations on the first vehicle according to the domain control platform type and the first remote vehicle control request.

[0053] Optionally, the control module includes: an extraction unit for extracting a first vehicle control SDK identifier from the first remote vehicle control request; a search unit for searching for a target software development kit (SDK) matching the first vehicle control SDK identifier in the middleware factory module of the remote vehicle control application; a calling unit for calling an SDK interface instance of the first vehicle control SDK; a conversion unit for converting the first remote vehicle control request into a specific format request matching the first vehicle control SDK; and a control unit for performing remote vehicle control operations on the first vehicle using the SDK interface instance and the specific format request.

[0054] Optionally, the control unit includes: a sending subunit, configured to send the specific format request to the first vehicle using the SDK interface instance; a receiving subunit, configured to receive vehicle control result information returned by the first vehicle based on the specific format request through a callback of the SDK interface instance; a conversion subunit, configured to convert the internal data format of the vehicle control result information into target result information in the unified user data format of the remote vehicle control application; and a display subunit, configured to display the target result information on the remote vehicle control interface of the first vehicle in the remote vehicle control application.

[0055] Optionally, the control unit further includes: a lookup subunit, used to look up a second SDK associated with the first vehicle control SDK in a preset event bus of the remote vehicle control application after the conversion subunit converts the internal data format of the vehicle control result information into the target result information in the unified user data format of the remote vehicle control application; a retrieval subunit, used to retrieve the event transmitter of the HarmonyOS operating system; and a transmission subunit, used to transmit the target result information to the second SDK using the event transmitter.

[0056] Optionally, the identification module includes at least one of the following: a first identification unit for identifying the software-defined vehicle (SDA) domain control platform type of the first vehicle; a second identification unit for identifying the CIIA domain control platform type of the first vehicle; and a third identification unit for identifying the third-party domain control platform type of the first vehicle.

[0057] Optionally, the device further includes: a startup module, configured to start the remote vehicle control application on the target mobile terminal before the first receiving module receives the first remote vehicle control request for the first vehicle through the remote vehicle control application of the target mobile terminal; a loading module, configured to load multiple adapters in the middleware factory module of the remote vehicle control application; a registration module, configured to register a domain control platform type vehicle control SDK for each of the multiple adapters; and a configuration module, configured to configure a unified user data format for the remote vehicle control application.

[0058] Optionally, the device further includes: a second receiving module, configured to receive a second remote vehicle control request for a second vehicle through the remote vehicle control application of the target mobile terminal after the first receiving module receives a first remote vehicle control request for a first vehicle through the remote vehicle control application of the target mobile terminal; a determining module, configured to determine the priority of the first remote vehicle control request and the second remote vehicle control request; and a processing module, configured to, if the priority of the first remote vehicle control request is greater than the priority of the second remote vehicle control request, switch the first vehicle control SDK currently running in the remote vehicle control application to a second vehicle control SDK matching the second vehicle; and if the priority of the first remote vehicle control request is less than or equal to the priority of the second remote vehicle control request, refuse to respond to the second remote vehicle control request.

[0059] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0060] Example 3 Embodiments of the present invention also provide a storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.

[0061] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps: S1, receiving a first remote vehicle control request for the first vehicle through the remote vehicle control application of the target mobile terminal, wherein the target mobile terminal runs the HarmonyOS operating system, the HarmonyOS operating system loads the remote vehicle control application, and the remote vehicle control application is bound to multiple vehicles; S2, identify the domain control platform type of the first vehicle, wherein the domain control platform type is used to characterize the remote vehicle control method of the first vehicle; S3, Perform remote vehicle control operation on the first vehicle according to the domain control platform type and the first remote vehicle control request.

[0062] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing computer programs, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0063] Embodiments of the present invention also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0064] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0065] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program: S1, receiving a first remote vehicle control request for the first vehicle through the remote vehicle control application of the target mobile terminal, wherein the target mobile terminal runs the HarmonyOS operating system, the HarmonyOS operating system loads the remote vehicle control application, and the remote vehicle control application is bound to multiple vehicles; S2, identify the domain control platform type of the first vehicle, wherein the domain control platform type is used to characterize the remote vehicle control method of the first vehicle; S3, Perform remote vehicle control operation on the first vehicle according to the domain control platform type and the first remote vehicle control request.

[0066] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0067] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0068] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, or of course, using hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0069] It should be understood that the terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that additional or alternative steps may be used.

[0070] The above description is merely a specific embodiment of the present invention, enabling those skilled in the art to understand or implement the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A remote vehicle control method based on the HarmonyOS system, characterized in that, include: The remote vehicle control application of the target mobile terminal receives a first remote vehicle control request for the first vehicle, wherein the target mobile terminal runs the HarmonyOS operating system, the HarmonyOS operating system loads the remote vehicle control application, and the remote vehicle control application is bound to multiple vehicles; Identify the domain control platform type of the first vehicle, wherein the domain control platform type is used to characterize the remote vehicle control method of the first vehicle; The remote vehicle control operation is performed on the first vehicle according to the domain control platform type and the first remote vehicle control request.

2. The method according to claim 1, characterized in that, Performing remote vehicle control operations on the first vehicle based on the domain control platform type and the first remote vehicle control request includes: Extract the first vehicle control SDK identifier from the first remote vehicle control request; Search the middleware factory module of the remote vehicle control application for the target software development kit (SDK) that matches the first vehicle control SDK identifier; Call the SDK interface instance of the first vehicle control SDK; The first remote vehicle control request is converted into a specific format request that matches the first vehicle control SDK; The first vehicle is remotely controlled using the SDK interface instance and the specific format request.

3. The method according to claim 2, characterized in that, Performing remote vehicle control operations on the first vehicle using the SDK interface instance and the specific format request includes: The SDK interface instance is used to send the specific format request to the first vehicle; The system receives the vehicle control result information returned by the first vehicle based on the specific format request through the callback of the SDK interface instance. Convert the internal data format of the vehicle control result information into the target result information in the unified user data format of the remote vehicle control application; The target result information is displayed on the remote control interface of the first vehicle in the remote vehicle control application.

4. The method according to claim 3, characterized in that, After converting the internal data format of the vehicle control result information into the target result information in the unified user data format of the remote vehicle control application, the method further includes: Search for the second SDK associated with the first vehicle control SDK in the preset event bus of the remote vehicle control application; Invoke the event emitter of the HarmonyOS operating system; The target result information is transmitted to the second SDK using the event transmitter.

5. The method according to claim 1, characterized in that, The domain control platform type of the first vehicle includes at least one of the following: Identify the software-defined vehicle SDA domain control platform type of the first vehicle; Identify the CIIA domain control platform type of the first vehicle; Identify the type of third-party domain control platform for the first vehicle.

6. The method according to claim 1, characterized in that, Before receiving the first remote vehicle control request for the first vehicle via the remote vehicle control application of the target mobile terminal, the method further includes: The remote vehicle control application is launched on the target mobile terminal; Multiple adapters are loaded into the middleware factory module of the remote vehicle control application; For each of the multiple adapters, register a vehicle control SDK of the domain control platform type; Configure the remote vehicle control application to use a unified user data format.

7. The method according to claim 1, characterized in that, After receiving a first remote vehicle control request for the first vehicle via a remote vehicle control application on the target mobile terminal, the method further includes: The target mobile terminal receives a second remote vehicle control request for the second vehicle through its remote vehicle control application. Determine the priority of the first remote vehicle control request and the second remote vehicle control request; If the priority of the first remote vehicle control request is greater than the priority of the second remote vehicle control request, the first vehicle control SDK currently running in the remote vehicle control application is switched to the second vehicle control SDK that matches the second vehicle; if the priority of the first remote vehicle control request is less than or equal to the priority of the second remote vehicle control request, the second remote vehicle control request is refused to be responded to.

8. A remote vehicle control device based on the HarmonyOS system, characterized in that, include: The first receiving module is used to receive a first remote vehicle control request for a first vehicle through a remote vehicle control application of a target mobile terminal, wherein the target mobile terminal runs the HarmonyOS operating system, the HarmonyOS operating system loads the remote vehicle control application, and the remote vehicle control application is bound to multiple vehicles. The identification module is used to identify the domain control platform type of the first vehicle, wherein the domain control platform type is used to characterize the remote vehicle control method of the first vehicle; The control module is used to perform remote vehicle control operations on the first vehicle according to the domain control platform type and the first remote vehicle control request.

9. A storage medium, characterized in that, The storage medium stores a computer program, wherein the computer program is configured to execute the method described in any one of claims 1 to 7 when it is run.

10. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the method as described in any one of claims 1 to 7.

Images