Internet of vehicles system architecture and vehicle

Abstract

The present disclosure relates to a kind of vehicle networking system architecture and vehicle, including: central computing platform, vehicle networking terminal is connected with central computing platform by vehicle-mounted ethernet and CAN bus communication;Central computing platform includes M core processor and A core processor, the network access equipment module of vehicle networking terminal is connected with A core processor by vehicle-mounted ethernet communication, the micro control unit of vehicle networking terminal is connected with A core processor by CAN bus communication;Micro control unit sends terminal control instruction to A core processor by CAN bus, and controls network access equipment module, sends first information to M core processor by vehicle-mounted ethernet;M core processor generates control instruction according to first information or terminal control instruction;A core processor sends control instruction to vehicle load, sends vehicle data reported by vehicle load to network access equipment module by vehicle-mounted ethernet;Network access equipment module carries out V2X and sends vehicle data.

Description

Technical Field

[0001] This disclosure relates to the field of vehicle engineering technology, and in particular to a vehicle networking system architecture and vehicle. Background Technology

[0002] To facilitate information exchange between vehicles and other devices, related technologies integrate V2X (Vehicle to Everything) and T-Box (Telematics Box) functions. The integrated terminal includes a microcontroller unit, a system-on-a-chip (SoC) computing chip, and network connectivity devices. The microcontroller unit handles communication, power management, and Bluetooth connectivity. The network connectivity devices handle in-vehicle Ethernet communication, external cellular network communication, and WiFi communication. The SoC computing chip handles computation; however, configuring an SoC increases the terminal's cost, and the integrated terminal is relatively large, limiting its installation space within the vehicle. Summary of the Invention

[0003] To overcome the problems existing in related technologies, this disclosure provides a vehicle networking system architecture and a vehicle.

[0004] According to a first aspect of the present disclosure, a vehicle-to-everything (V2X) system architecture is provided, the V2X system architecture comprising:

[0005] A central computing platform and a vehicle networking terminal that communicates with the central computing platform via in-vehicle Ethernet and CAN bus, respectively.

[0006] The central computing platform includes an M-core processor and an A-core processor. The network access device module of the vehicle-to-everything (V2X) terminal is connected to the M-core processor via the vehicle Ethernet. The microcontroller unit of the V2X terminal is connected to the A-core processor via the CAN bus.

[0007] The microcontroller unit sends terminal control commands to the A-core processor of the central computing platform via the CAN bus, and controls the network access device module to send first information to the M-core processor via the vehicle Ethernet. The first information includes data sent by any device to the vehicle network terminal via V2X.

[0008] The M-core processor generates a corresponding load control instruction based on the first information or the terminal control instruction;

[0009] The A-core processor sends the load control command to the corresponding vehicle load, and sends the received vehicle data reported by the vehicle load to the network access device module via the vehicle Ethernet.

[0010] The network access device module sends the vehicle data via the V2X method.

[0011] Optionally, the central computing platform includes a hardware security module connected to the A-core processor. The hardware security module is used to decrypt and verify the received terminal control commands, and to sign and encrypt the load control commands and / or the vehicle data.

[0012] Optionally, the A-core processor uploads the terminal control command and the certificate of the vehicle-to-everything (V2X) terminal accompanying the terminal control command to the hardware security module;

[0013] The hardware security module decrypts the terminal control commands according to a pre-configured key, and verifies the signature of the decrypted terminal control commands according to the certificate.

[0014] Optionally, the A-core processor uploads the load control instructions and / or the vehicle data to the hardware security module;

[0015] The hardware security module encrypts the load control commands and / or the vehicle data according to a pre-configured key.

[0016] Optionally, the A-core processor runs a V2X protocol stack and is configured with a virtual memory-based operating system and user applications.

[0017] Optionally, the M-core processor is configured with an embedded control application.

[0018] Optionally, the central computing platform includes an in-vehicle Ethernet gateway, and based on the in-vehicle Ethernet gateway, the network access device module of the vehicle network terminal is communicatively connected to the A-core processor.

[0019] Optionally, based on SOA services, the network access device module of the vehicle network terminal receives vehicle data from the vehicle load.

[0020] Optionally, the communication protocols of the SOA service include Some / IP and Data Distribution Service (DDS).

[0021] According to a second aspect of the present disclosure, a vehicle is provided, comprising: the vehicle networking system architecture described in any one of the first aspects.

