CN117221046A - Vehicle-mounted gateway middle layer based on SOME/IP communication - Google Patents

Abstract

The invention relates to the technical field of vehicle-mounted gateways, in particular to a vehicle-mounted gateway middle layer based on SOME/IP communication, which comprises an interface layer and an implementation layer, wherein the interface layer is used for providing an interface for an application of an ECU, and the implementation layer is used for providing a communication channel for the application of the ECU; the interface layer comprises an SOME/IP interface, an IPC interface and a Hardware Communicate interface; the implementation layer comprises a general function module and a communication function module, wherein the general function module comprises a utility module, a log & trace module and a configuration module, and the communication function module comprises an SOME/IP core module, an IPC communication module and a hardware interface communication module.

Description

Vehicle-mounted gateway middle layer based on SOME/IP communication

Technical Field

The invention relates to the technical field of vehicle-mounted gateways, in particular to a vehicle-mounted gateway middle layer based on SOME/IP communication.

Background

The existing vehicle-mounted gateway in the market has single function, only supports communication by using a SOME/IP mode, and does not support communication by using other interfaces. If the communication is needed among processes according to different scene requirements, the shared memory, the message queue and the FIFO are needed to be used for communication; outside the process, communication needs to be performed by using different hardware interfaces CAN, serial ports, SPI and the like. These functions are difficult to be integrally implemented by the vehicle-mounted gateway on the market at present.

In addition, if the application needs to use a communication interface other than SOME/IP, the application needs to directly call a system interface, the detail problem of different communication interfaces needs to be considered, the service is also strongly associated with the communication interface, and the reusability and portability of the application module are reduced, which is difficult to realize by the vehicle-mounted gateway on the market at present.

In addition, the message content of the vehicle-mounted gateway on the market at present does not realize the use of a uniform coding format, which is not beneficial to the definition and analysis of data of the application on the ECU (Electronic Control Unit ).

Disclosure of Invention

The invention provides a vehicle-mounted gateway middle layer based on SOME/IP communication for solving the defects and shortcomings of the prior art.

In order to achieve the above purpose, the technical scheme adopted by the invention is that the vehicle-mounted gateway intermediate layer based on SOME/IP communication comprises an interface layer and an implementation layer, wherein the interface layer is used for providing an interface for the application of the ECU, and the implementation layer is used for providing a communication channel for the application of the ECU;

the interface layer comprises an SOME/IP interface, an IPC interface and a Hardware Communicate interface;

the implementation layer comprises a general function module and a communication function module, wherein the general function module comprises a utility module, a log & trace module and a configuration module,

the utility module is used for providing a general function;

the log & trace module is used for carrying out log initialization and trace server initialization according to the parameters stored by the configuration module, providing log output control and carrying out real-time log tracking function by the client connected with the server;

the configuration module is used for reading the configuration file, storing the log level of the log & trace module, setting the log file and initializing parameters of the trace server according to the configuration file, selecting a communication interface, and storing attribute parameters of the communication interface;

the communication function module comprises a SOME/IP core module, an IPC communication module and a hardware interface communication module,

the SOME/IP core module is used for establishing a communication channel of SOME/IP, providing the function of SOME/IP communication and being in signal connection with the SOME/IP interface;

the IPC communication module is used for establishing an IPC communication channel, providing an IPC communication function and being in signal connection with the IPC interface;

the hardware interface communication module is used for establishing a hardware communication channel, providing the capability of receiving and transmitting data through a hardware interface, and is in signal connection with the Hardware Communicate interface.

Preferably, the SOME/IP core module comprises a run module, a Routing module, a service_discovery module, an endpoint module, an e2e_protection module,

the run time module is used for resource creation;

the Routing module is used for providing synchronous communication or asynchronous communication functions of services, events and event groups defined in the SOME/IP protocol and managing data and states of the services, the events and the event groups, and provides an interface for the run time module;

the service_discovery module provides a service discovery function in an SOME/IP protocol, wherein the service discovery function comprises service discovery, service subscription, event group processing and service discovery data package, and provides an interface for the Routing module;

the endpoint module is used for managing the socket of the IP endpoint, TCP or UDP and receiving and transmitting data packets, providing a network communication channel function of TCP unicast or UDP unicast, multicast and broadcast, and providing an interface for the Routing module and the service_discovery module;

the e2e_protection module provides communication protection for the endpoint module.

Preferably, the IPC communication module comprises a FIFO communication module, a socket communication module, a shared memory communication module and a message queue communication module,

