Vehicle communication method, system, device and medium

Abstract

The invention discloses a vehicle communication method, system and device and a medium, and relates to the technical field of computers, and the method comprises the steps that a first agent side responds to a service request of a target client side for a target service, and sends a target address of a target server side capable of providing the target service to the target client side, the first agent side and the target client side belong to the same domain controller; the target client side directly communicates with the target server side according to the target address, and when the target client side and the target server side belong to different domain controllers, serialization and deserialization transmission strategies are adopted for data transmission between the target client side and the target server side; and when the target client and the target server belong to the same domain controller, data transmission between the target client and the target server adopts a serialization-free transmission strategy.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and in particular, to a vehicle communication method, system, device and medium. BACKGROUND

[0002] At present, with the evolution of automotive electronic and electrical architecture to domain control and central computing, a large number of functional modules from different suppliers running on different operating systems are integrated in the vehicle. Due to the differences in their functional fields and technology selection, these modules generally use a variety of communication protocols, such as the AIDL (Android Interface Definition Language) protocol widely used in the intelligent cockpit domain, the DDS (Data Distribution Service) protocol dominant in the intelligent driving domain, and the SOME / IP (Service-Oriented Vehicle Ethernet Communication) protocol used for service-oriented communication. This heterogeneous communication environment leads to a significant technical dilemma: business modules running on different protocol stacks cannot directly interoperate, forming isolated "protocol islands", which seriously hinders the coordination and iterative upgrade of the overall vehicle function.

[0003] However, the existing communication mechanism generally relies on the serialization and deserialization process of data to exchange data between different entities. This process needs to be performed regardless of the actual physical location and running environment of the communication parties, without exception. This introduces unnecessary central processor resource consumption and communication delay, especially in high-frequency and large-volume communication scenarios, which becomes a bottleneck restricting the performance and efficiency improvement of the system. SUMMARY

[0004] A series of simplified concepts are introduced in the summary section, which will be further described in detail in the specific embodiments section. The summary section of the present application does not mean to attempt to limit the key features and necessary technical features of the claimed technical solutions, nor to attempt to determine the protection scope of the claimed technical solutions.

[0005] In a first aspect, an embodiment of the present application provides a vehicle communication method, the vehicle comprising at least two domain controllers, each of the domain controllers comprising a proxy end, at least one service end and at least one client end, the proxy end being communicatively connected with the at least one service end and the at least one client end based on a preset communication protocol, the proxy ends of different domain controllers being communicatively connected based on the preset communication protocol, the method comprising: The first proxy end sends a target address of a target service end capable of providing a target service to a target client end in response to a service request of the target client end for the target service, the first proxy end and the target client end belonging to the same domain controller; The target client communicates directly with the target server based on the target address. When the target client and the target server belong to different domain controllers, the data transmission between the target client and the target server adopts a serialization and deserialization transmission strategy. When the target client and the target server belong to the same domain controller, the data transmission between the target client and the target server adopts an unserialization transmission strategy.

[0006] In one embodiment of the present invention, the same domain controller includes multiple processes, each process sharing the same shared memory. Before the first agent responds to a service request from the target client for the target service, the method further includes: When the target client and the target server are located in different processes of the same domain controller, the first agent responds to the online request of the target server, allocates a target address to the target server, and stores the target address in the shared memory.

[0007] In one embodiment of the present invention, the same domain controller includes at least one process, and the first agent, in response to a service request from a target client for a target service, includes: When the first proxy, the target client, and the target server are in the same process, the first proxy responds to the online request of the target server by registering the object pointer of the target server.

[0008] In one embodiment of the present invention, before the first proxy responds to the target client's service request for the target service, it includes: When the target client and the target server are located on different domain controllers, the first agent obtains the target address of the target server and the target services that the target server can provide from the second agent. The second agent and the target server are located on the same domain controller. In response to the online request of the target server, the second agent allocates a target address to the target server and sends the target address and the target services provided by the target server to the first agent.

[0009] In one embodiment of the present invention, the target client communicates directly with the target server based on the target address, including: When the target client and the target server are located in different processes of the same domain controller, the target client writes the structured data to be transmitted into shared memory; The target server reads the structured data from the shared memory.

[0010] In one embodiment of the present invention, the target client communicates directly with the target server based on the target address, including: When the target client and the target server are located on the same domain controller and in the same process, the target client obtains the object pointer of the target server from the first agent. The target client communicates by calling functions on the target server based on the object pointer.

