Vehicle-mounted intelligent communication methods, readable storage media and systems

Abstract

This application provides an in-vehicle intelligent communication method, a readable storage medium, and a system. The method encapsulates client operation request parameters and server-returned feedback results in key-value pairs within a Bundle object. Because Bundle uses a key-value pair storage structure, it supports flexible storage of various basic data types and serializable objects. No modification to the AIDL interface is required; only the key-value pairs within the Bundle need to be adjusted for adaptation. This avoids the frequent modifications and SDK updates caused by parameter changes in traditional AIDL interfaces, significantly reducing system iteration and maintenance costs. Furthermore, Bundle is a native data encapsulation container of the Android system, and its key-value pair structure provides a unified transmission standard for requested data. Both communicating parties can quickly locate the required parameters based on agreed-upon key names, eliminating the need for custom data parsing rules and reducing CPU and memory overhead and error rates during data parsing.

Description

Technical Field

[0001] This application relates to the field of aerosol technology, and more specifically, to an in-vehicle intelligent communication method, a readable storage medium, and a system. Background Technology

[0002] With the continuous development of automotive intelligence, in-vehicle intelligent cockpit systems integrate multiple functions such as navigation, entertainment, information display, and vehicle control (such as air conditioning, windows, seats, lights, etc.). In-vehicle systems typically use AIDL (Android Interface Definition Language) to achieve inter-process communication.

[0003] To avoid frequent modifications to the AIDL and updates to the SDK due to changes in server-side interface parameters, and to prevent caller crashes by using a single AIDL interface, pure JSON strings are currently commonly used for communication between vehicle systems. However, using JSON strings as text format requires serialization / deserialization during data encoding and decoding, resulting in high CPU and memory performance overhead. Summary of the Invention

[0004] The purpose of this application is to provide an in-vehicle intelligent communication method, a readable storage medium, and a system to solve the problem of high CPU and memory performance overhead caused by the current use of pure JSON strings for in-vehicle communication.

[0005] Firstly, this application provides an in-vehicle intelligent communication method applied to an in-vehicle intelligent cockpit system including a client and a server. The method is executed by the client and includes: sending target request information to a target server; wherein the target server represents a server that has completed an AIDL connection with the client; the target request information includes a client identity identifier, a first Bundle object, and a target callback object; the key-value pairs of the first Bundle object encapsulate target operation request parameters; the target callback object is an adjustment object corresponding to the target operation request parameters; receiving target feedback information returned by the server; wherein the target feedback information includes an identity verification identifier and a second Bundle object; the key-value pairs of the second Bundle object encapsulate feedback results corresponding to the target operation request parameters; verifying the identity verification identifier based on the client identity identifier; if the verification passes, obtaining the feedback results corresponding to the target operation request parameters in the key-value pairs of the second Bundle object; and performing a callback on the target callback object based on the feedback results corresponding to the target operation request parameters.

[0006] In the above-designed in-vehicle intelligent communication method, when the client and server of the in-vehicle intelligent cockpit system establish an AIDL connection, the operation request parameters of the requested information are encapsulated in the key-value pairs of the first Bundle object, and the feedback result page corresponding to the operation request parameters returned by the server is encapsulated in the key-value pairs of the second Bundle object. Since the Bundle adopts a key-value storage structure, it supports flexible storage of various basic data types (such as int, String, boolean) and serializable objects. When request parameters are added, their quantity adjusted, or their meaning changed, there's no need to modify the AIDL interface definition. Adaptation is achieved simply by adjusting the key-value pairs within the Bundle. This avoids the frequent modifications and SDK updates required by traditional AIDL interfaces due to parameter changes, as well as crashes caused by interface incompatibility, significantly reducing system iteration and maintenance costs. Furthermore, Bundle is a native data encapsulation container in the Android system, and its key-value pair structure provides a unified transmission standard for request data. Both communicating parties can quickly locate the required parameters based on agreed-upon key names, eliminating the need for custom data parsing rules (such as the additional serialization / deserialization logic required for pure JSON strings). This reduces CPU and memory overhead and error rates during data parsing, improving communication reliability while minimizing CPU and memory consumption. Additionally, this solution effectively verifies the legitimacy of feedback information through a client identity verification mechanism, preventing the receipt of forged or tampered feedback data and reducing communication risks. Moreover, targeted callbacks of feedback results are implemented through the target callback object, ensuring accurate transmission of results to the corresponding business processing logic and preventing result processing chaos.

[0007] In an optional implementation of the first aspect, before sending the target request information to the target server, the method further includes: obtaining a target interface call identifier; wherein the target interface call identifier includes the target server package name and at least one service instance parameter under the target server package name; and establishing an AIDL connection with the corresponding server through a basic communication component based on the target server package name in the target interface call identifier and each service instance parameter, thereby completing the AIDL connection with the target server.

[0008] In the above implementation, the client in this solution establishes an AIDL connection with the target server through the target interface call identifier and the basic communication component. Since the target interface call identifier includes the server package name and service instance parameters, the server package name can uniquely identify the server process, and the service instance parameters can uniquely identify the specific service instance within the server, avoiding connection to the wrong server or service instance. At the same time, the basic communication component integrates the core logic for AIDL connection establishment, which can quickly complete server location and connection establishment. Compared with the traditional method of manually configuring connection parameters, it reduces the steps and time required for connection establishment.

[0009] In an alternative implementation of the first aspect, before obtaining the interface call identifier of the target server, the method further includes: initializing the basic communication components after power-on startup.

[0010] In the above implementation, this solution initializes the basic communication components after the client is powered on, ensuring that the basic communication components are in a ready state, avoiding abnormalities caused by uninitialized components during subsequent AIDL connection establishment and communication, and improving the stability of the communication process.

[0011] Secondly, this application also provides an in-vehicle intelligent communication device, which is applied to an in-vehicle intelligent cockpit system including a client and a server. The in-vehicle intelligent communication device is installed in the client and includes: a first sending module, a first receiving module, a verification module, a first acquiring module, and a callback module. The first sending module is used to send target request information to a target server. The target server refers to the server that has completed an AIDL connection with the client. The target request information includes a client identity identifier, a first Bundle object, and a target callback object. The key-value pairs of the first Bundle object encapsulate target operation request parameters, and the target callback object is the target... The system comprises: a target operation request parameter corresponding to an adjustment object; a first receiving module for receiving target feedback information returned by the server; wherein the target feedback information includes an identity verification identifier and a second Bundle object, the second Bundle object containing key-value pairs encapsulating the feedback result corresponding to the target operation request parameter; a verification module for verifying the identity verification identifier based on the client's identity identifier; a first obtaining module for obtaining the feedback result corresponding to the target operation request parameter in the key-value pairs of the second Bundle object if the verification module passes the verification; and a callback module for performing a callback on the target callback object based on the feedback result corresponding to the target operation request parameter.

