Method and apparatus for processing semantic data, middleware, storage medium, and product

Abstract

A semantic data processing method and apparatus, and middleware, a storage medium, and a product. The method comprises: receiving semantic data issued by a sender (S101); parsing the semantic data on the basis of a semantic protocol of the sender, identifying target application software corresponding to the parsed semantic data, and converting the parsed semantic data to generate a control instruction executable by the target application software (S102); and sending the control instruction to the target application software, wherein the target application software executes a target operation on the basis of the control instruction (S103).

Description

Semantic data processing methods, devices, middleware, storage media and products

[0001] This application claims priority to Chinese Patent Application No. 202411509098.3, filed on October 28, 2024, entitled "Method, Apparatus, Middleware, Storage Medium and Product for Processing Semantic Data", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of vehicle technology, and in particular to a method, apparatus, middleware, storage medium and product for processing semantic data. Background Technology

[0003] With the rapid development of hardware and software technologies in the field of intelligent vehicle cockpits, modern intelligent vehicles are able to support increasingly complex human-machine interaction scenarios. Voice control, as a key technology, can now cover the entire control range of the intelligent cockpit. However, the different sensing hardware devices and control software products within the intelligent cockpit are sourced from different suppliers, resulting in different implementation technologies. The semantic data generated by the voice content also adheres to their respective semantic protocols, making it impossible to achieve standardization.

[0004] Therefore, whenever voice control functionality needs to be added or improved, it is necessary to coordinate with technical personnel from various relevant suppliers to interface with the technical protocols and to perform customized development for different semantic protocols. This not only increases the initial product development costs, but also requires a significant investment of human and material resources to ensure normal operation during the later maintenance phase. Summary of the Invention

[0005] This application provides a semantic data processing method, apparatus, middleware, storage medium, and product to address the problems of high development costs and low efficiency caused by semantic data generated by different sensing end hardware devices and control end software products following their respective semantic protocols and requiring extensive technical protocol integration during voice development.

[0006] One embodiment of this application provides a method for processing semantic data. The method is applied to middleware, which is a background service process, and includes the following steps: receiving semantic data sent by a sender; parsing the semantic data according to the sender's semantic protocol and identifying the target application software corresponding to the parsed semantic data; converting the parsed semantic data to generate control instructions executable by the target application software; and sending the control instructions to the target application software, wherein the target application software performs a target operation according to the control instructions.

[0007] Optionally, the parsed semantic data is transformed to generate control instructions executable by the target application software, including: obtaining the target communication protocol; and transforming the parsed semantic data based on the target communication protocol to generate control instructions executable by the target application software.

[0008] Optionally, before sending the control commands to the target application software, the method further includes: encapsulating the control commands into target format data using the communication protocol of the target application software.

[0009] Optionally, before converting the parsed semantic data to generate control instructions executable by the target application software, the method further includes: reading all application software of the vehicle; if the target application software is not found among all application software, then intercepting the parsed semantic data and generating an interception prompt.

[0010] Optionally, the target application software is a foreground service process.

[0011] Another embodiment of this application provides a semantic data processing apparatus. The apparatus is applied to middleware, which is a background service process. The apparatus includes: a receiving module for receiving semantic data sent by a sender; a processing module for parsing the semantic data according to the sender's semantic protocol, identifying the target application software corresponding to the parsed semantic data, and converting the parsed semantic data to generate control instructions executable by the target application software; and a sending module for sending the control instructions to the target application software, wherein the target application software performs a target operation according to the control instructions.

[0012] Optionally, the processing module is further configured to: acquire the target communication protocol; and transform the parsed semantic data based on the target communication protocol to generate control instructions executable by the target application software.

[0013] Optionally, the semantic data processing apparatus further includes: an encapsulation module, used to encapsulate the control commands into target format data using the communication protocol of the target application software before sending the control commands to the target application software.

