Multi-bluetooth device panel management method and system, storage medium and terminal device

Abstract

The application discloses a multi-Bluetooth device panel management method and system, a storage medium and a terminal device. The method comprises the following steps: in response to a first operation of a user, obtaining a device identifier, requesting and receiving corresponding panel configuration data from a server; based on the device identifier and the panel configuration data, constructing a panel configuration object and storing the panel configuration object in a panel configuration mapping table in a local storage unit; based on layout configuration parameters and a controlled component configuration list in the panel configuration object, combining screen parameters of a terminal device to generate a control panel interface corresponding to a target Bluetooth device; establishing a Bluetooth communication connection with the target Bluetooth device; in response to a selection operation of a user on any paired Bluetooth device, obtaining a corresponding panel configuration object and regenerating a corresponding control panel interface. The application significantly improves the system expansibility through a dynamically configured and driven panel management mechanism, takes into account local caching and on-demand updating, optimizes the user experience, and reduces the maintenance cost.

Description

Technical Field

[0001] This application relates to the field of panel management technology, and in particular to a method and system for managing multiple Bluetooth device panels, a storage medium, and a terminal device. Background Technology

[0002] In smart home, industrial control and commercial display scenarios, users often manage multiple heterogeneous Bluetooth devices, such as smart door locks, curtains, sockets, industrial controllers or advertising screens, through mobile terminals (such as mobile phones or tablets).

[0003] However, existing management solutions based on traditional apps have significant limitations: First, they have poor scalability, requiring modifications to the application code and the release of a new version for each new device type or function, resulting in long development cycles and difficulty in quickly responding to market demands; second, they offer a poor user experience, requiring users to download multiple applications or manually select configuration templates, making the process cumbersome and prone to errors; third, they have high maintenance costs, as the control logic and interface elements for various devices are hard-coded into the application, leading to code redundancy, and device function upgrades or UI adjustments rely on frequent application updates; fourth, configuration management lacks dynamic adaptability, failing to simultaneously support local caching and on-demand updates, severely restricting the flexibility of multi-device collaborative management.

[0004] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main purpose of this application is to provide a method for managing multiple Bluetooth device panels, which aims to solve the problems of poor scalability, poor user experience, high maintenance costs, and lack of dynamic adaptability in configuration management of existing multiple Bluetooth device panel management solutions.

[0006] To achieve the above objectives, the multi-Bluetooth device panel management method proposed in this application includes: In response to the user's first operation on the target Bluetooth device, the device identifier of the target Bluetooth device is obtained; Based on the device identifier, request the corresponding panel configuration data from the server. The panel configuration data includes layout configuration parameters and a list of controlled component configurations. The system receives panel configuration data corresponding to the device identifier sent by the server, constructs a panel configuration object based on the device identifier and the corresponding panel configuration data, and stores it in a panel configuration mapping table in the local storage unit; the panel configuration mapping table is used to index the corresponding panel configuration object according to the device identifier. Based on the layout configuration parameters and the controlled component configuration list in the panel configuration object, and combined with the screen parameters of the terminal device, the control panel interface corresponding to the target Bluetooth device is generated. Based on the device identifier, a Bluetooth communication connection is established with the target Bluetooth device; In response to the user's selection of any paired Bluetooth device, the device identifier of the corresponding Bluetooth device is obtained, the panel configuration mapping table is queried based on the device identifier to obtain the corresponding panel configuration object, and the corresponding control panel interface is regenerated in combination with the screen parameters of the terminal device.

[0007] In one embodiment, the panel configuration mapping table is implemented using a hash table structure, wherein the device identifier is used as the key and the panel configuration object is used as the value.

[0008] In one embodiment, generating the control panel interface corresponding to the target Bluetooth device based on the layout configuration parameters and the controlled component configuration list in the panel configuration object, combined with the screen parameters of the terminal device, includes: Based on the layout configuration parameters in the panel configuration object and the screen parameters, layout constraint parameters are generated; Based on the controlled component configuration list and the layout constraint parameters, a control panel interface corresponding to the target Bluetooth device is generated.

[0009] In one embodiment, the layout configuration parameters include the target number of columns, and the screen parameters of the terminal device include the screen width, width ratio coefficient, and scaling factor; the layout constraint parameters include the display size and position coordinates of each controlled component. The step of generating layout constraint parameters based on the layout configuration parameters in the panel configuration object and the screen parameters includes: The width of the display area is determined based on the screen width and the width ratio coefficient. The display size of each controlled component is calculated based on the width of the display area, the number of target columns, and the scaling factor. When the number of target columns is greater than 1, the horizontal distance between adjacent controlled components is calculated based on the width of the display area, the number of target columns, and the display size of the controlled components. Calculate the margins of the control panel interface based on the screen width and the width of the display area; Based on the display size of the controlled component, the horizontal distance, and the margin, the position coordinates of each controlled component in the control panel interface are determined.

[0010] In one embodiment, the controlled component configuration list includes the control type, function instructions, and display attributes of the controlled component; The step of generating the control panel interface corresponding to the target Bluetooth device based on the controlled component configuration list and the layout constraint parameters includes: Iterate through each controlled component in the controlled component configuration list, and for each controlled component, determine whether the predefined UI component factory has registered UI component creation logic for the corresponding control type; If already registered, the UI component creation logic corresponding to the control type of the UI component factory is invoked, and the UI component corresponding to the control type is instantiated based on the functional instructions and display attributes of the controlled component. If not registered, the corresponding new UI component creation logic is generated according to the control type of the controlled component. The new UI component creation logic is registered to the UI component factory, and the UI component creation logic of the corresponding control type in the UI component factory is called. Based on the functional instructions and display attributes of the controlled component, the UI component corresponding to the control type is instantiated. Based on the layout constraint parameters, the instantiated UI components are arranged to generate and render the control panel interface.

