Visual arrangement method, device and equipment for automobile scene function and storage medium

Abstract

The invention discloses a visual arrangement method and device for an automobile scene function, equipment and a storage medium, and relates to the technical field of new energy automobile control, and the method comprises the steps: responding to a mixed configuration operation of a user on function entries and event entries, and generating a function arrangement list; responding to execution time configuration of each function in the function arrangement list by a user; mapping each function in the function arrangement list into a corresponding system code and an operation code based on a pre-stored function comparison table; combining the system code, the operation code, the execution time configuration and the event trigger identifier into scene description data; the scene description data is encoded, the arrangement data packet is generated, and the shareable arrangement data packet is generated by responding to user mixed configuration and mapping, so that user definition, event triggering and social propagation of scene functions are realized, individual requirements can be met without modifying vehicle end software, and the development cycle is shortened.

Description

Technical Field

[0001] This invention relates to the field of new energy vehicle control technology, and in particular to a method, device, equipment and storage medium for visually arranging automotive scene functions. Background Technology

[0002] As the level of automotive intelligence continues to improve, users' demands for vehicle functions have shifted from single-operation to scenario-based experiences involving multi-system collaboration. Complex scenarios such as parking and resting, emergency response in rainy weather, and welcoming and dropping off guests have become key to enhancing the user experience. The market urgently needs an agile development mechanism that allows users to customize function combinations on demand, quickly verify new scenario requirements, and support the social dissemination of scenarios, in order to achieve a personalized experience for each user and continuous iteration of vehicle functions.

[0003] However, the various functions of existing vehicles are relatively independent, and function combinations must be hard-coded by engineers in the code. This not only results in long development cycles and high testing costs, but also fails to support user customization. Existing systems lack visual drag-and-drop orchestration tools, making it impossible for users to intuitively configure the timing relationships and trigger conditions of functions; the inconsistent data formats of functions make cross-platform editing and synchronization difficult; and there is no scene sharing mechanism, making it impossible to quickly replicate and promote excellent scenes among different users. This severely restricts the playability and scalability of the vehicle's functions and makes it difficult to meet the growing personalized needs of users.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this invention is to provide a method, apparatus, device, and storage medium for visually arranging automotive scene functions, aiming to solve the technical problem of how to achieve agile development and personalized customization of automotive scene functions through user-defined function combinations, event trigger configurations, and data packet sharing.

[0006] To achieve the above objectives, the present invention provides a method for visually arranging automotive scene functions, the method comprising the following steps: Respond to user's mixed configuration operations for function items and event items, and generate a function orchestration list; Respond to the user's configuration of the execution time for each function in the function orchestration list; Based on the pre-stored function lookup table, each function in the function arrangement list is mapped to the corresponding system code and operation code; The system code, the operation code, the execution time configuration, and the event trigger identifier are combined into scene description data; The scene description data is encoded to generate an orchestrated data package.

[0007] In one embodiment, the step of generating a function orchestration list in response to a user's mixed configuration operation of function items and event items includes: A visual arrangement interface is provided, which includes a function button area, an arrangement area, a timeline area, and an event triggering area. The system detects the user's action of dragging a function button from the function button area to the arrangement area, generates a corresponding function entry in the arrangement area, and displays a list of executable operations for the function entry for the user to select. The system detects user actions of dragging environmental event or vehicle status event buttons to the event triggering area and establishes the triggering relationship between the event and the function orchestration list. The function entries, selected executable operations, and trigger relationships are integrated into a function orchestration list.

[0008] In one embodiment, the step of responding to a user's configuration of the execution time for each function in the function orchestration list includes: The user-defined duration for triggered functions is set to a preset zero value, while the duration for continuous functions is set to a non-zero time value. Set the start time of the response to user requests for functions unrelated to the event to a relative time value; The start time for responding to user requests for functionality associated with an event is set to an offset time value with the event trigger time as zero. The duration and start time are configured to be associated with the corresponding function entries.

[0009] In one embodiment, the step of mapping each function in the function orchestration list to its corresponding system code and operation code based on a pre-stored function lookup table includes: Load a function lookup table, which records the mapping relationship between function name, system code and executable opcode; Iterate through each function entry in the function orchestration list and extract its function name and selected operation; The system code is obtained by querying the lookup table using the function name as the index, and the operation code is obtained by querying the lookup table using the selected operation as the index. The system code and operation code are associated with the corresponding function entries.

[0010] In one embodiment, the step of combining the system code, the opcode, the execution time configuration, and the event trigger identifier into scene description data includes: Assign a function number to each function entry; Extract the system code, operation code, start time, duration, and event trigger identifier for each function entry; Convert the minute value of the start time into start minute bytecode, and convert the second value of the start time into start second bytecode; Convert the minute value of the duration into continuous minute bytecode, and convert the second value of the duration into continuous second bytecode; The function number, system code, operation code, start minute bytecode, start second bytecode, duration minute bytecode, duration second bytecode, and event trigger identifier are arranged in a preset order to obtain scene description data.

[0011] In one embodiment, the step of encoding the scene description data to generate an orchestration data packet includes: Convert each field in the scene description data into two hexadecimal characters; Concatenate all hexadecimal characters into a complete hexadecimal string in byte order; The hexadecimal string is compressed to generate a lightweight orchestrated data packet; Add a version identifier, integrity check code, and digital signature to the orchestrated data packet; The orchestrated data package is associated with the scene name and stored or exported as a shareable file.

[0012] In one embodiment, the method further includes: In response to a user's request to share the orchestrated data packet, an encrypted access token is generated and access permissions and validity period are set; Create a sharing link or QR code based on the encrypted access token; The sharing link or QR code is published to the target user, so that the target user can download the orchestrated data packet by verifying the encrypted access token; Receive execution status feedback uploaded by the vehicle terminal, and optimize the function lookup table or adjust the execution time configuration based on the execution status feedback.

[0013] Furthermore, to achieve the above objectives, the present invention also proposes a visualization and arrangement device for automotive scene functions, comprising: The hybrid configuration module is used to respond to users' hybrid configuration operations for function items and event items, and generate a function orchestration list; The time configuration module is used to respond to the user's configuration of the execution time for each function in the function orchestration list; The mapping module is used to map each function in the function arrangement list to a corresponding system code and operation code based on a pre-stored function lookup table. The combination module is used to combine the system code, the operation code, the execution time configuration, and the event trigger identifier into scene description data; The encoding module is used to encode the scene description data and generate an orchestrated data package.

