Vehicle-mounted cabin domain man-machine interaction SOA communication control method and system

Abstract

The invention discloses a vehicle-mounted cabin domain man-machine interaction SOA communication control method and system, and the method comprises the steps: building a vehicle-mounted Ethernet used for SOA communication based on an SOMEIP protocol stack, building a communication robustness mechanism at a Framework layer of an Android operating system of a cabin domain controller, building a corresponding relation between downlink and uplink signal values, setting an immediate response mechanism according to the SOA multi-application, and carrying out the communication of the vehicle-mounted Ethernet. And performing mutual decoupling and synchronous state change on the multi-application calling process, filtering and reporting the state change of the multi-application calling, and clearing the SOA signal cache. According to the method and the device, the man-machine interaction experience is enhanced, the consistency of display states among different applications is ensured by realizing the associated synchronous change of multiple applications to the same function state, the confusion of users caused by inconsistent states is eliminated, and a clear and coherent interaction interface is provided, so that the interaction experience of the users is remarkably improved.

Description

Technical Field

[0001] The present invention relates to a communication control method and system, and in particular to a vehicle-mounted cockpit domain human-computer interaction SOA communication control method and system. Background Art

[0002] At present, the intelligentization, electrification and networking of automobiles have become the development trend. The electronic and electrical architecture of the whole vehicle and the vehicle communication network are also constantly upgraded. The service-oriented idea of ​​SOA (Service-Oriented Architecture) has been applied in major domain controllers of automobiles. Among them, the cockpit domain controller, as one of the core domain controllers of automobiles, integrates more and more human-computer interaction functions, such as lane-level navigation, intelligent voice, 3D models, vehicle air conditioning, lighting, seats, windows and other control functions. In order to meet these functional requirements, the computing power of the cockpit domain controller is constantly improving in hardware. The software uses virtual machines to implement multiple operating systems, and integrates the SOMEIP protocol stack and AP Autosar middleware in the automotive field. Under the support of a powerful software and hardware architecture system, the use of SOA service-oriented thinking for flexible and efficient communication is also a commonly used vehicle communication method. However, in the cockpit domain, because it involves human-computer interaction, users can directly operate or perceive the cockpit HMI interface. Then, when users frequently and quickly operate to control a certain function of the car, the communication performance between the domain controllers responsible for implementing the function will often receive greater performance challenges, resulting in signal loss, return exceptions, etc., resulting in a poor human-computer interaction experience, which can no longer meet people's requirements and urgently needs to be improved. Summary of the invention

[0003] The purpose of the present invention is to provide a vehicle-mounted cockpit domain human-computer interaction SOA communication control method and system, aiming at the problems of poor human-computer interaction experience such as signal loss and return abnormality existing in the prior art, and solving the shortcomings of the prior art.

[0004] The present invention provides the following scheme:

[0005] A vehicle-mounted cockpit domain human-computer interaction SOA communication control method is applied to vehicle-mounted cockpit domain human-computer interaction SOA communication control, comprising:

[0006] An in-vehicle Ethernet for SOA communication is established based on the SOMEIP protocol stack, and a communication robustness mechanism is established at the Framework layer of the Android operating system of the cockpit domain controller. The communication robustness mechanism includes: SOA anti-explosion mechanism, SOA multi-application setting immediate response mechanism and SOA service cache mechanism;

[0007] Obtain HMI signals in the CarService component through the preset configuration table and establish the corresponding relationship between downlink and uplink signal values;

[0008] According to the SOA multi-application setting, an immediate response mechanism is provided to mutually decouple the multi-application calling processes and synchronize the state changes, and immediately simulate and return the corresponding normal execution results when interacting, process the underlying signals reported from the SOMEIP protocol stack or middleware, and filter and report the state changes of multi-application calling;

[0009] The SOA service cache mechanism is used to optimize the HMI signal status and cache the received event-type signals until the cockpit domain control enters the STR power supply, clearing the SOA signal cache.

[0010] Furthermore, the in-vehicle Ethernet for SOA communication is established based on the SOMEIP protocol stack, and a communication robustness mechanism is established at the Framework layer of the Android operating system of the cockpit domain controller, further including:

[0011] Implementing a signal management strategy based on a timestamp-based signal request queue, wherein the signal management strategy records the timestamp of each signal request and processes the signal in the time order of the signal request;

[0012] Setting a maximum frequency threshold of signal requests and performing real-time detection, and when it is detected that the frequency of signal requests exceeds the maximum frequency threshold, placing signals outside the signal request queue into the signal request queue;

[0013] The signal request queue is detected in real time, and based on the intelligent signal request merging algorithm, the signal requests with the same target and parameters inside and outside the signal request queue are identified.

[0014] Furthermore, the real-time detection of the signal request queue is performed based on the intelligent signal request merging algorithm to identify signal requests with the same target and parameters inside and outside the signal request queue, specifically:

[0015] The communication robustness mechanism dynamically adjusts the parameters of the merging strategy based on the real-time load and performance feedback of the on-board system;

[0016] The communication robustness mechanism detects whether the signal request is a high priority request, and for high priority signal requests, configures the corresponding sending mechanism to merge standards or direct sending.

[0017] Furthermore, the HMI signal is obtained in the CarService component through the preset configuration table, and the corresponding relationship between the downlink and uplink signal values ​​is established, specifically:

[0018] The preset configuration table is used to manage and define a data structure or database related to the HMI, and the corresponding relationship between the downlink and uplink signal values ​​is specifically for buffer management of signal requests and frequency control of signal requests.

