Vehicle-mounted V2X protocol stack supporting heterogeneous network converged communication

Abstract

The invention provides a vehicle-mounted V2X protocol stack supporting heterogeneous network converged communication, and relates to the field of vehicle-mounted V2X protocol stacks, the protocol stack is set through a software architecture, and the software architecture adopts a hierarchical design and comprises an access layer, a network layer server, middleware, a network layer client and an application layer from bottom to top, according to the interface calling relation in each layer, only one-way calling is carried out on the adjacent layer, one-way interface calling is carried out from the upper layer to the lower layer, and cross-layer calling cannot be carried out; the access layer comprises an access layer abstract interface and an access layer implementation, and the dynamic configuration access technology and suppliers are supported through the access layer abstract interface and the access layer implementation; the access layer abstract interface comprises a request type interface and an indication type interface. The invention provides a V2X protocol stack which is compatible downwards, expands different access technologies, can upwards provide a unified application interface, adopts a service-oriented architecture inside, can support simultaneous service providing for multiple applications, and can dynamically select network service types.

Description

Technical Field

[0001] The present invention relates to the field of vehicle-mounted V2X protocol stacks, and in particular to a software architecture and key implementation method of a vehicle-mounted V2X protocol stack supporting heterogeneous network converged communications. Background Art

[0002] Intelligent connected vehicles refer to a new generation of vehicles that organically combine the Internet of Vehicles and smart cars. They serve as an important carrier of a new round of scientific and technological revolution and industrial transformation.

[0003] "Networking" is one of the core elements of intelligent connected vehicles. Using the Internet of Vehicles technology, vehicles can exchange and share real-time information with the external environment, linking together the elements of traffic participation such as "car-road-cloud-people". Application scenarios derived from real-time exchange and sharing of information data can improve driving safety, increase traffic efficiency, provide information services, and collaboratively realize autonomous driving.

[0004] At present, there are many wireless communication access technologies for Internet of Vehicles at home and abroad, such as 4G / 5G, LTE-V2X, NR-V2X, DSRC, EUHT, GNSS, etc. Moreover, different access technologies, or the same access technologies in different countries and regions, have corresponding upper-layer V2X protocol stack standards. These different access technologies and V2X protocol stacks have built the current heterogeneous Internet of Vehicles network.

[0005] From the perspective of vehicle-road-cloud integrated applications, the business data content carried in the above heterogeneous networks is actually repeated, crossed, and complementary. If heterogeneous network converged communication can be supported, applications can simultaneously obtain more data in heterogeneous networks, which will bring significant benefits. For example, from the perspective of communication performance, the first-come-first-served + deduplication mechanism for repeated data can reduce latency and packet loss rate, thereby enhancing data availability and reliability; from the perspective of data quality, the fusion method for crossed and complementary data can improve data credibility and expand data content; from the perspective of infrastructure utilization and application service area, because the external infrastructure coverage of various access technologies has overlapping and complementary areas, the use of multiple access technologies at the same time can improve infrastructure utilization on the one hand, and expand the area range of applications to provide services to users on the other hand. However, for vehicles currently equipped with multi-mode terminals, when facing the above heterogeneous networks, most of the V2X protocol stacks are chimney-style software architectures, and services and data are difficult to share, and they all operate independently, which makes it relatively complex and difficult for applications to achieve the effect of heterogeneous network converged communication. Therefore, it is necessary to design a V2X protocol stack that is backward compatible and extensible with different access technologies, can provide a unified application interface upward, adopts a service-oriented architecture internally, can support the provision of services to multiple applications at the same time, and can dynamically select the network service type, thereby providing heterogeneous network converged communication capabilities for vehicles equipped with multi-mode terminals. Summary of the invention

[0006] In order to provide heterogeneous network converged communication capabilities for vehicles equipped with multi-mode terminals, the present invention provides a V2X protocol stack that is downward compatible and extensible with different access technologies, can provide a unified application interface upward, adopts a service-oriented architecture internally, can support the provision of services for multiple applications at the same time, and can dynamically select the network service type.

