Method for isolating received and transmitted data

Abstract

The invention provides a method for isolating transceiving data, which comprises the following steps: a gateway system in a host routes target data to a gateway instance corresponding to a current interface type according to the current interface type corresponding to the target data in a shared memory, and then the gateway instance sends the target data to a gateway instance corresponding to the current interface type in other data. The gateway instances in other hosts write the target data into the shared memories of other hosts, the application can read the target data from the shared memories, data transmission of the application between different hosts is achieved, and the method is suitable for applications of various interface types to send data to the applications in other hosts. Isolation of data of different interface types is achieved, normal operation of other interfaces cannot be affected by faults of one interface, the overall reliability of the system is improved, zero-copy communication is achieved, memory bandwidth consumption and CPU loads are greatly reduced, the data transmission efficiency is improved, and efficient cross-interface communication is achieved.

Description

Technical Field

[0001] The present application relates to the technical field of data transmission, and in particular to a method for isolating data transmission and reception. Background Art

[0002] In modern distributed systems, data exchange between different communication protocols and interface types is often required. Especially in high-performance systems that require zero-copy communication, such as autonomous driving, robotics, and industrial automation, a gateway mechanism is needed that can efficiently process data of different interface types.

[0003] Current communication methods have the following main problems: 1. Protocol diversity and integration difficulties: The system needs to support multiple protocols such as DDS, SOMEIP, CAN and Ethernet, each with different characteristics; 2. Performance bottleneck: Traditional communication methods involve multiple data replications, resulting in increased latency and waste of resources, especially when processing large data structures; 3. Limitations of a single gateway architecture: Mixed processing of data from different interface types increases complexity; 4. Resource competition leads to performance degradation; 5. Insufficient fault isolation: a single fault may affect the entire system. Summary of the Invention

[0004] In view of the above-mentioned defects or deficiencies in the prior art, the present application aims to provide a method for isolating transmitted and received data to solve the problems in the related technology such as protocol diversity and integration difficulties, data transmission delays, resource waste, high complexity of data processing of different interface types, and failures affecting the system.

[0005] An embodiment of the present application provides a method for isolating data transmission and reception, which is applied to each host, wherein the host includes each application and a gateway system, wherein the gateway system includes a shared memory and a gateway instance corresponding to each interface type. The method includes:

[0006] The gateway system routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory, wherein the target data is the data to be transmitted written by the application in the host where the gateway system is located;

[0007] The gateway instance sends the target data to the gateway instance corresponding to the current interface type in the other host, so that the gateway instance corresponding to the current interface type in the other host writes the target data into the shared memory of the other host, wherein the application in the other host reads the target data from the shared memory.

[0008] Optionally, gateway instances of the same interface type between different hosts are connected through a network corresponding to the interface type, and the gateway instance sends the target data to the gateway instance corresponding to the current interface type in the other host, including:

[0009] The gateway instance converts the target data into a format according to a transmission format of a network corresponding to the current interface type;

[0010] The gateway instance sends the target data after format conversion to the network corresponding to the current interface type, so that the gateway instance corresponding to the current interface type in other hosts obtains the target data from the network.

[0011] Optionally, the gateway system routes the target data to a corresponding gateway instance according to a current interface type corresponding to the target data in the shared memory, including:

[0012] The gateway system calls the discovery thread according to a preset discovery cycle, so that the discovery thread routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory;

[0013] The gateway instance sends the target data to a gateway instance corresponding to the current interface type in another host, including:

[0014] The gateway system calls a forwarding thread according to a preset forwarding period, so that the forwarding thread controls the gateway instance and sends the target data to the gateway instance corresponding to the current interface type in other hosts.

[0015] Optionally, the gateway instance includes an inbound gateway and an outbound gateway, and the gateway instance sends the target data to a gateway instance corresponding to the current interface type in another host, so that the gateway instance corresponding to the current interface type in the other host writes the target data into a shared memory of the other host, including:

[0016] The outbound gateway in the gateway instance sends the target data to the inbound gateway corresponding to the current interface type in the other host, so that the inbound gateway in the other host writes the target data into the shared memory of the other host.

[0017] Optionally, the shared memory is composed of dedicated memory areas for each interface type; before the gateway system routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory, the system further includes:

[0018] The application in the host where the gateway system is located writes the target data into a dedicated memory area of ​​the current interface type in the host;

[0019] The gateway system routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory, including:

[0020] The gateway system routes the target data to the corresponding gateway instance through the channel corresponding to the dedicated memory area of ​​the current interface type.

[0021] Optionally, determining a dedicated memory area for each interface type includes:

[0022] The gateway system obtains each interface type and the transmission data attribute corresponding to each interface type;

[0023] The gateway system divides the shared memory of the host into dedicated memory areas for each interface type according to the transmission data attributes corresponding to each interface type.

[0024] Optionally, creating a channel corresponding to the dedicated memory area includes:

[0025] The gateway system creates a gateway instance in response to a gateway creation request sent by an application on the host, and binds the gateway instance to a corresponding interface type;

[0026] The gateway system verifies the type of the gateway instance based on the interface type bound to the gateway instance in response to the channel creation request sent by the application of the host;

[0027] If the verification is successful, the gateway system creates a channel corresponding to the gateway instance and binds the channel to the dedicated memory area.

[0028] Optionally, the application in the host where the gateway system is located writes the target data into a dedicated memory area of ​​the current interface type in the host, including:

[0029] An application in the host where the gateway system is located determines a current security level of the target data, and determines a target sub-area in the dedicated memory area of ​​the current interface type according to the current security level;

[0030] The application in the host where the gateway system is located writes the target data into the target sub-area.

[0031] The present application also provides a method for isolating data transmission and reception, which is applied to each host, wherein the host includes each application and a gateway system, wherein the gateway system includes a shared memory and a gateway instance corresponding to each interface type. The method includes:

[0032] In response to receiving target data sent by gateway instances of the same interface type in other hosts, the gateway instance writes the target data into the shared memory of the host, so that an application of the host reads the target data from the shared memory.

[0033] Optionally, before the gateway instance writes the target data into the shared memory of the host, the method further includes:

[0034] The gateway instance performs at least one of data verification processing, authorization verification processing, encryption conversion processing, identity authentication processing and data filtering processing on the target data according to the security level of the corresponding interface type.

[0035] An embodiment of the present application further provides an electronic device, comprising:

[0036] processor and memory;

[0037] The processor is used to execute the steps of the method for isolating the sending and receiving of data provided in any embodiment of the present application by calling the program or instructions stored in the memory.

[0038] An embodiment of the present application also provides a computer-readable storage medium, which stores a program or instruction, and the program or instruction enables a computer to execute the steps of the method for isolating the sending and receiving of data provided in any embodiment of the present application.

[0039] In summary, the present application proposes a method for isolating data transmission and reception. The gateway system in the host routes the target data to the gateway instance corresponding to the current interface type according to the current interface type corresponding to the target data in the shared memory, and then the gateway instance sends the target data to the gateway instance corresponding to the current interface type in other data, so that the gateway instance in the other host writes the target data into the shared memory of the other host. The application can read the target data from the shared memory to realize data transmission between applications of different hosts. It is suitable for applications of various interface types to send data to applications in other hosts. The method performs data transmission through gateway instances of various interface types between different hosts, and can realize the isolation of data of different interface types. The failure of one interface will not affect the normal operation of other interfaces, thereby improving the overall reliability of the system. Moreover, the method realizes zero-copy communication through shared memory. Data only needs to be written once, and there is no need to copy data, which greatly reduces memory bandwidth consumption and CPU load, and improves data transmission efficiency, thereby realizing efficient cross-interface communication. In addition, the system has good scalability and can support dynamic addition of new interface types or removal of no longer required interface types. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the specific implementation methods of the present application or the technical solutions in the prior art, the following is a brief introduction to the drawings required for use in the specific implementation methods or the description of the prior art. Obviously, the drawings described below are some implementation methods of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0041] Figure 1 This is a schematic diagram of a gateway instance deployed in a gateway system provided by an embodiment of the present application;

[0042] Figure 2 This is a flow chart of a method for isolating sent and received data provided by an embodiment of the present application;

[0043] Figure 3 This is a diagram of a multi-host gateway system deployment architecture provided by an embodiment of the present application;

[0044] Figure 4 This is a memory pool allocation diagram provided by an embodiment of the present application;

[0045] Figure 5 This is a memory matching flow chart of a gateway instance provided in an embodiment of the present application;

[0046] Figure 6 This is an isolation architecture diagram of a gateway system provided in an embodiment of the present application;

[0047] Figure 7 This is a diagram of a data transmission and reception process provided by an embodiment of the present application;

[0048] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The present application will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely for the purpose of explaining the relevant invention and are not intended to limit the invention. It should also be noted that, for ease of description, only portions relevant to the invention are shown in the accompanying drawings.

[0050] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0051] As mentioned in the background technology, in response to the problems in the existing technology, this application proposes a method for isolating data transmission and reception. The method is applied to each host. The host includes various applications and a gateway system. The gateway system includes shared memory and gateway instances corresponding to each interface type.

[0052] Specifically, each host can deploy a gateway system. This gateway system uses an architecture designed based on interface type isolation, separating the logical processing of different communication protocols into different gateway instances to achieve efficient and flexible cross-interface communication. The gateway system consists of gateway instances for each interface type and a shared memory.

[0053] The core of the gateway (ESRGatewayGeneric) system is the ESRGatewayGeneric base class, which provides unified basic functionality for gateway instances of various specific interface types. It also implements strict interface type differentiation through the Interfaces enumeration. The base class simply defines an interface. Different gateway types inherit from this unified interface and then implement their code. This ensures that the interface name is consistent at the upper level, while downstream, different implementations are called based on the interface type.

[0054] When created, each gateway instance is bound to a specific interface type, such as DDS (Data Distribution Service), SOMEIP (Scalable service-oriented MiddlewarE over IP), CAN (Controller Area Network), or Ethernet, and only processes data streams that match the interface type.

[0055] Figure 1 This is a schematic diagram of a gateway system deployment gateway instance provided by an embodiment of the present application, such as Figure 1 As shown, the gateway system can enumerate all interface types, including Data Distribution Service (DDS), Scalable Service-Oriented Middleware over IP (SOMEIP), Controller Area Network (CAN), Ethernet, Process Field Network (PROFINET), Ethernet for Control Automation Technology (ETHERCAT), custom interfaces, and internal interfaces. Furthermore, the gateway system can create individual gateway instances and bind them to corresponding interface types, such as the ESR2DDS gateway, DDS2ESR gateway, ESR2SOMEIP gateway, SOMEIP2ESR gateway, ESR2CAN gateway, CAN2ESR gateway, ESR2Ethernet gateway, and Ethernet2ESR gateway shown in the figure. This architectural design allows the gateway system to optimize for the characteristics of each interface type while ensuring the consistency and scalability of the overall architecture.

[0056] Figure 2This is a flowchart of a method for isolating the sending and receiving of data provided in an embodiment of the present application. The method is applicable to fields such as autonomous driving systems (processing communications between control domains), robotic systems (processing internal and external communications of robots), distributed computing (cross-node, cross-protocol data exchange), and industrial automation (integration of industrial equipment with different protocols). Taking the field of autonomous driving systems as an example, vehicles need to simultaneously process data from multiple sensors (lidar, millimeter-wave radar, cameras, etc.), which usually use different communication interfaces (CAN, Ethernet, SOMEIP, etc.). Therefore, the method for isolating the sending and receiving of data provided in an embodiment of the present application can be used to realize data sending and receiving between different control domains (i.e., different hosts).

