CN118796504A - A middleware communication system, method, vehicle-mounted terminal and storage medium - Google Patents

Abstract

The present application proposes a middleware communication system, method, vehicle-mounted terminal and storage medium, wherein the middleware communication system includes a server layer, a client layer and a middleware communication interface layer; the server layer includes a server, and the client layer includes a client; the server and the client come from different systems, or different processes of the same system; the server layer establishes a connection with the client layer after passing through the middleware communication interface layer; the middleware communication interface layer is used for communication between different systems, and provides a unified communication interface for communication between different processes of the same system; the middleware communication interface layer includes: a communication middleware management unit, a first connection unit and a second connection unit; the server, the first connection unit, the communication middleware management unit, the second connection unit and the client establish connections in sequence. The present application greatly improves the communication efficiency and information transmission security by designing a unified communication interface layer to handle the communication between different systems or different processes of the same system.

Description

A middleware communication system, method, vehicle-mounted terminal and storage medium

Technical Field

The present application belongs to the technical field of middleware, and in particular, relates to a middleware communication system, method, vehicle-mounted terminal and storage medium.

Background Art

At present, data or signal transmission and communication between different processes in each vehicle can be summarized as inter-chip communication and IPC communication. Among them, inter-chip communication refers to the communication between various systems, such as the communication between the vehicle central control and TBOX, which is generally based on Ethernet; IPC communication refers to the communication between processes within the system, for example, there are many business processes that need to communicate within an operating system. However, although there are many ways and methods to achieve communication in the prior art, such as SomeIP, DDS, FDBUS, etc., the middleware interface is relatively complex, and there is no unified interface for "inter-chip communication" and "IPC communication". When developers receive new requirements, they often need to design a set of "inter-chip communication" and "IPC communication" libraries, or access existing communication libraries. Due to the complexity of traditional library interfaces, too many underlying details are exposed to developers, and "inter-chip communication" and "IPC communication" are not integrated into one, which makes the development and debugging costs high.

Summary of the invention

In response to the defects of the above-mentioned prior art, the present application provides a middleware communication system, method, vehicle-mounted terminal and storage medium. By designing a unified communication interface layer to handle the communication between different systems inside the vehicle, or between different processes in the same system, the communication efficiency and information transmission security are greatly improved, so that developers do not need to pay attention to the underlying communication details and can focus more on the development of upper-level logic.

To achieve the above-mentioned purpose, the present application provides a middleware communication system, including: any server layer and any client layer; wherein the server layer includes any number of servers for the service provider end, and the client layer includes any number of clients for the service requester end; wherein the server and the client are from different systems, or different processes of the same system.

The middleware communication system also includes:

Middleware communication interface layer; the server layer establishes a connection with the client layer after passing through the middleware communication interface layer; the middleware communication interface layer is used for communication between different systems, and provides a unified communication interface for communication between different processes in the same system.

Among them, the middleware communication interface layer at least includes: a communication middleware management unit, a first connection unit and a second connection unit; one end of the first connection unit is connected to the server, the other end of the first connection unit is connected to one end of the communication middleware management unit, the other end of the communication middleware management unit is connected to one end of the second connection unit, and the other end of the second connection unit is connected to the client.

In the present application, the communication middleware management unit includes:

The registration module is used to register preset service functions and generate interfaces that can be called by clients.

The calling module is used to match the connection interface between the server and the client according to the calling request output from the client.

The message publishing module is used to receive data information from the server and generate target information according to the data information.

The message subscription module is used to receive the target information and broadcast it to the client.

The abnormal monitoring module is used to monitor the connection status between the server and the client through preset rules and output abnormal instructions.

The exception handling module is used to enter the exception handling mode according to the corresponding preset mechanism when receiving the exception instruction.

And, an encryption setting module is used to set a preset encryption attribute for the target information before outputting the target information to the second connection unit.

In the present application, the first connection unit is used to synchronously start several of the server terminals, transmit the data information, and output the service request from the client to the server terminal; the second connection unit is used to synchronously start several of the client terminals, transmit the service request, and output the target information to the client terminal.

To achieve the above object, the present application also provides a method of a middleware communication system, the method comprising:

The middleware communication interface layer provides a unified communication interface for the server and the client according to preset rules; wherein the server and the client are from different systems, or different processes of the same system. The middleware communication interface layer at least includes a communication middleware management center.

Acquire the transmission status of communication information in the communication middleware management center; when the transmission status refers to the communication middleware management center receiving data information output by any server, output the target information to the client through the communication interface; when the transmission status refers to the communication middleware management center receiving a service request output by any client, transmit it to the server through the communication interface.

The preset rules are specifically:

The preset service function is registered through the data information output by the server to generate an interface that can be called by the client; according to the call request output from the client, the connection between the server and the client is matched to generate the communication interface.

To achieve the above objectives, the present application also provides a vehicle-mounted terminal, including multiple systems, each of which includes a number of processes; wherein the multiple systems and the processes communicate with each other based on any of the middleware communication methods described above.

To achieve the above objectives, the present application also provides a storage medium, which is a type of computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements any of the middleware communication methods described above.

Compared with the prior art, the present invention has the following beneficial effects:

The present application proposes a middleware communication system, method, vehicle-mounted terminal and storage medium. The present application realizes the communication between the server and the client between different systems in the vehicle or different processes in the same system by providing a unified middleware communication interface layer, which greatly simplifies the communication between different systems or processes, reduces the amount of specific code that developers must write, and thus improves development efficiency. In addition, the middleware communication system proposed in the present application hides the complexity of the underlying communication, so that developers do not have to deal with underlying details such as network programming, data serialization, error handling, etc., which helps developers focus on the upper-level logic without paying attention to the underlying communication details, thereby reducing the possibility of errors and debugging costs.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a framework of sources of a server layer and a client layer in one embodiment of the present application.

FIG. 2 is a schematic diagram of a framework of a middleware communication system in an embodiment of the present application.

FIG3 is a schematic diagram of a communication middleware management unit in an embodiment of the present application.

FIG. 4 is a flow chart of a middleware communication method in an embodiment of the present application.

DETAILED DESCRIPTION

In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme will be clearly and completely described below in conjunction with the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

Embodiment 1:

In order to solve the above technical problems, the present application provides a middleware communication system, which is designed to use a single and identical interface to handle communication, so that inter-chip communication and IPC communication interface are integrated into one to form a unified middleware communication interface layer, which is simpler than the communication library interface in the prior art and has lower development cost.

In this embodiment, as shown in FIG1, the middleware communication system includes: any server layer and any client layer; wherein the server layer includes any number of servers for service providers, and the client layer includes any number of clients for service requesters; wherein the servers and clients are from different systems, or different processes of the same system. The middleware communication system also includes:

Middleware communication interface layer; the server layer establishes a connection with the client layer after passing through the middleware communication interface layer; the middleware communication interface layer is used for communication between different systems, and provides a unified communication interface for communication between different processes in the same system.

In the communication process, any communication protocol may be used to implement data transmission, such as TCP protocol or Ethernet, etc., but are not limited thereto.

It should be noted that the server layer includes multiple servers, which can be applications, services or components that provide specific functions or services. These servers can be applications from different systems, such as a server running on the Windows operating system communicating with a server running on Linux. The servers can also be different processes in the same system, such as a server running in the main control process communicating with a server running in a subprocess, but are not limited to this.

The client layer contains multiple clients, which are applications, services or components that request services from the server. Similarly, clients can also be applications from different systems or different processes in the same system.

For example, clients in different systems: Suppose a vehicle has a Linux-based chassis domain controller that manages the vehicle's braking system, suspension system, and steering system. At the same time, there is a QNX-based powertrain domain controller that manages the engine, transmission, and electrical system of the vehicle. These two domain controllers act as servers and provide specific control and monitoring services. Clients from different systems, such as Android-based infotainment systems or Windows-based remote diagnostic tools, can request services provided by these servers, such as obtaining vehicle status information, performing diagnostic tests, etc.

Clients in different processes of the same system: In the body domain controller of a vehicle, there may be multiple processes running on the same microcontroller. For example, one process is responsible for monitoring the status of the doors and windows, while another process is responsible for monitoring the vehicle's lighting system. When the door status changes, the door monitoring process, as a client, requests the service provided by the body domain controller to update the door status information and pass it to the lighting monitoring process.