[0011] In one embodiment of the present invention, the target client communicates directly with the target server based on the target address, including: When the target client and the target server are located on different domain controllers, the target client performs a serialization operation on the structured data to be transmitted to generate network transmission data packets; The target server performs a deserialization operation on the received network transmission data packets to obtain the structured data.

[0012] Secondly, this application proposes a vehicle communication system, wherein the vehicle includes at least two domain controllers, each domain controller includes an agent, at least one server and at least one client, the agent communicates with the at least one server and the at least one client based on a preset communication protocol, and the agent of different domain controllers communicates with each other based on the preset communication protocol, the system includes: an address transmission module and a data communication module; The address transmission module is configured such that: in response to a service request from a target client for a target service, the first proxy sends the target address of the target server that can provide the target service to the target client, wherein the first proxy and the target client belong to the same domain controller; The data communication module is configured such that: the target client communicates directly with the target server based on the target address; wherein, when the target client and the target server belong to different domain controllers, the data transmission between the target client and the target server adopts a serialization and deserialization transmission strategy; when the target client and the target server belong to the same domain controller, the data transmission between the target client and the target server adopts an unserialization transmission strategy.

[0013] Thirdly, an electronic device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program stored in the memory to implement the steps of a vehicle communication method as described in any of the first aspects above.

[0014] Fourthly, this application also proposes a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of a vehicle communication method according to any one of the first aspects.

[0015] In summary, the vehicle communication method of this application embodiment achieves unified registration, management and discovery of service resources by deploying agent terminals in each domain controller. By intelligently judging the location of the domain controller to which the server and client belong before communication is established, it adaptively selects the optimal transmission strategy for different communication scenarios. By distinguishing between cross-domain and intra-domain scenarios and using mechanisms such as non-serialized shared memory or function calls in intra-domain communication, it significantly reduces data transmission latency and system resource consumption. Thus, while ensuring communication reliability, it greatly improves the overall efficiency and real-time performance of the in-vehicle communication network.

[0016] The vehicle communication method proposed in this application, along with other advantages, objectives, and features of this application, will be partly apparent from the following description and partly understood by those skilled in the art through study and practice of this application. Attached Figure Description

[0017] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit this specification. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 This is a schematic flowchart of a vehicle communication method provided in an embodiment of this application; Figure 2 A schematic diagram of the communication architecture of a vehicle communication method provided in this application embodiment; Figure 3 A schematic diagram of the communication architecture of a vehicle communication method provided in this application, in which the target client and the target server are located in different processes of the same domain controller; Figure 4 A schematic diagram of the communication architecture in a vehicle communication method provided in this application, in which the target client and the target server are located in the same process; Figure 5 A schematic diagram of the communication architecture in a vehicle communication method provided in this application, in which the target client and the target server are located in different domain controllers; Figure 6 This application provides a schematic diagram of a vehicle communication system structure. Figure 7 This is a schematic diagram of a vehicle communication electronic device provided in an embodiment of this application. Detailed Implementation

[0018] To better understand the technical solutions provided in the embodiments of this specification, the technical solutions of the embodiments of this specification will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments of this specification and the specific features in the embodiments are detailed descriptions of the technical solutions of the embodiments of this specification, rather than limitations on the technical solutions of this specification. In the absence of conflict, the embodiments of this specification and the technical features in the embodiments can be combined with each other.

[0019] In this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, without necessarily requiring or implying any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element. The term "two or more" includes two or more cases.

[0020] Please see Figure 1 This is a schematic flowchart of a vehicle communication method provided in an embodiment of this application. The vehicle includes at least two domain controllers. Each domain controller includes a proxy, at least one server, and at least one client. The proxy communicates with the at least one server and the at least one client based on a preset communication protocol. The proxy of different domain controllers communicates with each other based on the preset communication protocol. Specifically, this may include: S110. In response to the target client’s service request for the target service, the first agent sends the target address of the target server that can provide the target service to the target client. The first agent and the target client belong to the same domain controller. For example, such as Figure 2The diagram illustrates the communication architecture of a vehicle communication method proposed in this application. The client and server refer to the ports of the domain controller, interacting through a pre-defined communication protocol, such as the VexusBus protocol, to achieve unified communication across and within the vehicle domain. The client is used to call functions provided by the server to complete its tasks. Specifically, the client can run in different processes or threads of the domain controller, such as the user interface module of the intelligent seating domain and the perception module of the intelligent driving domain. The client sends a service request to an agent within the same domain controller. The agent sends the target address of the server to the target client. The client establishes a communication connection directly with the server based on the obtained target address and selects a transmission strategy based on the communication scenario, such as serialized network transmission or unserialized intra-domain transmission. The server provides specific functions or services. The server sends an online request to an agent within the same domain controller, registers its interface information, and obtains a unique target address. Once registration is successful, the server waits for client calls and performs corresponding data processing and responses based on the communication scenario, such as intra-domain or cross-domain communication.