[0011] In one embodiment, the multi-Bluetooth device panel management method further includes: When the application restarts, all stored panel configuration objects are loaded in batches from the local storage unit.

[0012] This application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the multi-Bluetooth device panel management method described above.

[0013] This application also proposes a terminal device, the terminal device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the multi-Bluetooth device panel management method as described above.

[0014] This application also proposes a multi-Bluetooth device panel management system, which includes multiple Bluetooth devices, a server, and a terminal device as described above; wherein, when the multiple Bluetooth devices are connected to the terminal device via Bluetooth, they are used to obtain control commands from the terminal device and operate according to the control commands; the server is communicatively connected to the terminal device and is used to return corresponding panel configuration data to the terminal device when it receives request information from the terminal device.

[0015] In one embodiment, the server is further configured to update panel configuration data of multiple Bluetooth devices, and upon receiving a request from the terminal device, return the updated panel configuration data to the terminal device.

[0016] This application proposes a method for managing multiple Bluetooth device panels, comprising: responding to a user's first operation on a target Bluetooth device (such as scanning a QR code on the target Bluetooth device), obtaining the device identifier of the target Bluetooth device; based on the device identifier, requesting corresponding panel configuration data from a server, the panel configuration data including layout configuration parameters and a list of controlled component configurations; receiving the panel configuration data corresponding to the device identifier sent by the server, constructing a panel configuration object according to the device identifier and the corresponding panel configuration data, and storing it in a panel configuration mapping table in a local storage unit; the panel configuration mapping table is used to index the corresponding panel configuration object according to the device identifier; based on the layout configuration parameters and the list of controlled component configurations in the panel configuration object, combined with the screen parameters of the terminal device, generating a control panel interface corresponding to the target Bluetooth device; establishing a Bluetooth communication connection with the target Bluetooth device based on the device identifier; responding to a user's selection operation on any paired Bluetooth device, obtaining the device identifier of the corresponding Bluetooth device, querying the panel configuration mapping table based on the device identifier to obtain the corresponding panel configuration object, and regenerating the corresponding control panel interface in combination with the screen parameters of the terminal device. Compared with existing technologies, the terminal application does not need to pre-install any interface code for any specific Bluetooth device, and only needs to integrate a general configuration parsing and rendering engine to achieve multi-panel management. When a new Bluetooth device comes online, the user can obtain its device identifier through a simple first operation (such as scanning the device's QR code). The terminal then requests the corresponding panel configuration data from the server and dynamically generates a dedicated control panel interface. The entire process requires no application updates or re-releases, supporting an unlimited number of new devices, offering strong scalability and low maintenance costs. Simultaneously, after the terminal device obtains the panel configuration for the first time, it stores it in a local panel configuration mapping table in the form of "device identifier - panel configuration object," achieving efficient indexing of all paired Bluetooth devices. When switching devices subsequently, the configuration can be directly read from the local mapping table, and the control panel interface can be quickly reconstructed based on the current terminal's screen parameters. This supports offline use and ensures the latest data is available upon configuration updates, balancing performance and flexibility. Furthermore, users can instantly load the target Bluetooth device's dedicated control panel interface on the terminal through a first operation (such as scanning a QR code), eliminating the need to download multiple apps or manually select templates. When switching the control panel interface of a paired device, the configuration is read from the local mapping table and the interface is re-rendered based on the current screen parameters, resulting in a seamless and smooth multi-device switching experience and a superior user experience. Thus, this application significantly improves system scalability and multi-device adaptability through a dynamically configured panel management mechanism, optimizes user experience, and greatly reduces maintenance costs. Attached Figure Description

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

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart illustrating an embodiment of the multi-Bluetooth device panel management method of this application. Figure 2 This is a flowchart illustrating Embodiment 2 of the multi-Bluetooth device panel management method of this application. Figure 3 This is a flowchart illustrating an embodiment of the multi-Bluetooth device panel management method of this application. Figure 4 This is a flowchart illustrating another embodiment of the multi-Bluetooth device panel management method of this application. Figure 5 A schematic diagram of the device structure provided for one embodiment of the terminal device of this application; Figure 6 This is a schematic diagram of a structure provided for an embodiment of the multi-Bluetooth device panel management system of this application.

[0020] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Specific Implementation It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0022] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments.

[0023] With the development of the Internet of Things (IoT) and smart hardware devices, Bluetooth Low Energy (BLE) devices are widely used in smart homes, industrial control, medical devices, and other fields. Currently, the following control solutions are available on the market: Option 1: Traditional physical remote control Each Bluetooth device comes with a dedicated physical remote control, which users send control signals by pressing a button. However, this approach suffers from issues such as easy loss, susceptibility to wear and tear, limited functionality, and difficulty in managing multiple devices.

[0024] The drawbacks of this solution include its susceptibility to loss, wear and tear, limited lifespan, fixed functionality, and inability to adapt to equipment upgrades or personalized needs.

[0025] Option 2: Fixed Interface App Solution During mobile application development, the layout, number of buttons, and functionality of the control panel interface are fixed, including: Static fixed interface: The application pre-compiles a fixed control panel interface for each device type. Different devices require different application versions or interface modules.

[0026] Preset template selection: The application has a variety of built-in preset control panel interface templates, and users need to manually select the matching template.

[0027] Local configuration database: The application has a built-in configuration database that looks up configuration files based on the device identifier. The configuration information must be collected before the application is released.