[0007] The technical solution of the present invention is implemented as follows: an on-vehicle V2X protocol stack supporting heterogeneous network converged communication, including a protocol stack set up through a software architecture, the software architecture adopts a layered design, and includes from bottom to top: an access layer, a network layer server, a middleware, a network layer client, and an application layer, and the interface call relationship in each layer is a one-way call to the adjacent layer, and a one-way interface call is made from the upper layer to the lower layer, and cross-layer calls cannot be made; The access layer includes an access layer abstract interface and an access layer implementation, and supports dynamic configuration of access technologies and suppliers through the access layer abstract interface and the access layer implementation; The access layer abstract interface includes a request class interface and an indication class interface, wherein the request class interface includes: initialization, deinitialization, creation of send / receive stream, update of send / receive stream parameters, destruction of send / receive stream, sending data, receiving data, and update of access layer configuration parameters; wherein the indication class interface includes: send / receive stream state change, access layer indicator parameter change, and access layer configuration parameter change; The access layer implementation is used to perform specific adaptation implementation for various access technologies or various module supplier solutions. The access technologies include: LTE-V2X, NR-V2X, EUHT, DSRC and GNSS.

[0008] This in-vehicle V2X protocol stack that supports heterogeneous network converged communications solves the interoperability and dynamic configuration issues of in-vehicle communication systems under multiple access technologies and supplier environments, and achieves flexible and efficient communication protocol management through layered design and interface abstraction.

[0009] Compared with existing technologies, this vehicle-mounted V2X protocol stack has obvious advantages in architecture design. Traditional V2X protocol stacks are usually tailored for specific access technologies or communication standards, lacking flexibility and scalability. With the development of vehicle-mounted communication technology, multiple access technologies (such as LTE-V2X, NR-V2X, DSRC, etc.) have gradually emerged, and different automobile manufacturers or communication service providers use different technical solutions. This heterogeneity makes the traditional protocol stack appear stretched when facing multiple technologies and difficult to meet the needs.

[0010] This protocol stack adopts a layered design, which clearly defines multiple layers such as the access layer, network layer server, middleware, network layer client, and application layer. The interface call relationship between each layer is a one-way call, which avoids the complexity of cross-layer calls and simplifies the design and implementation of the system. This structured design not only makes the responsibilities between layers clearer, but also enhances the maintainability and scalability of the system. Developers can modify or expand a certain layer without affecting other layers, so as to quickly respond to market and technological changes.

[0011] The access layer design of this protocol stack fully considers the needs of dynamic configuration. Traditional protocol stacks often have limitations in supporting access technologies and are difficult to adapt to rapidly changing communication environments. The access layer of this system includes access layer abstract interfaces and access layer implementations, which support flexible configuration of different access technologies and vendors. The access layer abstract interface provides rich functions through request class interfaces and indication class interfaces, enabling the system to dynamically adjust the access mode according to real-time needs. For example, the system can switch between different access technologies (such as LTE-V2X and DSRC) to adapt to different network conditions and application scenarios. This flexibility is unmatched by traditional protocol stacks.

[0012] The design of the access layer implementation enables the system to be specifically adapted to various access technologies or module suppliers. Traditional V2X protocol stacks often require independent development and debugging for each access technology, resulting in high development costs and long development cycles. However, this system uses a modular design to enable different access technologies to be adapted through the access layer implementation, reducing development difficulty and time. This adaptation mechanism not only improves the versatility of the system, but also provides convenient conditions for the introduction of future access technologies. Enterprises can quickly integrate new technologies without significantly changing the system architecture.

[0013] The layered design of the protocol stack and the implementation of abstract interfaces also provide guarantees for the security and reliability of the system. Traditional protocol stacks have strong coupling between different layers. If a problem occurs in one layer, it may affect the stability of the entire system. This protocol stack ensures the independence of each layer through clear layer division and one-way calls, reducing the overall risk of system failure. This design not only improves the robustness of the system, but also provides a good foundation for subsequent security enhancement measures (such as authentication, encryption, etc.).

