In-vehicle Ethernet data authentication method and system based on Classic Autosar platform

Abstract

The present invention discloses a vehicle-mounted Ethernet data authentication method and system based on the Classic Autosar platform. The Classic Autosar platform is deployed on both the vehicle central controller and the domain controller, and a data authentication layer is added. During the transmission of Ethernet application data, the data authentication layer configures and authenticates the application data's authentication metadata. The application data, data message header, and configured authentication metadata are then encapsulated for data transmission. The authentication metadata configuration includes information such as the local node identifier, the peer node identifier, the SWC service ID, the BSW service ID, and the data domain. The present invention implements vehicle-wide Ethernet data authentication, ensuring normal data transmission of vehicle-mounted application services, avoiding illegal and malicious Ethernet data attacks, ensuring the security of vehicle-mounted Ethernet data transmission, and improving the reliability of the network in the field of autonomous driving.

Description

Technical Field

[0001] The present invention belongs to the field of autonomous driving technology, and in particular relates to a vehicle-mounted Ethernet data authentication method and system based on the Classic Autosar platform. Background Art

[0002] AUTOSAR (AUTotmotive Open System Architecture) is a set of standard protocols developed for automotive technology. It aims to improve the updating and exchange of automotive electronic software systems, while also making it easier and more efficient to manage increasingly complex automotive electronic software systems. This can shorten the development cycle and improve the quality of automotive electronic software.

[0003] The Classic Autosar platform meets the development needs of deeply embedded ECUs, but it cannot meet the growing Ethernet bandwidth and security requirements of in-vehicle networks, making it difficult to securely manage the increasingly diverse Ethernet services. Furthermore, in autonomous vehicle networks, the increasing number of Ethernet services poses a security risk to the in-vehicle Ethernet, potentially leading to network and even complete vehicle system failure. Summary of the Invention

[0004] In order to solve the deficiencies in the prior art, the present invention aims to provide a method and system for authenticating vehicle Ethernet data based on the ClassicAutosar platform.

[0005] To achieve the purpose of the present invention, the technical solution adopted by the present invention is:

[0006] An in-vehicle Ethernet data authentication system based on the Classic Autosar platform includes a central controller and a domain controller. The Classic Autosar platform is deployed on both the central controller and the domain controller, and a data authentication layer is added to the Classic Autosar platform framework.

[0007] During the transmission of Ethernet application data, the data authentication layer configures and authenticates the authentication metadata of the application data; the Classic Autosar platform encapsulates the application data, data packet header and configures the authentication metadata before transmitting the Ethernet application data.

[0008] Furthermore, the data authentication layer configures authentication metadata for application data when sending data; and the data authentication layer performs data authentication on vehicle Ethernet data containing authentication metadata, data packet header, and application data when receiving data.

[0009] Furthermore, the configuration content of the authentication metadata includes the local node identifier, the peer node identifier, the SWC service ID, the BSW service ID, and the data domain information.

[0010] Furthermore, the Classic Autosar platform framework includes the application layer component SWC layer, the runtime environment RTE layer, the basic software BSW layer, and the hardware abstraction MCAL layer; each controller deploys a data authentication layer between the MCAL layer and the BSW layer.

[0011] Furthermore, application data is sent and received through the SWC layer, the RTE layer schedules and switches application services deployed on the controller, the BSW layer provides basic software services, the data authentication layer configures authentication metadata for application data, and the MCAL layer forwards the processed application data to other controllers.

[0012] A method for authenticating vehicle Ethernet data based on the Classic Autosar platform, comprising the following steps:

[0013] In the first step, the vehicle application service on the controller is started, application data is generated, and application data is sent and received through the application layer component SWC layer;

[0014] In the second step, the controller uses the runtime environment (RTE) layer to schedule and switch between different vehicle controller application services and monitor the running status of different application services.

[0015] In the third step, the controller provides basic software services for different in-vehicle application services through the basic software BSW layer, is responsible for Ethernet encapsulation of different application data, and adds data message headers;

[0016] In the fourth step, the controller configures and encapsulates authentication metadata for different application data through the data authentication layer. The data authentication layer of the peer controller receives the data, decodes the authentication metadata, and authenticates the in-vehicle Ethernet data.

[0017] In the fifth step, the controller uses the hardware abstraction MCAL layer to encapsulate the application data that has passed the authentication metadata and data packet header at the hardware driver layer, and forwards it to the connected vehicle controller through the hardware driver; the other end controller receives the data and decodes it at the hardware driver layer.

[0018] Furthermore, in the first step, the application layer component SWC layer also allocates the SWC service ID and the data Domain domain.

[0019] Furthermore, in the third step, the basic software BSW layer also allocates a BSW service ID.

[0020] Furthermore, in the third step, basic software services include OS, TCP / IP, Ethif, DEM, CDD, and Canif.