The middleware communication system of the present application provides a platform that makes service communication between different systems or different processes of the same system simpler, more efficient and scalable, while reducing the complexity of development and maintenance; and it provides the ability to provide service requests and data transmission across different systems and different processes within the same system. In this way, the integration and communication of domain controllers within the vehicle become more flexible and efficient.

As shown in FIG2, the middleware communication interface layer includes at least: a communication middleware management unit, a first connection unit and a second connection unit; one end of the first connection unit is connected to the server, the other end of the first connection unit is connected to one end of the communication middleware management unit, the other end of the communication middleware management unit is connected to one end of the second connection unit, and the other end of the second connection unit is connected to the client.

In this embodiment, the middleware communication interface layer is equivalent to a simplified communication library. Preferably, the communication middleware management unit can be managed uniformly through the IpcContext unit, and template functions can be used in the IpcContext unit, that is, in actual use, different types of data can be processed without modifying the code through template functions. Developers can create reusable communication logic that can be applied to different data types and communication modes. At the same time, template functions can ensure that the compatibility of data types is checked at compile time, reducing runtime errors.

If you need to support new data types or communication modes, you only need to add new template function implementations in the IpcContext unit without having to modify the code repeatedly. In addition, the template function provides a higher level of abstraction, allowing developers to focus on business logic rather than underlying communication details.

Further, as shown in FIG. 3, the communication middleware management unit includes:

The registration module is used to register preset service functions and generate interfaces that can be called by clients.

Preferably, the registration module may include funcName (function name), f (function entity) and optional nodeName (service name), but are not limited thereto.

Among them, the function entity f is a template parameter, so this embodiment can register any type of function without providing a specific registration method for each function type.

The IpcContext unit is responsible for storing registered service functions and related information, such as function name, function pointer, service name, etc. It is also responsible for processing client call requests, finding the corresponding function entity according to the function name, and executing it.

For example, when a developer registers a service function, the IpcContext unit records the detailed information of the function and stores the function pointer. If a service name is provided, the function will be bound to the specified service name.

When a client calls a service through an instruction, it passes the function name and parameters. The IpcContext unit finds the corresponding function entity according to the function name, executes it, and returns the result to the client.

The registration module of this embodiment can register any type of function, and there is no need to provide a specific registration method for each function type. This simplifies the development process, and developers no longer need to write different registration codes for different function types.

In other embodiments, developers can register multiple service functions in one process, and these functions can be managed uniformly through the IpcContext unit. This management method makes the registration, search and execution of service functions more efficient and centralized. In addition, when calling a service, the client only needs to know the function name and parameters, and does not need to care about the specific implementation location of the function. This simplifies the client code and makes the client call more intuitive and easy to understand.

The calling module is used to match the connection interface between the server and the client according to the calling request output from the client.

It should be noted that when the client sends a call request, the call module will parse the request and extract the function name and parameters. Based on the function name, the call module will search for the service function registered on the server. If a matching service function is found, the call module will build a call context and pass the parameters to the service function. Finally, the call module will process the return value of the service function and return it to the client.

In this embodiment, the client can conveniently call the server's functions through the calling module without knowing the specific implementation details of the server. The calling module provides an abstract layer that hides the complexity of the server's implementation, making the client call simpler and more unified.

The message publishing module is used to receive data information from the server and generate target information according to the data information.

It should be noted that when the server generates data information, the information will be processed by the message publishing module. The message publishing module will generate target information based on the data information. The process may also include data format conversion, filtering, etc., which are not limited to this. Then, the message publishing module will send the target information to the message subscription module.

In this embodiment, the server can flexibly publish data information without worrying about how to pass it to the client. The message publishing module ensures that the data information has undergone necessary processing before being published, thereby improving the reliability and consistency of the data.

The message subscription module is used to receive the target information and broadcast it to the client.

It should be noted that the message subscription module will listen to the target information from the message publishing module. When receiving the target information, the message subscription module will broadcast this information to all subscribed clients. Clients can receive the data of interest by subscribing to specific message types.

In this embodiment, the client can dynamically subscribe to the message type it is interested in without knowing the specific content of the message. The message subscription module implements a message broadcast mechanism, so that data can be efficiently distributed to all subscribed clients.