[0057] See also Figure 2 , the method for isolating the sending and receiving of data specifically includes:

[0058] S110 : The gateway system routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory.

[0059] The target data is the data to be transmitted written by the application on the host where the gateway system is located. The application on the host can communicate with the gateway instance on the host through shared memory.

[0060] Specifically, the application can first write the data to be transmitted into the shared memory of the host. In the process of writing the target data, the application can also write the current interface type corresponding to the target data and use the current interface type as the metadata of the target data. This metadata is used to indicate the interface type of the gateway instance of the processed target data.

[0061] After the target data is written into the shared memory, the gateway system may further route the target data to the gateway instance corresponding to the current interface type according to the current interface type corresponding to the target data, so as to forward the target data through the gateway instance of the current interface type.

[0062] Among them, each gateway instance is dedicated to processing a single type of data. For example, the DDS gateway instance only processes data with the DDS interface type tag, and the SOMEIP gateway instance only processes data with the SOMEIP interface type tag. This specificity allows the gateway system to be optimized for the characteristics of a specific interface type.

[0063] S120: The gateway instance sends the target data to the gateway instance corresponding to the current interface type in the other host, so that the gateway instance corresponding to the current interface type in the other host writes the target data into the shared memory of the other host.

[0064] Specifically, after the gateway system routes the target data to the gateway instance of the corresponding interface type, the gateway instance can send the target data to the gateway instance corresponding to the current interface type in other hosts, so that the gateway instance in the other hosts writes the target data into the shared memory of the other hosts, and then the application in the other hosts reads the target data from the shared memory.

[0065] When target data arrives at a gateway instance of the same interface type on another host, the gateway instance can write the target data to the host's shared memory based on the current interface type, while also attaching the corresponding interface type tag. Furthermore, when reading shared memory, the application can receive data that matches the interface type of interest based on the interface type filter, thereby achieving the purpose of reading the target data from shared memory. This entire process ensures the full type security and isolation of data from source to destination, while also achieving efficient zero-copy communication through the design of shared memory and gateway interfaces.

[0066] Each gateway instance may include an inbound gateway and an outbound gateway; gateway instances of the same interface type between different hosts are connected through their own dedicated networks to form a communication network matrix separated by interface type.

[0067] For example, Figure 3 This is a multi-host gateway system deployment architecture diagram provided by an embodiment of the present application, such as Figure 3 As shown, the ESR2DDS gateway on host A (i.e., the outbound gateway in the gateway instance corresponding to the DDS interface type) is connected to the DDS2ESR gateway on host B (i.e., the inbound gateway in the gateway instance corresponding to the DDS interface type) through the DDS network. Similarly, the ESR2SOMEIP gateway on host A is connected to the SOMEIP2ESR gateway on host B through the SOMEIP network, and the ESR2CAN gateway on host A is connected to the CAN2ESR gateway on host B through the CAN bus.

[0068] In an embodiment of the present application, the gateway instance can send target data to gateway instances of the same interface type on other hosts through the network corresponding to the current interface type.

[0069] In a specific embodiment, gateway instances of the same interface type between different hosts are connected through a network corresponding to the interface type, and the gateway instance sends target data to the gateway instance corresponding to the current interface type in the other host, including:

[0070] The gateway instance converts the target data into a format according to the transmission format of the network corresponding to the current interface type; the gateway instance sends the converted target data to the network corresponding to the current interface type, so that the gateway instance corresponding to the current interface type in other hosts can obtain the target data from the network.

[0071] The gateway instance can determine the transmission format of the target data according to the network corresponding to the current interface type, and then convert the target data according to the transmission format, such as converting from ESR (Ethernet Switch Router) to DDS protocol.

[0072] Furthermore, the gateway instance sends the target data after format conversion to the network corresponding to the current interface type, and then the target data can reach the gateway instance in other hosts connected to the gateway instance through the network.

[0073] It should be noted that when the target data reaches the gateway instance in other hosts connected to the gateway instance, the other gateway instance can convert the format of the target data, such as from the DDS protocol to the ESR protocol, and then write the format-converted target data into the shared memory.

[0074] Through the above implementation, corresponding network connections can be set up for gateway instances between different hosts, and data can then be transmitted through the corresponding network to gateway instances with the same interface type in other hosts. This architecture can achieve cross-host interface isolation, ensuring the independence and security of data from different protocols during network transmission, while maintaining the modularity and scalability of the system. Through this design, the gateway system can maintain efficient data exchange and strict interface isolation even in complex distributed environments, providing a unified and flexible solution for cross-host and cross-protocol communication.

[0075] In an embodiment of the present application, a gateway instance may be composed of an inbound gateway and an outbound gateway, and the outbound gateway of the gateway instance is connected to the inbound gateway of the gateway instance of the same interface type in other hosts (through the corresponding network).

[0076] In some embodiments, the gateway instance includes an inbound gateway and an outbound gateway, and the gateway instance sends target data to a gateway instance corresponding to a current interface type in another host, so that the gateway instance corresponding to the current interface type in the other host writes the target data into a shared memory of the other host, including:

[0077] The outbound gateway in the gateway instance sends the target data to the inbound gateway corresponding to the current interface type in the other host, so that the inbound gateway in the other host writes the target data into the shared memory of the other host.

[0078] Among them, the outbound gateway in the gateway instance can send the target data to the inbound gateway corresponding to the current interface type in other hosts through the network of the corresponding interface type, and then the inbound gateway can write the target data into the shared memory of the host where it is located.

[0079] For example, Figure 3 As shown, Host A and Host B each run multiple applications. These applications communicate with the gateway instances on their respective hosts through local shared memory. Each interface type (DDS, SOMEIP, CAN) has a corresponding outbound gateway (ESR2XXX gateway) and inbound gateway (XXX2ESR gateway), responsible for handling data conversion and transmission for the specific protocol. The corresponding gateways on different hosts are connected to each other through their own dedicated networks.