[0019] Furthermore, the immediate response mechanism is set according to the SOA multi-application, the multi-application call process is mutually decoupled and the state change is synchronized, and the corresponding normal execution result is immediately simulated and returned during the interaction, the underlying signal reported from the SOMEIP protocol stack or middleware is processed, and the state change of the multi-application call is filtered and reported, further including:

[0020] Establish a multi-application call manager responsible for maintaining an application call registry, recording each application's call request and status for a specific function;

[0021] Analyze and verify call requests from different applications based on the call request parsing engine, and detect the communication format and interaction process when the state changes according to the state synchronization protocol;

[0022] The calculation result of the instant feedback generator is obtained. When the user performs a setting operation, the instant feedback generator immediately generates a simulation execution result according to a preset response template, and the simulation execution result is distributed to all registered applications through the multi-application call manager.

[0023] Furthermore, the multi-application call manager is specifically a vehicle system component responsible for coordinating and managing call requests from multiple applications to vehicle functions;

[0024] The call request parsing engine is specifically a system component for analyzing and processing call requests from different application programs;

[0025] The instant feedback generator is specifically a system component responsible for generating and returning the simulation execution result in real time when the user performs an operation.

[0026] A vehicle-mounted cockpit domain human-computer interaction SOA communication control system, used to implement the vehicle-mounted cockpit domain human-computer interaction SOA communication control method, comprising:

[0027] A communication robustness mechanism establishment module is used to establish an in-vehicle Ethernet for SOA communication based on the SOMEIP protocol stack, and to establish a communication robustness mechanism at the Framework layer of the Android operating system of the cockpit domain controller. The communication robustness mechanism includes: SOA anti-explosion mechanism, SOA multi-application setting immediate response mechanism and SOA service cache mechanism;

[0028] The module for establishing the correspondence relationship between downlink and uplink signal values ​​obtains the HMI signal in the CarService component through the preset configuration table and establishes the correspondence relationship between the downlink and uplink signal values;

[0029] The multi-application call status filtering and reporting module sets an immediate response mechanism according to the SOA multi-application, decouples the multi-application call processes from each other and synchronizes the state changes, and immediately simulates and returns the corresponding normal execution results when interacting, processes the underlying signals reported from the SOMEIP protocol stack or middleware, and filters and reports the state changes of multi-application calls;

[0030] The SOA signal cache optimization and clearing module uses the SOA service cache mechanism to optimize the HMI signal status and cache the received event-type signals until the cockpit domain control enters the STR power supply, clearing the SOA signal cache.

[0031] A smart cockpit is provided with the vehicle-mounted cockpit domain human-computer interaction SOA communication control system.

[0032] An electronic device comprises: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the method.

[0033] A computer-readable storage medium stores a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of the method.

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

[0035] The present invention enhances the human-computer interaction experience by realizing the associated synchronous changes of multiple applications to the same functional state, thereby ensuring the consistency of display states between different applications, eliminating user confusion caused by inconsistent states, and providing a clear and coherent interactive interface, thereby significantly improving the user's interactive experience.

[0036] The present invention improves communication reliability by introducing SOA communication robustness mechanisms, especially anti-explosion points and application call immediate return mechanisms, effectively preventing communication congestion and system crashes caused by frequent user operations, ensuring that the communication process remains stable and reliable even under high load conditions, thereby ensuring the smoothness of human-computer interaction.

[0037] The present invention optimizes communication efficiency. By adopting the SOA_Service component caching strategy, the application layer can directly obtain the service status through the system cache without frequently initiating calls to the execution end or the cloud. This greatly reduces communication delays and speeds up data processing, which is especially important for cockpit HMI displays that require fast responses. It further improves the response speed of user operations and the overall performance of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0039] Figure 1 It is a flow chart of the SOA communication control method for human-computer interaction in the vehicle cockpit domain.

[0040] Figure 1A It is a flow chart of the optimization technical solution of step S1.

[0041] Figure 1B It is a flow chart of the optimization technical solution of step S13.

[0042] Figure 1C It is a flow chart of the optimization technical solution of step S3.

[0043] Figure 2 It is the architecture diagram of the vehicle cockpit domain human-computer interaction SOA communication control system.

[0044] Figure 3 It is a SOA communication interaction block diagram between cockpit domain control and execution end domain control.

[0045] Figure 4 It is a timing diagram of the anti-explosion mechanism.

[0046] Figure 5 It is a flowchart of the robustness mechanism signal processing.

[0047] Figure 6 It is a flow chart of the implementation method of the embodiment of the present application in a specific application scenario.

[0048] Figure 7 It is a structural diagram of an electronic device. DETAILED DESCRIPTION

[0049] The technical solution of the present invention will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0050] like Figure 1 The vehicle cockpit domain human-computer interaction SOA communication control method shown is applied to vehicle cockpit domain human-computer interaction SOA communication control, including:

[0051] Step S1, establishing an in-vehicle Ethernet for SOA communication based on the SOMEIP protocol stack, and establishing a communication robustness mechanism at the Framework layer of the Android operating system of the cockpit domain controller, wherein the communication robustness mechanism includes: SOA anti-explosion mechanism, SOA multi-application setting immediate response mechanism and SOA service cache mechanism;