the FIFO communication module uses named pipeline communication to provide communication among different processes in the ECU;

the socket communication module provides a TCP or UDP communication interface to carry out communication between an ECU internal process or the ECU and the ECU;

the shared memory communication module is used for creating a shared memory segment and providing communication among different processes in the ECU;

the message queue communication module is used for communicating by using the message queue of the kernel to provide communication among different processes in the ECU.

Preferably, the hardware interface communication module comprises a serial port communication module, an SPI communication module, a CAN communication module and an inter-core communication module,

the serial port communication module is used as a serial port interface for packaging an operating system;

the SPI communication module is used for packaging an SPI interface provided by an operating system;

the CAN communication module is used for packaging a CAN interface provided by an operating system;

the inter-core communication module is used as an inter-core communication interface provided by a packaging chip manufacturer.

Preferably, the hardware interface communication module further includes an IC communication module that serves as an IC interface provided by the packaged operating system.

Preferably, the SOME/IP core module further comprises a Message module, and the Message module is used for packaging the Message header and the Message content according to the SOME/IP protocol.

Preferably, the general function module further comprises a protobuf module and a json module,

the protobuf module is used for repackaging an interface of the open source library into a single instance type through the open source library protobuf library so as to realize packaging and unpacking;

the json module is used for repackaging the interface of the open source library into a single instance class to realize package and unpack.

Preferably, the communication function module further includes a protobuf module, a json module, and a Message module, where the protobuf module and the json module are disposed below the Message module;

the Message module is used for packaging the Message header and the Message content according to the SOME/IP protocol;

the protobuf module is used for repackaging an interface of the open source library into a single instance type through the open source library protobuf library so as to realize packaging and unpacking;

the json module is used for repackaging the interface of the open source library into a single instance class to realize package and unpack.

The invention has the beneficial effects that:

the invention provides a vehicle gateway middle layer based on SOME/IP communication, which provides rich communication interfaces, including inter-process communication interfaces in the ECU and communication interfaces between the ECU, and can also select the needed communication interfaces according to configuration interfaces and configuration files to complete data interaction.

Drawings

FIG. 1 is a diagram of a first embodiment of an on-board gateway interface layer based on SOME/IP communication;

fig. 2 is a second embodiment of a vehicular gateway interface layer based on SOME/IP communication according to the present invention.

Detailed Description

The invention will now be described in further detail with reference to the accompanying drawings, which are simplified schematic illustrations, illustrating the basic structure of the invention by way of illustration only, the direction of this embodiment being the direction of fig. 1.

The invention provides a vehicle-mounted gateway middle layer based on SOME/IP communication, which comprises an interface layer and an implementation layer, wherein the interface layer is used for providing an interface for an application of an ECU, and the implementation layer is used for providing a communication channel for the application of the ECU;

the interface layer comprises a SOME/IP interface 1, an IPC interface 2 and a Hardware Communicate interface 3;

the implementation layer comprises a general function module 4 and a communication function module 5, the general function module 4 comprises a utility module 41, a log & trace module 42 and a configuration module 43,

the utility module 41 is configured to provide a general function;

the log & trace module 42 is configured to perform log initialization and trace server initialization according to the parameters stored in the configuration module 43, provide log output control, and perform real-time log tracking function when the client is connected to the server;

the configuration module 43 is configured to read a configuration file, store the log level of the log & trace module, set the log file, and initialize parameters of the trace server according to the configuration file, select a communication interface, and store attribute parameters of the communication interface;

the configuration module 43 contains all configuration parameters of the middle layer implementation layer, and can be configured statically through a file or dynamically through an interface, such as configuration logs, and can control log behaviors of the log & trace module 42 through configuration files or calling interfaces; and designating which communication mode is selected, and assigning a pointer where the base class is located to a corresponding communication module according to the parameter instantiation when the initialization function of the communication base class is called by defining the communication mode parameter.

The communication function module 5 comprises a SOME/IP core module 6, an IPC communication module 7 and a hardware interface communication module 8,

the SOME/IP core module 6 is used for establishing a communication channel of SOME/IP, providing a function of SOME/IP communication and being in signal connection with the SOME/IP interface 1;

the IPC communication module 7 is used for establishing an IPC communication channel, providing an IPC communication function and being in signal connection with the IPC interface 2;

the hardware interface communication module 8 is used for establishing a hardware communication channel, providing the capability of receiving and transmitting data through a hardware interface, and is in signal connection with the Hardware Communicate interface 3.