[0014] Optionally, the semantic data processing device further includes: a reading module, used to read all application software installed in the vehicle before converting the parsed semantic data into control instructions executable by the target application software; and an interception module, used to intercept the parsed semantic data and generate an interception prompt when the target application software is not present in the total number of application software.

[0015] Optionally, the target application software is a foreground service process.

[0016] Another embodiment of this application provides a middleware, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the program to implement the semantic data processing method as described in the above embodiments.

[0017] Another embodiment of this application provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed, are used to implement the semantic data processing method as described in the above embodiments.

[0018] Another embodiment of this application provides a computer program product, including: a computer program or instructions, which, when executed, implement the semantic data processing method as described in the above embodiments.

[0019] Therefore, this application has at least the following beneficial effects:

[0020] This application embodiment receives semantic data sent by the sender and converts various heterogeneous semantic data into unified control commands executable by application software. It eliminates the need for separate protocol integration for each different speech recognition service or third-party application software, greatly simplifying the development and integration process. This not only improves the reusability of product functions but also significantly reduces the development cost of enterprise smart cockpit products.

[0021] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 is a flowchart of a semantic data processing method provided according to an embodiment of this application;

[0024] Figure 2 is a diagram showing the communication relationship between the middleware, the speech recognition service, and the operating system according to an embodiment of this application;

[0025] Figure 3 is an example diagram of a semantic data processing method according to an embodiment of this application;

[0026] Figure 4 is a block diagram of a semantic data processing apparatus according to an embodiment of this application;

[0027] Figure 5 is a schematic diagram of the structure of an on-board computer according to an embodiment of this application. Detailed Implementation

[0028] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0029] The following description, with reference to the accompanying drawings, outlines a method, apparatus, middleware, and storage medium for processing semantic data according to embodiments of this application. Addressing the problems mentioned in the background section, this application provides a method for processing semantic data. In this method, semantic data sent by a sender is received, and various heterogeneous semantic data are converted into unified control instructions executable by application software. This eliminates the need for separate protocol integration for each different speech recognition service or third-party application software, greatly simplifying the development and integration process. This not only improves the reusability of product functions but also significantly reduces the development cost of enterprise smart cockpit products.

[0030] Specifically, Figure 1 is a flowchart illustrating a semantic data processing method provided in an embodiment of this application.

[0031] As shown in Figure 1, this semantic data processing method is applied to middleware, which is a background service process. The method includes the following steps:

[0032] In step S101, semantic data sent by the sender is received.

[0033] For example, this method is executed by an on-board computer (or, referred to as an on-board controller). The on-board computer includes a first memory and a first processor. The first memory stores a semantic data processing program; the semantic data processing program is invoked and executed by the first processor to implement the semantic data processing method provided in this application. The first memory may include, but is not limited to, the following: Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), and Electrically Erasable Programmable Read-Only Memory (EEPROM). The first processor may consist of one or more integrated circuit chips. Optionally, the first processor may be a general-purpose processor, such as a Central Processing Unit (CPU) or a Network Processor (NP). Optionally, the first processor may implement the semantic data processing method provided in this application by running programs or code.

[0034] For example, an onboard computer is installed in a vehicle. The onboard computer runs an onboard operating system, and middleware runs within that operating system. Optionally, the middleware can be a background service process at the operating system level. Alternatively, the middleware can be a software module deployed in an onboard infotainment system or a smart cockpit domain controller.

[0035] Middleware, also known as semantic processing middleware, is a software layer located between the operating system and applications, used to handle the conversion and unified scheduling of heterogeneous semantic data. Optionally, middleware can parse diverse voice protocols from different speech recognition services; it can also convert the parsed semantics into unified, application-executable instructions; and it can distribute instructions to target applications (such as navigation, music players, or third-party software) according to business rules.

[0036] For example, the sender could be a speech recognition service. Middleware could receive semantic data sent by the speech recognition service.