[0022] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0023] The above technical solution establishes a central computing platform that communicates with the vehicle network terminal via both in-vehicle Ethernet and CAN bus. The central computing platform includes an M-core processor and an A-core processor. The network access device module of the vehicle network terminal communicates with the M-core processor via in-vehicle Ethernet, and the microcontroller unit of the vehicle network terminal communicates with the A-core processor via CAN bus. By decoupling the central computing platform and the vehicle network terminal and enabling them to communicate in multiple ways, the central computing platform and the vehicle network terminal can be installed in different locations within the vehicle, avoiding limitations on installation location and improving the flexibility of vehicle installation and configuration.

[0024] Furthermore, the microcontroller sends terminal control commands to the A-core processor of the central computing platform via the CAN bus and controls the network access device module to send first information to the M-core processor via the vehicle Ethernet. The M-core processor generates corresponding load control commands based on the first information or the terminal control commands. The A-core processor sends control commands to the corresponding vehicle load and sends the received vehicle data reported by the vehicle load to the network access device module via the vehicle Ethernet. The network access device module then transmits the vehicle data via V2X. The microcontroller forwards the first information to the M-core processor of the central computing platform via the vehicle Ethernet, and the A-core processor sends the received vehicle data reported by the vehicle load to the network access device module via the vehicle Ethernet. Sending control commands and vehicle data via the CAN bus and vehicle Ethernet respectively reduces the risk of congestion in signaling and data transmission. Furthermore, the M-core processor and A-core processor can be reused, reducing the cost of vehicle configuration.

[0025] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0026] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0027] Figure 1 This is a structural block diagram illustrating a vehicle networking system architecture according to an exemplary embodiment.

[0028] Figure 2 This is a functional block diagram of a vehicle illustrating an exemplary embodiment. Detailed Implementation

[0029] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0030] It should be noted that all actions involving the acquisition of signals, information, or data in this application are carried out in compliance with the relevant data protection laws and policies of the country where the application is located, and with the authorization granted by the owner of the relevant device.

[0031] Figure 1 This is a structural block diagram illustrating a vehicle-to-everything (V2X) system architecture according to an exemplary embodiment, such as... Figure 1 As shown, the vehicle-to-everything (V2X) system architecture includes:

[0032] The central computing platform 110 and the vehicle networking terminal (Telematics BOX, T-BOX) 120 are respectively connected to the central computing platform 110 via vehicle Ethernet and CAN bus.

[0033] The central computing platform 110 includes an M-core processor 1101 and an A-core processor 1102. The network access device (NAD) module 1201 of the vehicle networking terminal 120 communicates with the M-core processor 1101 via the vehicle Ethernet. The microcontroller unit 1202 of the vehicle networking terminal 120 communicates with the A-core processor 1102 via the CAN bus.

[0034] The microcontroller unit 1202 sends terminal control commands to the A-core processor 1102 of the central computing platform 110 via the CAN bus, and controls the network access device module 1201 to send first information to the M-core processor 1101 via the vehicle Ethernet. The first information includes data sent by any device to the vehicle network terminal 120 via V2X.

[0035] In this embodiment of the disclosure, the terminal control command may be a wake-up command or a remote control command sent to the vehicle by a mobile terminal pre-bound to the vehicle's central computing platform 110. The wake-up command is used to remotely wake the vehicle when it is in sleep mode, and the remote control command is used to remotely instruct the vehicle to report information such as tire pressure or interior temperature. For example, the mobile terminal may be an authenticated vehicle owner's mobile terminal.

[0036] In this embodiment of the disclosure, the first information may be data sent by vehicles in the vehicle's surrounding environment to the vehicle's vehicle-to-vehicle (V2V) terminal 120 via V2V, and this data is vehicle data collected by vehicles in the vehicle's surrounding environment. Alternatively, it may be road data sent by roadside devices in the vehicle's surrounding environment to the vehicle's vehicle-to-vehicle (V2V) terminal 120 via V2V.

[0037] The M-core processor 1101 generates a corresponding load control instruction based on the first information or the terminal control instruction.

[0038] The A-core processor 1102 sends the load control command to the corresponding vehicle load, and sends the received vehicle data reported by the vehicle load to the network access device module 1201 via the vehicle Ethernet.

[0039] In this embodiment, the central computing platform 110 can communicate with the vehicle load via an in-vehicle Ethernet or CAN bus, and then send load control commands to the vehicle load and obtain vehicle data reported by the vehicle load via the in-vehicle Ethernet or CAN bus. The vehicle load may include electronic control units (ECUs), actuators, sensors, etc. configured on the vehicle.