[0052] Step S2, obtain HMI signals in the CarService component through the preset configuration table, and establish a corresponding relationship between downlink and uplink signal values; the purpose of this step is to realize the SOA anti-explosion mechanism through the interactive display and clickable signals of the CarService component, and the SOA anti-explosion mechanism includes cache management of signal requests and frequency control of signal requests;

[0053] Step S3, according to the SOA multi-application setting immediate response mechanism, the multi-application call process is mutually decoupled and synchronized state changes, and the corresponding normal response is immediately simulated and returned during interaction.

[0054] Execution result, processes the underlying signal reported from the SOMEIP protocol stack or middleware, filters and reports the status changes of multiple application calls; in this step, the normal execution result corresponding to the immediate simulation return can be determined according to the system clock cycle to determine the time of "immediate simulation return". For example, if the system clock cycle is in milliseconds, then the normal execution result corresponding to the immediate simulation return is also in milliseconds.

[0055] Step S4, using the SOA service cache mechanism to optimize the HMI signal state, cache the received event-type signal, and clear the SOA signal cache until the cockpit domain control enters the STR power supply.

[0056] The technical solution provided in steps S1 to S4 is based on the robust service communication mechanism of the SOME / IP protocol stack in the vehicle Ethernet environment to enhance the stability and response speed of the vehicle infotainment system. The robust service communication mechanism is particularly aimed at the communication problems in the service-oriented architecture (SOA). The overall performance and user experience of the vehicle system are improved through the intelligent strategy in the technical solution.

[0057] The technical solution provided by steps S1 to S4 establishes a communication robustness mechanism in the Framework layer of the Android operating system, so that the system can better handle high loads and network anomalies, ensuring the continuity and reliability of services. The SOA anti-explosion mechanism effectively prevents system overload caused by a large number of signal requests in a short period of time through cache management and frequency control, thereby improving the stability and security of the system. The SOA multi-application setting immediate response mechanism allows the system to quickly respond to user operations in a multi-application environment, while decoupling the dependencies between applications, improving the system's response speed and user experience.

[0058] The SOA service cache mechanism reduces frequent access to the underlying hardware and optimizes system performance by caching the HMI signal status. At the same time, by clearing the cache when the power status changes, the correctness and update of the system status are ensured. Through the preset configuration table and CarService components, the system can efficiently process HMI signals, realize fast display of signals and response to user operations, and improve the fluency of user interaction.

[0059] In the process of calling multiple applications, the normal execution results are returned by simulation, which improves the instant feedback of user operations and enhances the user's operating experience. When the cockpit domain controller enters a specific power state (such as STR), the SOA signal cache is automatically cleared, which reduces memory usage and improves system startup speed and operating efficiency.

[0060] In the technical solutions provided in steps S1 to S4, STR refers to the "sleep" or "standby" state in the field of automotive electronics and power management. The system is put into a low-energy state through power management to reduce energy consumption when the vehicle is turned off or inactive. STR is the abbreviation of Stop, Turn, and Rear.

[0061] like Figure 1A As shown, preferably, in step S1, the in-vehicle Ethernet for SOA communication is established based on the SOMEIP protocol stack, and a communication robustness mechanism is established at the Framework layer of the Android operating system of the cockpit domain controller, further comprising:

[0062] Step S11, implementing a signal management strategy based on the timestamp signal request queue, wherein the signal management strategy records the timestamp of each signal request and performs signal processing in the time sequence of the signal requests;

[0063] Step S12, setting a maximum frequency threshold of signal requests and performing real-time detection, and when it is detected that the frequency of signal requests exceeds the maximum frequency threshold, placing signals outside the signal request queue into the signal request queue;

[0064] Step S13: perform real-time detection on the signal request queue, and identify signal requests with the same target and parameters inside and outside the signal request queue based on an intelligent signal request merging algorithm.

[0065] The optimization technical solution provided in steps S11 to S13 optimizes the SOA communication process based on the SOME / IP protocol stack in the vehicle-mounted Ethernet through a refined signal management strategy to improve the efficiency of signal processing and the response speed of the system, and enhances the robustness and stability of communication by introducing timestamp management, frequency control and intelligent merging algorithms, ensuring that signal requests are processed in the order in which they are initiated, ensuring the fairness and sequentiality of signal processing, preventing system overload caused by excessive signal requests, helping to protect the vehicle-mounted system from the impact of high-frequency signal requests, improving the stability of the system, reducing repeated requests for the same resources, optimizing network traffic and the use of system resources, and improving communication efficiency.

[0066] The optimization technical solution provided in steps S11 to S13 also reduces unnecessary signal transmission through an intelligent merging algorithm, thereby saving network bandwidth and processing resources, enabling the system to respond to user operations more quickly and reducing waiting time, thereby improving the user's interactive experience and optimizing the signal processing process, so that the vehicle-mounted system can better adapt to possible future expansions and maintain the long-term effectiveness of the system.

[0067] like Figure 1B As shown, exemplary, in step S13, the signal request queue is detected in real time, and based on the intelligent signal request merging algorithm, signal requests with the same target and parameters inside and outside the signal request queue are identified, specifically:

[0068] Step S131, the communication robustness mechanism dynamically adjusts the parameters of the merging strategy according to the real-time load and performance feedback of the vehicle system;

[0069] Step S132, the communication robustness mechanism detects whether the signal request is a high priority request. For high priority signal requests, the corresponding sending mechanism is configured as a combined standard or direct sending to ensure timely response of key functions.