[0028] This solution has significant limitations: First, it has poor scalability, requiring modification of the application code and release of a new version for each new device type or function, resulting in a long development cycle and difficulty in quickly responding to market demands. Second, it offers a poor user experience, requiring users to download multiple applications or manually select configuration templates, making the process cumbersome and prone to errors. Third, it incurs high maintenance costs, as the control logic and interface elements for various devices are hard-coded into the application, leading to code redundancy, and device function upgrades or UI adjustments rely on frequent application updates. Fourth, configuration management lacks dynamic adaptability, failing to simultaneously support local caching and on-demand updates, severely restricting the flexibility of multi-device collaborative management.

[0029] Option 3: Scan the QR code to open the fixed page Some applications support scanning device QR codes, but the QR codes usually only contain the device ID or a fixed URL. The application then redirects to a pre-defined control page, and the interface layout and functions are still pre-compiled.

[0030] This application provides a method for managing multiple Bluetooth device panels.

[0031] It should be noted that the executing entity in this embodiment can be a terminal device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or other electronic devices capable of performing the above functions. The following description uses a terminal device employing the multi-Bluetooth device panel management method as an example to illustrate this embodiment and the subsequent embodiments.

[0032] Please see Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the multi-Bluetooth device panel management method of this application. In this embodiment, the multi-Bluetooth device panel management method includes steps S10 to S60: Step S10: In response to the user's first operation on the target Bluetooth device, obtain the device identifier of the target Bluetooth device.

[0033] It should be noted that the first operation can include triggering methods such as scanning a QR code or touching an NFC tag. Taking scanning a QR code as an example, the user can use the terminal device's application software to scan the QR code on the target Bluetooth device to obtain the device identifier. If the QR code contains a device identifier, the application will use it to construct a configuration request URL, in the format: `configuration server address / ?key=device ID`. If the QR code directly contains a configuration URL, the application will use that URL directly.

[0034] It should be noted that the target Bluetooth device may include one or more device identifiers. When multiple device identifiers are included, they are used to implement different panel controls, and there is no limitation here.

[0035] Step S20: Based on the device identifier, request the corresponding panel configuration data from the server. The panel configuration data includes layout configuration parameters and a list of controlled component configurations.

[0036] It should be noted that the app sends an HTTP GET request to the configuration server, and the timeout can be set to 20 seconds. The server returns panel configuration data in JSON format.

[0037] Step S30: Receive panel configuration data corresponding to the device identifier sent by the server; construct a panel configuration object based on the device identifier and the corresponding panel configuration data; and store it in the panel configuration mapping table in the local storage unit; the panel configuration mapping table is used to index the corresponding panel configuration object based on the device identifier.

[0038] It should be noted that a unique panel identifier (i.e., panel ID) can be preset based on the device identifier, and then a panel configuration object can be constructed based on the panel ID and the parsed panel configuration data. In this way, by introducing the panel ID as an intermediate layer, the device function and display form can be decoupled. When multiple functional modules of the same Bluetooth device have corresponding device identifiers, different functional modules can use different control panel interfaces, improving control flexibility. Among them, the correspondence between the device identifier and the panel ID can be established through a hash table structure. In this way, a two-way mapping relationship between the device physical identifier (Bluetooth MAC address) and the logical panel ID can be established. The hash table data structure supports fast lookup with O(1) time complexity.

[0039] In one embodiment, step S30 includes steps S31 to S33: Step S31: Receive and parse the panel configuration data.

[0040] In this step, the app receives and parses the panel configuration data returned by the server, extracting various information required for interface construction, including layout configuration parameters and a controlled component configuration list. It's important to note that layout configuration parameters define the overall panel layout rules, such as the number of grid columns, orientation (horizontal / portrait screen adaptation), spacing, and alignment. The controlled component configuration list is a collection of configurations for all interactive controls in the panel (such as buttons, sliders, color pickers, etc.). Each component includes its type, bound Bluetooth device functional attributes (such as "on / off," "temperature value"), and display label. For example, layout configuration parameters may include the target number of columns, logo configuration (logo name, display method, size), and one or more custom text information. The controlled component configuration list includes the control type, function commands, and display attributes of the controlled components.

[0041] The controlled components can include one or more of the following control types: buttons, sliders, and color pickers. The app can use regular expressions or a JSON parser to extract the configuration of each button, parsing out display attributes such as button index, color (hexadecimal to Color object), icon name, button name, and border style, as well as extracting function commands (hexadecimal string to byte array), and handling special characters (such as converting "@@" to a newline character). The app can use regular expressions or a JSON parser to extract the configuration of each slider, parsing out display attributes such as minimum value, maximum value, step value, unit, icon path, and color, as well as extracting function command templates (used to generate actual commands based on the current value). The app can use regular expressions or a JSON parser to extract the configuration of the color picker, parsing out display attributes such as function flags, default color, and favorite color list, as well as extracting function command templates.

[0042] It's worth noting that the panel configuration data is defined using structured JSON (JavaScript Object Notation, a lightweight data exchange format), offering excellent readability, versatility, and extensibility. In this format, various controls (such as buttons, sliders, and color pickers) are described using standardized fields to define their type, function, display attributes, and interactive behaviors. When new controls (such as knobs, voice triggers, and chart components) need to be supported, simply add the corresponding control type identifier and related attribute fields to the configuration specification, and extend the corresponding parsing logic and UI component creator on the application side to achieve dynamic support for the new controls without modifying the overall architecture.

[0043] Step S32: Construct a panel configuration object based on the panel ID and the parsed panel configuration data.

