Networking methods, communication methods, devices and vehicles for cockpit IoT

By establishing a long-term two-way Bluetooth connection and relay node in the cockpit IoT system, the network performance problem when connecting a large number of IoT peripherals to in-vehicle devices is solved, achieving stable and efficient data and command transmission, expanding the number of peripherals that can be accessed, and reducing connection latency and power consumption.

CN123124139APending Publication Date: 2026-11-17CHONGQING CHANGAN AUTOMOBILE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611325795.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-28
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The limited Bluetooth channels in vehicles cannot be expanded indefinitely, leading to increased competition for broadcast channels when in-vehicle devices connect to a large number of IoT peripherals, frequent scheduling conflicts, increased packet loss and retransmission rates, and poor network performance.

Method used

By establishing a long-term, two-way Bluetooth connection between the first and second nodes in the cockpit IoT system, and identifying a relay node in the second node, a third node is connected to the relay node, forming a Bluetooth topology network to achieve two-way transmission of data and commands.

Benefits of technology

It breaks through the limitation on the number of Bluetooth channels in vehicle devices, significantly expands the total number of peripherals that can be accessed in the cabin, reduces connection latency and power consumption, and enhances network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123124139A_ABST
    Figure CN123124139A_ABST
Patent Text Reader

Abstract

This invention provides a networking method, communication method, device, and vehicle for a cockpit IoT system, relating to the field of cockpit IoT technology. The method is applied to a cockpit IoT system, which is a Bluetooth topology network. The cockpit IoT system includes a first node, multiple second nodes, and a third node. The first node is integrated into an in-vehicle device, and the second and third nodes are Bluetooth terminal nodes within the cockpit. The method includes: establishing a long-term bidirectional Bluetooth connection between the first node and each of the second nodes; determining a relay node among the multiple second nodes, and establishing a long-term bidirectional Bluetooth connection between the relay node and the corresponding third node. This invention can expand the total number of peripherals that can be accessed within the cockpit and enhances the network performance of the cockpit IoT in dynamic vehicle environments.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of cockpit IoT technology, specifically to a cockpit IoT networking method, communication method, device, and vehicle. Background Technology

[0002] With the development of intelligent connected vehicles, the level of intelligence and personalization in cockpits continues to improve, and the variety and quantity of in-vehicle IoT peripherals are growing rapidly, covering a wide range of types such as smart aromatherapy, air purifiers, ambient lighting, and health monitoring devices. In-vehicle devices need to simultaneously complete the discovery, connection, and data interaction of a large number of peripherals, which places higher demands on the carrying capacity of short-range communication systems.

[0003] Currently, Bluetooth technology is the primary method for connecting in-vehicle devices to IoT peripherals due to its low power consumption and good compatibility. However, the Bluetooth channel of the in-vehicle host is limited by the radio frequency channel, chip processing power, and protocol stack concurrency limits, and cannot be infinitely expanded. When the number of connected devices exceeds the threshold, broadcast channel contention intensifies, scheduling conflicts occur frequently, packet loss rate and retransmission rate increase, leading to poor network performance. Summary of the Invention

[0004] The purpose of this invention is to provide a networking method, communication method, device, and vehicle for cockpit IoT, so as to solve the problem that the current in-vehicle equipment connecting a large number of in-vehicle IoT peripherals will result in poor network performance.

[0005] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0006] In a first aspect, the present invention provides a networking method for a cockpit Internet of Things (IoT) system, which is a Bluetooth topology network. The cockpit IoT system includes a first node, multiple second nodes, and a third node. The first node is integrated on an in-vehicle device, and the second and third nodes are both Bluetooth terminal nodes in the cockpit. The method includes: establishing a long-term bidirectional Bluetooth connection between the first node and each of the second nodes; determining a relay node among the multiple second nodes, and establishing a long-term bidirectional Bluetooth connection between the relay node and the corresponding third node.

[0007] Furthermore, establishing a long-term bidirectional Bluetooth connection between the first node and each of the second nodes includes: configuring a first interaction feature value for the first node, which is used for data transmission between the first node and the second nodes; executing the operation of the second node to complete network access to the first node; and establishing a low-level physical connection between the first node and the second nodes based on the idle Bluetooth channel of the first node.

[0008] Furthermore, the first interactive feature value includes: a first uplink data transmission feature value and a first downlink command transmission feature value. The first uplink data transmission feature value is used to receive data uploaded by the second node, and the first downlink command transmission feature value is used to send control commands of the vehicle-mounted device to the second node.

[0009] Furthermore, the operation of the second node completing the network access to the first node includes: for each second node, the second node broadcasts a first network access request, the first network access request carrying the identity information of the second node; the first node receives the first network access request and verifies the identity information of the second node, and if the identity information of the second node is verified and the first node has an idle Bluetooth channel, the second node is allowed to access the first node.

[0010] Furthermore, establishing a long-term, two-way Bluetooth connection between the relay node and the corresponding third node includes: configuring a second interaction feature value for the relay node, which is used for data transmission between the relay node and the corresponding third node; executing the operation for the corresponding third node to complete network access to the relay node; and establishing an underlying physical connection between the third node and the relay node.

[0011] Furthermore, the second interactive feature value includes: a second uplink data transmission feature value and a second downlink command transmission feature value. The second uplink data transmission feature value is used to receive data uploaded by the third node, and the second downlink command transmission feature value is used to send control commands of the vehicle-mounted device to the third node.

[0012] Furthermore, the method also includes: establishing a mapping relationship between the first uplink data transmission feature value and the second uplink data transmission feature value through the first node, and establishing a mapping relationship between the first downlink command transmission feature value and the second downlink command transmission feature value.

[0013] Furthermore, the operation of the corresponding third node completing the network access to the relay node includes: for each third node, the third node broadcasts a second network access request, which carries the identity information of the third node; the relay node receives the second network access request and sends it to the first node for verification; if the first node verifies the identity information of the third node and the number of third nodes already connected to the relay node is less than the maximum number of primary connections allowed by the relay node, the first node notifies the relay node to allow the third node to access the relay node.

[0014] Furthermore, determining a relay node among multiple second nodes includes: determining a relay node among multiple second nodes when the number of second nodes connected to the first node is equal to a preset number threshold.

[0015] Furthermore, the cockpit IoT system also includes a fourth node, and the method further includes: determining a secondary relay node among multiple third nodes when the number of third nodes connected to the relay node is equal to the maximum number of primary connections of the relay node; and establishing a long-term bidirectional Bluetooth connection between the secondary relay node and the corresponding fourth node.

[0016] Furthermore, it also includes: determining the data transmission delay between the first node and each third node; and rejecting any new node from accessing any node in the cockpit IoT system if the data transmission delay is greater than or equal to the delay threshold.

[0017] Secondly, embodiments of the present invention provide a communication method applied to a cockpit IoT system. The cockpit IoT system is a Bluetooth topology network, comprising a first node, multiple second nodes, and a third node. The first node is integrated into an in-vehicle device, and the second and third nodes are both in-cabin Bluetooth terminal nodes. The multiple second nodes include a relay node. The method includes: a third node sending data to be transmitted to a relay node via a long-term bidirectional Bluetooth connection between the third node and the relay node; a relay node forwarding the data to be transmitted to the first node via a long-term bidirectional Bluetooth connection between the relay node and the first node; and / or, a first node sending a command to be transmitted to a relay node via a long-term bidirectional Bluetooth connection between the relay node and the first node; and a relay node sending a command to be transmitted to the third node via a long-term bidirectional Bluetooth connection between the third node and the relay node.

[0018] Thirdly, embodiments of the present invention provide a networking device for a cockpit Internet of Things (IoT) system, applied to a cockpit IoT system. The cockpit IoT system is a Bluetooth topology network, comprising a first node, multiple second nodes, and a third node. The first node is integrated into an in-vehicle device, and the second and third nodes are both in-cabin Bluetooth terminal nodes. The device includes:

[0019] The first establishment module is used to establish a long-term, two-way Bluetooth connection between the first node and each of the second nodes.

[0020] The second establishment module is used to determine the relay node among multiple second nodes and establish a long-term Bluetooth bidirectional connection between the relay node and the corresponding third node.

[0021] Fourthly, embodiments of the present invention provide a communication device applied to a cockpit Internet of Things (IoT) system. The cockpit IoT system is a Bluetooth topology network, comprising a first node, multiple second nodes, and a third node. The first node is integrated into an in-vehicle device, and the second and third nodes are both in-cabin Bluetooth terminal nodes. The multiple second nodes include relay nodes. The device includes:

[0022] The first transmission module is used to transmit data from the third node to the relay node via a long-term, two-way Bluetooth connection between the third node and the relay node; and to forward data to the first node via a long-term, two-way Bluetooth connection between the relay node and the first node; and / or,

[0023] The second transmission module is used to send the instruction to be transmitted from the first node to the relay node through a long-term two-way Bluetooth connection between the relay node and the first node; and to send the instruction to be transmitted from the relay node to the third node through a long-term two-way Bluetooth connection between the third node and the relay node.

[0024] Fifthly, embodiments of the present invention provide an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0025] The memory stores instructions that the computer executes;

[0026] The processor executes computer execution instructions stored in memory to implement the methods provided in the first or second aspect above.

[0027] In a sixth aspect, embodiments of the present invention provide a vehicle, including: a vehicle body and electronic equipment as provided in the fifth aspect above.

[0028] In a seventh aspect, embodiments of the present invention provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the methods provided in the first or second aspect above.

[0029] Eighthly, embodiments of the present invention provide a computer program product, comprising: a computer program, which, when executed by a processor, implements the method provided in the first or second aspect above.

[0030] The beneficial effects of this invention are:

[0031] This invention provides a networking method, communication method, device, and vehicle for a cockpit IoT. It establishes a long-term, bidirectional Bluetooth connection between a first node and a second node, then identifies relay nodes within the second node to connect numerous third nodes. This overcomes the limitation on the number of Bluetooth channels for in-vehicle devices, significantly expanding the total number of peripherals that can be connected within the cockpit. Furthermore, the bidirectional, long-term connections between the first and second nodes, and between the relay nodes and the third nodes, avoid frequent role switching and temporary connection overhead, effectively reducing connection latency and power consumption, and enhancing the network performance of the cockpit IoT in dynamic vehicle environments. Attached Figure Description

[0032] Figure 1 This is a structural diagram illustrating an application scenario provided in an embodiment of the present invention;

[0033] Figure 2 A flowchart illustrating the networking method for the cockpit Internet of Things provided in an embodiment of the present invention;

[0034] Figure 3 A schematic diagram of the uplink data transmission process provided in an embodiment of the present invention;

[0035] Figure 4 A schematic diagram of the downlink command transmission process provided in an embodiment of the present invention;

[0036] Figure 5 A schematic diagram of the networking device for the cockpit Internet of Things provided in an embodiment of the present invention;

[0037] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention.

[0038] The accompanying drawings have illustrated specific embodiments of the invention, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the invention in any way, but rather to illustrate the concept of the invention to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0039] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.

[0040] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0041] 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 the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

[0042] The terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, product, 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 process, method, product, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in the process, method, product, or apparatus that includes elements is not excluded. For example, the use of terms such as "first," "second," etc., to indicate names does not imply any particular order.

[0043] Currently, the in-vehicle IoT peripherals include: multi-zone ambient lighting (2-4 channels in the front row and 2-4 channels in the rear row), intelligent fragrance system, seat ventilation / heating / massage controllers (2 in the front row and 2 in the rear row), rear entertainment control terminal, in-vehicle cup heating / cooling device, cabin storage box temperature control device, in-vehicle air purifier, rear ambient lighting control panel, etc., indicating that there are a large number of in-vehicle IoT peripherals.

[0044] Currently, BLE access technologies for automotive IoT peripherals mainly fall into three major categories, all of which suffer from the inability to adapt to the core constraints of automotive scenarios, as detailed below:

[0045] (1) BLE (Bluetooth Low Energy) direct connection solution: Based on the Bluetooth SIG (Bluetooth Special Interest Group) standard BLE protocol, the vehicle device acts as the BLE host and directly establishes point-to-point connections with each vehicle IoT peripheral to realize data interaction and command control. The core drawback of this solution is that the hardware resources and protocol stack limitations of the native BLE host of the general vehicle device only support a maximum of 7 concurrent master connections. Among them, 3-4 connections are already occupied by core functions such as mobile phone Bluetooth calls, mobile phone interconnection, and vehicle microphones. Only a few idle connections are left, which cannot meet the simultaneous access requirements of more than 10 peripherals. If the number of connections is forcibly increased, it will cause the core functions to lag and disconnect, and it will not pass the vehicle manufacturer's access test.

[0046] (2) BLE Mesh (Bluetooth Low Energy Mesh Network) networking solution: Based on the Bluetooth SIG standard BLE Mesh protocol, multi-device networking is achieved through broadcast flooding mechanism. Theoretically, it can support thousands of nodes to access, which seems to solve the problem of insufficient connection number. However, there are three problems: First, the end-to-end latency is high. Due to the use of broadcast flooding forwarding, the message redundancy is high and the collision probability is high. The end-to-end latency is generally high and cannot meet the real-time control requirements of peripherals (such as ambient light brightness adjustment and seat heating on). Second, the development complexity is high. Complex dynamic routing algorithms and message parsing mechanisms need to be developed. The development cycle of a single project is long and the development cost is high. Third, the adaptation of vehicle equipment is difficult. Traditional BLE Mesh has no central node and cannot be efficiently linked with the control center of vehicle equipment. Moreover, message flooding will occupy a large amount of 2.4GHz frequency band resources of vehicle terminals and interfere with vehicle equipment WiFi and Bluetooth keys, and cannot pass the vehicle EMC (Electromagnetic Compatibility) test.

[0047] (3) General BLE Cascading Transparent Transmission Solution: This solution is mostly adapted from smart home scenarios. The core is to achieve simple cascading transparent transmission through BLE broadcast mode, that is, after the first-level slave device receives the master device's instruction, it forwards it to the second-level slave device through broadcast. The problems with this solution are: there is no bidirectional stable long-term connection, it only supports one-way instruction issuance, and it cannot realize the reporting of peripheral device status data (such as fragrance concentration, seat temperature feedback); the communication reliability is poor, the broadcast transparent transmission is easily interfered with, the packet loss rate is generally high, and it cannot meet the stability requirements of mass production in vehicles; no optimization has been made for the vehicle-specific scenario where the connection resources of vehicle devices are limited, and the cascading node still needs to occupy a lot of connection resources of the vehicle device, which conflicts with the core functions of the vehicle device and cannot be applied in the vehicle.

[0048] To address the aforementioned issues, this invention establishes a long-term, two-way Bluetooth connection between the first and second nodes, while distributing a large number of third nodes to relay nodes within the second node. This overcomes the limitation on the number of Bluetooth channels for in-vehicle devices, significantly expanding the total number of peripherals that can be connected within the cockpit. Furthermore, the two-way, long-term connections between the first and second nodes, and between the relay nodes and the third nodes, avoid frequent role switching and temporary connection overhead, effectively reducing connection latency and power consumption, and enhancing the network performance of the cockpit IoT in dynamic vehicle environments.

[0049] The following is a combination of... Figure 1 The application scenarios of the embodiments of the present invention are described.

[0050] Figure 1 A structural diagram illustrating an application scenario provided in an embodiment of the present invention. For example... Figure 1 The diagram illustrates an application scenario applicable to embodiments of the present invention. Figure 1In the cockpit IoT system, there are: a first node, multiple second nodes, and multiple third nodes.

[0051] The first node includes multiple Bluetooth channels, such as Figure 1 Of the 7 Bluetooth channels, Bluetooth channels 1 and 2 are disabled for connecting Bluetooth devices, Bluetooth channels 6 and 7 are already connected to the necessary Bluetooth devices (such as atomic nodes S1 and S2), and there are 3 remaining free Bluetooth channels: Bluetooth channel 3, Bluetooth channel 4 and Bluetooth channel 5. Each Bluetooth channel is used to connect one Bluetooth device.

[0052] Furthermore, after the second node a1 comes online, it can establish a connection with the first node via Bluetooth channel 3; after the second node a2 comes online, it can establish a connection with the first node via Bluetooth channel 4; after the second node a3 comes online, it can establish a connection with the first node via Bluetooth channel 5; when the third node b1 needs to establish a connection with the first node, since the first node has no free Bluetooth channel, the second node a2 can be selected as the relay node among the multiple second nodes, and the third node b1 can be connected to the second node a2. After the third nodes b2 to b5 come online, they can connect to the second node a2 in sequence. When the number of third nodes connected to the second node a2 reaches the maximum number of connections allowed by the second node a2, one of the third nodes (such as the third node b4) can be selected as the relay node, and the new fourth nodes c1 and c2 can be connected to the relay node. Thus, the networking of each node can be completed.

[0053] In this invention, the first node, as the root node, can be integrated into the vehicle's onboard equipment. This onboard equipment can be an onboard terminal, a cockpit IoT gateway, or other onboard devices, without limitation. As the core hub of the cockpit IoT system, the first node does not require additional independent hardware and can reuse existing hardware resources from the onboard terminal or cockpit IoT gateway.

[0054] Furthermore, the relay node is an independent Bluetooth master-slave integrated terminal device that can be deployed in the central area of ​​the cockpit. The relay node is small in size, easy to install, and supports common vehicle power supply methods.

[0055] In this invention, child nodes that are not relay nodes (such as second node a1, second node a3, third node b1, third node b2, third node b3, third node b5, fourth node c1, and fourth node c2) are deployed on in-vehicle IoT peripherals. For example, since they all use standard BLE slave chips, the third node does not need to have master-slave integration functionality, which has the advantages of low cost, low power consumption, and adaptability to the control requirements of various in-vehicle IoT peripherals.

[0056] Among them, the cockpit IoT system can be deployed in various vehicles such as passenger cars, commercial vehicles, sedans, SUVs, trucks, buses, engineering vehicles, autonomous vehicles, and unmanned delivery vehicles.

[0057] The following is based on the above. Figure 1 The cockpit IoT system shown is the main execution entity. The specific implementation method of the cockpit IoT networking method provided by the embodiments of the present invention will be described in detail with reference to specific embodiments.

[0058] Figure 2 A flowchart illustrating the networking method for the cockpit Internet of Things provided in this embodiment of the invention. Figure 1 .like Figure 2 As shown, this cockpit IoT networking method is applied to a cockpit IoT system, which is a Bluetooth topology network. The cockpit IoT system includes a first node, multiple second nodes, and a third node. The first node is integrated into the vehicle's onboard equipment, while the second and third nodes are Bluetooth terminal nodes within the cockpit. The specific implementation may include the following steps:

[0059] S201, establish a long-term, two-way Bluetooth connection between the first node and each of the second nodes.

[0060] The number of second nodes connected to the first node is less than or equal to the first connection number, which is a preset number of idle Bluetooth channels, such as... Figure 1 As shown, the number of idle Bluetooth channels in the first node is 3.