[0040] For example, when the terminal control command is a remote window opening command, upon receiving the remote window opening command from a pre-bound mobile terminal, the vehicle network terminal 120 forwards the remote window opening command to the A-core processor 1102 via the CAN bus. Upon receiving the remote window opening command, the M-core processor 1101 generates its own vehicle window opening command, and the A-core processor 1102 sends the vehicle window opening command to the Body Control Module (BCM) via the vehicle Ethernet or CAN bus. Thus, the Body Control Module can control the window opening.

[0041] In another example, when the terminal control command is a wake-up command, upon receiving a wake-up command from a pre-bound mobile terminal, the vehicle network terminal 120 forwards the wake-up command to the A-core processor 1102 via the CAN bus. Upon receiving the wake-up command, the M-core processor 1101 generates a corresponding load wake-up command, which is then sent by the A-core processor 1102 to each control unit of the vehicle via the vehicle Ethernet or CAN bus. This enables remote vehicle wake-up.

[0042] In another example, if the first information is a low tire pressure message sent by a vehicle within a preset range, upon receiving the low tire pressure message, the vehicle network terminal 120, through its microcontroller unit 1202, controls the network access device module 1201 to send the low tire pressure message to the M-core processor 1101 via the vehicle Ethernet. The M-core processor 1101 can then generate a low tire pressure alarm for surrounding vehicles based on this information and display the alarm via the vehicle's multimedia system.

[0043] As another example, taking the vehicle load-reported vehicle data as the water immersion alarm information reported by the vehicle water immersion sensor as an example, if the vehicle determines that it has a water immersion alarm while the vehicle is parked, the water immersion alarm information is reported to the A-core processor 1102 via the vehicle Ethernet or CAN bus. Upon receiving the water immersion alarm information, the A-core processor 1102 sends the water immersion alarm information to the network access device module 1201 via the vehicle Ethernet. Upon receiving the water immersion alarm information, the microcontroller unit 1202 of the network access device module 1201 determines whether there is a network connection. If it is determined that the vehicle is in a state without network connection, the target device is determined from vehicles and roadside devices within a preset range, and then a forwarding warning information including water immersion alarm information, vehicle location information, and terminal information corresponding to the pre-bound mobile terminal is generated. The forwarding warning information is further sent to the target device via the V2V method so that the target device forwards the water immersion alarm information and vehicle location information to the mobile terminal corresponding to the terminal information. If it is determined that the vehicle is connected to the network, a water immersion alarm and vehicle location information are sent to a pre-bound mobile terminal via 5G communication.

[0044] The network access device module 1201 sends the vehicle data via the V2X method.

[0045] The vehicle-to-everything (V2X) terminal 120 may include multiple types of communication antennas, including 5G (5th Generation Mobile Communication Technology) antennas, Bluetooth antennas, Wi-Fi antennas, and V2V antennas. (See [link to documentation]). Figure 1 As shown, the vehicle-to-everything (V2X) terminal 120 can be equipped with both a 5G communication antenna and a V2X antenna.

[0046] In this embodiment of the disclosure, vehicle data is transmitted via a 5G communication antenna to a mobile terminal pre-bound to the vehicle, or via a V2V antenna to other vehicles, or via a V2V antenna to roadside equipment. Different communication antennas are used to transmit vehicle data to different terminals.

[0047] The above technical solution establishes a central computing platform that communicates with the vehicle network terminal via both in-vehicle Ethernet and CAN bus. The central computing platform includes an M-core processor and an A-core processor. The network access device module of the vehicle network terminal communicates with the M-core processor via in-vehicle Ethernet, and the microcontroller unit of the vehicle network terminal communicates with the A-core processor via CAN bus. By decoupling the central computing platform and the vehicle network terminal and enabling them to communicate in multiple ways, the central computing platform and the vehicle network terminal can be installed in different locations within the vehicle, avoiding limitations on installation location and improving the flexibility of vehicle installation and configuration.

[0048] Furthermore, the microcontroller forwards first information to the M-core processor of the central computing platform via the vehicle Ethernet. This first information includes data and instructions sent by any device to the vehicle-to-everything (V2X) terminal via V2X. Based on this first information, the M-core processor generates corresponding load control instructions. The A-core processor sends control instructions to the corresponding vehicle load and transmits the received vehicle data reported by the vehicle load to the network access device module via the vehicle Ethernet. The network access device module then transmits the vehicle data via V2X. By forwarding the first information to the M-core processor of the central computing platform via the vehicle Ethernet, and by transmitting the received vehicle data reported by the vehicle load to the network access device module via the vehicle Ethernet, the microcontroller reduces the risk of data transmission congestion by using different communication methods. Additionally, the M-core and A-core processors can be reused, reducing the cost of vehicle configuration.