[0044] In this step, the app constructs a PanelConfig object (i.e., the panel configuration object) based on the parsed panel configuration data. This includes: panel ID (e.g., a device identifier or QR code content can be used as the ID), layout configuration object (LayoutConfig), device name, and button configuration list (List). <buttonconfig>), Slider Configuration List (List) <sliderconfig>(Optional) Color Picker Configuration (ColorPickerConfig). Thus, this step encapsulates the panel configuration for each device through a PanelConfig object, employing an object-oriented design pattern to achieve logical isolation and independent management of the configuration.

[0045] Step S33: Store the panel configuration object into the panel configuration mapping table in the local storage unit.

[0046] In this step, the app persistently stores the PanelConfig object in a panel configuration mapping table in the local storage unit, such as using SharedPreferences or a local database. The storage format is: panel ID as the key, JSON serialized data of the PanelConfig object as the value, and the currently active panel ID is also saved. In this way, memory index optimization can be achieved. By maintaining a global panel configuration mapping table (Map<Panel ID, PanelConfig>), all configurations are cached in memory, avoiding disk I / O overhead.

[0047] Step S40: Based on the layout configuration parameters and controlled component configuration list in the panel configuration object, and combined with the screen parameters of the terminal device, generate the control panel interface corresponding to the target Bluetooth device.

[0048] It should be noted that the screen parameters of the terminal device include screen width, width ratio, and scaling factor. Screen width refers to the available width of the terminal device in the horizontal direction under the current screen orientation (landscape or portrait); width ratio is the ratio of the content area width to the screen width; and scaling factor is the degree to which the content is enlarged or reduced on the screen. Layout configuration parameters define the overall arrangement rules of the panel (such as the number of rows or columns). The controlled component configuration list contains the type of each interactive control, its bound device function attributes, and its relative size information. In this step, by combining the relative layout strategy issued by the server with the local screen characteristics of the terminal, a consistent and operable control panel interface is achieved through adaptive rendering on terminal devices of different sizes and resolutions, thereby improving cross-device compatibility and user experience. For example, a button matrix can be dynamically created using the GridView component. Each button displays a corresponding icon, name, color, and border style based on the configuration, supporting visual effects such as rainbow gradient borders. Slider controls can be dynamically created at specified locations, supporting features such as circular progress displays, left and right icons, and real-time numerical displays; the number and attributes of the sliders are determined by configuration data. A color picker can be dynamically created, supporting features such as palette selection and quick switching between favorite colors. The device logo and custom text information can be dynamically displayed based on configuration, and so on. In this way, this step can dynamically generate the control panel interface corresponding to the target Bluetooth device.

[0049] In this embodiment, the control panel interface is built during application runtime and does not rely on pre-compiled templates. The number, type, and layout of controls can be flexibly adjusted through configuration data, supporting large-scale layouts (such as 137 buttons).

[0050] Step S50: Establish a Bluetooth communication connection with the target Bluetooth device based on the device identifier.

[0051] It should be noted that the terminal device app can communicate with the device and send control commands via the BLE protocol. For example, when controlling via a button, the user clicks the button, and the app writes a feature based on the function byte array in the button's configuration and sends it to the device via BLE. When controlling via a slider, the user drags the slider, and the app generates a function byte array based on the slider's current value and configuration, using a time-difference transmission strategy (sent every 100ms during sliding and immediately upon stopping), and sends it to the device via BLE. When controlling via a color picker, the user selects or adjusts a color, and the app generates a function byte array based on the color's RGB values ​​and configuration, using a time-difference transmission strategy, and sends it to the device via BLE.

[0052] It's important to note that when a user connects a Bluetooth device, the app establishes an association between the Bluetooth device and the control panel interface. When switching back to a paired Bluetooth device for panel control, the app looks up the associated panel ID based on the device identifier and automatically switches to the corresponding control panel interface, eliminating the need for rescanning. Furthermore, the app supports simultaneous connections to multiple Bluetooth devices, with each device corresponding to a separate control panel interface.

[0053] In step S60, in response to the user's selection operation of any paired Bluetooth device, the device identifier of the corresponding Bluetooth device is obtained, the panel configuration mapping table is queried based on the device identifier to obtain the corresponding panel configuration object, and the corresponding control panel interface is regenerated in combination with the screen parameters of the terminal device.

[0054] It should be noted that the app supports quick switching between multiple panels. Users can select the corresponding Bluetooth device from the device list. The app looks up the panel ID associated with that device, retrieves the corresponding PanelConfig object from the panel configuration mapping table, and regenerates the control panel interface using the PanelConfig object and the terminal device's screen parameters. In this case, switching panels does not require reconnecting the Bluetooth device. Thus, this embodiment allows switching between different panels and sending control commands to multiple Bluetooth devices.

[0055] This embodiment primarily provides a method for dynamically generating a Bluetooth device control panel interface based on configuration data. The control panel interface is dynamically constructed at runtime based on configuration data provided by the server, rather than using a pre-compiled interface template.

[0056] Compared with existing technologies, this embodiment has the technical advantages of strong scalability, high development efficiency, good user experience, low maintenance cost, intelligent unified management of multiple Bluetooth devices, flexible personalization and customization, and strong dynamic adaptability, specifically including: Highly scalable: New Bluetooth devices can be launched simply by configuring data on the server, and users can scan the configuration to obtain the identifier to use them without updating the application version. This achieves the effect of "one APP application, unlimited Bluetooth devices" for managing multiple Bluetooth devices, reducing the development cycle from weeks to hours.

[0057] High development efficiency: Bluetooth device manufacturers do not need to develop a dedicated APP for each product. They only need to set the device identifier and development configuration data, reducing development costs by 90% and shortening the development cycle by 90%.

[0058] Excellent user experience: Users don't need to download multiple apps or manually select templates; they can simply scan and use, making the operation simple and intuitive. One app manages all devices, with seamless interface switching.

