Vehicle product operation method and device applied to vehicle and terminal equipment
By designing vehicle product instances and decoupling modules layer by layer, the problem of high coupling between modules in vehicle software architecture was solved, which improved stability and scalability, and increased software development efficiency and module compatibility.
Patent Information
- Application Number
- CN202411015876.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-26
- Publication Date
- 2024-11-08
AI Technical Summary
Existing vehicle software architectures suffer from problems such as high coupling between modules, difficulty in independently configuring and freely combining functions, low efficiency in software development and maintenance, and poor algorithm reusability when dealing with diverse vehicle products, resulting in poor stability of vehicle products.
A vehicle product operation method is adopted, which achieves flexible decoupling and mutual association between vehicle products and software modules by creating product instances, function instances, step instances, task instances and actuator instances in a progressive design, thereby enhancing the hierarchical distinction and logical rigor of the software architecture.
It improves the stability of vehicle products and the compatibility of software modules, supports efficient expansion and maintenance, reduces module dependencies, and enhances development efficiency and system flexibility.
Smart Images

Figure CN118915547A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of intelligent control technology, and in particular to a vehicle product operation method, device and terminal equipment applied to a vehicle. Background Art
[0002] With the development of autonomous driving technology, the functions of vehicles are constantly increasing. For example, the parking system has developed from a single automatic parking assistance function to a variety of automatic parking assistance functions. These diverse functional requirements have led to the increasing complexity of the vehicle's software architecture. However, the software architecture of existing vehicles focuses on the implementation of underlying algorithms and a brief description of the overall framework, ignoring the design of the middle layer between the architecture and the algorithm, especially the decoupling and compatibility processing between software modules. This has led to the existing vehicle software architecture having high coupling between modules, difficulty in independent configuration and free combination of functions, low efficiency in software development and maintenance, and poor algorithm reusability when dealing with diverse vehicle products. The existence of these situations further leads to the problem of poor stability of vehicle products. Summary of the invention
[0003] One of the purposes of the present invention is to provide a vehicle product operation method applied to a vehicle to solve the problem of poor stability of vehicle products in the prior art; the second purpose is to provide an apparatus; and the third purpose is to provide a terminal device.
[0004] In order to achieve the above object, the technical solution adopted by the present invention is as follows:
[0005] A vehicle product operation method applied to a vehicle, the method comprising:
[0006] In response to a trigger instruction, the vehicle product recommended by the vehicle is activated; wherein the trigger instruction is used to instruct the activation of the vehicle product recommended by the vehicle so that the vehicle product is executed; the vehicle product is used to represent the service implemented by the vehicle application; the vehicle product corresponds to at least one function, the function corresponds to multiple steps, the steps correspond to multiple tasks, and the tasks correspond to multiple actuators; wherein the function represents the function that needs to be executed to implement the vehicle product; the steps represent the steps that need to be executed to implement the function; the tasks represent the algorithm tasks that need to be executed to implement the steps; the actuator represents the algorithm code required to implement the task; (the product instance is not written in the first step, it is written in the second step)
[0007] Sequentially create a product instance of the vehicle product, a function instance of the function corresponding to the vehicle product, a step instance of the step corresponding to the function, a task instance of the task corresponding to the step, and an actuator instance of the actuator corresponding to the task, to complete the creation of the product instance of the vehicle product;
[0008] Execute the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the actuator instance of the actuator corresponding to the task in sequence to complete the execution of the vehicle product.
[0009] Optionally, sequentially creating a product instance of the vehicle product, a function instance of the function corresponding to the vehicle product, a step instance of the step corresponding to the function, a task instance of the task corresponding to the step, and an actuator instance of the actuator corresponding to the task to complete the creation of the product instance of the vehicle product includes:
[0010] According to the vehicle product, create the product instance of the vehicle product;
[0011] According to a preset mapping relationship, the vehicle product is mapped to at least one corresponding function; wherein the mapping relationship is used to characterize the corresponding relationship between the vehicle product and the function;
[0012] Loading a function configuration of each of the functions from a configuration file of the vehicle product, and creating a function instance of the function;
[0013] Splitting the step configuration of at least one step from the functional configuration of each of the functions;
[0014] According to the step configuration, generating a step instance of the step in the function instance;
[0015] Splitting a task configuration of at least one task from the step configuration of each of the steps;
[0016] According to the task configuration, generating a task instance of the task in the step instance;
[0017] Determine the number of executors required to execute the task according to the task configuration, and create executor instances according to the number of executors;
[0018] The algorithm configuration parameters corresponding to the executor in the configuration file are loaded into the executor instance.
[0019] Optionally, executing the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the actuator instance of the actuator corresponding to the task in sequence to complete the execution of the vehicle product includes:
[0020] According to the function corresponding to the vehicle product, after executing the product instance, sequentially executing the function instances in the product instance;
[0021] Determine the execution order of the steps in the function instance according to the preset logic of the function;
[0022] The step instances of the steps in the function instance are executed sequentially, and when the entry conditions of the steps are met, the step instances of the steps are entered and run until the step instances of all the steps in the function instance are completed.
[0023] Optionally, the step instance of entering and executing the step when the entry condition of the step is met includes:
[0024] Determining, according to the preset logic of the step, the execution order of the task instances of the task in the step instance of the step;
[0025] The task instances of the tasks in the step instance are sequentially run, and the running results of the task instances are stored when the tasks reach the closing condition, until the task instances of all the tasks in the step instance are completed.
[0026] Optionally, the running of the task instance of the task in the step instance includes:
[0027] The executor instance in the task instance is called, and the algorithm in the executor instance is run.
[0028] Optionally, in response to the trigger instruction, before activating the vehicle product recommended by the vehicle, the method further includes:
[0029] Traversing the product configuration list of the vehicle, obtaining the vehicle products of the vehicle and the release condition of each of the vehicle products; the release condition is used to characterize the vehicle state that the vehicle needs to achieve when the vehicle product is executed; the vehicle state at least includes the running state and the environment perception state of the vehicle;
[0030] Calculating the matching degree between the vehicle state indicated by the release condition and the vehicle state of the vehicle at the current moment, and determining the recommended value of the vehicle product according to the matching degree;
[0031] A vehicle product with a maximum recommendation value among the vehicle products is obtained as the vehicle product recommended by the vehicle.
[0032] Optionally, before obtaining the vehicle product with the largest recommendation value among the vehicle products as the vehicle product recommended by the vehicle, the method further includes:
[0033] Obtaining a usage frequency of each of the vehicle products of the vehicle;
[0034] When the recommended value is greater than a first threshold, the recommended value of the vehicle product is optimized using the usage frequency.
[0035] Optionally, after completing the execution of the vehicle product, the method further includes:
[0036] If the function corresponding to the vehicle product is completed, or the execution of the vehicle product is actively exited, the execution of the vehicle product is terminated; otherwise, the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the executor instance of the executor corresponding to the task are re-executed in sequence to complete the execution of the vehicle product.
[0037] A vehicle product operating device applied to a vehicle comprises a headlamp body, wherein the headlamp body is provided with the above-mentioned lampshade.
[0038] A trigger module, for activating a vehicle product recommended by the vehicle in response to a trigger instruction; wherein the trigger instruction is used to instruct the activation of the vehicle product recommended by the vehicle so that the vehicle product is executed; the vehicle product is used to represent the service implemented by the vehicle application; the vehicle product corresponds to at least one function, the function corresponds to a plurality of steps, the steps correspond to a plurality of tasks, and the tasks correspond to a plurality of actuators; wherein the function represents the function required to be executed by the vehicle product; the steps represent the steps required to be executed to implement the function; the tasks represent the algorithm tasks required to be executed to implement the steps; the actuator represents the algorithm code required to implement the task;
[0039] An execution module is used to sequentially create a product instance of the vehicle product, a function instance of the function corresponding to the vehicle product, a step instance of the step corresponding to the function, a task instance of the task corresponding to the step, and an actuator instance of the actuator corresponding to the task to complete the creation of the product instance of the vehicle product; and sequentially execute the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the actuator instance of the actuator corresponding to the task to complete the execution of the vehicle product.
[0040] Optionally, an execution module is used to:
[0041] According to the vehicle product, create the product instance of the vehicle product;
[0042] According to a preset mapping relationship, the vehicle product is mapped to at least one corresponding function; wherein the mapping relationship is used to characterize the corresponding relationship between the vehicle product and the function;
[0043] Loading a function configuration of each of the functions from a configuration file of the vehicle product, and creating a function instance of the function;
[0044] Splitting the step configuration of at least one step from the functional configuration of each of the functions;
[0045] According to the step configuration, generating a step instance of the step in the function instance;
[0046] Splitting a task configuration of at least one task from the step configuration of each of the steps;
[0047] According to the task configuration, generating a task instance of the task in the step instance;
[0048] Determine the number of executors required to execute the task according to the task configuration, and create executor instances according to the number of executors;
[0049] The algorithm configuration parameters corresponding to the executor in the configuration file are loaded into the executor instance.
[0050] Optionally, an execution module is used to:
[0051] According to the function corresponding to the vehicle product, after executing the product instance, sequentially executing the function instances in the product instance;
[0052] Determine the execution order of the steps in the function instance according to the preset logic of the function;
[0053] The step instances of the steps in the function instance are executed sequentially, and when the entry conditions of the steps are met, the step instances of the steps are entered and run until the step instances of all the steps in the function instance are completed.
[0054] Optionally, an execution module is used to:
[0055] Determining, according to the preset logic of the step, the execution order of the task instances of the task in the step instance of the step;
[0056] The task instances of the tasks in the step instance are sequentially run, and the running results of the task instances are stored when the tasks reach the closing condition, until the task instances of all the tasks in the step instance are completed.
[0057] Optionally, an execution module is used to:
[0058] The executor instance in the task instance is called, and the algorithm in the executor instance is run.
[0059] Optionally, the trigger module is used to:
[0060] Traversing the product configuration list of the vehicle, obtaining the vehicle products of the vehicle and the release condition of each of the vehicle products; the release condition is used to characterize the vehicle state that the vehicle needs to achieve when the vehicle product is executed; the vehicle state at least includes the running state and the environment perception state of the vehicle;
[0061] Calculating the matching degree between the vehicle state indicated by the release condition and the vehicle state of the vehicle at the current moment, and determining the recommended value of the vehicle product according to the matching degree;
[0062] A vehicle product with a maximum recommendation value among the vehicle products is obtained as the vehicle product recommended by the vehicle.
[0063] Optionally, the trigger module is used to:
[0064] Obtaining a usage frequency of each of the vehicle products of the vehicle;
[0065] When the recommended value is greater than a first threshold, the recommended value of the vehicle product is optimized using the usage frequency.
[0066] Optionally, an execution module is used to:
[0067] If the function corresponding to the vehicle product is completed, or the execution of the vehicle product is actively exited, the execution of the vehicle product is terminated; otherwise, the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the executor instance of the executor corresponding to the task are re-executed in sequence to complete the execution of the vehicle product.
[0068] A terminal device, comprising: a memory and a processor;
[0069] The memory is used to store a computer program; the processor is used to implement any one of the vehicle product operation methods applied to a vehicle according to the computer program stored in the memory.
[0070] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it is used to implement any one of the vehicle product operation methods applied to a vehicle.
[0071] A computer program product comprises a computer program, wherein when the computer program is executed by a processor, the method described in any one of the vehicle product operation methods applied to a vehicle is implemented.
[0072] Beneficial effects of the present invention:
[0073] In the vehicle product operation method applied to a vehicle proposed in the present application, by realizing flexible decoupling and mutual association between vehicle products and software modules, the software of the vehicle product realizes a more hierarchical architecture design, improves the compatibility of each module in the software, and decouples the upper-level logic and lower-level calculation of the vehicle product. Based on this hierarchical architecture, when a new vehicle product is added to the vehicle, the newly added vehicle product can be expanded and maintained more efficiently. At the same time, the decoupling of the software modules of the vehicle product realized by this hierarchical architecture reduces the dependence of each module in the software of the vehicle product and improves the stability of the vehicle product. BRIEF DESCRIPTION OF THE DRAWINGS
[0074] Figure 1 A flow chart of a vehicle product operation method applied to a vehicle proposed in this embodiment;
[0075] Figure 2 A schematic diagram of a process for creating a product instance proposed in this embodiment;
[0076] Figure 3 A schematic diagram of the operation flow of a product example proposed in this embodiment;
[0077] Figure 4 A flow chart of a vehicle product operation method applied to a vehicle proposed in this embodiment;
[0078] Figure 5 A flowchart of an example of a vehicle product operation method applied to a vehicle proposed in this embodiment;
[0079] Figure 6 A schematic diagram of the relationship between a task and an executor proposed in this embodiment;
[0080] Figure 7 A schematic diagram of the structure of a vehicle product operating device applied to a vehicle proposed in this embodiment;
[0081] Figure 8 This is a schematic diagram of the hardware structure of an electronic device proposed in this embodiment. DETAILED DESCRIPTION
[0082] The following will describe the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention, not for limiting the scope of protection of the present invention.
[0083] With the development of autonomous driving technology, the functions of vehicles are constantly increasing. For example, the parking system has evolved from a single automatic parking assistance function to a comprehensive parking solution that integrates multiple functions. On the vehicle, the services implemented by different functions are called different vehicle products. At present, in the field of parking, vehicle products already have automatic parking in, automatic parking out, memory parking, remote car moving, etc. With the increase in the types and number of vehicle products, and the growth of the functional complexity of each vehicle product, it is particularly important to build a software architecture that is both flexible and configurable and easy to expand. The design of this software architecture requires efficient reuse of existing functional modules to ensure maximum resource utilization. In addition, it is necessary to consider that some vehicle products may have at least one function reused, so the software architecture needs to support flexible combination and decoupling between modules.
[0084] At present, the existing autonomous parking system architecture has proposed the overall framework and the implementation strategy of the underlying algorithm, but there is a significant gap in the detailed description of the architecture, especially the failure to fully explain the key middle layer design between the high-level architecture and the underlying algorithm. This lack limits our understanding of how the system implements complex functions and how different software modules can collaborate efficiently. At the same time, the current architecture lacks an in-depth discussion of the software modular design principles within the software development cycle, which directly affects the subsequent maintainability, testability and upgradeability of the system.
[0085] Therefore, the ideal parking system software architecture should be designed as a modular, loosely coupled system, focusing on filling the gaps in the middle-layer design, clarifying the module function division and interface definition, promoting independent operation and close collaboration, and ensuring high efficiency and stability. At the same time, the compatibility and scalability of the system should be enhanced, and space should be reserved for different product forms and future technology iterations through flexible architecture configuration and standardized interface protocols, accelerating product development, and responding to market diversity and change challenges.
[0086] In response to the above requirements, the vehicle product operation method applied to the vehicle provided in the embodiment of the present application designs a software architecture of a highly modular and flexibly configurable decision-making planning system. The present application implements multi-layer abstraction and configuration management from product to algorithm to the output of decision-making planning information to ensure that the system can meet current needs and flexibly respond to future changes.
[0087] Specifically, the software architecture innovatively introduces an auxiliary tool layer, which concentrates basic algorithms and software units as shared modules, greatly promoting the reusability and continuous maintenance capabilities of the project. Starting from the information input layer, the software architecture realizes the progressive layer of product abstraction layer, function abstraction layer, step abstraction layer, task abstraction layer, and executor abstraction layer until the final result publishing layer. Each layer in the software architecture has clear responsibilities and provides flexible compilation-independent configuration options through the configuration manager, making the entire system both hierarchical and logically rigorous.
[0088] The vehicle product built with this software architecture realizes the flexible decoupling and inter-related design between the vehicle product and the software module during operation. The decoupling design of the upper-level logic and the lower-level calculation of the vehicle product further improves the flexibility and stability of the system. In addition, the use of this software architecture in the vehicle product enables the vehicle product to be quickly adapted, and enables the software of the vehicle product to achieve a more hierarchical architecture design, which enhances the logic and understandability of the system.
[0089] At the same time, through the construction of this software architecture, in the process of vehicle product maintenance, the algorithm module can be updated and replaced more easily due to the freely configurable nature of the underlying algorithm. In addition, in the process of vehicle product development, the maintainability and reusability of the software module can reduce the amount of code development, and through the decoupling between modules, the independence of the development of each software module is achieved, thereby improving development efficiency.
[0090] Optionally, the software architecture of the present application can be used to implement the abstraction of vehicle products that implement static control on the vehicle. For example, the implementation of each parking function in the parking system is usually static control. Optionally, the static control can be a control method in which the control strategy is relatively fixed and does not need to consider dynamic factors in the control decision process. For example, in a parking scenario, for a vehicle product parked in the car, the vehicle needs to obtain the parking space information and then generate the control strategy for the vehicle during the parking process based on the parking space information. During this process, the parking space information will not change dynamically.
[0091] This embodiment proposes a flow chart of a vehicle product operation method applied to a vehicle. Figure 1 As shown, with the electronic device as the execution subject, the method of this embodiment may include the following steps:
[0092] S101. In response to a trigger instruction, activate a vehicle product recommended by the vehicle. The trigger instruction is used to instruct the activation of the vehicle product recommended by the vehicle so that the vehicle product is executed. The vehicle product is used to characterize the service implemented by the vehicle application. The vehicle product corresponds to at least one function, the function corresponds to multiple steps, the steps correspond to multiple tasks, and the tasks correspond to multiple actuators. The function characterizes the function that needs to be executed to implement the vehicle product. The steps characterize the steps that need to be executed to implement the function. The tasks characterize the algorithmic tasks that need to be executed to implement the steps. The actuators characterize the algorithmic codes required to implement the tasks.
[0093] In this embodiment, the electronic device can obtain the trigger instruction generated when the user triggers the vehicle product on the terminal device. Optionally, the terminal device can be a car computer or a user terminal such as a mobile phone or a tablet. The electronic device can respond to the trigger instruction to activate the vehicle product recommended by the vehicle. When the vehicle product is activated, the vehicle product starts to execute. Optionally, the user can view the vehicle products recommended by the vehicle on the terminal. After viewing the at least one vehicle product, the user can click or select the vehicle product to generate the trigger instruction. The trigger instruction is used to instruct the activation of the vehicle product recommended by the vehicle so that the vehicle product is executed. Optionally, all vehicle products corresponding to the vehicle can be displayed on the terminal device. The vehicle product recommended by the vehicle can be a vehicle product recommended by the vehicle that the user is most likely to use at the current moment.
[0094] Optionally, the vehicle product is used to represent the services implemented by the vehicle application. One vehicle product may correspond to one service. For example, the vehicle product may include parking in when the user is in the vehicle, parking outside when the user is outside the vehicle, parking out when the user is in the vehicle, parking out when the user is outside the vehicle, remote control straight driving, reverse tracking, remote moving, memory parking, etc.
[0095] Optionally, each vehicle product may correspond to at least one function. The function is used to characterize the functions that need to be performed to implement the vehicle product. For example, the function may include parking, parking, tracking and reversing, remote control execution, remote car moving, etc. Each function may correspond to multiple steps. The steps are used to characterize the steps that need to be performed to implement the function. For example, the steps may include normal parking, parking in the garage, normal parking, parking adjustment, remote control execution, cruising, tracking, etc. Each step may correspond to multiple tasks. The task is used to characterize the algorithmic task that needs to be performed to implement the step. For example, the task may include target recommendation, target point calculation, trigger rule decision, path planning, speed planning, state monitoring, etc. Each task may correspond to multiple actuators. The actuator is used to characterize the algorithmic code required to implement the task. For example, the actuator may include a parking space recommender, a parking direction recommender, a parking planning trigger decision maker, a parking planning trigger decision maker, a cruising planning decision maker, etc.
[0096] S102. Create in sequence a product instance of a vehicle product, a function instance of a function corresponding to the vehicle product, a step instance of a step corresponding to the function, a task instance of a task corresponding to the step, and an executor instance of an executor corresponding to the task to complete the creation of a product instance of the vehicle product.
[0097] In this embodiment, when the vehicle product starts to execute, the electronic device first needs to create an instance of the vehicle product. In the process of creating the instance of the vehicle product, the electronic device can sequentially create a product instance of the vehicle product, a function instance of the function corresponding to the vehicle product, a step instance of the step corresponding to the function, a task instance of the task corresponding to the step, and an actuator instance of the actuator corresponding to the task. When the product instance, function instance, step instance, task instance, and actuator instance are all created, the product instance of the vehicle product is created.
[0098] In one example, the process of creating the product instance may include the following steps:
[0099] Step 11: Create a product instance of the vehicle product based on the vehicle product.
[0100] In this step, the electronic device can create a product instance of the vehicle product when determining the vehicle product that needs to be executed. Alternatively, the electronic device can also create a product instance of each vehicle product according to the vehicle products configured in each vehicle when the vehicle is started. It should be noted that the product instance created in this step is an instance object including an object name. At this time, the configuration of the functions, steps, tasks, and actuators in the vehicle product has not been completed in the product instance according to the configuration file of the vehicle product. Only after the product instance completes the configuration of the instances of the functions, steps, tasks, and actuators, the product instance is truly created and can be executed.
[0101] Step 12: Map the vehicle product to at least one corresponding function according to a preset mapping relationship, wherein the mapping relationship is used to represent the corresponding relationship between the vehicle product and the function.
[0102] In this step, the electronic device may store the mapping relationship between the vehicle product and the function. Optionally, the mapping relationship is used to characterize the corresponding relationship between the vehicle product and the function. Usually, each vehicle product may correspond to at least one function. Optionally, the mapping relationship may be directly written into the product code of the vehicle product. Alternatively, the electronic device may obtain the corresponding relationship between each vehicle product and the function by reading the mapping relationship table. For example, both parking inside the vehicle and parking outside the vehicle may correspond to the parking function.
[0103] Step 13: Load the function configuration of each function from the configuration file of the vehicle product and create a function instance of the function.
[0104] In this step, the electronic device can read the configuration file of the vehicle product. Optionally, each vehicle can include a configuration file for the configuration information of the vehicle product. Alternatively, a configuration file can be set for each vehicle product. The electronic device can parse the configuration file and obtain the function configuration of each function in the vehicle product. The electronic device can create a function instance of the function in the product instance according to the function configuration.
[0105] Step 14: Split at least one step configuration from the function configuration of each function, and generate a step instance of the step in the function instance according to the step configuration.
[0106] In this step, the electronic device can obtain the function configuration of a function from step 13 when processing a function. The electronic device can split the function configuration to obtain the step configuration of at least one step included in the function. Optionally, a first preset identifier is usually set in the function configuration, and the electronic device can implement the splitting of the step according to the first preset identifier. For example, the first preset identifier can be <step> and< / step> Electronic devices can<step> and< / step> The content between the steps is regarded as a step. The electronic device can generate a step instance of the step in the function instance according to the step configuration.
[0107] Step 15: Split the task configuration of at least one task from the step configuration of each step. Generate a task instance of the task in the step instance according to the task configuration.
[0108] In this step, the electronic device may continue to split the step instance of each step split in step 14. The electronic device may split to obtain a task configuration with one less task. Optionally, the step configuration may be provided with a second preset identifier. The electronic device may split the step according to the second preset identifier. The electronic device may generate a task instance of the task in the step instance according to the task configuration.
[0109] Step 16: According to the task configuration, determine the number of executors required to execute the task, and create executor instances based on the number of executors.
[0110] In this step, the electronic device can determine the executor corresponding to each task and the number of each executor required when executing the task according to the task configuration of each task. The electronic device can create an executor instance according to the executor and the number of the executors. For example, when three executors A are required, three executor instances of executor A can be created.
[0111] Step 17: Load the algorithm configuration parameters corresponding to the executor in the configuration file into the executor instance.
[0112] In this step, the electronic device can obtain the algorithm configuration parameters corresponding to each actuator from the configuration file. The electronic device can add the algorithm configuration parameters to the code of each actuator to generate the actuator instance. For example, when the actuator is an algorithm model, the algorithm configuration parameters can be model parameters. For another example, when the actuator includes judgment logic, the algorithm configuration parameters can include thresholds for judgment.
[0113] In one implementation, the specific creation process of the product instance can be as follows: Figure 2 shown. Figure 2 The specific creation process shown starts with creating a function instance and includes the following steps:
[0114] Step 21: Start creating a function instance.
[0115] Step 22: Load the function configuration from the configuration file and create a function instance of the function.
[0116] Step 23: Separate the step configuration of each step from the functional configuration.
[0117] Step 24: Traverse each step configuration.
[0118] Step 25. Create a step instance based on the step configuration.
[0119] Step 26. Separate the configuration of each task from the step configuration.
[0120] Step 27: Traverse each task configuration.
[0121] Step 28: Create a task instance based on the task configuration.
[0122] Step 29: According to the task configuration, determine the executors and the number of executors required to execute the task, and create executor instances according to the number of executors of each executor.
[0123] Step 30: Load the algorithm configuration parameters corresponding to each executor instance from the configuration file.
[0124] Step 31: Determine whether all tasks in this step have been traversed. If yes, proceed to step 32. If not, proceed to step 27 and continue traversing the next task.
[0125] Step 32: Determine whether all steps in the function have been traversed. If yes, proceed to step 33. If no, proceed to step 24 and continue traversing the next step.
[0126] Step 33: Complete the creation of the function instance.
[0127] S103, sequentially execute the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the executor instance of the executor corresponding to the task to complete the execution of the vehicle product.
[0128] In this embodiment, after the product instance of the vehicle product is created, the electronic device can execute the function instances in the product instance of the vehicle product in sequence according to the preset logic. When each function instance is executed, the function instance will execute the step instance in the function instance according to the preset execution logic of each step. During the execution of each step instance, the task instance in the step instance will be executed according to the preset execution logic. When each task instance is executed, the executor instance in the task instance begins to execute. When all executor instances of a task instance complete the instance, or the execution achieves the preset result, the task instance completes execution. When all tasks in the step instance complete execution, the step instance execution ends. When all steps in the function instance complete execution, the function instance completes execution.
[0129] In one example, the specific execution process of the product instance of the vehicle product may include the following steps:
[0130] Step 41 : After executing the product instance, the function instances in the product instance are sequentially executed according to the functions corresponding to the vehicle product.
[0131] In this step, the electronic device can obtain the execution order of the functions corresponding to the vehicle product. After executing the product instance, the electronic device can sequentially execute the function instances according to the execution order of the functions. Alternatively, the electronic device can, according to the calling relationship between the functions, after determining the first executed function instance, implement the calling execution of other function instances during the execution of the first function instance.
[0132] Step 42: Determine the execution order of the steps in the function instance according to the preset logic of the function. Execute the step instances of the steps in the function instance sequentially, and enter and run the step instance of the step when the entry condition of the step is met, until the step instances of all the steps in the function instance are completed.
[0133] In this step, the electronic device may obtain the preset logic of multiple steps in the function. Optionally, the preset logic is used to characterize the order in which each step is executed. The electronic device may determine the execution order of the steps in the function instance according to the preset logic. The electronic device may sequentially execute each step instance in the function instance according to the execution order. Optionally, the electronic device may determine whether the entry condition of the next step instance is met when executing each step instance. If the execution condition of the next step instance is met, the electronic device may end the execution of the current step instance and enter the next step instance. The electronic device may sequentially execute each step instance of the function instance until all step instances in the function instance are executed.
[0134] Step 43: Determine the execution order of the task instances of the tasks in the step instance of the step according to the preset logic of the step. Run the task instances of the tasks in the step instance in sequence, and store the running results of the task instances when the tasks reach the closing conditions, until the task instances of all the tasks in the step instance are completed.
[0135] In this step, each step may correspond to multiple tasks. Each step may include the preset logic of the multiple tasks. The electronic device may determine the execution order of each task instance in the step instance according to the preset logic. The electronic device may sequentially execute each task instance according to the execution order. Optionally, when the electronic device executes a task instance, the electronic device may determine whether the task instance meets the closing condition. If the task instance meets the closing condition, the electronic device may end the execution of the task instance and store the running result of the task instance. The electronic device may execute the next task instance according to the execution order. The electronic device may sequentially execute each task instance in the step instance according to the execution order until all task instances are executed.
[0136] Step 44: Call the executor instance in the task instance and run the algorithm in the executor instance.
[0137] In this step, during the execution of each task instance, the electronic device may run the executor instance in the task instance to implement the algorithm corresponding to the executor instance.
[0138] In one implementation, the specific execution process of the product instance can be as follows: Figure 3 shown. Figure 3 The specific operation process shown starts from running the function instance and includes the following steps:
[0139] Step 51: Start executing the function instance.
[0140] Step 52: traverse the step instances in the function instance.
[0141] Step 53: Determine whether the entry condition of the next step of the current step is met. If yes, proceed to step 54. If not, proceed to step 55.
[0142] Step 54: Switch from the step instance of the current step to the step instance of the next step. The step instance of the next step becomes the step instance of the new current step.
[0143] Step 55: Execute the step instance of the current step.
[0144] Step 56: Traverse the tasks in this step instance
[0145] Step 57: If the task instance of the current task reaches the closing condition, proceed to step 56; otherwise, proceed to step 58.
[0146] Step 58: Call each executor instance in the task instance, run the corresponding algorithm module, and implement the execution of the task instance.
[0147] Step 59: Store the task results.
[0148] Step 60: Determine whether all the task instances in the step instance have been traversed. If yes, proceed to step 61. If no, proceed to step 56.
[0149] Step 61: Determine whether all ratio instances in the function instance have been traversed. If yes, proceed to step 62. If no, proceed to step 52.
[0150] Step 62: The function instance ends execution.
[0151] The vehicle product operation method applied to the vehicle provided by the present application can obtain the trigger instruction generated when the user triggers the vehicle product on the terminal device. The electronic device can respond to the trigger instruction to activate the vehicle product recommended by the vehicle and start the vehicle product. The electronic device can sequentially create a product instance of the vehicle product, a function instance of the function corresponding to the vehicle product, a step instance of the step corresponding to the function, a task instance of the task corresponding to the step, and an actuator instance of the actuator corresponding to the task to achieve the creation of the product instance of the vehicle product. The electronic device can sequentially execute the function instance in the product instance of the vehicle product according to the preset logic. When each function instance is executed, the electronic device can sequentially execute the step instance in the function instance. During the execution of each step instance, the electronic device can sequentially execute the task instance in the step instance. The electronic device implements the execution of the task instance by running the actuator instance in the task instance. In the present application, by running the product instance, function instance, step instance, task instance, and actuator instance of the vehicle product layer by layer, the dependence between the instances is reduced and the stability of the vehicle product is improved.
[0152] This embodiment proposes a flow chart of a vehicle product operation method applied to a vehicle. Figures 1 to 3 Based on the embodiment shown, Figure 4 As shown, with the electronic device as the execution subject, the method of this embodiment may include the following steps:
[0153] S201, traverse the product configuration list of the vehicle, obtain the vehicle products of the vehicle and the release conditions of each vehicle product. The release conditions are used to represent the vehicle state that the vehicle needs to achieve when the vehicle product is executed. The vehicle state at least includes the vehicle's operating state and environmental perception state.
[0154] In this embodiment, the electronic device may obtain the product configuration list of the vehicle when the vehicle is powered on. After obtaining the product configuration list of the vehicle, the electronic device may obtain the vehicle products therein. Optionally, the electronic device may compose the vehicle products into a product list. Optionally, the electronic device may generate a product instance of each vehicle product and compose the product list using the product instances.
[0155] The electronic device can also obtain the release conditions of each vehicle product from the product configuration list. Optionally, the release condition can be used to characterize the vehicle state that the vehicle needs to achieve when the vehicle product is executed. Optionally, the vehicle state includes at least the vehicle's operating state and environmental perception state. For example, in a parking scenario, the environmental perception state needs to include information such as the user can detect parking spaces or parked vehicles in the car and around the vehicle, and the operating state needs to include the vehicle being in a low-speed operation or braked state.
[0156] S202: Calculate the matching degree between the vehicle state indicated by the release condition and the vehicle state of the vehicle at the current moment, and determine the recommended value of the vehicle product according to the matching degree.
[0157] In this embodiment, the electronic device can obtain the vehicle state of the vehicle at the current moment. The electronic device can use the vehicle state of the vehicle at the current moment to match the vehicle state of each vehicle product. Optionally, if the vehicle state of the vehicle at the current moment meets the vehicle state required by the vehicle product, the electronic device can add the vehicle product to the release list. Optionally, if the vehicle state of the vehicle at the current moment meets the vehicle state required by the vehicle product, the electronic device can also calculate the degree of match between the vehicle state of the vehicle product and the vehicle state of the vehicle at the current moment. The electronic device can calculate a recommended value based on the degree of match. Optionally, the degree of match is the recommended value. The greater the degree of match, the greater the recommended value, and the greater the possibility that the user will select the vehicle product at the current moment when the electronic device is tasked.
[0158] In one example, the electronic device may also obtain the usage frequency of each vehicle product of the vehicle. The electronic device may use the usage frequency to optimize the recommendation value of the vehicle product. For example, the electronic device may use the sum of the usage frequency and the matching degree as a new recommendation value. For another example, when the matching degrees are the same, the electronic device may rank the electronic devices with higher usage frequencies in front.
[0159] S203: Acquire a vehicle product with the largest recommendation value among the vehicle products as the vehicle recommended product.
[0160] In this embodiment, the electronic device may select the vehicle product with the largest recommendation value from the recommendation values of all vehicle products as the vehicle product recommended by the vehicle. When there are multiple vehicle products with the same recommendation value, the electronic device may obtain the vehicle product ranked first as the vehicle product recommended by the vehicle.
[0161] S204. In response to the trigger instruction, activate the vehicle product recommended by the vehicle. The trigger instruction is used to instruct the activation of the vehicle product recommended by the vehicle so that the vehicle product is executed. The vehicle product is used to characterize the service implemented by the vehicle application. The vehicle product corresponds to at least one function, the function corresponds to multiple steps, the steps correspond to multiple tasks, and the tasks correspond to multiple actuators. The function characterizes the function that needs to be executed to implement the vehicle product. The step characterizes the steps that need to be executed to implement the function. The task characterizes the algorithm task that needs to be executed to implement the step. The actuator characterizes the algorithm code required to implement the task.
[0162] S205. Create in sequence a product instance of the vehicle product, a function instance of the function corresponding to the vehicle product, a step instance of the step corresponding to the function, a task instance of the task corresponding to the step, and an executor instance of the executor corresponding to the task to complete the creation of the product instance of the vehicle product.
[0163] S206, sequentially execute the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the executor instance of the executor corresponding to the task to complete the execution of the vehicle product.
[0164] Among them, steps S204 to S206 are Figure 1 The implementation of steps S101 to S103 in the illustrated embodiment is similar and will not be described in detail in this embodiment.
[0165] S207: If the function corresponding to the vehicle product is completed, or the execution of the vehicle product is actively exited, the execution of the vehicle product is terminated. Otherwise, the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the executor instance of the executor corresponding to the task are re-executed in sequence to complete the execution of the vehicle product.
[0166] In this embodiment, the electronic device can determine whether the function corresponding to the vehicle product has been completed when the execution of the vehicle product is completed. If the function corresponding to the vehicle product has been completed, the electronic device can end the execution of the vehicle product. If not, the electronic device can continue to determine whether the execution of the vehicle product is an active exit. If it is an active exit, the electronic device can end the execution of the vehicle product of the vehicle. If not, the electronic device needs to return to step 206 and re-execute the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the actuator instance of the actuator corresponding to the task in sequence to complete the execution of the vehicle product.
[0167] The vehicle product operation method applied to a vehicle provided by the present application, the electronic device can obtain the product configuration list of the vehicle when the vehicle is powered on, and obtain the vehicle products of the vehicle and the release conditions of each vehicle product according to the configuration list. The electronic device can obtain the vehicle status of the vehicle at the current moment. The electronic device can use the vehicle status to match the release condition to obtain the matching degree, and obtain the recommended value according to the matching degree. The electronic device can select the vehicle product with the largest recommendation value as the vehicle product recommended by the vehicle. The electronic device can activate the vehicle product recommended by the vehicle in response to the trigger instruction, so that the vehicle product starts to execute. The electronic device can create and execute the product instance of the vehicle product to complete the execution of the vehicle product. The electronic device can re-execute the product instance when all the functions corresponding to the vehicle product are executed, or when the vehicle product executes the active exit. In the present application, the intelligence of the vehicle's decision-making is improved through the recommendation of the vehicle product, and the user experience is improved. In addition, the present application ensures the execution of the vehicle product and improves the user experience by judging the end of execution.
[0168] This embodiment provides a flow chart of an example of a vehicle product operation method applied to a vehicle. Figures 1 to 4 Based on the embodiment shown, Figure 5 As shown, with the electronic device as the execution subject, the method of this embodiment may include the following step 7:
[0169] Step 71: The electronic device may read the vehicle products supported by the current vehicle from the configuration file when the vehicle is powered on.
[0170] Step 72: The electronic device may create a product instance of each product in sequence according to the product configuration list of step 71, and generate a product list.
[0171] Step 73: The electronic device may traverse product instances in the product list.
[0172] Step 74: The electronic device determines whether the product meets the release condition. If yes, proceed to step 75. If no, proceed to step 73.
[0173] Step 75: The electronic device adds the products meeting the release conditions to the release list.
[0174] Step 76: The electronic device determines whether the traversal is finished. If so, the process proceeds to step 77. If not, the process proceeds to step 73.
[0175] Step 77: The electronic device determines whether the segment release list is empty. If yes, proceed to step 78. If no, proceed to step 73.
[0176] Step 78: The electronic device recommends a vehicle product from the product release list.
[0177] Step 79, the electronic device determines whether the vehicle product is activated. Specifically, the electronic device determines whether the vehicle product to be activated sent from the state machine is not empty. At the same time, the electronic device checks whether the product sent by the state machine is in the release list. If both are yes, go to step 80. If not, go to step 73.
[0178] Step 80: The electronic device maps the activated vehicle product to the corresponding function.
[0179] Step 81: The electronic device creates a function instance of the function.
[0180] Step 82: The electronic device enters the functional logic and runs the corresponding function.
[0181] Step 83: The electronic device determines whether the segment function is completed, or whether the driver actively exits the execution of the vehicle product. If yes, proceed to step 82. If no, proceed to step 84.
[0182] This embodiment proposes a schematic diagram of a system architecture. Figures 1 to 5 The vehicle product operation method applied to a vehicle shown in FIG. 1 is a parking system as an example. The vehicle product can be arranged in a Figure 6 In the system architecture of the vehicle shown. Optionally, the parking system can be a parking decision planning system. The system architecture may include:
[0183] Auxiliary tools. The auxiliary tools may contain some basic modules such as data structures, algorithm modules, software modules, etc. The auxiliary tools can be called by the main program. The use of the auxiliary tools strips out the basic modules that can be used and maintained for future projects.
[0184] Information input layer. The information input layer can accept vehicle information, state machine signals and other signals. These inputs are obtained from other components through topic subscription and other methods. The original input of the information input layer can be obtained through the communication interface of each component. In order to isolate the communication interface from the internal algorithm, the information input layer of this application will also perform interface conversion. That is, the information input layer can map the data directly obtained from the communication interface to the data structure required by the algorithm, so that the algorithm is isolated from the interface, reducing the impact of upstream interface changes on the algorithm implementation, and improving the internal stability of the algorithm.
[0185] Product abstraction layer. This product abstraction layer is used to abstract each vehicle product. All vehicle products inherit from a product interface class. Each product abstraction corresponds to a specific vehicle product in the configuration list. Once each vehicle product is created, it can determine whether the conditions for the use of the vehicle product are met. For example, a vehicle product that is parked out of a car will determine whether the car is in the parking space and use the judgment result as one of the conditions.
[0186] The product abstraction layer may correspond to a product configuration. The product configuration is actually a product configuration file. The content of the file may include a product configuration list, whether the product is activated, and other information. The product abstraction layer may also correspond to a first manager. The first manager may read the product configuration file in the product configuration, and create a product instance of each vehicle product according to the product configuration list in the product configuration file. The first manager may also release all vehicle products that meet the usable conditions and send them to the HMI and state machine for users and upper-level system scheduling and selection. The first manager may also give a best product recommendation as the default product to be entered. The first manager may also provide a mapping relationship from product to function but does not perform the mapping. The implementation of the first manager is closer to the settings at the user and interaction levels.
[0187] Functional abstraction layer. The meaning of the product abstraction layer is similar to that of the product abstraction layer. However, the functional abstraction layer is closer to the algorithm. Moreover, the functions of the functional abstraction layer are specific execution units when the vehicle products of the product abstraction layer need to be expressed. Each function of the functional abstraction layer inherits from a functional interface class. Each function in the functional abstraction layer corresponds to the vehicle products in the product abstraction layer. Multiple vehicle products can correspond to one function. Different docking functions of the product abstraction layer can correspond to the docking functions of the functional abstraction layer. Optionally, the product to function is not mapped one to one. Optionally, one product can only correspond to one function.
[0188] The function abstraction layer may correspond to a second manager. The second manager may read the vehicle product that the state machine needs to enter, and create relevant function instances and load function configuration files according to the mapping relationship between vehicle products and functions provided by the product manager. The function abstraction layer may correspond to a function configuration file. The second manager may also pass the step-related information contained in the function configuration file in the function configuration to a lower level of abstraction.
[0189] Step abstraction layer. The step abstraction layer is an abstraction layer that decomposes the steps when executing a certain function. Each step inherits from a step interface class. The step abstraction layer makes a relatively macroscopic distinction between the behavior of the function on the decision-making and planning side. For example, for the parking function, different parking stages are quite different. Therefore, in the stage where the automatic parking vehicle has not entered the storage space, the vehicle needs a larger range of posture adjustment, and the tracking accuracy requirement does not need to be too high. In the stage where the vehicle has entered the storage space, the parking space accuracy, positioning accuracy and tracking accuracy are not enough and it is likely to cause storage friction, so the vehicle has higher requirements for tracking accuracy. Therefore, the parking function can be abstracted into two steps at the step abstraction layer: normal parking and storage friction parking. For another example, memory parking can be abstracted into multiple steps. That is, a function can be broken down by the step abstraction layer into a combination of multiple steps.
[0190] During the process of creating a function instance, the third manager corresponding to the step abstraction layer can create a corresponding step instance according to the step list in the function configuration. The third manager can also be responsible for the priority management of the steps and the switching actions of the previous and next steps. The third manager can also pass the task list of each step contained in the step list to the lower level abstraction. During the creation of each step instance, the third manager can load the step configuration by itself. The step configuration can include a step configuration file. The step list is applied to the scheduling level, which is more macroscopic and has multiple configurations. The step configuration file is applied to the algorithm level, and usually contains some information such as calibration parameters related to the step itself.
[0191] Task abstraction layer. The task abstraction layer is an abstract decomposition of the algorithm module that needs to be executed in each step. Each task inherits from the task interface class. Different steps have the same tasks and different tasks. For example, the normal docking step consists of multiple tasks. Each task is responsible for the specific execution of a decision or planned algorithm scheduling. Each task has the authority to determine whether to open the segment by itself.
[0192] The fourth manager corresponding to the task abstraction layer can create corresponding tasks according to the configuration in the task list. The fourth manager can also be responsible for the sequential execution scheduling of tasks. The fourth manager can also pass the executor list to the executor abstraction layer. The fourth manager can also load algorithm-related configuration information from the task configuration file of the task configuration when each task is created.
[0193] Executor abstraction layer. The executor abstraction layer is the top level abstraction of the underlying algorithm and is the smallest unit of the scheduling object when the task is executed. The executor abstraction layer and the executors of the same type corresponding to a task form a set. The elements in this set all inherit from the same interface class. The relationship between tasks and executors can be as follows: Figure 6 shown.
[0194] The fifth manager corresponding to the executor abstraction layer can create the corresponding executor instance in the executor list. The fifth manager can also execute each executor instance in turn to obtain the output of each task. When each executor instance is created, it will automatically load the algorithm-related configuration parameters from the executor configuration file in the executor configuration.
[0195] This embodiment provides a structural schematic diagram of a vehicle product operation device applied to a vehicle, such as Figure 7 As shown, the vehicle product operation device 70 applied to a vehicle of this embodiment is used to implement the operation corresponding to the electronic device in any of the above method embodiments. The vehicle product operation device 70 applied to a vehicle of this embodiment includes:
[0196] The trigger module 71 is used to activate the vehicle product recommended by the vehicle in response to the trigger instruction. The trigger instruction is used to instruct the activation of the vehicle product recommended by the vehicle so that the vehicle product is executed. The vehicle product is used to characterize the service implemented by the vehicle application. The vehicle product corresponds to at least one function, the function corresponds to multiple steps, the steps correspond to multiple tasks, and the tasks correspond to multiple actuators. The function characterizes the function that needs to be executed to implement the vehicle product. The step characterizes the steps that need to be executed to implement the function. The task characterizes the algorithm task that needs to be executed to implement the step. The actuator characterizes the algorithm code required to implement the task.
[0197] The execution module 72 is used to sequentially create a product instance of the vehicle product, a function instance of the function corresponding to the vehicle product, a step instance of the step corresponding to the function, a task instance of the task corresponding to the step, and an actuator instance of the actuator corresponding to the task, so as to complete the creation of the product instance of the vehicle product. The product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the actuator instance of the actuator corresponding to the task are sequentially executed to complete the execution of the vehicle product.
[0198] Optionally, the execution module 72 is used to:
[0199] Create a product instance of the vehicle product based on the vehicle product.
[0200] According to a preset mapping relationship, the vehicle product is mapped to at least one corresponding function, wherein the mapping relationship is used to characterize the corresponding relationship between the vehicle product and the function.
[0201] The function configuration of each function is loaded from the configuration file of the vehicle product, and a function instance of the function is created.
[0202] The step configuration of at least one step is separated from the functional configuration of each function.
[0203] Generates a step instance of the step in the function instance based on the step configuration.
[0204] Split the task configuration of at least one task from the step configuration of each step.
[0205] Generates a task instance of the task in the step instance according to the task configuration.
[0206] Based on the task configuration, the number of executors required to execute the task is determined, and executor instances are created based on the number of executors.
[0207] Load the algorithm configuration parameters corresponding to the executor in the configuration file into the executor instance.
[0208] Optionally, the execution module 72 is used to:
[0209] According to the functions corresponding to the vehicle product, after the product instance is executed, the function instances in the product instance are executed sequentially.
[0210] Determine the execution order of the steps in a function instance according to the preset logic of the function.
[0211] Execute the step instances of the steps in the function instance sequentially, and enter and run the step instance of the step when the entry condition of the step is met, until the step instances of all the steps in the function instance are completed.
[0212] Optionally, the execution module 72 is used to:
[0213] Determine the execution order of the task instances of the tasks in the step instance of the step according to the preset logic of the step.
[0214] Run the task instances of the tasks in the step instance sequentially, and store the running results of the task instances when the tasks reach the shutdown condition, until the task instances of all the tasks in the step instance are completed.
[0215] Optionally, the execution module 72 is used to:
[0216] Call the executor instance in the task instance and run the algorithm in the executor instance.
[0217] Optionally, the trigger module 71 is used to:
[0218] Traverse the vehicle's product configuration list to obtain the vehicle's vehicle products and the release conditions of each vehicle product. The release conditions are used to characterize the vehicle state that the vehicle needs to achieve when the vehicle product is executed. The vehicle state at least includes the vehicle's operating state and environmental perception state.
[0219] The matching degree between the vehicle state indicated by the release condition and the vehicle state of the vehicle at the current moment is calculated, and the recommended value of the vehicle product is determined according to the matching degree.
[0220] The vehicle product with the largest recommendation value among the vehicle products is obtained as the vehicle product for vehicle recommendation.
[0221] Optionally, the trigger module 71 is used to:
[0222] Get the usage frequency of each vehicle product of the vehicle.
[0223] When the recommended value is greater than the first threshold, the recommended value of the vehicle product is optimized using the usage frequency.
[0224] Optionally, the execution module 72 is used to:
[0225] If the function corresponding to the vehicle product is completed, or the execution of the vehicle product is actively exited, the execution of the vehicle product is terminated. Otherwise, the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the executor instance of the executor corresponding to the task are re-executed in sequence to complete the execution of the vehicle product.
[0226] The vehicle product operation device 70 applied to a vehicle provided in the embodiment of the present application can execute the above-mentioned method embodiment. Its specific implementation principle and technical effects can be found in the above-mentioned method embodiment, and this embodiment will not be repeated here.
[0227] This embodiment provides a hardware structure diagram of an electronic device. Figure 8 As shown, the electronic device 80 is used to implement the operations corresponding to the electronic device in any of the above method embodiments. The electronic device 80 of this embodiment may include: a memory 81, a processor 82 and a communication interface 84.
[0228] The memory 81 is used to store computer programs. The memory 81 may include a high-speed random access memory (RAM), and may also include a non-volatile memory (NVM), such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a disk or an optical disk.
[0229] The processor 82 is used to execute the computer program stored in the memory to implement the method in the above embodiment. For details, please refer to the relevant description in the above method embodiment. The processor 82 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the invention can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.
[0230] Optionally, the memory 81 may be independent or integrated with the processor 82 .
[0231] When the memory 81 is a device independent of the processor 82, the electronic device 80 may further include a bus 83. The bus 83 is used to connect the memory 81 and the processor 82. The bus 83 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.
[0232] The communication interface 24 can be connected to the processor 81 via the bus 83. The processor 82 can control the communication interface 24 to obtain signals such as departure instructions.
[0233] The electronic device provided in this embodiment can be used to execute the above-mentioned vehicle product operation method applied to the vehicle. Its implementation method and technical effect are similar, and this embodiment will not be repeated here.
[0234] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, it is used to implement the methods provided in the various embodiments described above.
[0235] Among them, the computer-readable storage medium can be a computer storage medium or a communication medium. The communication medium includes any medium that facilitates the transmission of a computer program from one place to another. The computer storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, a computer-readable storage medium is coupled to a processor so that the processor can read information from the computer-readable storage medium and write information to the computer-readable storage medium. Of course, the computer-readable storage medium can also be a component of the processor. The processor and the computer-readable storage medium can be located in an application-specific integrated circuit (ASIC). In addition, the ASIC can be located in a user device. Of course, the processor and the computer-readable storage medium can also exist in a communication device as discrete components.
[0236] Specifically, the computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special-purpose computer.
[0237] The present application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor of a device can read the computer program from the computer-readable storage medium, and at least one processor executes the computer program so that the device implements the methods provided in the various embodiments described above.
[0238] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.
[0239] Among them, each module can be physically separated, for example, installed in different locations of a device, or installed on different devices, or distributed on multiple network units, or distributed on multiple processors. Each module can also be integrated together, for example, installed in the same device, or integrated in a set of codes. Each module can exist in the form of hardware, or can also exist in the form of software, or can also be implemented in the form of software plus hardware. The present application can select some or all of the modules according to actual needs to achieve the purpose of the present embodiment.
[0240] When each module is implemented as an integrated module in the form of a software function module, it can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of each embodiment of the present application.
[0241] It should be understood that, although the various steps in the flowcharts in the above-described embodiments are sequentially displayed according to the indications of the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and they can be executed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily to be carried out sequentially, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
[0242] The above embodiments are only preferred embodiments for fully illustrating the present invention, and the protection scope of the present invention is not limited thereto. Any equivalent substitution or change made by a person skilled in the art based on the present invention is within the protection scope of the present invention.
Claims
1. A vehicle product operation method applied to a vehicle, characterized in that: The method comprises: In response to a trigger instruction, the vehicle product recommended by the vehicle is activated; wherein the trigger instruction is used to instruct the activation of the vehicle product recommended by the vehicle so that the vehicle product is executed; the vehicle product is used to represent the service implemented by the vehicle application; the vehicle product corresponds to at least one function, the function corresponds to a plurality of steps, the steps correspond to a plurality of tasks, and the tasks correspond to a plurality of actuators; wherein the function represents the function that needs to be executed to implement the vehicle product; the steps represent the steps that need to be executed to implement the function; the tasks represent the algorithm tasks that need to be executed to implement the steps; the actuator represents the algorithm code required to implement the task; Sequentially create a product instance of the vehicle product, a function instance of the function corresponding to the vehicle product, a step instance of the step corresponding to the function, a task instance of the task corresponding to the step, and an actuator instance of the actuator corresponding to the task, to complete the creation of the product instance of the vehicle product; Execute the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the actuator instance of the actuator corresponding to the task in sequence to complete the execution of the vehicle product.
2. The method according to claim 1, characterized in that The product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the actuator instance of the actuator corresponding to the task are sequentially created to complete the creation of the product instance of the vehicle product, including: According to the vehicle product, create the product instance of the vehicle product; According to a preset mapping relationship, the vehicle product is mapped to at least one corresponding function; wherein the mapping relationship is used to characterize the corresponding relationship between the vehicle product and the function; Loading a function configuration of each of the functions from a configuration file of the vehicle product, and creating a function instance of the function; Splitting the step configuration of at least one step from the functional configuration of each of the functions; According to the step configuration, generating a step instance of the step in the function instance; Splitting a task configuration of at least one task from the step configuration of each of the steps; According to the task configuration, generating a task instance of the task in the step instance; Determine the number of executors required to execute the task according to the task configuration, and create executor instances according to the number of executors; The algorithm configuration parameters corresponding to the executor in the configuration file are loaded into the executor instance.
3. The method according to claim 2, characterized in that Sequentially executing the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the actuator instance of the actuator corresponding to the task to complete the execution of the vehicle product, including: According to the function corresponding to the vehicle product, after executing the product instance, sequentially executing the function instances in the product instance; Determine the execution order of the steps in the function instance according to the preset logic of the function; The step instances of the steps in the function instance are executed sequentially, and when the entry conditions of the steps are met, the step instances of the steps are entered and run until the step instances of all the steps in the function instance are completed.
4. The method according to claim 3, characterized in that The step instance of entering and executing the step when the entry condition of the step is met includes: Determining, according to the preset logic of the step, the execution order of the task instances of the task in the step instance of the step; The task instances of the tasks in the step instance are sequentially run, and the running results of the task instances are stored when the tasks reach the closing condition, until the task instances of all the tasks in the step instance are completed.
5. The method according to claim 4, characterized in that The task instance of running the task in the step instance includes: The executor instance in the task instance is called, and the algorithm in the executor instance is run.
6. The method according to any one of claims 1 to 5, characterized in that In response to the trigger instruction, before activating the vehicle product recommended by the vehicle, the method further includes: Traversing the product configuration list of the vehicle, obtaining the vehicle products of the vehicle and the release condition of each of the vehicle products; the release condition is used to characterize the vehicle state that the vehicle needs to achieve when the vehicle product is executed; the vehicle state at least includes the running state and the environment perception state of the vehicle; Calculating the matching degree between the vehicle state indicated by the release condition and the vehicle state of the vehicle at the current moment, and determining the recommended value of the vehicle product according to the matching degree; A vehicle product with a maximum recommendation value among the vehicle products is obtained as the vehicle product recommended by the vehicle.
7. The method according to claim 6, characterized in that Before obtaining the vehicle product with the largest recommendation value among the vehicle products as the vehicle product recommended by the vehicle, the method further includes: Obtaining a usage frequency of each of the vehicle products of the vehicle; When the recommended value is greater than a first threshold, the recommended value of the vehicle product is optimized using the usage frequency.
8. The method according to any one of claims 1 to 5, characterized in that After completing the execution of the vehicle product, the method further includes: If the function corresponding to the vehicle product is completed, or the execution of the vehicle product is actively exited, the execution of the vehicle product is terminated; otherwise, the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the executor instance of the executor corresponding to the task are re-executed in sequence to complete the execution of the vehicle product.
9. A vehicle product operation device applied to a vehicle, characterized in that: The device comprises: A trigger module, for activating a vehicle product recommended by the vehicle in response to a trigger instruction; wherein the trigger instruction is used to instruct the activation of the vehicle product recommended by the vehicle so that the vehicle product is executed; the vehicle product is used to represent the service implemented by the vehicle application; the vehicle product corresponds to at least one function, the function corresponds to a plurality of steps, the steps correspond to a plurality of tasks, and the tasks correspond to a plurality of actuators; wherein the function represents the function required to be executed by the vehicle product; the steps represent the steps required to be executed to implement the function; the tasks represent the algorithm tasks required to be executed to implement the steps; the actuator represents the algorithm code required to implement the task; An execution module is used to sequentially create a product instance of the vehicle product, a function instance of the function corresponding to the vehicle product, a step instance of the step corresponding to the function, a task instance of the task corresponding to the step, and an actuator instance of the actuator corresponding to the task to complete the creation of the product instance of the vehicle product; and sequentially execute the product instance of the vehicle product, the function instance of the function corresponding to the vehicle product, the step instance of the step corresponding to the function, the task instance of the task corresponding to the step, and the actuator instance of the actuator corresponding to the task to complete the execution of the vehicle product.
10. A terminal device, characterized in that: The device comprises: a memory and a processor; The memory is used to store a computer program; the processor is used to implement the method according to any one of claims 1 to 8 according to the computer program stored in the memory.
11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it is used to implement the method according to any one of claims 1 to 8.
12. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.
