Standardized arbitration methods, devices, equipment, and media for in-vehicle Bluetooth multi-device multi-protocol connections

By introducing a connection arbitration engine into the in-vehicle Bluetooth system, multi-level arbitration and unified resource allocation are implemented, solving the connection conflict and resource contention issues in concurrent scenarios with multiple devices and protocols in in-vehicle Bluetooth, thereby improving connection stability and system flexibility.

CN123124129APending Publication Date: 2026-11-17HUIZHOU DESAY SV AUTOMOTIVE
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611427107.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-15
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In the existing in-vehicle Bluetooth connection management mechanism, each Profile Service makes independent decisions, which can easily lead to connection failures, degraded quality of connected services, and chaotic connection status management in scenarios with multiple devices and multiple protocols.

Method used

By introducing a connection arbitration engine, multi-level adjudication is carried out through pre-configured arbitration rules, including protocol-level and device-type-level adjudication, which unifies the allocation of Bluetooth hardware resources and solves the problems of resource contention and chaotic state management.

Benefits of technology

It improves the stability and system flexibility of in-vehicle Bluetooth multi-device and multi-protocol concurrent connections, and realizes configurable and rule-based management of Bluetooth connections.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123124129A_ABST
    Figure CN123124129A_ABST
Patent Text Reader

Abstract

This invention discloses a rule-based arbitration method, apparatus, device, and medium for multi-device, multi-protocol Bluetooth connections in vehicles, relating to the field of vehicle Bluetooth communication technology. The method includes: receiving a connection request for a target Bluetooth protocol on a target device; obtaining pre-configured arbitration rules, including protocol-level rules and device-type-level rules; performing multi-level arbitration on the connection request according to the arbitration rules, including protocol-level arbitration and device-type-level arbitration; and, if the multi-level arbitration passes, executing a low-level connection between the target device and the target Bluetooth protocol. This invention solves the connection conflict and resource exhaustion problems caused by limited Bluetooth resources when multiple devices and multiple protocols connect concurrently in a vehicle scenario by performing multi-level rule-based arbitration on Bluetooth connection requests.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of vehicle-mounted Bluetooth communication technology, and in particular to a standardized arbitration method, apparatus, device, and medium for vehicle-mounted Bluetooth multi-device multi-protocol connection. Background Technology

[0002] In in-vehicle infotainment systems, Bluetooth plays a crucial role in connecting various peripherals such as mobile phones, Bluetooth headsets, game controllers, and keyboards. In modern automotive scenarios, the infotainment system typically needs to connect to multiple mobile phones and various Bluetooth peripherals simultaneously, with each phone involving concurrent connections using multiple protocols such as HFP (Hands-Free Protocol), A2DP (Advanced Audio Distribution Protocol), PBAP (Phonebook Access Protocol), MAP (Message Access Protocol), and HID (Human Interface Device Protocol). Meanwhile, the Bluetooth chip's hardware resources, including the number of ACL (Asynchronous Connectionless Link) connections, SCO (Synchronous Connection Link) links, and overall throughput, all have limitations.

[0003] In the existing AOSP (Android Open Source Project) native Bluetooth connection management mechanism, each Profile Service (Bluetooth Protocol Service) independently manages the connection status and connection requests of its respective protocol. For each Bluetooth device, a connection policy with two states—ALLOWED (allowed) and FORBIDDEN (prohibited)—is maintained. When a device initiates a connection request, each Profile Service queries this policy; if it is ALLOWED, the connection is accepted; if it is FORBIDDEN, the connection is rejected. There is no information exchange between services; each service independently decides whether to establish a connection based solely on the target device's policy state.

[0004] The above approach has the following problems: each Profile Service makes independent decisions and there is no information exchange between them, which makes it impossible for the system to coordinate and allocate Bluetooth hardware resources from both the protocol level and the device type level. As a result, in multi-device and multi-protocol concurrent scenarios, problems such as connection failure, degraded quality of connected services, and chaotic connection status management may occur. Summary of the Invention

[0005] This invention provides a rule-based arbitration method, apparatus, device, and medium for in-vehicle Bluetooth multi-device multi-protocol connection, so as to realize rule-based arbitration management of Bluetooth connection requests.

[0006] According to one aspect of the present invention, a rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection is provided, comprising: Receive connection requests for the target Bluetooth protocol of the target device; Obtain pre-configured arbitration rules, wherein the arbitration rules include protocol-level rules and device-type-level rules; According to the arbitration rules, a multi-level arbitration is performed on the connection request, wherein the multi-level arbitration includes a protocol-level arbitration and a device-type-level arbitration; If the multi-level arbitration is successful, a low-level connection between the target device and the target Bluetooth protocol is established.

[0007] According to another aspect of the present invention, a rule-based arbitration device for in-vehicle Bluetooth multi-device multi-protocol connection is provided, comprising: The connection request receiving module is used to receive connection requests for the target Bluetooth protocol of the target device. The arbitration rule acquisition module is used to acquire pre-configured arbitration rules, wherein the arbitration rules include protocol-level rules and device type-level rules; A multi-level arbitration execution module is used to execute multi-level arbitration on the connection request according to the arbitration rules, wherein the multi-level arbitration includes protocol-level arbitration and device-type-level arbitration; The underlying connection execution module is used to execute the underlying connection between the target device and the target Bluetooth protocol when the multi-level arbitration is passed.

[0008] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: At least one processor; and a memory communicatively connected to the at least one processor; The memory stores a computer program that can be executed by the at least one processor, which is then executed by the at least one processor to enable the at least one processor to execute the rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection according to any embodiment of the present invention.

