Intelligent cabin system and vehicle
By introducing the FDBus architecture into the intelligent cockpit system, direct communication between the FDBus server and the first FDBus client is realized, solving the problem of low information transmission efficiency, reducing resource consumption, and improving data transmission security.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Utility models(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-30
- Publication Date
- 2026-04-03
AI Technical Summary
The information transmission methods in intelligent cockpit systems are inefficient, resource-intensive, and lack security, especially due to problems that have not been effectively addressed in the existing communication architecture design.
The FFBus architecture is used for internal cockpit connections. Through direct communication between the FFBus server and the first FFBus client, the data transmission link is shortened. The direct point-to-point communication solves the existing communication problem and reduces the data transmission link between various system modules, thereby reducing the load of the same signal volume.
It improves information transmission efficiency, reduces resource consumption, and enhances the security and reliability of data transmission.
Smart Images
Figure CN224075516U_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of electronic information technology, and more specifically, to an intelligent cockpit system and vehicle. Background Technology
[0002] With the rapid development of automotive technology, modern vehicles have gradually evolved into mobile infotainment centers and safe driving assistants. This transformation is mainly due to the development of intelligent cockpit systems, which integrate a variety of advanced functions and technologies, including but not limited to infotainment systems, driver assistance systems, and electronic control systems.
[0003] Intelligent cockpit systems use a combination of microcontroller units (MCUs) and system-on-chips (SoCs). However, within intelligent cockpit systems, information transmission methods often suffer from inefficiency and high resource consumption. Utility Model Content
[0004] To address the aforementioned technical problems, this disclosure provides an intelligent cockpit system and vehicle.
[0005] A first aspect of this disclosure provides an intelligent cockpit system, comprising:
[0006] First chip unit and second chip unit;
[0007] The first chip unit includes a first system module and a second system module. The first system module includes an FFBus server, and the second system module includes at least one first FFBus client. The FFBus server is used to send first cockpit data to the first FFBus client. Different first FFBus clients are used to perform different first cockpit services. The FFBus server is communicatively connected to the first FFBus client. The second chip unit includes an SPI communication module, and the FFBus server is communicatively connected to the SPI communication module.
[0008] Optionally, the first system module further includes at least one second FDBus client, the FDBus server is connected to the second FDBus client, the FDBus server is also used to send second cabin data to the second FDBus client, and different second FDBus clients are used to perform different second cabin services.
[0009] Optionally, the first system module further includes a first name service unit, which is connected to the FDBus server and is used to receive network information registered by the FDBus server.
[0010] The second system module includes a second name service unit, which is connected to both the first FDBus client and the first name service unit. The second name service unit is used to receive network information registered by the first FDBus client.
[0011] Optionally, the first system module further includes a host service unit, which is connected to the first name service unit and the second name service unit respectively, and is used to receive network information registered by the first name service unit and the second name service unit.
[0012] Optionally, the network information includes the node name and IP address of the network node, and the network node is any one of the FDBus server, the first FDBus client, the first name service unit, the second name service unit, and the host service unit.
[0013] Optionally, the FFBus server includes a caching module for caching data received by the FFBus server.
[0014] Optionally, the first chip unit is a system-on-a-chip (SoC) and the second chip unit is a microcontroller unit.
[0015] Optionally, the FDBus server is connected to the SPI communication module via an SPI communication bus.
[0016] Optionally, the first system module is a QNX system, and the second system module is an Android system.
[0017] A second aspect of this disclosure provides a vehicle including the intelligent cockpit system described in any of the first aspects.
[0018] By using the above technical solution, the FFBus architecture is used as the internal connection of the cockpit to connect the FFBus server and the first FFBus client used to perform the first cockpit service. This enables the FFBus server and the first FFBus client to communicate directly point-to-point, which can shorten the data transmission link between the first system module, the second system module and the second chip unit, and reduce the load of the same amount of signal.
[0019] Other features and advantages of this disclosure will be described in detail in the following detailed description section. Attached Figure Description
[0020] The accompanying drawings are provided to further illustrate the present disclosure and form part of the specification. They are used together with the following detailed description to explain the present disclosure, but do not constitute a limitation thereof. In the drawings:
[0021] Figure 1 This is a schematic diagram of the structure of an intelligent cockpit system shown in an exemplary embodiment of this disclosure.
[0022] Figure 2 This is a schematic diagram of the structure of another intelligent cockpit system illustrated in an exemplary embodiment of this disclosure.
[0023] Figure 3 This is a schematic diagram of the structure of another intelligent cockpit system illustrated in an exemplary embodiment of this disclosure.
[0024] Explanation of reference numerals in the attached figures
[0025] 11. First chip unit; 12. Second chip unit; 101. First system module; 102. Second system module; 103. SPI communication module; 111. FDBus server; 112. First FDBus client; 113. First name service unit; 114. Second name service unit; 115. Host service unit; 116. Second FDBus client; 21. System-on-a-chip; 22. Microcontroller unit; 201. QNX system; 202. Android system; 203. Other process modules. Detailed Implementation
[0026] The specific embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit this disclosure.
[0027] In related technologies, the information transmission method within intelligent cockpit systems often uses SPI (Serial Peripheral Interface) to send notifications from the MCU to the SOC. This transmission occurs between the QNX and Android systems. The QNX system deploys a Socket server and a Socket client, while the Android system deploys a Socket client. The Socket server sends the relevant data to the Socket clients in both systems, which then forward the data to other applications within those systems. In this method, the longest communication link involves four transmissions: SPI communication from the MCU to the QNX system, forwarding from the QNX SPI server to the QNX Socket server, forwarding from the QNX Socket server to the Android Socket Client, and finally forwarding from the Android Socket Client to the Android application. Furthermore, the data is transmitted as a raw data stream without serialization. Therefore, within intelligent cockpit systems, this information transmission method often suffers from inefficiency, high resource consumption, and security vulnerabilities due to the lack of serialization.
[0028] In view of this, the present disclosure provides an intelligent cockpit system and a vehicle to improve the information transmission efficiency within the intelligent cockpit system and reduce resource consumption.
[0029] Reference Figure 1 , Figure 1 This is a structural schematic diagram of an intelligent cockpit system according to an exemplary embodiment of the present disclosure, such as... Figure 1 As shown, the intelligent cockpit system may include a first chip unit 11 and a second chip unit 12. The first chip unit 11 includes a first system module 101 and a second system module 102. The first system module 101 includes an FFBus server 111, and the second system module 102 includes at least one first FFBus client 112. The FFBus server 111 is communicatively connected to the first FFBus client 112. The second chip unit 12 includes an SPI communication module 103, and the FFBus server 111 is communicatively connected to the SPI communication module 103.
[0030] The FDBus server 111 is used to send first cabin data to the first FDBus client 112, and different first FDBus clients 112 are used to perform different first cabin services.
[0031] The first FDBus client 112 is used to execute the first cabin service based on the first cabin data sent by the FDBus server 111. Different first FDBus clients 112 execute different first cabin services.
[0032] Among them, FDBus (Fast Distributed Bus) is an IPC (Inter-Process Communication) mechanism.
[0033] exist Figure 1 In the intelligent cockpit system shown, the SPI communication module 103 is connected to the FFBus server 111, and the FFBus server 111 is connected to the first FFBus client 112. Therefore, data can be transmitted between the first system module 101, the second system module 102, and the second chip unit 12.
[0034] In one example, the vehicle data collected by the second chip unit 12 can be sent to the FFBus server 111 of the first system module 101 via the SPI communication module 103. The FFBus server 111 parses the data according to the SPI protocol, and then sends the parsed data to the first FFBus client 112 for performing the first cockpit service as needed.
[0035] In the intelligent cockpit system of this disclosure embodiment, the FFBus architecture is used as the internal connection of the cockpit to connect the FFBus server 111 and the first FFBus client 112 for performing the first cockpit service. This enables the FFBus server 111 and the first FFBus client 112 to communicate directly point-to-point, which can shorten the data transmission link between the first system module 101, the second system module 102 and the second chip unit 12, and reduce the load of the same signal volume.
[0036] In some implementations, such as Figure 2 As shown, in Figure 1 Based on this, the first system module 101 may also include at least one second FDBus client 116, and the FDBus server 111 is connected to the second FDBus client 116.
[0037] The FDBus server 111 is also used to send second cabin data to the second FDBus client 116, and different second FDBus clients 116 are used to perform different second cabin services.
[0038] The second FDBus client 116 is used to execute second cabin services based on the second cabin data sent by the FDBus server 111. Different second FDBus clients 116 execute different second cabin services.
[0039] In this case, after the FDBus server 111 parses the received data according to the SPI protocol, it can also send the parsed data to the second FDBus client 116 for performing second cockpit services, as needed.
[0040] In some implementations, continue as Figure 1 As shown, the first system module 101 further includes a first name service unit 113, which is connected to the FDBus server 111 and is used to receive network information registered by the FDBus server 111; the second system module 102 includes a second name service unit 114, which is connected to both the first FDBus client 112 and the first name service unit 113, and is used to receive network information registered by the first FDBus client 112.
[0041] In this embodiment of the disclosure, after the network node (e.g., the FFBus server 111) in the first system module 101 is started, it can register its own network information with the first name service unit 113, so that the first name service unit 113 can subsequently parse the network information of the FFBus server 111. Similarly, after the network node (e.g., the first FFBus client 112) in the second system module 102 is started, it can register its own network information with the second name service unit 114, so that the second name service unit 114 can subsequently parse the network information of the first FFBus client 112. Furthermore, by connecting the first name service unit 113 and the second name service unit 114, the network information registered in the first name service unit 113 and the second name service unit 114 can be interconnected. This allows network nodes in the first system module 101 to obtain network information of network nodes in the second system module 102 through the first name service unit 113 and connect with the corresponding network nodes in the second system module 102 based on the obtained network information. Alternatively, it allows network nodes in the second system module 102 to obtain network information of network nodes in the first system module 101 through the second name service unit 114 and connect with the corresponding network nodes in the first system module 101 based on the obtained network information.
[0042] In some implementations, continue as Figure 2As shown, when the first system module 101 further includes at least one second FDBus client 116, the first name service unit 113 is also connected to the second FDBus client 116, and the first name service unit 113 is also used to receive network information registered by the second FDBus client 116.
[0043] In some implementations, continue as Figure 1 or Figure 2 As shown, the first system module 101 also includes a host service unit 115, which is connected to the first name service unit 113 and the second name service unit 114 respectively. The host service unit 115 is used to receive network information registered by the first name service unit 113 and the second name service unit 114.
[0044] In this embodiment of the disclosure, after startup, the first name service unit 113 and the second name service unit 114 can register their own network information with the host service unit 115, so that the host service unit 115 can subsequently parse the network information of the first name service unit 113 and the second name service unit 114, so that the first name service unit 113 can connect with the second name service unit 114.
[0045] In the above technical solution, the connection between the FFBus server 111 and each FFBus client is based on the network information provided by the name service unit and the host service unit 115. There is no need to make special requirements on the startup order of the FFBus server 111 and each FFBus client in the intelligent cockpit system, which reduces the development coupling of each part.
[0046] In some implementations, network information includes the node names and IP addresses of network nodes. Figure 1 In the intelligent cockpit system shown, the network node can be any one of the following: FDBus server 111, first FDBus client 112, first name service unit 113, second name service unit 114, and host service unit 115. Figure 2 In the intelligent cockpit system shown, the network node may also include a second FDBus client 116.
[0047] In some implementations, the FDBus server 111 includes a caching module for caching data received by the FDBus server 111.
[0048] In this embodiment of the disclosure, in addition to broadcasting and forwarding the data sent by the second chip unit 12 through the SPI communication module 103, the FFBus server 111 can also cache the received data through the caching module, so that the first chip unit 11 does not have to obtain the data from the second chip unit 12 every time.
[0049] In some implementations, the FDBus server 111 is connected to the SPI communication module 103 via the SPI communication bus.
[0050] In some implementations, the data transmitted between the SPI communication module 103 and the FDBus server 111 is serialized data.
[0051] In this embodiment of the disclosure, by serializing the data transmitted between the SPI communication module 103 and the FDBus server 111, the security of data transmission can be improved.
[0052] In some implementations, the first chip unit 11 is a system-on-a-chip 21, and the second chip unit 12 is a microcontroller unit 22. Optionally, the system-on-a-chip 21 is a Qualcomm 8155 chip.
[0053] In some implementations, the first system module 101 is a QNX system 201, and the second system module 102 is an Android system 202.
[0054] Reference Figure 3 , Figure 3 This is a structural schematic diagram of an intelligent cockpit system according to an exemplary embodiment of the present disclosure, such as... Figure 3 As shown, the intelligent cockpit system may include a system-on-a-chip (SoC) 21 and a microcontroller unit 22; the SoC 21 includes a QNX system 201 and an Android system 202. The QNX system 201 includes an FDBus server 111, a second FDBus client 116, a first name service unit 113, and a host service unit 115; the Android system 202 includes a first FDBus client 112 and a second name service unit 114. The microcontroller unit 22 includes an SPI communication module 103 and other process modules 203.
[0055] The host service unit 115 can communicate with the first name service unit 113 and the second name service unit 114 respectively. The first name service unit 113 can also communicate with the FFBus server 111, the second FFBus client 116 and the second name service unit 114 respectively. The second name service unit 114 can also communicate with the first FFBus client 112. The first FFBus client 112 can also communicate with the FFBus server 111. The second FFBus client 116 can also communicate with the FFBus server 111.
[0056] It should be noted that, Figure 3 The number of the FFBus server 111, the first FFBus client 112, and the second FFBus client 116 can all be one or more, and can be set according to actual needs.
[0057] In this embodiment, based on FDBus as the data communication interface for application development, a C++ wrapper used by the QNX system 201 and a Java interface wrapper used by the Android system 202 are provided, reducing development difficulty and enhancing scalability. Furthermore, the intelligent cockpit system facilitates serialization using the Google protocol, ensuring the security of transmitted content. In addition, reliable heartbeat and reconnection mechanisms exist between the server and client, ensuring that all parties maintain connection regardless of network conditions or whether any service re-enters or restarts, thus improving data security.
[0058] It should be noted that, in the above Figures 1-3 In the intelligent cockpit system shown, the server, client, and various units or modules can all be implemented through hardware circuits with relevant functions.
[0059] The following is combined Figure 3 The intelligent cockpit system shown here illustrates the startup process and data transmission process of the intelligent cockpit system.
[0060] System startup process:
[0061] After the vehicle starts, the microcontroller unit 22 is first woken up. The microcontroller unit 22 is responsible for powering on the system-on-a-chip 21 and other peripherals, and starting the internal SPI communication module 103 and other process modules 203.
[0062] After the system-on-a-chip 21 starts up, it first wakes up the QNX main system. The QNX system 201 is responsible for starting the relevant processes of the QNX system 201 and starting the Android system 202. This step indicates that after the FDBus server 111 of the QNX system 201 starts up, it communicates with the microcontroller unit 22 through the SPI driver.
[0063] QNX system 201 starts the first name service unit 113 and the host service unit 115. The first name service unit 113 connects to the host service unit 115 and sends the name and IP address of the first name service unit 113 to the host service unit 115.
[0064] Android system 202 starts the second name service unit 114 and sends the name and IP address of the second name service unit 114 to the host service unit 115.
[0065] The second name service unit 114 on the Android system 202 side obtains information from the first name service unit 113 from the host service unit 115 and establishes a connection with it;
[0066] The FDBus server 111, started on the QNX system 201 side, registers relevant information with the first name service unit 113;
[0067] The QNX system 201 side starts the second FDBus client 116 and registers relevant information to the first name service unit 113;
[0068] The Android system 202 side starts the first FDBus client 112 and registers relevant information to the second name service unit 114;
[0069] The first FDBus client 112, which is started on the Android system 202 side, sends the information of the FDBus server 111 that it wants to connect to to the second name service unit 114. The second name service unit 114 feeds back the specific URL to the first FDBus client 112. Based on the feedback information, the first FDBus client 112 directly connects to the FDBus server 111.
[0070] The initial connection establishment process is now complete. It should be noted that the order of some steps in the above startup process can be rearranged depending on the actual situation.
[0071] Communication process between microcontroller unit 22 and FDBus client:
[0072] The microcontroller unit 22 is responsible for collecting signals related to the actual vehicle, such as vehicle speed and power status, and sending the data to the FFBus server 111 on the QNX system 201 side through the SPI communication module 103. The FFBus server 111 parses the data according to the SPI protocol.
[0073] After caching the parsed data, the FDBus server 111 sends it to the first FDBus client 112 and the second FDBus client 116 that need the data through the FDBus interface.
[0074] Communication process between the first FDBus client 112 and the second FDBus client 116:
[0075] The first FFBus client 112 is responsible for collecting setting-related signals from the Android system 202 side, such as theme and time format, and sending the data to the FFBus server 111 through the FFBus interface. The FFBus server 111 is responsible for caching the data.
[0076] After caching the data, the FDBus server 111 sends it to the second FDBus client 116 that needs the data through the FDBus interface.
[0077] Based on the same concept, the vehicle provided in this disclosure includes various structures of the intelligent cockpit system in any of the above embodiments. To avoid repetition, these will not be described again here.
[0078] The preferred embodiments of this disclosure have been described in detail above with reference to the accompanying drawings. However, this disclosure is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this disclosure, various simple modifications can be made to the technical solutions of this disclosure, and these simple modifications all fall within the protection scope of this disclosure.
[0079] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, this disclosure will not describe the various possible combinations separately.
[0080] Furthermore, various different embodiments of this disclosure can be combined in any way, as long as they do not violate the spirit of this disclosure, they should also be regarded as the content disclosed in this disclosure.
[0081] It should be noted that in this disclosure, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0082] The various embodiments in this disclosure are described in a related manner. For the same or similar parts between the various embodiments, please refer to each other. Each embodiment focuses on describing the differences from other embodiments. For the same or similar parts, please refer to the description of the method embodiments.
Claims
1. An intelligent cockpit system, characterized in that, Comprising: a first chip unit (11) and a second chip unit (12); the first chip unit (11) comprises a first system module (101) and a second system module (102), the first system module (101) comprises an FDBus server (111), the second system module (102) comprises at least one first FDBus client (112), the FDBus server (111) is used to send first cabin data to the first FDBus client (112), different first FDBus clients (112) are used to execute different first cabin services, the FDBus server (111) is in communication connection with the first FDBus client (112), and the second chip unit (12) comprises an SPI communication module (103). The FDBus server (111) is in communication connection with the SPI communication module (103).
2. The intelligent cabin system of claim 1, wherein, The first system module (101) further comprises at least one second FDBus client (116), the FDBus server (111) is connected with the second FDBus client (116), and the FDBus server (111) is further used to send second cabin data to the second FDBus client (116). Different second FDBus clients (116) are used to execute different second cabin services.
3. The intelligent cabin system according to claim 1, characterized in that the first system module (101) further comprises a first name service unit (113), the first name service unit (113) is connected with the FDBus server (111), and the first name service unit (113) is used to receive network information registered by the FDBus server (111); the second system module (102) comprises a second name service unit (114), the second name service unit (114) is connected with the first FDBus client (112) and the first name service unit (113) respectively, and the second name service unit (114) is used to receive network information registered by the first FDBus client (112).
4. The intelligent cabin system of claim 3, wherein, The first system module (101) further comprises a host service unit (115), the host service unit (115) is connected with the first name service unit (113) and the second name service unit (114) respectively, and the host service unit (115) is used to receive network information registered by the first name service unit (113) and network information registered by the second name service unit (114).
5. The intelligent cabin system of claim 3 or 4, wherein, The network information comprises a node name and an IP address of a network node, and the network node is any one of the FDBus server (111), the first FDBus client (112), the first name service unit (113), the second name service unit (114), and the host service unit (115).
6. The intelligent cabin system of claim 1, wherein, The FDBus server (111) comprises a cache module, which is used for caching data received by the FDBus server (111).
7. The intelligent cabin system of claim 1, wherein, The first chip unit (11) is a system-level chip (21), and the second chip unit (12) is a microcontroller unit (22).
8. The intelligent cabin system of claim 1, wherein, The FDBus server (111) is connected with the SPI communication module (103) through an SPI communication bus.
9. The intelligent cabin system of claim 1, wherein, The first system module (101) is a QNX system (201), and the second system module (102) is an Android system (202).
10. A vehicle characterized by comprising: An intelligent cockpit system comprising the system of any one of claims 1-9.