Packet-switched in-vehicle multimodal network system for network resilience testing of connected vehicles

Abstract

The present application discloses a packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles, which is applied to the technical field of automobile network resilience testing. The packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles includes: a packet-switched network layer, connected between a test platform and a device layer, wherein the device layer is connected with a car that is allowed to be subjected to network resilience testing; the packet-switched network layer is used to receive a test event sent by the test platform, and to test the car through the test event, wherein the packet-switched network layer allows compatibility with cars with different electronic and electrical architectures. This solves the technical problem in the related art that the test platform cannot test cars with different electronic and electrical architectures.

Description

Technical Field

[0001] The present application relates to the technical field of automobile network resilience testing, and in particular to a packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles. Background Art

[0002] Generally speaking, cars of different brands or different types of cars of different brands may have different electronic and electrical architectures. In the related art, there are test platforms for testing cars, and the test types include functional testing, performance testing, safety testing, or network resilience testing. However, these test platforms generally only test cars with a certain electronic and electrical architecture, and cannot test cars with different electronic and electrical architectures.

[0003] Therefore, in the related art, the test platform is unable to test vehicles with different electronic and electrical architectures.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] An embodiment of the present application provides a packet-switched in-vehicle multimodal network system for Internet of Vehicles network resilience testing, so as to at least solve the technical problem in the related art that the test platform cannot test vehicles with different electronic and electrical architectures.

[0006] According to one aspect of an embodiment of the present application, a packet-switched in-vehicle multimodal network system for network resilience testing of an Internet of Vehicles is provided, comprising: a packet-switching network layer connected between a test platform and a device layer, wherein the device layer is connected with a car that is allowed to be subjected to network resilience testing; the packet-switching network layer is used to receive test events sent by the test platform, and to test the car through the test events, wherein the packet-switching network layer allows compatibility with cars with different electronic and electrical architectures.

[0007] Optionally, the packet switching network layer includes: a packet switch, and multiple bus adapters connected to the packet switch; wherein the car is connected to at least one of the multiple bus adapters to receive the test event sent by the packet switch through the at least one bus adapter; wherein the packet switch is connected to the test platform to receive the test event and feed back monitoring data to the test platform, wherein the monitoring data is the response data of the car to the test event when the car receives the test event.

[0008] Optionally, the multiple bus adapters allow adaptation to different types of communication buses, and each of the multiple bus adapters includes: multiple bus adapters that allow adaptation to the same type of communication bus; the network components in the car are connected to at least one of the bus adapters, and the network components and bus adapters connected to each other are connected via the same type of communication bus.

[0009] Optionally, the packet switching network layer is also used to receive configuration data sent by the test platform before receiving the test event sent by the test platform, wherein the configuration data includes: a connection topology diagram, an event injection point diagram, and a data monitoring point diagram; the connection topology diagram is used to indicate the connection topology between the packet switching network layer and the network components in the car, and the connection topology corresponds to the topology of the electronic and electrical architecture of the car; the event injection point diagram is used to indicate the first port corresponding to any sub-event in the test event in the packet switch, and the target network component to which any sub-event needs to be sent, wherein the first port is used for the test platform to input any sub-event to the packet switching network layer, and the network component includes the target network component; the data monitoring point diagram is at least used to indicate the second port corresponding to the monitoring data in the packet switch, and the second port is used for the packet switch to feedback the monitoring data to the test platform.

[0010] Optionally, the packet switch includes a plurality of third ports, and the plurality of third ports include: the first port, the second port, and a fourth port for connecting to the plurality of bus adapters.

[0011] Optionally, the connection topology diagram is further used to indicate, in the connection topology, a first index assigned to the at least one bus adapter and a second index assigned to a bus connected to the at least one bus adapter.

[0012] Optionally, the packet switch is used to determine the transmission path of any sub-event through the event injection point diagram when receiving any sub-event, and the transmission path at least includes: a target network component corresponding to any sub-event, a target bus adapter connected to the target network component, and a fifth port of the packet switch connected to the target bus adapter; the packet switch is also used to assign a label to any sub-event according to the third index of the fifth port and / or the fourth index of the target bus adapter, and send the any sub-event to the target bus adapter through the label; wherein the at least one bus adapter includes: the target bus adapter; wherein the first index includes: the fourth index.