[0014] As a preferred implementation, the network layer server includes a network management abstract interface, a network management implementation, a network protocol abstract interface, a network protocol implementation and an adaptation layer, and the network layer server supports dynamic configuration of network layer standards; The network management abstract interface includes management request interface and management indication interface, wherein the management request interface includes initialization, deinitialization, registration / deregistration of application, adding / updating / deleting service request, obtaining information base data, obtaining network service status; the management indication interface includes information base data change, network service status change; The network management implementation is used for specific adaptation of network management for different network layers; The network protocol abstract interface includes a protocol request interface and a protocol indication interface, wherein the protocol request interface includes initialization, deinitialization, message sending, and updating of data sublayer configuration parameters; the protocol indication interface includes receiving messages and changes in data sublayer configuration parameters; The network protocol implementation is used to perform specific adaptation of the network protocol for different network layers; The network adaptation layer is used to provide the interaction adaptation function between the access layer and the network layer server, including interface adaptation and data escape.

[0015] As a preferred implementation, the middleware has a built-in service bus; the service bus provides inter-process communication or inter-system communication, and the service bus can be cross-language and multiple communication modes can be selected to perform many-to-many communication between the client and the server.

[0016] As a preferred implementation, the network layer client includes a network service client abstract interface and a network service client implementation, and the network layer client is capable of dynamically configuring network services; The network service client abstract interface includes a client request class interface and a client indication class interface, wherein the client request class interface includes initialization, deinitialization, registration / deregistration of applications, adding / updating / deleting service requests, obtaining network service information, obtaining network service status, updating network service configuration parameters, and sending messages; the client indication class interface includes: network service information changes, network service status changes, network service configuration parameter changes, and receiving messages; The network service client is implemented to perform client-specific adaptation for network layers of different network standards.

[0017] As a preferred implementation, the application layer includes an application interface, a state machine, a service management module, a converged communication control module and a message codec; The application interface is used to provide a unified functional interface to application developers, including request interfaces: initialization, deinitialization, message sending, obtaining network service information, obtaining state machine status; including indication interfaces: receiving messages, network service information changes, state machine status changes; The state machine is used to provide internal state management functions of the message layer, including: event response, state transition judgment, and state transition processing; The service management module is used to provide the creation and destruction of components within the message layer and the control function of uplink and downlink data processing flow; The fusion communication control module controls one or more network layer clients according to the application configuration, provides fusion and distribution processing functions for downlink data, and provides fusion and deduplication processing functions for uplink data; The message codec is used to provide message encoding and decoding functions, and internally supports encoding and decoding processing of multiple data formats, including: ASN.1, protobuf, JSON and XML, and dynamically selects the corresponding processing method according to the protocol requirements of different messages.

[0018] As a preferred implementation, the network layer server and the network layer client implement inter-process communication or inter-system communication through the middleware, the sending end encodes or serializes the communication data, and the receiving end decodes or deserializes the communication data.

[0019] After adopting the above technical scheme, the beneficial effects of the present invention are: the present invention can support the implementation of multiple access technologies and V2X protocol stack standards, and can provide heterogeneous network converged communication services for multiple applications at the same time, so that applications can obtain more data in heterogeneous networks, thereby bringing the following significant benefits: from the perspective of communication performance, a first-come-first-served + deduplication mechanism is adopted for duplicate data, which can reduce latency and packet loss rate, thereby enhancing data availability and reliability; from the perspective of data quality, a fusion method is adopted for cross- and complementary data, which can improve data credibility and expand data content; from the perspective of infrastructure utilization and application service area, because the external infrastructure coverage of various access technologies has overlapping areas and complementary areas, the use of multiple access technologies at the same time can improve the utilization of infrastructure on the one hand, and expand the regional scope of application services for users on the other hand.