[0070] The optimization technical solution provided in step S131 to step S132 dynamically adjusts the signal request merging strategy and priority management to adapt to the communication needs of the vehicle system under different load and performance conditions, ensuring timely response of key functions and efficient use of system resources, wherein:

[0071] Step S131 implements the dynamic adjustment of the merging strategy, allowing the communication robustness mechanism to dynamically adjust the parameters of the signal request merging strategy according to the real-time load and performance feedback of the vehicle system. Based on the adaptive adjustment capability, the system can optimize the signal processing process according to the current working status, thereby maintaining efficient communication performance under different working conditions.

[0072] Step S132 implements priority management. By detecting the priority of signal requests, the system can be configured to merge standards or send directly for high-priority signal requests. This priority management mechanism ensures that critical functions (such as safety-related signals) can receive timely responses and maintain fast processing of critical signals even when the system load is high.

[0073] The intelligent merging algorithm and priority management of the optimization technical solution provided in steps S131 to S132 enable the vehicle-mounted system to more effectively utilize limited communication resources, reduce unnecessary signal transmission, thereby saving bandwidth and processing time, and improving overall communication efficiency. For signal requests for key functions, the vehicle-mounted system can ensure their priority processing. In emergency situations, safety-related signals that are prioritized by the vehicle-mounted system can be processed quickly, thereby ensuring the safety of the vehicle and passengers. In the face of high loads or performance fluctuations, stable and reliable communication can still be maintained, which is crucial to improving user trust and satisfaction with the vehicle-mounted system.

[0074] To sum up, the optimization technical solution provided by steps S131 to S132 not only improves the efficiency of signal processing and the stability of the system by dynamically adjusting the merging strategy and priority management, but also ensures the timely response of key functions, thereby improving the reliability of the vehicle system and user experience.

[0075] Preferably, in step S2, the HMI signal is obtained in the CarService component through the preset configuration table, and a corresponding relationship between downlink and uplink signal values ​​is established, specifically:

[0076] The preset configuration table is used to manage and define data structures or databases related to the HMI, and the corresponding relationship between the downlink and uplink signal values ​​is specifically the cache management of signal requests and the frequency control of signal requests, which is used to implement the SOA anti-explosion mechanism.

[0077] The central idea of ​​step S2 is to use the preset configuration table in the CarService component to manage and define the data structure or database related to the HMI (Human Machine Interface), and to achieve cache management and frequency control of signal requests by establishing the corresponding relationship between downlink and uplink signal values. Step S2 is a key component of the SOA anti-explosion mechanism, which aims to improve the stability and responsiveness of the vehicle communication system, and is used to achieve multiple functions such as signal request management, cache management, and frequency control.

[0078] Based on the technical means of step S2, the vehicle-mounted system can effectively manage the HMI signal, ensure the orderly processing of the signal request, and realize the cache management of the signal request by establishing the correspondence between the downlink and uplink signal values, so as to realize the storage and reuse of the previously processed signal request, thereby reducing the repeated requests for resources and improving the processing efficiency.

[0079] By controlling the frequency of signal requests, the vehicle system can prevent system overload caused by excessive signal requests, protect the vehicle system from the impact of high-frequency signal requests, and ensure the stability and reliability of the vehicle system.

[0080] like Figure 1C As shown, in step S3, the immediate response mechanism is set according to the SOA multi-application, the multi-application call process is decoupled from each other and the state change is synchronized, and the corresponding normal execution result is immediately simulated and returned during the interaction, and the underlying signal reported from the SOMEIP protocol stack or middleware is processed, and the state change of the multi-application call is filtered and reported, which further includes:

[0081] Step S31, establishing a multi-application call manager responsible for maintaining an application call registration table, recording each application's call request and status for a specific function;

[0082] Step S32, based on the call request parsing engine, analyzing and verifying the call requests from different applications, and detecting the communication format and interaction process when the state changes according to the state synchronization protocol, so as to ensure that all related applications can receive the latest state information;

[0083] Step S33, obtaining the calculation result of the instant feedback generator. When the user performs a setting operation, the instant feedback generator immediately generates a simulation execution result according to a preset response template, and the simulation execution result is distributed to all registered applications through the multi-application call manager.

[0084] The optimization technical solution provided by steps S31 to S33 builds an efficient and reliable multi-application call management framework, realizes the decoupling, state synchronization and instant feedback of the multi-application call process in the SOA environment, and ensures the communication efficiency and user experience in the multi-application environment by maintaining the application call registry, analyzing and verifying call requests, and generating instant feedback.

[0085] The optimization technical solution provided in steps S31 to S33 realizes multiple functions such as application call management, call request parsing and verification, state synchronization and communication format detection, instant feedback generation and simulation execution result distribution. By establishing a multi-application call manager, it cooperates with the vehicle system to record and track each application's call request and status for specific functions, thereby improving the transparency and traceability of call processing. The call request parsing engine is responsible for analyzing and verifying call requests from different applications, ensuring the legitimacy and correctness of the requests, and by detecting the communication format and interaction process when the state changes, it ensures that all relevant applications can receive the latest status information, thereby maintaining consistency and collaboration between different applications.

[0086] The optimization technical solution provided in steps S31 to S33 is based on an instant feedback generator. When the user performs a setting operation, a simulated execution result is immediately generated according to a preset response template, forming an instant feedback mechanism. The instant feedback mechanism greatly improves the user's interactive experience, allowing the user to immediately see the effect of the operation, thereby improving the user experience.