[0061] In this invention, based on an idle Bluetooth channel, a stable and continuous Bluetooth bidirectional long-term connection is established with each of the second nodes, enabling bidirectional transmission of control commands and sensor data between the first node and each of the second nodes. A Bluetooth bidirectional long-term connection refers to a Bluetooth connection mode that maintains bidirectional data transmission and reception capabilities between nodes, suppresses frequent disconnections and reconnections, and achieves continuous, stable, and long-term communication.

[0062] In the specific implementation process, the first node monitors the occupancy of the Bluetooth channel of the vehicle equipment and selects the free Bluetooth channel to reserve for the second node to access. The first node can lock the free Bluetooth channel to prevent it from being occupied by other core functions.

[0063] In this invention, the Bluetooth channel is a limited hardware and logic resource that can be used to establish and maintain Bluetooth communication links, including the maximum concurrent connection link, radio frequency channel, communication time slot, data cache and device scanning capability. There is an upper limit to the number of hardware connections of in-vehicle devices. If a large number of cabin Bluetooth peripherals are directly connected, this resource will be exhausted, causing the devices to be unable to pair, communication to be interrupted and disconnected.

[0064] In one optional implementation, the model of the target vehicle corresponding to the vehicle-mounted device can be determined; the number of vehicles with a preset mapping relationship can be obtained as the first connection number.

[0065] In this invention, the vehicle-mounted equipment is deployed in the target vehicle, and the number of initial connections varies depending on the vehicle model. The first node can first determine the vehicle model of the target vehicle corresponding to the vehicle-mounted equipment, and then obtain the number of connections that have a preset mapping relationship with the vehicle model as the first number of connections.

[0066] In another optional implementation, the total number of Bluetooth channels of the vehicle-mounted device can be obtained, and the number of occupied connections of Bluetooth channels already occupied by preset functions can be determined; based on the total number of connections and the number of occupied connections, a first number of connections can be determined. That is, the first number of connections is the total number of connections minus the number of occupied connections.

[0067] The preset functions can be core functions of the in-vehicle device, such as Bluetooth phone calls and smartphone connectivity. In this invention, the total number of connections for the in-vehicle device is fixed.

[0068] For example, this embodiment is for a vehicle cabin scenario, referring to... Figure 1 The in-vehicle equipment only supports 5 concurrent main connections, of which 2 are occupied by Bluetooth phone calls and mobile phone interconnection, leaving only 3 free Bluetooth channels. 14 in-vehicle IoT peripherals need to be connected in the cabin, specifically including: 2 front ambient lights, 2 rear ambient lights, 2 front seat heating / ventilation controllers, 2 rear seat heating controllers, 1 smart fragrance system, 1 in-vehicle cup heater, 1 cabin storage box temperature control device, 1 in-vehicle air purifier, and 1 rear ambient light control panel. This embodiment uses relay nodes, and at least one relay node can be deployed, such as installed in the front armrest box (responsible for connecting front peripherals) and / or in the rear center armrest (responsible for connecting rear peripherals). The first node is integrated into the vehicle's infotainment system, using automotive-grade hardware to achieve stable networking and control across all scenarios. The number of second nodes, relay nodes, and third nodes connected in this embodiment are only specific application examples and are not limitations on the scope of protection. Different vehicle models can flexibly adjust these based on their own vehicle's available connections and relay node hardware capabilities.

[0069] In this invention, the first node includes a first Bluetooth communication unit, a topology management unit, a first forwarding service unit, an in-vehicle resource adaptation unit, a first anomaly handling unit, and a first auxiliary hardware unit.

[0070] Specifically, the first Bluetooth communication unit conforms to the standard BLE automotive grade, selects core chips that are adapted to automotive grade requirements, supports concurrent connections in master mode, and the communication distance and operating temperature range meet the requirements of the vehicle environment. It connects to the main control unit of the first node through a standard interface, supports a limited number of concurrent master connections adapted to different vehicle models, and is used to establish a long-term bidirectional Bluetooth connection with the second node. It fully complies with Bluetooth certification requirements, supports standard universal protocols, can achieve reliable data transmission and reception, and adapts to the differences in Bluetooth channels of different vehicle models.

[0071] The topology management unit is integrated into the main control unit of the first node and is implemented using software logic. The functions of the topology management unit include: identity authentication of the second and third nodes, network access management, topology information maintenance, whitelist configuration and update, offline node marking and management; it can store the topology information of a limited number of third nodes, support real-time updates and queries of topology information, and provide support for data forwarding and command scheduling.

[0072] The first forwarding service unit is built on the standard BLE GATT (Generic Attribute Profile) layer and is implemented using software encapsulation. It does not require modification of the underlying protocol. The functions of the first forwarding service unit include: initialization of GATT forwarding service, management of first interaction feature values, parsing and verification of data frames, and data pass-through control. It supports custom feature identifiers and can adjust data format and verification rules according to mass production requirements.

[0073] The vehicle-mounted system resource adaptation unit is integrated into the first node main control unit and is implemented using software logic. The functions of the vehicle-mounted system resource adaptation unit include: real-time monitoring of the occupancy of the vehicle Bluetooth channels, identifying Bluetooth channels that have been occupied by other core functions, filtering and locking idle Bluetooth channels, avoiding resource conflicts with other core functions, and dynamically adjusting the number of relay nodes connected based on the differences in idle Bluetooth channels of different vehicle models; if there are insufficient idle Bluetooth channels, an alarm command is immediately sent to notify the user to release some non-core function Bluetooth channels.

[0074] The first anomaly handling unit is integrated within the first node main control unit and is implemented using software logic. The functions of the anomaly handling unit include: monitoring the link status with the second node through a heartbeat mechanism, processing the reconnection request of the second node, receiving the anomaly information of the third node reported by the relay node, updating the offline node status, and sending anomaly alarm prompts to the vehicle system.

[0075] The first auxiliary hardware unit includes a main control unit adapted to automotive-grade requirements, a local storage unit that meets operational storage needs, a bus interface for communication with the vehicle's infotainment system, and a power management unit that meets vehicle requirements, covering various needs such as automotive-grade functional safety, storage, communication, and protection.

[0076] S202, determine the relay node among multiple second nodes, and establish a long-term two-way Bluetooth connection between the relay node and the corresponding third node.

[0077] In this invention, the number of relay nodes should be within a reasonable range, that is, the number of relay nodes should not exceed the first connection limit. If the number of relay nodes exceeds the first connection limit, it will occupy the Bluetooth channels of other atomic nodes, which will cause resource conflicts with core functions such as Bluetooth phone calls and mobile phone interconnection, resulting in core functions lag and disconnection, and failing the vehicle manufacturer's access test.

[0078] In some embodiments, to ensure that more in-vehicle IoT peripherals can be connected and to ensure the quality of Bluetooth communication, the number of relay nodes can be determined to be 1.

[0079] Each relay node adopts a BLE master-slave integrated design with a clear division of roles. Upward, it acts as a slave to maintain a stable, long-term, two-way Bluetooth connection with the first node, enabling two-way interaction of data and commands. Downward, it acts as a master to connect to a third node, up to the maximum number of master connections for that relay node, enabling centralized management and data transmission of the third node. The number of third nodes that can be connected can be flexibly adjusted according to the hardware capabilities of the relay node and the distribution of in-vehicle IoT peripherals.

[0080] In this invention, the relay node includes: a second Bluetooth communication unit, a second forwarding service unit, a node access management unit, a lightweight anti-interference unit, a second local anomaly handling unit, and a second auxiliary hardware unit.

[0081] Specifically, the second Bluetooth communication unit uses an industrial-grade or automotive-grade BLE chip, and selects the corresponding level solution to adapt to different mass production needs. It supports simultaneous operation of master and slave roles, and the mature supply chain is adapted to mass production requirements. It supports simultaneously establishing a long-term two-way Bluetooth connection with the first node as a slave, and establishing a long-term two-way Bluetooth connection with a limited number of third nodes as a master. The number of third nodes can be flexibly adjusted according to hardware capabilities, and the communication distance and operating temperature range are adapted to the cabin environment.

[0082] The second forwarding service unit is built on the standard BLE GATT layer and implemented using software encapsulation. It corresponds to the first forwarding service unit of the first node. The functions of the second forwarding service unit include: initialization of the second forwarding service unit, management of the second interaction feature value, parsing and verification of data frames, and bidirectional data pass-through control between the third node and the first node. It does not modify the underlying protocol and fully complies with Bluetooth certification requirements. At the same time, it integrates triggering logic to ensure the real-time forwarding of data commands and strictly enforces the rule of only passing through and not processing business data.

[0083] The node access management unit is implemented using software logic. Its functions include: third-node identity authentication, network access management, topology binding, third-node information synchronization, and control of the number of third-node accesses. The access scale can be flexibly adjusted according to hardware capabilities.

[0084] The lightweight anti-interference unit is designed for low-frequency control scenarios in the cockpit. It is implemented using software logic and does not require complex full-network timing synchronization. Its functions include: allocating staggered connection intervals to each third-level node to avoid co-frequency collisions; and performing random backoff and retransmission after detecting interference and packet loss to reduce the probability of collisions. It can effectively control the packet loss rate caused by co-frequency interference and ensure highly reliable transmission.

[0085] The second anomaly handling unit is implemented using software logic. Its functions include: monitoring the link status with the first node and the third node through a heartbeat mechanism, processing the reconnection request of the third node, caching the data reported by the third node, reporting link anomaly information to the first node, notifying the third node to switch to a backup relay node, and ensuring network continuity through a node loss and rejoining mechanism.

[0086] The second auxiliary hardware unit includes a PCB (Printed Circuit Board) onboard antenna to ensure signal coverage in the cockpit, an ESD (Electro-Static Discharge) protection circuit that meets automotive EMC (Electromagnetic Compatibility) requirements, a status indicator circuit that displays different operating states, and a power management unit that supports multiple power supply methods and integrates protection functions.