[0020] Enhanced the flexibility and adaptability of the vehicle communication system. With the development of intelligent transportation and autonomous driving technology, the demand for vehicle communication is increasing, and the limitations of traditional protocol stacks are gradually emerging. This protocol stack enables the vehicle communication system to quickly adapt to new technologies and market demands through flexible layered design and dynamic configuration capabilities. This flexibility not only improves the market competitiveness of the system, but also provides a guarantee for future technological innovation and expansion.

[0021] The efficiency of the system has been significantly improved. By supporting dynamic configuration of multiple access technologies, the system can automatically select the optimal access method based on the actual network environment and communication needs. This intelligent selection mechanism not only improves the reliability of communication, but also optimizes the efficiency of resource utilization. For example, when the network load is high, the system can give priority to using access technologies with lower loads for communication, thereby ensuring communication quality and stability. This efficient resource management method enables the in-vehicle communication system to better serve various application scenarios and improve user experience.

[0022] The modular design of the protocol stack significantly reduces the system maintenance cost and development difficulty. Due to the independence between the layers, developers can independently develop and test specific access technologies or functions, reducing the complexity of system integration. This design that reduces maintenance costs allows companies to focus more on the development of core technologies, improving overall R&D efficiency and market response speed.

[0023] The security and reliability of the system have also been improved. Through clear hierarchical division and one-way interface calls, the system can quickly locate the source of the fault when a problem occurs, and take corresponding measures to ensure the stability of the overall system. This high-reliability design enables the vehicle communication system to maintain stable operation in various complex environments, enhancing users' trust in the system. The ability to support heterogeneous networks provides a good foundation for the development of the future Internet of Vehicles ecosystem. With the continuous evolution of new-generation communication technologies such as 5G and 6G, vehicle communications will face more challenges and opportunities. The design of this protocol stack not only adapts to the current multiple access technologies, but also provides the possibility of accessing new technologies in the future, enabling the vehicle communication system to maintain its leading position in a rapidly changing technological environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0025] Figure 1 This is a software architecture diagram of the present invention; Figure 2 This is an example diagram of the program composition and the relationship between programs of the present invention. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0027] Example: like Figure 1~2 As shown, a vehicle-mounted V2X protocol stack software architecture supporting heterogeneous network converged communication is provided. The software architecture adopts a layered design and includes, from bottom to top, an access layer (10), a network layer server (20), a middleware (30), a network layer client (40), and an application layer (50).

[0028] The access layer (10) includes: an access layer abstract interface (101) and an access layer implementation (102), and supports dynamic configuration of access technologies and suppliers; The access layer abstract interface (101) highly abstracts the interface capabilities provided by multiple access technologies in heterogeneous networks, including request interfaces: initialization, deinitialization, creation of send / receive streams, update of send / receive stream parameters, destruction of send / receive streams, sending data, receiving data, and update of access layer configuration parameters; and indication interfaces: change of send / receive stream status, change of access layer indicator parameters, and change of access layer configuration parameters; The access layer implementation (102) is used to make specific adaptation implementations for different access technologies or different module supplier solutions. The adaptation is performed through adaptive access technology. The adaptive access technology is divided into adaptive access technology X, adaptive access technology Y and adaptive access technology Z. Each adaptive access technology has an access technology program built in. The access technology program includes access technology program X and access technology program Y. The specific access technology program is formed by any combination of LTE-V2X, NR-V2X, EUHT, DSRC, GNSS, etc.; module suppliers include Quectel, Qualcomm, Nufront, etc. The access layer (10) provides the upper layer with a method for creating the access layer through the abstract factory mode, and selects a specific access technology or supplier according to parameters internally, thereby realizing dynamic configuration of the access layer. At the same time, a set of indicator class interfaces is provided to the upper layer through the observer mode, thereby realizing that data flow can be transmitted from bottom to top without violating the principle that the lower layer does not call the upper layer interface.