[0021] Communication between different modules within the vehicle can be categorized into five scenarios, all of which can be covered by the unified VexusBus protocol. Scenario 1 involves cross-domain communication, with the cockpit domain and intelligent driving domain communicating via Ethernet and the VexusBus protocol. Scenario 2 involves intra-domain communication (…). Figure 2 (Taking autonomous driving as an example) Different processes communicate using a server / client model, via shared memory and the VexusBus protocol. Scenario 3 involves different threads within the same process communicating via function calls and the VexusBus protocol. Scenario 4 involves different processes within the same process communicating via a PUB (publisher) / SUB (subscriber) model, via shared memory and the VexusBus protocol. Scenario 5 involves different threads within the same process communicating via a PUB / SUB model, via function calls and the VexusBus protocol.

[0022] The vehicle includes at least two domain controllers, each of which includes an agent, at least one server, and at least one client. The agent communicates with at least one server and at least one client based on a preset communication protocol. Agents of different domain controllers communicate with each other based on the preset communication protocol, which is the VexusBus protocol. The VexusBus protocol is used to provide a unified interface and high-performance transmission framework for service communication between different domains and systems within the intelligent vehicle. When a target client needs to call a target service, it will first send a service request to the first agent located in the same domain controller. The first agent, as the communication management core of its domain, maintains the correspondence between the interface information of all registered servers and the target address. After receiving the service request, it can quickly determine the target server that can provide the target service and its corresponding target address, and return the target address to the target client, thus providing a prerequisite for establishing a direct communication link between the two parties.

[0023] S120. The target client communicates directly with the target server based on the target address. When the target client and the target server belong to different domain controllers, the data transmission between the target client and the target server adopts a serialization and deserialization transmission strategy. When the target client and the target server belong to the same domain controller, the data transmission between the target client and the target server adopts an unserialization transmission strategy.

[0024] For example, after obtaining the target address, the target client establishes a direct communication link with the target server based on the target address, and autonomously selects a data transmission strategy based on whether the two parties belong to the same domain controller: if the target client and the target server belong to different domain controllers, a network transmission strategy based on serialization and deserialization is adopted to ensure reliable data transmission across domains; if the two are located in the same domain controller, an intra-domain transmission strategy without serialization is adopted, and efficient data interaction is carried out directly through shared memory or function calls, which significantly reduces communication latency and resource overhead.

[0025] In summary, the vehicle communication method proposed in this application achieves unified registration, management, and discovery of service resources by deploying agent terminals in each domain controller. By intelligently determining the location of the domain controllers to which the server and client belong before communication is established, it adaptively selects the optimal transmission strategy for different communication scenarios. By distinguishing between cross-domain and intra-domain scenarios and employing mechanisms such as non-serialized shared memory or function calls in intra-domain communication, it significantly reduces data transmission latency and system resource consumption. Thus, while ensuring communication reliability, it greatly improves the overall efficiency and real-time performance of the in-vehicle communication network.

[0026] In some examples, the same domain controller includes multiple processes, each sharing the same shared memory. Before the first agent responds to a service request from a target client for a target service, the method further includes: When the target client and the target server are located in different processes of the same domain controller, the first agent responds to the online request of the target server, allocates a target address to the target server, and stores the target address in the shared memory.

[0027] For example, such as Figure 3 The diagram illustrates the communication architecture of a vehicle communication method proposed in this application, where the target client and target server are located in different processes on the same domain controller. The same domain controller includes multiple processes, all sharing the same shared memory. The preset communication protocol is the Vexus Bus protocol, which runs on the first agent within each domain controller. When the target server starts and wants to provide services, it must first initiate an online registration request to the first agent located on the same domain controller. This online registration request contains service interface information uniformly defined by the Vexus Bus interface description language. Upon receiving this online request, according to the address allocation rules specified by the Vexus Bus protocol, an unused address identifier is allocated to the target server from its managed logical address pool; this address is the target address. After the allocation is completed, the first agent will register and store the mapping relationship between the first interface information of the target server and the target address in its local service registry, thereby completing the global visibility registration of the service. Then, based on the characteristic that multiple processes in the same domain controller share the same memory space, the target address is synchronously written into the shared memory to ensure that both communicating parties can quickly obtain the address information required for communication by accessing this shared area.