[0014] Furthermore, to achieve the above objectives, the present invention also proposes a visualization arrangement device for automotive scene functions. The device includes: a memory, a processor, and a visualization arrangement program for automotive scene functions stored in the memory and executable on the processor. The visualization arrangement program for automotive scene functions is configured to implement the steps of the visualization arrangement method for automotive scene functions as described above.

[0015] Furthermore, to achieve the above objectives, the present invention also proposes a storage medium storing a visualization arrangement program for automotive scene functions, wherein when the visualization arrangement program for automotive scene functions is executed by a processor, the steps of the visualization arrangement method for automotive scene functions as described above are implemented.

[0016] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the visualization arrangement method for automotive scene functions as described above.

[0017] One or more technical solutions proposed in this application have at least the following technical effects: The system receives mixed configurations of function and event items from users through a visual orchestration interface, allowing users to customize function combinations and trigger conditions, replacing the traditional hard-coded development model. Based on a function lookup table, functions are mapped to system codes and operation codes, and the start time and duration are precisely decomposed into minute bytecode and second bytecode. These are then arranged in a preset order to generate structured scene description data, ensuring standardized and lightweight data format. The data is then converted into a complete hexadecimal string and a version identifier and digital signature are added to generate a shareable orchestration data package. By responding to sharing requests, encrypted access tokens and QR codes are created, enabling the scene to be securely propagated among different users. After receiving and parsing the data package, the vehicle controls the actuators to execute instructions in sequence, realizing a closed loop from user orchestration to vehicle execution. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart illustrating an embodiment of the visual orchestration method for automotive scene functions in this application. Figure 2 This is a schematic diagram illustrating the scene function arrangement of an example provided in Embodiment 1 of the visual arrangement method for automotive scene functions in this application. Figure 3 This is a flowchart illustrating Embodiment 2 of the visual orchestration method for automotive scene functions in this application. Figure 4 This is a schematic diagram of the module structure of the visualization and arrangement device for automotive scene functions in an embodiment of this application; Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the visualization and orchestration method of the automotive scene function in the embodiments of this application.

[0021] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0022] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0023] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0024] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device capable of realizing the above functions, such as a visualization and arrangement device for automotive scene functions. The following description uses a visualization and arrangement device for automotive scene functions as an example to illustrate this embodiment and the subsequent embodiments.

[0025] Based on this, embodiments of this application provide a method for visually arranging automotive scene functions, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the visual arrangement method for automotive scene functions in this application.

[0026] In this embodiment, the visualization arrangement method for automotive scene functions includes steps S10 to S50: Step S10: Respond to the user's mixed configuration operation of function items and event items, and generate a function orchestration list; The functional orchestration system components used in this solution are as follows: the left side contains various vehicle function buttons, as well as environment and event buttons; the middle is the function and operation area; and the bottom is the timeline. Each function in this system has certain basic operations to ensure that the function can be executed in the operation area. Below are some examples of operable functions: Table 1

[0027] It should be noted that the purpose of this step is to establish a user-defined scenario. By receiving the user's function selection and event association intent through visual interaction, a structured function orchestration list is generated as the basis for subsequent timing configuration and data generation.

[0028] Functional entries refer to the abstract representation of the vehicle's subsystems such as doors, windows, air conditioning, and seats. Each entry carries a set of executable operations for that system. Event entries refer to the external conditions that trigger the execution of a scenario, such as rain sensor signals, door opening signals, temperature changes, and other environmental or vehicle status events. Hybrid configuration operations refer to the complex interactive behaviors of users simultaneously handling function selection and event binding.

[0029] like Figure 2 As shown, Figure 2 The diagram illustrates the function arrangement for the "Take a Break" scenario (example). The system allows users to drag and drop functions and events to the function list area in the middle of the system. When a function is clicked, the executable operation for that function will appear. For example, when the car door is clicked, the door will display an executable operation, such as selecting "lock" and setting the duration to 0, which is the trigger type.

[0030] For example, when you click on the air conditioner, you can first select automatic air conditioning for 15 minutes, then select internal circulation for 7 minutes, external circulation for 1 minute, and internal circulation for 7 minutes.

[0031] Other functions such as windows, interior lights, and ambient lighting can be set using the above method.

[0032] In addition, the system can add events to the function list area, such as triggering a "rain" event, which would close the windows and turn the air conditioning on to recirculate.

[0033] After completing the system function arrangement settings, you can save and name the arrangement. After saving, the arrangement will generate a hexadecimal string, with the data area (partial) shown in Table 2: Table 2

[0034] The first column of the table represents the sequence number of the function operation (or action), the second column represents the function code (corresponding to Table 1), the third column is the action to be performed by the function (corresponding to Table 1), the fourth column is the minute, the fifth column is the second, which is the start time of the function execution, the sixth column is the minute, and the seventh column is the second, which is the duration of the function execution (00 00 represents trigger type).

[0035] According to the above rules, the first function is to lock the car doors, which is executed and triggered at 0 minutes and 0 seconds; the second function is to leave the doors and windows slightly open, which is executed and triggered at 0 minutes and 0 seconds; the third function is to raise the doors and windows, which is executed and triggered at 14 minutes and 58 seconds; the fourth function is to turn on the air conditioning automatically, which is executed at 0 minutes and 0 seconds and ends at 15 minutes and 0 seconds. The data for the entire function can be obtained by following this pattern.

[0036] Data can be transmitted from the vehicle-to-everything (V2X) platform to the vehicle, where corresponding functional scenarios (such as a "rest scenario") are generated. After clicking the "rest scenario" button on the vehicle's infotainment system, the system parses and sends the data to the actuator according to defined rules. The actuator then executes the action based on the specified start and end times, thus enabling the vehicle to realize the "rest scenario." The start of the scenario can also be timed based on the triggering of a specific event, such as opening a door, illuminating the welcome lights, flashing the turn signals once, or opening the sunshade.

[0037] In addition, the system's programming function can be shared with other users (car owners) via links or QR codes. Other car owners can download the function to their own cars to achieve the same functionality as those programmed by others.

[0038] The system can be operated on a webpage, a mobile app, or a vehicle-mounted system, without time or space restrictions, and its functions can be programmed anytime, anywhere.