[0009] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, the computer instructions being configured to cause a processor to execute and implement the rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection as described in any embodiment of the present invention.

[0010] The technical solution of this invention, by receiving a connection request, obtaining pre-configured arbitration rules and executing multi-level arbitration at the protocol and device type levels, and only executing the underlying connection after the arbitration is passed, solves the connection conflict and resource competition problem caused by the lack of centralized arbitration in the scenario of multiple devices and multiple protocols in vehicle Bluetooth concurrency. It realizes configurable and rule-based management of Bluetooth connection, and improves connection stability and system flexibility.

[0011] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 A flowchart illustrating a rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection provided in an embodiment of the present invention; Figure 2 A flowchart illustrating another rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection provided in an embodiment of the present invention; Figure 3 This is a diagram illustrating the architecture of a rule-based arbitration system for in-vehicle Bluetooth multi-device multi-protocol connections provided in an embodiment of the present invention. Figure 4 A flowchart illustrating another rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of the structure of a rule-based arbitration device for in-vehicle Bluetooth multi-device multi-protocol connection provided in an embodiment of the present invention; Figure 6 A schematic diagram of the structure of an electronic device for implementing the rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection according to an embodiment of the present invention. Detailed Implementation

[0014] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0015] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0016] To further understand the present invention, before introducing specific embodiments, the prior art and the technical solution of the present invention will be described as follows: In existing technologies, each Profile Service makes independent decisions and cannot perceive the current connection status of other protocols. With limited hardware resources, the lack of unified allocation easily leads to connection failures or degraded quality of already connected services. Each service manages at the device level, making it impossible to configure the maximum number of connections for a single protocol. One protocol may consume too many link resources, affecting other protocols. There is a lack of coordination between services, making it impossible to express resource dependencies between protocols. For example, if a call protocol occupies the voice link while the audio protocol continues to transmit at a high bitrate, the two will interfere with each other, resulting in degraded call quality or audio stuttering. Each service maintains the connection status of its own protocols, and handles its own connection release separately when the device disconnects. The lack of unified resource reclamation management easily leads to inconsistent states or untimely resource release.

[0017] In view of this, the present invention adds a centralized connection arbitration engine to the vehicle system, which operates independently of each Profile Service. This engine intercepts connection requests before they reach the Profile Service and performs multi-level arbitration based on pre-configured protocol-level and device-type-level rules. This provides unified allocation and management of Bluetooth hardware resources from both protocol and device-type perspectives. Consequently, it avoids resource contention and state management chaos caused by independent decision-making by each service, thus improving system stability and resource utilization in concurrent connections across multiple devices and protocols in in-vehicle scenarios.

[0018] Figure 1This is a flowchart illustrating a rule-based arbitration method for multi-device, multi-protocol Bluetooth connection in an in-vehicle system, provided by an embodiment of the present invention. This embodiment is applicable to situations in in-vehicle scenarios where centralized arbitration management is performed on multiple protocol connection requests from multiple Bluetooth devices. This method can be executed by an in-vehicle Bluetooth connection arbitration device, which can be implemented in hardware and / or software and can be configured within the vehicle's infotainment system. Figure 1 As shown, the method specifically includes the following steps: S110: Receive a connection request for the target Bluetooth protocol of the target device.

[0019] The target device refers to the Bluetooth peripheral requesting a Bluetooth connection, which can be a mobile phone, Bluetooth headset, game controller, or keyboard, etc. The target Bluetooth protocol refers to the Bluetooth Profile (Bluetooth profile / protocol subset) to be established in this connection request, such as HFP, A2DP, PBAP, MAP, or HID. The connection request can be initiated by an upper-layer application or triggered by the Bluetooth device's automatic reconnection mechanism.

[0020] In this embodiment, a connection request from an upper-layer application or system can be received based on the connection arbitration engine. This connection request carries at least the device identifier of the target device and the protocol identifier of the target Bluetooth protocol. In this embodiment, the device identifier can be used to uniquely identify a Bluetooth device, and the protocol identifier can be used to uniquely identify a Bluetooth protocol. The connection arbitration engine can then execute subsequent arbitration procedures based on the device identifier and the protocol identifier.

[0021] S120, Obtain the pre-configured arbitration rules.

[0022] Arbitration rules are a pre-configured and stored set of rules that guide the connection arbitration engine in making decisions to allow or deny each connection request. Arbitration rules consist of two levels: protocol-level rules and device-type-level rules.

[0023] In this embodiment, the connection arbitration engine can load arbitration rules from the rule configurator. The rule configurator can provide a static configuration interface and a runtime dynamic configuration interface, supporting the loading of rule tables at system startup and the dynamic updating of rules during operation.

[0024] In practical applications, different vehicle models or original equipment manufacturers (OEMs) can adjust Bluetooth connection behavior by modifying rule configuration files without modifying the code.

[0025] S130. In accordance with the arbitration rules, a multi-level award shall be executed on the connection request.

[0026] The multi-level adjudication includes two levels: protocol-level adjudication and device-type-level adjudication. Protocol-level adjudication is used to verify the connection request according to the protocol-level rules corresponding to the target Bluetooth protocol, while device-type-level adjudication is used to verify the connection request according to the device-type rules corresponding to the target device's device type.

[0027] In some possible implementations, the step of performing multi-level adjudication on the connection request according to the arbitration rules includes: performing protocol-level adjudication on the target Bluetooth protocol according to the protocol-level rules; and, if the protocol-level adjudication passes, performing device-type-level adjudication on the target device according to the device-type-level rules.