[0037] Speech recognition services are integrated hardware and software systems that convert human language into structured semantic data. Speech recognition services extract user intent from human audio and generate machine-processable instructions or text (i.e., semantic data). It is understood that speech recognition services include hardware devices for capturing speech and software services for converting speech into semantics. This application integrates a speech recognition service into its intelligent vehicle cockpit system, where the speech recognition service uses its own semantic protocols to generate semantic data.

[0038] For example, a voice recognition service can capture human voice audio inside a vehicle using a microphone, use speech-to-text technology to convert the human voice audio into text, and use semantic understanding technology to parse the text into structured instructions to obtain semantic data.

[0039] In step S102, semantic data is parsed according to the sender's semantic protocol, and the target application software corresponding to the parsed semantic data is identified. The parsed semantic data is then converted to generate control instructions that can be executed by the target application software.

[0040] The diverse semantic protocols used in current smart cockpit voice recognition services (different vendors use different protocols, resulting in significant differences in semantic data structures) lead to high development costs for smart cockpits. Each new feature requires customizing protocols to interface with various vendors, making subsequent maintenance difficult. Therefore, the method provided in this embodiment standardizes the structure of multi-source semantic data through middleware, improving the development efficiency of smart cockpit systems.

[0041] The target application software is the application that ultimately executes the user's voice commands. Optionally, the target application software can run in the vehicle's operating system, or it can run in the vehicle's infotainment system or smart cockpit system. In this case, the target application software is a foreground service process that interacts with the user on the front-end display interface. For example, the target application software can be in-vehicle navigation software, vehicle control software (such as air conditioning control software, seat adjustment software), in-vehicle music player, etc.

[0042] In this embodiment, different speech recognition services may use different semantic protocols to represent the same intent or command. Therefore, this embodiment can parse various heterogeneous input semantic data and output unified executable instructions for application software. In actual execution, this embodiment calculates the target application software that needs to process the instructions contained in the semantic data according to business rules.

[0043] In one embodiment of this application, the parsed semantic data is transformed to generate control instructions executable by the target application software, including: obtaining a target communication protocol; and transforming the parsed semantic data based on the target communication protocol to generate control instructions executable by the target application software.

[0044] For example, the target communication protocol is the interface specification exposed by the target application software to receive control commands issued by the middleware. The middleware needs to convert semantic data from different sources into control commands that the target application software can recognize and that conform to the target communication protocol in order to transmit semantic data to the target application software.

[0045] The method provided in this embodiment ensures compatibility between control commands and target application software by acquiring the target communication protocol and converting semantic data based on that protocol. This method can adapt to differences in communication protocols among different application software, avoiding invalid commands due to protocol incompatibility. By dynamically adapting the target communication protocol, the accuracy and reliability of command generation are improved, enabling semantic data to be successfully converted into valid commands executable by the target application software. In this embodiment, the target application software is a foreground service process, which has higher priority and user interaction capabilities, ensuring timely response and execution of voice control commands. By limiting the operating mode of the target software, system resource scheduling is optimized, ensuring the real-time performance of critical operations while avoiding delays that may be caused by background process processing.

[0046] For ease of understanding, the specific implementation of this application embodiment can be described in detail with reference to Figure 2. As shown in Figure 2, 102 is the middleware that executes the semantic data processing method of this application embodiment, running as an independent process in the operating system. The semantic processing middleware is a background service process, without a foreground interface to interact with the user. 100-1 to 100-N refer to the application software independently developed by the current company, which runs as an independent process in the foreground and can interact with the user in the foreground interface. The semantic data communication between 101-1 to 101-N and the semantic middleware follows a custom inter-process communication protocol. The custom communication protocol usually includes control information descriptions, data structures or formats, and event occurrence order descriptions. 101-1 to 101-N refer to application software not independently developed by the current company that is accessed in the intelligent vehicle cockpit system, referred to here as third-party application software, which can interact with the user in the foreground interface, such as common social software, music players, etc. Third-party application software may have information communication protocols specified by the third-party company. In this case, the semantic processing middleware needs to process the semantic data according to the information communication protocol provided by the third-party company. 103-1 to 103-N refer to the voice recognition services integrated into the intelligent vehicle cockpit system. 104 refers to the operating system of the intelligent vehicle; all processes and services in Figure 1 run on the operating system. Semantic processing middleware services require adaptation development for different operating systems to achieve portability and functional reusability across different systems.