[0012] In the above-designed vehicle-mounted intelligent communication device, when the client and server of the vehicle-mounted intelligent cockpit system establish an AIDL connection, the operation request parameters of the requested information are encapsulated in the key-value pairs of the first Bundle object, and the feedback result page corresponding to the operation request parameters returned by the server is encapsulated in the key-value pairs of the second Bundle object. Since the Bundle adopts a key-value storage structure, it supports flexible storage of various basic data types (such as int, String, boolean) and serializable objects. When request parameters are added, their quantity adjusted, or their meaning changed, there's no need to modify the AIDL interface definition. Adaptation is achieved simply by adjusting the key-value pairs within the Bundle. This avoids the frequent modifications and SDK updates required by traditional AIDL interfaces due to parameter changes, as well as crashes caused by interface incompatibility, significantly reducing system iteration and maintenance costs. Furthermore, Bundle is a native data encapsulation container in the Android system, and its key-value pair structure provides a unified transmission standard for request data. Both communicating parties can quickly locate the required parameters based on agreed-upon key names, eliminating the need for custom data parsing rules (such as the additional serialization / deserialization logic required for pure JSON strings). This reduces CPU and memory overhead and error rates during data parsing, improving communication reliability while minimizing CPU and memory consumption. Additionally, this solution effectively verifies the legitimacy of feedback information through a client identity verification mechanism, preventing the receipt of forged or tampered feedback data and reducing communication risks. Moreover, targeted callbacks of feedback results are implemented through the target callback object, ensuring accurate transmission of results to the corresponding business processing logic and preventing result processing chaos.

[0013] Thirdly, this application also provides an in-vehicle intelligent communication method, applied to an in-vehicle intelligent cockpit system including a client and a server. The method is executed by the server and includes: receiving target request information; wherein the target request information includes a client identity identifier, a first Bundle object, and a target callback object, the first Bundle object's key-value pairs encapsulating target operation request parameters, and the target callback object being an adjustment object corresponding to the target operation request parameters; obtaining the target operation request parameters from the key-value pairs of the first Bundle object; adjusting the parameter data corresponding to the target operation request parameters according to the target operation request parameters to obtain a feedback result corresponding to the target operation request parameters; encapsulating the feedback result corresponding to the target operation request parameters in key-value pairs of a second Bundle object to obtain a second Bundle object; generating an identity verification identifier based on the client identity identifier, and generating target feedback information based on the identity verification identifier and the second Bundle object; determining the target client corresponding to the target request information based on the client identity identifier and the target callback object; and sending the target feedback information to the target client.

[0014] In the above-designed in-vehicle intelligent communication method, when the client and server of the in-vehicle intelligent cockpit system establish an AIDL connection, the operation request parameters of the requested information are encapsulated in the key-value pairs of the first Bundle object, and the feedback result page corresponding to the operation request parameters returned by the server is encapsulated in the key-value pairs of the second Bundle object. Since the Bundle adopts a key-value storage structure, it supports flexible storage of various basic data types (such as int, String, boolean) and serializable objects. When request parameters are added, their quantity adjusted, or their meaning changed, there's no need to modify the AIDL interface definition. Adaptation is achieved simply by adjusting the key-value pairs within the Bundle. This avoids the frequent modifications and SDK updates required by traditional AIDL interfaces due to parameter changes, as well as crashes caused by interface incompatibility, significantly reducing system iteration and maintenance costs. Furthermore, Bundle is a native data encapsulation container in the Android system, and its key-value pair structure provides a unified transmission standard for request data. Both communicating parties can quickly locate the required parameters based on agreed-upon key names, eliminating the need for custom data parsing rules (such as the additional serialization / deserialization logic required for pure JSON strings). This reduces CPU and memory overhead and error rates during data parsing, improving communication reliability while minimizing CPU and memory consumption. Additionally, this solution effectively verifies the legitimacy of feedback information through a client identity verification mechanism, preventing the receipt of forged or tampered feedback data and reducing communication risks. Moreover, targeted callbacks of feedback results are implemented through the target callback object, ensuring accurate transmission of results to the corresponding business processing logic and preventing result processing chaos.

[0015] In an optional implementation of the third aspect, adjusting the parameter data corresponding to the target operation request parameters according to the target operation request parameters to obtain the feedback result corresponding to the target operation request parameters includes: identifying the target operation type corresponding to the target operation request parameters according to the target operation request parameters; searching for the target service instance corresponding to the target operation type among multiple service instances according to the target operation type; and adjusting the parameter data corresponding to the target operation request parameters through the target service instance to obtain the feedback result corresponding to the target operation request parameters.

[0016] In the above implementation, this solution encapsulates different types of request processing logic into independent service instances, realizing modular decomposition of processing logic. This facilitates subsequent upgrades, maintenance, or vulnerability patching of individual service instances without affecting the normal operation of other service instances. Furthermore, by identifying the target operation type and matching the corresponding target service instance, each service instance focuses on processing specific types of requests, avoiding confusion in the processing logic of different types of requests and reducing the processing error rate.

[0017] In an optional implementation of the third aspect, before receiving the target request information, the method further includes: initializing each service instance after power-on startup and registering each service instance to the core control service component to complete the initialization of the server.

[0018] In the above implementation method, after the vehicle system is powered on and started, the server completes the initialization and registration of all service instances, which can ensure that the server is in a ready state after startup, improve the timeliness and stability of the server's response to client requests, and facilitate the unified management of service instances.

[0019] Fourthly, this application also provides an in-vehicle intelligent communication device applied to an in-vehicle intelligent cockpit system including a client and a server. The device is located in the server and includes: a second receiving module, a second acquiring module, an adjustment module, an encapsulation module, a generation module, a determination module, and a second sending module. The second receiving module is used to receive target request information; wherein the target request information includes a client identity identifier, a first Bundle object, and a target callback object. The key-value pairs of the first Bundle object encapsulate target operation request parameters, and the target callback object is the adjustment object corresponding to the target operation request parameters. The second acquiring module is used to acquire the target operation from the key-value pairs of the first Bundle object. The system comprises the following modules: a request parameter module, an adjustment module, and a second sending module. The adjustment module adjusts the parameter data corresponding to the target operation request parameter to obtain the feedback result corresponding to the target operation request parameter. The encapsulation module encapsulates the feedback result corresponding to the target operation request parameter into key-value pairs of a second Bundle object to obtain the second Bundle object. The generation module generates an identity verification identifier based on the client's identity identifier and generates target feedback information based on the identity verification identifier and the second Bundle object. The determination module determines the target client corresponding to the target request information based on the client's identity identifier and the target callback object. The second sending module sends the target feedback information to the target client.