[0059] Low maintenance costs: The configuration and code of the control panel interface are separated. Upgrading Bluetooth device functions or adjusting the interface only requires updating the configuration data. There is no need to release application updates or require manual updates by users, reducing maintenance costs by 80%.

[0060] Intelligent unified management of multiple devices: Through multi-panel management and the interface switching mechanism for any paired Bluetooth device, intelligent unified management of heterogeneous Bluetooth devices is achieved.

[0061] Flexible personalization: It can provide exclusive control panel interfaces for different customers or product lines, enhance brand recognition, support A / B testing (i.e., the original version and the modified version), and optimize interface design.

[0062] Strong dynamic adaptability: It can be compatible with local caching, generate the control panel interface based on the local PanelConfig object, and update the configuration data of the control panel interface after the user scans the code, realizing on-demand updates.

[0063] In summary, this embodiment solves the problems of poor scalability, poor user experience, high maintenance costs, and lack of dynamic adaptability in configuration management associated with fixed-interface APP or page solutions.

[0064] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 Step S40 includes steps S41 to S42: Step S41: Generate layout constraint parameters based on the layout configuration parameters and screen parameters in the panel configuration object.

[0065] Step S42: Based on the controlled component configuration list and layout constraint parameters, generate the control panel interface corresponding to the target Bluetooth device.

[0066] In one implementation, please refer to Figure 3 The layout configuration parameters include the target number of columns; the screen parameters of the terminal device include the screen width, width ratio factor, and scaling factor; the layout constraint parameters include the display size and position coordinates of each controlled component; step S41 includes steps S411~S415: Step S411: Determine the width of the display area based on the screen width and the width ratio coefficient; Step S412: Calculate the display size of each controlled component based on the width of the display area, the number of target columns, and the scaling factor; Step S413: If the number of target columns is greater than 1, calculate the horizontal distance between adjacent controlled components based on the width of the display area, the number of target columns, and the display size of the controlled components. Step S414: Calculate the margins of the control panel interface based on the screen width and the width of the display area; Step S415: Determine the position coordinates of each controlled component in the control panel interface based on the display size, horizontal distance, and margin of the controlled component.

[0067] It should be noted that if N is 1, there is no need to calculate the horizontal distance between adjacent controlled components; only the display size and margin of the controlled components need to be calculated.

[0068] It should be noted that controlled components of the same type can be set in one row (if the number exceeds the maximum value of each row, a new line will be created). The row height can be preset according to the type of controlled component, and controlled components of the same type can be set to have the same display size to simplify calculations.

[0069] In this embodiment, the display size, spacing, and margins of each controlled component can be dynamically calculated based on the configured target number of columns and screen width. The calculation formula includes: Available width = screen width × width ratio coefficient; Display size = Available width / N × Scaling factor; Spacing = (Available width - N × Control size) / (N - 1); Margin = (Screen width - Available width) / 2; The app dynamically adjusts the width ratio and scaling factor based on the screen orientation (landscape / portrait) and screen size to ensure proper display on different devices.

[0070] Taking a button as an example of a controlled component, the app dynamically calculates the interface layout parameters based on the target number of columns in the layout configuration. For an N-column layout, the available width of the display area is calculated as: screen width × width ratio (e.g., 0.84); button diameter = available width / N × scaling factor (e.g., 0.9); spacing = (available width - N × button diameter) / (N - 1) (e.g., N is 2, 3, or 4); margin = (screen width - available width) / 2. Thus, this implementation method achieves adaptive display of the control panel interface through parameterized, formula-driven layout design, and is easy to maintain and expand.

[0071] In yet another implementation, please refer to Figure 4 The controlled component configuration list includes the control type, function instructions, and display attributes of the controlled components; step S42 includes steps S421 to S424: Step S421: Iterate through each controlled component in the controlled component configuration list. For each controlled component, determine whether the predefined UI component factory has registered UI component creation logic for the corresponding control type. Step S422: If already registered, call the UI component creation logic of the corresponding control type in the UI component factory, and instantiate the UI component corresponding to the control type based on the function instructions and display attributes of the controlled component. Step S423: If not registered, generate the corresponding new UI component creation logic according to the control type of the controlled component, register the new UI component creation logic to the UI component factory, and call the UI component creation logic of the corresponding control type in the UI component factory. Based on the function instructions and display attributes of the controlled component, instantiate the UI component corresponding to the control type. Step S424: Arrange the instantiated UI components according to the layout constraint parameters, and generate and render the control panel interface.

[0072] It should be noted that UI components are visual control objects that are actually rendered on the interface, possessing event binding, state update, and rendering capabilities. The registration and creation logic stores a method for constructing a control type (such as how to generate a button, slider, or color picker from the configuration) in the mapping table of the UI component factory for subsequent reuse.

[0073] In this implementation, UI components are dynamically created based on panel configuration data during program execution, rather than at compile time, thereby dynamically generating the control panel interface. Specifically, a component configuration item is retrieved from the controlled component configuration list, which includes at least the control type (e.g., "button", "slider", "colorPicker"), function instructions (e.g., controlling device on / off, adjusting brightness, setting color values, etc.), and display attributes (e.g., title, icon, initial value, size, visibility, etc.). Based on the control type of the component, the corresponding registration creation logic (i.e., the construction function or class of that type of control) is searched in the mapping table of the UI Component Factory. For example, if the control type is "slider", the factory returns a registered createSlider(config) function or SliderComponent class. The found creation logic is called, passing the function instructions and display attributes of the current component as parameters. Internally, this logic will: initialize the DOM elements or native view of the control; bind events (e.g., send a Bluetooth command when the swipe ends); set the initial state (e.g., the slider position corresponds to the current device brightness value); and configure styles and interactive behaviors (based on display attributes). The creation logic returns a fully capable UI component object. This object can be added to the interface layout for rendering; it can respond to user interactions (such as clicks and drags); it can update its display based on device status (e.g., buttons turn gray when the device is off); and it can send control commands to the target Bluetooth device through bound logic. Finally, this UI component instance is inserted into the final generated control panel interface according to the layout configuration parameters. Thus, this embodiment uses the factory pattern to dynamically instantiate UI components, reducing memory allocation overhead and improving switching performance. Moreover, because UI components can be reused, code redundancy is reduced, code quality is improved, and new control types only require extending the parsing logic without modifying the core code.