[0080] ESR application 1 or ESR application 2 on host A can write the data to be transmitted into the shared memory of host A, and then the gateway system will route the target data in the shared memory to the gateway instances of the corresponding interface types. Then, the outbound gateways of each interface type on host A can send the data to the inbound gateway on host B through the corresponding network. Then, the inbound gateway can write the data into the shared memory of host B. ESR application 3 or ESR application 4 on host B can obtain the data transmitted by the application on host A from the shared memory.

[0081] Through the above implementation, cross-host interface isolation can be achieved, ensuring the independence and security of data of different protocols during transmission, and further ensuring the security of data transmission and reception.

[0082] In an embodiment of the present application, for the gateway system on each host, a discovery thread and a forwarding thread can be set for it. The discovery thread is used to route the data in the shared memory to the corresponding gateway instance, and the forwarding thread is used to transmit the data to the gateway instance of other hosts through the corresponding network, so as to realize a multi-threaded concurrent processing architecture and improve concurrency performance. At the same time, corresponding cycles can also be set for the discovery thread and the forwarding thread to realize time-based task scheduling and ensure reasonable processing timing.

[0083] In some embodiments, the gateway system routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory, including:

[0084] The gateway system calls the discovery thread according to a preset discovery cycle, so that the discovery thread routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory;

[0085] The gateway instance sends the target data to the gateway instance corresponding to the current interface type on other hosts, including:

[0086] The gateway system calls the forwarding thread according to a preset forwarding cycle, so that the forwarding thread controls the gateway instance and sends the target data to the gateway instance corresponding to the current interface type in other hosts.

[0087] Specifically, the gateway system may call a discovery thread when detecting that a preset discovery cycle has been reached, so as to route the target data in the shared memory to a gateway instance of a corresponding interface type through the discovery thread.

[0088] Furthermore, the gateway system may call a forwarding thread when detecting that a preset forwarding period has been reached, so as to control the gateway instance through the forwarding thread to send target data to a gateway instance of a corresponding interface type in another host.

[0089] Among them, the gateway system can call the discovery thread in the order in which the target data in the shared memory is written by the application, and route each target data to the corresponding gateway instance in the order; and the gateway system can call the forwarding thread in the order in which the target data is routed to the gateway instance, notify the gateway instance in the order, and send each target data to other gateway instances of the corresponding interface type.

[0090] Through the above implementation, the separation of the discovery thread and the forwarding thread can be achieved, the system concurrency performance can be improved through multi-threaded concurrent processing, resource competition can be prevented, and time-based task scheduling can be achieved to ensure reasonable timing processing. In addition, atomic operations can be used to ensure state consistency under multi-threading.

[0091] In an embodiment of the present application, in order to further ensure the isolation of transmission and reception of data between different interface types, a dedicated memory pool can be allocated for each interface type, that is, the shared memory is divided into dedicated memory areas corresponding to each interface type. These dedicated memory areas can be targetedly optimized according to the characteristics of each interface type to ensure efficient operation of the system and strict security isolation.

[0092] In some embodiments, the shared memory is composed of dedicated memory areas for each interface type; before the gateway system routes the target data to the corresponding gateway instance based on the current interface type corresponding to the target data in the shared memory, the system further includes:

[0093] The application in the host where the gateway system is located writes the target data into the dedicated memory area of ​​the current interface type in the host;

[0094] The gateway system routes the target data to the corresponding gateway instance based on the current interface type corresponding to the target data in shared memory, including:

[0095] The gateway system routes the target data to the corresponding gateway instance through the channel corresponding to the dedicated memory area of ​​the current interface type.

[0096] The application in the host where the gateway system is located can write target data into a dedicated memory area of ​​the current interface type in the local shared memory.

[0097] Furthermore, the gateway system may route the target data in the dedicated memory area to the corresponding gateway instance through the channel corresponding to the dedicated memory area of ​​the current interface type.

[0098] Figure 4 This is a memory pool allocation diagram provided by an embodiment of the present application. Figure 4 As shown in the figure, each gateway instance is bound to a specific interface type (such as DDS, SOMEIP, CAN, Ethernet, etc.) when it is created. The gateway system can allocate a dedicated memory pool for each interface type to optimize memory usage. When a channel is created, the matching memory pool is selected based on the interface type in the service description of the gateway instance.

[0099] Specifically, each gateway instance is bound to a specific interface type when it is created. This binding is not just a simple label, but forms a key operational constraint that determines all subsequent data processing behaviors of the gateway instance. When a gateway is instantiated, it explicitly declares the specific communication protocol it belongs to through a constructor parameter. This parameter permanently associates the gateway instance with the interface type. Figure 4 The DDS gateway, SOMEIP gateway, CAN gateway, and Ethernet gateway are bound to DDS, SOMEIP, CAN, and Ethernet respectively.

[0100] The binding of interface types directly affects the memory management strategy of the gateway system. The gateway system can allocate a corresponding memory pool for each gateway instance, that is, divide a dedicated memory area in the shared memory. Figure 4 The DDS dedicated memory area, SOMEIP dedicated memory area, CAN dedicated memory area, and Ethernet dedicated memory area.

[0101] Furthermore, the gateway system's channel creation process can fully leverage the aforementioned binding and memory specialization mechanisms. When establishing a communication channel, the gateway system checks the interface type specified in the service description. This interface type identifier serves as a key to unlock the corresponding memory pool. The channel creation mechanism performs a matching operation to ensure that data flowing through the channel will be allocated from the memory pool optimized for the interface type specified in the service description.

[0102] When channels are created, they are associated with a service description that contains the interface type. The gateway system can use this information to match the channel with the appropriate memory pool, ensuring that data is allocated from memory optimized for that specific interface type. Figure 4 As shown, the DDS channel, SOMEIP channel, CAN channel, and Ethernet channel are matched with the DDS dedicated memory area, the SOMEIP dedicated memory area, the CAN dedicated memory area, and the Ethernet dedicated memory area, respectively.