[0020] In the above-designed vehicle-mounted intelligent communication device, when the client and server of the vehicle-mounted intelligent cockpit system establish an AIDL connection, the operation request parameters of the requested information are encapsulated in the key-value pairs of the first Bundle object, and the feedback result page corresponding to the operation request parameters returned by the server is encapsulated in the key-value pairs of the second Bundle object. Since the Bundle adopts a key-value storage structure, it supports flexible storage of various basic data types (such as int, String, boolean) and serializable objects. When request parameters are added, their quantity adjusted, or their meaning changed, there's no need to modify the AIDL interface definition. Adaptation is achieved simply by adjusting the key-value pairs within the Bundle. This avoids the frequent modifications and SDK updates required by traditional AIDL interfaces due to parameter changes, as well as crashes caused by interface incompatibility, significantly reducing system iteration and maintenance costs. Furthermore, Bundle is a native data encapsulation container in the Android system, and its key-value pair structure provides a unified transmission standard for request data. Both communicating parties can quickly locate the required parameters based on agreed-upon key names, eliminating the need for custom data parsing rules (such as the additional serialization / deserialization logic required for pure JSON strings). This reduces CPU and memory overhead and error rates during data parsing, improving communication reliability while minimizing CPU and memory consumption. Additionally, this solution effectively verifies the legitimacy of feedback information through a client identity verification mechanism, preventing the receipt of forged or tampered feedback data and reducing communication risks. Moreover, targeted callbacks of feedback results are implemented through the target callback object, ensuring accurate transmission of results to the corresponding business processing logic and preventing result processing chaos.

[0021] Fifthly, this application provides an in-vehicle intelligent communication system, including a client and a server. The client and server establish an AIDL connection. The client is used to send target request information to a target server. The target server refers to the server that has established an AIDL connection with the client. The target request information includes a client identity identifier, a first Bundle object, and a target callback object. The key-value pairs of the first Bundle object encapsulate target operation request parameters, and the target callback object is the adjustment object corresponding to the target operation request parameters. The server is used to obtain the target operation request parameters from the key-value pairs of the first Bundle object; adjust the parameter data corresponding to the target operation request parameters according to the target operation request parameters to obtain the feedback result corresponding to the target operation request parameters; and encapsulate the feedback result corresponding to the target operation request parameters in a second Bundle object. The system retrieves the second Bundle object from the key-value pairs; generates an identity verification identifier based on the client's identity, and generates target feedback information based on the identity verification identifier and the second Bundle object; determines the target client corresponding to the target request information based on the client's identity and the target callback object; sends the target feedback information to the target client; the client is also used to receive the target feedback information returned by the server; wherein, the target feedback information includes the identity verification identifier and the second Bundle object, and the key-value pairs of the second Bundle object encapsulate the feedback results corresponding to the target operation request parameters; verifies the identity verification identifier based on the client's identity; if the verification passes, retrieves the feedback results corresponding to the target operation request parameters from the key-value pairs of the second Bundle object; and performs a callback to the target callback object based on the feedback results corresponding to the target operation request parameters.

[0022] In the above-designed in-vehicle intelligent communication system, when the client and server of the in-vehicle intelligent cockpit system establish an AIDL connection, the operation request parameters of the requested information are encapsulated in the key-value pairs of the first Bundle object, and the feedback result page corresponding to the operation request parameters returned by the server is encapsulated in the key-value pairs of the second Bundle object. Since the Bundle adopts a key-value storage structure, it supports flexible storage of various basic data types (such as int, String, boolean) and serializable objects. When request parameters are added, their quantity adjusted, or their meaning changed, there's no need to modify the AIDL interface definition. Adaptation is achieved simply by adjusting the key-value pairs within the Bundle. This avoids the frequent modifications and SDK updates required by traditional AIDL interfaces due to parameter changes, as well as crashes caused by interface incompatibility, significantly reducing system iteration and maintenance costs. Furthermore, Bundle is a native data encapsulation container in the Android system, and its key-value pair structure provides a unified transmission standard for request data. Both communicating parties can quickly locate the required parameters based on agreed-upon key names, eliminating the need for custom data parsing rules (such as the additional serialization / deserialization logic required for pure JSON strings). This reduces CPU and memory overhead and error rates during data parsing, improving communication reliability while minimizing CPU and memory consumption. Additionally, this solution effectively verifies the legitimacy of feedback information through a client identity verification mechanism, preventing the receipt of forged or tampered feedback data and reducing communication risks. Moreover, targeted callbacks of feedback results are implemented through the target callback object, ensuring accurate transmission of results to the corresponding business processing logic and preventing result processing chaos.

[0023] In an optional implementation of the fifth aspect, the server includes a service instance component and a core control service component, with the service instance component connected to the core control service component. The core control service component is used to identify the target operation type corresponding to the target operation request parameters based on the target operation request parameters. Based on the target operation type, it searches for the target service instance corresponding to the target operation type in the service instance component. The service instance component is used to adjust the parameter data corresponding to the target operation request parameters through the target service instance to obtain the feedback result corresponding to the target operation request parameters.

[0024] In an optional implementation of the fifth aspect, the client includes a basic communication component and a callback object interface; the basic communication component is used to send target request information to the target server and receive target feedback information returned by the server; the callback object interface is used to call back the target callback object according to the feedback result corresponding to the target operation request parameters.

[0025] In a sixth aspect, the present invention provides an electronic device including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the methods described in the first aspect, any optional embodiment of the first aspect, the third aspect, and any optional embodiment of the third aspect.

[0026] In a seventh aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, performs the methods described in the first aspect, any optional embodiment of the first aspect, the third aspect, and any optional embodiment of the third aspect.

[0027] Eighthly, the present invention provides a computer program product, including a computer program / instruction, which, when executed by a processor, performs the methods described in the first aspect, any optional implementation of the first aspect, the third aspect, and any optional implementation of the third aspect.

[0028] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0029] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 This is a first structural schematic diagram of an in-vehicle intelligent communication system provided in an embodiment of this application; Figure 2 This is a schematic diagram of the second structure of the in-vehicle intelligent communication system provided in an embodiment of this application; Figure 3 This is an overall interactive schematic diagram of the vehicle-mounted intelligent communication method provided in the embodiments of this application; Figure 4 This is a schematic diagram of the structure of the in-vehicle intelligent communication device provided in the embodiments of this application; Figure 5 This is a schematic diagram of the structure of the in-vehicle intelligent communication device provided in the embodiments of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0031] Icons: 10-Client; 110-Basic Communication Components; 120-Callback Object Interface; 20-Server; 210-Service Instance Components; 220-Core Control Service Components; 400-First Sending Module; 410-First Receiving Module; 420-Verification Module; 430-First Acquisition Module; 440-Callback Module; 500-Second Receiving Module; 510-Second Acquisition Module; 520-Adjustment Module; 530-Encapsulation Module; 540-Generation Module; 550-Determining Module; 560-Second Sending Module; 6-Electronic Device; 601-Processor; 602-Memory; 603-Communication Bus. Detailed Implementation

[0032] The embodiments of the technical solution of this application will now be described in detail with reference to the accompanying drawings. These embodiments are only used to more clearly illustrate the technical solution of this application and are therefore merely examples, and should not be used to limit the scope of protection of this application.