The SOME/IP core module 6 includes a run module 61, a Routing module 62, a service_discovery module 63, an endpoint module 64, an e2e_protection module 65,

the run time module 61 is used for resource creation;

the Routing module 62 is configured to provide synchronous communication or asynchronous communication functions of services, events and event groups defined in the SOME/IP protocol, and management of data and status of the services, events and event groups, and provide an interface for the running time module 61;

the service_discovery module 63 provides service discovery functions in the SOME/IP protocol, where the service discovery functions include service discovery, service subscription, event group processing, and service discovery data packet, and provides an interface for the Routing module 62;

the endpoint module 64 is configured to perform socket management and packet transceiving on an IP endpoint, TCP or UDP, provide a network communication channel function of TCP unicast or UDP unicast, multicast or broadcast, and provide an interface for the Routing module 62 and the service_discovery module 63;

the e2e_protection module 65 provides communication protection for the endpoint module 64.

The IPC communication module 7 includes a FIFO communication module 71, a socket communication module 72, a shared memory communication module 73, a message queue communication module 74,

the FIFO communication module 71 uses named pipe communication to provide communication between different processes in the ECU; the FIFO communication module 71 may implement naming pipe-specific behavior, such as creating naming pipes from file paths, pipe error handling, etc.

The socket communication module 72 provides a TCP or UDP communication interface to perform communication between the ECU internal process or the ECU and the ECU; the socket communication module 72 may define a simple protocol to communicate, and also implement communication based on a subscription or publishing mode, so as to implement subscription or publishing mode communication based on a forwarding mechanism in many-to-many manner, and introduce an MQTT open source library of one-to-many subscription or publishing mode to communicate.

The shared memory communication module 73 is used for creating a shared memory segment and providing communication among different processes in the ECU; the shared memory communication module 73 may implement functions such as creation of a shared memory, control operation of the shared memory, size setting of the shared memory, and read timeout control of a shared memory client. When the one-to-many communication model is implemented, a signaling mode can be used, and when the update of the data of the server is completed, all clients are notified to read the data by using the signaling mode.

The message queue communication module 74 is configured to use the message queue of the kernel to communicate, and provide communication between different processes in the ECU. The message queue communication module 74 may perform functions such as creation of message queues, control of message queues, message exchange of message queues, and the like.

The hardware interface communication module 8 comprises a serial port communication module 81, an SPI communication module 82, a CAN communication module 83, an inter-core communication module 84,

the serial communication module 81 is used as a serial interface for packaging an operating system; the serial port communication module 81 is configured to implement serial port device initialization, serial port attribute setting, and the like. Serial attribute settings include the settings of stop bits, data bits, parity bits.

The SPI communication module 82 serves as an SPI interface provided by the packaged operating system; the SPI communication module 82 may also be used to implement initialization of SPI devices, attribute settings of the SPI, and the like. The attribute setting of the SPI includes selection of the slave address, and communication rate setting.

The CAN communication module 83 serves as a CAN interface provided by the packaged operating system. The CAN communication module 83 is further configured to implement initialization, filter setting, baud rate setting, and the like of the CAN device.

The inter-core communication module 84 serves as an inter-core communication interface provided by the package chip manufacturer. The inter-core communication module 84 is further configured to implement hardware initialization, endpoint setting, exception handling, etc. for inter-core communication.

Preferably, the hardware interface communication module 8 further includes an I2C communication module 85, and the I2C communication module 85 is used as an I2C interface provided by the package operating system; the hardware interface communication module 8 is further used for initializing the I2C device, setting the attribute of the I2C, and the like, where the attribute of the I2C includes selection of the slave address, filling of the data structure, and the like.

The SOME/IP core module 6 further comprises a Message module 66, and the Message module 66 is configured to encapsulate a Message header and a Message content according to the SOME/IP protocol.

The general function module 4 further comprises a protobuf module 44 and a json module 45,

the protobuf module 44 is configured to repackage the interface of the open source library into a single instance class through the open source library protobuf, so as to implement encapsulation and unpacking;

the json module 45 is configured to repackage the interface of the open source library into a single instance class, so as to implement encapsulation and decapsulation.

Preferably, the communication function module 5 further includes a protobuf module 44, a json module 45, and a Message module 66, where the protobuf module 44 and the json module 45 are disposed below the Message module 66.

The Message module 66 is configured to encapsulate the Message header and the Message content according to the SOME/IP protocol;

the protobuf module 44 is configured to repackage the interface of the open source library into a single instance class through the open source library protobuf, so as to implement encapsulation and unpacking;