[0047] According to the embodiments of this application, the application software that needs to process the instructions contained in the semantic data, i.e., 100-1 to 100-N or 101-1 to 101-N, can be calculated based on the business rules.

[0048] For self-developed application software, the semantic processing middleware 102 uses a custom communication protocol to repackage semantic data and output it as unified executable instructions for the application software, and sends it to one or more application software programs 100-1 to 100-N. For third-party application software, the semantic processing middleware 102 uses the information communication protocol specified by the third-party company to repackage semantic data and output it as unified executable instructions for the application software, and sends it to one or more third-party application software programs 101-1 to 101-N.

[0049] In one embodiment of this application, before converting the parsed semantic data to generate control instructions executable by the target application software, the method further includes: reading all application software of the vehicle; if the target application software is not found among all application software, then intercepting the parsed semantic data and generating an interception prompt.

[0050] It is understood that this application embodiment can read the list of all installed application software in the current intelligent vehicle operating system, check whether the target application software corresponding to the parsed semantic data exists in the list. If the target application software is found not to exist in the vehicle's operating system, i.e., when the user attempts to call an uninstalled or unusable application via voice command, the semantic processing middleware will intercept the semantic data and generate a corresponding interception prompt. In actual execution, the prompt can be given to the user in the form of voice, informing the user that the specified application software has not been found or cannot be used, avoiding potential errors or abnormal situations caused by attempting to call a non-existent application. If the target application software exists, the subsequent data conversion and instruction generation process continues, and finally the control command is sent to the corresponding target application software.

[0051] The method provided in this embodiment intercepts invalid commands in advance by reading all application software installed in the vehicle and checking whether the target application software exists before converting semantic data. If the target application software does not exist, the semantic data is intercepted and a prompt is generated, avoiding operation failures caused by calling invalid applications. This method optimizes system resource allocation, prevents invalid commands from consuming processing resources, and improves user experience, allowing users to promptly understand the reason for operation failure.

[0052] In step S103, a control command is sent to the target application software, wherein the target application software executes the target operation according to the control command.

[0053] In one embodiment of this application, before sending the control command to the target application software, the method further includes: encapsulating the control command into target format data using the communication protocol of the target application software.

[0054] In this embodiment, for self-developed application software (100-1 to 100-N), the semantic processing middleware repackages control commands based on a custom data protocol (such as standard JSON format). For third-party application software (101-1 to 101-N), if encapsulation according to the third-party company's data protocol is required, the control commands are repackaged according to its specific data structure and communication protocol. This ensures a smooth and efficient transition from user voice input to final operation execution, enabling control commands to be correctly transmitted and processed, thus improving the response speed and user experience of the intelligent vehicle cockpit system.

[0055] The method provided in this embodiment encapsulates control commands into target format data using the target application software's communication protocol before sending the commands, thus resolving the data format compatibility issue between different software interfaces. This encapsulation process ensures that the control commands can be correctly recognized and executed by the target application software. This method optimizes the command transmission process, avoids command failures caused by format errors, and improves the stability and reliability of the system.

[0056] The semantic data processing method of this application embodiment, as shown in Figure 3, will be described in detail below, including the following steps:

[0057] Step 1: Collect human language audio data from the physical world, i.e., voice input, using hardware devices (such as microphones).

[0058] Step 2: The speech recognition service identifies the collected speech data, generates semantic data based on the semantic protocol, and sends the semantic data to the semantic processing middleware.

[0059] Step 3: The semantic processing middleware can proactively query the semantic recognition service to obtain semantic data, or passively wait to receive semantic data.

[0060] Step 4: The semantic processing middleware parses the semantic data based on the semantic protocol of the semantic data sender.