[0033] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms “comprising” and “having”, and any variations thereof, in the specification, claims, and foregoing description of the drawings are intended to cover non-exclusive inclusion.

[0034] In the description of the embodiments of this application, technical terms such as "first" and "second" are used only to distinguish different objects and should not be construed as indicating or implying relative importance or implicitly specifying the number, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly defined.

[0035] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0036] In the description of the embodiments in this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0037] In the description of the embodiments of this application, the term "multiple" refers to two or more (including two), similarly, "multiple sets" refers to two or more (including two sets), and "multiple pieces" refers to two or more (including two pieces).

[0038] In the description of the embodiments of this application, the technical terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing the embodiments of this application and simplifying the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the embodiments of this application.

[0039] In the description of the embodiments of this application, unless otherwise expressly specified and limited, technical terms such as "installation," "connection," "joining," and "fixing" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. For those skilled in the art, the specific meaning of the above terms in the embodiments of this application can be understood according to the specific circumstances.

[0040] With the continuous development of automotive intelligence, in-vehicle intelligent cockpit systems integrate multiple functions such as navigation, entertainment, information display, and vehicle control (such as air conditioning, windows, seats, lights, etc.). In-vehicle systems typically use AIDL (Android Interface Definition Language) to achieve inter-process communication.

[0041] To avoid frequent modifications to the AIDL and updates to the SDK due to changes in server-side interface parameters, and to prevent caller crashes by using a single AIDL interface, pure JSON strings are currently commonly used for communication between vehicle systems. However, using JSON strings as text format requires serialization / deserialization during data encoding and decoding, resulting in high CPU and memory performance overhead.

[0042] Based on the above problems, this application designs an in-vehicle intelligent communication method, a readable storage medium, and a system. In this solution, when the client and server of the in-vehicle intelligent cockpit system establish an AIDL connection, the operation request parameters of the requested information are encapsulated in the key-value pairs of the first Bundle object, and the feedback result page corresponding to the operation request parameters returned by the server is encapsulated in the key-value pairs of the second Bundle object. Since the Bundle adopts a key-value storage structure, it supports flexible storage of various basic data types (such as int, String, boolean) and serializable objects. When request parameters are added, their quantity adjusted, or their meaning changed, there's no need to modify the AIDL interface definition. Adaptation is achieved simply by adjusting the key-value pairs within the Bundle. This avoids the frequent modifications and SDK updates required by traditional AIDL interfaces due to parameter changes, as well as crashes caused by interface incompatibility, significantly reducing system iteration and maintenance costs. Furthermore, Bundle is a native data encapsulation container in the Android system, and its key-value pair structure provides a unified transmission standard for request data. Both communicating parties can quickly locate the required parameters based on agreed-upon key names, eliminating the need for custom data parsing rules (such as the additional serialization / deserialization logic required for pure JSON strings). This reduces CPU and memory overhead and error rates during data parsing, improving communication reliability while minimizing CPU and memory consumption. Additionally, this solution effectively verifies the legitimacy of feedback information through a client identity verification mechanism, preventing the receipt of forged or tampered feedback data and reducing communication risks. Moreover, targeted callbacks of feedback results are implemented through the target callback object, ensuring accurate transmission of results to the corresponding business processing logic and preventing result processing chaos.

[0043] Based on the above ideas, this application first provides an in-vehicle intelligent communication system, such as... Figure 1 As shown, the vehicle-mounted intelligent communication system includes a client 10 and a server 20, and the client 10 and the server 20 establish an AIDL connection.

[0044] Among them, Client 10 refers to the functional module or application in the in-vehicle intelligent cockpit system that initiates communication requests, such as the navigation application module, the air conditioning control interaction module, the entertainment system application, etc., which is responsible for sending operation requests to the server, receiving processing results, and displaying processing results.

[0045] Server 20 refers to the functional module or service unit in the in-vehicle intelligent cockpit system that receives and processes client requests, such as the air conditioning control service module, window adjustment service module, seat adjustment service module, and lighting control service module, which has the ability to respond to client operation requests and return feedback results.

[0046] AIDL connection refers to inter-process communication connection established based on Android Interface Definition Language (AIDL). It is the standard connection method for realizing data interaction between different processes in the in-vehicle Android system, ensuring the stability and standardization of cross-process communication.

[0047] In an optional implementation of this embodiment, further, as shown... Figure 2 As shown, the server 20 designed in this solution may include a service instance component 210 and a core control service component 220. The service instance component 210 is connected to the core control service component 220. The client 10 designed in this solution may include a basic communication component 110 and a callback object interface 120.

[0048] Among them, service instance component 210 represents the component that integrates all service instances in the server, and is the carrier of service instances. It is responsible for providing the core control service component with the interface for finding and calling service instances. Core control service component 220 represents the core scheduling component in the server, which is responsible for managing all service instances (including initialization, registration, search, etc.). After receiving client requests, it identifies the operation type according to the request parameters and matches the corresponding target service instance. Basic communication component 110 represents the core component in client 10 that is responsible for establishing and maintaining AIDL connections, sending request information, and receiving feedback information. It integrates the implementation logic of AIDL interface and the basic functions of data transmission. Callback object interface 120 represents the callback interface defined in the client. It specifies the method specification for the target callback object to handle feedback results. The target callback object completes the reception and subsequent processing of feedback results by implementing this interface.

[0049] Based on the above-designed in-vehicle intelligent communication system, client 10 and server 20 can execute in-vehicle intelligent communication methods to achieve intelligent communication, such as... Figure 3 As shown, this vehicle-mounted intelligent communication method can be implemented in the following ways: Step S300: The client sends target request information to the target server. The target request information includes the client's identity identifier, the first Bundle object, and the target callback object.

[0050] Step S310: The target server obtains the target operation request parameters from the key-value pairs of the first Bundle object.

[0051] Step S320: The target server adjusts the parameter data corresponding to the target operation request parameters according to the target operation request parameters, and obtains the feedback result corresponding to the target operation request parameters.

[0052] Step S330: The target server encapsulates the feedback result corresponding to the target operation request parameters into key-value pairs of the second Bundle object, and obtains the second Bundle object.

[0053] Step S340: The target server generates an identity verification identifier based on the client's identity identifier, and generates target feedback information based on the identity verification identifier and the second Bundle object.

[0054] Step S350: The target server determines the target client corresponding to the target request information based on the client's identity identifier and the target callback object.

[0055] Step S360: The target server sends target feedback information to the target client.

[0056] Step S370: The client receives the target feedback information returned by the target server. The target feedback information includes an identity verification identifier and a second Bundle object.

[0057] Step S380: The client verifies the identity verification identifier in the target feedback information based on the client's identity identifier. If the verification passes, proceed to step S390.

[0058] Step S390: The client obtains the feedback result corresponding to the target operation request parameter in the key-value pair of the second Bundle object.

[0059] Step S400: The client sends a callback to the target callback object based on the feedback result corresponding to the target operation request parameters.