[0013] Optionally, the at least one bus adapter is used to receive a first data packet from a communication bus connected to the at least one bus adapter; the at least one bus adapter is also used to perform a normalization operation on the first data packet to obtain a second data packet that can be recognized by the packet switch, wherein the first data packet carries direct response data or indirect response data of the vehicle to the test event.

[0014] Optionally, the at least one bus adapter is further used to receive a third data packet from the packet switch; the at least one bus adapter is further used to perform a denormalization operation on the third data packet to obtain a fourth data packet that is allowed to be transmitted by the communication bus connected to the at least one bus adapter; wherein the third data packet includes at least one of the following: the second data packet, the test event.

[0015] Optionally, the packet switch is further used to query the data monitoring point diagram when receiving the second data packet to determine whether the second data packet carries the monitoring data required by the test platform; the packet switch is also used to send the second data packet to the test platform through the second port when the second data packet carries the monitoring data; wherein the data monitoring point diagram is configuration data received by the packet switching network layer from the test platform before receiving the test event sent by the test platform; wherein the second port is the port in the packet switch indicated by the data monitoring point diagram for feeding back the monitoring data to the test platform.

[0016] In an embodiment of the present application, a packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles is provided, comprising: a packet-switched network layer connected between a test platform and a device layer, wherein a car that is allowed to be tested for network resilience is connected to the device layer; the packet-switched network layer is used to receive a test event sent by the test platform, and to test the car through the test event, wherein the packet-switched network layer allows compatibility with cars with different electronic and electrical architectures. This solves the technical problem in the related art that the test platform cannot test cars with different electronic and electrical architectures, and achieves the technical effect of allowing the test platform to perform network resilience testing on cars with different electronic and electrical architectures. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 11 is a schematic diagram of the architecture of a packet-switched in-vehicle multimodal network system for network resilience testing of an Internet of Vehicles according to an embodiment of the present application (I);

[0019] Figure 2 2 is a schematic diagram of the architecture of a packet-switched in-vehicle multimodal network system for network resilience testing of an Internet of Vehicles according to an embodiment of the present application (II);

[0020] Figure 3 is a schematic diagram of a distributed automotive electronic and electrical architecture according to an embodiment of the present application;

[0021] Figure 4 is a schematic diagram of a domain-controlled automotive electrical and electronic architecture according to an embodiment of the present application;

[0022] Figure 5 is a schematic diagram of a centrally controlled automotive electrical and electronic architecture according to an embodiment of the present application;

[0023] Figure 6 is a schematic diagram of the structure of a bus adapter according to an embodiment of the present application;

[0024] Figure 7 It is a schematic diagram of N-way packet concurrency of a packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles according to an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0027] Figure 1FIG1 is a schematic diagram of the architecture of a packet-switched in-vehicle multimodal network system for network resilience testing of an Internet of Vehicles according to an embodiment of the present application (I). Figure 1 As shown, the system includes:

[0028] A packet-switched network layer 11 connected between a test platform 12 and a device layer 13 to which a car 14 is connected that allows network resilience testing to be performed;

[0029] The packet switching network layer 11 is used to receive the test events sent by the test platform 12 and test the car 14 through the test events, wherein the packet switching network layer 11 allows compatibility with cars with different electronic and electrical architectures.

[0030] In the embodiment of the present application, a packet-switched in-vehicle multimodal network system for network resilience testing of the Internet of Vehicles is provided, comprising: a packet-switched network layer connected between a test platform and a device layer, wherein the device layer is connected to a car that is allowed to be subjected to network resilience testing; the packet-switched network layer is used to receive a test event sent by the test platform, and to test the car through the test event, wherein the packet-switched network layer allows compatibility with cars with different electronic and electrical architectures. This system solves the technical problem in the related art that the test platform cannot test cars with different electronic and electrical architectures, and achieves the technical effect of allowing the test platform to perform network resilience testing on cars with different electronic and electrical architectures.