[0049] Optionally, the central computing platform 110 includes a hardware security module (HSM) connected to the A-core processor 1102. The hardware security module is used to decrypt and verify the received terminal control commands, and to sign and encrypt the load control commands and / or the vehicle data.

[0050] In this embodiment, the asymmetric encryption key is stored in the HSM to ensure key security. This allows encryption, decryption, signing, and signature verification to be handled entirely within the HSM. It is understood that asymmetric encryption uses different keys for encryption and decryption; the public key is publicly available to all devices, while the private key must be stored in the vehicle's HSM.

[0051] Optionally, the A-core processor 1102 uploads the terminal control command and the certificate of the vehicle networking terminal 120 accompanying the terminal control command to the hardware security module;

[0052] The hardware security module decrypts the terminal control commands according to a pre-configured key, and verifies the signature of the decrypted terminal control commands according to the certificate.

[0053] It can be explained that the mobile terminal sends a terminal control command to the vehicle-to-everything (V2X) terminal 120 via the mobile network. The V2X terminal 120 can verify the terminal control command once, and then, if the verification is successful, send the terminal control command and the certificate of the V2X terminal 120 to the M-core processor via the CAN bus. In this way, the hardware security module does not need to verify the mobile terminal, but only the V2X terminal 120.

[0054] Optionally, the A-core processor 1102 uploads the load control instructions and / or the vehicle data to the hardware security module;

[0055] The hardware security module encrypts the load control commands and / or the vehicle data according to a pre-configured key.

[0056] It can be explained that the A-core processor 1102 uploads the plaintext load control command and / or the vehicle data to the hardware security module. The hardware security module encrypts the plaintext load control command and / or the vehicle data according to a pre-configured key, obtaining the encrypted load control command and the vehicle data. The encrypted load control command is then sent to the corresponding electronic control unit or on-board actuator.

[0057] Optionally, the A-core processor 1102 runs a V2X protocol stack and is configured with a virtual memory-based operating system and user applications.

[0058] Optionally, the M-core processor 1101 is configured with an embedded control application.

[0059] A-core processors (Application Processors) are processors designed for mobile computing. They can run at very high clock frequencies and support the memory management units required by full operating systems such as Linux, Android, MS Windows, and mobile operating systems. Virtual memory-based operating systems and user applications can then be configured within A-core processors. M-core processors (Micro-controller Processors) are small in size but highly energy efficient, and can be configured for embedded control applications to control in-vehicle electronic control units or actuators based on received terminal control commands.

[0060] Optionally, the central computing platform 110 includes an in-vehicle Ethernet gateway, and based on the in-vehicle Ethernet gateway, the network access device module 1201 of the vehicle networking terminal 120 is communicatively connected to the A-core processor 1102.

[0061] See also Figure 1 As shown, the central computing platform 110 includes an in-vehicle Ethernet gateway, an A-core processor 1102 connected to the in-vehicle Ethernet gateway, and a network access device module 1201 also connected to the in-vehicle Ethernet gateway.

[0062] Optionally, based on SOA (Service-Oriented Architecture) services, the network access device module 1201 of the vehicle network terminal 120 receives vehicle data from the vehicle load.

[0063] Optionally, the communication protocols of the SOA service include Some / IP (Scalable service-Oriented Middleware over IP) and Data Distribution Service (DDS).

[0064] This disclosure also provides a vehicle, including: the vehicle networking system architecture described in any of the foregoing embodiments.

[0065] Figure 2 This is a block diagram illustrating a vehicle 600 according to an exemplary embodiment. For example, vehicle 600 can be a hybrid vehicle, a non-hybrid vehicle, an electric vehicle, a fuel cell vehicle, or other types of vehicle. Vehicle 600 can be an autonomous vehicle, a semi-autonomous vehicle, or a non-autonomous vehicle.

[0066] Reference Figure 2 The vehicle 600 may include various subsystems, such as an infotainment system 610, a perception system 620, a decision control system 630, a drive system 640, and a vehicle computing platform 650. The vehicle 600 may also include more or fewer subsystems, and each subsystem may include multiple components. Furthermore, each subsystem and component of the vehicle 600 can be interconnected via wired or wireless means.