[0060] In the above implementation, the target server refers to the server that has completed the AIDL connection with the client and is able to receive and process the client's specific operation requests, i.e., the target object of the client's current communication.

[0061] In step S300, the client first confirms that it has completed the AIDL connection with the target server, and then constructs the target request information, which includes the client identity identifier, the first Bundle object, and the target callback object. After the construction is completed, the target request information is sent to the target server through the established AIDL connection.

[0062] The client identity identifier represents a unique identity credential assigned to each client, such as the client's package name or unique device number. It is used by the server to identify the client's identity and by the client to verify the validity of the identity verification identifier returned by the server.

[0063] A Bundle object represents a container used in the Android system for encapsulating and transmitting data. It stores data in key-value pairs and supports the storage and transmission of various basic data types and serializable objects. In this application, the key-value pairs of the first Bundle object encapsulate the target operation request parameters; the key-value pairs of the second Bundle object encapsulate the feedback results corresponding to the target operation request parameters.

[0064] The target callback object represents the object corresponding to the target operation request parameters, used to receive and process the feedback result. In essence, it is an implementation instance of a callback interface. When the server returns the feedback result, the result is called back to the corresponding processing logic on the client through this object.

[0065] In step S310, the target server receives the target request information sent by the client, and parses out the client identity identifier, the first Bundle object, and the target callback object. Since the Bundle object uses binary transmission, and the Bundle is a native data encapsulation container of the Android system, its key-value pair structure provides a unified transmission standard for request data, which is more in line with the underlying transmission mechanism of AIDL. Therefore, the target server does not need to use other data parsing rules for parsing, but can directly obtain the target operation request parameters encapsulated in the key-value pairs of the first Bundle object.

[0066] The target server can then execute step S320. After obtaining the target operation request parameters, it can call the corresponding business processing logic based on the extracted target operation request parameters, adjust the actual data corresponding to the parameters, and obtain the processing result as the feedback result after the adjustment is completed. Specifically, as one possible implementation, the core control service component in the target server can identify the target operation type corresponding to the target operation request parameters based on the target operation request parameters, and then search for the target service instance corresponding to the target operation type in the service instance component. Subsequently, the service instance component adjusts the parameter data corresponding to the target operation request parameters through the target service instance to obtain the feedback result corresponding to the target operation request parameters.

[0067] Based on the feedback result corresponding to the target operation request parameters, the target server continues to execute step S330, which encapsulates the feedback result corresponding to the target operation request parameters in key-value pairs of the second Bundle object to obtain the second Bundle object. Based on the received client identity identifier, an identity verification identifier is generated through a preset algorithm (such as MD5 encryption). Then, the identity verification identifier and the second Bundle object are combined to construct the target feedback information.