[0029] The network layer server (20) includes: a network management abstract interface (201), a network management implementation (202), a network protocol abstract interface (203), a network protocol implementation (204), an adaptation layer (205), and supports dynamic configuration of network layer standards; The network management abstract interface (201) highly abstracts the management sublayer interface capabilities of the network layer in the heterogeneous network, including request interfaces: initialization, deinitialization, application registration / deregistration, adding / updating / deleting service requests, obtaining information base data, obtaining network service status; including indication interfaces: information base data changes, network service status changes; The network management implementation (202) is used to implement specific adaptations related to network management in accordance with different network layer standard requirements, for example, referring to the YD / T 3707-2020 standard to implement DSMP (Dedicated Short Message Protocol); The network protocol abstract interface (203) highly abstracts the data sublayer interface capabilities of the network layer in the heterogeneous network, including request interfaces: initialization, deinitialization, message sending, and updating of data sublayer configuration parameters; and indication interfaces: receiving messages and changes in data sublayer configuration parameters; The network protocol implementation (204) is used to implement specific adaptations related to network protocols in accordance with different network layer standard requirements, for example, referring to the YD / T 3707-2020 standard to implement DSMP (Dedicated Short Message Protocol); The network adaptation layer (205) is used to provide an interactive adaptation function between the access layer (10) and the network layer server (20), including interface adaptation and data escape, for example, indicating the mapping of the network standard corresponding to the access technology, the network layer application identifier and the access layer destination layer 2 identifier.

[0030] The management sublayer composed of the network management abstract interface (201) and the network management implementation (202), and the data sublayer composed of the network protocol abstract interface (203) and the network protocol implementation (204), respectively provide the creation method to the upper layer through the abstract factory mode, and select the specific network standard according to the parameters internally, so as to realize the dynamic configuration of the network standard. At the same time, a set of indicator class interfaces is provided to the upper layer through the observer mode, so as to realize the data flow can be transmitted from bottom to top, without violating the principle that the lower layer does not call the upper layer interface.

[0031] Wherein, the middleware (30) comprises: a service bus (301); The service bus (301) is used to provide inter-process communication (IPC) or inter-system communication (RPC) capabilities. It has the characteristics of cross-language, high transmission performance, support for multiple communication modes, and many-to-many communication between the client and the server. For example, the ZMQ communication framework is used to implement the service bus, which supports two modes: request-response and subscription-publish. The communication type (inter-process communication / inter-system communication) and communication configuration (node / IP address / port number) are managed in the form of configuration files, which can meet the requirements of flexible configuration and deployment. At the same time, the transmitted data is encoded or serialized. For example, data formats such as protobuf and JSON are used to meet the requirements of compressed data space and cross-system distributed deployment of applications / services.

[0032] The network layer client (40) includes: a network service client abstract interface (401), a network service client implementation (402), in which the network service is embodied as a network service N and a network service M, and supports dynamic configuration of network service capabilities; The network service client abstract interface (401) highly abstracts the network service interface capabilities in heterogeneous networks, including request interfaces: initialization, deinitialization, registration / deregistration of applications, adding / updating / deleting service requests, obtaining network service information, obtaining network service status, updating network service configuration parameters, and sending messages; including indication interfaces: network service information changes, network service status changes, network service configuration parameter changes, and receiving messages; The network service client implementation (402) is used to implement specific adaptation related to the client for network layers of different network standards, wherein the network standards include network standard M and network standard N.

[0033] The network layer client (40) provides a creation method to the upper layer through the abstract factory mode, selects a specific network service according to parameters, thereby realizing dynamic configuration of the network service, and can create multiple clients corresponding to different network services, so that the application can interact with multiple network services. At the same time, a set of indicator class interfaces is provided to the upper layer through the observer mode, so that data flow can be transmitted from bottom to top without violating the principle that the lower layer does not call the upper layer interface.