[0028] Specifically, the connection arbitration engine can first execute a protocol-level decision, and after the protocol-level decision is passed, the connection arbitration engine will further execute a device type-level decision.

[0029] In some possible implementations, before performing multi-level arbitration on the connection request according to the arbitration rules, the method further includes: if the target Bluetooth protocol is not in the list of managed protocols, skipping the multi-level arbitration and directly invoking the underlying Bluetooth protocol service to perform the actual connection of the target Bluetooth protocol.

[0030] In this embodiment, the connection arbitration engine can first determine whether the target Bluetooth protocol belongs to the managed protocol list. The managed protocol list can be pre-configured and lists the Bluetooth protocols that need to be managed by the arbitration engine. If the determination result is that the target Bluetooth protocol does not belong to the managed protocol list, then all multi-level arbitration processes are skipped, and the connection request is directly passed to the underlying Bluetooth protocol service to execute the actual connection.

[0031] S140. If the multi-level arbitration is successful, perform the underlying connection between the target device and the target Bluetooth protocol.

[0032] In this embodiment, the underlying connection refers to the operation of actually establishing a Bluetooth physical link by calling the underlying Bluetooth protocol stack services. Multi-level adjudication indicates that the connection request has passed all verifications at the protocol and device type levels.

[0033] In some possible implementations, performing the underlying connection between the target device and the target Bluetooth protocol includes: adding the target device to a list of devices waiting to be connected, and adding the target Bluetooth protocol to a set of protocols waiting to be connected corresponding to the target device; and calling the underlying Bluetooth protocol service to perform the actual connection of the target Bluetooth protocol.

[0034] In this embodiment, the connection arbitration engine can add the target device to the list of devices waiting to be connected and add the target Bluetooth protocol to the set of protocols waiting to be connected corresponding to that device. Then, it calls underlying Bluetooth protocol services, such as HeadsetClientService and A2dpSinkService in AOSP, to execute the actual connection of the target Bluetooth protocol. The connection arbitration engine obtains the connection result by listening to Bluetooth system broadcasts or callbacks and updates the state management information based on the connection result.

[0035] In some possible implementations, if the actual connection is successful, the target Bluetooth protocol is moved from the set of protocols waiting to be connected to the set of connected protocols corresponding to the target device, and the target device is moved from the list of devices waiting to be connected to the list of connected devices. If the actual connection fails, the target Bluetooth protocol is removed from the set of protocols waiting to be connected to.

[0036] Moving the protocol to the connected set upon successful connection ensures accurate recording of established connections. Removing the protocol from the waiting set upon connection failure promptly clears unnecessary waiting states, preventing the protocol from remaining in the waiting set and affecting subsequent decision-making and resource statistics.

[0037] In some possible implementations, reconnection management logic can also be executed via a connection arbitration engine. If the actual connection result for the target Bluetooth protocol fails, the process further includes: obtaining the current reconnection count for the target Bluetooth protocol; if the current reconnection count is less than the maximum reconnection count for the target Bluetooth protocol, incrementing the current reconnection count and re-invoking the underlying Bluetooth protocol service to execute the actual connection for the target Bluetooth protocol; if the current reconnection count is greater than or equal to the maximum reconnection count, removing the target Bluetooth protocol from the set of waiting connection protocols.

[0038] Specifically, the connection arbitration engine can obtain the current reconnection count for the target Bluetooth protocol. If the current reconnection count is less than the maximum reconnection count for the target Bluetooth protocol, the connection arbitration engine increments the current reconnection count and re-invokes the underlying Bluetooth protocol service to perform the actual connection. If the current reconnection count is greater than or equal to the maximum reconnection count, the connection arbitration engine removes the target Bluetooth protocol from the set of waiting connection protocols.

[0039] Since the underlying layer usually continues to call back the failure status after a Bluetooth connection fails, if the number of times is not limited, the connection arbitration engine will repeatedly trigger reconnection, wasting system resources and never succeeding. By actively removing the protocol and clearing its reconnection status after reaching the maximum number of reconnections, we can avoid the continuous occupation of vehicle processor and Bluetooth controller resources by invalid reconnections, and also prevent the protocol from remaining in the waiting connection set and causing subsequent state management abnormalities.

[0040] In some possible implementations, upon receiving a disconnected status from the target Bluetooth protocol, the connection arbitration engine can remove the target Bluetooth protocol from the set of connected protocols. If the target device's set of connected protocols is empty and the set of waiting protocols is also empty, the engine deletes the device object corresponding to the target device and releases related resources.

[0041] In another possible implementation, when performing the underlying connection, if the maximum allowed number of connections corresponding to the device type of the target device is one, that is, only one device is allowed to be online at the same time for this type, then device replacement logic is used.

[0042] Specifically, when the connection arbitration engine detects that a connected device of this device type already exists, it adds the connection of the corresponding target Bluetooth protocol among the connected devices to the set of protocols waiting to be disconnected, and adds the connected device to the list of devices waiting to be disconnected. Upon receiving a status indicating that the connection of the corresponding target Bluetooth protocol among the connected devices has been successfully disconnected, the engine removes the connected device from the list of connected devices.

[0043] Then, the connection arbitration engine calls the underlying Bluetooth protocol service to execute the actual connection between the target device and the target Bluetooth protocol. This achieves automatic replacement, eliminating the need for upper-layer applications to manually handle the disconnection logic of the old device.

[0044] The technical solution of this invention, by receiving a connection request, obtaining pre-configured arbitration rules and executing multi-level arbitration at the protocol and device type levels, and only executing the underlying connection after the arbitration is passed, solves the connection conflict and resource competition problem caused by the lack of centralized arbitration in the scenario of multiple devices and multiple protocols in vehicle Bluetooth concurrency. It realizes configurable and rule-based management of Bluetooth connection, and improves connection stability and system flexibility.