[0103] The above design creates a clear separation between different communication domains while maintaining high performance through dedicated memory management. This isolation is based on binding the interface type during gateway instance creation. The memory pool allocation and channel creation mechanisms build on this foundation, resulting in a unified, efficient, and well-isolated communication system.

[0104] In the above implementation, the gateway system can allocate dedicated memory pools and processing resources for each interface type, ensuring complete physical and logical isolation of data from different interface types. This design allows the system to optimize memory based on the characteristics of each interface type, improving resource utilization efficiency by customizing memory allocation patterns based on expected usage patterns, maintaining consistency and scalability across the architecture, and preventing cross-contamination between different protocol domains. This enables protocol-specific data storage, creates a natural fault isolation boundary, and prevents faults from cascading across different interface types. This ensures high-performance data transmission and reception while providing strong isolation between different protocol domains.

[0105] In one example, determining the dedicated memory area for each interface type includes:

[0106] The gateway system obtains each interface type and a transmission data attribute corresponding to each interface type; the gateway system divides the shared memory of the host into dedicated memory areas for each interface type according to the transmission data attribute corresponding to each interface type.

[0107] Specifically, the gateway system may determine each interface type and a corresponding transmission data attribute, wherein the transmission data attribute may include a transmission data frequency and a transmission data block size.

[0108] The gateway system can divide the local shared memory into dedicated memory areas for each interface type according to the transmission data attributes corresponding to each interface type to adapt to the unique characteristics and requirements of the protocol associated with the interface type.

[0109] For example, the memory pool assigned to the DDS interface type can be configured with a larger data block size to efficiently handle larger data loads common in distributed systems; the memory pool assigned to the CAN interface type prioritizes smaller and more numerous data blocks to manage the high-frequency, compact messages typical in controller area networks.

[0110] Compared to a general one-size-fits-all memory allocation method, the above example can allocate memory areas based on the transmission characteristics of the protocol associated with each interface type, meeting the transmission characteristics and requirements of various protocols.

[0111] In one example, creating a channel corresponding to a dedicated memory area includes:

[0112] The gateway system responds to the gateway creation request sent by the application of the host, creates a gateway instance, and binds the gateway instance to the corresponding interface type;

[0113] The gateway system responds to the channel creation request sent by the application of the host and verifies the type of the gateway instance based on the interface type bound to the gateway instance;

[0114] If the verification passes, the gateway system creates a channel corresponding to the gateway instance and binds the channel to the dedicated memory area.

[0115] The application can initiate the creation of a gateway instance of the corresponding interface type. It should be noted that if a gateway instance of the corresponding interface type has already been created in the gateway system, the application can request the return of the allocated dedicated memory area and channel without having to create the gateway instance again.

[0116] Specifically, in response to a gateway creation request sent by an application on the host, the gateway system may first create a gateway instance and bind the gateway instance to an interface type corresponding to the application.

[0117] After binding is complete, the application can continue to request the gateway system to create a channel. In response to the channel creation request sent by the application, the gateway system can verify the type of the gateway instance based on the interface type bound to the gateway instance, that is, determine whether the bound interface type is consistent with the created instance type. If they are consistent, the gateway system will continue to create the channel corresponding to the gateway instance and request the corresponding dedicated memory area in shared memory based on the bound interface type, and bind the channel to this dedicated memory area. The channel is the data transmission channel between the gateway instance and the dedicated memory area of ​​the corresponding interface type.

[0118] Figure 5 This is a memory matching flow chart of a gateway instance provided in an embodiment of the present application, such as Figure 5As shown, an application can first request the gateway system to create a gateway instance. The gateway system then creates the gateway instance and binds it to a specific interface type. Furthermore, the application continues to request channel creation. The gateway system checks the interface type against the gateway instance's service description, verifying whether the interface type matches the gateway type. The service description includes the interface type, explicitly identifying the communication interface type used by each service. This identification serves as the foundation for the entire matching process and is used throughout every step of the system's operation.

[0119] To optimize performance and resource usage, the gateway system allocates dedicated memory pools for each interface type. These memory pools are optimized based on the characteristics of each interface type. During channel creation, the system automatically verifies that the interface type in the service description matches the gateway's interface type. Only channels that successfully match are established. If the interface type matches the gateway type, the gateway system creates the channel and requests a memory pool, allocating a dedicated memory area from shared memory. Shared memory then returns the dedicated memory area, returns a memory pool reference, and returns a channel reference to the gateway system. The gateway system then returns the channel creation results to the application.

[0120] Through the above process, the type safety of data flow can be ensured. The data routing decision of the gateway system is also implemented based on the interface type in the service description, ensuring that data always flows to the correct target and maintaining the efficient operation and strict isolation of the system.

[0121] In an embodiment of the present application, for the dedicated memory area under each interface type, multiple sub-areas can be further divided in the dedicated memory area according to the security level of the data, so as to allocate independent memory areas for data of different security levels, ensuring that data of high security levels will not be accessed by components of low security levels.

[0122] In one example, an application in a host where the gateway system is located writes target data into a dedicated memory area of ​​the current interface type in the host, including:

[0123] The application in the host where the gateway system is located determines the current security level of the target data and determines the target sub-area in the dedicated memory area of ​​the current interface type based on the current security level; the application in the host where the gateway system is located writes the target data into the target sub-area.

[0124] The application on the host computer where the gateway system resides can first determine a target sub-region within the dedicated memory region for the current interface type based on the current security level of the target data and the pre-configured relationship between security levels and regions. Furthermore, the application can write the target data into the target sub-region.

[0125] Correspondingly, after the target data is forwarded to the gateway instance on the other host through the forwarding thread, the gateway instance of the other host can also write the target data into the target sub-area in the dedicated memory area of ​​the corresponding interface type according to the current security level of the target data.