[0034] The application layer (50) includes: an application interface (501), a state machine (502), a service management module (503), a converged communication control module (504), and a message codec (505). In actual application, it is divided into application A, application B, and application C.

[0035] The application interface (501) is used to provide a set of unified functional interfaces to application developers, including request interfaces: initialization, deinitialization, message sending, network service information acquisition, state machine status acquisition; and indication interfaces: message receiving, network service information change, state machine status change; The state machine (502) is used to provide internal state management functions of the message layer, including: event response, state transition judgment, and state transition processing; The service management module (503) is used to provide the creation and destruction of components within the message layer and the control function of uplink and downlink data processing flow; The fusion communication control module (504) controls one or more network layer clients according to the application configuration, provides fusion and distribution processing functions for downlink data, and provides fusion and deduplication processing functions for uplink data.

[0036] Furthermore, the deduplication processing function sequentially goes through: calculating data summary processing, comparing historical data processing, and updating historical data processing; specifically, the calculation of data summary uses a hash algorithm to process the data to achieve the purpose of compressing data storage space. The selection of the hash algorithm only needs to consider data processing performance and collision probability, without considering security. For example, the MD5 algorithm can be used; comparing historical data processing is to compare the current data summary with the historical data summary within a period of time, and then determine whether it is duplicate data. The comparison processing needs to consider the time complexity of finding elements. For example, the historical data summary can be stored using the std::unordered_set container, and the find() method is used to find whether the target element exists. The average time complexity of finding elements is O(1); updating historical data processing means storing the current data summary that does not belong to duplicate data in the historical data, and aging the historical data after a period of time of △t, and the time complexity of inserting and deleting elements needs to be considered. For example, a double list can be used to alternately store historical data. After a period of △t, the list is switched and the list to be used is cleared. The list can be implemented using the std::unordered_set container, and the insert() method is used to insert elements and the clear() method is used to clear elements. The average time complexity of inserting and deleting elements is O(1). The message codec (505) is used to provide message encoding and decoding functions, and internally supports encoding and decoding processing of multiple data formats, including: ASN.1, protobuf, JSON, XML, etc., and can dynamically select processing methods according to the protocol requirements of different messages. For example, with reference to T / CSAE 53-2020 or T / CSAE 157-2020 standards, support for the first and second phase application message sets of the cooperative intelligent transportation system vehicle communication system is achieved.

[0037] The access layer (10), the network layer server (20), the middleware (30), the network layer client (40), and the application layer (50) are specifically distributed in the program as follows: Figure 2 Specifically, the application includes: the middleware (30), the network layer client (40), and the application layer (50); the network service program includes a network service program M and a network service program N, and the specific network service program includes: an access layer (10), the network layer server (20), and the middleware (30), and the application and the network service program perform many-to-many communication interaction.

[0038] The middleware (30) in the technical solution has a built-in service bus (301), and this design has obvious advantages over the prior art. Traditional systems usually rely on specific communication protocols and frameworks for inter-process or inter-system communication, which often limits the flexibility and scalability of the system. The communication methods in the prior art are often single and cannot meet the needs of different application scenarios. However, by introducing the service bus (301), the present solution realizes the support of cross-language and multiple communication modes, so that the client and the server can flexibly carry out many-to-many communication. This cross-language capability means that components written in different development languages ​​can interact seamlessly, greatly enhancing the compatibility of the system. At the same time, the many-to-many communication capability enables multiple clients and servers to interact simultaneously, improving the concurrent processing capability and resource utilization of the system. In addition, the introduction of the service bus enables the system to more easily integrate new services and functions in the future, reducing the impact on the original system and improving the flexibility and maintainability of the overall architecture. Therefore, compared with the prior art, the present technical solution has significantly improved the flexibility, scalability and compatibility of inter-system communication.