[0068] The target server also includes a client identity identifier (uniquely identifying the client) and a target callback object (bound to the client's specific request logic) to accurately locate the target client that sent the request. Then, through the AIDL connection, the constructed target feedback information is sent to the target client.

[0069] The client is in a listening state and receives the target feedback information returned by the target server after processing. This feedback information includes an identity verification identifier and a second Bundle object. The key-value pairs of the second Bundle object encapsulate the feedback results corresponding to the target operation request parameters.

[0070] The client extracts its own client identity identifier and matches it with the received identity verification identifier. The verification method can be adapted to the specific application scenario. For example, in an unencrypted scenario, verification can be achieved by directly comparing the client identity identifier with the identity verification identifier; in an encrypted scenario, the client can first decrypt the identity verification identifier, and then compare the decrypted identity verification identifier with the client identity identifier to achieve verification.

[0071] If the identity verification passes, it means that the received feedback information comes from a legitimate target server and has not been tampered with. At this time, the client can directly extract the feedback result corresponding to the target operation request parameter in the key-value pair of the second Bundle object, and then use the target callback object to call back the extracted feedback result to the corresponding business processing logic, thus completing the closed loop of the entire communication process.

[0072] The above-mentioned vehicle-mounted intelligent communication method can be illustrated by the following specific example: Assuming the in-vehicle air conditioning application (client) has completed an AIDL connection with the in-vehicle air conditioning control server (target server), the in-vehicle air conditioning application constructs the target request information: the client's identity is "com.car.navi.app" (air conditioning application package name); the first Bundle object encapsulates the target operation request parameters in key-value pairs, with the key being "operation_param" and the value being "temperature:26℃, type:aircondition"; the target callback object is "TempAdjustCallback". Subsequently, the in-vehicle air conditioning application sends this request information to the in-vehicle air conditioning control server via the AIDL connection.

[0073] The vehicle air conditioning control server receives the target request information sent by the vehicle air conditioning application through the established AIDL connection, and parses out the client identity "com.car.navi.app", the first Bundle object (key "operation_param", value "temperature:26℃, type:aircondition") and the target callback object "TempAdjustCallback".

[0074] The vehicle air conditioning control server obtains the target operation request parameter "adjust the air conditioning temperature to 26℃" from the key-value pair of the first Bundle object.

[0075] The vehicle air conditioning control server, based on the target operation request parameters, invokes the air conditioning temperature adjustment instance to adjust the air conditioning temperature to 26℃. It then uses a temperature sensor to detect the current air conditioning temperature, confirms that it has reached 26℃, and receives the feedback result "Air conditioning temperature successfully adjusted to 26℃". Specifically, assuming the air conditioning control server's service instance component includes a "temperature adjustment service instance" and a "fan speed adjustment service instance", the core control service component matches the "temperature adjustment service instance" to the vehicle air conditioning application's request based on "adjust the air conditioning temperature to 26℃". The temperature adjustment service instance processes the vehicle air conditioning application's request, controls the air conditioning temperature to adjust to 26℃, and returns the feedback result "Temperature adjustment successful, current temperature 26℃" to the core control service component.

[0076] The vehicle air conditioning control server encapsulates the feedback result in the form of key-value pairs in the second Bundle object, with the key being "result" and the value being "success: true, current_temp:26℃". Based on the client's identity identifier "com.car.navi.app", it uses MD5 encryption to generate an identity verification identifier "com.car.navi.app_123456". This verification identifier is combined with the second Bundle object to generate the target feedback information.

[0077] The vehicle air conditioning control server accurately locates the vehicle air conditioning application (target client) that sent the request based on the client identity identifier "com.car.navi.app" (uniquely identifying the vehicle air conditioning application) and the target callback object "TempAdjustCallback" (logically bound to the temperature adjustment request of the vehicle air conditioning application). Then, it sends the constructed target feedback information to the vehicle air conditioning application through an AIDL connection.

[0078] The vehicle air conditioning application listens for and receives target feedback information returned by the vehicle air conditioning control server. This target feedback information includes the identity verification identifier "com.car.navi.app_123456" (a verification code generated based on the client identity identifier) ​​and a second Bundle object (the key is "result" and the value is "success: true, current_temp:26℃").

[0079] The in-vehicle air conditioning application extracts its own client identity identifier "com.car.navi.app", decrypts the received identity verification identifier "com.car.navi.app_123456" (assuming it is generated using encryption), and obtains "com.car.navi.app" after decryption, which matches its own identifier, and the verification passes.

[0080] The in-vehicle air conditioning application parses the key-value pairs of the second Bundle object, extracts the feedback result as "Air conditioning temperature has been successfully adjusted to 26℃, current temperature 26℃", and through the target callback object "TempAdjustCallback", sends the feedback result back to the UI update logic of the in-vehicle air conditioning application, popping up a prompt "Air conditioning temperature successfully adjusted, current temperature 26℃" on the in-vehicle air conditioning application interface, thus completing the entire communication process.

[0081] In the above-designed in-vehicle intelligent communication method, when the client and server of the in-vehicle intelligent cockpit system establish an AIDL connection, the operation request parameters of the requested information are encapsulated in the key-value pairs of the first Bundle object, and the feedback result page corresponding to the operation request parameters returned by the server is encapsulated in the key-value pairs of the second Bundle object. Since the Bundle adopts a key-value storage structure, it supports flexible storage of various basic data types (such as int, String, boolean) and serializable objects. When request parameters are added, their quantity adjusted, or their meaning changed, there's no need to modify the AIDL interface definition. Adaptation is achieved simply by adjusting the key-value pairs within the Bundle. This avoids the frequent modifications and SDK updates required by traditional AIDL interfaces due to parameter changes, as well as crashes caused by interface incompatibility, significantly reducing system iteration and maintenance costs. Furthermore, Bundle is a native data encapsulation container in the Android system, and its key-value pair structure provides a unified transmission standard for request data. Both communicating parties can quickly locate the required parameters based on agreed-upon key names, eliminating the need for custom data parsing rules (such as the additional serialization / deserialization logic required for pure JSON strings). This reduces CPU and memory overhead and error rates during data parsing, improving communication reliability while minimizing CPU and memory consumption. Additionally, this solution effectively verifies the legitimacy of feedback information through a client identity verification mechanism, preventing the receipt of forged or tampered feedback data and reducing communication risks. Moreover, targeted callbacks of feedback results are implemented through the target callback object, ensuring accurate transmission of results to the corresponding business processing logic and preventing result processing chaos.

[0082] In an optional implementation of this embodiment, before sending the target request information to the target server, the client can also obtain the target interface call identifier, and then establish an AIDL connection with the corresponding server through the basic communication component based on the target server package name and each service instance parameter in the target interface call identifier, thus completing the AIDL connection with the target server. Specifically, the client calls the basic communication component, passing in the target server package name and service instance parameters from the target interface call identifier. The basic communication component locates and positions the target server process using the Android system's Binder mechanism based on the server package name; then, based on the service instance parameters, it locates the corresponding service instance within the target server process. After locating the instance, an AIDL connection is established between the client and the target server through the Binder mechanism. Once the connection is successfully established, the client can send the request information to the target server.

[0083] As a concrete example, the in-vehicle air conditioning application, based on business needs (the need to adjust the air conditioning temperature), identifies the target server as the in-vehicle air conditioning control server and obtains its target interface call identifier. This identifier includes the target server package name "com.car.aircondition.service" and the service instance parameter "temp_adjust" (the air conditioning temperature adjustment service instance parameter). The in-vehicle air conditioning application calls its own basic communication component, passing in the target server package name "com.car.aircondition.service" and the service instance parameter "temp_adjust". The basic communication component, through the Android Binder mechanism, locates the in-vehicle air conditioning control server process based on the server package name, and then locates the temperature adjustment service instance within that process based on the service instance parameter "temp_adjust". After location is complete, an AIDL connection is successfully established between the in-vehicle air conditioning application and the in-vehicle air conditioning control server. Once the connection is established, the in-vehicle air conditioning application can send air conditioning adjustment requests to the in-vehicle air conditioning control server.

[0084] In the above implementation, the client in this solution establishes an AIDL connection with the target server through the target interface call identifier and the basic communication component. Since the target interface call identifier includes the server package name and service instance parameters, the server package name can uniquely identify the server process, and the service instance parameters can uniquely identify the specific service instance within the server, avoiding connection to the wrong server or service instance. At the same time, the basic communication component integrates the core logic for AIDL connection establishment, which can quickly complete server location and connection establishment. Compared with the traditional method of manually configuring connection parameters, it reduces the steps and time required for connection establishment.

[0085] In an optional implementation of this embodiment, before establishing AIDL between the client and the target server, the client can prioritize initializing the basic communication components after the in-vehicle intelligent cockpit system is powered on and started, ensuring the normal execution of subsequent AIDL connection establishment and communication processes. Specifically, after the in-vehicle intelligent cockpit system is powered on, the client process starts. At this time, the client first triggers the initialization process of the basic communication components, where the initialization content may include, but is not limited to: loading the AIDL interface definition file, initializing the Binder communication object, configuring the communication timeout, initializing the data transmission buffer, and registering the communication status listening callback, etc. After the basic communication components are initialized, the basic communication components are in a ready state and can respond to subsequent AIDL connection establishment requests.

[0086] As a concrete example: After the in-vehicle intelligent cockpit system is powered on, the in-vehicle air conditioning application process starts, first triggering the initialization process of the basic communication components: loading the AIDL interface definition file (containing the AIDL interface for interacting with the air conditioning control server); initializing the Binder communication object and configuring the communication timeout to 500ms (to avoid communication blocking affecting user operation); initializing a 1024KB data transmission buffer to store request parameters and feedback results; and registering a communication status listener callback to monitor the establishment and disconnection status of AIDL connections (such as triggering reconnection logic when the connection is broken). After the basic communication components of the in-vehicle air conditioning application are initialized, the basic communication components are in a ready state and can respond to subsequent requests to establish AIDL connections with various servers.

[0087] In the above implementation, this solution initializes the basic communication components after the client is powered on, ensuring that the basic communication components are in a ready state, avoiding abnormalities caused by uninitialized components during subsequent AIDL connection establishment and communication, and improving the stability of the communication process.

[0088] In an optional implementation of this embodiment, after the in-vehicle system powers on and starts up, the server also needs to complete the initialization and registration of all service instances to ensure accurate response to client requests. Specifically, after the in-vehicle intelligent cockpit system powers on, the server process starts, and the server triggers the initialization process: First, it initializes each internal service instance (such as the air conditioning temperature adjustment service instance, seat angle adjustment service instance, window lifting service instance, etc.). The initialization includes loading the configuration parameters of the service instances, initializing the corresponding hardware control interfaces, and setting the working status of the service instances. Subsequently, it registers all initialized service instances to the core control service component, which records the operation type and invocation method corresponding to each service instance, completing the overall initialization of the server. After initialization, the server is in a ready state and can receive and process client requests.

[0089] In the above implementation method, after the vehicle system is powered on and started, the server completes the initialization and registration of all service instances, which can ensure that the server is in a ready state after startup, improve the timeliness and stability of the server's response to client requests, and facilitate the unified management of service instances.

[0090] Figure 4 A schematic structural block diagram of an in-vehicle intelligent communication device provided in this application is presented. It should be understood that the device is disposed in the client described above, and the device is connected to... Figure 3The method implementation corresponding to the client is capable of executing the steps involved in the aforementioned method. The specific functions of this device can be found in the description above; to avoid repetition, detailed descriptions are omitted here. This device includes at least one software functional module that can be stored in memory or embedded in the device's operating system (OS) in the form of software or firmware. Specifically, the device includes: a first sending module 400, a first receiving module 410, a verification module 420, a first acquiring module 430, and a callback module 440; the first sending module 400 is used to send target request information to the target server; wherein, the target server represents the server that has completed the AIDL connection with the client, and the target request information includes a client identity identifier, a first Bundle object, and a target callback object. The key-value pairs of the first Bundle object encapsulate target operation request parameters, and the target callback object is the adjustment object corresponding to the target operation request parameters; the first receiving module 410 is used to receive... The system receives target feedback information returned by the server; the target feedback information includes an identity verification identifier and a second Bundle object, and the key-value pairs of the second Bundle object encapsulate the feedback results corresponding to the target operation request parameters; the verification module 420 is used to verify the identity verification identifier based on the client's identity identifier; the first acquisition module 430 is used to acquire the feedback results corresponding to the target operation request parameters in the key-value pairs of the second Bundle object if the verification module passes the verification; the callback module 440 is used to call back the target callback object based on the feedback results corresponding to the target operation request parameters.

[0091] In the above-designed vehicle-mounted intelligent communication device, when the client and server of the vehicle-mounted intelligent cockpit system establish an AIDL connection, the operation request parameters of the requested information are encapsulated in the key-value pairs of the first Bundle object, and the feedback result page corresponding to the operation request parameters returned by the server is encapsulated in the key-value pairs of the second Bundle object. Since the Bundle adopts a key-value storage structure, it supports flexible storage of various basic data types (such as int, String, boolean) and serializable objects. When request parameters are added, their quantity adjusted, or their meaning changed, there's no need to modify the AIDL interface definition. Adaptation is achieved simply by adjusting the key-value pairs within the Bundle. This avoids the frequent modifications and SDK updates required by traditional AIDL interfaces due to parameter changes, as well as crashes caused by interface incompatibility, significantly reducing system iteration and maintenance costs. Furthermore, Bundle is a native data encapsulation container in the Android system, and its key-value pair structure provides a unified transmission standard for request data. Both communicating parties can quickly locate the required parameters based on agreed-upon key names, eliminating the need for custom data parsing rules (such as the additional serialization / deserialization logic required for pure JSON strings). This reduces CPU and memory overhead and error rates during data parsing, improving communication reliability while minimizing CPU and memory consumption. Additionally, this solution effectively verifies the legitimacy of feedback information through a client identity verification mechanism, preventing the receipt of forged or tampered feedback data and reducing communication risks. Moreover, targeted callbacks of feedback results are implemented through the target callback object, ensuring accurate transmission of results to the corresponding business processing logic and preventing result processing chaos.

[0092] Figure 5 A schematic structural block diagram of an in-vehicle intelligent communication device provided in this application is presented. It should be understood that the device is located in the server described above, and the device is connected to... Figure 3The method implementation corresponding to the server-side implementation can execute the steps involved in the aforementioned method. The specific functions of this device can be found in the description above; to avoid repetition, detailed descriptions are omitted here. This device includes at least one software function module that can be stored in a memory or embedded in the device's operating system (OS) in the form of software or firmware. Specifically, the device includes: a second receiving module 500, a second acquiring module 510, an adjustment module 520, an encapsulation module 530, a generation module 540, a determination module 550, and a second sending module 560; the second receiving module 500 is used to receive target request information; wherein, the target request information includes a client identity identifier, a first Bundle object, and a target callback object, the key-value pairs of the first Bundle object encapsulate target operation request parameters, and the target callback object is the adjustment object corresponding to the target operation request parameters; the second acquiring module 510 is used to acquire the target operation request parameters from the key-value pairs of the first Bundle object; the adjustment module 520 is used to adjust according to... The target operation request parameters are adjusted to obtain the corresponding feedback result. The encapsulation module 530 encapsulates the feedback result corresponding to the target operation request parameters into key-value pairs of a second Bundle object to obtain the second Bundle object. The generation module 540 generates an identity verification identifier based on the client identity identifier and generates target feedback information based on the identity verification identifier and the second Bundle object. The determination module 550 determines the target client corresponding to the target request information based on the client identity identifier and the target callback object. The second sending module 560 sends the target feedback information to the target client.

[0093] In the above-designed vehicle-mounted intelligent communication device, when the client and server of the vehicle-mounted intelligent cockpit system establish an AIDL connection, the operation request parameters of the requested information are encapsulated in the key-value pairs of the first Bundle object, and the feedback result page corresponding to the operation request parameters returned by the server is encapsulated in the key-value pairs of the second Bundle object. Since the Bundle adopts a key-value storage structure, it supports flexible storage of various basic data types (such as int, String, boolean) and serializable objects. When request parameters are added, their quantity adjusted, or their meaning changed, there's no need to modify the AIDL interface definition. Adaptation is achieved simply by adjusting the key-value pairs within the Bundle. This avoids the frequent modifications and SDK updates required by traditional AIDL interfaces due to parameter changes, as well as crashes caused by interface incompatibility, significantly reducing system iteration and maintenance costs. Furthermore, Bundle is a native data encapsulation container in the Android system, and its key-value pair structure provides a unified transmission standard for request data. Both communicating parties can quickly locate the required parameters based on agreed-upon key names, eliminating the need for custom data parsing rules (such as the additional serialization / deserialization logic required for pure JSON strings). This reduces CPU and memory overhead and error rates during data parsing, improving communication reliability while minimizing CPU and memory consumption. Additionally, this solution effectively verifies the legitimacy of feedback information through a client identity verification mechanism, preventing the receipt of forged or tampered feedback data and reducing communication risks. Moreover, targeted callbacks of feedback results are implemented through the target callback object, ensuring accurate transmission of results to the corresponding business processing logic and preventing result processing chaos.

[0094] According to some embodiments of this application, such as Figure 6As shown, this application provides an electronic device 6, including: a processor 601 and a memory 602. The processor 601 and the memory 602 are interconnected and communicate with each other through a communication bus 603 and / or other forms of connection mechanism (not shown). The memory 602 stores a computer program executable by the processor 601. When the computing device is running, the processor 601 executes the computer program to execute any of the optional implementation methods of the aforementioned client execution, such as steps S300, S370 to S390: the client sends target request information to the target server. The target request information includes a client identity identifier, a first Bundle object, and a target callback object; the client receives target feedback information returned by the target server. The target feedback information includes an identity verification identifier and a second Bundle object; the client verifies the identity verification identifier in the target feedback information according to the client identity identifier. If the verification passes, the client obtains the feedback result corresponding to the target operation request parameter in the key-value pair of the second Bundle object. Alternatively, the method may execute any of the aforementioned optional server-side execution methods, such as steps S310 to S360: The target server obtains the target operation request parameters from the key-value pairs of the first Bundle object; the target server adjusts the parameter data corresponding to the target operation request parameters according to the target operation request parameters to obtain the feedback result corresponding to the target operation request parameters; the target server encapsulates the feedback result corresponding to the target operation request parameters in the key-value pairs of the second Bundle object to obtain the second Bundle object; the target server generates an identity verification identifier based on the client identity identifier, and generates target feedback information based on the identity verification identifier and the second Bundle object; the target server determines the target client corresponding to the target request information based on the client identity identifier and the target callback object; the target server sends the target feedback information to the target client.

[0095] This application provides a computer-readable storage medium storing a computer program that, when executed by a processor, performs the method in any of the aforementioned optional implementations.

[0096] The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Red-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0097] This application provides a computer program product that, when run on a computer, causes the computer to perform a method in any of the optional implementations.