[0045] Figure 2 This is a flowchart illustrating another rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection provided by an embodiment of the present invention. This embodiment further optimizes the process of performing multi-level arbitration on connection requests according to arbitration rules in the above embodiments. Technical terms that are the same as or corresponding to those in the above embodiments will not be repeated here. Figure 2 As shown, the method specifically includes the following steps: S210: Receive a connection request for the target Bluetooth protocol of the target device.

[0046] S220, Obtain the pre-configured arbitration rules.

[0047] S230. According to the maximum number of connections in the protocol, obtain the first maximum number of connections corresponding to the target Bluetooth protocol; if the current number of connections to the target Bluetooth protocol is greater than or equal to the first maximum number of connections, reject the connection request.

[0048] The protocol-level rules include maximum connection limit rules and protocol coexistence rules. Maximum connection limit rules define the maximum number of devices allowed to connect simultaneously for each Bluetooth protocol. Protocol coexistence rules define the restrictions on the maximum number of allowed connections for other target protocols when the connection count of the baseline protocol reaches a trigger threshold.

[0049] The first maximum number of connections refers to the maximum number of devices allowed to connect simultaneously for the target Bluetooth protocol as defined in the protocol's maximum connection rule. For example, if the maximum number of connections for HEADSET_CLIENT (HFP protocol) is defined as 2 in the protocol's maximum connection rule, then when the target Bluetooth protocol is HFP, the first maximum number of connections is 2.

[0050] Specifically, the connection arbitration engine uses the target Bluetooth protocol's protocol ID as the key to query the protocol maximum connection count rule mapping table to obtain the corresponding maximum number of connections. If the protocol does not have a corresponding configuration in the rule mapping table, the default value can be used.

[0051] If the number of devices currently connected to the target Bluetooth protocol is greater than or equal to the first maximum number of connections, the connection arbitration engine rejects the connection request. In other words, if the number of devices currently connected to the target Bluetooth protocol has already reached the maximum allowed by that protocol, new connection requests will be directly rejected, and subsequent arbitration steps will not be executed.

[0052] If the current number of connected devices for the target Bluetooth protocol is less than the first maximum number of connected devices, continue to perform subsequent protocol coexistence rule checks.

[0053] S240. If the current number of connections for the target Bluetooth protocol is less than the first maximum number of connections, determine whether to trigger a connection limit for other target protocols based on the simulated number of connections after the target Bluetooth protocol is successfully connected, according to the protocol coexistence rules; if the connection limit is triggered, verify the connection request based on the current number of connections for other target protocols.

[0054] Here, "simulated connection count" refers to the number of connections for the target Bluetooth protocol that would be established if the current connection request were successful (i.e., the current number of connections plus one). "Other target protocols" refers to other Bluetooth protocols whose connection counts need to be limited, as specified in the protocol coexistence rule limitation mapping table.

[0055] Specifically, the connection arbitration engine can iterate through all protocol coexistence rules to find rules that use the target Bluetooth protocol as the base protocol and whose trigger threshold is less than or equal to the number of simulated connections. If such a rule exists, it means that after a successful connection to the target protocol, a limit on the number of connections to other target protocols specified in that rule will be triggered.

[0056] When the connection limit is triggered, the connection arbitration engine obtains the current number of connections for the target other protocol and compares it with the maximum allowed number of connections specified for that target other protocol in the protocol coexistence rules. If the current number of connections for the target other protocol is greater than or equal to the maximum allowed number of connections, the connection request is rejected; if it is less than the maximum allowed number of connections, subsequent device type-level arbitration is carried out through protocol-level arbitration.

[0057] In some possible implementations, protocol coexistence rules can express complex multi-protocol constraints. For example, the rule `{profileId:HEADSET_CLIENT,triggerCount:2,limitMap:{HID_HOST:2}}` indicates that when the number of HFP protocol connections reaches two, the maximum allowed number of HID_HOST (HID host protocol) connections is limited to two. That is, if two HFP devices are already connected, and two HID_HOST devices are already connected, new HFP connection requests will be rejected to avoid excessive Bluetooth resource consumption.

[0058] S250. Based on the device type quantity limit rule, obtain the device quantity limit corresponding to the device type of the target device; determine the sum of the number of connected devices and the number of devices waiting to be connected under the device type; if the sum of the number of devices is greater than or equal to the device quantity limit, reject the connection request.

[0059] The device type-level rules include a maximum number of device type rules. These rules define the maximum number of devices allowed to connect simultaneously for each device type. Device types include PHONE, AUDIO / VIDEO, and PERIPHERAL, among others. The maximum number of devices allowed to connect to the system simultaneously for that device type.

[0060] In this embodiment, the connection arbitration engine can query the device type quantity limit rule based on the target device's device type to obtain the corresponding device quantity limit. For example, if the device type quantity limit rule defines a limit of 3 for the PHONE type, then when the target device is a mobile phone, the device quantity limit is 3.

[0061] The connection arbitration engine determines the sum of the number of connected devices and the number of devices in a waiting connection state for this device type. The number of connected devices refers to the number of devices that have successfully established at least one protocol connection for this type. The number of devices in a waiting connection state refers to the number of this type of devices currently waiting to establish a connection.

[0062] If the total number of devices is greater than or equal to the maximum number of devices, the connection arbitration engine will reject the connection request. This means that if the total number of devices already connected and waiting to connect for this device type has reached or exceeded the maximum limit for that type, new connection requests will be rejected.