The abnormal monitoring module is used to monitor the connection status between the server and the client through preset rules and output abnormal instructions.

It should be noted that the abnormal monitoring module will monitor the connection status between the server and the client according to the preset rules. If an abnormality is detected, the abnormal monitoring module will output an abnormal instruction to notify other modules to take corresponding measures.

Preferably, the preset rule may adopt a heartbeat mechanism or a disconnection reconnection mechanism to detect whether the connection is normal, but is not limited thereto.

In this embodiment, the abnormal monitoring module can timely discover and report potential problems in the system, improving the robustness and stability of the system. Through preset rules, the abnormal monitoring module can automatically respond to various abnormal situations, reducing the need for manual intervention.

The exception handling module is used to enter the exception handling mode according to the corresponding preset mechanism when receiving the exception instruction.

It should be noted that when an exception instruction is received, the exception handling module will enter the exception handling mode according to a preset mechanism. In the exception handling mode, the exception handling module will take a series of measures to restore the system state or notify the user.

Preferably, by setting a callback function when the client and server are disconnected, the application can respond in time when the network connection is disconnected and take corresponding exception handling measures.

This exception handling mode can uniformly manage the disconnection callback functions of all clients and servers. This means that the disconnection callback functions of both the client and the server can be set and managed through a unified interface.

When the session connection is disconnected, the corresponding callback function will be called immediately, and the application layer can quickly know the disconnection event so that timely countermeasures can be taken. After the abnormal event is triggered, the corresponding callback function is called according to the previously set callback function and node name. The callback function can execute any application-specific logic, such as notifying the user, recording logs, and trying to reconnect.

Furthermore, in the callback function, the application can try to restore the connection, such as sending a reconnection request or restarting the service. If the connection restoration fails, the application can redirect to an alternative service or take other fault-tolerant measures.

In this embodiment, the exception handling module provides an automated mechanism to deal with system exceptions, reducing the impact of failures on the system. Through the preset mechanism, the exception handling module can quickly respond to and handle various abnormal situations, improving the reliability of the system.

And, an encryption setting module is used to set a preset encryption attribute for the target information before outputting the target information to the second connection unit.

It should be noted that before the target information is transmitted to the client, the encryption setting module will set a preset encryption attribute for the target information, which may include encrypting the data, setting an encryption key or encryption algorithm, etc., but are not limited thereto.

In this embodiment, the encryption setting module ensures the security and privacy of data during transmission, preventing data from being intercepted or tampered by unauthorized third parties. Through encryption, the encryption setting module enhances the security of the system and protects sensitive data from being leaked.

In the present application, the first connection unit is used to synchronously start several of the server terminals, transmit the data information, and output the service request from the client to the server terminal; the second connection unit is used to synchronously start several of the client terminals, transmit the service request, and output the target information to the client terminal.

It should be noted that the first connection unit is firstly responsible for starting multiple servers.

It can ensure that all servers are started synchronously when the system starts up through any startup script or program. When the server needs to exchange data with the client or other servers, the first connection unit is responsible for passing the data information to the corresponding target. Preferably, it can also use some message queue, shared memory or other communication mechanism to achieve this.

When the client sends a service request, the first connection unit receives the request and passes it to the appropriate server, and then determines to which server the request is sent through the load balancing mechanism.

In this embodiment, the servers can be started synchronously to ensure that all servers are ready when the system is started.

The first connection unit provides data transmission and request transmission between the servers, making the communication between the servers more efficient and reliable. Through the load balancing mechanism, the first connection unit can optimize the utilization of the servers and avoid overloading of some servers.

Furthermore, the second connection unit is responsible for starting multiple clients, and it can also ensure that all clients are started synchronously when the system starts through any startup script or program. When the server needs to pass data or responses to the client, the second connection unit is responsible for receiving this information and passing it to the client. After the server processes the client's request, it will generate target information. The second connection unit outputs this target information to the client.

The second connection unit provides data transmission and service request transmission between clients, making communication between clients more efficient and reliable. Through the second connection unit, the server can quickly transmit the processing results to the client, improving the client's response speed and user experience.