the json module 45 is configured to repackage the interface of the open source library into a single instance class, so as to implement encapsulation and decapsulation.

The present invention includes two embodiments, embodiment one (as shown in fig. 1): if the hardware interface communication module 8 includes a serial port communication module 81, an SPI communication module 82, a CAN communication module 83, an inter-core communication module 84, and an I2C communication module 85, the protobuf module 44 and the json module 45 are disposed in the general function module 4; example two (as shown in fig. 2): if the hardware interface communication module 8 includes a serial port communication module 81, an SPI communication module 82, a CAN communication module 83, and an inter-core communication module 84, the protobuf module 44 and the json module 45 are disposed in the communication function module 5.

In the second embodiment, compared with the first embodiment, the interface layer is unchanged, mainly the implementation layer is changed, and a packet mode that all communication modules use the SOME/IP protocol is implemented. The implementation layer is logically subdivided into a generic function module 4 and a communication function module 5. The Message module 66 in the SOME/IP core module 6 is removed and placed under each communication module, so as to provide the same packet data interface for each communication module, and the protobuf, json module 45 of the universal function module 4 is removed under the Message module 66 of the communication module, so as to provide coding of Message content for the Message module. According to the characteristics of each communication module, the basic function interface of the SOME/IP core module 6 is realized as far as possible to keep the interface of the interface layer of the middle layer uniform, and a uniform service-oriented communication interface which does not distinguish communication channels is provided for the application of the ECU.

And, the I2C communication module is removed from the hardware communication module, because I2C communication is generally used for reading and writing registers, it is difficult to implement service-oriented communication. The shared memory is used for realizing the service-oriented communication of many-to-many, the information such as read-write control data, message data, data size and the like can be stored in the memory in a specific data structure, the applied memory is regarded as a ring buffer, and the message transmission between processes is to access the buffer.

The transmission data comprises a configuration file, wherein the configuration file comprises four configuration parameter groups, namely interface type, interface characteristics, log & trace parameters and packaging related configuration. The method comprises the following steps:

1. the interface types include: SOME/IP interface 1, IPC interface 2, hardware Communicate interface 3;

wherein the corresponding communication channels are respectively: the SOME/IP core module 6 is in signal connection with the SOME/IP interface 1;

the IPC communication module 7 in signal connection with the IPC interface 2 includes a FIFO communication module 71, a socket communication module 72, a shared memory communication module 73, and a message queue communication module 74;

the hardware interface communication module 8 in signal connection with the Hardware Communicate interface 3 includes a serial port communication module 81, an SPI communication module 82, a CAN communication module 83, an inter-core communication module 84, and an I2C communication module 85.

2. Interface characteristics: specifying the characteristics of the communication channel and configuring parameters.

3. The log & trace parameters include ports and ips that specify log paths, sizes, storage numbers, ranks, trace.

4. Packaging related configuration: protobuf, json, null. Where null represents transmission original data and protobuf, json represents packed data.

The implementation method of the invention comprises the following steps:

s1: the configuration module 43 initializes, reads the configuration file of the transmission data, and stores the log level, log file setting and parameters of the initialization of the trace server of the log & trace module according to the configuration file, and selects one communication channel in the communication function module 5, and stores the attribute parameters of the communication channel;

s2: the log & trace module performs log initialization and trace server initialization according to the parameters stored by the configuration module, and provides log output control and a function of real-time log tracking by a client connected with a server;

s3: and the communication function module 5 selects a communication channel corresponding to the attribute parameter to initialize according to the attribute parameter stored by the configuration module, and provides the communication channel for an interface layer.

If the communication channel selected for transmitting the data is the SOME/IP core module 6, the SOME/IP core module is initialized, wherein the initialization sequence of each module is that an initialization json module or a protobuf module is selected according to the parameters of the configuration file, if no packing parameters are set in the configuration file, the original data is transmitted by default, and then the e2e_protection module, the endpoint module 64, the service_discovery module 63, the Routing module 62, the Message module 66 and the run module 61 are initialized. After initialization is completed, the communication channel is in a working state, and data receiving and transmitting and service processing of the client and the server can be performed according to SOME/IP protocol standard.

If the communication channel selected for transmitting data is the IPC communication module 7, the initialization json module or protobuf module is selected according to the parameters of the configuration file, if the packaging parameters are not set in the configuration file, the original data is transmitted by default, and then one of the FIFO communication module 71, the socket communication module 72, the shared memory communication module 73 and the message queue communication module 74 is selected according to the parameters stored by the configuration module 43 to establish the IPC communication channel, wherein the communication channel is in a working state and provides the data receiving and transmitting function for the interface layer.