[0063] S260. If the target device is not in the list of connected devices, obtain the set of cross-type restriction conditions corresponding to the device type of the target device according to the device type coexistence rule; traverse the set of cross-type restriction conditions, and reject the connection request if the connection request meets any cross-type restriction condition.

[0064] The device type level rules also include device type coexistence rules. The connected device list is one of the core state tables maintained by the connection state manager, recording the devices that have successfully established connections. The cross-type constraint set refers to all cross-device type constraints defined for the target device's device type within the device type coexistence rules. Device type coexistence rules are used to define connection quota constraints between different device types.

[0065] Specifically, the connection arbitration engine first determines whether the target device already exists in the connected device list. If the target device is already in the connected device list, it means that the device has already established a connection with the vehicle's infotainment system using certain protocols. This request is only to add a new protocol connection for the device. In this case, the check of device type coexistence rules can be skipped to avoid unnecessary restrictions on subsequent protocol additions to already connected devices. If the target device is not in the connected device list, the cross-type restriction condition set corresponding to the device type is obtained according to the device type coexistence rules.

[0066] The connection arbitration engine iterates through the set of cross-type constraints and rejects a connection request if it satisfies any of these constraints. Cross-type constraints can express complex cross-device type limitations, such as "when there are two PHONE type devices, there can be at most one PERIPHERAL type device." If two PHONE type devices are already connected, and the target device is a PERIPHERAL type device and one PERIPHERAL type device is already connected, then the new PERIPHERAL device connection request will be rejected.

[0067] S270. If the multi-level arbitration is successful, perform the underlying connection between the target device and the target Bluetooth protocol.

[0068] The technical solution of this invention employs a four-layer progressive arbitration structure—including maximum connection count checks, protocol coexistence rule checks, device type quantity limit checks, and device type coexistence rule checks—to perform refined rule-based arbitration of Bluetooth connection requests. Protocol-level arbitration controls the maximum number of connections and inter-protocol coexistence constraints at the protocol level, while device-type-level arbitration controls the capacity limit of device types and cross-type quota constraints. These two layers of arbitration work together progressively, effectively resolving resource contention and protocol conflicts in concurrent multi-device, multi-protocol scenarios for in-vehicle Bluetooth.

[0069] Figure 3 This is a diagram illustrating the architecture of a rule-based arbitration system for multi-device, multi-protocol Bluetooth connectivity in vehicles, provided in an embodiment of the present invention. This embodiment further explains the overall architecture, state management mechanism, and rule configuration method of the vehicle Bluetooth connection arbitration system. Technical terms that are the same as or corresponding to those in the above embodiments will not be repeated here. Figure 3 As shown, the entire system is divided into five layers in terms of architecture: configuration layer, arbitration layer, state management layer, service layer, and hardware layer.

[0070] The configuration layer contains a rule configurator, providing both static and runtime dynamic configuration interfaces, supporting rule table loading at system startup and dynamic updates during operation. The arbitration layer contains the connection arbitration engine, the core of the system, responsible for receiving connection and disconnection requests and executing multi-level arbitration. The state management layer contains the connection state manager, responsible for maintaining connection state information for all devices and protocols. The service layer contains various native Bluetooth ProfileServices from AOSP; after arbitration approval, these services execute the actual Bluetooth connection. The hardware layer contains the Bluetooth hardware controller and Bluetooth protocol stack, responsible for the actual Bluetooth physical link communication.

[0071] The connection state manager maintains three core state tables. The first is the connected devices table, which records devices that have successfully established at least one protocol connection and their set of connected protocols. The second is the waiting devices table, which records devices that have passed arbitration and are waiting for the underlying connection to complete, and their set of waiting connection protocols. The third is the waiting disconnect devices table, which records devices waiting to disconnect and their set of waiting disconnect protocols.

[0072] The Connection State Manager creates a Device Connection Object for each connected or pending Bluetooth device. This object manages the complete lifecycle information of each Bluetooth protocol under the device, specifically including five core members: a set of protocols waiting to connect, used to record protocols on the device that are waiting to initiate a connection; a set of connected protocols, used to record protocols on the device that have successfully established a connection; a set of protocols waiting to disconnect, used to record protocols on the device that are waiting to disconnect; a protocol reconnection count dictionary, used to record the current number of reconnection attempts for each protocol on the device; and a protocol maximum reconnection count dictionary, used to record the maximum number of reconnections allowed for each protocol on the device.

[0073] When the connection arbitration engine receives a protocol connection success status broadcast by the Bluetooth system, it moves the protocol from the device object's waiting-to-connect protocols set to the connected protocols set, and moves the device from the waiting-to-connect devices table to the connected devices table. When it receives a protocol disconnect status, it removes the protocol from either the connected protocols set or the waiting-to-disconnect protocols set. When both the device object's connected protocols set and waiting-to-connect protocols set are empty, the engine deletes the device object, releasing memory and Bluetooth underlying resources.

[0074] Regarding reconnection management, when a connection for a certain protocol fails, the connection arbitration engine queries the current and maximum reconnection counts for that protocol in the device object. If the current reconnection count is less than the maximum, the current reconnection count is incremented and the connection is re-initiated. If the current reconnection count has reached the maximum, the reconnection is abandoned, the protocol is removed from the set of waiting connections, and its reconnection count is cleared. This reconnection management mechanism avoids the consumption of system resources by infinite reconnections.