It should be noted that the first and second connection units are uniformly managed by the IpcContext unit, and the upper-level logic does not need to manage these services additionally. Preferably, a hash table can be used to store all current server nodes in the unit, thereby improving the overall performance of the system and user experience through efficient transmission of data and service requests.

In summary, the middleware communication system in the embodiment of the present application is uniformly managed and processed through the IpcContext unit, making client calls simpler and more efficient. Its design implements an efficient, secure, flexible and reliable communication mechanism, improves the maintainability and scalability of the system, and also provides developers with greater control and flexibility.

Embodiment 2:

As shown in FIG. 4 , in order to solve the above technical problem, the present application also proposes a method of a middleware communication system, the method comprising:

The middleware communication interface layer provides a unified communication interface for the server and the client according to preset rules; wherein the server and the client are from different systems, or different processes of the same system. The middleware communication interface layer at least includes a communication middleware management center.

It should be noted that the method of this embodiment provides a set of unified communication interfaces for the server and the client by providing a middleware communication interface layer. This set of interfaces defines the standard format and method for data exchange between the server and the client. The communication middleware management center is part of the middleware communication interface layer, which is responsible for managing and coordinating the communication between the server and the client. The management center maintains the transmission status of a communication information and records the flow of data information and service requests.

Furthermore, the transmission status of the communication information in the communication middleware management center is obtained; when the transmission status refers to the communication middleware management center receiving data information output by any server, the target information is output to the client through the communication interface; when the transmission status refers to the communication middleware management center receiving a service request output by any client, it is transmitted to the server through the communication interface.

It should be noted that when the server outputs data information, the communication middleware management center receives the information. The management center processes the data information according to preset rules and converts it into target information. Then, the target information is output to the client through the communication interface.

When the client outputs service requests, the communication middleware management center receives these requests. The management center processes these requests according to preset rules and converts them into a form that the server can understand. Then, the service requests are passed to the server through the communication interface.

Preferably, the transmission status of the communication information can be obtained by monitoring and tracking the data of the middleware system. For example, the communication middleware management center can set a state machine to track the status of the data packet or message. The state machine can record each stage of the data from sending to receiving, such as creation, sending, receiving, processing, etc. By querying the state machine, the current communication status can be obtained.

The communication middleware can also obtain the required information transmission status from the detailed log information, including the sending and receiving time of the message, the sending and receiving nodes, the message ID, the status change, etc. By analyzing the log file, the current status of the communication middleware management center can be understood, which is not limited to this.

The preset rules are specifically:

The preset service function is registered through the data information output by the server to generate an interface that can be called by the client; according to the call request output from the client, the connection between the server and the client is matched to generate the communication interface.

It should be noted that the preset rules involve registering a preset service function with the data information output by the server, and matching the connection between the server and the client according to the call request of the client to generate a communication interface.

The data information output by the server must first be registered in a preset service function. This service function can be pre-defined or dynamically generated based on the data information output by the server. The registration process can be to map the data information to a function or method so that the data information can be processed by the function or method later.

By registering a preset service function, you can generate a callable interface for the client. This interface can be an API, Web service, or other form of interface, which defines how the client calls the server's functions. The generated interface needs to ensure that the client can access the server's functions safely and efficiently through the interface.

When the client initiates a call request, the communication interface is responsible for matching these requests to the corresponding server. The matching process can involve load balancing, service discovery, or matching directly based on the request content. Through matching, the communication interface ensures that the client's request can be correctly routed to the server.

Based on the matching results, the communication interface will generate a specific communication path for data exchange between the client and the server. This communication interface defines the format, protocol, security measures, etc. of data transmission to ensure the security and reliability of the communication process.

In this embodiment, by registering the preset service function, the function of the server is abstracted, so that the client does not need to care about the specific implementation details of the server. This simplifies the client development process, and the client developer can focus more on the business logic. In addition, the generated client call interface provides a flexible service access method, and the client can call different server functions as needed. This flexibility also makes the system easier to expand and maintain.

In summary, the middleware communication method in Example 2 provides a unified communication interface so that the server and the client can communicate across systems or processes, regardless of the operating system or process environment they are running in. Through preset rules, the data information output by the server is registered in the preset service function to generate an interface that can be called by the client. This service registration and discovery mechanism simplifies the client's access to the server function. The middleware communication method can match the connection between the server and the client according to the client's call request to generate a communication interface. This request matching and routing mechanism ensures that the client's request can be efficiently and accurately routed to the correct server. The specific implementation process and principle have been introduced in detail in Example 1 and will not be repeated in this embodiment.