[0039] Understandably, by providing a visual interface that includes function button areas, arrangement areas, timeline areas, and event trigger areas, when a user drags a function button to the arrangement area, the system creates a corresponding function item object in the background and queries a pre-stored function lookup table to obtain all executable operations supported by that item (such as the automatic, cooling, and heating modes of an air conditioner), displaying them in a list for the user to select. When a user drags an event button to the event trigger area, the system records the event type identifier and establishes a mapping relationship between the event identifier and the list identifier in the metadata structure of the function arrangement list. Finally, the system packages the user-selected function item, the selected operation, and the trigger relationship into a function arrangement list object, completing the first round of transformation from user intent to data structure.

[0040] In one feasible implementation, step S10 includes steps A11 to A14: Step A11: Provide a visual arrangement interface, which includes a function button area, an arrangement area, a timeline area, and an event triggering area; It should be noted that the purpose of this step is to build a physical carrier for user interaction, to graphically and modularize the abstract vehicle functions and triggering conditions, to lower the user configuration threshold, and to achieve cross-platform operation.

[0041] The function button area is a collection of draggable components displaying icons for vehicle functions such as doors, windows, air conditioning, seats, and ambient lighting; the arrangement area is a container that receives user drag-and-drop operations and generates function entries; the timeline area provides visual input controls for the start time and duration of each function entry; and the event trigger area is the binding entry point for environmental events and vehicle status events.

[0042] Understandably, the system loads the entire vehicle's function catalog and renders it as interactive button components, with each button bound to a unique function identifier; the arrangement area listens for drag events, dynamically generates function entries, and supports sorting; the timeline area provides input boxes for start time and duration; the event trigger area displays bindable events in the form of icons, and after the user drags an event icon to this area, the system records the event type and associates it with the entire scene; this interface design allows users to complete complex scene arrangement through dragging, clicking, and input without programming.

[0043] Step A12: Detect the user's action of dragging the function button from the function button area to the arrangement area, generate the corresponding function item in the arrangement area, and display the list of executable operations of the function item for the user to select. It should be noted that the purpose of this step is to achieve intuitive interaction in function selection, convert user gestures into function items that the system can recognize, and provide fine-grained operation configuration capabilities.

[0044] Drag and drop is a press-move-release gesture sequence performed by the user on a touchscreen or mouse; a function entry is a data object created by the system in memory, containing a function identifier, name, and a set of selectable operations; the list of executable operations is the set of specific actions supported by the function (such as unlocking, locking, and unlocking the left front door of a door lock).

[0045] Understandably, the system listens for drag-and-drop events in the orchestration area. When a function button is detected being dragged in, it captures the function identifier of the dragged button; creates a new function entry object in the orchestration area, storing the function identifier and name; queries a pre-stored function lookup table to obtain all executable operations for that function (00=raise window, 01=lower window, 02=leave gap), and displays them in a list; after the user selects an operation, the selected operation code is recorded in the operation field of the function entry, completing the initial configuration of the function entry.

[0046] Step A13: Detect the user's action of dragging the environmental event or vehicle status event button to the event trigger area, and establish the trigger relationship between the event and the function orchestration list; It should be noted that the purpose of this step is to enable dynamic configuration of scene triggering conditions, upgrade function orchestration from manual execution to automatic response, and improve the level of scene intelligence.

[0047] Environmental events are detected by external sensors (such as rain sensors detecting rain and temperature sensors detecting high temperatures); vehicle status events are read by the vehicle bus (such as door opening signals and engine start signals); the triggering relationship is a logical binding between event identifiers and function orchestration list identifiers, which automatically triggers execution when the event conditions are met.

[0048] Understandably, the system displays environmental event buttons (such as the rain sensor icon) and vehicle status event buttons (such as the door icon). After the user drags the event button to the trigger area, the system records the event type identifier and trigger condition parameters (such as rainfall greater than 5 mm per hour). A mapping relationship between event identifiers and list identifiers is established in the metadata structure of the function orchestration list. This rule is stored in the metadata header of the scene, and after being parsed by the vehicle, the corresponding event listener is registered to realize the automatic scene triggering of "rain → automatic window closing + air conditioning recirculation".

[0049] Step A14: Integrate the function entries, selected executable operations, and trigger relationships into a function orchestration list.

[0050] It should be noted that the purpose of this step is to aggregate the scattered configuration information into a unified data structure, thereby completing the data-driven expression of functional combination logic.

[0051] Integration is the process of merging multiple sub-data structures into a single complete object; the function orchestration list is a scene blueprint that contains all function items, operation selections, and trigger relationships, and is an intermediate product of scene data generation.

[0052] Understandably, the system traverses all function entry cards in the orchestration area, extracts the function identifier, system code, operation code, and time parameter stored in the cards; reads the event identifier, trigger condition, and trigger identifier (0 or 1) from the event trigger area; packages all information into a structured data format, including function arrays and trigger objects; this structure serves as the input source for step S20, completing the first aggregation from user operation to data structure.

[0053] Step S20: Respond to the user's configuration of the execution time for each function in the function orchestration list; It should be noted that the purpose of this step is to receive the user's time strategy settings, define the execution time and duration of each function on the scene timeline, and realize the timing combination and parallel scheduling of multiple functions.

[0054] The execution time configuration includes start time (when the function starts) and duration (how long the function lasts); the duration of trigger-type functions is zero (instantaneous action), and the duration of continuous functions is non-zero (long-term action); the relative time value is zero point when the scene starts, and the offset time value is zero point when the event is triggered.

[0055] Understandably, the system provides a time configuration interface for each function item in the function orchestration list; users can input relative time (starting the timer from scene start) or offset time (starting the timer from event trigger); the system verifies the validity of the time values ​​(they cannot overlap or be negative); and writes the configuration results into the time parameter field of the function item to form a function orchestration list with timing information.

[0056] In one feasible implementation, step S20 includes steps A21 to A23: Step A21: Respond to the user's setting of the duration of triggered functions to a preset zero value, and the setting of the duration of continuous functions to a non-zero time value; It should be noted that the purpose of this step is to distinguish the function type and configure the corresponding time attributes to ensure that the system can correctly identify instantaneous actions and continuous actions, and accurately control the actuator behavior and timer logic.

[0057] Triggered functions refer to actions that have a short execution time and do not require maintenance (such as unlocking the car door or flashing the turn signal). A duration of 0 indicates that the action ends immediately after completion. Continuous functions refer to actions that require maintaining the state (such as running the air conditioner or opening the car window). A non-zero time value indicates the duration of the state maintenance.