[0039] The design of the network layer client (40) includes a network service client abstract interface (401) and a network service client implementation (402). Compared with the prior art, this structure has higher flexibility and adaptability in dynamically configuring network services. The client implementation in the prior art is often static and cannot be adjusted in real time according to changes in the network environment, resulting in the performance and stability of the client being affected under different network conditions. The network layer client (40) of this solution can dynamically configure network services, which means that the client can automatically adjust its service request and response mechanism according to the real-time network status. The network service client abstract interface (401) defines a series of request class and indication class interfaces, including initialization, deinitialization, registration / derailment of applications, and addition, deletion, modification, and query of service requests. The diversity and flexibility of these interfaces enable developers to more conveniently implement complex network interactions. At the same time, the client indication class interface can timely feedback the status changes of the network service, further enhancing the real-time and responsiveness of the system. The network service client implementation (402) is specifically adapted to different network standards. This adaptation capability enables the system to support multiple network protocols and improves its adaptability in a diverse network environment. Therefore, compared with the existing technology, this solution has significantly improved the dynamic configuration capability, flexibility and diversity of the network layer client.

[0040] In the design of the application layer (50), the structure consisting of the application interface (501), state machine (502), business management module (503), fusion communication control module (504) and message codec (505) has a more comprehensive and efficient function implementation compared to the prior art. In the prior art, the design of the application layer is often relatively simple, and the coupling between functional modules is high, making it difficult to achieve flexible function expansion and maintenance. However, this solution provides a standardized functional interface for application developers by providing a unified application interface (501), thereby simplifying the application development process. The introduction of the state machine (502) enables the message layer to effectively manage the state, handle event response and state migration, and improve the stability and reliability of the system. The business management module (503) is responsible for the creation and destruction of components and the control of data processing processes, thereby enhancing the organization and manageability of the system. The design of the fusion communication control module (504) enables the system to centrally control multiple network layer clients, thereby improving the efficiency and consistency of data processing. The message codec (505) supports encoding and decoding of multiple data formats, and can dynamically select processing methods according to the requirements of different protocols, thereby enhancing the compatibility and flexibility of the system. Therefore, compared with the prior art, this solution has significantly improved the comprehensiveness, modularity and flexibility of the application layer.

[0041] In the process of realizing inter-process communication or inter-system communication between the network layer server (20) and the network layer client (40) through the middleware (30), the difference between the present solution and the prior art is mainly reflected in the processing method of data encoding and decoding. In the prior art, the data transmission between the server and the client often lacks a unified encoding and decoding mechanism, which may cause format mismatch or data loss when exchanging data between different components. However, the present solution clearly stipulates that the sending end encodes or serializes the communication data, and the receiving end decodes or deserializes the communication data, thereby ensuring the integrity and consistency of the data during the transmission process. This clear processing mechanism not only improves the efficiency of data exchange, but also reduces the potential errors caused by inconsistent data formats. In addition, through the introduction of middleware, the system can flexibly adapt the data processing method under different network environments and protocols, thereby enhancing the robustness and adaptability of the system. Therefore, compared with the prior art, the present solution has made significant improvements in the standardization, integrity and system adaptability of data processing.

[0042] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A vehicle-mounted V2X protocol stack supporting heterogeneous network converged communication, characterized in that: The protocol stack is set up through a software architecture, and the software architecture adopts a layered design, including from bottom to top: an access layer (10), a network layer server (20), a middleware (30), a network layer client (40) and an application layer (50), and the interface call relationship in each layer is a one-way call to the adjacent layer, and a one-way interface call is made from the upper layer to the lower layer, and cross-layer calls cannot be made; The access layer (10) includes an access layer abstract interface (101) and an access layer implementation (102), and supports dynamic configuration of access technology and supplier through the access layer abstract interface (101) and the access layer implementation (102); The access layer abstract interface (101) comprises a request class interface and an indication class interface, wherein the request class interface comprises: initialization, deinitialization, creation of a send / receive stream, updating send / receive stream parameters, destruction of a send / receive stream, sending data, receiving data, and updating access layer configuration parameters; wherein the indication class interface comprises: change of a send / receive stream state, change of an access layer indicator parameter, and change of an access layer configuration parameter; The access layer implementation (102) is used to perform specific adaptation implementation for various access technologies or various module supplier solutions, and the access technologies include: LTE-V2X, NR-V2X, EUHT, DSRC and GNSS.