[0087] Among them, the number of third nodes connected to the relay node is less than or equal to the maximum number of primary connections allowed by the corresponding relay node.

[0088] In this invention, the number of third nodes connected to the relay node should be within a reasonable range. If the number of third nodes connected to the relay node exceeds the maximum number of main connections allowed, it will cause the Bluetooth channel of the relay node to be exhausted and increase the probability of co-channel interference, resulting in increased communication latency and decreased reliability, which will fail to meet the real-time control requirements of the vehicle.

[0089] Furthermore, as a Bluetooth master-slave integrated terminal device, the relay node has its own Bluetooth channel, so a long-term bidirectional Bluetooth connection can be established between the relay node and the corresponding third node based on the relay node's Bluetooth channel.

[0090] In this configuration, a relay node can establish a long-term, two-way Bluetooth connection with only a portion of the multiple in-vehicle IoT peripherals. In some implementations, the relay node establishes a long-term, two-way Bluetooth connection with in-vehicle IoT peripherals within a preset range. For example, a relay node installed in the front armrest is used to connect to front-seat in-vehicle IoT peripherals, and a relay node installed in the rear center armrest is used to connect to rear-seat in-vehicle IoT peripherals.

[0091] In this invention, after the cockpit IoT system is networked, the first node is the sole control hub of the entire cockpit IoT system. It does not require additional independent hardware and is responsible for coordinating the topology management, data forwarding, command scheduling, and anomaly handling of the entire cockpit IoT system. It only occupies idle Bluetooth channels and can dynamically adjust the number of second nodes connected based on the differences in the number of first connections for different vehicle models without affecting the normal operation of the vehicle's core functions. The first node is responsible for receiving control commands issued by the vehicle's devices and forwarding them to the corresponding relay nodes, as well as receiving the status data of the third node transmitted by the relay nodes and synchronizing it to the cockpit control interface. It supports deep integration with existing smart cockpit gateways, enabling zero-code, lightweight configuration adaptation of the third node.

[0092] The relay node is a BLE master-slave integrated terminal device, serving as a communication bridge between the first and third nodes. Upward, it acts as a slave, establishing a stable, long-term, bidirectional Bluetooth connection with the first node and receiving control commands from the first node, which are then passed through to the corresponding third node. Downward, it acts as a master, establishing stable, long-term, bidirectional Bluetooth connections with each of the third nodes. It can flexibly adjust the number of third nodes that can connect based on its hardware capabilities, receiving status data reported by the third nodes and passing it through to the first node. It is responsible for managing the third node's network entry, authentication, and topology binding. It resolves co-channel interference by setting node communication intervals and ensures link stability based on node loss and re-entry mechanisms, supporting third node backup switching.

[0093] The third node consists of various in-vehicle IoT peripherals. It only needs to support the standard BLE slave function and can be implemented using a general-purpose BLE slave chip. It is responsible for executing the control commands issued by the first node to complete the corresponding functions, collecting its own working status data and transmitting it to the first node through the relay node to realize status feedback.

[0094] In this invention, after the network is completed, during normal operation, the first node manages all network nodes in a coordinated manner, the relay node is responsible for data transmission and management of the third node, and the third node is responsible for instruction execution and status reporting. When a link anomaly occurs, the node can be automatically reconnected and switched to backup through a lightweight anomaly handling mechanism to ensure the stable operation of the system.

[0095] Based on the networking method provided by this invention, the cockpit IoT system is a Bluetooth topology network containing a first node, multiple second nodes, and a third node. This allows for stable access to multiple in-vehicle IoT peripherals, fully covering the access needs of various vehicle in-vehicle IoT peripherals. The number of nodes accessing the cockpit IoT system can be adjusted according to actual scenario requirements, meeting all in-vehicle service needs without adding additional redundant layers. Simultaneously, this tree-like topology can adapt to the access and exit of third and second nodes in real time, dynamically updating the entire network topology information, ensuring network stability in high-density access scenarios, and avoiding link disruptions caused by node access or exit.

[0096] In practice, after the vehicle IoT peripheral is put into operation, if there is an available Bluetooth channel, the first node allows the vehicle IoT peripheral to establish a long-term two-way Bluetooth connection with the first node as a second node through the available Bluetooth channel; if there is no available Bluetooth channel, the first node determines a relay node among multiple second nodes, and then runs the vehicle IoT peripheral as a third node to establish a long-term two-way Bluetooth connection with the relay node.

[0097] In summary, this embodiment of the invention establishes a long-term bidirectional Bluetooth connection between the first node and the second node, determines a relay node within the second node, and distributes a large number of third nodes to each relay node, thereby breaking through the limitation on the number of Bluetooth channels for in-vehicle devices and significantly expanding the total number of peripherals that can be connected in the cockpit. In addition, the bidirectional long-term connection between the first node and the second node, and between the relay node and the third node, avoids frequent role switching and temporary connection establishment overhead, effectively reduces connection latency and power consumption, and enhances the network performance of the cockpit IoT in the dynamic environment of the vehicle.

[0098] Furthermore, establishing a long-term, two-way Bluetooth connection between the first node and each of the second nodes includes: configuring a first interaction feature value for the first node, which is used for data transmission between the first node and the second nodes; executing an operation for the second node to complete network access to the first node; and establishing a low-level physical connection between the first node and the second nodes based on the idle Bluetooth channel of the first node.

[0099] In this invention, after the first node is powered on, the first node completes the initialization of the BLE protocol stack, sets the BLE version parameters, and configures parameters such as the broadcast interval, connection interval, and connection timeout parameters of the first node.

[0100] Furthermore, the first node configures a dedicated network entry broadcast UUID (Universally Unique Identifier) ​​and access whitelist for the second node, allowing only second nodes within the whitelist to access the network. Simultaneously, the first node initializes its dedicated forwarding service at the standard GATT layer and configures the first interaction characteristic value. After completing all configurations, the first node starts network listening mode, waiting for the second node to join the network.

[0101] After the second node completes the network access operation to the first node, a low-level physical connection is established between the first node and the second node based on an idle Bluetooth channel. Specifically, the second node sends a low-level connection establishment request of the BLE link layer to the first node, the first node allocates an idle Bluetooth channel reserved for the second node, and the two negotiate to determine unified link physical parameters such as connection interval, slave delay, connection timeout, and channel frequency hopping sequence, and complete wireless channel timing synchronization and frequency hopping calibration, thereby establishing a low-level physical connection that can send and receive low-level data packets bidirectionally.

[0102] In this invention, after completing the above parameter configuration, network access operation, and underlying physical connection, a long-term bidirectional Bluetooth connection is established between the first node and each of the second nodes. Subsequently, the second nodes can maintain stable communication with the first node based on this long-term bidirectional Bluetooth connection.

[0103] In summary, this invention achieves a standardized and reusable data transmission channel between the first and second nodes by configuring a first interaction feature value for the first node and then performing network access and underlying physical connection establishment for the second node based on this feature. The first interaction feature value is used for data interaction between the first and second nodes, enabling the first node to efficiently manage the business data streams of multiple second nodes in a one-to-many manner, avoiding parsing overhead and adaptation confusion caused by differences in data formats among different second nodes. Simultaneously, the separation of the network access process from the underlying physical connection design ensures that the second node only occupies an idle Bluetooth channel after connecting to the first node, thus avoiding the ineffective consumption of idle Bluetooth channels by invalid second nodes and guaranteeing the stable establishment and continuous maintenance of long-term connections under resource-constrained conditions.

[0104] Furthermore, the first interactive feature value includes: a first uplink data transmission feature value and a first downlink command transmission feature value. The first uplink data transmission feature value is used to receive data uploaded by the second node, and the first downlink command transmission feature value is used to send control commands of the vehicle-mounted device to the second node.

[0105] Specifically, the first node configures the first uplink data transmission characteristic value, the first downlink command transmission characteristic value, and the corresponding communication attributes at the GATT layer.

[0106] In this invention, communication attributes include: access permissions, corresponding UUID, transmission attributes, etc. Communication attributes may also include other content, which is not limited thereto.

[0107] Specifically, if the second node needs to upload data to the first node, it can write the data to be transmitted into the first uplink data transmission characteristic value and send it to the first node. If the first node needs to send instructions to the second node, it can write the instructions to be transmitted into the first downlink instruction transmission characteristic value and send it to the second node.

[0108] In summary, this invention further refines the first interaction feature value of the first node into a first uplink data transmission feature value and a first downlink command transmission feature value, achieving physical and logical separation of data reporting and command issuance between the first and second nodes. Specifically, the uplink channel is dedicated to carrying data to be transmitted by each second node, while the downlink channel is dedicated to transmitting control commands from the vehicle-mounted equipment. The two channels do not compete for bandwidth or processing resources, thus avoiding priority conflicts caused by large uplink data flows blocking critical downlink commands. Simultaneously, this bidirectional feature value isolation mechanism eliminates the need for the first node to parse command aliasing when receiving data or to consider data interference when issuing commands. This significantly reduces the protocol parsing complexity and error risk for the first node in handling mixed traffic, thereby achieving high-throughput acquisition of uplink data while ensuring ultra-low latency response to downlink control commands. This fully meets the requirements of real-time control and dense sensing in cockpit scenarios.

[0109] Furthermore, the operation of the second node completing the network access to the first node includes: for each second node, the second node broadcasts a first network access request, the first network access request carrying the identity information of the second node; the first node receives the first network access request and verifies the identity information of the second node, and if the identity information of the second node is verified and the first node has an idle Bluetooth channel, the second node is allowed to access the first node.