[0074] Based on the first embodiment of this application, in the third embodiment of this application, the content that is the same as or similar to that in the first embodiment can be referred to the above description, and will not be repeated hereafter. On this basis, the panel configuration mapping table is implemented using a hash table structure, where the device identifier is used as the key and the panel configuration object is used as the value.

[0075] It should be noted that if a unique panel identifier (i.e., panel ID) is preset based on the device identifier, then the panel configuration mapping table is constructed using the panel ID as the key and the panel configuration object as the value.

[0076] In this embodiment, when the user selects a device, the APP directly obtains the PanelConfig object through hash lookup, and then dynamically reconstructs the control panel interface without having to re-establish the Bluetooth connection. The switching time can be controlled within 100ms.

[0077] In one embodiment, the multi-Bluetooth device panel management method further includes step S70: When the application restarts, all stored panel configuration objects are loaded in batches from the local storage unit.

[0078] In this implementation, the PanelConfig object is persisted locally using a key-value pair storage mechanism. When the application restarts, a batch I / O strategy is used to load all PanelConfig objects at once, which can reduce the number of disk accesses and eliminates the need for users to rescan the QR code or reconfigure.

[0079] To significantly shorten the time spent on configuration loading and parsing during APP startup, in another implementation, the panel configuration parsing process adopts a multi-threaded or coroutine parallel processing mechanism.

[0080] In this implementation, during the startup phase, the panel configuration data to be parsed (such as JSON format data) is divided into tasks at the panel ID granularity, generating multiple independent parsing subtasks. These subtasks are submitted to a thread pool (multi-threaded model) or scheduled by an event loop (coroutine model) to concurrently perform operations such as syntax parsing, field validation, and object construction.

[0081] In another implementation, to prevent the mapping between device identifier and panel ID from being confused due to data corruption, version inconsistency, or write interruption during abnormal restarts, configuration hot updates, or recovery from persistent storage, a data integrity verification mechanism is introduced.

[0082] In this implementation, data integrity verification is performed during data loading, including: verifying whether the panel IDs referenced by all Bluetooth devices exist in the loaded panel configuration set; optionally checking for unreferenced isolated panels or dangling references pointing to invalid panels; and detecting whether the configuration data has been silently corrupted by comparing checksums or version numbers. If the verification fails, the system reverts to the secure default configuration, records alarm logs, or automatically continues operation using the default panel and displays alarm information.

[0083] This application provides a terminal device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the multi-Bluetooth device panel management method in Embodiment 1 above.

[0084] The following is for reference. Figure 5 The diagram illustrates a structural schematic of a terminal device suitable for implementing embodiments of this application. The terminal device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0085] like Figure 5 As shown, the terminal device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the terminal device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows terminal devices to communicate wirelessly or wiredly with other devices to exchange data. Although terminal devices with various systems are shown in the figures, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0086] The terminal device provided in this application, employing the multi-Bluetooth device panel management method described in the above embodiments, can solve the problems of poor scalability, unsatisfactory user experience, high maintenance costs, and lack of dynamic adaptability in configuration management in existing multi-Bluetooth device panel management schemes. Compared with the prior art, the beneficial effects of the terminal device provided in this application are the same as those of the multi-Bluetooth device panel management method provided in the above embodiments, and other technical features in this terminal device are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0087] This application provides a multi-Bluetooth device panel management system. Please refer to [link / reference]. Figure 6 The multi-Bluetooth device panel management system includes multiple Bluetooth devices, a server, and the terminal device as described above. The multiple Bluetooth devices are used to obtain control commands from the terminal device when connected via Bluetooth, and to operate according to the control commands. The server is connected to the terminal device and is used to return the corresponding panel configuration data to the terminal device when it receives a request from the terminal device.

[0088] The multi-Bluetooth device panel management system provided in this application, employing the multi-Bluetooth device panel management method described in the above embodiments, can solve the problems of poor scalability, unsatisfactory user experience, high maintenance costs, and lack of dynamic adaptability in configuration management in existing multi-Bluetooth device panel management solutions. Compared with the prior art, the beneficial effects of the multi-Bluetooth device panel management system provided in this application are the same as those of the multi-Bluetooth device panel management method provided in the above embodiments, and other technical features in the terminal device are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0089] In one embodiment, the server is also used to update the panel configuration data of multiple Bluetooth devices, and when it receives a request from a terminal device, it returns the updated panel configuration data to the terminal device.

[0090] This embodiment boasts strong scalability, high development efficiency, low maintenance costs, and strong compatibility. Specifically, when a new Bluetooth device is added, only server configuration data is required. Users can scan the configuration to obtain the identifier and use the device without updating the application version. This achieves the effect of controlling multiple Bluetooth devices with a single app, reducing the development cycle from weeks to hours. Moreover, device manufacturers do not need to develop a dedicated app for each product; they only need to generate configuration data and the required Bluetooth device identifier, reducing development costs and shortening the development cycle by 90%. Furthermore, configuration and code are separated, so device function upgrades and control panel interface adjustments only require updating the configuration data, without releasing application updates, reducing maintenance costs by 80%. In addition, to improve development efficiency and system consistency, the panel configuration data issued by the server can adopt a unified format (such as JSON), while the client control panel's rendering engine is based on a cross-platform UI framework (such as Flutter). This framework allows a single codebase to be built and run on multiple operating system platforms such as Android, iOS, Windows, macOS, and Linux.