[0126] Through the above implementation, independent memory areas can be allocated for data of different security levels in the shared memory, ensuring that high-security-level data cannot be accessed by components of low-security levels. In addition, other security mechanisms can also be set.

[0127] For example, Figure 6 This is an isolation architecture diagram of a gateway system provided in an embodiment of the present application, such as Figure 6 As shown, the gateway system can adopt a layered security model to clearly separate the application layer, shared memory layer, and interface isolation layer, and implement different levels of security policies for each layer.

[0128] refer to Figure 6 In the application layer, different applications can access shared memory through strict access control mechanisms; in the shared memory layer, the gateway system can allocate independent memory areas for data of different security levels to ensure that high-security-level data will not be accessed by low-security-level components; in the interface isolation layer, each interface gateway is assigned a specific security level configuration, for example, DDS and Ethernet gateways are usually configured as high security levels, SOMEIP gateways are configured as medium security levels, and CAN gateways are configured as lower security levels to balance performance and security requirements.

[0129] Among them, the security policy of the Ethernet gateway may include access control and encryption, the security policy of the DDS gateway may include encryption and authentication, the security policy of the SOMEIP gateway may include authentication, and the security policy of the CAN gateway may include data filtering.

[0130] This multi-level security architecture enables the gateway system to flexibly apply security strategies such as encryption, authentication, access control, and data filtering according to the characteristics and security requirements of different interface types, forming a comprehensive and sophisticated security protection network.

[0131] The embodiment of the present application provides a method for isolating the sending and receiving of data. The gateway system in the host routes the target data to the gateway instance corresponding to the current interface type according to the current interface type corresponding to the target data in the shared memory, and then the gateway instance sends the target data to the gateway instance corresponding to the current interface type in other data, so that the gateway instance in the other host writes the target data to the shared memory of the other host. The application can read the target data from the shared memory, realizing data transmission between applications of different hosts, and is suitable for applications of various interface types to send data to applications in other hosts. The method performs data transmission through gateway instances of various interface types between different hosts, and can realize the isolation of data of different interface types. The failure of one interface will not affect the normal operation of other interfaces, thereby improving the overall reliability of the system. Moreover, the method realizes zero-copy communication through shared memory. Data only needs to be written once, and there is no need to copy data, which greatly reduces memory bandwidth consumption and CPU load, and improves data transmission efficiency, realizing efficient cross-interface communication. In addition, the system has good scalability and can support dynamic addition of new interface types or removal of no longer required interface types.

[0132] The present application also provides a method for isolating data transmission and reception, which is applied to each host. The host includes each application and a gateway system. The gateway system includes a shared memory and a gateway instance corresponding to each interface type. The method for isolating data transmission and reception specifically includes:

[0133] In response to receiving target data sent by gateway instances of the same interface type in other hosts, the gateway instance writes the target data into the shared memory of the host, so that an application of the host reads the target data from the shared memory.

[0134] Specifically, if a gateway instance receives target data from a gateway instance on another host, it can convert the target data's format based on the target data's current interface type and write it to local shared memory, for example, to a dedicated memory area within the shared memory corresponding to the current interface type. The target data can then be transmitted by the gateway instance on the other host via a network with the corresponding interface type.

[0135] After the gateway instance writes the target data to the local shared memory, the host application can read the target data from the shared memory. For example, the application can read data matching the interface type from the shared memory based on the interface type filter.

[0136] For example, Figure 7 This is a data transmission and reception process diagram provided by an embodiment of the present application, such as Figure 7As shown, the publisher application (i.e., the data sender) can write the data to be transmitted into the dedicated memory area of ​​the corresponding interface type through the interface type tag, such as the DDS memory area, SOMEIP memory area or CAN memory area in the figure, and then the gateway instance of the corresponding interface type, such as the DDS gateway, SOMEIP gateway, and CAN gateway in the figure, can transmit the data through the external network to the gateway instance of the host where the subscriber application (i.e., the data receiver) is located.

[0137] Furthermore, after being transmitted to the gateway instance of the host where the application is located, the gateway instance of the host where the application is located can write the data into the dedicated memory area of ​​the corresponding interface type, and then the subscriber application can filter by interface type and read the data of the corresponding interface type from the shared memory.

[0138] In the embodiments of the present application, corresponding security processing policies can be set for different interface types to further ensure the security of data transmission and reception. When the gateway instance receives data transmitted from the external network, it can process the received data according to the corresponding security processing policy and then write the processed data to the local shared memory.

[0139] In some implementations, before the gateway instance writes the target data into the shared memory of the host, the method further includes:

[0140] The gateway instance performs at least one of data verification processing, authorization verification processing, encryption conversion processing, identity authentication processing and data filtering processing on the target data according to the security level of the corresponding interface type.

[0141] Among them, when the gateway instance receives the target data sent by the gateway instance of the corresponding interface in other hosts, it can perform at least one of data verification processing, authorization verification processing, encryption conversion processing, identity authentication processing and data filtering processing on the target data according to the security level of the corresponding interface type.

[0142] Specifically, data validation ensures that input or transmitted data conforms to predefined rules, formats, or business logic, preventing invalid, erroneous, or malicious data from entering the system. Authorization verification verifies the authority to access specific resources or perform specific operations, preventing unauthorized access. Cryptographic conversion protects data confidentiality by converting data into an unreadable form (encryption) or altering its structure (conversion) through algorithms. Data filtering filters, cleanses, or modifies data based on rules.

[0143] For example, the Ethernet gateway instance can perform access control processing (identity authentication processing, authorization verification processing) and encryption conversion processing, the DDS gateway instance can perform encryption conversion processing and identity authentication processing, the SOMEIP gateway instance can perform identity authentication processing, and the CAN gateway instance can perform data filtering processing.

[0144] Furthermore, after the above processing is completed, the processed target data may be written into a local shared memory, specifically into a dedicated memory area corresponding to the interface type.

[0145] Through the above implementation, corresponding security processing measures can be assigned to gateway instances of different interface types, further ensuring data security.