[0058] Understandably, the system identifies the operation type of the function entry (e.g., "lock" is a trigger type, "heat" is a continuous type); for trigger type functions, the duration field is automatically set to 0x00 0x00 (two bytes of zero value); for continuous type functions, the system receives the minute and second values ​​input by the user and converts them into bytecode (e.g., 15 minutes → 0x0F 0x00); this configuration determines whether the controller will subsequently start the timer sustain instruction.

[0059] Step A22: Respond to user requests for a function unrelated to the event by setting the start time to a relative time value; It should be noted that the purpose of this step is to configure a timeline based on the scenario startup baseline, so that the function can be automatically triggered at a specific time according to the preset script, thereby achieving the effect of timed execution.

[0060] The relative time value is the offset from the scene start time (e.g., executed 30 seconds after scene start); the event-independent function refers to the function that is not triggered by external events and is executed purely according to the time script.

[0061] Understandably, the system provides a start time input box for each function item; users can input minute and second values ​​(e.g., 00:30 means execution will begin 30 seconds after the scene starts); the system converts the decimal value into hexadecimal bytecode (30 seconds → 0x00 0x1E); this time value is filled into the start time field of the scene data packet, and the vehicle-side parses it and starts the function according to the timeline.

[0062] Step A23: Respond to the user's request to set the start time of the function associated with the event to an offset time value with the event trigger time as zero; It should be noted that the purpose of this step is to configure a dynamic timeline based on event triggering, so that the function is delayed in execution after the event occurs, thus realizing a conditional response scenario.

[0063] The event trigger time being zero means that the timer is reset when the event occurs, and the offset time value is the delay relative to the event time (e.g., after the event + 3 seconds); the function associated with the event means that its execution time depends on the event rather than the scene start time.

[0064] Understandably, the system checks whether the function entry is bound to an event trigger identifier; if so, it provides an event-based relative time configuration; it converts the offset time into bytecode and marks the event trigger identifier as 1 in the data packet; when the vehicle-side controller receives an event signal, it starts an independent timer, and triggers the function execution after the timer reaches the offset time.

[0065] Step A24: Associate the duration and start time configuration with the corresponding function entries.

[0066] It should be noted that the purpose of this step is to bind the time configuration results with the function entries to form a complete function description with time sequence information, providing a unified data structure for subsequent mapping and combination.

[0067] Association involves writing the time parameter as an attribute field of a function entry; after configuration, the function entry becomes an object containing complete information such as function identifier, operation, time, and event.

[0068] Understandably, the system traverses the function orchestration list, fills the time bytecode generated in steps A21-A23 into the time parameter field of the corresponding entry; writes the event trigger identifier (0 or 1) into the event flag bit of the entry; updates the function entry data structure to contain a complete set of fields; and this structured entry is the input unit for the mapping process in step S30.

[0069] Step S30: Based on the pre-stored function lookup table, map each function in the function arrangement list to its corresponding system code and operation code; It should be noted that the purpose of this step is to convert user-friendly function names and operation descriptions into machine code that the vehicle controller can recognize, thereby decoupling function definition from execution mechanism.

[0070] The function lookup table is a pre-stored mapping dictionary that records the correspondence between function names and system codes and operation codes; mapping is the process of looking up and translating from the table.

[0071] Understandably, the system loads the function lookup table into memory; iterates through the function arrangement list, extracts the function name and selected operation for each entry; it queries the lookup table using the function name as the key to obtain the system code, and queries the lookup table using the selected operation as the key to obtain the operation code; it then fills the obtained code and operation code back into the function entry, thus completing the machine coding of the function.

[0072] In one feasible implementation, step S30 includes steps A31 to A34: Step A31: Load the function lookup table, which records the mapping relationship between function name, system code and executable opcode; It should be noted that the purpose of this step is to initialize the dictionary data required for the mapping, providing fast access capabilities for subsequent batch queries and supporting dynamic updates.

[0073] The function lookup table is a data table stored locally or in the cloud, containing function names, system codes, and a list of operation codes; the mapping relationship is a standard correspondence specification between vehicle functions and controller instructions defined by the OEM.

[0074] Understandably, when the system starts, it reads the function lookup table from the configuration file; parses the lookup table into a hash table or ordered array and stores it in the cache; if the lookup table version is updated, a hot reloading mechanism is triggered to reload it; this step ensures that subsequent mapping queries can be completed in constant time or logarithmic time complexity.

[0075] Step A32: Traverse each function entry in the function orchestration list and extract its function name and selected operation; It should be noted that the purpose of this step is to obtain the input data required for the mapping query by breaking down the user-configured function items into query keywords.

[0076] Traversal is the process of repeatedly accessing each element of a list; extraction is the process of reading the function name attribute and operation attribute of an item.

[0077] Understandably, the system obtains a function orchestration list object; iterates through the list using a loop structure; calls the get method for each entry to read the function name field and the selected operation field; and stores the extracted key-value pairs in a temporary query queue as input for the lookup table query in step A33.

[0078] Step A33: Use the function name as the index to look up the lookup table to obtain the system code, and use the selected operation as the index to look up the lookup table to obtain the operation code; It should be noted that the purpose of this step is to translate semantics into machine code through a table lookup operation, converting the user configuration into binary instructions that can be executed by the vehicle controller.

[0079] The system code is the code for the vehicle-side controller to identify the subsystem (e.g., 01 represents the door lock, 02 represents the door and window); the operation code is the code for identifying the specific action (e.g., 00 represents unlocking, 01 represents locking); the index query is a hash table lookup or array index access.

[0080] Understandably, the system uses the function name as the keyword to look up the lookup table to obtain the system code; it iterates through the selected operation list to match the operation selected by the user and obtains the operation code; if the query fails, it returns an error message to the user; if the query succeeds, it writes the code and operation code into the corresponding field of the function entry, thus completing the machine coding of the function.

[0081] Step A34: Associate the system code and operation code with the corresponding function entry.

[0082] It should be noted that the purpose of this step is to write the query results back into the function entries to form a complete executable function description, providing a data structure containing machine code for the combination in step S40.

[0083] Association is an assignment operation that stores the queried code and value into the attribute field of the function entry.

[0084] Understandably, the system iterates through the query result queue; for each entry, it assigns the obtained system code to the system code field and the operation code to the operation code field; the updated function entry contains complete information and is the basic unit for combining the scene description data in step S40.

[0085] Step S40: Combine the system code, operation code, execution time configuration, and event trigger identifier into scene description data; It should be noted that the purpose of this step is to package the mapped set of functional items into complete scene description data, forming a structured byte sequence, in preparation for final encoding and encapsulation.