[0110] Each second node completes its own BLE protocol stack initialization after power-on, with initialization parameters consistent with those of the first node. Then, it broadcasts at broadcast intervals, carrying the first network access request for the first node to scan.

[0111] The first node enables Bluetooth scanning mode and configures the corresponding scanning range and scanning interval. Then, upon detecting a broadcast from the second node, it extracts the first network access request from the broadcast and parses out the identity information of the second node carried in the first network access request.

[0112] In this invention, the identity information of the second node includes at least one of the following: the second node MAC (Media Access Control Address) address, the device model, and the firmware version information.

[0113] Furthermore, upon receiving the first network access request, the first node can extract identity information, such as the MAC address of the second node. The first node has a pre-configured whitelist containing the identity information of each second node. If the received identity information matches the information in the pre-configured whitelist, the identity verification of the second node is successful, allowing the second node to access the first node, and a successful access command is sent to the second node.

[0114] In this invention, if the identity verification of the second node fails, the first node sends an access denial command to the second node. The second node can stop the network access request and re-initiate the scanning and network access request after a specified interval.

[0115] For example, after the second node powers on, it completes the BLE protocol stack initialization, such as configuring the broadcast interval to 100ms, the connection interval to 50ms, and the connection timeout to 1000ms. The vehicle-mounted device has three remaining idle Bluetooth channels, and no more than this number of idle Bluetooth channels are locked for the second node to access; the second node's dedicated network access broadcast UUID (0xFFF0) and access whitelist are configured; the GATT forwarding service (UUID 0xFFE0) is initialized, the first uplink data transmission characteristic value (0xFFE1) and the first downlink command transmission characteristic value (0xFFE2) are bound, and the listening mode is enabled.

[0116] In summary, the second node of this invention exposes its existence in a broadcast manner, enabling the first node to automatically discover and allow the second node to join the network without pre-pairing, significantly reducing manual network configuration intervention. While verifying the legitimacy of the second node's identity, the first node dynamically determines whether the number of currently connected second nodes has not reached the first connection limit, ensuring that each idle Bluetooth channel is only allocated to verified second nodes. This avoids the risk of access by illegal devices or malicious nodes, and also avoids the overload problem of Bluetooth channels being exhausted and existing long-term connections being forced to be interrupted due to blindly accepting network access requests, thus providing a guarantee for the stability and security of the entire cockpit IoT.

[0117] Furthermore, establishing a long-term, two-way Bluetooth connection between the relay node and the corresponding third node includes: configuring a second interaction feature value for the relay node, which is used for data transmission between the relay node and the corresponding third node; executing the operation for the corresponding third node to complete network access to the relay node; and establishing an underlying physical connection between the third node and the relay node.

[0118] After determining that the second node is a relay node, the dedicated forwarding service for the first node is initialized at the standard GATT layer, and a second interaction characteristic value is configured. This second interaction characteristic value is used by the relay node to forward control commands to the corresponding third node, and by the relay node to receive data uploaded by the corresponding third node.

[0119] Furthermore, the relay node is configured with a dedicated network entry broadcast UUID for the third node. After all configurations are completed, the relay node starts the network listening mode and waits for the third node to join the network.

[0120] For example, after the third node powers on, it completes the BLE protocol stack initialization and broadcasts. Once the first node scans the third node's broadcast UUID and determines that the first node currently has no available Bluetooth channels, the third node can then establish a Bluetooth connection with the relay node.

[0121] After the third node completes the network access operation to the relay node, a low-level physical connection is established between the relay node and the third node based on the Bluetooth channel of the relay node. Specifically, the third node sends a low-level connection establishment request of the BLE link layer to the relay node, the relay node allocates a Bluetooth channel, and the two parties negotiate and determine unified link physical parameters such as connection interval, slave delay, connection timeout, and channel frequency hopping sequence to complete wireless channel timing synchronization and frequency hopping calibration, thereby establishing a low-level physical connection that can send and receive low-level data packets bidirectionally.

[0122] In this invention, after completing the above parameter configuration, network access operation, and underlying physical connection, a long-term bidirectional Bluetooth connection is established between the relay node and the corresponding third node. Subsequently, the third node and the relay node can conduct stable communication based on this long-term bidirectional Bluetooth connection.

[0123] In summary, this invention enables each relay node to independently configure a second interactive feature value, allowing each relay node to manage the corresponding third node from its own center. The third node must first complete the network access to the relay node before establishing the underlying physical connection. This ensures that the maximum number of primary connections of the relay node is effectively evaluated before the connection is established, avoiding local network paralysis caused by the relay node being overloaded due to the blind access of the third node.

[0124] Furthermore, the second interactive feature value includes: a second uplink data transmission feature value and a second downlink command transmission feature value. The second uplink data transmission feature value is used to receive data uploaded by the third node, and the second downlink command transmission feature value is used to send control commands of the vehicle-mounted device to the third node.

[0125] Specifically, the relay node is configured at the GATT layer with its second uplink data transmission characteristic value, second downlink command transmission characteristic value, and corresponding communication attributes.

[0126] In this invention, the communication attributes corresponding to the second uplink data transmission feature value and the second downlink instruction transmission feature value include: access permissions, corresponding UUID, transmission attributes, etc. The communication attributes may also include other content, which is not limited thereto.

[0127] Specifically, if a third node needs to upload data to a relay node, it can write the data to be transmitted into the second uplink data transmission characteristic value and send it to the relay node. If a relay node needs to send instructions to a third node, it can write the instructions to be transmitted into the second downlink instruction transmission characteristic value and send it to the corresponding third node.

[0128] In summary, this invention also decomposes the second interactive characteristic value of the relay node into a second uplink data transmission characteristic value and a second downlink command transmission characteristic value, enabling independent dual-channel isolation for data reporting and command issuance between the relay node and its connected third node. This invention provides uplink and downlink separated data transmission capabilities throughout the entire link from the first node to the relay node and from the relay node to the third node. In the uplink direction, the relay node can non-blockingly aggregate sensor data from each third node and forward it to the first node; in the downlink direction, it can independently receive control commands from the first node and accurately distribute them to the third nodes. The cascading of the two-level dual-channel system ensures that the entire communication link is free from crosstalk and congestion caused by the mixing of uplink and downlink traffic.

[0129] Furthermore, the method also includes: establishing a mapping relationship between a first uplink data transmission feature value and a second uplink data transmission feature value through a first node, and establishing a mapping relationship between a first downlink command transmission feature value and a second downlink command transmission feature value.

[0130] After establishing a long-term bidirectional Bluetooth connection between the first node and the relay node, a mapping relationship is further established between the first uplink data transmission feature value and the second uplink data transmission feature value, forming a fixed uplink data transmission path between the first node and the third nodes connected to each relay node. This mapping relationship allows the sensor data uploaded by the third node to be automatically directed to the first uplink feature value of the first node for direct reading by the vehicle-mounted device after being aggregated by the second uplink feature value of the relay node without protocol parsing or address rewriting. This achieves end-to-end transparent transmission of data acquisition by the third node, forwarding by the relay node, and reception by the first node, effectively reducing the data caching and routing overhead of the relay node, shortening the uplink data transmission latency, and avoiding the risk of data distortion or packet loss caused by hierarchical parsing and encapsulation.

[0131] In this invention, a mapping relationship is established between a first downlink command transmission characteristic value and a second downlink command transmission characteristic value. This allows control commands issued by the vehicle-mounted device to be automatically transmitted to the corresponding third node via the second downlink command transmission characteristic value of the corresponding relay node, based on this mapping relationship. This achieves an end-to-end command delivery channel where the first node writes the command, the relay node automatically forwards it, and the third node receives it. This eliminates the need for relay nodes to parse command content or maintain complex routing tables, significantly reducing protocol processing overhead and response latency, and ensuring that commands from the vehicle-mounted device reach the third node with minimal delay.

[0132] The present invention establishes a mapping relationship between feature values, which enables the communication link of the entire cockpit IoT system to be a fixed path, without broadcast flooding, and both uplink data and downlink commands are transmitted along the fixed path; after the system is powered on, it automatically completes initialization, node network access and topology binding, without manual intervention, and automatically completes the establishment and maintenance of the network.

[0133] In summary, this invention constructs an end-to-end logical mapping channel between two levels of feature values. The first node does not need to be aware of the specific identity and access location of the third node; it only needs to write the downlink control command into the first downlink command transmission feature value. This command will then be automatically transmitted to the target third node along the second downlink command transmission feature value of the relay node according to the mapping relationship. Similarly, the sensor data uploaded by the third node is automatically mapped to the first uplink data transmission feature value of the first node after being aggregated by the second uplink data transmission feature value of the relay node, and then read by the vehicle-mounted equipment. This mapping mechanism enables transparent transmission of uplink and downlink data streams. The first and third nodes do not need to maintain complex routing tables or hierarchical addressing protocols. The relay node only performs data forwarding according to a fixed mapping relationship, which greatly reduces the protocol parsing overhead and forwarding latency during data transmission. At the same time, the independent establishment of the uplink and downlink mapping relationship ensures that the control command and sensor data are logically completely isolated and do not interfere with each other. This provides a deterministic data transmission path and predictable communication latency for the cockpit IoT, significantly improving the real-time performance and reliability of the system.

[0134] Furthermore, the corresponding third node performs the operation of completing network access to the relay node, including: for each third node, the third node broadcasts a second network access request, which carries the identity information of the third node; the relay node receives the second network access request and sends it to the first node for verification; if the first node verifies the identity information of the third node and the number of third nodes already connected to the relay node is less than the maximum number of primary connections allowed by the relay node, the first node notifies the relay node to allow the third node to connect to the relay node.

[0135] Among them, the relay node can broadcast its own UUID at preset broadcast intervals for third nodes to scan.