[0087] The optimization technical solution provided by steps S31 to S33 generates simulation execution results by distributing simulation execution results, and distributes them to all registered applications through a multi-application call manager, thereby ensuring timely updating of information and synchronization between applications, improving the overall response speed, and enhancing the user experience, so that users can obtain a smoother and more intuitive interactive experience.

[0088] Exemplarily, the multi-application call manager is specifically a vehicle system component responsible for coordinating and managing call requests from multiple application programs APP to vehicle functions;

[0089] The call request parsing engine is specifically a system component for analyzing and processing call requests from different application programs;

[0090] The instant feedback generator is specifically a system component responsible for generating and returning the simulation execution result in real time when the user performs an operation;

[0091] It can be seen from the detailed description of the multi-application adjustment manager, call request parsing engine and instant feedback generator in this embodiment that the above-mentioned components and managers work together to ensure that the call requests for vehicle functions are effectively managed, analyzed, processed, and can be fed back to users in real time, thereby realizing coordinated management of the operation of the vehicle system, request analysis and processing, instant feedback, enhanced system stability and improved response speed, so that the vehicle system can more effectively process multi-application call requests, provide instant feedback, improve user experience, and ensure system stability and security.

[0092] For the method steps disclosed in the above embodiments, the method steps are described as a series of action combinations for the purpose of simple description, but those skilled in the art should know that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0093] Any process or method description described in a flowchart or other manner may be understood as representing a module, fragment or portion of a code including one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations, in which the order shown or discussed may not be followed, including executing and implementing the functions in a substantially simultaneous manner or in a reverse order according to the functions involved, or executing computer instructions and implementing the corresponding functions according to program structures such as loops and branches, which can be naturally understood by those skilled in the art when implementing the embodiments of the present invention.

[0094] like Figure 2 The vehicle-mounted cockpit domain human-computer interaction SOA communication control system shown is used to implement the vehicle-mounted cockpit domain human-computer interaction SOA communication control method described in the embodiment of the present application, including:

[0095] A communication robustness mechanism establishment module is used to establish an in-vehicle Ethernet for SOA communication based on the SOMEIP protocol stack, and to establish a communication robustness mechanism at the Framework layer of the Android operating system of the cockpit domain controller. The communication robustness mechanism includes: SOA anti-explosion mechanism, SOA multi-application setting immediate response mechanism and SOA service cache mechanism;

[0096] The module for establishing the correspondence relationship between downlink and uplink signal values ​​obtains the HMI signal in the CarService component through the preset configuration table and establishes the correspondence relationship between the downlink and uplink signal values;

[0097] The multi-application call status filtering and reporting module sets an immediate response mechanism according to the SOA multi-application, decouples the multi-application call processes from each other and synchronizes the state changes, and immediately simulates and returns the corresponding normal execution results when interacting, processes the underlying signals reported from the SOMEIP protocol stack or middleware, and filters and reports the state changes of multi-application calls;

[0098] The SOA signal cache optimization and clearing module uses the SOA service cache mechanism to optimize the HMI signal status and cache the received event-type signals until the cockpit domain control enters the STR power supply, clearing the SOA signal cache.

[0099] The implementation methods of the system described above are merely illustrative, for example, the various functional modules, units or subsystems in the system may or may not be physically separated, or may or may not be physical units, that is, they may be located in the same place, or they may be distributed to multiple different systems and their subsystems or modules. Those skilled in the art may select some or all of the functional modules, units or subsystems according to actual needs to achieve the purpose of the embodiments of the present invention, and those of ordinary skill in the art may understand and implement the above-mentioned situations without creative work.

[0100] like Figure 3 and Figure 4 As shown in the figure, the cockpit domain control SOA service capability is mainly reflected in the human-computer interaction, that is, the user operates the HMI to set or control a vehicle function, and displays the settings and function status. Other domain controllers execute the control instructions issued by the cockpit domain control and return the results. The SOA signal of the cockpit domain control system communicating with other domain controllers of the vehicle includes downlink instructions and uplink feedback values.

[0101] In order to achieve a good human-computer interaction experience for the cockpit domain control HMI and also meet the communication performance requirements of the cockpit domain control system, it is necessary to add signal uplink and downlink control and error handling mechanisms on the basis of realizing basic communication capabilities to enhance the robustness of its communication.

[0102] The main components of the SOA anti-explosion mechanism are as follows:

[0103] 1. SOA anti-explosion mechanism:

[0104] The SOA anti-explosion mechanism is mainly used to solve the problem of the impact of clicks of different frequencies on the cockpit domain control system when users operate the cockpit domain control HMI, and to balance the contradiction between smooth user experience and system communication reliability.

[0105] 2. SOA anti-explosion mechanism deployment location:

[0106] The SOA anti-explosion mechanism is deployed in the CarService component, which serves as the signal communication middleware on the system side. Its main functions are to process SOA signals, provide standardized interfaces and data formats, and provide signal transmission mechanisms.

[0107] 3. Applicable objects of SOA anti-explosion mechanism:

[0108] This mechanism is mainly applicable to signals that are displayed on the HMI and can be clicked, and there is a corresponding relationship between the downlink and uplink signal values. They are organized into a configuration table and preset in the CarService component.

[0109] 4. SOA anti-explosion strategy principle:

[0110] When the APP application sends the req0 signal for the first time, the CarService component sends it to the bottom layer and waits for the corresponding uplink resp0 signal to return;