[0021] Furthermore, in the fifth step, the hardware drivers include Candrv, Ethdrv, and Lindrv.

[0022] The beneficial effect of the present invention is that, compared with the existing technology, the present invention deploys the Classic Autosar platform on both the vehicle central controller and the domain controller, and adds a data authentication layer to the Classic Autosar framework. The data authentication layer configures and authenticates the authentication metadata of the application data, thereby realizing the authentication of the vehicle Ethernet data in the system.

[0023] The present invention implements vehicle-wide Ethernet data authentication by deploying an in-vehicle Ethernet data authentication system based on the Classic Autosar platform on the vehicle controller, thereby ensuring the normal data transmission of in-vehicle application services, avoiding illegal Ethernet data and Ethernet data attacked by malicious attacks, ensuring the security of in-vehicle Ethernet data transmission and normal application services, and improving the reliability of the network in the field of autonomous driving. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 This is a schematic diagram of the in-vehicle Ethernet data authentication system based on the Classic Autosar platform;

[0025] Figure 2 This is the architectural hierarchy diagram of the Classic Autosar platform;

[0026] Figure 3 This is a flowchart of the in-vehicle Ethernet data authentication method based on the Classic Autosar platform. DETAILED DESCRIPTION

[0027] The technical solution of the present invention will be further described below in conjunction with the accompanying drawings and embodiments. The following embodiments are only used to more clearly illustrate the technical solution of the present invention and are not intended to limit the scope of protection of this application.

[0028] like Figure 1 As shown, the in-vehicle Ethernet data authentication system based on the Classic Autosar platform described in the present invention includes a central controller, domain controller 1, domain controller 2 and domain controller 3. The Classic Autosar platform is deployed on the vehicle central controller and the domain controllers, and a data authentication layer is added to the Classic Autosar framework to realize the authentication of the in-vehicle Ethernet data in the system.

[0029] like Figure 2As shown in Figure 1, the Classic Autosar framework includes the application layer component (SWC), runtime environment (RTE), basic software (BSW), and hardware abstraction layer (MCAL). Each controller deploys a data authentication layer between the MCAL and BSW layers in the Classic Autosar framework. The data authentication layer configures and authenticates application data authentication metadata during Ethernet transmission on the Classic Autosar platform.

[0030] The Classic Autosar platform with an added data authentication layer is deployed on the central controller, domain controller 1, domain controller 2, and domain controller 3. It encapsulates application data, data packet headers, and configuration authentication metadata, and has Ethernet data authentication capabilities to authenticate Ethernet data of legitimate application services.

[0031] When sending data, the data authentication layer configures authentication metadata for application data. This metadata includes information such as the local node identifier, peer node identifier, SWC service ID, BSW service ID, and data domain. When receiving data, the data authentication layer authenticates the in-vehicle Ethernet data, which includes the authentication metadata, data packet header, and application data.

[0032] The SWC layer sends and receives application data, the RTE layer schedules and switches application services deployed on the controller, the BSW layer provides basic software services such as TCP / IP, the data authentication layer configures authentication metadata for application data, and the MCAL layer forwards processed application data to other controllers. This invention authenticates Ethernet data in the system, preventing illegal and malicious Ethernet data from entering the system.

[0033] like Figure 3 As shown, the in-vehicle Ethernet data authentication method based on the Classic Autosar platform of the present invention specifically includes:

[0034] In the first step, the in-vehicle application service on the controller is started, application data is generated, and different in-vehicle application services are implemented through the application layer component (SWC) layer. Application data is sent and received, and the SWC service ID and data domain are allocated.

[0035] In the second step, the controller switches and schedules different application services. The runtime environment (RTE) layer implements the scheduling and switching of different vehicle controller application services and monitors the operating status of different application services.

[0036] In the third step, the controller provides basic software services such as TCP / IP for different in-vehicle application services through the basic software (BSW) layer. It is responsible for Ethernet encapsulation of different application data, adding data packet headers, and assigning BSW service IDs. Basic software services include OS, TCP / IP, Ethif, DEM, CDD, Canif, etc.

[0037] In the fourth step, the controller configures authentication metadata for different application data through the data authentication layer. The configuration content includes information such as the local node identifier, the peer node identifier, the SWC service ID, the BSW service ID, and the data domain, and encapsulates this information. The data authentication layer of the peer controller receives the data, decodes it, and obtains the authentication metadata, which is used to authenticate the in-vehicle Ethernet data.

[0038] In the fifth step, the controller uses the hardware abstraction layer (MCAL) to encapsulate the application data, including authenticated metadata and data packet headers, at the hardware driver layer. The hardware driver then forwards the data to the connected vehicle controller. The controller receives the data and decodes it at the hardware driver layer. Hardware drivers include Candrv, Ethdrv, and Lindrv.