[0086] Combining involves concatenating fields from multiple functional items in a uniform format; scene description data is a structured byte sequence containing all information about the scene.

[0087] Understandably, the system iterates through all function entries, extracts the function number, system code, operation code, start minute byte value, start second byte value, duration minute byte value, duration second byte value, and event trigger identifier for each entry; arranges them in a preset order; and concatenates all entries sequentially to form complete scene description data.

[0088] Step S50: Encode the scene description data to generate an orchestration data package.

[0089] It should be noted that the purpose of this step is to convert the structured scene description data into a compact, transmittable, and shareable final data packet format, which facilitates distribution via the Internet of Vehicles, local storage, and social dissemination.

[0090] Encoding includes converting to hexadecimal strings, compression, and adding metadata; the final product is the data packet arrangement, which includes scene data, version information, checksum, and signature information.

[0091] Understandably, the system executes sub-steps A41 to A45 in sequence to convert the byte sequence into hexadecimal characters, compress it, add version and signature, and generate a complete data packet. This data packet is small in size, has a standard format, can be encrypted and shared, and can be directly parsed and executed by the vehicle.

[0092] In one feasible implementation, step S50 includes steps A41-A45: Step A41: Convert each field in the scene description data into two-digit hexadecimal characters; It should be noted that the purpose of this step is to convert the binary byte value into a hexadecimal representation in text form, which facilitates cross-platform transmission, storage and debugging, while maintaining data compactness.

[0093] Two hexadecimal characters are strings represented by the numbers 0 to 9 and the letters A to F. Each byte corresponds to two characters (e.g., the byte value 0x0E is converted to the string "0E"); the conversion is the binary to hexadecimal encoding process.

[0094] Understandably, the system iterates through each byte field of the scene description data; divides the 8-bit binary value of each byte by 16 to obtain the high 4 bits and low 4 bits; maps the high 4 bits to hexadecimal characters (0 to 9 are mapped to '0' to '9', 10 to 15 are mapped to 'A' to 'F'), and processes the low 4 bits in the same way; combines the two characters to form the hexadecimal string representation of the byte; after all bytes are converted, a continuous hexadecimal character sequence is formed.

[0095] Step A42: Concatenate all hexadecimal characters in byte order to form a complete hexadecimal string; It should be noted that the purpose of this step is to combine the scattered hexadecimal characters into a single continuous string, forming a standardized data representation that facilitates subsequent compression, signing, and sharing.

[0096] Concatenation is a string joining operation; a complete hexadecimal string is the sequential concatenation of all converted bytes, without adding delimiters or spaces.

[0097] Understandably, the system extracts the hexadecimal character pairs of each byte in the scene description data according to the order of the function items; it then appends the characters sequentially using a string buffer without adding any delimiters; finally, it obtains a continuous string with a length equal to twice the number of bytes; this string is the standard text representation of the scene data and can be directly used for network transmission, database storage, or QR code encoding.

[0098] Step A43: Compress the hexadecimal string to generate a lightweight orchestrated data packet; It should be noted that the purpose of this step is to reduce the size of data packets, improve transmission efficiency and storage economy, especially to reduce traffic consumption in the vehicle-to-everything (V2X) environment, and support rapid delivery and local caching.

[0099] Compression processing uses algorithms to reduce string redundancy; lightweight orchestration data packets are compressed data objects with significantly reduced size.

[0100] Understandably, the system scans the hexadecimal string to identify consecutive repeating byte patterns; uses run-length encoding to replace repeating sequences with shorter formats; or uses a general compression algorithm to compress the entire string; the compressed data is then appended with a compression algorithm identifier byte to form a lightweight orchestrated data packet.

[0101] Step A44: Add a version identifier, integrity check code, and digital signature to the orchestrated data packet; It should be noted that the purpose of this step is to ensure version management, anti-tampering, and source authentication of data packets, thereby improving data security and reliability and supporting the commercial distribution of scenario data.

[0102] The version identifier is the data packet format version number, used for compatibility assessment and upgrade management; the integrity check code is used to detect transmission errors; and the digital signature is used to verify the legitimacy of the data packet's origin and prevent tampering.

[0103] Understandably, the system appends a version number byte before compressing the data; calculates the cyclic redundancy check (CRC) code of the compressed data and appends a 4-byte checksum; uses a private key to sign the version number, data, and checksum, generating signature data which is appended to the end; and the vehicle receives the data and verifies the signature validity, integrity, and version number matching.

[0104] Step A45: Associate the orchestration data package with the scene name and store or export it as a shareable file.

[0105] It should be noted that the purpose of this step is to persistently save the user's orchestration results and support exporting them as independent files for cross-platform sharing, thus completing the final output of the orchestration process.

[0106] Associated storage stores data packets along with metadata such as scene names and descriptions into a database; exporting to a shareable file generates a data file that users can easily download, copy, or use to generate QR codes.

[0107] Understandably, the system packages lightweight orchestration data packages, scene names, creation times, author identifiers, and other metadata into scene objects; stores them in the cloud scene database and assigns a unique scene identifier; or generates a file and provides a download link, with the file named "scene name.scene format"; users can send this file to other car owners through the sharing function to achieve scene cloning and community dissemination.

[0108] Furthermore, the method also includes: In response to a user's request to share orchestrated data packets, generate an encrypted access token and set access permissions and validity period; Create a sharing link or QR code based on an encrypted access token; Share a link or QR code to the target user so that the target user can download the orchestration data package by verifying the encrypted access token; Receive execution status feedback uploaded by the vehicle terminal, and optimize the function comparison table or adjust the execution time configuration based on the execution status feedback.

[0109] It should be noted that the purpose of this step is to achieve secure social dissemination of scene data and system self-iterative optimization. It protects users' creative achievements through access control, while continuously improving the quality of orchestration by utilizing vehicle-side execution data, thus forming a business closed loop from user sharing to system evolution.

[0110] A sharing request is a data distribution intent triggered by a user after orchestration is completed; an encrypted access token is an encrypted string containing information such as owner identity, scene identifier, permission level, and validity period, generated using a symmetric encryption algorithm; access control defines the scope of operations a target user can perform on data packets (e.g., read-only, copyable, editable); the validity period controls the token's expiration time through a timestamp; a sharing link or QR code is the token's carrier form; execution status feedback is the instruction execution result returned by the vehicle controller (success, failure, delay, error code); the optimized function lookup table dynamically adjusts the operation code mapping relationship or adds new function entries; adjusting the execution time configuration corrects the start time or duration parameters to avoid conflicts.