[0111] If the APP application sends req1 and req2 signals during the waiting period, the CarService component needs to store them in the downstream cache, not send them to the bottom layer, and the cache needs to be overwritten and updated;

[0112] When the CarService component receives the uplink return resp0, it determines whether there is a value in the downlink cache. If so, the uplink return resp0 is not reported to the application, but is stored in the uplink cache, and the value in the downlink cache is sent to the bottom layer; the CarService component determines that there is no value in the downlink cache, and the uplink return resp0 is reported to the application

[0113] The CarService component starts a 2s timer after receiving the application request. If no uplink response is received, the most recently reported application status is reported as the timeout value or the SOA error code is reported.

[0114] like Figure 5 As shown in the SOA robustness flow chart, the cockpit domain control side has multiple applications setting and calling the same function. For example, when turning on the air conditioner, the air conditioner application, shortcut bar application, and voice application can all call it, among which:

[0115] 1. Principles and purposes of setting up immediate response mechanism for SOA multi-applications:

[0116] The principles and purposes of setting up an immediate response mechanism for multiple SOA applications are as follows:

[0117] 1) Multiple application calls are decoupled from each other, and each application can directly call the underlying interface capabilities

[0118] 2) Ensure synchronous state changes after multiple applications are called

[0119] 3) Multiple applications respond to user operations immediately after calling

[0120] 2. Deployment location of SOA multi-application immediate response mechanism:

[0121] The immediate response mechanism of SOA multi-application settings is deployed in CarService, and is deployed in the same service module as the SOA anti-explosion strategy, so that the two mechanisms are integrated and implemented.

[0122] 3. Implementation principle of SOA multi-application immediate response mechanism:

[0123] When the user performs a setting operation, after the application sends the instruction, the CarService component immediately simulates and returns the corresponding normal execution result. The relevant application that registers to monitor the setting status uses synchronous callback to the status to display the latest status. The basic logic is as follows:

[0124] The CarService component presets a list of paired signal values;

[0125] Each pair of signals can be set to enable the immediate response mechanism and explosion-proof point mechanism;

[0126] If the mechanism is enabled, the CarService component will immediately call back the target status to the application after receiving the application's downlink instruction request, and cache the callback;

[0127] Execute the reset 2s timer operation and execute the explosion prevention point mechanism;

[0128] After the CarService component sends a command, it starts the 200ms timing. If it times out, it determines whether there is a cached downlink request. If yes, it executes the request. If no, it determines whether there is an uplink cache. If yes, it reports it. If no, it waits for 2s timeout. During the 2s timeout, any uplink and downlink signals need to be executed. If 2s times out, it returns the last reported success value or abnormal value.

[0129] The CarService component needs to determine the execution result of the counterpart, that is, after the uplink signal returns normally, it needs to be compared with the immediate callback value. If they are the same, it will not be reported to the application. If they are different, it will be reported to the application.

[0130] Through this example, we can understand the basic principles of SOA service communication mechanism:

[0131] SOA service module:

[0132] The SOA service module processes the underlying signals reported by the SOMEIP protocol stack or middleware. The reporting principles are as follows:

[0133] For event cycle signals, according to the business layer requirements, if filtering is required, that is, reporting of status changes,

[0134] For event change signals, the signal is received and the signal status is judged to have changed again, that is, the status change is reported

[0135] For pure event signals, according to business needs, if filtering is required, that is, reporting of status changes, if filtering is not required in special scenarios, you can configure reporting as soon as it is received.

[0136] SOA service caching mechanism:

[0137] When the cockpit domain controller is powered on and the service establishes communication normally, the SOA service caches the received event-type signals to ensure that the upper-layer application can return quickly when getting the underlying signal. When the cockpit domain controller enters STR power, the SOA signal cache is cleared.

[0138] All application modules that rely on the underlying SOA signal need to call the get interface to actively obtain the underlying signal status after successfully registering and listening, to avoid the timing problems between the domain controllers and the startup of the internal modules of the cockpit domain controller when power is turned on, resulting in the registration SOAHAL layer being sent, but the upper layer not receiving it successfully, and the SOAHAL layer signal status not being reported when it has not changed.

[0139] SOA error code definition:

[0140] Service exceptions, process exceptions, and inter-process communication exceptions. Processes that have communication dependencies need to send the other end's exception information to the Error_handle module. After the exception is recovered, the normal operation of the system should be guaranteed.

[0141] SOA signal exception: define error codes for SOA signal exception types. When any of the following exceptions occurs in the signal, the SOA_Service layer needs to send the signal name + error code to the CarService component. The CarService component reports the error code and error type to the application, and the application needs to detect and process according to the business logic. The error code is defined as follows:

[0142]

[0143] like Figure 6 As shown, the technical solution provided by the embodiment of the present application can be summarized as the following process:

[0144] The SOA communication control method in the vehicle cockpit domain human-computer interaction is used to optimize the response speed and synchronization of user setting operations, including the following steps:

[0145] Step 1: Preset a list of paired signal values ​​in the CarService component, where each pair of signal values ​​corresponds to a specific vehicle setting state;

[0146] Step 2: Provide configuration options for each pair of signals to enable or disable the immediate response mechanism and the explosion prevention point mechanism. The immediate response mechanism is used to quickly feedback the results of user operations, and the explosion prevention point mechanism is used to control the frequency of signal transmission to prevent system overload.

[0147] Step 3: When the CarService component receives a downlink command request from the application, if the immediate response mechanism is activated, the CarService immediately generates and calls back a preset target state to the application, and caches the callback operation and its state value;