[0061] Step 5: The semantic processing middleware determines whether the semantic data needs to be sent to the self-developed application software.

[0062] Step 6: Based on the judgment result in Step 5, if yes, the semantic processing middleware repackages the control instructions into standard JSON format data based on the self-developed data protocol and sends it to the self-developed application software.

[0063] Step 7: The self-developed application software receives the JSON formatted data and performs the corresponding operations. This completes the data consumption.

[0064] Step 8: Based on the judgment result in Step 5, if it is not, the semantic processing middleware needs to read the relevant system configuration, query the target third-party application software, and determine whether it is installed on the current operating system.

[0065] Step 9: Based on the judgment result in Step 8, if it is negative, the semantic processing middleware intercepts the semantic data and prompts the user via voice that the third-party application software does not exist in the operating system. This completes the data consumption.

[0066] Step 10: Based on the judgment result in Step 8, if yes, the semantic processing middleware determines whether the control instructions need to be repackaged according to the data protocol provided by the third-party application software.

[0067] Step 11: Based on the judgment result in Step 10, if it is not, the semantic processing middleware will re-encapsulate the control instructions into standard JSON format data based on the self-developed data protocol.

[0068] Step 12: The semantic processing middleware uses a self-developed data protocol communication method to send JSON format data to third-party application software.

[0069] Step 13: The third-party application receives the JSON data and performs the corresponding operations. This completes the data consumption.

[0070] Step 14: Based on the judgment result in Step 10, if yes, the semantic processing middleware re-encapsulates the control instructions based on the third-party application software data protocol.

[0071] Step 15: The semantic processing middleware uses the third-party application software data protocol communication method to send the encapsulated data to the third-party application software.

[0072] Step 16: The third-party application software receives the protocol-encapsulated data and performs the corresponding operations. This completes the data consumption.

[0073] According to the semantic data processing method proposed in the embodiments of this application, semantic data sent by the sender is received and various heterogeneous semantic data are converted into unified control instructions executable by application software. There is no need to do separate protocol docking for each different speech recognition service or third-party application software, which greatly simplifies the development and integration process, not only improving the reusability of product functions, but also greatly reducing the development cost of enterprise intelligent cockpit products.

[0074] Next, the semantic data processing apparatus according to the embodiments of this application is described with reference to the accompanying drawings.

[0075] Figure 4 is a block diagram of a semantic data processing apparatus according to an embodiment of this application.

[0076] As shown in Figure 4, the semantic data processing device 10 includes a receiving module 100, a processing module 200, and a sending module 300.

[0077] The receiving module 100 is used to receive semantic data sent by the sender; the processing module 200 is used to parse the semantic data according to the sender's semantic protocol, identify the target application software corresponding to the parsed semantic data, and convert the parsed semantic data to generate control instructions that can be executed by the target application software; the sending module 300 is used to send control instructions to the target application software, wherein the target application software performs target operations according to the control instructions.

[0078] In one embodiment of this application, the processing module is further configured to: acquire the target communication protocol; and convert the parsed semantic data based on the target communication protocol to generate control instructions executable by the target application software.

[0079] In one embodiment of this application, the semantic data processing apparatus further includes: an encapsulation module, configured to encapsulate the control commands into target format data using the communication protocol of the target application software before sending the control commands to the target application software.

[0080] In one embodiment of this application, the semantic data processing device 10 further includes: a reading module, configured to read all the vehicle's application software before converting the parsed semantic data into control instructions executable by the target application software; and an interception module, configured to intercept the parsed semantic data and generate an interception prompt when the target application software is not present in the total application software.

[0081] In one embodiment of this application, the target application software is a foreground service process.

[0082] It should be noted that the foregoing explanation of the semantic data processing method embodiment also applies to the semantic data processing device of this embodiment, and will not be repeated here.

[0083] The semantic data processing apparatus proposed in the embodiments of this application receives semantic data sent by the sender and converts various heterogeneous semantic data into unified control instructions executable by application software. It eliminates the need for separate protocol integration for each different speech recognition service or third-party application software, greatly simplifying the development and integration process. This not only improves the reusability of product functions but also significantly reduces the development cost of enterprise smart cockpit products.