Embodiment three:

The present application also provides a vehicle-mounted terminal, including multiple systems, each of which includes a number of processes; wherein the multiple systems and the processes communicate with each other based on any of the middleware communication methods described above.

It should be noted that a vehicle terminal in this embodiment can be divided into multiple systems, each system is responsible for different functions, such as navigation system, entertainment system, security system, etc. Each system contains several processes, and the process is responsible for executing specific tasks of the system.

Integrate any of the above middleware communication methods in the vehicle terminal, which includes providing a unified communication interface for each system, and realizing functions such as service registration, request matching, and communication status management.

The communication between systems and processes is based on the middleware communication method. Through the communication interface, data can be exchanged between systems and service requests can be transmitted between processes.

Data can be shared between systems, such as a navigation system can provide location information to an entertainment system so that relevant information can be displayed during navigation. Control commands can be passed between processes, such as a process in a security system can send a security warning to a process in an entertainment system to adjust the displayed content.

The abnormality monitoring and processing mechanism in the middleware communication method can be applied to the vehicle terminal to ensure that the system can automatically respond and recover when encountering abnormal situations.

The encryption setting module can protect the security of the vehicle terminal when transmitting sensitive data, such as user personal information, vehicle status, etc.

Preferably, in a modern vehicle terminal, multiple systems can communicate with each other through middleware communication methods. The navigation system provides location information and route planning services. It can share location data with other systems through middleware communication methods, such as the entertainment system can display information about nearby restaurants or attractions; the entertainment system is responsible for providing entertainment content such as music and videos. It can receive location information from the navigation system through the middleware communication method to provide relevant entertainment content during navigation.

The safety system is responsible for monitoring the safety status of the vehicle, such as collision warning, lane departure warning, etc. It can send safety warnings to other systems through middleware communication methods, such as the entertainment system can pause the content to improve the driver's attention.

Multiple systems and processes in the vehicle terminal can exchange data and work together efficiently, improving the overall performance of the system and user experience. Based on the middleware communication method, the design of the vehicle terminal has high flexibility and scalability, and new systems or processes can be easily added without large-scale modifications to the existing system. The security mechanism in the middleware communication method ensures the security of data during transmission, protecting user privacy and the security of the vehicle terminal.

Through the middleware communication method, the vehicle terminal can efficiently process and transmit large amounts of data, such as high-definition map data, multimedia content, etc. The unified interface and modular design of the middleware communication method simplify the maintenance and upgrade process of the vehicle terminal and reduce maintenance costs.

In summary, multiple systems and processes of the vehicle terminal can communicate efficiently and securely based on the middleware communication method, providing users with an integrated and intelligent driving experience.

Embodiment 4:

The present application also provides a storage medium, which is a type of computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements any of the middleware communication methods described above.

Preferably, a computer-readable storage medium, such as a hard disk drive (HDD), a solid state drive (SSD), a flash memory card, an optical disk, etc., stores computer program codes for implementing the middleware communication method on the storage medium.

This embodiment implements various functions in the middleware communication method, such as service registration, request matching, communication interface generation, state management, etc., by writing a computer program to ensure that the program code complies with the corresponding programming language and development standards. Among them, the written program code is compiled to generate an executable file. The compiled executable file and necessary library files are deployed to a storage medium. The storage medium device is connected to the computer system where the processor is located. The processor reads the executable file on the storage medium and executes the program code.

In this embodiment, when the processor executes the computer program, the function of the middleware communication method is realized. The program is executed by the processor and interacts with the hardware and software of the vehicle terminal or other systems to realize the communication process.

By executing the program on the storage medium, data is transmitted between the server and the client, ensuring that data can be exchanged between systems efficiently and securely. The program implements service registration and discovery functions, so that the server's functions can be accessed by the client without having to worry about the specific implementation details of the server. The program implements request matching and routing functions, ensuring that client requests can be efficiently and accurately routed to the correct server.