[0148] Step 4: The CarService component starts a second-level timer and executes the explosion prevention mechanism, which is used to control the frequency of signal sending to prevent system pressure caused by frequent user operations;

[0149] Step 5: After the CarService component sends the command, a millisecond timer is started. If the expected uplink response signal is not received within the time specified by the millisecond timer, the following judgment is made:

[0150] Step 5a, determining whether there is a cached downlink request, and if so, executing the downlink request;

[0151] Step 5b: If there is no cached downlink request, check whether there is a cached uplink response. If so, report the cached uplink response to the application.

[0152] Step 5c: If there is no cache of either downlink request or uplink response, continue to wait until the 2-second timer times out;

[0153] Step 5d: during the timeout period of the second-level timer, if any uplink or downlink signal is received, the corresponding operation is immediately performed;

[0154] Step 5e: If no uplink response signal is received after the second-level timer times out, the last successfully reported status value or abnormal value is returned;

[0155] Step 6: After receiving the uplink response signal, the CarService component compares the normal return result of the signal with the value of the immediate callback. If the two are the same, it will not be reported to the application again to avoid unnecessary communication; if the two are different, the difference will be reported to the application so that the application can take appropriate measures;

[0156] Step 7: The CarService component maintains a call log in real time during steps 1 to 6. The call log records the timestamps and status of all operations for problem diagnosis and system optimization.

[0157] Through the optimization technical solutions provided in steps one to seven, the embodiment of the present application can provide fast and synchronous feedback when the user performs vehicle setting operations. At the same time, through the explosion-proof point mechanism and the preset signal value list, the frequency of signal transmission and the use of system resources are effectively managed, ensuring the stability and response speed of the vehicle cockpit domain controller when processing user operations. In summary, the embodiment of the present application can further optimize the communication process, reduce unnecessary data transmission, and improve the communication efficiency of the system by comparing the normal return result of the uplink signal with the immediate callback value.

[0158] like Figure 7 As shown, the present invention provides a vehicle-mounted cockpit domain human-computer interaction SOA communication control method, and also provides a corresponding intelligent cockpit, electronic equipment and storage medium:

[0159] A smart cockpit is provided with the vehicle-mounted cockpit domain human-computer interaction SOA communication control system.

[0160] An electronic device comprises: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of a vehicle-mounted cockpit domain human-computer interaction SOA communication control method.

[0161] A computer-readable storage medium stores a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of a vehicle-mounted cockpit domain human-computer interaction SOA communication control method.

[0162] Figure 7 A schematic diagram of the structure of a computer device provided in an embodiment of the present application, wherein the device 800 includes a processor 801, a memory 802, a communication interface 803, and a bus 804. The processor 801, the memory 802, and the communication interface 803 communicate via the bus 804, and may also communicate via other means such as wireless transmission. The memory 802 is used to store instructions, and the processor 801 is used to execute instructions stored in the memory 802. The memory 802 stores program code 8021, and the processor 801 may call the program code 8021 stored in the memory 802 to execute the steps of the vehicle-mounted cockpit domain human-computer interaction SOA communication control method.

[0163] It should be understood that in the embodiment of the present application, the processor 801 may be a CPU, and the processor 801 may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0164] The memory 802 may include a read-only memory ROM and a random access memory RAM, and provide instructions and data to the processor 801. The memory 802 may also include a non-volatile random access memory. The memory 802 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (double date SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, ESDRAM), and so on.

[0165] DRAM, SLDRAM) and direct rambus random access memory (direct rambus RAM, DR RAM).

[0166] The bus 804 may include, in addition to the data bus, a power bus, a control bus, a status signal bus, etc. However, for the sake of clarity, various buses are labeled as bus 804 in the figure.

[0167] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid state drive (SSD).

[0168] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0169] In addition, those skilled in the art will appreciate that although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present invention and form different embodiments.

[0170] Any of the embodiments claimed in the book can be used in any combination in the embodiments of the present invention.

[0171] In the description of this specification, the description with reference to the terms "one embodiment", "example", "specific example", etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0172] In addition, the technical solutions between the various embodiments of the present invention can be combined with each other, but it must be based on the fact that ordinary technicians in the field can implement it. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0173] All features disclosed in this specification, or steps in all methods or processes disclosed, except mutually exclusive features and / or steps, can be combined in any way. Any feature disclosed in this specification, unless otherwise stated, can be replaced by other equivalent or alternative features with similar purposes. That is, unless otherwise stated, each feature is only an example of a series of equivalent or similar features. Throughout the specification, the same reference numerals indicate the same elements.

[0174] Those skilled in the art will appreciate that the modules in the devices in the embodiments can be adaptively changed and set in one or more devices different from the embodiments. The modules or units or components in the embodiments can be combined into one module or unit or component, and in addition they can be divided into multiple submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including corresponding claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner can be combined in any combination. Unless otherwise explicitly stated, each feature disclosed in this specification (including corresponding claims, abstracts and drawings) can be replaced by an alternative feature that provides the same, equivalent or similar purpose.