[0136] In this invention, after power-on, the third node completes its own BLE protocol stack initialization, configures the corresponding BLE version requirements, connection interval, and connection timeout parameters, and can broadcast a second network access request at preset broadcast intervals for the relay node to scan. Then, the relay node starts BLE scanning mode to scan for the dedicated network access broadcasts of the third node within the corresponding area. If the corresponding third node broadcast is detected, the identity information in the second network access request is extracted.

[0137] The second network access request carries the identity information of the third node, which includes at least one of the following: the device model, MAC address, and functional attribute information of the third node.

[0138] Furthermore, after receiving the second network access request from the third node, the relay node completes the third node's identity authentication and verifies its compatibility to prevent unauthorized devices from accessing the network. Once the third node's authentication is successful, the network access is confirmed, and the relay node, acting as a BLE host, establishes a standard BLE bidirectional long-term connection with the third node, completing the topology binding between the three nodes.

[0139] For example, after the third node powers on, it completes the BLE protocol stack initialization, such as a connection interval of 100ms and a timeout of 2000ms, and starts broadcasting. After the front armrest box relay node scans the broadcast of the front third node, it extracts the network access request. After the relay node authenticates the request, it establishes the underlying physical connection and completes the topology binding. The number of accesses by the third node does not exceed the maximum number of primary connections allowed by the relay node. After the rear center armrest relay node scans the broadcast of the rear third node, it completes the access and topology binding. The number of accesses by the corresponding third node does not exceed the maximum number of primary connections allowed by the relay node. The relay node synchronizes all third node information to the first node, and the first node establishes a topology management list.

[0140] In addition, the number of third nodes connected to a relay node should not exceed the maximum number of primary connections it is allowed to make. This maximum number of primary connections can be flexibly adjusted according to the relay node's hardware capabilities and the distribution of cockpit peripherals.

[0141] In some embodiments, if the number of accesses by the third node reaches the maximum number of primary connections, the relay node sends an access failure instruction to the third node, and the third node automatically scans other relay nodes' broadcasts and initiates a network access request.

[0142] In some embodiments, if the number of accesses to the third node reaches the maximum number of primary connections, one of the third nodes can be selected as a secondary relay node, allowing the newly requesting node to establish a Bluetooth connection with the secondary relay node as a fourth node.

[0143] After the third node is connected, the relay node synchronizes the device information and connection status of the third node to the first node through a long-term two-way Bluetooth connection. The first node updates the network topology information and establishes a topology management list for subsequent data forwarding and command scheduling.

[0144] In some embodiments, after establishing a long-term Bluetooth bidirectional connection between the relay node and the third node, the relay node synchronizes the device information and connection status of the third node to the first node through the long-term Bluetooth bidirectional connection with the first node. The first node updates the topology information of the cockpit IoT system and establishes a topology management list for subsequent data forwarding and command scheduling.

[0145] In summary, in this invention, the third node can only join the network after being independently authenticated by the relay node with a legitimate identity, avoiding the risk of unauthorized peripheral devices infiltrating the cockpit network through the relay node. At the same time, the relay node dynamically verifies its remaining carrying capacity before establishing a connection, ensuring that its main connection resources are not over-occupied. This not only avoids communication interruption of the third node connected to it due to the overload of a relay node, but also controls the access scale of the entire cockpit IoT to the maximum number of main connections of each relay node. If more third nodes need to be connected, only additional relay nodes need to be added without modifying the configuration of the first node, thus ensuring the security, stability and scalability of the network.

[0146] Further, determining a relay node among multiple second nodes includes: determining a relay node among multiple second nodes when the number of second nodes connected to the first node is equal to a preset number threshold.

[0147] The preset threshold number can be the first number of connections mentioned above, for example... Figure 1 As shown in 3. In addition, the preset quantity threshold can also be other values, and there is no limitation on this.

[0148] In this invention, if a new vehicle IoT peripheral needs to be connected when the number of second nodes reaches a preset threshold, a relay node is determined among the multiple second nodes, and the new vehicle IoT peripheral is connected to the relay node.

[0149] In summary, when the number of second nodes connected to the first node is equal to a preset threshold, the present invention determines a relay node among multiple second nodes, which can increase the number of in-vehicle IoT peripherals connected in the cockpit IoT system.

[0150] Furthermore, the cockpit IoT system also includes a fourth node, and the method further includes: determining a secondary relay node among multiple third nodes when the number of third nodes connected to the relay node is equal to the maximum number of primary connections allowed to the relay node; and establishing a long-term bidirectional Bluetooth connection between the secondary relay node and the corresponding fourth node.

[0151] In some embodiments, when the number of third nodes connected to a relay node is equal to the maximum number of primary connections allowed by the relay node, another relay node can be determined in the second node to connect new in-vehicle IoT peripherals. Alternatively, a secondary relay node can be determined in the third node of the current relay node to connect new in-vehicle IoT peripherals.

[0152] For example, refer to Figure 1 The second node a2, as a relay node, is allowed to connect to a maximum of 5 primary connections. After the number of connected third nodes reaches 5, the third node b4 is determined as a secondary relay node, and the new vehicle IoT peripheral device is connected to this secondary relay node as a fourth node.

[0153] In some alternative implementations, a third-level relay node can be determined among multiple fourth nodes to establish a long-term Bluetooth connection with the fifth node, depending on actual needs. This invention does not limit the number of relay nodes.

[0154] It is understood that the relay node directly connected to the first node is a first-level relay node. This invention does not limit the number of first-level relay nodes, and can be adjusted according to actual needs.

[0155] In this invention, the method for establishing a long-term Bluetooth connection between each node can refer to the method for establishing a connection between the first node and the second node, and between the relay node and the third node, as described above, and will not be repeated here.

[0156] In this invention, if the number of third nodes connected to a relay node has reached the maximum number of primary connections allowed by the relay node, a secondary relay node can be determined among multiple third nodes, and a new in-vehicle IoT peripheral (i.e., a fourth node) can be connected to the secondary relay node, which can increase the number of in-vehicle IoT peripherals connected in the cockpit IoT system.

[0157] Furthermore, it also includes: determining the data transmission delay between the first node and each third node; and rejecting any new node from accessing any node in the cockpit IoT system if the data transmission delay is greater than or equal to the delay threshold.

[0158] During the networking process, if the data transmission delay is greater than or equal to the delay threshold, and a new node needs to connect to the first, second, or third node, the new node's access will be rejected to ensure the communication quality between the existing nodes in the cockpit IoT system.

[0159] In practice, the first node periodically sends heartbeat packets to each third node through relay nodes. The data transmission delay is determined based on the responses from the third nodes. If the current data transmission delay is significant, the first node can reject new node access to ensure the communication needs of already connected nodes. If the data transmission delay is minimal, new node access can be allowed, thus enabling more nodes to join the network.

[0160] In this invention, a tree-like topology structure consisting of a first node, a second node, and a third node is adopted. This tree-like topology structure is precisely matched to the business needs of the in-vehicle cockpit. The number of nodes connected in the cockpit IoT can be adjusted according to the data transmission latency requirements. When the latency is too high, the connection of new nodes can be avoided. This achieves high-density access of in-vehicle IoT peripherals while effectively avoiding problems such as latency accumulation and reduced link reliability caused by too many nodes. This adapts to scenarios where different vehicle models have only a few idle Bluetooth channels remaining in the vehicle's infotainment system.

[0161] Furthermore, this embodiment of the invention also provides a communication method applied to a cockpit IoT system. The cockpit IoT system is a Bluetooth topology network, comprising a first node, multiple second nodes, and a third node. The first node is integrated into an in-vehicle device, and the second and third nodes are both in-cabin Bluetooth terminal nodes. The multiple second nodes include relay nodes. (Refer to...) Figure 3 and Figure 4 ,in, Figure 3 The uplink data transmission process includes the following steps:

[0162] S301, through a long-term two-way Bluetooth connection between the third node and the relay node, the third node sends the data to be transmitted to the relay node;

[0163] The S302 uses a long-term, two-way Bluetooth connection between the relay node and the first node to forward the data to be transmitted to the first node.

[0164] The data to be transmitted includes status data collected by the third node and / or event reporting information.

[0165] In this invention, a BLE notify (Bluetooth notification) event-triggered forwarding mechanism can be used instead of a polling mechanism. No data parsing, modification, or storage operations are performed; only transparent forwarding is executed. The third node assembles the data to be transmitted into data frames according to a preset data format. Then, the first data frame is written into the second uplink data transmission characteristic value of the relay node's GATT layer through a long-term Bluetooth bidirectional connection with the relay node.

[0166] Furthermore, once the second uplink data transmission characteristic value of the relay node's GATT layer is written into the data frame, a notify notification is triggered immediately. Upon receiving the notification, the relay node initiates the forwarding process, eliminating the need for polling and avoiding increased latency and resource waste. The relay node only performs operations such as receiving data frames, verifying data frames, and forwarding data frames to the first node. It does not decode, modify, or perform business logic processing on the data frames. It only temporarily caches the data frames until forwarding is complete, and clears the cache after forwarding is finished, ensuring data integrity and originality.

[0167] During the verification process, after receiving the trigger notification, the relay node extracts the data frame, verifies the validity of the checksum, and, upon successful verification, does not modify the data content of the data frame. Instead, it directly transmits the data frame to the first node's GATT first uplink data transmission characteristic value via its own Bluetooth bidirectional long-term connection with the first node. Upon receiving the data frame, the first node parses the third node's MAC address and data content within the data frame, synchronizes it to the cockpit control interface, and completes the uplink data transmission.