[0091] In smart home applications, users manage multiple heterogeneous Bluetooth devices (such as living room lights, bedroom lights, smart curtains, and smart sockets) through a single app. The system achieves efficient and unified control of terminal devices based on a multi-Bluetooth device panel management method. Specifically, when a user performs an operation on a target Bluetooth device for the first time (such as scanning a living room light's QR code), the app obtains its device identifier and requests the corresponding panel configuration data from the server. The server returns JSON structured data containing layout configuration parameters (such as a 5-column grid) and a list of controlled component configurations (such as switches and brightness adjustment buttons). Based on this, the app constructs a panel configuration object, stores it in a local panel configuration mapping table using the device identifier as an index, and establishes an association between the device identifier and the panel ID. Subsequently, it dynamically generates an adapted control panel interface based on the terminal screen parameters and establishes a Bluetooth communication connection. Similarly, panel configuration objects for Bluetooth devices such as bedroom lights can be constructed and saved, and Bluetooth communication connections can be established. When a user subsequently selects any paired device (e.g., switching to the bedroom light), the App quickly queries the mapping table using the device identifier to obtain the corresponding panel configuration object. The interface is then directly reconstructed in memory, eliminating the need to re-download or re-parse the configuration. The switching time is less than 100ms. All configurations are persistently stored, allowing for batch recovery and data consistency verification after application restart, ensuring zero configuration loss. This embodiment abandons the traditional fragmented "one device, one application" model, achieving a unified intelligent management experience of "one App, multiple devices, dedicated interface, second-level switching, and automatic recovery," significantly improving development efficiency, system performance, and user satisfaction.

[0092] In the scenario of unified management of multiple devices in an industrial control system, operators manage industrial Bluetooth devices with different functions, such as production control devices, environmental monitoring devices, and visualization devices, through the same App. Among them, the production control devices include 10 function buttons (start, stop, reset, mode selection, parameter adjustment, etc.) for production process control. The environmental monitoring devices include 5 control buttons + 2 sliders (real-time temperature adjustment, precise speed control) for dynamic adjustment of environmental parameters. The visualization devices include 8 control buttons + 1 color selector (LED indicator color control) for status visualization display. When the operator scans the QR code of any device (such as the production control device), the App obtains its device identifier and requests the corresponding panel configuration data from the server; the server returns a structured configuration containing layout parameters (such as 5 columns of grid) and a list of controlled components (such as 10 buttons); the App constructs a panel configuration object based on this, stores it in the local panel configuration mapping table with the device identifier as the key, and establishes an association between the device MAC address and the panel ID. When switching devices later, the system quickly loads the corresponding configuration from memory through O(1) lookup and dynamically generates an adapted control panel interface. All panels are configured with persistent storage, allowing for batch restoration after the app restarts. This embodiment abandons the traditional "one device, one dedicated app" model, significantly reducing development costs by 90%, supporting hot updates (upgrading device functionality without requiring a new version release), and unifying operational logic, greatly reducing operator training costs and the risk of misoperation.

[0093] In centralized management scenarios for commercial display devices, administrators use a single app to uniformly manage multiple Bluetooth display terminals (such as advertising screens, information display screens, and conference control screens) in shopping malls, showrooms, or conference rooms. The advertising screen includes 15 function buttons (play, pause, previous track, next track, volume up, volume down, mode switching, timer settings, etc.) for multimedia advertising playback control. The information display screen includes 8 control buttons (channel switching, content update, mode selection, brightness preset, etc.) for information display management. The conference control screen includes 5 buttons + 1 slider (power on / off, signal source selection, real-time brightness adjustment, etc.) for conference environment control. Administrators scan the configuration identifiers on each display screen, and the app sequentially retrieves the differentiated panel configurations (e.g., 15-button multimedia control, 8-button information management, 5-button + slider conference adjustment), completing local storage and device-panel association. In the unified management interface, administrators can intuitively view the status of all devices. Clicking on any device triggers a quick panel switch: the system dynamically generates a dedicated control panel interface based on pre-stored configurations, automatically adapting to control types and layouts, ensuring a smooth switching process without reconnection. Thanks to memory caching and efficient indexing mechanisms, interface reconstruction takes less time than the human perception threshold. Thus, this embodiment achieves "one-application full-management" for commercial display devices, avoiding the cumbersome operation of switching between multiple applications and significantly improving management efficiency. Simultaneously, new device access or function upgrades only require updating server configuration, eliminating the need to develop new app versions, greatly shortening response cycles, reducing maintenance costs, and ensuring the professionalism and service quality of equipment management in commercial venues.

[0094] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0095] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the multi-Bluetooth device panel management method described in the above embodiments.

[0096] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having 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 fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0097] The aforementioned computer-readable storage medium may be included in the terminal device; or it may exist independently and not assembled into the terminal device.

[0098] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by a terminal device, the terminal device: in response to a user's first operation on a target Bluetooth device, obtains the device identifier of the target Bluetooth device; based on the device identifier, requests corresponding panel configuration data from a server, the panel configuration data including layout configuration parameters and a list of controlled component configurations; receives the panel configuration data corresponding to the device identifier sent by the server, constructs a panel configuration object based on the device identifier and the corresponding panel configuration data, and stores it in a panel configuration mapping table in a local storage unit; the panel configuration mapping table is used to index the corresponding panel configuration object based on the device identifier; based on the layout configuration parameters and the list of controlled component configurations in the panel configuration object, and combined with the screen parameters of the terminal device, generates a control panel interface corresponding to the target Bluetooth device; establishes a Bluetooth communication connection with the target Bluetooth device based on the device identifier; in response to a user's selection operation on any paired Bluetooth device, obtains the device identifier of the corresponding Bluetooth device, queries the panel configuration mapping table based on the device identifier to obtain the corresponding panel configuration object, and regenerates the corresponding control panel interface in combination with the screen parameters of the terminal device.