[0067] In some embodiments, the infotainment system 610 may include a communication system, an entertainment system, and a navigation system, etc.

[0068] The perception system 620 may include several sensors for sensing information about the environment surrounding the vehicle 600. For example, the perception system 620 may include a global positioning system (which may be GPS, BeiDou, or other positioning systems), an inertial measurement unit (IMU), lidar, millimeter-wave radar, ultrasonic radar, and a camera device.

[0069] The decision control system 630 may include a computing system, a vehicle controller, a steering system, a throttle, and a braking system.

[0070] The drive system 640 may include components that provide powered motion to the vehicle 600. In one embodiment, the drive system 640 may include an engine, an energy source, a transmission system, and wheels. The engine may be one or a combination of internal combustion engines, electric motors, and compressed air engines. The engine is capable of converting energy provided by the energy source into mechanical energy.

[0071] Some or all of the functions of vehicle 600 are controlled by vehicle computing platform 650. Vehicle computing platform 650 may include at least one processor 651 and memory 652, and processor 651 may execute instructions 653 stored in memory 652.

[0072] Processor 651 can be any conventional processor, such as a commercially available CPU. The processor may also include, for example, a Graphic Processing Unit (GPU), a Field Programmable Gate Array (FPGA), a System on Chip (SOC), an Application Specific Integrated Circuit (ASIC), or a combination thereof.

[0073] The memory 652 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0074] In addition to instruction 653, memory 652 can also store data, such as road maps, route information, vehicle position, direction, speed, and other data. The data stored in memory 652 can be used by vehicle computing platform 650.

[0075] In this embodiment of the disclosure, processor 651 may execute instructions 653 to complete all or part of the steps of vehicle control.

[0076] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of this disclosure. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0077] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A vehicle-to-everything (V2X) system architecture, characterized in that, The vehicle-to-everything (V2X) system architecture includes: A central computing platform and a vehicle networking terminal that communicates with the central computing platform via in-vehicle Ethernet and CAN bus, respectively. The central computing platform includes an M-core processor and an A-core processor. The network access device module of the vehicle-to-everything (V2X) terminal is connected to the M-core processor via the vehicle Ethernet. The microcontroller unit of the V2X terminal is connected to the A-core processor via the CAN bus. The microcontroller sends terminal control commands to the A-core processor via the CAN bus and controls the network access device module to send first information to the M-core processor via the vehicle Ethernet. The first information includes data sent by any device to the vehicle network terminal via V2X. The M-core processor generates a corresponding load control instruction based on the first information or the terminal control instruction; The A-core processor sends the load control command to the corresponding vehicle load, and sends the received vehicle data reported by the vehicle load to the network access device module through the vehicle Ethernet. The central computing platform includes a vehicle Ethernet gateway, and the network access device module of the vehicle network terminal is communicatively connected to the A-core processor based on the vehicle Ethernet gateway. The network access device module sends the vehicle data via the V2X method.

2. The vehicle networking system architecture according to claim 1, characterized in that, The central computing platform includes a hardware security module connected to the A-core processor. The hardware security module is used to decrypt and verify the received terminal control commands, and to sign and encrypt the load control commands and / or the vehicle data.

3. The vehicle networking system architecture according to claim 2, characterized in that, The A-core processor uploads the terminal control command and the certificate of the vehicle-to-everything (V2X) terminal accompanying the terminal control command to the hardware security module; The hardware security module decrypts the terminal control commands according to a pre-configured key, and verifies the signature of the decrypted terminal control commands according to the certificate.

4. The vehicle networking system architecture according to claim 2, characterized in that, The A-core processor uploads the load control instructions and / or the vehicle data to the hardware security module; The hardware security module encrypts the load control commands and / or the vehicle data according to a pre-configured key.

5. The vehicle networking system architecture according to claim 1, characterized in that, The A-core processor runs the V2X protocol stack and is configured with a virtual memory-based operating system and user applications.

6. The vehicle networking system architecture according to claim 1, characterized in that, The M-core processor is equipped with an embedded control application.

7. The vehicle networking system architecture according to any one of claims 1-6, characterized in that, Based on SOA services, the network access device module of the vehicle network terminal receives vehicle data from the vehicle load.

8. The vehicle networking system architecture according to claim 7, characterized in that, The communication protocols for the SOA service include Some / IP and Data Distribution Service (DDS).

9. A vehicle, characterized in that, include: The vehicle networking system architecture according to any one of claims 1-8.

Images