[0168] During the uplink data transmission process, there is no broadcast flooding throughout the entire process, and the data transmission path is fixed as the third node, the corresponding relay node, and the first node, ensuring data transmission latency and data transmission success rate.

[0169] In this invention, if a data frame fails to be verified, the relay node discards the data frame and sends a retransmission command to the third node, which then retransmits the data frame.

[0170] Reference Figure 4 The downlink command transmission process includes the following steps:

[0171] S401, through a long-term two-way Bluetooth connection between the relay node and the first node, the first node sends the command to be transmitted to the relay node;

[0172] S402 uses a long-term, two-way Bluetooth connection between the third node and the relay node to send the command to be transmitted to the third node.

[0173] In some implementations, a BLE notify event-triggered forwarding mechanism is also used during downlink data transmission, instead of a polling mechanism. No parsing, modification, or storage operations are performed on the service instructions; only transparent forwarding is executed.

[0174] The command to be transmitted can be a control command. Specifically, the user issues a control command to the target third node through the cockpit control interface, mobile application, or voice assistant. The in-vehicle equipment then sends the control command to the first node. After receiving the control command, the first node parses the MAC address of the target third node, queries the topology management list for the corresponding bound relay node, frames the control command according to a preset command format to obtain a command frame, and then writes the command frame into the GATT layer second downlink command transmission feature value of the corresponding relay node through a Bluetooth bidirectional long-term connection.

[0175] Furthermore, once the second downlink command transmission characteristic value of the relay node's GATT layer is written into the command frame, a notify notification is immediately triggered. Upon receiving the notification, the relay node initiates the command forwarding process without polling. Consistent with the uplink data transmission rules, the relay node only performs the operations of receiving, verifying, and forwarding command frames, without decoding, modifying, or performing business logic processing on the command frames. After forwarding, the temporary buffer is cleared immediately to ensure command integrity and real-time performance. After detecting an update to the second downlink command transmission characteristic value, the relay node extracts the command frame, verifies the validity of the checksum, and after successful verification, parses the MAC address of the target third node. It then transmits the command frame to the corresponding target third node through its own Bluetooth bidirectional long-term connection with the target third node.

[0176] Furthermore, after receiving the command frame, the target third node parses the control command, executes the corresponding control action, and after execution, feeds back the execution result to the first node through the uplink path according to the uplink data transmission method. The first node synchronizes with the cockpit control interface to complete the downlink command transmission, ensuring the transmission latency and command execution success rate throughout the process. If the verification fails, the relay node discards the command frame and sends a retransmission request to the first node, which then reissues the command.

[0177] For example, a user issues commands through the vehicle's infotainment system control interface, such as turning on the front seat heating or adjusting the brightness of the rear ambient lights. After the first node parses the command, it transmits it to the target third node through the corresponding relay node. After the target third node executes the command, it transmits the execution result (such as seat heating temperature and ambient light brightness) back to the first node through the relay node and synchronizes it to the infotainment control interface. The entire process takes ≤55ms with no noticeable delay. In a test of 10,000 command issuances and data reporting, the communication success rate was 99.92%, with no packet loss or disconnection.

[0178] Furthermore, simulating a disconnection between the front relay node and the first node, the relay node immediately initiates a reconnection, with a reconnection interval of 500ms, repeated 5 times, and successfully reconnecting on the 3rd attempt. During the reconnection, the 3 cached third node status data were successfully retransmitted. Simulating an offline state of a rear ambient light third node, the first node immediately marks the node as offline, and the cockpit control interface displays a prompt. After the third node reconnects, it automatically initiates a network access request, completes the reconnection within 1.2s, and restores normal data interaction. Simulating an in-vehicle electromagnetic interference scenario, if the latency is too high, the number of relays can be reduced to optimize latency. In the actual test of an extreme electromagnetic interference scenario (two relay nodes), the maximum end-to-end latency was 78ms, and the communication success rate was 99.88%, meeting the requirements for mass production in vehicles.

[0179] In some alternative implementations, the link status between the first node and the relay node, and between the relay node and the third node, can be monitored in real time through a standard BLE connection heartbeat mechanism. A fixed heartbeat period is set, and the heartbeat data packet carries the node MAC address and connection status information.

[0180] If the third node does not receive a heartbeat packet from the relay node within a specified number of heartbeat cycles, it is determined that the Bluetooth link between the third node and the relay node is broken. The third node will immediately initiate a reconnection automatically, setting a fixed reconnection interval and a number of consecutive reconnections. If the reconnection is successful, normal data interaction will resume. If the consecutive reconnection fails after reaching the maximum number of attempts, the third node will automatically stop reconnecting, start the BLE scanning mode to scan for the dedicated broadcasts of other relay nodes, initiate a network access request to complete the backup topology switch, and ensure that the function is not interrupted.

[0181] If a relay node does not receive a heartbeat packet from the first node within a specified number of heartbeat cycles, it determines that the link between the relay node and the first node is broken. The relay node immediately initiates a reconnection automatically, setting a fixed reconnection interval and a number of consecutive reconnections. If the reconnection is successful, normal data forwarding is resumed, and the data of the third node cached during the reconnection is retransmitted to the first node. The cache is set to a fixed capacity, and data exceeding the capacity is automatically overwritten by the oldest data. If the consecutive reconnection fails after reaching the maximum number of attempts, the relay node suspends the forwarding of data to the third node, sends a link abnormality command to all connected third nodes, notifies the third nodes to switch to the backup relay node, and continuously scans the first node's broadcast until the reconnection is successful.

[0182] In this invention, if the first node detects that a relay node or a third node is offline (i.e., it has not received a heartbeat packet and the reconnection has failed), it immediately updates the topology management list, marks the node as offline, and displays an offline prompt on the cockpit control interface. If the offline node comes back online, it automatically initiates a network access request. After the topology reconnection is completed, the first node updates the topology management list and resumes normal data interaction.

[0183] In this invention, to address the data security requirements of in-vehicle scenarios, cascaded network encryption technology can be integrated. All data transmitted between the first node, relay node, and third node is encrypted, effectively improving communication security and further enhancing the high reliability transmission capability of the entire network system, ensuring the confidentiality and integrity of data transmission from in-vehicle IoT peripherals.

[0184] As can be seen, to address the problems of high latency, message redundancy, and poor reliability caused by broadcast flooding in existing technologies, and to achieve the core objective of high reliability and low latency of this invention, this invention employs GATT feature value reading and writing to achieve targeted forwarding of data packets, clearly defining a fixed forwarding path: the uplink data path is "from the third node to the relay node to the first node," and the downlink command path is "from the first node to the relay node to the third node." This invention does not use the broadcast flooding method found in existing technologies, effectively avoiding the generation of redundant messages. It can stably control end-to-end latency within a preset range, achieving low-latency communication, while also simplifying the development process, reducing development complexity, and adapting to the real-time control requirements of vehicle-mounted scenarios.

[0185] The following are embodiments of the apparatus of the present invention, which can be used to execute embodiments of the method of the present invention. For details not disclosed in the embodiments of the apparatus of the present invention, please refer to the embodiments of the method of the present invention.

[0186] Figure 5 This is a schematic diagram of the networking device for a cockpit Internet of Things (IoT) provided in an embodiment of the present invention. Figure 5 As shown, the networking device 50 of the cockpit IoT is applied to the cockpit IoT system, which is a Bluetooth topology network. The cockpit IoT system includes a first node, multiple second nodes, and a third node. The first node is integrated on the vehicle equipment. The second and third nodes are both Bluetooth terminal nodes in the cockpit. The device includes a first establishment module 501 and a second establishment module 502.

[0187] Among them, the first establishment module 501 is used to establish a long-term Bluetooth bidirectional connection between the first node and each of the second nodes;

[0188] The second establishment module 502 is used to determine the relay node among multiple second nodes and establish a long-term Bluetooth bidirectional connection between the relay node and the corresponding third node.

[0189] Furthermore, the first establishment module 501 is specifically used for: configuring the first interaction feature value of the first node, the first interaction feature value being used for data transmission between the first node and the second node; executing the operation of the second node to complete network access to the first node; and establishing the underlying physical connection between the first node and the second node based on the idle Bluetooth channel of the first node.

[0190] Furthermore, the first interactive feature value includes: a first uplink data transmission feature value and a first downlink command transmission feature value. The first uplink data transmission feature value is used to receive data uploaded by the second node, and the first downlink command transmission feature value is used to send control commands of the vehicle-mounted device to the second node.

[0191] Furthermore, when the first establishment module 501 performs the operation of the second node completing the network access to the first node, it is specifically used for: for each second node, the second node broadcasts a first network access request, the first network access request carrying the identity information of the second node; the first node receives the first network access request and verifies the identity information of the second node, and if the identity information of the second node is verified and the first node has an idle Bluetooth channel, the second node is allowed to access the first node.

[0192] Furthermore, the second establishment module 503 is specifically used for: configuring the second interaction feature value of the relay node, the second interaction feature value being used for data transmission between the relay node and the corresponding third node; executing the operation of the corresponding third node to complete network access to the relay node; and establishing the underlying physical connection between the third node and the relay node.

[0193] Furthermore, the second interactive feature value includes: a second uplink data transmission feature value and a second downlink command transmission feature value. The second uplink data transmission feature value is used to receive data uploaded by the third node, and the second downlink command transmission feature value is used to send control commands of the vehicle-mounted device to the third node.

[0194] Furthermore, the device also includes a mapping module (not shown in the figure), used to establish a mapping relationship between the first uplink data transmission feature value and the second uplink data transmission feature value through the first node, and to establish a mapping relationship between the first downlink command transmission feature value and the second downlink command transmission feature value.