[0098] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and not to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application, and they should all be covered within the scope of the claims and specification of this application. In particular, as long as there is no structural conflict, the various technical features mentioned in the embodiments can be combined in any way. This application is not limited to the specific embodiments disclosed herein, but includes all technical solutions falling within the scope of the claims.

Claims

1. A vehicle-mounted intelligent communication method, characterized in that, An in-vehicle intelligent cockpit system including a client and a server, wherein the method is executed by the client, and the method includes: Send target request information to the target server; wherein, the target server refers to the server that has completed the AIDL connection with the client, the target request information includes the client identity identifier, a first Bundle object and a target callback object, the key-value pairs of the first Bundle object encapsulate the target operation request parameters, and the target callback object is the adjustment object corresponding to the target operation request parameters; Receive the target feedback information returned by the server; wherein, the target feedback information includes an identity verification identifier and a second Bundle object, and the key-value pairs of the second Bundle object encapsulate the feedback result corresponding to the target operation request parameters; The identity verification identifier is verified based on the client identity identifier; If the verification passes, the feedback result corresponding to the target operation request parameter in the key-value pair of the second Bundle object is obtained; The target callback object is called back based on the feedback result corresponding to the target operation request parameters.

2. The method according to claim 1, characterized in that, Before sending the target request information to the target server, the method further includes: Obtain the target interface call identifier; wherein, the target interface call identifier includes the target server package name and at least one service instance parameter under the target server package name; Using the basic communication components, an AIDL connection is established with the corresponding server based on the target server package name in the target interface call identifier and the parameters of each service instance, thus completing the AIDL connection with the target server.