[0028] By uniformly allocating addresses through the first agent and pre-storing address information in shared memory, an efficient addressing channel is established for subsequent high-speed communication. By accurately identifying the communication scenario as intra-domain cross-process and forcibly adopting a shared memory-based, non-serialization-based transmission strategy, the CPU computational overhead and memory copy overhead caused by serialization and deserialization processes are fundamentally eliminated. This not only significantly reduces communication latency and improves the system's real-time response capability, making it particularly suitable for applications with high real-time requirements such as autonomous driving, but also reduces unnecessary resource consumption.

[0029] In some examples, the same domain controller includes at least one process that, prior to the first agent responding to a service request from a target client for a target service, includes: When the first proxy, the target client, and the target server are in the same process, the first proxy responds to the online request of the target server by registering the object pointer of the target server.

[0030] For example, such as Figure 4 The diagram illustrates a communication architecture in a vehicle communication method proposed in this application, where the target client and target server reside in the same process. The same domain controller includes at least one process. When the target client, target server, and first agent are all located within the same process of the same domain controller, the first agent responds to the target server's online request. This online request includes service interface information uniformly defined by a preset communication protocol, namely the Vexus Bus Interface Description Language (IDL). Upon receiving the online request, the first agent does not allocate a network logical address but instead registers and stores the target server's object pointer in its process's service registry. This registration operation establishes a mapping relationship between the service interface information and the object pointer, thereby completing the service publication.

[0031] For target servers and clients deployed within the same process, a communication mechanism that directly registers and passes object pointers, and uses object pointer function calls, completely eliminates all performance overhead associated with serialization, deserialization, and cross-process communication. This not only achieves near-limitless communication latency, reaching nanosecond-level call response, but also significantly reduces the computational burden on the central processing unit and memory access pressure.

[0032] In some examples, the first proxy, before responding to a service request from the target client for the target service, includes: When the target client and the target server are located on different domain controllers, the first agent obtains the target address of the target server and the target services that the target server can provide from the second agent. The second agent and the target server are located on the same domain controller. In response to the online request of the target server, the second agent allocates a target address to the target server and sends the target address and the target services provided by the target server to the first agent.

[0033] For example, such as Figure 5The diagram illustrates the communication architecture of a vehicle communication method proposed in this application where the target client and target server are located on different domain controllers. When the target client and target server are on different domain controllers, service discovery and communication rely on the collaborative work of agents within each domain controller. Specifically, the second agent, located on the same domain controller as the target server, first responds to the target server's online request. This online request contains service interface information uniformly defined by the Vexus Bus Interface Description Language (IDL). Upon receiving this online request, the second agent, according to the preset address allocation rules in the Vexus Bus protocol, allocates a unique network logical identifier as its target address from its maintained logical address pool, thus completing the address binding of the target server within this domain. Subsequently, the second agent will periodically or event-triggeredly transmit the service interface information of all registered servers in its domain and their corresponding target addresses to other domain controllers, such as the agent in the domain where the first agent is located, through the synchronization message format defined by the Vexus Bus protocol via the inter-domain network link. This will achieve the synchronization and sharing of global service information and ensure that the first agent can maintain a complete registry containing all available services for the entire vehicle.

[0034] In some examples, the target client communicates directly with the target server based on the target address, including: When the target client and the target server are located in different processes of the same domain controller, the target client writes the structured data to be transmitted into shared memory; The target server reads the structured data from the shared memory.

[0035] For example, when the target client and target server are located in different processes within the same domain controller, after obtaining the target address of the target server from the first agent, the target client establishes a direct communication link with the target server based on this address information. The target client directly writes the structured data to be transmitted into a designated area of ​​shared memory shared by multiple processes within the domain controller. Here, structured data refers to business data objects uniformly defined by the Vexus Bus interface description language and whose original organization and type information are maintained in memory. After the target server detects that the data in the shared memory is ready through real-time monitoring or event notification mechanisms, it immediately reads the structured data from the corresponding area of ​​the shared memory and directly uses it for subsequent business logic processing. The entire data transmission process completely avoids the serialization operation of converting data into a byte stream and the deserialization operation of reconstructing the byte stream into a data object, achieving zero serialization overhead for cross-process communication within the domain.