[0146] In the embodiment of the present application, a strict state management and error handling mechanism can also be used to ensure the stable and reliable operation of the system. Specifically, the gateway system can strictly manage the status of all tasks, ensure the consistency and predictability of task execution through atomic operations and status flags, and ensure that the same service description does not create duplicate channels through channel search and verification mechanisms, avoiding resource waste and potential conflicts. The system can also define detailed error types and processing strategies to accurately handle various abnormal situations and improve system robustness; data streams of different interface types are strictly isolated, and the failure of one interface will not affect the normal operation of other interfaces, thereby improving the overall reliability of the system.

[0147] The gateway system also supports the dynamic addition of new communication channels at runtime, allowing functionality to be expanded without restarting the service. It also supports the safe removal of unneeded channels at runtime, freeing up associated resources and optimizing system performance. Furthermore, the gateway system allows task parameters and configurations to be adjusted without interrupting service, adapting to evolving communication needs. The gateway system easily adds new interface types by simply implementing the corresponding gateway and channel classes, without modifying the core framework.

[0148] The gateway system ensures real-time transmission and processing of critical data through optimized scheduling algorithms and resource allocation strategies. It provides strict isolation between interfaces of different security levels to meet the functional safety requirements of in-vehicle systems. It implements strict memory access control to prevent unauthorized access and memory corruption. It implements integrity checks during data transmission to prevent data tampering. It supports configuring different security policies for different interface types, including authentication, encryption, and access control.

[0149] In an embodiment of the present application, a three-tiered gateway system architecture is also proposed, comprising an interface isolation layer, a channel management layer, and a data forwarding layer. The interface isolation layer includes an interface type binding mechanism (a gateway instance is bound to a specific interface type upon creation to ensure specific processing), a memory pool isolation mechanism (a dedicated memory pool is allocated for each interface type to avoid resource competition), and service description filtering (service descriptions are filtered based on the interface type field to ensure type safety).

[0150] The channel management layer can include dynamic channel creation (dynamically creating a matching communication channel based on the service description), channel type verification (verifying whether the interface type of the channel matches the gateway type), and resource lifecycle management (complete management of the channel creation, use, and release process).

[0151] The data forwarding layer can include a zero-copy transmission mechanism (efficient data exchange through shared memory and pointer passing), interface type routing (routing data to the correct target based on the interface type), and batch processing optimization (processing data in groups by interface type to improve efficiency).

[0152] This three-level hierarchical architecture ensures strict isolation and efficient processing of data of different interface types, while providing good scalability and security. It is particularly suitable for high-performance systems that need to process multiple communication protocols, such as autonomous driving, robotics and industrial automation.

[0153] It should also be noted that the gateway system provided in the embodiment of this application can be implemented using C++ technology, following the C++14 writing specification, and making extensive use of modern C++ features such as smart pointers, lambda expressions, atomic operations, and thread-safe containers to ensure high code quality and maintainability. The gateway system is designed in accordance with POSIX standards and has good cross-platform compatibility. It can be deployed and run on multiple operating systems such as Linux, QNX, and Android. Through conditional compilation and platform abstraction layers, the system can adapt to different hardware and software environments, providing a unified solution for heterogeneous system integration.

[0154] In addition, the gateway system provided in the embodiment of the present application realizes efficient, reliable and secure cross-interface communication through an innovative interface type isolation mechanism and a three-level hierarchical architecture. This system not only solves the problem of mixed processing of data of different interface types in the traditional gateway architecture, but also significantly improves performance and reduces resource consumption through a dedicated memory pool and zero-copy technology. The modular design and dynamic configuration capability of the system give it excellent scalability and adaptability, and it can easily integrate new interface types and communication protocols. Actual applications have shown that compared with traditional gateway solutions, the gateway system has significant advantages in data throughput, latency, CPU occupancy and memory efficiency.

[0155] The embodiment of the present application provides a method for isolating the sending and receiving of data. In response to receiving target data sent by a gateway instance of the same interface type in other hosts, the gateway instance writes the target data into the shared memory of the host where it is located, so that the application of the host where it is located reads the target data from the shared memory, thereby realizing data transmission between applications of different hosts. The method is suitable for applications of various interface types to send data to applications in other hosts. The method performs data transmission through gateway instances of various interface types between different hosts, and can achieve isolation of data of different interface types. The failure of one interface will not affect the normal operation of other interfaces, thereby improving the overall reliability of the system. Moreover, the method realizes zero-copy communication through shared memory. Data only needs to be written once, and there is no need to copy data, which greatly reduces memory bandwidth consumption and CPU load, and improves data transmission efficiency, thereby achieving efficient cross-interface communication. In addition, the system has good scalability and can support the dynamic addition of new interface types or the removal of no longer required interface types.

[0156] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 8 As shown, the electronic device 400 includes one or more processors 401 and a memory 402 .

[0157] The processor 401 may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 400 to perform desired functions.

[0158] The memory 402 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may, for example, include random access memory (RAM) and / or cache memory (cache), etc. The non-volatile memory may, for example, include read-only memory (ROM), a hard disk, a flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 401 may run the program instructions to implement the method for isolating the transmission and reception of data in any embodiment of the present application described above and / or other desired functions. Various contents such as initial external parameters, threshold values, etc. may also be stored in the computer-readable storage medium.

[0159] In one example, electronic device 400 may further include an input device 403 and an output device 404, which are interconnected via a bus system and / or other connection mechanisms (not shown). Input device 403 may include, for example, a keyboard, a mouse, etc. Output device 404 may output various information to the outside, including warning information, braking force, etc. Output device 404 may include, for example, a display, a speaker, a printer, a communication network, and remote output devices connected thereto.

[0160] Of course, to simplify, Figure 8 Only some of the components related to the present application in the electronic device 400 are shown, and components such as buses, input / output interfaces, etc. are omitted. In addition, the electronic device 400 may further include any other appropriate components according to specific application scenarios.