[0075] Regarding rule configuration, the rule configurator supports both static and dynamic configuration modes. Static configuration mode loads the rule table from a configuration file at system startup; the configuration file can use JSON, XML, or other structured data formats. Dynamic configuration mode allows the system to receive rule update commands through a configuration interface during runtime, dynamically modifying the rule table content. Modified rules take effect immediately without requiring a system restart. This flexible configuration approach allows different vehicle models or OEMs to adjust their connection strategies based on their Bluetooth hardware capabilities and business needs without modifying the underlying code.

[0076] Figure 4 A flowchart illustrating another rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection provided by an embodiment of the present invention. Figure 4 As shown, the method includes: Step 1: Receive connection request - The upper layer application initiates a connect(device, profileId) request.

[0077] Step 2: Determine if under arbitration management—Check if the target protocol is in the managed protocol list (isConnectManagerProfile). If not, pass the information directly to the underlying layer. Here, isConnectManagerProfile is the function that checks whether the target protocol belongs to the managed protocol list.

[0078] Step 3: Protocol-level adjudication isRejectConnect(profileId): ① Get the maximum number of connections (maxCount) for profileId; ②If maxCount ≥ 0 and the current number of connected devices ≥ maxCount, then reject the connection; ③ Obtain the coexistence rules for profileId under the condition of current connection count + 1; ④ If coexistence rules exist, check if the current connection count of other protocols exceeds the limit; ⑤ If any limit is exceeded, the connection will be rejected.

[0079] Among them, isRejectConnect is the rejection judgment function of the protocol-level adjudication.

[0080] Step 4: Device Type Level Decision isRejectConnectTargetDevice(device,profileId): ① Obtain the device type (deviceType) corresponding to the protocol; ② Obtain the list of coexistence rules for this device type; ③ If the target device is already in the connected list of devices of the same type, skip it (reuse the existing connection); ④ Iterate through all the restriction rules and check whether any combination of restriction conditions is satisfied; ⑤ If any of the restrictions are met, the connection is rejected.

[0081] Among them, isRejectConnectTargetDevice is the rejection judgment function for device type-level adjudication.

[0082] Step 5: Target device type capacity check isAllowConnectTargetDevice(device,deviceType): ① Obtain the maximum number of connections allowed for each device type; ② Count the number of connected devices and the number of devices waiting to connect for this device type; ③ If the limit has been reached, then reject.

[0083] Among them, isAllowConnectTargetDevice is the function for determining device type and capacity.

[0084] Step 6: Execute the connection — After arbitration, the underlying Profile Service is called to execute the actual connection, and the state management table is updated asynchronously when the connection state changes.

[0085] The technical solution of this invention decouples rule configuration, connection arbitration, state management, service execution, and hardware communication through a five-layer architecture design. It achieves fine-grained management of all connection states through three core state tables and five lifecycle members of the device connection object. It realizes the flexible and adjustable rule system through two modes: static configuration and dynamic configuration. It solves the problems of unclear system architecture, chaotic state management, and difficulty in rule adjustment in the scenario of multiple devices and multiple protocols in vehicle Bluetooth. It realizes the modularity, scalability, and configurability of the connection arbitration system.

[0086] Figure 5 This is a schematic diagram of a standardized arbitration device for in-vehicle Bluetooth multi-device multi-protocol connection provided in an embodiment of the present invention. Figure 5 As shown, the device includes: The connection request receiving module 510 is used to receive a connection request for a target Bluetooth protocol for a target device. The arbitration rule acquisition module 520 is used to acquire pre-configured arbitration rules, wherein the arbitration rules include protocol-level rules and device type-level rules; The multi-level arbitration execution module 530 is used to execute multi-level arbitration on the connection request according to the arbitration rules, wherein the multi-level arbitration includes protocol-level arbitration and device type-level arbitration; The underlying connection execution module 540 is used to execute the underlying connection between the target device and the target Bluetooth protocol when the multi-level arbitration is passed.

[0087] In some possible implementations, the multi-level adjudication execution module 530 includes: The protocol-level adjudication submodule is used to perform protocol-level adjudication on the target Bluetooth protocol according to the protocol-level rules. The device type-level adjudication submodule is used to perform device type-level adjudication on the target device according to the device type-level rules if the protocol-level adjudication is passed.

[0088] In some possible implementations, the protocol-level rules include maximum connection limit rules and protocol coexistence rules, and the protocol-level adjudication submodule includes: The maximum connection number acquisition unit is used to acquire the first maximum connection number corresponding to the target Bluetooth protocol according to the maximum connection number rule of the protocol; The first rejection unit is configured to reject the connection request if the current number of connected devices of the target Bluetooth protocol is greater than or equal to the first maximum number of connections. The coexistence rule verification unit is used to determine, according to the protocol coexistence rule, whether to trigger a limit on the number of connections to other target protocols based on the simulated number of connections after the target Bluetooth protocol is successfully connected, when the current number of connections to the target Bluetooth protocol is less than the first maximum number of connections. The protocol quantity verification unit is used to verify the connection request based on the current connection quantity of other protocols of the target when the connection quantity limit is triggered.

[0089] In some possible implementations, the device type-level rules include a maximum number of device types rule, and the device type-level adjudication submodule includes: The quantity limit acquisition unit is used to obtain the maximum number of devices corresponding to the device type of the target device according to the device type quantity limit rule; A quantity statistics unit is used to determine the sum of the number of connected devices and the number of devices waiting to be connected under the device type; The second rejection unit is used to reject the connection request if the sum of the number of devices is greater than or equal to the upper limit of the number of devices.