[0111] Understandably, after receiving a user's sharing request, the system reads the orchestration data packet identifier, owner identifier, and preset permission template of the shared scenario; it then encrypts structured data such as the owner signature, scenario identifier, permission mask (e.g., 0x01 indicates read-only), and expiration timestamp using an Advanced Encryption Standard (AES) algorithm to generate an encrypted access token string; this token is then appended to the platform's Uniform Resource Locator (URL) as a query parameter to form a sharing link, or the token is converted into a QR code image using a QR code encoding algorithm; the user sends the link or QR code to the target user via instant messaging tools or a car owner forum; when the target user accesses the link or scans the QR code, the system extracts the token and decrypts it using a key to verify the owner signature. The system verifies the validity of the name, checks whether the download permission is allowed, and determines whether the current time has expired. After successful verification, it reads the orchestration data package from the cloud storage and transmits it to the target user device. During the execution of the scenario, the vehicle records the execution status and time of each function instruction and transmits it back to the cloud orchestration system through the vehicle network channel. The system analyzes the reasons for failure. If it finds that the operation code of a certain function is frequently invalid, it updates the operation code definition of that function in the function comparison table. If it finds that a scenario fails to execute due to a time conflict, it recommends an optimized start time or duration configuration to the scenario author. This closed-loop feedback mechanism enables the orchestration system to have self-learning capabilities, continuously improve the success rate of scenarios and vehicle compatibility, and achieve ecological evolution.

[0112] This embodiment provides a visual arrangement method for automotive scene functions. With this solution, users can arrange the functions they want to combine to achieve, flexibly responding to various scene requirements; it enables agile development. When users need to implement certain functions, OEMs can directly arrange functions to meet their needs without changing the vehicle-side component software, enabling rapid verification and delivery; it can meet the needs of different user groups, and user groups can analyze functions with each other, greatly improving the operability of the whole vehicle and achieving a personalized experience for each user.

[0113] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 3 Step S40 includes steps S401 to S405: Step S401: Assign a function number to each function entry; It should be noted that the purpose of this step is to assign a unique sequence identifier to each function in the function orchestration list, so as to ensure that the execution order of functions in the scene data package is clear and traceable, and to avoid ambiguity when multiple functions are executed concurrently.

[0114] The function number is the sequential number of the function items in the scene, starting from 0 or 1 and incrementing. The allocation process is to automatically number the functions according to the insertion order when traversing the function arrangement list, which is used to identify the execution order of the functions in the scene.

[0115] Understandably, the system iterates through the function arrangement list and assigns an incrementing number (such as 01, 02, 03) to each entry. This number determines the position of the function in the hexadecimal data packet. When the vehicle parses the data, it executes the functions in the order of the numbers to ensure that the scene timing logic is consistent with the user's arrangement.

[0116] Step S402: Extract the system code, operation code, start time, duration and event trigger identifier for each function item; It should be noted that the purpose of this step is to extract all key parameters from the configured function entries to form structured data fragments, providing a complete set of semantic information for subsequent bytecode conversion.

[0117] The system code is the digital code of the vehicle-side controller to identify the subsystem (e.g., 01 indicates the door lock system), the operation code is the digital code to identify the specific action (e.g., 00 indicates the unlocking action), the start time and duration are time parameters configured by the user, and the event trigger flag is a 0 or 1 flag indicating whether the function is event-driven.

[0118] Understandably, the system sequentially accesses each entry in the function orchestration list, reads the system code field, operation code field, time configuration field (minutes and seconds of start time, minutes and seconds of duration), and event binding field obtained from its mapping, extracts these parameters to a temporary cache, and forms the raw dataset to be encoded.

[0119] Step S403: Convert the minute value of the start time into start minute bytecode, and convert the second value of the start time into start second bytecode; It should be noted that the purpose of this step is to convert the decimal time value input by the user into a single-byte hexadecimal code value that can be recognized by the vehicle controller, thereby realizing the digital encapsulation of time parameters and ensuring time accuracy and data compactness.

[0120] The start minute bytecode is the hexadecimal single-byte value corresponding to the "minute" part of the start time (e.g., 14 minutes → 0x0E), and the start second bytecode is the hexadecimal single-byte value corresponding to the "second" part (e.g., 58 seconds → 0x3A). The conversion process is to divide the decimal number by 16 to obtain the quotient and remainder. The quotient is mapped to the high-order hexadecimal byte, and the remainder is mapped to the low-order byte.

[0121] Step S404: Convert the minute value of the duration into continuous minute bytecode, and convert the second value of the duration into continuous second bytecode; It should be noted that the purpose of this step is to convert the user-configured duration into hexadecimal bytecode, distinguish between trigger-type (00 00 indicates instantaneous) and continuous-type (non-zero value indicates duration) functions, and provide an accurate time reference for the vehicle-side timer.

[0122] The conversion logic between continuous minute bytecode and continuous second bytecode is the same as in step S403; for trigger-type functions, both continuous minute and continuous second are set to 0x00, indicating that no timer is needed; for continuous functions, the conversion is based on the user input value (e.g., 15 minutes → 0x0F 0x00).

[0123] Understandably, the system reads the duration in minutes (e.g., 15), converts it to 0x0F and fills it into the third byte position; it reads the duration in seconds (e.g., 0), converts it to 0x00 and fills it into the fourth byte position; for trigger-type functions, both bytes are forced to be 0x00 0x00, indicating that the action does not need to be maintained after execution, and the controller marks it as complete immediately after sending the instruction.

[0124] Step S405: Arrange the function number, system code, operation code, start minute bytecode, start second bytecode, duration minute bytecode, duration second bytecode, and event trigger identifier in a preset order to obtain scene description data.

[0125] It should be noted that the purpose of this step is to concatenate all discrete bytecode and identifiers in a standardized order to form a structured byte sequence, thereby achieving standardized assembly of scene description data and ensuring that the vehicle-side parsing can read each field at a fixed offset.

[0126] The preset order refers to the arrangement rule of "serial number → code → opcode → start minute → start second → duration minute → duration second → event identifier"; the scene description data is an ordered collection of this series of bytecodes, which is the direct input for generating the final shareable data packet.