[0195] Furthermore, when the second establishment module 502 performs the operation of the corresponding third node completing the network access to the relay node, it is specifically used for: for each third node, the third node broadcasts a second network access request, which carries the identity information of the third node; the relay node receives the second network access request and sends it to the first node for verification; if the first node verifies the identity information of the third node and the number of third nodes already connected to the relay node is less than the maximum number of main connections allowed by the relay node, the first node notifies the relay node to allow the third node to access the relay node.

[0196] Furthermore, when the second establishment module 502 determines the relay node among multiple second nodes, it is specifically used to determine the relay node among multiple second nodes when the number of second nodes connected to the first node is equal to a preset number threshold.

[0197] Furthermore, it also includes a third establishment module (not shown in the figure), which is used to determine the secondary relay node among multiple third nodes when the number of third nodes connected to the relay node is equal to the maximum number of primary connections of the relay node; and to establish a Bluetooth bidirectional long-term connection between the secondary relay node and the corresponding fourth node.

[0198] Furthermore, it also includes a rejection module (not shown in the figure): used to determine the data transmission delay between the first node and each third node; if the data transmission delay is greater than or equal to the delay threshold, it rejects the access of any new node to any node in the cockpit IoT system.

[0199] The networking device for the cockpit Internet of Things provided in this embodiment of the invention can be used to execute the method steps of the above-described method embodiment. The specific implementation and technical effects are similar, and will not be repeated here.

[0200] In some embodiments, a communication device is also provided for use in a cockpit IoT system. The cockpit IoT system is a Bluetooth topology network. The cockpit IoT system includes a first node, multiple second nodes, and a third node. The first node is integrated into an in-vehicle device. The second and third nodes are both in-cabin Bluetooth terminal nodes. The multiple second nodes include relay nodes. The device includes:

[0201] The first transmission module is used to transmit data from the third node to the relay node via a long-term, two-way Bluetooth connection between the third node and the relay node; and to forward data to the first node via a long-term, two-way Bluetooth connection between the relay node and the first node; and / or,

[0202] The second transmission module is used to send the instruction to be transmitted from the first node to the relay node through a long-term two-way Bluetooth connection between the relay node and the first node; and to send the instruction to be transmitted from the relay node to the third node through a long-term two-way Bluetooth connection between the third node and the relay node.

[0203] The communication device provided in this embodiment of the invention can be used to execute the method steps of the corresponding method embodiments described above. The specific implementation and technical effects are similar, and will not be repeated here.

[0204] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. The electronic device 60 includes at least one processor 601 and a memory 602.

[0205] Optionally, the electronic device 60 also includes a communication component 603. The processor 601, memory 602, and communication component 603 are connected via a bus 604.

[0206] In a specific implementation, at least one processor 601 executes computer execution instructions stored in memory 602, causing at least one processor 601 to perform the above-described method.

[0207] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0208] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0209] The memory may include random access memory (RAM) and non-volatile memory (NVM), such as at least one disk storage device.

[0210] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0211] This invention also provides a vehicle, including: a vehicle body and electronic equipment as provided in the above embodiments.

[0212] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0213] This invention also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0214] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as ferromagnetic random access memory (FRAM), static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic surface memory, flash memory, magnetic disk, optical disk, or compact disc read-only memory (CD-ROM), etc. The readable storage medium can be any available medium accessible to general-purpose or special-purpose computers.

[0215] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0216] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0217] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0218] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0219] If a function is implemented as 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 this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0220] Those skilled in the art will understand that the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0221] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0222] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0223] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0224] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0225] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and 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 the invention is limited only by the appended claims.

Claims

1. A networking method for a cockpit Internet of Things (IoT), characterized in that, The method is applied to a cockpit IoT system, which is a Bluetooth topology network. The cockpit IoT system includes a first node, multiple second nodes, and a third node. The first node is integrated into an in-vehicle device, and the second and third nodes are both in-cabin Bluetooth terminal nodes. The method includes: Establish a long-term, two-way Bluetooth connection between the first node and each of the second nodes; A relay node is determined among the plurality of second nodes, and a long-term Bluetooth bidirectional connection is established between the relay node and the corresponding third node.

2. The method according to claim 1, characterized in that, The establishment of a long-term, two-way Bluetooth connection between the first node and each of the second nodes includes: Configure a first interaction feature value for the first node, which is used for data transmission between the first node and the second node; The second node performs the operation to complete the network access to the first node; Based on the idle Bluetooth channel of the first node, a low-level physical connection is established between the first node and the second node.

3. The method according to claim 2, characterized in that, The first interactive feature value includes: a first uplink data transmission feature value and a first downlink command transmission feature value. The first uplink data transmission feature value is used to receive data uploaded by the second node, and the first downlink command transmission feature value is used to send control commands of the vehicle-mounted device to the second node.

4. The method according to claim 2, characterized in that, The operation of the second node completing network access to the first node includes: For each second node, the second node broadcasts a first network access request, which carries the identity information of the second node; The first node receives the first network access request and verifies the identity information of the second node. If the identity information of the second node is verified and the first node has an idle Bluetooth channel, the second node is allowed to access the first node.

5. The method according to claim 3, characterized in that, Establishing a long-term, two-way Bluetooth connection between the relay node and the corresponding third node includes: Configure a second interaction feature value for the relay node, the second interaction feature value being used for data transmission between the relay node and the corresponding third node; The corresponding third node performs the operation to complete the network access to the relay node; Establish the underlying physical connection between the third node and the relay node.

6. The method according to claim 5, characterized in that, The second interactive feature value includes: a second uplink data transmission feature value and a second downlink command transmission feature value. The second uplink data transmission feature value is used to receive data uploaded by the third node, and the second downlink command transmission feature value is used to send control commands of the vehicle-mounted device to the third node.

7. The method according to claim 6, characterized in that, The method further includes: establishing a mapping relationship between the first uplink data transmission feature value and the second uplink data transmission feature value through the first node, and establishing a mapping relationship between the first downlink command transmission feature value and the second downlink command transmission feature value.

8. The method according to any one of claims 5 to 7, characterized in that, The operation of the corresponding third node completing the network access to the relay node includes: For each third node, the third node broadcasts a second network access request, which carries the identity information of the third node; The relay node receives the second network access request and sends the second network access request to the first node for verification; If the first node successfully verifies the identity information of the third node, and the number of third nodes that the relay node has connected to is less than the maximum number of primary connections allowed by the relay node, the first node notifies the relay node to allow the third node to connect to the relay node.

9. The method according to any one of claims 1 to 7, characterized in that, The step of determining the relay node among the plurality of second nodes includes: If the number of second nodes connected to the first node is equal to a preset number threshold, a relay node is determined from the plurality of second nodes.

10. The method according to any one of claims 1 to 7, characterized in that, The cockpit IoT system also includes a fourth node, and the method further includes: When the number of third nodes connected to the relay node is equal to the maximum number of primary connections allowed by the relay node, a secondary relay node is determined from among the multiple third nodes; Establish a long-term, two-way Bluetooth connection between the secondary relay node and the corresponding fourth node.

11. The method according to any one of claims 1 to 7, characterized in that, Also includes: Determine the data transmission delay between the first node and each of the third nodes; If the data transmission delay is greater than or equal to the delay threshold, any new node is denied access to any node in the cockpit IoT system.

12. A communication method, characterized in that, The method is applied to a cockpit IoT system, which is a Bluetooth topology network. The cockpit IoT system includes a first node, multiple second nodes, and a third node. The first node is integrated into an in-vehicle device. The second and third nodes are both in-cabin Bluetooth terminal nodes. The multiple second nodes include relay nodes. The method includes: Through a long-term, two-way Bluetooth connection between the third node and the relay node, the third node sends the data to be transmitted to the relay node; through a long-term, two-way Bluetooth connection between the relay node and the first node, the relay node forwards the data to be transmitted to the first node; and / or, Through a long-term, two-way Bluetooth connection between the relay node and the first node, the first node sends the instruction to be transmitted to the relay node; through a long-term, two-way Bluetooth connection between the third node and the relay node, the relay node sends the instruction to be transmitted to the third node.

13. A networking device for a cockpit Internet of Things (IoT), characterized in that, An application is made in a cockpit IoT system, wherein the cockpit IoT system is a Bluetooth topology network, the cockpit IoT system includes a first node, multiple second nodes, and a third node, the first node is integrated into an in-vehicle device, the second nodes and the third nodes are both in-cabin Bluetooth terminal nodes, and the device includes: The first establishment module is used to establish a long-term Bluetooth bidirectional connection between the first node and each of the second nodes. The second establishment module is used to determine a relay node among the plurality of second nodes and establish a Bluetooth bidirectional long-term connection between the relay node and the corresponding third node.

14. A communication device, characterized in that, An application is made in a cockpit IoT system, wherein the cockpit IoT system is a Bluetooth topology network, the cockpit IoT system includes a first node, multiple second nodes, and a third node, the first node is integrated into an in-vehicle device, the second nodes and the third node are both in-cabin Bluetooth terminal nodes, and the multiple second nodes include relay nodes, the device comprising: A first transmission module is configured to, via a long-term, bidirectional Bluetooth connection between the third node and the relay node, transmit data to be transmitted from the third node to the relay node; and via a long-term, bidirectional Bluetooth connection between the relay node and the first node, forward the data to be transmitted to the first node; and / or, The second transmission module is used to transmit instructions to the relay node via a long-term Bluetooth bidirectional connection between the relay node and the first node; and to transmit instructions to the third node via a long-term Bluetooth bidirectional connection between the third node and the relay node.

15. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 12.

16. A vehicle, characterized in that, Includes the vehicle body and the electronic equipment as described in claim 15.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 12.

18. A computer program product, characterized in that, include: A computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 12.