[0031] Optionally, the packet switching network layer includes: a packet switch, and multiple bus adapters connected to the packet switch; wherein the car is connected to at least one of the multiple bus adapters to receive the test event sent by the packet switch through the at least one bus adapter; wherein the packet switch is connected to the test platform to receive the test event and feed back monitoring data to the test platform, wherein the monitoring data is the response data of the car to the test event when the car receives the test event.

[0032] like Figure 2 As shown, in the embodiment of the present application, the packet switching network layer specifically includes a packet switch and a plurality of bus adapters for connecting to the device layer; the types of the plurality of bus adapters include but are not limited to the following: Figure 2 Various in-vehicle bus adapters such as CAN bus adapter, LAN bus adapter, LIN bus adapter, etc. shown in the figure.

[0033] Optionally, the multiple bus adapters allow adaptation to different types of communication buses, and each of the multiple bus adapters includes: multiple bus adapters that allow adaptation to the same type of communication bus; the network components in the car are connected to at least one of the bus adapters, and the network components and bus adapters connected to each other are connected via the same type of communication bus.

[0034] For example, the packet switching network layer may have multiple CAN bus adapters, which allow the CAN communication bus to be adapted. The network components that support the CAN bus at the device layer can be connected to the CAN bus adapter via the CAN communication bus, and then communicate with the test platform via the packet switching network layer.

[0035] Figure 2 The device layer in allows the connection of cars, which include ECUs and sensors with different functions, such as VCU vehicle controller, MCU motor controller, etc. These ECUs and sensors can be called network components, and each ECU and sensor assumes a relatively independent functional system. Different ECUs use different in-vehicle network communication buses, including but not limited to CAN bus, LIN bus, vehicle Ethernet LAN bus, Bluetooth communication bus, etc.

[0036] The equipment layer also includes in-vehicle components to be tested, reference in-vehicle components, and simulated in-vehicle components.

[0037] The in-vehicle component to be tested is a separate component set in the equipment layer, which can be tested in conjunction with the car when the device layer is connected to the car; it can also be tested separately by the test platform. The reference in-vehicle component is a baseline component when conducting an endogenous security threat perception test, that is, when the in-vehicle component to be tested is tested, the reference in-vehicle component can be tested before or after the in-vehicle component to be tested, or at the same time as the in-vehicle component to be tested, to generate a basic signal; wherein the basic signal is used to compare with the test signal generated when the in-vehicle component to be tested is tested.

[0038] The simulated in-vehicle components are components that, when testing, can use simulation technology to generate network signals that are exactly the same as the real components of the car (i.e., the real network components inside the car). The use of simulated in-vehicle components can reduce testing costs.

[0039] Through the device layer, when it is impossible to connect to the car to be tested, the device layer can be configured on demand according to the electronic and electrical architecture of the car to be tested, and the electronic and electrical architecture of the car to be tested can be simulated and / or replaced through the in-vehicle components to be tested, reference in-vehicle components, and simulated in-vehicle components.