[0084] Figure 5 is a schematic diagram of the structure of the vehicle-mounted computer provided in an embodiment of this application. The vehicle-mounted computer may include:

[0085] The memory 501, the processor 502, and the computer program stored on the memory 501 and capable of running on the processor 502.

[0086] When the processor 502 executes the program, it implements the semantic data processing method provided in the above embodiments.

[0087] Furthermore, the onboard computer also includes:

[0088] Communication interface 503 is used for communication between memory 501 and processor 502.

[0089] The memory 501 is used to store computer programs that can run on the processor 502.

[0090] The memory 501 may include high-speed RAM (Random Access Memory) memory, and may also include non-volatile memory, such as at least one disk storage.

[0091] If the memory 501, processor 502, and communication interface 503 are implemented independently, they can be interconnected via a bus to communicate with each other. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, only one thick line is used in Figure 5, but this does not indicate that there is only one bus or one type of bus.

[0092] Optionally, in a specific implementation, if the memory 501, processor 502, and communication interface 503 are integrated on a single chip, then the memory 501, processor 502, and communication interface 503 can communicate with each other through an internal interface.

[0093] Processor 502 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of this application.

[0094] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the semantic data processing method described above.

[0095] This application also provides a computer-readable storage medium storing a computer program or instructions thereon, which, when executed, are used to implement the semantic data processing method described above.

[0096] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0097] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0098] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0099] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (FPGAs), field-programmable gate arrays (FPGAs), etc.

[0100] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0101] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A method for processing semantic data, wherein, The method is applied to middleware, which is a background service process, and includes the following steps: Receive semantic data sent by the sender; The semantic data is parsed according to the semantic protocol of the sender, and the target application software corresponding to the parsed semantic data is identified. The parsed semantic data is then converted to generate control instructions that can be executed by the target application software. The control command is sent to the target application software, wherein the target application software performs the target operation according to the control command.

2. The semantic data processing method according to claim 1, wherein, The parsed semantic data is transformed to generate control instructions executable by the target application software, including: Obtain the target communication protocol; Based on the target communication protocol, the parsed semantic data is transformed to generate control instructions executable by the target application software.

3. The method for processing semantic data according to claim 1 or 2, wherein, Before sending the control commands to the target application software, the method further includes: The control commands are encapsulated into target format data using the communication protocol of the target application software.

4. The method for processing semantic data according to any one of claims 1 to 3, wherein, Before converting the parsed semantic data into control instructions executable by the target application software, the method further includes: Read all application software installed in the vehicle; If the target application software is not found among all the application software, the parsed semantic data is intercepted and an interception prompt is generated.

5. The method for processing semantic data according to any one of claims 1 to 4, wherein, The target application software is a foreground service process.

6. A semantic data processing apparatus, wherein, The device is applied to middleware, which is a background service process, including: The receiving module is used to receive semantic data sent by the sender; The processing module is used to parse the semantic data according to the semantic protocol of the sender, identify the target application software corresponding to the parsed semantic data, and convert the parsed semantic data to generate control instructions that can be executed by the target application software. A sending module is used to send the control command to the target application software, wherein the target application software performs a target operation according to the control command.

7. The semantic data processing apparatus according to claim 6, wherein, The processing module is further used for: Obtain the target communication protocol; Based on the target communication protocol, the parsed semantic data is transformed to generate control instructions executable by the target application software.

8. A middleware, wherein, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the semantic data processing method as described in any one of claims 1 to 5.

9. A computer-readable storage medium having a computer program or instructions stored thereon, wherein, When the computer program or instructions are executed, they implement the semantic data processing method according to any one of claims 1 to 5.

10. A computer program product comprising: A computer program or instruction, wherein when executed, the computer program or instruction implements the semantic data processing method according to any one of claims 1 to 5.

Images