[0036] In some examples, the target client communicates directly with the target server based on the target address, including: When the target client and the target server are located on the same domain controller and in the same process, the target client obtains the object pointer of the target server from the first agent. The target client communicates by calling functions on the target server based on the object pointer.

[0037] For example, when a target client within the same process initiates a service request to the target server through the first proxy, the first proxy matches the interface information in the service request with the service registry. Upon successful matching, the first proxy directly returns the registered object pointer to the target client. After obtaining this object pointer, the target client can directly access the target server's memory space and call its functions through simple object pointer calls. Throughout this process, communication data is always transmitted within the process's address space in its original structured form, completely avoiding any form of data serialization, deserialization, or memory copying operations, thus achieving true zero-copy communication.

[0038] In some examples, the target client communicates directly with the target server based on the target address, including: When the target client and the target server are located on different domain controllers, the target client performs a serialization operation on the structured data to be transmitted to generate network transmission data packets; The target server performs a deserialization operation on the received network transmission data packets to obtain the structured data.

[0039] For example, when the target client and target server are located on different domain controllers, after the target client establishes a network connection with the target server based on the target address, it needs to use a network transmission strategy based on serialization and deserialization for data interaction. Specifically, the target client first converts the raw structured data to be transmitted into a byte stream format conforming to the Vexus Bus protocol specification, according to the data structure uniformly defined by the Vexus Bus interface description language. This process is the serialization operation. The serialization operation strictly follows the encoding rules preset by the Vexus Bus protocol, standardizing the data type, length, field order, and nesting structure to generate a flat network transmission data packet that can be transmitted over the network. Subsequently, the target client sends the serialized network transmission data packet to the network address of the domain controller where the target server is located via an inter-domain network link such as vehicular Ethernet.

[0040] The network data packets received by the target server are continuous byte streams, requiring reverse parsing to restore them to the original data format that the application can process. The target server parses the received network data packets according to the same Vexus Bus protocol's preset decoding rules, progressively extracting the type identifier, field length, and specific data content. Based on the data structure defined by the Vexus Bus interface description language, it reconstructs a structured data object in memory that is completely identical to the original data structure of the sending end. This process is called deserialization. After deserialization, the target server can directly use the restored structured data object for subsequent business logic processing.

[0041] like Figure 6 As shown, this application proposes a vehicle communication system. The vehicle includes at least two domain controllers. Each domain controller includes an agent, at least one server, and at least one client. The agent communicates with the at least one server and the at least one client based on a preset communication protocol. The agent of different domain controllers communicates with each other based on the preset communication protocol. The system includes an address transmission module 21 and a data communication module 22. The address transmission module 21 is configured such that: in response to a service request from a target client for a target service, the first proxy sends the target address of the target server that can provide the target service to the target client, wherein the first proxy and the target client belong to the same domain controller; The data communication module 22 is configured such that: the target client communicates directly with the target server based on the target address, wherein when the target client and the target server belong to different domain controllers, the data transmission between the target client and the target server adopts a serialization and deserialization transmission strategy; when the target client and the target server belong to the same domain controller, the data transmission between the target client and the target server adopts an unserialization transmission strategy.

[0042] The effects of applying the aforementioned method in the above system can be found in the description of the aforementioned method embodiments, and will not be repeated here.

[0043] like Figure 7 As shown, this application embodiment also provides an electronic device 300, including a memory 310, a processor 320, and a computer program 311 stored in the memory 310 and executable on the processor. When the processor 320 executes the computer program 311, it implements the steps of any of the above-described vehicle communication methods.

[0044] Since the electronic device described in this embodiment is a device used to implement a vehicle communication device in the embodiments of this application, those skilled in the art can understand the specific implementation method and various variations of the electronic device in this embodiment based on the method described in the embodiments of this application. Therefore, how the electronic device implements the method in the embodiments of this application will not be described in detail here. Any device used by those skilled in the art to implement the method in the embodiments of this application falls within the scope of protection of this application.

[0045] In practical implementation, when the computer program 311 is executed by the processor, it can achieve the following: Figure 1 Any of the corresponding implementation methods in the embodiments.

[0046] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0047] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-readable program code.

[0048] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0049] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0050] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes ​ The steps of the function specified in one or more boxes.