Preferably, the program can implement the communication status management function, monitor and manage the communication process, and ensure the transparency and controllability of the communication process. The program can implement the encryption setting module to protect the security and reliability of data during transmission. The program can implement the registration of service functions, so that the system can flexibly add new services and has high scalability. The program can also implement the abnormal monitoring and processing functions to improve the robustness and stability of the system.

In summary, the computer program on the storage medium of this embodiment realizes an efficient, secure, flexible and reliable communication mechanism through execution, which helps to build a stable, easy-to-use and secure distributed system.

The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The memory is used to store an operating system, an application program, a boot loader, data, and other programs, such as the program code of the computer program, etc. The memory may also be used to temporarily store data that has been output or is to be output.

In several embodiments provided in the present application, it is understood that each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved.

If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

The specific embodiments described above further describe the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above description is only a specific embodiment of the present application and is not intended to limit the scope of protection of the present application. It is particularly pointed out that for those skilled in the art, any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims (10)

1. A middleware communication system, comprising: any service layer and any client layer; wherein the service end layer comprises any number of service ends for service providing ends, the client layer comprises any number of clients for servicing the request end; it is characterized in that the method comprises the steps of,

The server and the client are respectively from different systems or different processes of the same system; the middleware communication system further includes:

A middleware communication interface layer; the server layer establishes connection with the client layer after passing through the middleware communication interface layer; the middleware communication interface layer is used for communication between different systems and communication between different processes of the same system to provide a unified communication interface;

The middleware communication interface layer at least comprises: the communication middleware management unit, the first connection unit and the second connection unit; one end of the first connecting unit is connected with the service end, the other end of the first connecting unit is connected with one end of the communication middleware management unit, the other end of the communication middleware management unit is connected with one end of the second connecting unit, and the other end of the second connecting unit is connected with the client.

2. The middleware communication system according to claim 1, wherein said communication middleware management unit comprises:

The registration module is used for registering a preset service function and generating an interface which can be called by the client;

And the calling module is used for matching the connection interface between the server and the client according to the calling request output from the client.

3. The middleware communication system according to claim 2, wherein said communication middleware management unit further comprises:

The message publishing module is used for receiving the data information from the server and generating target information according to the data information;

and the message subscription module is used for receiving the target information and broadcasting and transmitting the target information to the client.

4. A middleware communication system according to claim 3 wherein said communication middleware management unit further comprises:

The abnormality monitoring module is used for monitoring the connection state between the server and the client through a preset rule and outputting an abnormality instruction; and the exception handling module is used for entering an exception handling mode according to a corresponding preset mechanism when the exception instruction is received.

5. The middleware communication system of claim 4, wherein the communication middleware management unit further comprises:

And the encryption setting module is used for setting preset encryption attributes for the target information before outputting the target information to the second connection unit.

6. A middleware communication system in accordance with claim 5, wherein,

The first connection unit is used for synchronously starting a plurality of service ends, transmitting the data information and outputting a service request from a client to the service ends;

the second connection unit is used for synchronously starting a plurality of clients, transmitting the service request and outputting the target information to the clients.

7. A method of a middleware communication system according to any of claims 1-6, comprising:

Providing a unified communication interface for the server and the client according to a preset rule through the middleware communication interface layer; the server and the client are respectively from different systems or different processes of the same system; the middleware communication interface layer at least comprises a communication middleware management center;

acquiring a transmission state of communication information in a communication middleware management center;

When the transfer state refers to the data information output by any server is received by the communication middleware management center, outputting target information to the client through the communication interface;

and when the transfer state refers to that the communication middleware management center receives a service request output by any client, the service request is transferred to the server through the communication interface.

8. The middleware communication method according to claim 7, wherein the preset rule is specifically: registering a preset service function through the data information output by the service end to generate an interface which can be called by the client;

and according to the call request output from the client, matching the connection between the server and the client to generate the communication interface.

9. The vehicle-mounted terminal is characterized by comprising a plurality of systems, wherein a plurality of processes are included in the systems; wherein the plurality of systems, and the process communicate based on the middleware communication method of any one of claims 7 to 8.

10. A storage medium, being one of computer readable storage media, having stored thereon a computer program which, when executed by a processor, implements the middleware communication method according to any of claims 7-8.