Vehicle-based instrument business processing method, instrument development method and device
By splitting the vehicle instrument application into instrument middleware and application, and using SOA architecture design, the problem of strong code coupling of instrument application is solved, unified data adaptation and independent development of business functions are realized, processing efficiency and development convenience are improved sex.
Patent Information
- Application Number
- CN202410927318.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-11
- Publication Date
- 2024-11-22
AI Technical Summary
The existing vehicle instrument applications have strong coupling of business processing codes and display codes, which leads to a great impact on the normal operation of instrument applications and is difficult to reuse between different models and platforms, resulting in low development efficiency.
Split the instrument application into two parts: instrument middleware and instrument application. The instrument middleware is designed based on the SOA architecture. Through the adaptation layer, the vehicle signal is converted into standard internal signals, and the target service is notified for business processing to achieve unified data adaptation. and independent development and maintenance of business functions.
Reduce the coupling and dependence of instrument applications, improve the quality and accuracy of data specifications and processing results, optimize the instrument business processing process, improve the overall business operation effect, and provide general instrument development tools to improve the Development efficiency and maintenance ease.
Smart Images

Figure CN119003199A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of vehicle technology, and in particular to a vehicle-based instrument business processing method, an instrument development method and a device. Background Art
[0002] As a window for human-vehicle interaction, the instrument panel provides the driver with the vehicle's operating status and various parameters, and is an important part of the vehicle.
[0003] In the related art, the business processing code and display code of the instrument application on the vehicle are mixed together, and the code has a strong dependency. Once a problem occurs in the code, it will have a significant impact on the normal operation of the instrument application. Summary of the invention
[0004] The embodiments of the present application provide a vehicle-based instrument business processing method, an instrument development method and a device, which optimize the instrument business processing flow and improve the overall business operation effect.
[0005] In a first aspect, an embodiment of the present application provides a vehicle instrument service processing method, which is applied to an instrument system on a vehicle, wherein the instrument system includes an instrument middleware and multiple instrument applications, and the instrument middleware includes multiple preset services. The method includes:
[0006] Receiving a vehicle signal and a target subject event to which the vehicle signal belongs, sent by an out-of-domain system; the out-of-domain system is a system on the vehicle other than the instrument system;
[0007] Converting the vehicle signal into a standard instrument internal signal;
[0008] Notifying a target service corresponding to the target subject event among the plurality of preset services;
[0009] The target service is used to obtain the internal signal of the standard instrument, and based on the internal signal of the standard instrument, the target service is used to perform business processing to obtain a processing result;
[0010] The processing result is sent to a corresponding instrument application and / or an external system to output corresponding information based on the processing result.
[0011] In a possible implementation manner, the signal is represented in the form of a variable; the converting the vehicle signal into a standard instrument internal signal includes:
[0012] Assign the value of the vehicle signal variable to the standard instrument internal signal variable that represents the same business meaning as the vehicle signal variable.
[0013] In a possible implementation manner, the memory space is divided in the form of subject events; after converting the vehicle signal into a standard instrument internal signal, the method further includes:
[0014] The standard instrument internal signal is written into the memory space corresponding to the target subject event in the shared memory.
[0015] In a possible implementation manner, notifying a target service corresponding to the target subject event among the plurality of preset services includes:
[0016] In response to data update stored in the memory space corresponding to the target subject event in the shared memory, sending a notification message to a target service subscribed to the target subject event;
[0017] The adopting the target service to obtain the internal signal of the standard instrument includes:
[0018] The target service is used to read the internal signal of the standard instrument from the memory space corresponding to the target subject event in the shared memory.
[0019] In a possible implementation manner, the process of performing business processing based on the internal signal of the standard instrument and using the target service to obtain a processing result includes:
[0020] The business processing strategy in the target service is adopted to process the internal signal of the standard instrument to obtain a processing result.
[0021] In a possible implementation, sending the processing result to a corresponding instrument application and / or an external system includes:
[0022] Using an in-domain application to call a service interface corresponding to the target service to obtain the processing result;
[0023] and / or,
[0024] The out-of-domain system is used to call the service interface corresponding to the target service to obtain the processing result.
[0025] In a possible implementation manner, the instrument middleware includes an adaptation layer, and the adaptation layer includes an intra-domain adaptation function module, an extra-domain adaptation function module and a protocol stack function module; and further includes:
[0026] Adopting the intra-domain adaptation function module to communicate with the intra-domain application based on the communication protocol in the protocol stack function module;
[0027] The out-of-domain adaptation function module is used to communicate with the out-of-domain system based on the communication protocol in the protocol stack function module.
[0028] In a possible implementation, the instrument middleware includes a service layer, which includes a basic service function module, an instrument logic service function module, and a service management function module; and further includes:
[0029] Using the basic service function module to process the basic business of the instrument system;
[0030] The instrument logic service function module is used to process the instrument logic business of the instrument system;
[0031] The service management function module is used to manage the multiple preset services.
[0032] In a second aspect, an embodiment of the present application provides a vehicle instrument development method, the method being applied to an instrument development terminal, the method comprising:
[0033] Get the first instrument middleware;
[0034] Modifying the adaptation layer code in the first instrument middleware based on user operations so that the adaptation layer code can identify the vehicle signal sent by the external system and convert it into a standard instrument internal signal;
[0035] Based on user operations, multiple preset services of the service layer in the first meter middleware are configured so that the configured services meet the meter business requirements;
[0036] The modified and configured second instrument middleware is integrated into the instrument system, and a plurality of instrument applications are deployed in the instrument system; the instrument system is used for instrument business processing of the vehicle.
[0037] In a possible implementation manner, the signal is represented in the form of a variable; and the adaptation layer code in the first instrument middleware is modified based on the user operation so that the adaptation layer code can identify the vehicle signal sent by the external system and convert it into a standard instrument internal signal, including:
[0038] Based on user operations, an assignment code for assigning the value of the vehicle signal variable to the standard instrument internal signal variable representing the same business meaning as the vehicle signal variable is added after the signal receiving code for receiving the vehicle signal in the adaptation layer code, so that the adaptation layer code can recognize the vehicle signal sent by the external system and convert it into a standard instrument internal signal.
[0039] In a possible implementation manner, configuring a plurality of preset services of the service layer in the first meter middleware based on the user operation so that the configured services meet the meter business requirements includes:
[0040] For any preset service among the plurality of preset services, configuring whether the preset service is enabled based on a user operation;
[0041] When there are multiple preset business processing policies for any enabled preset service, the selected preset business processing policy is determined as the business processing policy corresponding to the preset service based on the user operation, so that the preset service performs business processing through the corresponding business processing policy.
[0042] In a third aspect, an embodiment of the present application provides a vehicle instrument service processing device, which is arranged in a vehicle machine device, wherein an instrument system is deployed on the vehicle machine device, wherein the instrument system includes an instrument middleware and a plurality of instrument applications, wherein the instrument middleware includes a plurality of preset services, and wherein the device includes:
[0043] A receiving module, used for receiving a vehicle signal sent by an out-of-domain system and a target subject event to which the vehicle signal belongs; the out-of-domain system is a system on the vehicle other than the instrument system;
[0044] A conversion module, used for converting the vehicle signal into a standard instrument internal signal;
[0045] A notification module, used for notifying a target service corresponding to the target subject event among the plurality of preset services;
[0046] A processing module, used to obtain the internal signal of the standard instrument by using the target service, and based on the internal signal of the standard instrument, use the target service to perform business processing to obtain a processing result;
[0047] The sending module is used to send the processing result to the corresponding instrument application and / or the external system to output corresponding information based on the processing result.
[0048] In a fourth aspect, an embodiment of the present application provides a vehicle instrument development device, the device being arranged in an instrument development terminal, the device comprising:
[0049] An acquisition module, used for acquiring the first instrument middleware;
[0050] A modification module, used to modify the adaptation layer code in the first instrument middleware based on user operations, so that the adaptation layer code can recognize the vehicle signal sent by the external system and convert it into a standard instrument internal signal;
[0051] A configuration module, configured to configure a plurality of preset services of the service layer in the first meter middleware based on user operations, so that the configured services meet the meter business requirements;
[0052] The integration module is used to integrate the modified and configured second instrument middleware into the instrument system and deploy multiple instrument applications in the instrument system; the instrument system is used for vehicle instrument business processing.
[0053] In a fifth aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory communicatively connected to the processor;
[0054] The memory stores computer-executable instructions;
[0055] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the method described in any one of the first aspects or the method described in any one of the second aspects.
[0056] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the method described in any one of the first aspect or the method described in any one of the second aspect.
[0057] In a seventh aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the method described in any one of the first aspect or the method described in any one of the second aspect.
[0058] The vehicle-based instrument business processing method, instrument development method and device provided in the embodiments of the present application split the traditional instrument application into two parts: an instrument middleware for instrument business processing and an instrument application for outputting instrument information. The instrument middleware is designed based on the SOA architecture. By dividing the business functions involved into multiple independent preset services, these preset services can be independently developed and maintained, reducing dependencies and making them more maintainable. On this basis, in the process of processing instrument business, the adaptation function of the instrument middleware can convert the vehicle signal from the external system into a standard instrument internal signal, realize the unified adaptation of data, improve the data standardization, and can also notify the whole vehicle. The target service corresponding to the target subject event to which the signal belongs enables the target service to obtain the internal signal of the standard instrument, and perform business processing based on the internal signal of the standard instrument to obtain the processing result. By selecting the corresponding preset service according to different processing requirements, the business processing can be customized and optimized, and the quality and accuracy of the processing results can be improved. By sending the processing results to the corresponding instrument application and / or external system, the instrument application and / or external system can output the corresponding information based on the processing results. In summary, using instrument middleware for instrument business processing can improve data standardization, improve the quality and accuracy of processing results, thereby optimizing the instrument business processing process and improving the overall business operation effect. BRIEF DESCRIPTION OF THE DRAWINGS
[0059] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0060] Figure 1 A schematic diagram of an application scenario provided for this application;
[0061] Figure 2 A schematic diagram of a process flow of a vehicle instrument development method provided in this application;
[0062] Figure 3 A flow chart of a vehicle instrument service processing method provided in this application;
[0063] Figure 4 A schematic diagram of an instrument service processing process provided for this application;
[0064] Figure 5 A schematic diagram of the structure of a vehicle instrument development device provided in this application;
[0065] Figure 6 A schematic diagram of the structure of a vehicle instrument service processing device provided by the present application;
[0066] Figure 7 A schematic diagram of the structure of the electronic device provided in this application.
[0067] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0068] Here, exemplary embodiments will be described in detail, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application.
[0069] IP (Internet Protocol): refers to the Internet interconnection protocol, which is the network layer protocol in the TCP / IP system.
[0070] TCP / IP (Transmission Control Protocol / Internet Protocol): refers to the TCP / IP protocol. TCP / IP refers to a protocol suite that enables information transmission between multiple different networks.
[0071] As mentioned in the background technology, the instrument panel is an important part of the vehicle, providing the driver with the vehicle's operating status and various parameters as a window for human-vehicle interaction. In the related technology, the business processing code and display code of the instrument application on the vehicle are mixed together, and the code is highly dependent on each other. Once a problem occurs in the code, it will have a significant impact on the normal operation of the instrument application.
[0072] In response to the above technical problems, the inventors of the present application discovered in their research that, from a functional perspective, traditional instrument applications can be seen as consisting of two parts, one part is a functional module for instrument business processing and this part is implemented by business processing code, and the other part is a functional module for outputting instrument information and this part is implemented by display code. In order to reduce the coupling between the business processing code and the display code of the instrument application, each business processing function involved in the instrument application can be extracted and encapsulated into independent services respectively, thereby splitting the traditional instrument application into two parts: an instrument middleware for instrument business processing and an instrument application for outputting instrument information. Furthermore, the instrument middleware can be designed based on a service-oriented architecture (SOA).
[0073] On this basis, the inventor of this application also found that in the traditional instrument project development process, the instrument application is deeply customized for specific vehicle configurations, which makes it difficult to reuse directly in other instrument projects. Different vehicle manufacturers, different instrument vehicle platforms, and differences in vehicle signals will cause the entire instrument application to need to be redeveloped, so there is an urgent need for a universal instrument development tool. The functions provided by the instruments corresponding to different vehicle manufacturers and different instrument vehicle platforms are not much different, and the way of outputting instrument information may be different. Therefore, the instrument middleware can be transformed into a universal instrument development tool, so that instrument developers can develop instruments based on the instrument middleware tool, and realize business processing functions by reusing multiple services in the instrument middleware tool. There is no need to rewrite the code related to the business processing function, which improves development efficiency, and the way to output instrument information can be designed according to the specific vehicle model. Taking into account the differences in vehicle signals, an adaptation function can be added to the instrument middleware tool so that the instrument middleware tool can recognize various vehicle signals and be more versatile.
[0074] Specifically, by splitting the traditional instrument application into two parts, an instrument middleware for instrument business processing and an instrument application for outputting instrument information, and the instrument middleware is designed based on the SOA architecture, and by dividing the business functions involved into multiple independent preset services, these preset services can be independently developed and maintained, reducing dependencies and making them more maintainable; on this basis, in the process of processing instrument business, through the adaptation function of the instrument middleware, the whole vehicle signal from the external system can be converted into a standard instrument internal signal, realizing unified adaptation of data, improving data standardization, and notifying the target service corresponding to the target subject event to which the whole vehicle signal belongs, so that the target service obtains the standard instrument internal signal, and performs business processing based on the standard instrument internal signal to obtain the processing result, by selecting the corresponding preset service according to different processing requirements, the business processing is customized and optimized, and the quality and accuracy of the processing result are improved, and by sending the processing result to the corresponding instrument application and / or external system, the instrument application and / or external system can output the corresponding information based on the processing result. In summary, using the instrument middleware for instrument business processing can improve data standardization, improve the quality and accuracy of the processing result, thereby optimizing the instrument business processing process and improving the overall business operation effect.
[0075] Figure 1 A schematic diagram of an application scenario provided for this application, such as Figure 1 As shown, the application scenario includes an instrument development terminal 1 and a vehicle device 2. Among them, the instrument development terminal 1 is a terminal device used by instrument developers. Exemplarily, the terminal device is a tablet computer, a laptop computer, a computer or other terminal device that can realize instrument development. An instrument middleware tool is installed on the instrument development terminal 1. The instrument middleware tool can be regarded as an instrument development tool. Instrument developers can develop instruments based on the instrument middleware tool to obtain an instrument system. The instrument system includes an instrument middleware and multiple instrument applications. The instrument middleware is obtained by modifying the code and configuring the service of the instrument middleware tool.
[0076] like Figure 1 As shown, the developed instrument system is used to be deployed in the vehicle-mounted device 2 on the vehicle, so that when the vehicle is driving, the vehicle-mounted device 2 uses the instrument system to process instrument services, thereby outputting instrument information on the vehicle, such as displaying the instrument information on the instrument panel or playing the instrument information.
[0077] It should be noted that other business systems are also deployed in the vehicle equipment 2, such as an in-vehicle infotainment system, an automatic driving system, a chassis control system, etc. These multiple business systems can be isolated through virtualization technology without affecting each other.
[0078] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0079] First, the instrument middleware tool in the present application is described with an exemplary embodiment.
[0080] The instrumentation middleware tool (Cluster MiddleWare, CMW) includes an adaptation layer, a data layer, and a service layer.
[0081] The adapter layer includes an intra-domain adapter function module, an extra-domain adapter function module, and a protocol stack function module. The protocol stack function module supports a variety of communication protocols. For example, the communication protocol can be a desktop bus (DBus), a scalable service-oriented middleware protocol based on IP protocol (SOME / IP), a distributed file system (DFS), a flexible data bus (FDBus), a shared memory (ShareMemory), an inter-process communication library (IPCL), or an IP control protocol (IPCP), but is not limited to this. The intra-domain adapter function module (HMI Adapter) is used to communicate with intra-domain applications based on the communication protocol in the protocol stack function module. In-domain applications refer to multiple instrument applications in the instrument system. For example, multiple instrument applications include instrument panel applications (Cluster Human-Machine Interface, Cluster HMI), head-up display applications (Head-Up Display Human-Machine Interface, HUD HMI), prompt sound playback applications (ChimePlayer), acoustic vehicle alerting applications (Acoustic Vehicle Alerting System, AVAS), but are not limited to this. Among them, the out-of-domain adaptation function module (CMW Adapter) is used to communicate with the out-of-domain system across domains based on the communication protocol in the protocol stack function module. Cross-domain communication refers to communication with other systems (otherdomain) outside the instrument system, that is, the instrument domain, such as microcontroller units (MCU), in-vehicle infotainment systems (In-Vehicle Infotainment, IVI), autonomous driving control units (Autonomous Driving Control Unit, ADCU) and other vehicle nodes. Specifically, the out-of-domain adaptation function module is used to convert the vehicle signal received from the out-of-domain system into a standard instrument internal signal, and write the standard instrument internal signal into the data layer.
[0082] It should be noted that the adaptation layer supports multiple commonly used communication protocols on the market, and each communication protocol needs to be obtained separately from the communication operator, which is costly. Generally, the vehicle manufacturer only uses one communication protocol for the instrument project on a certain model. Accordingly, before delivering the instrument middleware tool to the vehicle manufacturer, the provider of the instrument middleware tool needs to set the communication protocol supported by the adaptation layer of the instrument middleware tool to the communication protocol required by the vehicle manufacturer's instrument project. In this way, for different vehicle manufacturers or different instrument projects, the provider of the instrument middleware tool can set the communication protocol supported by the adaptation layer according to the specific needs of the instrument development project, thereby achieving flexible adaptation.
[0083] The data (DataFactory) layer is used for data storage and management as well as notification distribution. The data refers to the standard instrument internal signal converted by the out-of-domain adaptation function module. Notification distribution refers to the preset service corresponding to the subject event to which the vehicle signal belongs.
[0084] The service layer is used to implement the specific functional logic related to the instrument. Specifically, the service layer includes a basic service function module (Base Service), a service management function module (Service Management) and an instrument logic service function module (Logic Service). Accordingly, the instrument system is used to use the basic service function module to process the basic business of the instrument system. The basic service function module includes multiple basic services of instruments, such as vehicle configuration service (CarconfigService), data synchronization service (InfoSYNCService), power management service (PowerManagerService), etc., but not limited to this. The instrument system is also used to use the instrument logic service function module to process the instrument logic business of the instrument system. The instrument logic service function module includes multiple services, for example, these multiple services include vehicle speed information service (SpeedService), vehicle computer information service (TripComputerService), mileage information service (OdoService), door and window information service (DoorWindowService), warning light information service (TTService), automatic driving information service (AdasService), etc., but not limited to this. Each service is used to implement a specific business function, for example, the speed information service is used to implement business functions such as actual speed calculation, displayed speed calculation, speeding warning, and speed unit switching. The instrument system is also used to manage multiple preset services using a service management function module. The service management function module includes multiple management services, such as work queue management (WorkQueue), service life cycle management (ServiceLifeManager), health monitoring management (HealthMonitor), service configuration management (ServiceConfig), etc., but not limited to this.
[0085] It should be noted that the services provided by the service layer can be developed and maintained according to actual development needs, and also support service expansion.
[0086] In addition, the instrument middleware tool also provides a set of service application programming interfaces (Application Programming Interface, API) to facilitate in-domain applications or out-domain systems to obtain data.
[0087] In summary, the instrument middleware tool in this application has the following advantages:
[0088] 1. In view of the differences in vehicle models, multiple instrument logic services are provided to facilitate instrument developers to flexibly configure different vehicle models according to actual development needs.
[0089] 2. In view of the differences between software and hardware platforms, the instrument middleware tool encapsulates the calls of different system functions and abstracts the differences in hardware device parameters. The relevant codes of the instrument middleware tool are written in C language (a computer programming language), so it can achieve flexible switching between different software platforms (such as QNX, Linux, etc.) and rapid adaptation to hardware interface differences.
[0090] 3. In view of the differences in communication methods, the instrument middleware tool encapsulates a variety of common communication components, which can be flexibly adapted according to actual development needs during delivery.
[0091] 4. Provide a set of service API interfaces to reduce the inconvenience of re-adapting interfaces for different instrument projects.
[0092] 5. In view of the differences in vehicle signals, the adaptation layer converts different vehicle signals into standard instrument internal signals to achieve rapid adaptation.
[0093] It can be seen that the design of the instrument middleware tool considers the reliability, rationality, reusability, scalability, and security of the overall solution from the perspective of the platform, and provides the vehicle information to the in-domain applications and out-of-domain systems in a more friendly service interface, which can save the development workload of instrument developers and improve development efficiency. Based on the differences in vehicle models, software and hardware platforms, and communication methods, the adaptation layer, data layer, and service layer are abstracted, and the API interface of each service is standardized to maximize the reuse of business codes.
[0094] In one application scenario, instrument developers can develop instruments based on the above instrument middleware tools. Figure 2 A flow chart of a vehicle instrument development method provided in this application, such as Figure 2 As shown, the execution subject of the vehicle instrument development method is the vehicle instrument development device, and the vehicle instrument development device is integrated in the instrument development terminal. The method includes:
[0095] S101. Obtain a first instrument middleware.
[0096] The first instrument middleware is an instrument middleware tool. For the related description of the instrument middleware tool, please refer to the above embodiment and will not be repeated here.
[0097] In actual applications, the provider of the instrument middleware tool packages and delivers the instrument middleware tool to the instrument developer, so that the instrument developer can deploy the instrument middleware tool on the instrument development terminal. When there is a demand for instrument development, the instrument middleware tool is used to execute the vehicle instrument development method provided in this embodiment.
[0098] S102: modify the adaptation layer code in the first instrument middleware based on the user operation, so that the adaptation layer code can recognize the vehicle signal sent by the external system and convert it into a standard instrument internal signal.
[0099] In actual applications, vehicle manufacturers have their own definition specifications for vehicle signals, and the definition specifications of different vehicle manufacturers are different. Taking vehicle speed as an example, vehicle manufacturer 1 defines the vehicle speed signal as a, while vehicle manufacturer 2 defines the vehicle speed signal as s. Based on this, the first instrument middleware, as a general instrument development tool, also provides a set of definition specifications for standard instrument internal signals, which include signal definition, type, protocol, data format and other related definition information. In addition, the internal processing logic of the first instrument middleware is executed based on the standard instrument internal signal. Therefore, for the current instrument project, the instrument developer needs to associate the vehicle signal involved in the instrument project with the standard instrument internal signal in the first instrument middleware, so that the first instrument middleware can identify the vehicle signal and convert the vehicle signal into a standard instrument internal signal.
[0100] The instrument development terminal has the function of displaying the definition specification of the standard instrument internal signal provided by the first instrument middleware. The instrument developer triggers the instrument development terminal to display the definition specification, so as to understand how the signal is defined inside the first instrument middleware according to the definition specification. Exemplarily, the definition specification exists in the form of a signal list, which lists the relevant definition information of multiple standard instrument internal signals. On this basis, the instrument developer can modify the adaptation layer code in the first instrument middleware through the instrument development terminal according to the actual instrument development requirements and the definition specification, so that the adaptation layer code can recognize the vehicle signal sent by the out-of-domain system and convert it into a standard instrument internal signal.
[0101] S103: Based on the user operation, multiple preset services of the service layer in the first meter middleware are configured so that the configured services meet the meter business requirements.
[0102] Among them, the service layer provides multiple preset services, but there may be differences between the business functions that can be realized by these multiple preset services and the business functions required by the current instrument project. Therefore, the instrument developer can also configure the multiple preset services to make the configured services meet the instrument business requirements. Among them, these multiple preset services are specifically referred to the multiple services included in the above-mentioned instrument logic service function module, which will not be repeated here.
[0103] S104, integrating the modified and configured second instrument middleware into the instrument system, and deploying multiple instrument applications in the instrument system; the instrument system is used for instrument business processing of the vehicle.
[0104] Among them, the second instrument middleware is an instrument middleware that meets the instrument business requirements by modifying and configuring the first instrument middleware. It is integrated into the instrument system through the second instrument middleware, and multiple instrument applications are deployed in the instrument system, so that the instrument system can be deployed to the vehicle equipment later, so that the vehicle equipment can use the instrument system to perform instrument business processing during vehicle driving, thereby outputting instrument information on the vehicle.
[0105] This embodiment provides a vehicle-based instrument development solution. By acquiring the first instrument middleware and modifying and configuring it, it can quickly adapt to different vehicle signals and instrument business requirements, reducing the time and cost of development from scratch; the modification of the adaptation layer code enables it to identify and convert vehicle signals sent by the out-of-domain system, which means that the first instrument middleware can adapt to the signal definition specifications of different vehicle manufacturers, improving compatibility and flexibility; service configuration allows developers to make adjustments according to specific instrument business requirements, increasing scalability; by integrating the modified and configured second instrument middleware into the instrument system and deploying multiple instrument applications, modular design can be achieved, so that the maintenance and upgrade of the instrument system becomes more convenient and reduces the impact on the entire instrument system; since the instrument system is developed based on the middleware, future maintenance and upgrades can be achieved by updating and configuring the middleware without large-scale changes to the entire instrument system. In summary, the instrument development solution can quickly and flexibly adapt to different instrument business requirements by modifying and configuring the first instrument middleware, improving development efficiency, system stability and reliability, while reducing development costs and facilitating future maintenance and upgrades.
[0106] In an optional embodiment, the signal in the code is represented in the form of a variable, for example, the vehicle signal is represented in the form of a vehicle signal variable. Accordingly, step S102 is specifically implemented as follows: based on the user operation, in the adaptation layer code, after the signal receiving code for receiving the vehicle signal, an assignment code for assigning the value of the vehicle signal variable to a standard instrument internal signal variable representing the same business meaning as the vehicle signal variable is added, so that the adaptation layer code can recognize the vehicle signal sent by the external system and convert it into a standard instrument internal signal.
[0107] Among them, the adaptation layer code includes a signal receiving code. After the signal receiving code, it should also include a signal conversion code to convert the vehicle signal into a standard instrument internal signal. The signal conversion code is also an assignment code. The logic of the assignment code is to assign the value of the vehicle signal variable to the standard instrument internal signal variable that represents the same business meaning as the vehicle signal variable. When writing the assignment code, the instrument developer queries the standard instrument internal signal variable that represents the business meaning from the definition specification of the standard instrument internal signal provided by the first instrument middleware.
[0108] For example, the business meaning represented by the vehicle signal variable is vehicle speed, and the vehicle signal variable is s, the variable value is 100, and the standard instrument internal signal variable representing the same business meaning as the vehicle signal variable is v.
[0109] By adding assignment codes at corresponding positions in the adaptation layer code, the compatibility and flexibility of the system are improved, and the development and maintenance process is simplified.
[0110] It should be noted that after step S102, the method provided in this embodiment also includes: modifying the adaptation layer code in the first instrument middleware based on user operations so that the adaptation layer code can convert the internal signal of the standard instrument into a whole vehicle signal. The internal signal of the standard instrument is a signal contained in the processing result obtained after the business processing by the corresponding preset service. Since the processing result needs to be fed back to the in-domain application and / or the out-domain system, it is also necessary to convert the internal signal of the standard instrument contained in the processing result into a whole vehicle signal so that the in-domain application and the out-domain system can recognize it. Similarly, the signal in the code is represented in the form of a variable. This step is specifically implemented as follows: based on the user operation, an assignment code is added to the position before the code for sending the processing result in the adaptation layer code; the assignment code is used to assign the value of the internal signal variable of the standard instrument to the whole vehicle signal variable representing the same business meaning. Please refer to the above content for the specific implementation of this step, which will not be repeated here.
[0111] In an optional embodiment, step S103 is specifically implemented as follows: for any preset service among multiple preset services, whether the preset service is enabled is configured based on user operations; in the case that there are multiple preset business processing policies for any enabled preset service, the selected preset business processing policy is determined as the business processing policy corresponding to the preset service based on the user operation, so that the preset service performs business processing through the corresponding business processing policy.
[0112] Among them, the first instrument middleware also provides business function description information corresponding to each preset service. The business function description information corresponding to the preset service is used to explain the business function implemented by the preset service, so that the instrument developer can understand the business function implemented by each preset service. Therefore, the instrument developer can determine whether to enable a preset service based on the specific instrument business needs. For any preset service, if the preset service is configured to be enabled, after the instrument system is deployed to the vehicle equipment, the instrument system can use the preset service in the instrument middleware to implement the corresponding business function when processing the instrument business. Conversely, if the preset function is configured to be disabled, the instrument system cannot use the preset service in the instrument middleware to implement the corresponding business function.
[0113] In one application scenario, each preset service in the first instrument middleware has at least one preset business processing strategy corresponding thereto, and the preset business processing strategy is used to implement the corresponding business function. For example, the vehicle speed calculation service has three preset business processing strategies, and the preset business processing strategy is used to calculate the vehicle speed. However, for the current instrument project, only one business processing strategy is required, so the instrument developer can select a preset business processing strategy from at least one preset business processing strategy corresponding to the preset service, and determine the selected preset business processing strategy as the business processing strategy corresponding to the preset service, so that when the instrument system uses the preset service in the instrument middleware to implement the corresponding business function, the business processing strategy is used for specific implementation.
[0114] In this embodiment, the instrument developer can flexibly enable or disable preset services according to the instrument business requirements. This flexibility allows the instrument developer to adjust the use of preset services according to actual conditions, and among the enabled preset services, it is also possible to select preset business processing strategies that are suitable for the current instrument business requirements. This customizability enables the system to adapt to changing business environments and improves the adaptability and flexibility of the system.
[0115] After the instrument system is developed, it can be deployed to the vehicle's onboard equipment, so that during the vehicle's driving, the instrument system can be used to process instrument services and output instrument information, thereby assisting driving. Figure 3 A flow chart of a vehicle instrument service processing method provided in this application, such as Figure 3 As shown, the execution subject of the vehicle instrument service processing method is the vehicle instrument service processing device, and the vehicle instrument service processing device is integrated in the vehicle equipment. The method is applied to the instrument system on the vehicle, and the instrument system includes an instrument middleware and multiple instrument applications. The instrument middleware is also Figure 2 The second instrument middleware in the embodiment shown. The method includes:
[0116] S201. Receive a vehicle signal and a target subject event to which the vehicle signal belongs, which are sent by an out-of-domain system; the out-of-domain system is a system on the vehicle other than the instrument system.
[0117] Exemplarily, the vehicle signal is a signal such as vehicle speed, engine speed, battery level, status of warning lights, status of seat belts, etc., but is not limited thereto.
[0118] The target topic event is the topic event to which the vehicle signal belongs. The message transmission mechanism in this application is implemented based on the publish / subscribe model. Each message has a specific topic. In this application, the message refers to the vehicle signal sent by the external system.
[0119] Among them, the out-of-domain adaptation function module in the instrument middleware obtains the vehicle signal sent by the out-of-domain system and the target subject event to which the vehicle signal belongs through a specific communication protocol. Exemplarily, there are two ways to obtain the vehicle signal of the out-of-domain system and the target subject event to which the vehicle signal belongs: one is timed acquisition, such as obtaining the vehicle signal of the out-of-domain system and the target subject event to which the vehicle signal belongs at every preset time interval; the other is event-triggered acquisition, such as responding to the notification message of the out-of-domain system, obtaining the vehicle signal of the out-of-domain system and the target subject event to which the vehicle signal belongs. Specifically, the out-of-domain system provides an API interface to the outside, and the out-of-domain adaptation function module obtains the vehicle signal and the target subject event to which the vehicle signal belongs by calling the API interface.
[0120] S202, converting the vehicle signal into a standard instrument internal signal.
[0121] Among them, the out-of-domain adaptation function module in the instrument middleware can also convert the vehicle signal into a standard instrument internal signal, so as to execute subsequent business logic according to the standard instrument internal signal.
[0122] S203: Notify a target service corresponding to the target subject event among multiple preset services.
[0123] In the present application, each preset service subscribes to one or more topics, which can be set according to specific instrument business requirements, and this embodiment does not limit this. Among them, the target service is a service that subscribes to the target topic event among multiple preset services.
[0124] S204: Use the target service to acquire the internal signal of the standard instrument, and use the target service to process the internal signal of the standard instrument to obtain a processing result.
[0125] In this embodiment, after obtaining the internal signal of the standard instrument, the out-of-domain adaptation function module stores the internal signal of the standard instrument in a memory space, and the target service reads the internal signal of the standard instrument from the memory space.
[0126] Exemplarily, the target service is a vehicle speed calculation service, and the processing results obtained by using the vehicle speed calculation service for business processing include data such as actual vehicle speed, displayed vehicle speed, and speeding warning information.
[0127] S205. Send the processing results to the corresponding instrument application and / or the external system to output corresponding information based on the processing results.
[0128] The instrument application is used to obtain the processing result, and then the instrument application is used to output corresponding information based on the processing result. For example, if the processing result includes displaying the vehicle speed, the displayed vehicle speed can be displayed on the instrument panel so that the driver can know the current vehicle speed in time. For another example, if the processing result includes speeding warning information, the speeding warning information can also be played through the audio player on the vehicle.
[0129] Among them, an off-domain system is used to obtain processing results, and then the off-domain system is used to output corresponding information based on the processing results. For example, the processing results include displaying the vehicle speed. If the off-domain system is an in-vehicle infotainment system, the displayed vehicle speed can also be displayed on the central control screen.
[0130] This embodiment provides a vehicle-based instrument business processing solution. In the process of processing instrument business, through the adaptation function of the instrument middleware, the whole vehicle signal from the out-of-domain system can be converted into a standard instrument internal signal, so as to achieve unified data adaptation and improve data standardization. It can also notify the target service corresponding to the target subject event to which the whole vehicle signal belongs, so that the target service can obtain the standard instrument internal signal, and perform business processing based on the standard instrument internal signal to obtain the processing result. By selecting corresponding preset services according to different processing requirements, the business processing can be customized and optimized, and the quality and accuracy of the processing results can be improved. By sending the processing results to the corresponding instrument application and / or out-of-domain system, the instrument application and / or out-of-domain system can output corresponding information based on the processing results. In summary, using the instrument middleware for instrument business processing can improve data standardization, improve the quality and accuracy of processing results, thereby optimizing the instrument business processing flow and improving the overall business operation effect.
[0131] In an optional embodiment, the signal in the code is represented in the form of a variable, for example, the vehicle signal is represented in the form of a vehicle signal variable; accordingly, step S202 is specifically implemented as: assigning the value of the vehicle signal variable to a standard instrument internal signal variable that represents the same business meaning as the vehicle signal variable.
[0132] Among them, in the adaptation layer code, after the signal receiving code is the assignment code, the logic of which is to assign the value of the vehicle signal variable to the standard instrument internal signal variable representing the same business meaning as the vehicle signal variable.
[0133] In an optional embodiment, the memory space is divided in the form of subject events; after step S202, the method provided by this embodiment further includes: writing the internal signal of the standard instrument into the memory space corresponding to the target subject event in the shared memory.
[0134] The data layer of the instrument middleware uses shared memory to store the internal signals of the standard instrument, and the corresponding process or thread of the adaptation layer writes the internal signals of the standard instrument into the shared memory.
[0135] Shared memory is an efficient data sharing mechanism that allows multiple processes or threads to quickly access and exchange data, thereby reducing data transmission delays and improving system response speed. Shared memory can provide a consistent data access mechanism to ensure that the data accessed by multiple processes or threads is consistent. By writing the internal signals of standard instruments into shared memory, it can ensure that the signals obtained by the target service are the latest and accurate, thereby improving data reliability and system stability.
[0136] This embodiment also combines the topic mechanism to realize data writing and reading. Among them, the shared memory includes memory spaces corresponding to multiple topics respectively; among them, multiple topics can be set according to specific instrument business requirements, which is not limited in this embodiment. By classifying the internal signals of the standard instrument, it is convenient to write and read the signals.
[0137] On the basis of the above optional embodiments, optionally, after writing the internal signal of the standard instrument into the shared memory, it also includes: in response to the data update stored in the memory space corresponding to the target subject event in the shared memory, sending a notification message to the target service subscribing to the target subject event; accordingly, using the target service to obtain the internal signal of the standard instrument, which is specifically implemented as: using the target service to read the internal signal of the standard instrument from the memory space corresponding to the target subject event in the shared memory.
[0138] By adopting the publish-subscribe method to realize the writing and reading of the internal signals of the standard instrument, the internal signals of the standard instrument can be read by the target service that subscribes to the target subject event to which it belongs, while other preset services that have not subscribed to the target subject event do not need to read the internal signals of the standard instrument, saving the number of data interactions and saving resources.
[0139] In an optional embodiment, based on the internal signal of the standard instrument, the target service is used to perform business processing to obtain the processing result, which is specifically implemented as follows: the business processing strategy in the target service is used to process the internal signal of the standard instrument to obtain the processing result. The determination method of the business processing strategy is shown in Figure 2 The illustrated embodiments will not be described in detail here.
[0140] In an optional embodiment, the processing results are sent to the corresponding instrument application and / or an out-of-domain system, including: using the in-domain application to call the service interface corresponding to the target service to obtain the processing results; and / or, using the out-of-domain system to call the service interface corresponding to the target service to obtain the processing results.
[0141] Among them, the service interface refers to the service API interface. When the in-domain application implements the function of outputting instrument information, it needs to obtain the corresponding processing results from the instrument middleware. When the instrument is developed, the type of processing results that the in-domain application needs to obtain and the service interface for obtaining the processing results of this type have been configured in advance. In one application scenario, the in-domain application obtains the processing results from the corresponding service interface at a regular interval; in another application scenario, after the target service obtains the processing results, it calls the interface of the in-domain adaptation function module to notify the in-domain adaptation function module, and the in-domain adaptation function module calls the interface of the in-domain application to notify the in-domain application, and the in-domain application obtains the processing results from the service interface of the target service. Similarly, when the instrument is developed, the type of processing results that the out-of-domain system needs to obtain and the service interface for obtaining processing results of this type have been configured in advance. In one application scenario, the out-of-domain system obtains the processing results from the corresponding service interface at a regular interval; in another application scenario, after the target service obtains the processing results, it calls the interface of the out-of-domain adaptation function module to notify the out-of-domain adaptation function module, and the out-of-domain adaptation function module calls the interface of the out-of-domain system to notify the out-of-domain system, and the out-of-domain system obtains the processing results from the service interface of the target service.
[0142] like Figure 4 As shown in the figure, CMW is the instrument middleware, which includes the Adapter layer, DataFactory layer, Service layer and standard service API interface. The Adapter layer includes HMI Adapter, CMW Adapter and a protocol stack that supports multiple communication protocols (such as DBus, SOME / IP, DFS, ShareMemory). The Service layer includes three functional modules: Base Service, ServiceManagement and Logic Service. In an instrument business processing process:
[0143] 1. CMW Adapter obtains vehicle signals from other domain systems such as MCU, IVI or ADCU, and converts the vehicle signals into standard instrument internal signals;
[0144] 2. CMW Adapter writes the internal signal of the standard instrument to the DataFactory layer;
[0145] 3. The DataFactory layer notifies the corresponding service in the Service layer (such as basic service or instrument logic service), and the corresponding service obtains the internal signal of the standard instrument;
[0146] Among them, this service is a service for subscribing to the subject events of the vehicle signal, which can be both a basic service and an instrument logic service.
[0147] 4. The corresponding service performs business processing based on the internal signal of the standard instrument, obtains the processing result, and calls the interface of HMIAdapter and / or CMW Adapter.
[0148] For ease of representation, Figure 4 Take calling HMI Adapter and CMW Adapter as an example.
[0149] 5. HMI Adapter communicates with applications in the domain (such as Cluster HMI, HUD HMI, Chime Player, AVAS);
[0150] 6. The application in the domain calls the service API interface to obtain the processing result;
[0151] 7. CMW Adapter communicates with the external system, and the external system calls the service API interface to obtain the processing results ( Figure 4 The operation of calling the service API interface by the out-of-domain system is not shown).
[0152] Figure 5 The schematic diagram of the structure of the vehicle instrument development device 30 provided in this application is as follows: Figure 5 As shown, the device 30 is arranged in the instrument development terminal, and the device 30 includes:
[0153] An acquisition module 301 is used to acquire a first instrument middleware;
[0154] A modification module 302, for modifying the adaptation layer code in the first meter middleware based on user operations, so that the adaptation layer code can identify the vehicle signal sent by the external system and convert it into a standard meter internal signal;
[0155] A configuration module 303, configured to configure a plurality of preset services of the service layer in the first meter middleware based on user operations, so that the configured services meet the meter business requirements;
[0156] The integration module 304 is used to integrate the modified and configured second instrument middleware into the instrument system and deploy multiple instrument applications in the instrument system; the instrument system is used for vehicle instrument business processing.
[0157] In an optional embodiment, the signal is represented in the form of a variable; the modification module 302 is specifically used to:
[0158] Based on user operations, an assignment code for assigning the value of the vehicle signal variable to the standard instrument internal signal variable representing the same business meaning as the vehicle signal variable is added after the signal receiving code for receiving the vehicle signal in the adaptation layer code, so that the adaptation layer code can recognize the vehicle signal sent by the external system and convert it into a standard instrument internal signal.
[0159] In an optional embodiment, the configuration module 303 is specifically configured to:
[0160] For any preset service among the multiple preset services, configuring whether the preset service is enabled based on a user operation;
[0161] When there are multiple preset business processing policies for any enabled preset service, the selected preset business processing policy is determined as the business processing policy corresponding to the preset service based on the user operation, so that the preset service performs business processing through the corresponding business processing policy.
[0162] The vehicle instrument development device 30 provided in this embodiment can execute the method provided in the above method embodiment, and its implementation principle and technical effect are similar, which will not be described in detail in this embodiment.
[0163] Figure 6 The schematic diagram of the structure of the vehicle instrument service processing device 40 provided in this application is as follows: Figure 6 As shown, the device 40 is arranged in a vehicle machine device, an instrument system is deployed on the vehicle machine device, the instrument system includes an instrument middleware and multiple instrument applications, the instrument middleware includes multiple preset services, and the device 40 includes:
[0164] The receiving module 401 is used to receive the vehicle signal and the target subject event to which the vehicle signal belongs, which are sent by the external system; the external system is the system on the vehicle other than the instrument system;
[0165] The conversion module 402 is used to convert the vehicle signal into a standard instrument internal signal;
[0166] Notification module 403, used to notify a target service corresponding to a target subject event among a plurality of preset services;
[0167] The processing module 404 is used to obtain the internal signal of the standard instrument by using the target service, and perform business processing by using the target service based on the internal signal of the standard instrument to obtain the processing result;
[0168] The sending module 405 is used to send the processing results to the corresponding instrument application and / or the external system to output corresponding information based on the processing results.
[0169] In an optional embodiment, the signal is represented in the form of a variable; the conversion module 402 is specifically used to: assign the value of the vehicle signal variable to the standard instrument internal signal variable representing the same business meaning as the vehicle signal variable.
[0170] In an optional embodiment, the memory space is divided in the form of subject events; the conversion module 402 is also used to write the standard instrument internal signal into the memory space corresponding to the target subject event in the shared memory after converting the whole vehicle signal into the standard instrument internal signal.
[0171] In an optional embodiment, the notification module 403 is specifically used to: send a notification message to a target service that subscribes to a target topic event in response to a data update stored in a memory space corresponding to a target topic event in a shared memory; the processing module 404, when using a target service to obtain an internal signal of a standard instrument, is specifically used to: use the target service to read the internal signal of the standard instrument from the memory space corresponding to the target topic event in the shared memory.
[0172] In an optional embodiment, the processing module 404, when using the target service to perform business processing based on the internal signal of the standard instrument to obtain the processing result, is specifically used to: use the business processing strategy in the target service to process the internal signal of the standard instrument to obtain the processing result.
[0173] In an optional embodiment, the sending module 405 is specifically used to use an in-domain application to call a service interface corresponding to the target service to obtain a processing result; and / or use an out-of-domain system to call a service interface corresponding to the target service to obtain a processing result.
[0174] In an optional embodiment, the meter middleware includes an adaptation layer, and the adaptation layer includes an intra-domain adaptation function module, an extra-domain adaptation function module and a protocol stack function module; and further includes:
[0175] The intra-domain communication module is used to communicate with the intra-domain application based on the communication protocol in the protocol stack function module by using the intra-domain adaptation function module;
[0176] The extra-domain communication module is used to communicate with the extra-domain system based on the communication protocol in the protocol stack function module by using the extra-domain adaptation function module.
[0177] In an optional embodiment, the instrument middleware includes a service layer, which includes a basic service function module, an instrument logic service function module, and a service management function module; the processing module 404 is further used to:
[0178] Use basic service function modules to handle the basic business of the instrument system;
[0179] The instrument logic service function module is used to process the instrument logic business of the instrument system;
[0180] The service management function module is used to manage multiple preset services.
[0181] The vehicle instrument service processing device 40 provided in this embodiment can execute the method provided in the above method embodiment, and its implementation principle and technical effect are similar, which will not be described in detail in this embodiment.
[0182] Figure 7 This is a schematic diagram of the structure of the electronic device provided in this application. Figure 7 As shown, the electronic device 50 provided in this embodiment includes: a processor 501 and a memory 502 communicatively connected to the processor 501. The processor 501 and the memory 502 are connected via a bus.
[0183] In the specific implementation process, the processor 501 executes the computer execution instructions stored in the memory 502, so that the processor 501 executes the above method. For example, when the electronic device 50 is provided as an instrument development terminal, the processor 501 is used to execute Figure 2 In the method of the embodiment shown; illustratively, when the electronic device 50 is provided as a vehicle device, the processor 501 is used to execute Figure 3 The method in the illustrated embodiment.
[0184] The specific implementation process of the processor 501 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.
[0185] The components, their connections and relationships, and their functions shown herein are only examples and are not intended to limit the implementation of the present application described and / or required herein. The various components are interconnected using different buses and can be installed on a common motherboard or in other ways as needed.
[0186] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.
[0187] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.
[0188] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.
[0189] It should be further noted that, although the various steps in the flowchart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
[0190] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.
[0191] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.
[0192] If the integrated unit / module is implemented in the form of hardware, the hardware may be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a digital signal processor (DSP), a programmable logic device (PLD), a field programmable gate array (FPGA), a controller, a microcontroller, a microprocessor or other electronic components. Unless otherwise specified, the memory may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as a USB flash drive, random-access memory (RAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), enhanced dynamic random-access memory (EDRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), high-bandwidth memory (HBM) or hybrid memory cube (HMC) and other media that can store program code.
[0193] In the above embodiments, the description of each embodiment has its own emphasis. For the part not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not 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.
[0194] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the claims.
[0195] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.
Claims
1. A vehicle instrument service processing method, It is characterized in that An instrument system applied to a vehicle, the instrument system comprising an instrument middleware and a plurality of instrument applications, the instrument middleware comprising a plurality of preset services, the method comprising: Receiving a vehicle signal and a target subject event to which the vehicle signal belongs, sent by an out-of-domain system; the out-of-domain system is a system on the vehicle other than the instrument system; Converting the vehicle signal into a standard instrument internal signal; Notifying a target service corresponding to the target subject event among the plurality of preset services; The target service is used to obtain the internal signal of the standard instrument, and based on the internal signal of the standard instrument, the target service is used to perform business processing to obtain a processing result; The processing result is sent to a corresponding instrument application and / or an external system to output corresponding information based on the processing result.
2. The method according to claim 1, It is characterized in that The signal is represented in the form of a variable; the whole vehicle signal is converted into a standard instrument internal signal, including: Assign the value of the vehicle signal variable to the standard instrument internal signal variable that represents the same business meaning as the vehicle signal variable.
3. The method according to claim 1, It is characterized in that The memory space is divided in the form of subject events; after converting the vehicle signal into a standard instrument internal signal, it also includes: The standard instrument internal signal is written into the memory space corresponding to the target subject event in the shared memory.
4. The method according to claim 3, It is characterized in that The notifying a target service corresponding to the target subject event among the plurality of preset services includes: In response to data update stored in the memory space corresponding to the target subject event in the shared memory, sending a notification message to a target service subscribed to the target subject event; The adopting the target service to obtain the internal signal of the standard instrument includes: The target service is used to read the internal signal of the standard instrument from the memory space corresponding to the target subject event in the shared memory.
5. The method according to claim 1, It is characterized in that The process of performing business processing based on the internal signal of the standard instrument using the target service to obtain a processing result includes: The business processing strategy in the target service is adopted to process the internal signal of the standard instrument to obtain a processing result.
6. The method according to claim 1, It is characterized in that The sending of the processing result to the corresponding instrument application and / or the external system includes: Using an in-domain application to call a service interface corresponding to the target service to obtain the processing result; and / or, The out-of-domain system is used to call the service interface corresponding to the target service to obtain the processing result.
7. The method according to claim 1, It is characterized in that The instrument middleware includes an adaptation layer, and the adaptation layer includes an intra-domain adaptation function module, an extra-domain adaptation function module and a protocol stack function module; and further includes: Adopting the intra-domain adaptation function module to communicate with the intra-domain application based on the communication protocol in the protocol stack function module; The out-of-domain adaptation function module is used to communicate with the out-of-domain system based on the communication protocol in the protocol stack function module.
8. The method according to claim 1 or 7, It is characterized in that The instrument middleware includes a service layer, which includes a basic service function module, an instrument logic service function module and a service management function module; and further includes: Using the basic service function module to process the basic business of the instrument system; The instrument logic service function module is used to process the instrument logic business of the instrument system; The service management function module is used to manage the multiple preset services.
9. A vehicle instrument development method, It is characterized in that The method is applied to an instrument development terminal, and the method comprises: Get the first instrument middleware; Modifying the adaptation layer code in the first instrument middleware based on user operations so that the adaptation layer code can identify the vehicle signal sent by the external system and convert it into a standard instrument internal signal; Based on user operations, multiple preset services of the service layer in the first meter middleware are configured so that the configured services meet the meter business requirements; The modified and configured second instrument middleware is integrated into the instrument system, and a plurality of instrument applications are deployed in the instrument system; the instrument system is used for instrument business processing of the vehicle.
10. The method according to claim 9, It is characterized in that The signal is represented in the form of a variable; the adaptation layer code in the first instrument middleware is modified based on the user operation so that the adaptation layer code can identify the vehicle signal sent by the external system and convert it into a standard instrument internal signal, including: Based on user operations, an assignment code for assigning the value of the vehicle signal variable to the standard instrument internal signal variable representing the same business meaning as the vehicle signal variable is added after the signal receiving code for receiving the vehicle signal in the adaptation layer code, so that the adaptation layer code can recognize the vehicle signal sent by the external system and convert it into a standard instrument internal signal.
11. The method according to claim 9, It is characterized in that The configuring of the plurality of preset services of the service layer in the first meter middleware based on the user operation so that the configured services meet the meter business requirements includes: For any preset service among the plurality of preset services, configuring whether the preset service is enabled based on a user operation; When there are multiple preset business processing policies for any enabled preset service, the selected preset business processing policy is determined as the business processing policy corresponding to the preset service based on the user operation, so that the preset service performs business processing through the corresponding business processing policy.
12. A vehicle instrument service processing device, It is characterized in that The device is provided in a vehicle machine device, wherein an instrument system is deployed on the vehicle machine device, wherein the instrument system includes an instrument middleware and a plurality of instrument applications, wherein the instrument middleware includes a plurality of preset services, and wherein the device includes: A receiving module, used for receiving a vehicle signal sent by an out-of-domain system and a target subject event to which the vehicle signal belongs; the out-of-domain system is a system on the vehicle other than the instrument system; A conversion module, used for converting the vehicle signal into a standard instrument internal signal; A notification module, used for notifying a target service corresponding to the target subject event among the plurality of preset services; A processing module, used to obtain the internal signal of the standard instrument by using the target service, and based on the internal signal of the standard instrument, use the target service to perform business processing to obtain a processing result; The sending module is used to send the processing result to the corresponding instrument application and / or the external system to output corresponding information based on the processing result.
13. A vehicle instrument development device, It is characterized in that The device is arranged in an instrument development terminal, and the device comprises: An acquisition module, used for acquiring the first instrument middleware; A modification module, used to modify the adaptation layer code in the first instrument middleware based on user operations, so that the adaptation layer code can recognize the vehicle signal sent by the external system and convert it into a standard instrument internal signal; A configuration module, configured to configure a plurality of preset services of the service layer in the first meter middleware based on user operations, so that the configured services meet the meter business requirements; The integration module is used to integrate the modified and configured second instrument middleware into the instrument system and deploy multiple instrument applications in the instrument system; the instrument system is used for vehicle instrument business processing.
14. An electronic device, It is characterized in that include: A processor and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor executes the method according to any one of claims 1 to 8 or the method according to any one of claims 9 to 11.
15. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method according to any one of claims 1 to 8 or the method according to any one of claims 9 to 11.
16. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 8 or the method according to any one of claims 9 to 11 is implemented.