[0127] Understandably, the system sorts each entry by function number from smallest to largest; for each entry, it sequentially extracts the function number byte, system code byte, opcode byte, start minute bytecode, start second bytecode, duration minute bytecode, and duration second bytecode, and finally appends the event trigger flag byte (0 or 1); by concatenating the byte sequences of all entries, it obtains complete scene description data, such as "01 03 00 0E 3A 0F 00 00" indicating that the air conditioner automatic function with sequence number 1 starts at 14 minutes and 58 seconds and lasts for 15 minutes, without event triggering.

[0128] This embodiment provides a visual orchestration method for automotive scene functions. By assigning sequence numbers to function items, extracting parameters, converting time value bytecode, and arranging them in a preset order, the system achieves the standardization and structured generation of scene description data. Precisely decomposing decimal time into minute and second bytecode not only ensures time accuracy and data compactness, but also enables the vehicle-side controller to accurately parse each field with a fixed offset. This combination process transforms the user-configured semantic scene into a machine-readable standardized byte sequence, providing a unified input format for subsequent encoding and generation of shareable orchestration data packets. It supports a complete data-driven chain from user customization to vehicle-side execution, enabling agile scene development and rapid iteration without modifying the vehicle-side software.

[0129] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the visualization and arrangement method of the automotive scene function of this application. Any simple transformations based on this technical concept are within the protection scope of this application.

[0130] This application also provides a visualization and arrangement device for automotive scene functions; please refer to... Figure 4 The visualization and orchestration device for automotive scene functions includes: The hybrid configuration module 10 is used to respond to the user's hybrid configuration operation of function items and event items and generate a function orchestration list; The time configuration module 20 is used to respond to the user's configuration of the execution time of each function in the function orchestration list; Mapping module 30 is used to map each function in the function arrangement list to the corresponding system code and operation code based on a pre-stored function lookup table; The combination module 40 is used to combine the system code, operation code, execution time configuration and event trigger identifier into scene description data; Encoding module 50 is used to encode scene description data and generate orchestrated data packets.

[0131] The visual orchestration device for automotive scene functions provided in this application, employing the visual orchestration method for automotive scene functions in the above embodiments, can solve the technical problem of how to achieve agile development and personalized customization of automotive scene functions through user-defined function combinations, event trigger configurations, and data packet sharing. Compared with the prior art, the beneficial effects of the visual orchestration device for automotive scene functions provided in this application are the same as those of the visual orchestration method for automotive scene functions provided in the above embodiments, and other technical features in the visual orchestration device for automotive scene functions are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0132] In one embodiment, the hybrid configuration module 10 is also used to provide a visual orchestration interface, which includes a function button area, an orchestration area, a timeline area, and an event triggering area. The system detects the user's action of dragging a function button from the function button area to the arrangement area, generates the corresponding function entry in the arrangement area, and displays a list of executable operations for the function entry for the user to select. Detect user actions of dragging environmental event or vehicle status event buttons to the event trigger area, and establish the trigger relationship between events and function orchestration lists; The function entries, selected executable operations, and trigger relationships are integrated into a function orchestration list.

[0133] In one embodiment, the time configuration module 20 is further configured to respond to the user setting the duration of trigger-type functions to a preset zero value and the duration of continuous-type functions to a non-zero time value; Set the start time of the response to user requests for functions unrelated to the event to a relative time value; The start time for responding to user requests for functionality associated with an event is set to an offset time value with the event trigger time as zero. Associate the duration and start time configurations with the corresponding feature entries.

[0134] In one embodiment, the mapping module 30 is further configured to load a function lookup table, which records the mapping relationship between function names, system codes and executable opcodes. Iterate through each function entry in the function orchestration list and extract its function name and selected operation; Use the function name as an index to look up the lookup table to obtain the system code, and use the selected operation as an index to look up the lookup table to obtain the operation code. Associate system codes with operation codes to the corresponding function entries.

[0135] In one embodiment, the combination module 40 is further configured to assign a function number to each function entry; Extract the system code, operation code, start time, duration, and event trigger identifier for each function entry; Convert the start time minute value to start minute bytecode, and convert the start time second value to start second bytecode; Convert the duration in minutes to duration in minutes bytecode, and convert the duration in seconds to duration in seconds bytecode; Arrange the function number, system code, operation code, start minute bytecode, start second bytecode, duration minute bytecode, duration second bytecode, and event trigger identifier in a preset order to obtain the scene description data.

[0136] In one embodiment, the encoding module 50 is further configured to convert each field in the scene description data into two-digit hexadecimal characters; Concatenate all hexadecimal characters into a complete hexadecimal string in byte order; Compress hexadecimal strings to generate lightweight orchestrated data packets; Add version identifiers, integrity check codes, and digital signatures to the orchestration of data packets; Associate orchestration data packages with scene names and store or export them as shareable files.

[0137] In one embodiment, the encoding module 50 is further configured to respond to a user's request to share the orchestrated data packet, generate an encrypted access token, and set access permissions and validity period. Create a sharing link or QR code based on an encrypted access token; Share a link or QR code to the target user so that the target user can download the orchestration data package by verifying the encrypted access token; Receive execution status feedback uploaded by the vehicle terminal, and optimize the function comparison table or adjust the execution time configuration based on the execution status feedback.

[0138] This application provides a visualization and arrangement device for automotive scene functions. The visualization and arrangement device for automotive scene functions includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the visualization and arrangement method for automotive scene functions in the above embodiment 1.

[0139] The following is for reference. Figure 5 This document illustrates a structural schematic diagram of a visualization orchestration device suitable for implementing the automotive scene functions of the embodiments of this application. The visualization orchestration device for automotive scene functions in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The visual orchestration device for automotive scene functions shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0140] like Figure 5As shown, the visualization and orchestration device for automotive scene functions may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to programs stored in ROM (Read Only Memory) 1002 or programs loaded from storage device 1003 into RAM (Random Access Memory) 1004. RAM 1004 also stores various programs and data required for the operation of the visualization and orchestration device for automotive scene functions. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via bus 1005. Input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the visualization orchestration device for automotive scene functions to communicate wirelessly or wiredly with other devices to exchange data. Although a visualization orchestration device for automotive scene functions with various systems is shown in the figure, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems may be implemented alternatively.

[0141] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0142] The visual orchestration device for automotive scene functions provided in this application, employing the visual orchestration method for automotive scene functions in the above embodiments, can solve the technical problem of how to achieve agile development and personalized customization of automotive scene functions through user-defined function combinations, event trigger configurations, and data packet sharing. Compared with the prior art, the beneficial effects of the visual orchestration device for automotive scene functions provided in this application are the same as those of the visual orchestration method for automotive scene functions provided in the above embodiments, and other technical features in this visual orchestration device for automotive scene functions are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0143] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0144] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0145] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the visualization arrangement method of the automotive scene function in the above embodiments.

