In-vehicle software execution method, device, vehicle, and memory medium.
Patent Information
- Authority / Receiving Office
- TR · TR
- Patent Type
- Applications
- Current Assignee / Owner
- GUANGZHOU AUTOMOBILE GROUP CO LTD
- Filing Date
- 2023-08-29
- Publication Date
- 2026-06-22
Smart Images
Figure 00000016_0000 
Figure 00000016_0001 
Figure 00000017_0000
Abstract
Description
1 TARIFF IN-VEHICLE SOFTWARE EXECUTION METHOD, DEVICE, VEHICLE AND MEMORY MEDIUM Technical Area An example of the application of this invention relates to the technical field of in-vehicle software, specifically, a type of in-vehicle software. The execution method is related to the device, tool, and memory medium. State of the Art In today's rapidly changing environment, the pace of innovation for traditional hardware is also increasing. It struggles to meet user needs; software-defined tools represent a new direction in the development of intelligent vehicles. This creates a market and businesses that place higher demands on the update and iteration speed of in-vehicle software. In this context, the software execution includes the software script file and the engine analyzer. Technical solutions that drive progress have emerged. Here, the product script file integrates in-vehicle software functions. It refers to the defining code structure. The product script file uses JavaScript Object Notation (JSON) syntax. abstracting the implementation details of the in-vehicle software, the function definitions and logic of the in-vehicle software. It describes the application in a highly structured manner. Currently, in the in-vehicle software technical field, the fixed coding method is generally used for developing in-vehicle software. It is used. In particular, in-vehicle software developers, based on the existing platform, develop specific in-vehicle software. coding functions using a specific programming language (for example, C / C++), and then executable after coding. producing programs and integrating these programs within a specific vehicle system or using third-party applications It is presented as a program. In-vehicle software development using the hardcoding method has a long development cycle. Furthermore, when the in-vehicle software needs to be modified and iterated, the software can be simply re-coded using the hard coding method. It is possible to encode, package, and update the software via wireless download technology (OTA). Change weakens iteration adaptation. Brief Description of the Invention An example application of this invention is an in-vehicle software execution method that improves upon the aforementioned problems. It provides devices, tools, and memory media. From a first perspective, an application example of this invention provides a method for executing in-vehicle software. The method in question... This includes: - obtaining the relevant script file for the in-vehicle software; the aforementioned script file comes in different types. It contains several nodes; - depending on the node type of the node in the mentioned script file, the mentioned script file Separate the logic script into logic scripts and interaction scripts; - the aforementioned logic script will be the logic script. to send the aforementioned interaction script file to the interaction engine, thus the aforementioned logic engine The logic script mentioned, the interaction engine mentioned, executes the interaction script mentioned, the script During the execution process of the file, the aforementioned interaction engine and logic engine scripts will operate according to the content of the script file. They call each other. Secondly, this invention offers an application example of an in-vehicle software execution method. The method in question... This includes: the logic script file sent by the receiving cloud, and the aforementioned logic script file. It includes a software ID. In response to the triggering operation associated with the aforementioned software ID, the aforementioned logic is executed. It executes the script file. When the trigger interaction node is reached, the interaction engine receives the interaction command information. is sent, so that the aforementioned interaction engine can send the interaction command information corresponding to the aforementioned interaction. It executes the node and creates the interaction event. From a third perspective, this invention offers an application example of an in-vehicle software execution method. The method in question... This includes: the interaction script file sent by the receiver cloud; and the script sent by the logic engine. When interaction command information is received, the interaction node corresponding to the aforementioned interaction command information is identified. It executes and creates an interaction event. It sends the aforementioned interaction event to the logic engine, thus... The logic engine executes the function node corresponding to the aforementioned interaction event. From a fourth perspective, an application example of this invention presents an in-vehicle software execution device. The device in question... This includes: script file collection module: used to retrieve the script file associated with the in-vehicle software, The aforementioned script file contains many nodes of different types. Script file splitting module: the aforementioned script Depending on the node type in the file, the aforementioned script file can be a logic script file or an interactive script file. It is used to allocate the logic to the file. Script file distribution module: the aforementioned logic script file is used for logic. 2 It is used to send the aforementioned interaction script file to the interaction engine, so that the mentioned The logic engine uses the aforementioned logic script file, and the interaction engine uses the aforementioned interaction script file. It executes, during the execution process of the script file, the aforementioned interaction engine and the aforementioned logic engine script. They call each other based on the contents of the file. From a sixth perspective, an application example of this invention presents an in-vehicle software execution device. The device in question... It includes the following: script file retrieval module: for receiving the logic script file sent by the receiver cloud. It is used; the aforementioned logic script file contains the software ID. Script file execution module: mentioned In response to the trigger operation associated with the software ID, the aforementioned logic script file is executed. It is used. Command information sending module: When the trigger interaction node is reached, it is sent to the interaction engine. Interaction commands are used to send information so that the aforementioned interaction engine can then send the aforementioned interaction commands. It executes the interaction node corresponding to the command information and creates the interaction event. From a seventh perspective, an application example of this invention presents an in-vehicle software execution device. The device in question... This includes: script file retrieval module: retrieving the interaction script file sent by the receiving cloud. Used for: Script execution module: interaction command information sent by the logic engine. When received, the interaction node corresponding to the aforementioned interaction command information executes the interaction event. It creates the interaction event sending module: to send the aforementioned interaction event to the logic engine. It is used so that the aforementioned logic engine executes the function node corresponding to the mentioned interaction event. From the eighth point of view, an application example of this invention presents a tool. The tool in question is memory, one or more It includes the processor and one or more application programs. Here, one or more application programs are in memory. stored, when called by one or more processors, one or more processors implement this invention. It is enabled to execute the method presented by the instance. From a ninth perspective, an application example of this invention presents a computer-readable memory medium. The program code is stored in the aforementioned computer-readable memory medium; the program code in question When called by the processor, the processor executes the method presented by this invention's implementation instance. is activated. This invention provides an application example of an in-vehicle software execution method, device, vehicle, and memory environment, as mentioned. Depending on the node type, the method can separate the received script file into a logic script file and an interaction script file. It sends the logic script file to the logic engine and the interaction script file to the interaction engine separately, so The logic engine executes the logic script file, the interaction engine executes the interaction script file, and the script file... During execution, the interaction engine and the logic engine can call each other based on the content of the script file. Thus, it can achieve the following technical effects: 1) A dual-engine mode was designed, working in collaboration between the logic engine and the interaction engine, enabling system operation. It can increase efficiency and system robustness, allowing the in-vehicle software script to be executed by a single main engine. Execution of different types of tasks simultaneously, such as processing the control logic and interaction content of the main engine. This solves the problem of low system operational efficiency and system robustness due to its processing. 2) An interaction script containing the definitions of the interaction content section, to be included in the relevant script file of the in-vehicle software. By adding this file, you can expand the scope of the script, handling large amounts of complex software tasks. This can be supported and stems from the fact that the in-vehicle software does not include the interactive content portion of the script file. problems of software business types being insufficient and unable to meet complex software business requirements It can solve it. 3) An interaction engine specifically designed to execute the interaction script file of the in-vehicle software. using the interaction engine to manage and execute the interaction script files of the in-vehicle software. This can enable different in-vehicle software interaction scripts to be easily executed during the process. This can prevent potential interaction conflicts. 4) When implementing in-vehicle software via script files, developers only use the cloud. They can develop in-vehicle software by writing appropriate descriptions in the relevant script file of the in-vehicle software. This results in a short in-vehicle software development process and high development flexibility. Furthermore, in-vehicle software modifications... And when iteration is required, simply update the description content in the relevant script file of the in-vehicle software. That's sufficient; there's no need to update the engine, which also means adapting the in-vehicle software through changes and iterations. It strengthens. Reference Numbers 100 In-vehicle software execution systems 3 110 Vehicles 500 Vehicles 120 Cloud devices 200 In-vehicle software execution devices 300 In-vehicle software execution devices 400 In-vehicle software execution devices 210 Script file collection module 220 Script file splitting module 230 Script file distribution module 310 Script file import module 410 Script file import module 320 Script execution module 420 Script execution module 330 Command information sending module 430 Interaction event sending module 510 Memory 520 Processors 600 Computer-readable memory media 610 Program code Brief Description of the Figures To more clearly illustrate the technical solutions in the application example of this invention, let's look at the application example. We will briefly introduce the figures to be used in the explanation; as is clearly seen, the figures in the explanation below are these. These are some application examples of the invention, and technical people in this field can derive these forms without making a creative effort. They can obtain other forms. Figure 1 shows the structural design of the in-vehicle software execution system provided by an application example of this invention. It is a diagram. Figure 2 shows the flow of the in-vehicle software execution method provided by an application example of this invention. It is a diagram. Figure 3 shows the interaction interface provided by a sample application of this invention and the corresponding... It is a diagram of the explanations. Figure 4 shows the flow of the in-vehicle software execution method provided by a sample application of this invention. It is a diagram. Figure 5 shows the flow of the in-vehicle software execution method provided by an application example of this invention. It is a diagram. Figure 6 shows the flow of the in-vehicle software execution method provided by an application example of this invention. It is a diagram. Figure 7 shows the flow of the in-vehicle software execution method provided by an application example of this invention. It is a diagram. Figure 8 shows the time of the in-vehicle software execution method provided by an example application of this invention. It is a flowchart. Figure 9 shows the structural design of the in-vehicle software execution device provided by an application example of this invention. It is a diagram. Figure 10 shows the structural design of the in-vehicle software execution device provided by an application example of this invention. It is a diagram. Figure 11 shows the structural design of the in-vehicle software execution device provided by an application example of this invention. It is a diagram. 4 Figure 12 is a structural diagram of the device provided by an application example of this invention. Figure 13 shows a computer-readable memory medium provided by an application example of this invention. It is a structural diagram. Detailed Description of the Invention To help those in this technology field better understand this invention plan, below is an application of this invention. The technical solution of the application example of this invention, along with the relevant figures, is clearly and completely presented. It will be explained. Figure 1 shows the structural design of the in-vehicle software execution system provided by an application example of this invention. This is the diagram. It includes the in-vehicle software execution system 100, vehicle 110, and cloud device 120. Vehicle 110 and cloud device 120, The vehicle can communicate via the cloud communication link and perform in-vehicle software deployment. The vehicle 110 can be a gasoline vehicle or an electric vehicle; electric vehicle can be an electric vehicle, hybrid electric vehicle. or it could be a fuel cell vehicle. Vehicle 110 could include a logic motor and an interaction motor. Here, the logic motor It is the main working environment for the in-vehicle software script file; it is the vehicle-side parser of the script file. Logic the engine, script lifecycle management, script execution, and vehicle service. the in-vehicle environment to perform calls to Service Oriented Architecture (SOA) functions It can be placed on the control panel. The interaction engine is the interaction content part of the in-vehicle software script file. It is the work environment, that is, the analyzer of the interactive content part, for example, interacting with users. It is used for various graphical interfaces. The interaction engine handles the front-end rendering of interaction content, the interaction itself. in-vehicle for managing the lifecycle of content and manipulating interactive content. It can be placed in the environment's control panel. During the script execution process, the logic engine and interaction occur. The engines can call each other by working together. Cloud devices 120 reside in the cloud and are used to design and generate the in-vehicle software script. Cloud Device 120 could be a cloud server, and cloud device 120 could include script file editing tools; these tools among them are NOTEPAD++ editor, VIM editor, GNU EMACS editor, SUBLIME TEXT editor, ATOM editor, Tools such as PSPAD editor, GEANY editor, Visual Studio Code editor, JEDIT editor, and NETBEANS editor. It can be found. Figure 2 is a flowchart of the in-vehicle software execution method provided by an application example of this invention. The aforementioned in-vehicle software execution method is on cloud device 120 or in-vehicle software execution device 200. It is applicable. The aforementioned in-vehicle software execution method includes steps s110 through s130. It may include. Step s110 retrieves the script file corresponding to the in-vehicle software; the script file contains many nodes of different types. includes. The in-vehicle software script file typically contains scene objects, interaction objects, and service sets. It can be abstracted from the tripartite structure of its objects. For example, for the intelligent scene service product called "Heavy Rain Mode", The relevant script file, "Determining that it is raining heavily while driving," has a scene object that "detects the product to the user." a pop-up interaction object asking whether to run it and options like "turn on wipers" and / or "turn on warning lights" It can be broken down into service set objects that contain many service actions. To accommodate complex business logic, the application example of this invention involves adding more nodes to a three-element structure. It derives. That is, the script file in the application example of this invention may contain several nodes of the following three types: Node type 1: Function node, used to define content related to vehicle control, scene decision, and vehicle cloud services. It is used for this purpose. The function node can be marked with tags such as "scenenode", "servicenode", "tspservicenode". Node type 2: Interaction node defines content related to human-machine interaction. The interaction node, For example, it can be marked with the "interactionnode" tag. The interaction node defines the interaction structure, interaction style, It can be used to describe the interaction state, interaction behavior, and interaction event. The interaction structure refers to the specific configuration and arrangement of elements within an interaction node. Each element has a unique tag name, for example, "text" for a text element, "button" for a button element. The elements, Specific modules can be freely nested together to create and ultimately form the interaction interface. For example, in Figure 3, the rectangular box on the left represents the interaction interface, and the rectangular box on the right represents the aforementioned interface. It represents the part of the script file corresponding to the interaction interface. The interaction interface consists of the first group of structures and the second group of structures. It consists of two structures: the first group structure includes three elements: the text title, the text content, and the image. The second group of structures includes two elements, such as button A and button B. Interaction style refers to the style properties of an element. For example, the color property, font size. This property refers to the internal padding property. Interaction status refers to the state or animation properties of an element. Interactional behavior refers to the interactive behavioral characteristics of elements. For example, the touch (tap) property. Long press function, drag function. An interaction event refers to a specific interaction event resulting from the interaction behavior of an item. For example, The interaction event can be represented using the "event" property. Node type 3: Business logic node defines the connection relationships of all nodes. Business logic The node can be marked with a label such as "connectionnode". The business logic node is the connection node. It defines the connection relationship between two nodes through the object and consequently controls the operation of all in-vehicle software. It forms the logic. It should be noted that the function node, interaction node, and operating logic in the application example of this invention are... The node contains specific textual content, the function referred to later in the application example of this invention. To run a node or interaction node means to run the text content contained within those nodes. income. Developers can implement in-vehicle software solutions at any stage of the vehicle's lifecycle via a cloud device. They can design and modify the software's script file. The cloud device allows developers to work through the cloud device. It can obtain the in-vehicle software script file that it designed or modified; this script file is of the three types mentioned above. It can contain numerous nodes and the software identifier (Identity Document, abbreviated as ID) of the in-vehicle software. The software ID of the in-vehicle software is used to identify the in-vehicle software. Step S120, depending on the node type of the node in the script file, converts the script file into a logic script file and The interaction is separated into a script file. In some implementations, the node tags of the node in the script file can be retrieved. Based on the node tag... The node type is determined. Specifically, the node type associated with the function node tag is the function node type. The interaction node type associated with the interaction node tag is the same as the node type associated with the business logic node tag. The node type can be defined as the operating logic node type. In some implementations, if the node type belongs to the interaction node type, then the mentioned node It is designated as the interaction node and allocated to the interaction script file. In some implementations, if the node type belongs to the function node type, then the mentioned node function It is designated as a node and allocated to the logic script file. In some implementations, if the node type belongs to the operating logic node type, then the node in question... It is designated as the business logic node and allocated to the logic script file. It should be noted that the logic script file obtained after the in-vehicle software script file is separated is a It may include one or more function nodes and one or more business logic nodes; the interaction script is a or it may contain more interaction nodes. It should also be noted that the logic script and interaction script in the application example of this invention... They have the same software ID; the logic script file and the interaction script file have the same software ID. It is used to indicate that it belongs to the contents of the script file of the same in-vehicle software, which is then used in subsequent calls. Script call errors when calling the logic script file and the interaction script file of the same in-vehicle software. prevents. In some implementations, the in-vehicle software writes the nodes sequentially according to their order in the script file. The in-vehicle software can allocate script files, for example, if the write order of the nodes is from node1 to node5, It can separate nodes 1 through 5 in sequence. In some implementations, to improve the efficiency of script file splitting, interaction nodes are often used. the number is less than the total number of function nodes and business logic nodes, and the interaction nodes it contains Considering that the content is less than the content contained in the function node and the business logic node, the node Depending on the type, you can separate the in-vehicle software script files accordingly; for example, first the interaction node, then the interaction script. It allocates the nodes to a file, then allocates the remaining nodes to a logic script file. Step s130 sends the logic script file to the logic engine and the interaction script file to the interaction engine. Thus, the logic engine executes the logic script file, and the interaction engine executes the interaction script file. During execution, the interaction engine and the logic engine call each other based on the contents of the script file. 6 For the interaction engine and the logic engine to call each other, the logic engine interaction node must be present. when triggered, or when it is triggered, the logic engine sends specific instruction information to the interaction engine. This means calling the interaction engine when needed. The interaction engine is activated by the logic engine. When called, it executes the aforementioned interaction node and generates the corresponding interaction event, the interaction engine. It reports the interaction event back and uses the interaction event to call the logic engine. In some implementations, after the in-vehicle software script file is separated, the logic script file is separated in turn. It sends the interaction script file to the logic engine. In some implementations, after separating the interaction script file from the in-vehicle software script file, First, it sends the interaction script file to the interaction engine, then the in-vehicle software extracts the logic from the script file. After separating the script file, the logic sends the script file to the logic engine. The in-vehicle software execution method provided by this invention’s application example has the following technical effects: can provide: 1) A dual-engine mode was designed, working in collaboration between the logic engine and the interaction engine, enabling system operation. It can increase efficiency and system robustness, allowing the in-vehicle software script to be executed by a single main engine. Execution of different types of tasks simultaneously, such as processing the control logic and interaction content of the main engine. This solves the problem of low system operational efficiency and system robustness due to its processing. 2) An interaction script containing the definitions of the interaction content section, to be included in the relevant script file of the in-vehicle software. By adding this file, you can expand the scope of the script, handling large amounts of complex software tasks. This can be supported and stems from the fact that the in-vehicle software does not include the interactive content portion of the script file. problems of software business types being insufficient and unable to meet complex software business requirements It can solve it. 3) An interaction engine specifically designed to execute the interaction script file of the in-vehicle software. using the interaction engine to manage and execute the interaction script files of the in-vehicle software. This can enable different in-vehicle software interaction scripts to be easily executed during the process. This can prevent potential interaction conflicts. 4) When implementing in-vehicle software via script files, developers only use the cloud. They can develop in-vehicle software by writing appropriate descriptions in the relevant script file of the in-vehicle software. This results in a short in-vehicle software development process and high development flexibility. Furthermore, in-vehicle software modifications... And when iteration is required, simply update the description content in the relevant script file of the in-vehicle software. That's sufficient; there's no need to update the engine, which also means adapting the in-vehicle software through changes and iterations. It strengthens. To make it easier to understand, an example from Figure 4 illustrates the in-vehicle software execution method shown in Figure 2. I am presenting this for explanation. In-vehicle software developers create the in-vehicle software script file on a cloud device. It can edit, the cloud device can generate the script file for the relevant in-vehicle software, as shown in Figure 4, the script The file contains function nodes 1, 3, 4, interaction nodes 2 and 5, and the operating logic node. Depending on the node type, Script files can be divided into logic script files and interaction script files. Here, the logic script file functions The main network contains nodes 1, 3, and 4, as well as the business logic node, while the interaction script file contains interaction nodes 2 and 5. After the script file is separated, the cloud device sends the logic script file to the logic engine, and the interaction script file... by sending it to the interaction engine, the logic engine and the interaction engine's in-vehicle software work together. It can enable him to accomplish it. Figure 5 illustrates the process of in-vehicle software execution method provided by an application example of this invention. It shows the diagram. The aforementioned in-vehicle software execution method follows the logic in tool 110 mentioned above. The engine is applicable to the logic motor in the vehicle's in-vehicle software execution device 300 or vehicle 500. The aforementioned vehicle... The software execution method may include the following steps, from step S210 to step S230. Step S210, the logic script file sent by the receiving cloud, the logic script file software ID. includes. As previously mentioned, after the cloud device separates the logic script file from the in-vehicle software script file... Then, it can send the logic script file to the vehicle side, specifically to the logic engine in the vehicle. The logic engine, the receiver It can receive the logic script file sent by the cloud device. Step S220 executes the logic script file in response to the trigger operation associated with the software ID. The user or another electronic control unit can execute the triggering action of the in-vehicle software. For example, when the user clicks the in-vehicle software application program (APP) icon or an electronic control unit, vehicle When the in-vehicle software sets the start flag as the first special character (e.g., 1), the in-vehicle software triggers the system. 7 The transaction is considered completed. In some implementations, the triggering process for the in-vehicle software is performed by triggering the logic engine as described above. It sends the software ID of the in-vehicle software corresponding to the operation. The logic engine associates the software ID with the software ID. In response to the trigger operation, it finds the logic script file that matches the software ID, and the found logic script It executes the file. Specifically, it sequentially executes function nodes according to the order of function nodes in the logic script file. can be carried out as follows. In some implementations, the triggering process for the in-vehicle software is performed by triggering the logic engine as described above. It sends the software ID and function node ID of the in-vehicle software corresponding to the operation. The function node ID is: It is used to define various function nodes. The logic engine, in response to the aforementioned triggering operation, It finds the logic script file that matches the software ID, and then uses the function node ID in the found logic script file to... It finds the matching function node and executes the found function node. Step S230, when the interaction node is triggered, sends the interaction command information to the interaction engine, Thus, the interaction engine executes the interaction node corresponding to the interaction command information, thereby processing the interaction event. It produces. If human-machine interaction is required during the execution process of the function node in the logic script file. In other words, the interaction node is considered triggered when user input interaction information is needed. This In this case, the interaction node that is triggered is determined based on the actual need for interaction. For example, the actual interaction If the need is to ask the user for permission to run function A, the triggered interaction node will provide confirmation in the interaction interface. This is the interaction node used to display the accept and reject buttons. If the user clicks the accept button, It is assumed that the user agrees to perform function A, in which case the logic engine corresponds to function A. The function node 'a' can be executed. If the user clicks the decline button, the user can no longer execute function 'a'. It is assumed that it does not agree to perform the action, in which case the logic engine function node corresponding to function a. It does not execute 'a', but it executes the other function nodes. In some implementations, when the interaction node is triggered, the logic engine is sent to the interaction engine. You can send interaction command information, so the interaction engine can create an interaction corresponding to that interaction command information. It executes the node and generates the interaction event. Specifically, the aforementioned interaction command information is the software ID, interaction node ID and interaction content parameters (i.e., which should be displayed in the interaction interface) The interaction engine may contain information (for example, the accept button and the decline button in the example above). When it receives interaction command information, it can search for the interaction script file corresponding to the software ID, and if found... In the interaction script file, you can find the interaction node corresponding to the interaction node ID and interact. It executes the interaction node and creates an interaction event based on the content parameters. For example, the interaction event In the example above, “the user clicked the accept button” or “the user clicked the decline button” it could be. After the logic engine sends the interaction command information, the interaction is reported back from the interaction engine. It can listen to the event, thus allowing the function node corresponding to the interaction event to continue executing. For example, If the interaction event is "user clicked the accept button", the function node corresponding to the interaction event is the one above. In the example, the function node could be A. The in-vehicle software execution method provided by this invention’s application example corresponds to the software ID. It can execute the logic script file sent from the cloud in response to the incoming trigger operation and interact with it. When the node is triggered, it sends interaction command information to the interaction engine, thereby activating the interaction engine. It can call upon, and through the collaboration of the logic engine and interaction engine, improve system operational efficiency and system robustness. It can increase the in-vehicle software script file being executed by a single main engine and controlled by the main engine. Because the system handles different types of tasks simultaneously, such as processing logic and interaction content, it operates efficiently. This can solve the problem of low efficiency and system robustness. Figure 6 shows the flowchart of the in-vehicle software execution method provided by the application example of this invention. This shows that the aforementioned in-vehicle software execution method is the logic engine in vehicle 110, mentioned above, in-vehicle. This is applicable to the logic engine in the software execution device 300 or vehicle 500. The aforementioned vehicle software execution device. The method may include steps S310 through S370. Step S310, the receiver receives the logic script file sent from the cloud, the logic script file software ID. includes. Step S320 executes the logic script file in response to the trigger operation corresponding to the software ID. Step S330: When the interaction node is triggered, the interaction command information is sent to the interaction engine. By sending this information, the interaction engine enables the interaction node to execute the interaction command corresponding to the command information. and creates an interaction event. 8 Here, for specific explanations from step S310 to step S330, please refer to step S210 above. See S230. Step S340 listens for the interaction event. In this invention's application example, the interaction event software ID is the interaction node of the interaction node. It includes the identity, the trigger element ID, and the interaction behavior event. Here, the interaction node ID is mentioned. It indicates the side to which the interaction event was sent, i.e., which interaction node sent the interaction event. It indicates that it has been sent. The triggering element is the element that is part of the interaction structure at the mentioned interaction node. This refers to, for example, a text element, button element, or image element. The interaction behavior event is triggered by the element. They are generated based on user actions, for example, the accept button and the reject button in the example mentioned. It functions as a trigger element; when the user clicks the accept button, the interaction behavior event is "user accept". "He clicked the button" is generated. After sending interaction command information, the logic engine listens for interaction events. Step S350: When an interaction event is detected, the logic script file contains the function corresponding to the interaction event. He finds the knot. In certain implementation modes, when an interaction event is detected, the interaction event can be analyzed and the interaction can be resolved. The event may include the software ID, interaction node ID, trigger element ID, and interaction behavior event. Logic based on software ID, interaction node ID, trigger element ID, and interaction behavior event. You can find the relevant function node in the script file. Specifically, the logic script file corresponding to the software ID can be found; in the found logic script file... The function node of the triggered interaction node can be found, followed by the trigger element after the mentioned function node. The function node corresponding to the identity and interaction behavior event can be found. Step S360 executes the function node corresponding to the interaction event in the logic script file. Step S370, in response to the exit operation corresponding to the software ID, the logic script file terminates its execution. After the in-vehicle software is executed, the user or other electronic control units can access the in-vehicle software. The user can perform an exit operation. For example, the user clicks the exit button in the in-vehicle software or a button. The electronic control unit sets the vehicle software's start flag as a second special character (e.g., 0), These situations are considered exit procedures for the in-vehicle software. In certain implementations, the output process for the in-vehicle software is sent to the logic engine to process this output. It sends the software ID of the corresponding in-vehicle software. The logic engine outputs the corresponding software ID. In response to the operation, the logic script corresponding to the software ID is executed in the logic script file being run. It finds the file and terminates the execution of the found logic script file. Compared to the in-vehicle software execution method shown in Figure 5, this invention's application example demonstrates the following: The provided in-vehicle software execution method can listen for the interaction event sent from the interaction engine, Execute the relevant function node based on the interaction event, thereby executing the functions triggered by the user's interaction action. It can accomplish this. Additionally, the logic script file can be started to execute in response to the trigger operation. By terminating the execution of the logic script file in response to the exit operation, the logic engine in-vehicle It can manage the software's lifecycle (from start to finish). The image shows an example of the in-vehicle software execution method provided by an application of this invention. It shows the diagram. The aforementioned in-vehicle software execution method, the interaction engine within the aforementioned vehicle 110, for the in-vehicle software execution device 400 or the interaction engine inside vehicle 500, which will be discussed below. It is applicable. The aforementioned in-vehicle software execution method follows these steps from step 410 to step 430: It may include. Step S410, interaction script file from the receiving cloud. As previously mentioned, the cloud device interacts with the in-vehicle software script from the script file. After separating, you can send the interaction script file to the vehicle side, specifically to the interaction engine on the vehicle side. You can send the interaction script file. The interaction engine receives the interaction script file from the receiving cloud device. can get it. Step S420, when interaction command information is received from the logic motor, the interaction command information is converted into... It executes the corresponding interaction node and creates the interaction event. In some implementations, when interaction command information is received from the logic engine, the interaction command 9 The information can be parsed and includes software ID, interaction node ID and interaction content parameters (i.e. Information that should be displayed in the interaction interface, such as the mentioned interaction structure, interaction style, interaction (The state, interaction animations) are obtained. In the interaction script file, the software ID and interaction node An interaction node corresponding to its identity is found. The interaction node is determined according to the interaction content parameters. It is carried out. Specifically, the interaction script file corresponding to the software ID can be found; the found interaction script The file contains the interaction node corresponding to the interaction node ID. The found interaction command... The interaction node corresponding to the information can be executed, the interaction node according to the interaction content parameters. The corresponding interaction interface is displayed, along with interaction interface trigger elements (e.g., buttons, images, or (contains texts). In response to user actions performed on the trigger element, it displays texts corresponding to the user action. An interactive behavioral event is created. Step S430 sends the interaction event to the logic engine, so the logic engine responds to the interaction event. Executes the incoming function node. The in-vehicle software execution method provided by this invention’s application example comes from the logic engine. When interaction script information is received, the interaction script information in the interaction script file from the cloud is used. It can execute the corresponding interaction node, create an interaction event, and send the interaction event to the logic engine. It sends the interaction event, so the logic engine executes the function node corresponding to the user interaction event. It can perform the functions it triggers through the process. To execute the interaction script file of the in-vehicle software... Thanks to its specially designed interaction engine, the interaction engine converts the in-vehicle software's interaction script file It can manage and execute, which involves the execution of various in-vehicle software interaction script files. It prevents potential interaction conflicts. Figure 8 shows the time of the in-vehicle software execution method provided by a sample application example of this invention. It shows the flowchart. The aforementioned in-vehicle software execution method is the one mentioned in tool 110 or as mentioned below. This method is applicable to the 500. Specifically, the aforementioned in-vehicle software execution method follows the steps one through the other. It may include steps up to five. Step one starts the logic engine in response to the trigger operation. The trigger operation is the aforementioned trigger. It sends the software ID of the in-vehicle software corresponding to the operation to the logic engine. Step Two, the logic engine finds the logic script file that matches the software ID of the on-board software, and The logic script found executes the function nodes in the file. Step Three: When the target interaction node is triggered, the logic engine sends command information to the interaction engine. The aforementioned command information refers to the software ID of the in-vehicle software, and the interaction node of the target interaction node. It includes identity and interaction content parameters. Step Four, the interaction engine finds the interaction script file that matches the software ID of the in-vehicle software, It finds the target interaction node that matches the interaction node ID in the interaction script file that is located, and The interaction event is generated by executing the target interaction node found based on the interaction content parameters. Step Five: The interaction engine sends the interaction event to the logic engine. This interaction event is in-vehicle. the software ID, the target interaction node's interaction node ID, the trigger element ID, and Interaction involves a behavioral event. Step Six: When the logic engine detects an interaction event, the on-board software matches the logic with the software ID. In the script file, the target interaction node's interaction node ID, trigger item ID, and interaction are specified. It finds the target function node that matches the behavioral event. Step Seven: The logic engine executes the target function node until step three triggers the target interaction node. It loops between step seven or moves to step eight in response to the exit operation. The aforementioned exit operation is logic. It sends the software ID of the in-vehicle software corresponding to this output operation to its engine. Step Eight, in response to the logic engine output process, the on-board software matches the logic ID. Terminates the execution of the script file. An important point to note is that there are sections not explained in detail in this example application. Please refer to the relevant sections; they will not be repeated here. Figure 9 shows the structural design of the in-vehicle software execution device provided by an application example of this invention. It shows the diagram. The aforementioned in-vehicle software execution device is 200, and the aforementioned cloud device is 120. Applicable. In-vehicle software execution device 200, script file collection module 210, script file splitting module It may contain modules 220 and 230 of the script file distribution module. Script file collection module 210 is used to retrieve the script file for the in-vehicle software; the aforementioned script The file contains numerous nodes of various types. Script file splitting module 220, according to the node type of the nodes in the mentioned script file, It is used to separate the script file into a logic script file and an interaction script file. The aforementioned logic script... The file and the aforementioned interaction script file have the same software ID. Script distribution module 230 sends the aforementioned logic script to the logic engine and the aforementioned It is used to send the interaction script file to the interaction engine, thus the aforementioned logic engine. The logic script mentioned, the interaction engine mentioned, executes the interaction script mentioned, the script During the execution of the file, the aforementioned interaction engine and the aforementioned logic engine script file They call each other according to the content. In some implementations, the script file splitting module 220, if the node's node type is interaction node If it belongs to that type, it designates the mentioned node as the interaction node and adds the interaction node to the interaction script file. It separates and the aforementioned interaction node is used to define content related to human-machine interaction. In some implementations, the script file splitting module 220, if the node's node type matches the function node type. If it belongs, it designates the mentioned node as a function node and allocates the function node to the logic script file, the mentioned The function node is used to define content related to vehicle control, scene decisions, and vehicle cloud services. In some implementations, the script file splitting module 220, if the node's node type operating logic If it belongs to a node type, it identifies the mentioned node as an operating logic node and designates the operating logic node as such. The logic script separates the node into files, where the aforementioned business logic node defines the connection relationships of all nodes. It is used for. In some implementations, the script file splitting module 220 splits the nodes in the aforementioned script file. It also retrieves node tags. Based on the node tag, it determines the node type. Figure 10 shows the structural design of the in-vehicle software execution device 300, provided by an application example of this invention. It shows the diagram. The in-vehicle software execution device mentioned is 300, the logic engine in vehicle 110, or the one in vehicle 500. Applicable for logic engines. In-vehicle software execution device 300, script file retrieval module 310, script The file may contain execution module 320 and instruction information sending module 330. Script file retrieval module 310 is used to retrieve the logic script file from the receiving cloud, as mentioned. The logic script file contains the software ID. Script execution module 320 responds to the trigger operation corresponding to the mentioned software ID. The logic mentioned is used to execute the script file. The command information sending module 330 sends the interaction command to the interaction engine when the interaction node is triggered. It is used to send information so that the aforementioned interaction engine receives the aforementioned interaction command information. It executes the corresponding aforementioned interaction node and creates the interaction event. In some implementations, the script execution module 320 is also used to listen for the aforementioned interaction event. It is used. When the mentioned interaction event is listened to, the mentioned interaction is found in the mentioned logic script file. It finds the function node corresponding to the event. This corresponds to the aforementioned interaction event in the logic script file. Executes the corresponding function node. In certain implementation modes, the script execution module 320 resolves the aforementioned interaction event. It is also used for, and as a result of this analysis, the aforementioned software ID found within the mentioned interaction event is determined. Obtain the interaction node ID, trigger element ID, and interaction behavior event of the aforementioned interaction node. The aforementioned interaction behavior event is generated based on user actions performed on the triggering element. The mentioned software ID, the mentioned interaction node ID, the mentioned trigger element ID, and the mentioned According to the interaction behavior event, the software ID mentioned in the aforementioned logic script file, interaction node ID, the mentioned trigger element ID, and the interaction behavior event corresponding to the mentioned interaction. It finds the function node. In certain application modes, the script execution module 320, also with the software ID of the in-vehicle software. In response to the associated exit operation, the aforementioned logic is used to terminate the execution of the script file. Figure 11 shows the structural design of the in-vehicle software execution device 300, provided by an application example of this invention. It shows the diagram. The in-vehicle software execution device mentioned is 400, the interaction engine in vehicle 110 or vehicle 500. It can be used for the interaction engine inside. In-vehicle software execution device 400, script file import module 410, The script execution module may include module 420 and interaction event sending module 430. Script file retrieval module 410 is used to retrieve the interaction script file from the receiving cloud. 11 Script execution module 420, when receiving interaction command information from the logic engine, the relevant It generates an interaction event by executing the interaction node corresponding to the interaction command information. Interaction event sending module 430 sends the aforementioned interaction event to the aforementioned logic engine. Thus, the aforementioned logic engine executes the function node corresponding to the mentioned interaction event. In certain implementation modes, the script execution module 420 contains the aforementioned interaction command information. The solutions include the mentioned software ID, the mentioned interaction node ID, and the mentioned interaction content. It obtains the parameters. In the aforementioned interaction script file, the mentioned software ID and the mentioned It finds the interaction node that matches the interaction node ID. Based on the mentioned interaction content parameters. It executes the aforementioned interaction node. In certain implementation modes, the script execution module 420 contains the aforementioned interaction command information. executes the corresponding interaction node, the interaction interface corresponding to the mentioned interaction node. It shows that the aforementioned interactive interface includes the trigger element. It responds to the user action on the trigger element. This generates an interaction behavior event corresponding to the user action. The in-vehicle software execution device presented in the application example of this invention is capable of executing 200 in-vehicle software. Up to 400 devices can implement the in-vehicle software execution method provided by this invention. The aforementioned device and The specific operating processes of the modules relate to the in-vehicle software execution method in the application example of this invention. These may refer to processes, which will not be explained again here. The connections between the modules shown or discussed in the application example presented by this invention are direct. or indirectly through certain interfaces, devices or modules, these connections are electrical, The application of this invention, whether mechanical or otherwise, does not impose any limitations in this regard. Furthermore, in the application example of this invention, the various functional modules can be integrated into a single processing module, They can exist separately in physical form, or two or more modules can be integrated into a single module. (mentioned) The integrated module can be implemented as a hardware module or as a software function module; this invention's application This example does not impose any limitations in this regard. Figure 12 shows the structural schematic of the device provided by an application example of this invention. The device is the 500. The vehicle in question is the same as the 110 and also features the aforementioned logic engine and interaction engine. 500 may include memory 510, one or more processors 520, and one or more application programs; where a or more application programs can be stored in memory 510 and powered by one or more processors 520. When called, the aforementioned in-vehicle software execution method presented by the application example of this invention. One or more processors can be configured to enable the 520 to operate in such a way as to accomplish this. The 520 processor may include one or more processing cores. The 520 processor can support various parts of the 500 tool. By using various interfaces and lines to connect them, the commands and programs stored in memory 510, The tool is used to run or execute code sets or instruction sets and retrieve data stored in memory 510. It is used to perform various functions of the 500 and to process data. Processor 520, Digital Signal Processing (DSP), Field Programmable Gate Arrays Field-Programmable Gate Array (FPGA), Programmable Logic Array (PLA), etc. It can be implemented in at least one hardware form. Processor 520, central processing unit (CPU), graphics processing unit (GPU) The unit can integrate one or more combinations of components such as the CPU, GPU, and modem. Here, the CPU primarily functions as the operating system. The GPU processes the system, user interface, and application programs. It handles rendering of display content and... It is responsible for the drawing. The modem handles wireless communication. As can be understood, the modem in question also has a 520 processor. It may not be integrated internally; it may be carried out via a separate communication chip. Memory 510 consists of Random Access Memory (RAM) and Read-Only Memory. Memory (ROM) may contain 510 commands, programs, codes, code sets, or instruction sets. It can be used for storage. Memory 510 can include program storage and data storage. Here, Program storage space, for the operating system to execute commands, to perform at least one function. The commands can store instructions for performing the various method implementation examples mentioned. Data The storage space can store data generated as the vehicle is used 500 times. Figure 13 shows a computer-readable memory medium provided by an application example of this invention. This is the structural diagram. The program code 610 is within the aforementioned computer-readable memory medium 600. The aforementioned program code 610 is stored; when called by the processor, the processor implements this invention. to enable the execution of the aforementioned in-vehicle software execution method presented by the example It is structured. 12 Computer-readable memory medium 600, flash memory, electrically erasable programmable memory. Read-only memory (Electrically-Erasable Programmable Read-Only Memory, EEPROM) is programmable memory that can be erased. Read-only memory (Erasable Programmable Read-Only Memory, EPROM) is an electronic hard drive or ROM. It can be one of the memory types. In certain implementations, computer-readable memory media 600, Non-Transitory Computer-Readable Storage Medium (For short, it includes Non-TCRSM). Computer-readable memory medium 600, which executes any step of the aforementioned method. Program code 610 has storage space. These program codes 610 are used for one or more computer programs. It can be read from the software or written into one or more computer programming software programs. Program codes 610 It can be compressed appropriately. In summary, the application example of this invention encompasses in-vehicle software execution methods, devices, vehicles, and memory media. and relates to the field of in-vehicle software technology. The method mentioned involves in-vehicle systems containing numerous nodes of different types. This involves obtaining the script file corresponding to the software. Depending on the node type, the script file can be a logic script. It is divided into logic script files and interaction script files. The logic script file goes to the logic engine, and the interaction script file goes to the interaction engine. The logic engine sends the logic script file to the interaction engine, and the interaction engine sends the interaction script file to the logic engine. It executes the script file; during the execution of the script file, the interaction engine and the logic engine execute the script file. They interact with each other according to their content, which improves system operational efficiency, system robustness, and It expands the scope of work for script files, supports numerous complex software tasks, and enables various in-tool software interactions. It prevents interaction conflicts encountered during the execution of script files, and facilitates in-vehicle software development. It provides good flexibility and adaptability for change iterations. Finally, it should be noted that: The above application examples are intended to illustrate the technical solutions of this invention. has been used, but not limited to, previous application examples. This invention is described in detail by referring to previous application examples. Although explained in this way, technical experts in the field should understand that: Previous application examples have shown that... Technical solutions may be modified, or some technical specifications may be replaced with equivalents. These changes or modifications, the essence of the relevant technical solutions, the spirit of each application example of this invention's technical solution and It should not be excluded from the scope.
Claims
13 Requests 1. It is an in-vehicle software execution method, and its characteristics include the following: Obtaining the script file corresponding to the in-vehicle software; the aforementioned script file comes in many different types. It contains a number of nodes; Depending on the node type of the node in the mentioned script file, the mentioned script file can be used as a logic script. separating them into a file and an interaction script file; The aforementioned logic script file is sent to the logic engine, and the aforementioned interaction script file is sent to the interaction engine. sending to the engine, the logic script file of the mentioned logic engine, the mentioned interaction to enable the engine to execute the aforementioned interaction script file, script execution During this process, the contents of the script file for the aforementioned interaction engine and the aforementioned logic engine. interacting with each other in that direction.
2. This is a method that conforms to Request 1, and its characteristic is that it determines the node type of the node in the aforementioned script file. According to this, the aforementioned script file should be separated into a logic script file and an interaction script file. It includes, and contains the following: If the node type belongs to the interaction node type, then the mentioned node is considered an interaction node. It identifies, allocates the interaction node to the interaction script file, and the aforementioned interaction node is a human-machine interface. It is used to describe content related to interaction; If the node type belongs to the function node type, then the node in question is designated as a function node, and The function node is dedicated to logic scripting; the aforementioned function node controls vehicle control, scene decisions, and vehicle management. It is used to describe content related to cloud services; If the node type's operating logic belongs to the node type's operating logic, then the aforementioned node operating logic It is designated as a node, and the business logic node is allocated to the logic script file; the aforementioned business The logic node is used to define the connection relationships of all nodes.
3. A method that conforms to claim 1 or 2, and whose characteristic is that the node in the mentioned script file is the node. Depending on the type, the aforementioned script file is separated into logic script file and interaction script file. First, the method mentioned also includes the following: Obtaining the node tags of the node in the aforementioned script file; Determine the node type based on the node label.
4. This is a method that conforms to Claim 1, and its characteristic is the aforementioned logic script file and the aforementioned interaction. The script file has the same software ID.
5. It is an in-vehicle software execution method, and its features include the following: The logic script file received according to any request specified in requests 1 through 4, the aforementioned logic script The file contains the software ID; the aforementioned logic script in response to the triggering action corresponding to the mentioned software ID Execute the file; When the interaction node is triggered, interaction command information is sent to the interaction engine, so that the aforementioned interaction engine, the aforementioned interaction corresponding to the aforementioned interaction command information It executes the node and creates the interaction event.
6. This is a method that conforms to Request 5, and its characteristic is that it provides interaction command information to the interaction engine. After being sent, the aforementioned method also includes the following: listening to the aforementioned interaction event; When the aforementioned interaction event is listened to, the aforementioned interaction is found in the aforementioned logic script file. Find the function node corresponding to the event; the function node in the aforementioned logic script file that corresponds to the mentioned interaction event execute.
7. This is a method that conforms to Request 6, and its characteristic is the interaction mentioned in the aforementioned logic script file. 14 Finding the function node corresponding to the event involves the following: to analyze the aforementioned interaction event, the aforementioned software involved in that interaction event its identity, the interaction node ID of the mentioned interaction node, the trigger element ID, and obtaining the interaction behavior event; the aforementioned interaction behavior event, on the triggering element It is generated based on user actions; the mentioned software ID, the mentioned interaction node ID, the mentioned trigger element ID, and Based on the aforementioned interaction behavior event, the software ID mentioned in the logic script file, the mentioned interaction node ID, the mentioned trigger element ID, and the mentioned interaction behavior It searches for the function node corresponding to the event.
8. Claim 5 through 7 is a suitable method for any claim, and its characteristic is that the mentioned method This includes the following: the aforementioned logic script file in response to the exit operation associated with the mentioned software ID It involves terminating its execution.
9. An in-vehicle software execution method, The 10th feature includes the following: Request 1 retrieves the interaction script file specified in any method from 1 to 4; When interaction command information is received from the logic engine, the aforementioned interaction command information is... It generates the interaction event by executing the corresponding interaction node; It sends the aforementioned interaction event to the aforementioned logic engine, so that the aforementioned logic engine, 5 It executes the function node corresponding to the aforementioned interaction event.
11. This is a method that conforms to Request 9, and its feature is that the mentioned command information, software ID, and interaction It includes the node ID and interaction content parameters; the aforementioned interaction command information. It executes and includes the corresponding interaction node: The mentioned interaction analyzes the command information, the mentioned software ID, and the mentioned interaction 10. It obtains the node ID and the aforementioned interaction content parameters; In the aforementioned interaction script file, the mentioned software ID and the mentioned interaction node It finds the interaction node that matches its identity; The aforementioned interaction node executes the mentioned interaction node according to the mentioned interaction content parameters.
12. A method that conforms to request 9 or 10, and whose characteristic is that it corresponds to the aforementioned interaction command information. It generates the interaction event by executing the incoming interaction node, and includes: The interaction node that corresponds to the mentioned interaction command information executes the mentioned interaction. It shows the interaction interface corresponding to the node, and the aforementioned interaction interface contains the trigger element; in response to the user action on the aforementioned trigger element, corresponding to the user action Interaction produces a behavioral event. 20 13. It is an in-vehicle software execution device, and its features include the following: The script file collection module is used to retrieve the script file for the in-vehicle software; the aforementioned script The file contains numerous nodes of different types; The script file splitting module splits the specified script according to the node type of the node specified within the script file. It separates the file into a logic script file and an interaction script file; 25 The script distribution module distributes the specified logic script to the logic engine, along with the specified interaction. By passing the script file to the interaction engine, the specified logic engine processes the specified logic script file. This ensures that the specified interaction engine runs the specified interaction script file. When executed, the specified interaction engine and the specified logic engine interact with each other according to the content of the script file. communicates. 30 14. It is an in-vehicle software execution device, and its features include the following: The script file import module retrieves the logic script file specified in any of prompts 1 through 4. The specified logic script file contains the software ID; The script execution module responds to the trigger operation associated with the specified software ID. It executes the specified logic script file; The command information sending module sends commands to the Interaction engine when the interaction node is triggered. It sends interaction command information, so that the specified interaction engine can use the specified interaction command 5. It executes the specified interaction node according to the information, and generates an interaction event.
15. It is an in-vehicle software execution device, and its features include the following: The script import module imports the interaction script specified in any of prompts 1 through 4. he / she will receive; The script execution module receives interaction command information sent by the logic engine. 10 When received, it executes the specified interaction node according to the specified interaction command information. It produces an interaction event; The interaction event sending module sends the specified interaction event to the specified logic engine. In this way, the specified logic engine executes the function node appropriate to the specified interaction event.
16. It is a vehicle, and its feature is: 15 memory is found; There is one or more processors; There is one or more application programs, one or more specified application programs stored in the specified memory, one or more specified application programs, one or more specified applications When called by the processor, it executes the method specified in any of prompts 1 through 11. It controls one or more specified processors.
17. It is a computer-readable memory medium whose characteristics include the following: The program code is found; when the specified program code is called by the processor, the processor executes prompts 1 through 11. It is directed to execute the method specified in any of them.