3. The method according to claim 2, characterized in that, Before obtaining the interface call identifier of the target server, the method further includes: The basic communication components are initialized after power-on startup.

4. A vehicle-mounted intelligent communication method, characterized in that, An in-vehicle intelligent cockpit system including a client and a server, wherein the method is executed by the server, and the method includes: Receive target request information; wherein, the target request information includes a client identity identifier, a first Bundle object, and a target callback object, the first Bundle object encapsulates target operation request parameters in key-value pairs, and the target callback object is an adjustment object corresponding to the target operation request parameters; Retrieve the target operation request parameters from the key-value pairs of the first Bundle object; Based on the target operation request parameters, adjust the parameter data corresponding to the target operation request parameters to obtain the feedback result corresponding to the target operation request parameters; The feedback result corresponding to the target operation request parameters is encapsulated in key-value pairs of the second Bundle object to obtain the second Bundle object; An identity verification identifier is generated based on the client identity identifier, and target feedback information is generated based on the identity verification identifier and the second Bundle object; Based on the client identity identifier and the target callback object, the target client corresponding to the target request information is determined; Send the target feedback information to the target client.

5. The method according to claim 4, characterized in that, The step of adjusting the parameter data corresponding to the target operation request parameters according to the target operation request parameters to obtain the feedback result corresponding to the target operation request parameters includes: Based on the target operation request parameters, identify the target operation type corresponding to the target operation request parameters; Based on the target operation type, find the target service instance corresponding to the target operation type among multiple service instances; By using the target service instance, the parameter data corresponding to the target operation request parameters is adjusted to obtain the feedback result corresponding to the target operation request parameters.

6. The method according to claim 5, characterized in that, Before receiving the target request information, the method further includes: After power-on startup, each service instance is initialized and registered to the core control service component, thus completing the server initialization.

7. A vehicle-mounted intelligent communication system, characterized in that, The in-vehicle intelligent communication system includes a client and a server, and the client establishes an AIDL connection with the server. The client is used to send target request information to the target server; wherein, the target server refers to the server that has completed the AIDL connection with the client, and the target request information includes the client identity identifier, a first Bundle object and a target callback object, wherein the key-value pairs of the first Bundle object encapsulate the target operation request parameters, and the target callback object is the adjustment object corresponding to the target operation request parameters; The server is configured to: obtain the target operation request parameters from the key-value pairs of the first Bundle object; adjust the parameter data corresponding to the target operation request parameters according to the target operation request parameters to obtain the feedback result corresponding to the target operation request parameters; encapsulate the feedback result corresponding to the target operation request parameters in the key-value pairs of the second Bundle object to obtain the second Bundle object; generate an identity verification identifier according to the client identity identifier, and generate target feedback information according to the identity verification identifier and the second Bundle object; determine the target client corresponding to the target request information according to the client identity identifier and the target callback object; and send the target feedback information to the target client. The client is also configured to receive target feedback information returned by the server; wherein the target feedback information includes an identity verification identifier and a second Bundle object, the key-value pairs of the second Bundle object encapsulating the feedback result corresponding to the target operation request parameter; the client verifies the identity verification identifier according to the client identity identifier; if the verification passes, the client obtains the feedback result corresponding to the target operation request parameter in the key-value pairs of the second Bundle object; and the client calls back the target callback object according to the feedback result corresponding to the target operation request parameter.

8. The system according to claim 7, characterized in that, The server includes a service instance component and a core control service component, and the service instance component is connected to the core control service component. The core control service component is used to identify the target operation type corresponding to the target operation request parameters based on the target operation request parameters. Based on the target operation type, locate the target service instance corresponding to the target operation type in the service instance component; The service instance component is used to adjust the parameter data corresponding to the target operation request parameters through the target service instance, and obtain the feedback result corresponding to the target operation request parameters.

9. The system according to claim 7, characterized in that, The client includes basic communication components and a callback object interface; The basic communication component is used to send target request information to the target server and receive target feedback information returned by the server. The callback object interface is used to call back the target callback object based on the feedback result corresponding to the target operation request parameters.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 3 or 4 to 6.

Images