[0051] This application also provides a computer program product, which includes computer software instructions that, when executed on a processing device, cause the processing device to execute the LDPC decoding method of a solid-state drive controller.

[0052] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0053] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0054] In the several embodiments provided in this application, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between devices or units, and may be electrical, mechanical, or other forms.

[0055] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0056] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0057] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0058] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended 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 of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

[0059] Although preferred embodiments have been described in this specification, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this specification.

[0060] Obviously, those skilled in the art can make various modifications and variations to this specification without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims and their equivalents, this specification is also intended to include such modifications and variations.

Claims

1. A vehicle communication method characterized by, The vehicle includes at least two domain controllers, each of which includes an agent end, at least one service end and at least one client, the agent end is communicatively connected with the at least one service end and the at least one client based on a preset communication protocol, the agent ends of different domain controllers are communicatively connected based on the preset communication protocol, and the method comprises: The first agent end sends a target address of a target service end capable of providing a target service to the target client in response to a service request of the target client for the target service, and the first agent end and the target client belong to the same domain controller; The target client directly communicates with the target service end according to the target address, wherein when the target client and the target service end belong to different domain controllers, the target client and the target service end adopt a serialization and deserialization transmission strategy for data transmission; and when the target client and the target service end belong to the same domain controller, the target client and the target service end adopt a serialization-free transmission strategy for data transmission.

2. The vehicle communication method according to claim 1, characterized by, The same domain controller includes a plurality of processes, each of which shares the same shared memory, and before the first agent end responds to the service request of the target client for the target service, the method further comprises: In the case that the target client and the target service end are located in different processes of the same domain controller, the first agent end allocates a target address to the target service end and stores the target address in the shared memory in response to an online request of the target service end.

3. The vehicle communication method according to claim 1, characterized by, The same domain controller includes at least one process, and before the first agent end responds to the service request of the target client for the target service, the method further comprises: In the case that the first agent end, the target client and the target service end are located in the same process, the first agent end registers an object pointer of the target service end in response to an online request of the target service end.

4. The vehicle communication method according to claim 1, characterized by, Before the first agent end responds to the service request of the target client for the target service, the method further comprises: In the case that the target client and the target service end are located in different domain controllers, the first agent end acquires a target address of the target service end and a target service capable of being provided by the target service end sent by a second agent end, wherein the second agent end and the target service end are located in the same domain controller, and the second agent end allocates a target address to the target service end in response to an online request of the target service end and sends the target address and the target service provided by the target service end to the first agent end.

5. The vehicle communication method according to claim 1, characterized by, The target client directly communicates with the target service end according to the target address, comprising: In the case that the target client and the target service end are located in different processes of the same domain controller, the target client writes structured data to be transmitted into a shared memory; The target service end reads the structured data from the shared memory.

6. The vehicle communication method according to claim 1, characterized by, The target client directly communicates with the target service end according to the target address, including: In the case that the target client and the target service end are located in the same domain controller and in the same process, the target client obtains an object pointer of the target service end from the first proxy end; The target client calls a function of the target service end based on the object pointer to communicate.

7. The vehicle communication method according to claim 1, characterized by, The target client directly communicates with the target service end according to the target address, including: In the case that the target client and the target service end are located in different domain controllers, the target client serializes structured data to be transmitted to generate a network transmission data packet; The target service end deserializes the received network transmission data packet to obtain the structured data.

8. A vehicle communication system characterized by comprising: The vehicle includes at least two domain controllers, each of which includes a proxy end, at least one service end and at least one client, the proxy end is communicatively connected with the at least one service end and the at least one client based on a preset communication protocol, the proxy ends of different domain controllers are communicatively connected based on the preset communication protocol, and the system includes an address transmission module and a data communication module. The address transmission module is configured to: in response to a service request of a target client to a target service, a first proxy end sends a target address of a target service end capable of providing the target service to the target client, and the first proxy end and the target client belong to the same domain controller. The data communication module is configured to: the target client directly communicates with the target service end according to the target address, wherein when the target client and the target service end belong to different domain controllers, the target client and the target service end adopt serialization and deserialization transmission strategies for data transmission; and when the target client and the target service end belong to the same domain controller, the target client and the target service end adopt serialization-free transmission strategies for data transmission.

9. An electronic device comprising: A memory and a processor, characterized in that the processor is used to execute the steps of the vehicle communication method of any one of claims 1-7 when the computer program stored in the memory is executed.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the vehicle communication method of any one of claims 1-7.

Images