[0146] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, RAM (Random Access Memory), ROM (Read Only Memory), EPROM (Erasable Programmable Read Only Memory or Flash Memory), optical fibers, CD-ROM (CD-Read Only Memory), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0147] The aforementioned computer-readable storage medium may be included in the visualization and orchestration device for automotive scene functions; or it may exist independently and not be installed in the visualization and orchestration device for automotive scene functions.

[0148] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by the visual orchestration device for automotive scene functions, the visual orchestration device for automotive scene functions: responds to the user's mixed configuration operation of function items and event items, and generates a function orchestration list; responds to the user's configuration of the execution time of each function in the function orchestration list; maps each function in the function orchestration list to a corresponding system code and operation code based on a pre-stored function lookup table; combines the system code, operation code, execution time configuration, and event trigger identifier into scene description data; and encodes the scene description data to generate an orchestration data packet.

[0149] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including LAN (Local Area Network) or WAN (Wide Area Network)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0150] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0151] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0152] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the visualization orchestration method of the above-described automotive scene functions. This solves the technical problem of how to achieve agile development and personalized customization of automotive scene functions through user-defined function combinations, event trigger configurations, and data packet sharing. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the visualization orchestration method of automotive scene functions provided in the above embodiments, and will not be elaborated upon here.

[0153] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the visualization arrangement method for automotive scene functions as described above.

[0154] The computer program product provided in this application solves the technical problem of how to achieve agile development and personalized customization of automotive scene functions through user-defined function combinations, event-triggered configurations, and data packet sharing. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the visual arrangement method of automotive scene functions provided in the above embodiments, and will not be repeated here.

[0155] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for visually arranging automotive scene functions, characterized in that, The method includes: Respond to user's mixed configuration operations for function items and event items, and generate a function orchestration list; Respond to the user's configuration of the execution time for each function in the function orchestration list; Based on the pre-stored function lookup table, each function in the function arrangement list is mapped to the corresponding system code and operation code; The system code, the operation code, the execution time configuration, and the event trigger identifier are combined into scene description data; The scene description data is encoded to generate an orchestrated data package.

2. The method as described in claim 1, characterized in that, The step of generating a function orchestration list in response to a user's mixed configuration operation of function items and event items includes: A visual arrangement interface is provided, which includes a function button area, an arrangement area, a timeline area, and an event triggering area. The system detects the user's action of dragging a function button from the function button area to the arrangement area, generates a corresponding function entry in the arrangement area, and displays a list of executable operations for the function entry for the user to select. The system detects user actions of dragging environmental event or vehicle status event buttons to the event triggering area and establishes the triggering relationship between the event and the function orchestration list. The function entries, selected executable operations, and trigger relationships are integrated into a function orchestration list.

3. The method as described in claim 1, characterized in that, The steps for responding to user configuration of execution time for each function in the function orchestration list include: The user-defined duration for triggered functions is set to a preset zero value, while the duration for continuous functions is set to a non-zero time value. Set the start time of the response to user requests for functions unrelated to the event to a relative time value; The start time for responding to user requests for functionality associated with an event is set to an offset time value with the event trigger time as zero. The duration and start time are configured to be associated with the corresponding function entries.

4. The method as described in claim 1, characterized in that, The step of mapping each function in the function arrangement list to its corresponding system code and operation code based on a pre-stored function lookup table includes: Load a function lookup table, which records the mapping relationship between function name, system code and executable opcode; Iterate through each function entry in the function orchestration list and extract its function name and selected operation; The system code is obtained by querying the lookup table using the function name as the index, and the operation code is obtained by querying the lookup table using the selected operation as the index. The system code and operation code are associated with the corresponding function entries.

5. The method as described in claim 1, characterized in that, The step of combining the system code, the operation code, the execution time configuration, and the event trigger identifier into scene description data includes: Assign a function number to each function entry; Extract the system code, operation code, start time, duration, and event trigger identifier for each function entry; Convert the minute value of the start time into start minute bytecode, and convert the second value of the start time into start second bytecode; Convert the minute value of the duration into continuous minute bytecode, and convert the second value of the duration into continuous second bytecode; The function number, system code, operation code, start minute bytecode, start second bytecode, duration minute bytecode, duration second bytecode, and event trigger identifier are arranged in a preset order to obtain scene description data.

6. The method as described in claim 1, characterized in that, The step of encoding the scene description data to generate an orchestrated data packet includes: Convert each field in the scene description data into two hexadecimal characters; Concatenate all hexadecimal characters into a complete hexadecimal string in byte order; The hexadecimal string is compressed to generate a lightweight orchestrated data packet; Add a version identifier, integrity check code, and digital signature to the orchestrated data packet; The orchestrated data package is associated with the scene name and stored or exported as a shareable file.

7. The method as described in claim 1, characterized in that, The method further includes: In response to a user's request to share the orchestrated data packet, an encrypted access token is generated and access permissions and validity period are set; Create a sharing link or QR code based on the encrypted access token; The sharing link or QR code is published to the target user, so that the target user can download the orchestrated data packet by verifying the encrypted access token; Receive execution status feedback uploaded by the vehicle terminal, and optimize the function lookup table or adjust the execution time configuration based on the execution status feedback.

8. A visualization and arrangement device for automotive scene functions, characterized in that, include: The hybrid configuration module is used to respond to users' hybrid configuration operations for function items and event items, and generate a function orchestration list; The time configuration module is used to respond to the user's configuration of the execution time for each function in the function orchestration list; The mapping module is used to map each function in the function arrangement list to a corresponding system code and operation code based on a pre-stored function lookup table. The combination module is used to combine the system code, the operation code, the execution time configuration, and the event trigger identifier into scene description data; The encoding module is used to encode the scene description data and generate an orchestrated data package.

9. A visualization and arrangement device for automotive scene functions, characterized in that, The device includes: a memory, a processor, and a visualization program for automotive scene functions stored in the memory and executable on the processor, the visualization program for automotive scene functions being configured to implement the steps of the visualization program for automotive scene functions as described in any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium stores a visualization program for automotive scene functions, and when the visualization program for automotive scene functions is executed by the processor, it implements the steps of the visualization program for automotive scene functions as described in any one of claims 1 to 7.

Images