[0039] The beneficial effect of the present invention is that, compared with the existing technology, the present invention deploys the Classic Autosar platform on both the vehicle central controller and the domain controller, and adds a data authentication layer to the Classic Autosar framework. The data authentication layer configures and authenticates the authentication metadata of the application data, thereby realizing the authentication of the vehicle Ethernet data in the system.

[0040] The present invention implements vehicle-wide Ethernet data authentication by deploying an in-vehicle Ethernet data authentication system based on the Classic Autosar platform on the vehicle controller, thereby ensuring the normal data transmission of in-vehicle application services, avoiding illegal Ethernet data and Ethernet data attacked by malicious attacks, ensuring the security of in-vehicle Ethernet data transmission and normal application services, and improving the reliability of the network in the field of autonomous driving.

[0041] The applicant of the present invention has made a detailed explanation and description of the implementation examples of the present invention in conjunction with the drawings in the specification. However, those skilled in the art should understand that the above implementation examples are only preferred implementation plans of the present invention, and the detailed description is only to help readers better understand the spirit of the present invention, and is not a limitation on the scope of protection of the present invention. On the contrary, any improvements or modifications based on the inventive spirit of the present invention should fall within the scope of protection of the present invention.

Claims

1. An in-vehicle Ethernet data authentication system based on the Classic Autosar platform, characterized in that: Including central controller and domain controller, the Classic Autosar platform is deployed on both the central controller and the domain controller, and a data authentication layer is added to the Classic Autosar platform framework; The data authentication layer configures and authenticates the authentication metadata of the application data during the transmission of Ethernet application data. The Classic Autosar platform encapsulates the application data, datagram header, and configured authentication metadata before transmitting the Ethernet application data. The configuration content of the authentication metadata includes the local node ID, the peer node ID, the SWC service ID, the BSW service ID, and the data domain information.

2. The in-vehicle Ethernet data authentication system based on the Classic Autosar platform according to claim 1, characterized in that: The data authentication layer configures authentication metadata for application data when sending data; When receiving data, the data authentication layer performs data authentication on the in-vehicle Ethernet data including authentication metadata, data packet header and application data.

3. The in-vehicle Ethernet data authentication system based on the Classic Autosar platform according to claim 1, characterized in that: The Classic Autosar platform framework includes the application layer component SWC layer, the runtime environment RTE layer, the basic software BSW layer, and the hardware abstraction MCAL layer; each controller deploys a data authentication layer between the MCAL layer and the BSW layer.

4. The in-vehicle Ethernet data authentication system based on the Classic Autosar platform according to claim 3, characterized in that: Application data is sent and received through the SWC layer, the RTE layer schedules and switches application services deployed on the controller, the BSW layer provides basic software services, the data authentication layer configures authentication metadata for application data, and the MCAL layer forwards the processed application data to other controllers.

5. A vehicle Ethernet data authentication method based on the Classic Autosar platform, characterized in that: Including steps: In the first step, the vehicle application service on the controller is started, application data is generated, and application data is sent and received through the application layer component SWC layer; In the second step, the controller uses the runtime environment (RTE) layer to schedule and switch between different vehicle controller application services and monitor the running status of different application services. In the third step, the controller provides basic software services for different in-vehicle application services through the basic software BSW layer, is responsible for Ethernet encapsulation of different application data, and adds data message headers; In the fourth step, the controller configures and encapsulates authentication metadata for different application data through the data authentication layer. The data authentication layer of the peer controller receives the data, decodes the authentication metadata, and authenticates the in-vehicle Ethernet data. The authentication metadata configuration includes the local node ID, peer node ID, SWC service ID, BSW service ID, and data domain information. In the fifth step, the controller uses the hardware abstraction MCAL layer to encapsulate the application data that has passed the authentication metadata and data packet header at the hardware driver layer, and forwards it to the connected vehicle controller through the hardware driver; the other end controller receives the data and decodes it at the hardware driver layer.

6. The in-vehicle Ethernet data authentication method based on the Classic Autosar platform according to claim 5, characterized in that: In the first step, the application layer component SWC layer also allocates the SWC service ID and the data Domain domain.

7. The in-vehicle Ethernet data authentication method based on the Classic Autosar platform according to claim 5, characterized in that: In the third step, the basic software BSW layer also allocates the BSW service ID.

8. The in-vehicle Ethernet data authentication method based on the Classic Autosar platform according to claim 5, characterized in that: In the third step, basic software services include OS, TCP / IP, Ethif, DEM, CDD, and Canif.

9. The in-vehicle Ethernet data authentication method based on the Classic Autosar platform according to claim 5, characterized in that: In the fifth step, the hardware drivers include Candrv, Ethdrv, and Lindrv.

Images