[0090] In some possible implementations, the device type-level rules also include device type coexistence rules, and the device type-level adjudication submodule further includes: The constraint condition acquisition unit is used to acquire a set of cross-type constraint conditions corresponding to the device type of the target device according to the device type coexistence rule when the target device is not in the list of connected devices. The conditional traversal verification unit is used to traverse the cross-type restriction condition set and reject the connection request if the connection request meets any of the cross-type restriction conditions.

[0091] In some possible implementations, the underlying connection execution module 540 includes: The status list update submodule is used to add the target device to the list of devices waiting to be connected, and to add the target Bluetooth protocol to the set of protocols waiting to be connected corresponding to the target device; The underlying call submodule is used to call the underlying Bluetooth protocol service to execute the actual connection of the target Bluetooth protocol.

[0092] In some possible implementations, the underlying connection execution module 540 further includes: The connection success processing submodule is used to move the target Bluetooth protocol from the waiting connection protocol set to the connected protocol set corresponding to the target device when the actual connection is successful, and to move the target device from the waiting connection device list to the connected device list. A connection failure handling submodule is used to remove the target Bluetooth protocol from the set of waiting connection protocols in the event of an actual connection failure.

[0093] In some possible implementations, the underlying connection execution module 540 further includes: A disconnection state processing submodule is used to remove the target Bluetooth protocol from the set of connected protocols when a disconnection state of the target Bluetooth protocol is received. The device object deletion submodule is used to delete the device object corresponding to the target device when the connected protocol set of the target device is empty and the waiting connection protocol set is empty.

[0094] In some possible implementations, the underlying calling submodule includes: The old device to be disconnected unit is used to add the connection of the target Bluetooth protocol in the connected device to the waiting disconnect protocol set and add the connected device to the waiting disconnect device list when the maximum allowed number of connections corresponding to the device type of the target device is one and there are already connected devices under the device type; The old device removal unit is used to remove the connected device from the connected device list after receiving a status indicating that the connection to the target Bluetooth protocol has been successfully disconnected from the connected device. The new device connection unit is used to call the underlying Bluetooth protocol service to execute the actual connection between the target device and the target Bluetooth protocol.

[0095] In some possible implementations, the underlying connection execution module 540 further includes: The reconnection count acquisition submodule is used to acquire the current reconnection count corresponding to the target Bluetooth protocol when the actual connection result of the target Bluetooth protocol fails. The reconnection execution submodule is used to increment the current reconnection count and re-invoke the underlying Bluetooth protocol service to execute the actual connection of the target Bluetooth protocol when the current reconnection count is less than the maximum reconnection count corresponding to the target Bluetooth protocol. The reconnection termination submodule is used to remove the target Bluetooth protocol from the set of waiting connection protocols when the current reconnection count is greater than or equal to the maximum reconnection count.

[0096] In some possible implementations, the device also includes: The managed protocol determination module 550 is used to determine whether the target Bluetooth protocol belongs to the managed protocol list before the multi-level decision execution module 530 executes the multi-level decision. The direct connection processing module is used to skip the multi-level arbitration and directly call the underlying Bluetooth protocol service to execute the actual connection of the target Bluetooth protocol when the target Bluetooth protocol is not in the managed protocol list.

[0097] The rule-based arbitration device for in-vehicle Bluetooth multi-device multi-protocol connection provided in this embodiment of the invention can execute the rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0098] Figure 6 This is a schematic diagram of the structure of an electronic device for implementing the standardized arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection according to embodiments of the present invention. The electronic device is intended to represent various forms of digital computers, such as laptops, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0099] like Figure 6As shown, the electronic device 60 includes at least one processor 61 and a memory, such as a read-only memory (ROM) 62 and a random access memory (RAM) 63, communicatively connected to the at least one processor 61. The memory stores computer programs executable by the at least one processor. The processor 61 can perform various appropriate actions and processes based on the computer program stored in the ROM 62 or loaded from storage unit 68 into the RAM 63. The RAM 63 can also store various programs and data required for the operation of the electronic device 60. The processor 61, ROM 62, and RAM 63 are interconnected via a bus 64. An input / output (I / O) interface 65 is also connected to the bus 64.

[0100] Multiple components in electronic device 60 are connected to I / O interface 65, including: input unit 66, such as keyboard, mouse, etc.; output unit 67, such as various types of monitors, speakers, etc.; storage unit 68, such as disk, optical disk, etc.; and communication unit 69, such as network card, modem, wireless transceiver, etc. Communication unit 69 allows electronic device 60 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0101] Processor 61 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 61 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 61 performs the various methods and processes described above, such as the rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connectivity.

[0102] In some embodiments, the rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol (IVMP) connectivity can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 68. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 60 via ROM 62 and / or communication unit 69. When the computer program is loaded into RAM 63 and executed by processor 61, one or more steps of the rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connectivity described above can be performed. Alternatively, in other embodiments, processor 61 can be configured to perform the rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connectivity by any other suitable means (e.g., by means of firmware).

[0103] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific integrated circuits (ASICs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0104] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0105] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0106] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0107] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0108] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and Virtual Private Server (VPS) services, such as high management difficulty and weak business scalability.

[0109] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0110] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A rule-based arbitration method for multi-device, multi-protocol connection of in-vehicle Bluetooth, characterized in that, include: Receive connection requests for the target Bluetooth protocol of the target device; Obtain pre-configured arbitration rules, wherein the arbitration rules include protocol-level rules and device-type-level rules; According to the arbitration rules, a multi-level arbitration is performed on the connection request, wherein the multi-level arbitration includes a protocol-level arbitration and a device-type-level arbitration; If the multi-level arbitration is successful, a low-level connection between the target device and the target Bluetooth protocol is established.