If the communication channel selected for transmitting data is the hardware interface communication module 8, firstly, the json module or protobuf module is selected and initialized according to the parameters of the configuration file, if the packaging parameters are not set in the configuration file, the original data is transmitted by default, and then, one of the serial port communication module 81, the I2C communication module 85, the SPI communication module 82, the CAN communication module 83 and the internuclear communication module 84 is selected and used for establishing the hardware communication channel according to the parameters stored by the configuration module, wherein the communication channel is in a working state and provides the data receiving and transmitting function for the interface layer.

Data related to configuration, display and state is generally packaged through a json module. When binary data, file data or data with high compression rate and small occupied bandwidth are required to be transmitted, packaging is carried out through a protobuf module.

When the configuration file is communicated by SOME/IP, original data is sent from the ECU app1, if the configuration file is configured by using protobuf, the data is packed by the protobuf module, after the processed data enters the SOME/IP core module, the SOME/IP packet header data and verification data are packed according to the data format of the SOME/IP through the Message module 66, then the service_discovery module 63 provides Routing information for the Routing module 62 through a broadcast service discovery function, the data is sent to the end point module 64 for processing after the Routing module 62 selects the correct route, the e2e_protection module 65 provides safe point-to-point communication protection for the end point module 64, the data is finally sent to the ECU2 through the end point module 64, and the ECU2 obtains the original data in an inverse order.

When the configuration file is communicated by using the IPC, original data is sent from the app1 in the ECU1, if the protobuf package is opened in the configuration file, the data is processed by the protobuf module, and the processed data enters the IPC communication module 7. If the IPC channel selected by the configuration file is the FIFO communication module 71, the data will enter the same ECU through the FIFO communication module 71, that is, app2 of ECU1, and app2 of ECU1 obtains the original data in reverse order; if the IPC channel selected by the configuration file is the socket communication module 72, the data will enter the same ECU through the socket communication module 72, that is, app2 of ECU1, and app2 of ECU1 obtains the original data in a reverse order method; if the IPC channel selected by the configuration file is the shared memory communication module 73, the data will enter the same ECU through the shared memory communication module 73, that is, app2 of ECU1, and app2 of ECU1 obtains the original data in a reverse order method; if the IPC channel selected by the configuration file is the message queue communication module 74, the data will enter the same ECU via the message queue communication module 74, that is, app2 of ECU1, and app2 of ECU1 obtains the original data in reverse order.

When the configuration file is communicated by hardware, original data is sent from the app1 in the ECU1, if protobuf packaging is started in the configuration file, the data is processed by the protobuf module, and the processed data enters the hardware communication module. If the hardware channel selected by the configuration file is the serial port communication module 81, the data enter the app2 of the ECU2 through the serial port communication module 81, and the app2 of the ECU2 obtains the original data according to the reverse order method; if the hardware channel selected by the configuration file is the SPI communication module 82, the data enters the app2 of the ECU2 through the SPI communication module 82, and the app2 of the ECU2 obtains the original data according to a reverse sequence method; if the hardware channel selected by the configuration file is the CAN serial port communication module 81, the data enter the app2 of the ECU2 through the CAN communication module 83, and the app2 of the ECU2 obtains the original data according to a reverse sequence method; if the hardware channel selected by the configuration file is the inter-core communication module 84, the data will enter the app2 of the ECU2 through the inter-core communication module 84, and the app2 of the ECU2 obtains the original data in a reverse order method; if the hardware channel selected by the configuration file is the I2C communication module 85, the data will enter the app2 of the ECU2 through the I2C communication module 85, and the app2 of the ECU2 obtains the original data in an inverse order.

The foregoing description of the preferred embodiments of the invention is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the invention.

Claims (8)

1. The utility model provides a vehicle gateway intermediate layer based on SOME/IP communication which characterized in that: the vehicle-mounted gateway middle layer comprises an interface layer and an implementation layer, wherein the interface layer is used for providing an interface for the application of the ECU, and the implementation layer is used for providing a communication channel for the application of the ECU;

the interface layer comprises an SOME/IP interface (1), an IPC interface (2) and a Hardware Communicate interface (3);

the implementation layer comprises a general function module (4) and a communication function module (5), the general function module (4) comprises a utility module (41), a log & trace module (42) and a configuration module (43),

-said utility module (41) is adapted to provide a generic function;