[0040] It should be noted that when there is a car to be tested, the car is connected to the device layer, and the above connection topology diagram will be obtained during the connection process (i.e. Figure 2 The connection topology diagram includes a connection topology between a network component in a car and at least one of a plurality of bus adapters, and also includes a connection topology between at least one bus adapter and a packet switch. The connection topology in the connection topology diagram corresponds to the electronic and electrical architecture of the car.

[0041] Optionally, in the case where multiple bus adapters are always connected to the packet switch, the connection topology diagram is used to indicate which ports of the packet switch at least one bus adapter is connected to in this test.

[0042] It should also be noted that when the car that needs to be tested is determined, the test requirements for the car will be clarified; the test requirements specifically indicate whether the entire car needs to be tested or which network components in the car need to be tested; the test requirements also indicate which network components to inject test events into during the test, as well as the monitoring data that needs to be obtained.

[0043] The event injection point diagram and data monitoring point diagram can be determined according to the test requirements. The event injection point diagram includes Figure 2 The business injection point diagram and attack injection point diagram in .

[0044] Thus, configuration data is obtained and injected into the packet switching network layer before starting the test to configure the packet switching network layer. The in-vehicle components to be tested, the reference in-vehicle components, and the simulated in-vehicle components of the network components and / or device layer in the vehicle have been connected to at least one bus adapter through their supported communication buses, and at least one bus adapter has been connected to the packet switch, or the connection port of the packet switch has been allowed to communicate. Thus, the device layer including the vehicle can communicate with the test platform through the packet switching network layer.

[0045] It should be noted that when the car is connected to the device layer, the configuration data is fixed. When the car to be tested is determined and / or the car is connected to the device layer, the connection relationship between the device layer and the packet switching network layer is also fixed.

[0046] Optionally, the packet switching network layer is also used to receive configuration data sent by the test platform before receiving the test event sent by the test platform, wherein the configuration data includes: a connection topology diagram, an event injection point diagram, and a data monitoring point diagram; the connection topology diagram is used to indicate the connection topology between the packet switching network layer and the network components in the car, and the connection topology corresponds to the topology of the electronic and electrical architecture of the car; the event injection point diagram is used to indicate the first port corresponding to any sub-event in the test event in the packet switch, and the target network component to which any sub-event needs to be sent, wherein the first port is used for the test platform to input any sub-event to the packet switching network layer, and the network component includes the target network component; the data monitoring point diagram is at least used to indicate the second port corresponding to the monitoring data in the packet switch, and the second port is used for the packet switch to feedback the monitoring data to the test platform.

[0047] It should be noted that the connection topology in the connection topology diagram corresponds to the topology of the electronic and electrical architecture of the vehicle. The topology of the electronic and electrical architecture of the vehicle mainly includes: a distributed automotive electronic and electrical architecture, a multi-domain controlled automotive electronic and electrical architecture, and a centralized controlled automotive electronic and electrical architecture.

[0048] like Figure 3 As shown, in the distributed automotive electronic and electrical architecture, each ECU component has a control function, and the distributed in-vehicle network forwards data packets according to the corresponding communication requirements.

[0049] like Figure 4 As shown in the figure, in the domain-controlled automotive electronic and electrical architecture, there are multiple domain controllers in the car to control different in-car components. Through the domain-controlled internal network architecture, the car body is divided into different domains, and data is forwarded in the corresponding domain.

[0050] like Figure 5 As shown in the figure, in the centralized control automotive electronic and electrical architecture, there is a centralized controller in the car, and all the components in the car communicate with the centralized controller through the centralized control in-car network architecture.

[0051] Optional, such as Figure 2 As shown, the configuration data is specifically stored in the packet switch. The event injection point diagram specifically includes: a service injection point diagram and an attack injection point diagram. When the test platform sends a test event, the packet switch queries the service injection point diagram or the attack injection point diagram according to the type of the test event (i.e., whether it is a service event or an attack event), and determines the target network component to which the test event needs to be sent through the timing of the test event being injected into the packet switch and the port identifier of the injection port (i.e., the first port).

[0052] Optionally, the packet switch includes a plurality of third ports, and the plurality of third ports include: the first port, the second port, and a fourth port for connecting to the plurality of bus adapters. It should be noted that the plurality of third ports can transmit data.

[0053] Optionally, the connection topology diagram is further used to indicate, in the connection topology, a first index assigned to the at least one bus adapter and a second index assigned to a bus connected to the at least one bus adapter.

[0054] Optionally, the packet switch is used to determine the transmission path of any sub-event through the event injection point diagram when receiving any sub-event, and the transmission path at least includes: a target network component corresponding to any sub-event, a target bus adapter connected to the target network component, and a fifth port of the packet switch connected to the target bus adapter; the packet switch is also used to assign a label to any sub-event according to the third index of the fifth port and / or the fourth index of the target bus adapter, and send the any sub-event to the target bus adapter through the label; wherein the at least one bus adapter includes: the target bus adapter; wherein the first index includes: the fourth index.

[0055] After the packet switch sends the any sub-event to the target bus adapter through the tag, the target bus adapter sends the any sub-event to the target network element.

[0056] In an optional embodiment, after any sub-event is injected into the packet switch through the first port, the packet switch queries the event injection point map to determine the transmission path of the any sub-event, and then assigns a label to the any sub-event according to the third index of the fifth port on the transmission path and / or the fourth index of the target bus adapter; the switching network of the packet switch sends any sub-event to the fifth port based on the label; after sending to the fifth port, the label on any sub-event is removed, and the any sub-event is sent to the target bus adapter; the target bus adapter can send any sub-event to the target network component according to the second index of the bus connected to the target network component.

[0057] When the packet switch receives feedback data from the target network component for any sub-event, it queries the connection topology diagram to determine the transmission path of the feedback data in the network component of the car. The feedback data may or may not need to be transmitted. When the feedback data needs to be transmitted, a label is assigned to the feedback data in the packet switch according to the transmission path of the feedback data in the network component of the car, and the feedback data is transmitted in the packet switch according to the label. After being transmitted to the output port corresponding to the feedback data, the label is removed. Similarly, when the packet switch obtains the received data (including the test event and the feedback data of the test event), it can transmit the test event and the feedback data of the test event between the network components of the car according to the test requirements by querying the event injection point diagram and the connection topology diagram, thereby realizing the test of the network elasticity of the car.

[0058] At the same time, when the packet switch receives feedback data from the target network component for any sub-event, the packet switch queries the data monitoring point diagram, determines whether the feedback data is the required monitoring data according to the source port of the feedback data, and sends the feedback data as monitoring data to the test platform through the second port if the feedback data is monitoring data. In this way, the feedback data generated by the car during the test can be obtained, and the test platform can analyze the network elasticity of the car according to the received monitoring data to obtain the test results.

[0059] It should be noted that the first index, the second index, the third index, and the fourth index are allocated in the process of connecting the car to the device layer, and are included in the configuration data and injected into the packet switch along with the configuration data.

[0060] Optionally, the at least one bus adapter is used to receive a first data packet from a communication bus connected to the at least one bus adapter; the at least one bus adapter is also used to perform a normalization operation on the first data packet to obtain a second data packet recognizable by the packet switch, wherein the first data packet carries direct response data or indirect response data of the vehicle to the test event.

[0061] It can be understood that direct response data is, for example, the feedback data mentioned above; indirect response data is, for example, secondary feedback data of the feedback data when the feedback data needs to continue to be transmitted in the network components of the car.

[0062] Optionally, the at least one bus adapter is further used to receive a third data packet from the packet switch; the at least one bus adapter is further used to perform a denormalization operation on the third data packet to obtain a fourth data packet that is allowed to be transmitted by the communication bus connected to the at least one bus adapter; wherein the third data packet includes at least one of the following: the second data packet, the test event.

[0063] like Figure 6 As shown, the formats of data packets provided by different buses are different, and the bus adapter is used to normalize the data packets received from the bus to obtain a second data packet that can be recognized by the packet switch. The bus adapter is also used to denormalize the third data packet received from the packet switch to obtain a fourth data packet that the communication bus allows to be transmitted.

[0064] Specifically, the bus adapter receives a first data packet from various buses, parses the carried data through a corresponding protocol, re-packs the data, and obtains a second data packet recognized by the packet switching network; the bus adapter re-packs the third data packet received from the packet switch according to the corresponding protocol into a fourth data packet that can be recognized by the corresponding bus, and sends it to the corresponding bus.

[0065] Optionally, the packet switch is further used to query the data monitoring point diagram when receiving the second data packet to determine whether the second data packet carries the monitoring data required by the test platform; the packet switch is also used to send the second data packet to the test platform through the second port when the second data packet carries the monitoring data; wherein the data monitoring point diagram is configuration data received by the packet switching network layer from the test platform before receiving the test event sent by the test platform; wherein the second port is the port in the packet switch indicated by the data monitoring point diagram for feeding back the monitoring data to the test platform.

[0066] In an optional embodiment, the in-vehicle component to be tested may be a certain type of specific network component, or may be a network component of different categories. When performing an endogenous security threat perception test on a certain type of specific network component to be tested, data packets may be sent to the specific network component to be tested and N heterogeneous network components with the same function by concurrently sending data packets, and by detecting abnormalities in their network interactions, unknown vulnerabilities and unknown backdoors inside the component to be tested may be discovered.

[0067] like Figure 7 As shown, when an endogenous security threat perception test is required, after receiving the data packet of the endogenous security threat perception test, the packet switch performs N-way packet concurrency according to the configuration parameters, and concurrently forwards N heterogeneous components with the same function as reference components.

[0068] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0069] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0070] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0071] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0072] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0073] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles, characterized in that: Used to test the cyber resilience of vehicles, including: a packet-switched network layer connected between the test platform and the device layer, wherein the vehicle is connected to allow network resilience testing to be performed; The packet switching network layer is used to receive the test events sent by the test platform and test the car through the test events, wherein the packet switching network layer allows compatibility with cars with different electronic and electrical architectures, wherein, The packet switching network layer comprises: a packet switch, and a plurality of bus adapters connected to the packet switch; wherein the automobile is connected to at least one bus adapter among the plurality of bus adapters to receive the test event sent by the packet switch through the at least one bus adapter; The packet switch is connected to the test platform to receive the test event and feed back monitoring data to the test platform, wherein the monitoring data is the response data of the car to the test event when the car receives the test event, wherein: The packet switching network layer is further used to receive configuration data sent by the test platform before receiving the test event sent by the test platform, wherein the configuration data includes: a connection topology diagram, an event injection point diagram and a data monitoring point diagram; The connection topology diagram is used to indicate the connection topology between the packet switching network layer and the network components in the automobile, the connection topology corresponding to the topology of the electronic and electrical architecture of the automobile; The event injection point diagram is used to indicate the first port corresponding to any sub-event in the test event in the packet switch, and the target network component to which the any sub-event needs to be sent, wherein the first port is used for the test platform to input the any sub-event to the packet switching network layer, and the network component includes the target network component; The data monitoring point diagram is used to indicate the second port corresponding to the monitoring data in the packet switch, and the second port is used by the packet switch to feed back the monitoring data to the test platform.