2. The vehicle-mounted V2X protocol stack supporting heterogeneous network converged communication according to claim 1, characterized in that: The network layer server (20) comprises a network management abstract interface (201), a network management implementation (202), a network protocol abstract interface (203), a network protocol implementation (204) and an adaptation layer (205), and the network layer server (20) supports dynamic configuration of network layer standards; The network management abstract interface (201) includes a management request interface and a management indication interface, wherein the management request interface includes initialization, deinitialization, application registration / deregistration, adding / updating / deleting service requests, obtaining information base data, and obtaining network service status; the management indication interface includes information base data changes and network service status changes; The network management implementation (202) is used to perform specific adaptation of network management for different network layers; The network protocol abstract interface (203) includes a protocol request interface and a protocol indication interface, wherein the protocol request interface includes initialization, deinitialization, message sending, and updating of data sublayer configuration parameters; the protocol indication interface includes receiving messages and data sublayer configuration parameter changes; The network protocol implementation (204) is used to perform specific adaptation of the network protocol to different network layers; The network adaptation layer (205) is used to provide an interactive adaptation function between the access layer (10) and the network layer server (20), including interface adaptation and data escape.

3. The vehicle-mounted V2X protocol stack supporting heterogeneous network converged communication according to claim 1, characterized in that: The middleware (30) has a built-in service bus (301); the service bus (301) provides inter-process communication or inter-system communication, and the service bus can be cross-language and multiple communication modes can be selected to perform many-to-many communication between the client and the server.

4. The vehicle-mounted V2X protocol stack supporting heterogeneous network converged communication according to claim 1, characterized in that: The network layer client (40) includes a network service client abstract interface (401) and a network service client implementation (402), and the network layer client (40) is capable of dynamically configuring network services; The network service client abstract interface (401) includes a client request class interface and a client indication class interface, wherein the client request class interface includes initialization, deinitialization, registration / deregistration of applications, adding / updating / deleting service requests, obtaining network service information, obtaining network service status, updating network service configuration parameters, and sending messages; The client indication interface includes: network service information change, network service status change, network service configuration parameter change, and message reception; The network service client is implemented (402) to perform client-specific adaptation for network layers of different network standards.

5. The vehicle-mounted V2X protocol stack supporting heterogeneous network converged communication according to claim 1, characterized in that: The application layer (50) includes an application interface (501), a state machine (502), a service management module (503), a converged communication control module (504) and a message codec (505); The application interface (501) is used to provide a unified functional interface to application developers, including request interfaces: initialization, deinitialization, message sending, obtaining network service information, obtaining state machine status; and indication interfaces: receiving messages, network service information changes, state machine status changes; The state machine (502) is used to provide internal state management functions of the message layer, including: event response, state transition judgment, and state transition processing; The service management module (503) is used to provide the creation and destruction of components within the message layer and the control function of uplink and downlink data processing flow; The fusion communication control module (504) controls one or more network layer clients according to the application configuration, provides fusion and distribution processing functions for downlink data, and provides fusion and deduplication processing functions for uplink data; The message codec (505) is used to provide message encoding and decoding functions, and internally supports encoding and decoding processing of multiple data formats, including: ASN.1, protobuf, JSON and XML, and dynamically selects corresponding processing methods according to the protocol requirements of different messages.

6. The vehicle-mounted V2X protocol stack supporting heterogeneous network converged communication according to claim 1, characterized in that: The network layer server (20) and the network layer client (40) implement inter-process communication or inter-system communication through the middleware (30), the sending end encodes or serializes the communication data, and the receiving end decodes or deserializes the communication data.

Images