the log & trace module (42) is used for carrying out log initialization and trace server initialization according to parameters stored by the configuration module (43), providing log output control and carrying out real-time log tracking function by connecting a client with a server;

the configuration module (43) is used for reading the configuration file, storing the log level of the log & trace module, setting the log file and initializing parameters of the trace server according to the configuration file, selecting a communication interface, and storing attribute parameters of the communication interface;

the communication function module (5) comprises a SOME/IP core module (6), an IPC communication module (7) and a hardware interface communication module (8),

the SOME/IP core module (6) is used for establishing a communication channel of SOME/IP, providing a function of SOME/IP communication and being in signal connection with the SOME/IP interface (1);

the IPC communication module (7) is used for establishing an IPC communication channel, providing an IPC communication function and being in signal connection with the IPC interface (2);

the hardware interface communication module (8) is used for establishing a hardware communication channel, providing the capability of receiving and transmitting data through a hardware interface, and is in signal connection with the Hardware Communicate interface (3).

2. The SOME/IP communication based vehicular gateway interface of claim 1 wherein: the SOME/IP core module (6) comprises a running module (61), a Routing module (62), a service_discovery module (63), an endpoint module (64) and an e2e_protection module (65),

the run time module (61) is used for resource creation;

the Routing module (62) is configured to provide a synchronous communication or asynchronous communication function of services, events and event groups defined in the SOME/IP protocol, and management of data and states of the services, events and event groups, and provide an interface for the running module (61);

the service_discovery module (63) provides a service discovery function in the SOME/IP protocol, wherein the service discovery function comprises service discovery, service subscription, event group processing and service discovery data package, and provides an interface for the Routing module (62);

the endpoint module (64) is used for performing socket management and data packet transceiving on an IP endpoint, TCP or UDP, providing a network communication channel function of TCP unicast or UDP unicast, multicast and broadcast, and providing interfaces for the Routing module (62) and the service_discovery module (63);

the e2e_protection module (65) provides communication protection for an endpoint module (64).

3. The SOME/IP communication based vehicular gateway interface of claim 2, wherein: the IPC communication module (7) comprises a FIFO communication module (71), a socket communication module (72), a shared memory communication module (73) and a message queue communication module (74),

the FIFO communication module (71) uses named pipe communication to provide communication among different processes in the ECU;

the socket communication module (72) provides a TCP or UDP communication interface to carry out communication between an ECU internal process or the ECU and the ECU;

the shared memory communication module (73) is used for creating a shared memory segment and providing communication among different processes in the ECU;

the message queue communication module (74) is used for communicating by using the message queue of the kernel to provide communication among different processes in the ECU.

4. A vehicular gateway interface based on SOME/IP communication according to claim 3, characterized in that: the hardware interface communication module (8) comprises a serial port communication module (81), an SPI communication module (82), a CAN communication module (83) and an inter-core communication module (84),

the serial communication module (81) is used as a serial interface for packaging an operating system;

the SPI communication module (82) is used for packaging an SPI interface provided by an operating system;

the CAN communication module (83) is used as a CAN interface provided by a packaging operation system;

the inter-core communication module (84) serves as an inter-core communication interface provided by the package chip manufacturer.

5. The SOME/IP communication based vehicular gateway interface of claim 4 wherein: the hardware interface communication module (8) further comprises an I2C communication module (85), the I2C communication module (85) serving as an I2C interface provided by the packaged operating system.

6. The SOME/IP communication based vehicular gateway interface of claim 5 wherein: the SOME/IP core module (6) further comprises a Message module (66), wherein the Message module (66) is used for packaging the Message header and the Message content according to the SOME/IP protocol.

7. The SOME/IP communication based vehicular gateway interface of claim 6 wherein: the general function module (4) also comprises a protobuf module (44) and a json module (45),

the protobuf module (44) is used for repackaging an interface of the open source library into a single instance class through the open source library protobuf to realize package and unpackage;

the json module (45) is used for repackaging the interfaces of the open source library into single instance types to realize package and unpackage.

8. The SOME/IP communication based vehicular gateway interface of claim 5 wherein: the communication function module (5) further comprises a protobuf module (44), a json module (45) and a Message module (66), wherein the protobuf module (44) and the json module (45) are arranged below the Message module (66);

the Message module (66) is used for packaging the Message header and the Message content according to the SOME/IP protocol;

the protobuf module (44) is used for repackaging an interface of the open source library into a single instance class through the open source library protobuf to realize package and unpackage;

the json module (45) is used for repackaging the interfaces of the open source library into single instance types to realize package and unpackage.