[0099] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0100] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0101] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0102] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described multi-Bluetooth device panel management method. This solves the problems of poor scalability, unpleasant user experience, high maintenance costs, and lack of dynamic adaptability in configuration management in existing multi-Bluetooth device panel management schemes. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the multi-Bluetooth device panel management method provided in the above embodiments, and will not be repeated here.

[0103] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.< / sliderconfig> < / buttonconfig>

Claims

1. A method for managing multiple Bluetooth device panels, characterized in that, include: In response to the user's first operation on the target Bluetooth device, the device identifier of the target Bluetooth device is obtained; Based on the device identifier, request the corresponding panel configuration data from the server. The panel configuration data includes layout configuration parameters and a list of controlled component configurations. The system receives panel configuration data corresponding to the device identifier sent by the server, constructs a panel configuration object based on the device identifier and the corresponding panel configuration data, and stores it in a panel configuration mapping table in the local storage unit; the panel configuration mapping table is used to index the corresponding panel configuration object according to the device identifier. Based on the layout configuration parameters and the controlled component configuration list in the panel configuration object, and combined with the screen parameters of the terminal device, the control panel interface corresponding to the target Bluetooth device is generated. Based on the device identifier, a Bluetooth communication connection is established with the target Bluetooth device; In response to the user's selection of any paired Bluetooth device, the device identifier of the corresponding Bluetooth device is obtained, the panel configuration mapping table is queried based on the device identifier to obtain the corresponding panel configuration object, and the corresponding control panel interface is regenerated in combination with the screen parameters of the terminal device.

2. The multi-Bluetooth device panel management method as described in claim 1, characterized in that, The panel configuration mapping table is implemented using a hash table structure, where the device identifier is used as the key and the panel configuration object is used as the value.

3. The multi-Bluetooth device panel management method as described in claim 1, characterized in that, The process of generating the control panel interface corresponding to the target Bluetooth device based on the layout configuration parameters and the controlled component configuration list in the panel configuration object, combined with the screen parameters of the terminal device, includes: Based on the layout configuration parameters in the panel configuration object and the screen parameters, layout constraint parameters are generated; Based on the controlled component configuration list and the layout constraint parameters, a control panel interface corresponding to the target Bluetooth device is generated.

4. The multi-Bluetooth device panel management method as described in claim 3, characterized in that, The layout configuration parameters include the target number of columns; the screen parameters of the terminal device include the screen width, width ratio coefficient, and scaling coefficient; the layout constraint parameters include the display size and position coordinates of each controlled component. The step of generating layout constraint parameters based on the layout configuration parameters in the panel configuration object and the screen parameters includes: The width of the display area is determined based on the screen width and the width ratio coefficient. The display size of each controlled component is calculated based on the width of the display area, the number of target columns, and the scaling factor. When the number of target columns is greater than 1, the horizontal distance between adjacent controlled components is calculated based on the width of the display area, the number of target columns, and the display size of the controlled components. Calculate the margins of the control panel interface based on the screen width and the width of the display area; Based on the display size of the controlled component, the horizontal distance, and the margin, the position coordinates of each controlled component in the control panel interface are determined.

5. The multi-Bluetooth device panel management method as described in claim 3, characterized in that, The controlled component configuration list includes the control type, function instructions, and display attributes of the controlled components; The step of generating the control panel interface corresponding to the target Bluetooth device based on the controlled component configuration list and the layout constraint parameters includes: Iterate through each controlled component in the controlled component configuration list, and for each controlled component, determine whether the predefined UI component factory has registered UI component creation logic for the corresponding control type; If already registered, the UI component creation logic corresponding to the control type of the UI component factory is invoked, and the UI component corresponding to the control type is instantiated based on the functional instructions and display attributes of the controlled component. If not registered, the corresponding new UI component creation logic is generated according to the control type of the controlled component. The new UI component creation logic is registered to the UI component factory, and the UI component creation logic of the corresponding control type in the UI component factory is called. Based on the functional instructions and display attributes of the controlled component, the UI component corresponding to the control type is instantiated. Based on the layout constraint parameters, the instantiated UI components are arranged to generate and render the control panel interface.

6. The multi-Bluetooth device panel management method as described in claim 1, characterized in that, Also includes: When the application restarts, all stored panel configuration objects are loaded in batches from the local storage unit.

7. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the multi-Bluetooth device panel management method as described in any one of claims 1 to 6.

8. A terminal device, characterized in that, The terminal device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the multi-Bluetooth device panel management method as described in any one of claims 1 to 6.

9. A multi-Bluetooth device panel management system, characterized in that, It includes multiple Bluetooth devices, a server, and a terminal device as described in claim 8; wherein, when the multiple Bluetooth devices are connected to the terminal device via Bluetooth, they are used to obtain control commands from the terminal device and operate according to the control commands; the server is communicatively connected to the terminal device and is used to return corresponding panel configuration data to the terminal device when it receives request information from the terminal device.

10. The multi-Bluetooth device panel management system as described in claim 9, characterized in that, The server is also used to update the panel configuration data of multiple Bluetooth devices, and when it receives a request from the terminal device, it returns the updated panel configuration data to the terminal device.

Images