[0175] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A vehicle cockpit domain human-computer interaction SOA communication control method, applied to vehicle cockpit domain human-computer interaction SOA communication control, characterized in that: include: An in-vehicle Ethernet for SOA communication is established based on the SOMEIP protocol stack, and a communication robustness mechanism is established at the Framework layer of the Android operating system of the cockpit domain controller. The communication robustness mechanism includes: SOA anti-explosion mechanism, SOA multi-application setting immediate response mechanism and SOA service cache mechanism; Obtain HMI signals in the CarService component through the preset configuration table and establish the corresponding relationship between downlink and uplink signal values; According to the SOA multi-application setting, an immediate response mechanism is provided to mutually decouple the multi-application calling processes and synchronize the state changes, and immediately simulate and return the corresponding normal execution results when interacting, process the underlying signals reported from the SOMEIP protocol stack or middleware, and filter and report the state changes of multi-application calling; The SOA service cache mechanism is used to optimize the HMI signal status and cache the received event-type signals until the cockpit domain control enters the STR power supply, clearing the SOA signal cache.

2. The vehicle-mounted cockpit domain human-computer interaction SOA communication control method according to claim 1 is characterized in that: The in-vehicle Ethernet for SOA communication is established based on the SOMEIP protocol stack, and a communication robustness mechanism is established at the Framework layer of the Android operating system of the cockpit domain controller, further comprising: Implementing a signal management strategy based on a timestamp-based signal request queue, wherein the signal management strategy records the timestamp of each signal request and processes the signal in the time order of the signal request; Setting a maximum frequency threshold of signal requests and performing real-time detection, and when it is detected that the frequency of signal requests exceeds the maximum frequency threshold, placing signals outside the signal request queue into the signal request queue; The signal request queue is detected in real time, and based on the intelligent signal request merging algorithm, the signal requests with the same target and parameters inside and outside the signal request queue are identified.

3. The vehicle-mounted cockpit domain human-computer interaction SOA communication control method according to claim 2 is characterized in that: The real-time detection of the signal request queue is based on the intelligent signal request merging algorithm to identify signal requests with the same target and parameters inside and outside the signal request queue, specifically: The communication robustness mechanism dynamically adjusts the parameters of the merging strategy based on the real-time load and performance feedback of the on-board system; The communication robustness mechanism detects whether the signal request is a high priority request, and for high priority signal requests, configures the corresponding sending mechanism to merge standards or direct sending.

4. The vehicle-mounted cockpit domain human-computer interaction SOA communication control method according to claim 1 is characterized in that: The HMI signal is obtained in the CarService component through the preset configuration table, and the corresponding relationship between the downlink and uplink signal values ​​is established, specifically: The preset configuration table is used to manage and define a data structure or database related to the HMI, and the corresponding relationship between the downlink and uplink signal values ​​is specifically for buffer management of signal requests and frequency control of signal requests.

5. The vehicle-mounted cockpit domain human-computer interaction SOA communication control method according to claim 1 is characterized in that: The method of setting an immediate response mechanism according to the SOA multi-application, decoupling the multi-application call processes from each other and synchronizing the state changes, and immediately simulating and returning the corresponding normal execution results when interacting, processing the underlying signals reported from the SOMEIP protocol stack or middleware, filtering and reporting the state changes of the multi-application calls, further includes: Establish a multi-application call manager responsible for maintaining an application call registry, recording each application's call request and status for a specific function; Analyze and verify call requests from different applications based on the call request parsing engine, and detect the communication format and interaction process when the state changes according to the state synchronization protocol; The calculation result of the instant feedback generator is obtained. When the user performs a setting operation, the instant feedback generator immediately generates a simulation execution result according to a preset response template, and the simulation execution result is distributed to all registered applications through the multi-application call manager.

6. The vehicle-mounted cockpit domain human-computer interaction SOA communication control method according to claim 5 is characterized in that: The multi-application call manager is specifically a vehicle system component responsible for coordinating and managing call requests from multiple applications to vehicle functions; The call request parsing engine is specifically a system component for analyzing and processing call requests from different application programs; The instant feedback generator is specifically a system component responsible for generating and returning the simulation execution result in real time when the user performs an operation.

7. A vehicle-mounted cockpit domain human-computer interaction SOA communication control system, used to implement the vehicle-mounted cockpit domain human-computer interaction SOA communication control method according to any one of claims 1 to 6, characterized in that: include: A communication robustness mechanism establishment module is used to establish an in-vehicle Ethernet for SOA communication based on the SOMEIP protocol stack, and to establish a communication robustness mechanism at the Framework layer of the Android operating system of the cockpit domain controller. The communication robustness mechanism includes: SOA anti-explosion mechanism, SOA multi-application setting immediate response mechanism and SOA service cache mechanism; The module for establishing the correspondence relationship between downlink and uplink signal values ​​obtains the HMI signal in the CarService component through the preset configuration table and establishes the correspondence relationship between the downlink and uplink signal values; The multi-application call status filtering and reporting module sets an immediate response mechanism according to the SOA multi-application, decouples the multi-application call processes from each other and synchronizes the state changes, and immediately simulates and returns the corresponding normal execution results when interacting, processes the underlying signals reported from the SOMEIP protocol stack or middleware, and filters and reports the state changes of multi-application calls; The SOA signal cache optimization and clearing module uses the SOA service cache mechanism to optimize the HMI signal status and cache the received event-type signals until the cockpit domain control enters the STR power supply, clearing the SOA signal cache.

8. A smart cockpit, characterized in that: The smart cockpit is provided with the vehicle-mounted cockpit domain human-computer interaction SOA communication control system described in claim 7.

9. An electronic device, characterized in that: include: A processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the method described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: It stores a computer program executable by an electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the method described in any one of claims 1 to 6.

Images