[0161] In addition to the above-mentioned methods and devices, an embodiment of the present application may also be a computer program product, which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps of the method for isolating the sending and receiving of data provided in any embodiment of the present application.

[0162] The computer program product may be written in any combination of one or more programming languages ​​to implement the program code for performing the operations of the embodiments of the present application, including object-oriented programming languages ​​such as Java, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0163] In addition, an embodiment of the present application may also be a computer-readable storage medium having computer program instructions stored thereon. When the computer program instructions are executed by a processor, the processor executes the steps of the method for isolating the sending and receiving of data provided in any embodiment of the present application.

[0164] The computer-readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can, for example, include but is not limited to a system, device or component of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0165] It should be noted that the terms used in this application are only for describing specific embodiments and are not intended to limit the scope of this application. As shown in the specification and claims of this application, unless the context clearly indicates an exception, the words "one", "an", "a kind of" and / or "the" do not specifically refer to the singular and may also include the plural. The terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method or device. In the absence of further restrictions, the elements defined by the sentence "comprise a..." do not exclude the presence of other identical elements in the process, method or device comprising the elements.

[0166] It should also be noted that the terms "center", "up", "down", "left", "right", "vertical", "horizontal", "inside", "outside", etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on this application. Unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", etc. should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate medium, or it can be a communication between the internal parts of two elements. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0167] This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and core ideas of this application. The above is only the preferred implementation method of this application. It should be pointed out that due to the limitations of textual expression, there are objectively infinite specific structures. For ordinary technicians in this technical field, without departing from the principles of this application, they can also make several improvements, modifications or changes, and can also combine the above technical features in an appropriate manner; these improvements, modifications, changes or combinations, or the direct application of the inventive concept and technical solution to other occasions without improvement, should be regarded as the scope of protection of this application.

Claims

1. A method for isolating data transmission and reception, characterized in that: Applied to each host, the host includes each application and a gateway system, the gateway system includes shared memory and gateway instances corresponding to each interface type, the method includes: The gateway system routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory, wherein the target data is the data to be transmitted written by the application in the host where the gateway system is located; The gateway instance sends the target data to the gateway instance corresponding to the current interface type in the other host, so that the gateway instance corresponding to the current interface type in the other host writes the target data into the shared memory of the other host, wherein the application in the other host reads the target data from the shared memory.

2. The method according to claim 1, characterized in that Gateway instances of the same interface type between different hosts are connected through a network corresponding to the interface type, and the gateway instance sends the target data to the gateway instance corresponding to the current interface type in the other host, including: The gateway instance converts the target data into a format according to a transmission format of a network corresponding to the current interface type; The gateway instance sends the target data after format conversion to the network corresponding to the current interface type, so that the gateway instance corresponding to the current interface type in other hosts obtains the target data from the network.

3. The method according to claim 1, characterized in that The gateway system routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory, including: The gateway system calls the discovery thread according to a preset discovery cycle, so that the discovery thread routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory; The gateway instance sends the target data to a gateway instance corresponding to the current interface type in another host, including: The gateway system calls a forwarding thread according to a preset forwarding period, so that the forwarding thread controls the gateway instance and sends the target data to the gateway instance corresponding to the current interface type in other hosts.

4. The method according to claim 1, wherein The gateway instance includes an inbound gateway and an outbound gateway, and the gateway instance sends the target data to the gateway instance corresponding to the current interface type in the other host, so that the gateway instance corresponding to the current interface type in the other host writes the target data into the shared memory of the other host, including: The outbound gateway in the gateway instance sends the target data to the inbound gateway corresponding to the current interface type in the other host, so that the inbound gateway in the other host writes the target data into the shared memory of the other host.

5. The method according to claim 1, wherein The shared memory is composed of dedicated memory areas for each interface type; before the gateway system routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory, it also includes: The application in the host where the gateway system is located writes the target data into a dedicated memory area of ​​the current interface type in the host; The gateway system routes the target data to the corresponding gateway instance according to the current interface type corresponding to the target data in the shared memory, including: The gateway system routes the target data to the corresponding gateway instance through the channel corresponding to the dedicated memory area of ​​the current interface type.

6. The method according to claim 5, characterized in that Determination of dedicated memory areas for each interface type includes: The gateway system obtains each interface type and the transmission data attribute corresponding to each interface type; The gateway system divides the shared memory of the host into dedicated memory areas for each interface type according to the transmission data attributes corresponding to each interface type.

7. The method according to claim 5, characterized in that The creation of the channel corresponding to the dedicated memory area includes: The gateway system creates a gateway instance in response to a gateway creation request sent by an application on the host, and binds the gateway instance to a corresponding interface type; The gateway system verifies the type of the gateway instance based on the interface type bound to the gateway instance in response to the channel creation request sent by the application of the host; If the verification is successful, the gateway system creates a channel corresponding to the gateway instance and binds the channel to the dedicated memory area.

8. The method according to claim 5, characterized in that The application in the host where the gateway system is located writes the target data into a dedicated memory area of ​​the current interface type in the host, including: An application in the host where the gateway system is located determines a current security level of the target data, and determines a target sub-area in the dedicated memory area of ​​the current interface type according to the current security level; The application in the host where the gateway system is located writes the target data into the target sub-area.

9. A method for isolating sent and received data, characterized in that: Applied to each host, the host includes each application and a gateway system, the gateway system includes shared memory and gateway instances corresponding to each interface type, the method includes: In response to receiving target data sent by gateway instances of the same interface type in other hosts, the gateway instance writes the target data into the shared memory of the host, so that an application of the host reads the target data from the shared memory.

10. The method according to claim 1, characterized in that Before the gateway instance writes the target data into the shared memory of the host, the method further includes: The gateway instance performs at least one of data verification processing, authorization verification processing, encryption conversion processing, identity authentication processing and data filtering processing on the target data according to the security level of the corresponding interface type.

Images