2. The method according to claim 1, characterized in that, The execution of a multi-level arbitration ruling on the connection request in accordance with the arbitration rules includes: According to the aforementioned protocol-level rules, a protocol-level decision is made on the target Bluetooth protocol; If the protocol-level decision passes, a device-type-level decision is made on the target device according to the device-type-level rules.

3. The method according to claim 2, characterized in that, The protocol-level rules include maximum connection limit rules and protocol coexistence rules. The protocol-level decision-making process for the target Bluetooth protocol based on these rules includes: According to the maximum number of connections rule of the protocol, obtain the first maximum number of connections corresponding to the target Bluetooth protocol; If the current number of connected devices for the target Bluetooth protocol is greater than or equal to the first maximum number of connections, the connection request is rejected. If the current number of connections for the target Bluetooth protocol is less than the first maximum number of connections, the protocol coexistence rule determines whether to trigger a limit on the number of connections for other target protocols based on the simulated number of connections after the target Bluetooth protocol is successfully connected. If the connection limit is triggered, the connection request is verified based on the current connection count of the target's other protocols.

4. The method according to claim 2, characterized in that, The device type-level rules include a maximum number of device types rule. The step of making a device type-level decision on the target device based on the device type-level rules includes: According to the upper limit rule for the number of devices of the device type, obtain the upper limit for the number of devices corresponding to the device type of the target device; Determine the sum of the number of connected devices and the number of devices waiting to be connected under the specified device type; If the sum of the number of devices is greater than or equal to the maximum number of devices, the connection request is rejected.

5. The method according to claim 4, characterized in that, The device type-level rules also include device type coexistence rules, and the step of making a device type-level decision on the target device based on the device type-level rules further includes: If the target device is not in the list of connected devices, obtain the set of cross-type restriction conditions corresponding to the device type of the target device according to the device type coexistence rules; Iterate through the set of cross-type restrictions, and if the connection request satisfies any of the cross-type restrictions, reject the connection request.

6. The method according to claim 1, characterized in that, The execution of the underlying connection between the target device and the target Bluetooth protocol includes: Add the target device to the list of devices waiting to be connected, and add the target Bluetooth protocol to the set of protocols waiting to be connected corresponding to the target device; The underlying Bluetooth protocol service is invoked to execute the actual connection of the target Bluetooth protocol.

7. The method according to claim 6, characterized in that, Also includes: If the actual connection is successful, the target Bluetooth protocol is moved from the set of protocols waiting to be connected to the set of connected protocols corresponding to the target device, and the target device is moved from the list of devices waiting to be connected to the list of connected devices. In the event of a failed actual connection, the target Bluetooth protocol is removed from the set of protocols awaiting connection.

8. The method according to claim 7, characterized in that, Also includes: If the target Bluetooth protocol is received as disconnected, the target Bluetooth protocol will be removed from the set of connected protocols. If the set of connected protocols for the target device is empty and the set of protocols waiting to be connected is empty, delete the device object corresponding to the target device.

9. The method according to claim 6, characterized in that, When the maximum allowed number of connections corresponding to the device type of the target device is one, the step of invoking the underlying Bluetooth protocol service to execute the actual connection of the target Bluetooth protocol includes: If a connected device already exists under the device type, add the connection of the connected device corresponding to the target Bluetooth protocol to the waiting disconnect protocol set, and add the connected device to the waiting disconnect device list; Upon receiving a status indicating that the connection to the target Bluetooth protocol has been successfully disconnected from the connected device, the connected device is removed from the list of connected devices. The underlying Bluetooth protocol service is invoked to execute the actual connection between the target device and the target Bluetooth protocol.

10. The method according to claim 6, characterized in that, If the actual connection result of the target Bluetooth protocol fails, the method further includes: Obtain the current reconnection count corresponding to the target Bluetooth protocol; If the current reconnection count is less than the maximum reconnection count corresponding to the target Bluetooth protocol, the current reconnection count is incremented, and the underlying Bluetooth protocol service is invoked again to execute the actual connection of the target Bluetooth protocol. If the current number of reconnections is greater than or equal to the maximum number of reconnections, the target Bluetooth protocol will be removed from the set of waiting connection protocols.

11. The method according to claim 1, characterized in that, Prior to executing a multi-level arbitration decision on the connection request in accordance with the arbitration rules, the method further includes: If the target Bluetooth protocol is not in the list of managed protocols, the multi-level arbitration is skipped, and the underlying Bluetooth protocol service is directly invoked to execute the actual connection of the target Bluetooth protocol.

12. A standardized arbitration device for in-vehicle Bluetooth multi-device multi-protocol connection, characterized in that, include: The connection request receiving module is used to receive connection requests for the target Bluetooth protocol of the target device. The arbitration rule acquisition module is used to acquire pre-configured arbitration rules, wherein the arbitration rules include protocol-level rules and device type-level rules; A multi-level arbitration execution module is used to execute multi-level arbitration on the connection request according to the arbitration rules, wherein the multi-level arbitration includes protocol-level arbitration and device-type-level arbitration; The underlying connection execution module is used to execute the underlying connection between the target device and the target Bluetooth protocol when the multi-level arbitration is passed.

13. An electronic device, characterized in that, The electronic device includes: At least one processor; and a memory communicatively connected to the at least one processor; The memory stores a computer program that can be executed by the at least one processor, which is then executed by the at least one processor to enable the at least one processor to perform the rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection as described in any one of claims 1-11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the rule-based arbitration method for in-vehicle Bluetooth multi-device multi-protocol connection as described in any one of claims 1-11.