2. The packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles according to claim 1, characterized in that: The plurality of bus adapters allow adapting to different types of communication buses, and each of the plurality of bus adapters includes: a plurality of bus adapters that allow adapting to the same type of communication bus; The network component in the vehicle is connected to the at least one bus adapter, and the network component and the bus adapter connected to each other are connected via the same type of communication bus.

3. The packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles according to claim 1, characterized in that: The packet switch includes: the first port, the second port, and a fourth port for connecting with the various bus adapters.

4. The packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles according to claim 1, characterized in that: The connection topology diagram is further used to indicate, in the connection topology, a first index assigned to the at least one bus adapter and a second index assigned to a bus connected to the at least one bus adapter.

5. The packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles according to claim 4, characterized in that: The packet switch is used to determine the transmission path of any sub-event through the event injection point diagram when receiving any sub-event, wherein the transmission path includes: a target network component, a target bus adapter and a fifth port corresponding to any sub-event, wherein the target bus adapter is connected to the target network component, and the fifth port is a port where the packet switch is connected to the target bus adapter; The packet switch is further configured to assign a label to any of the sub-events according to the third index of the fifth port and / or the fourth index of the target bus adapter, and send the any of the sub-events to the target bus adapter via the label; Wherein, the at least one bus adapter includes: the target bus adapter; wherein, the first index includes: the fourth index.

6. The packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles according to claim 1, characterized in that: The at least one bus adapter is configured to receive a first data packet from a communication bus connected to the at least one bus adapter; The at least one bus adapter is further configured to perform a normalization operation on the first data packet to obtain a second data packet that can be recognized by the packet switch; The first data packet carries direct response data or indirect response data of the vehicle to the test event.

7. The packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles according to claim 6, characterized in that: The at least one bus adapter is further configured to receive a third data packet from the packet switch; The at least one bus adapter is further used to perform a denormalization operation on the third data packet to obtain a fourth data packet that is allowed to be transmitted by the communication bus connected to the at least one bus adapter; Wherein, the third data packet includes at least one of the following: the second data packet, the test event.

8. The packet-switched in-vehicle multimodal network system for network resilience testing of Internet of Vehicles according to claim 6, characterized in that: The packet switch is further configured to query a data monitoring point diagram upon receiving the second data packet to determine whether the second data packet carries the monitoring data required by the test platform; The packet switch is further configured to send the second data packet to the test platform through a second port when the second data packet carries the monitoring data.

Images