Dynamic mapping access method and system for sub-equipment in bridging gateway and bridging gateway

Abstract

The invention discloses a dynamic mapping access method and system for sub-equipment in a bridging gateway and the bridging gateway, and belongs to the technical field of smart home and Internet of Things. The method comprises the following steps that: a bridging gateway acquires functional capability information of accessed non-Matter sub-equipment; performing structured analysis on the functional capability information to generate a sub-device capability description model; matching the sub-device capability description model with a preset Matter device model mapping rule, and determining a mapping scheme comprising a device type, an endpoint number and a cluster combination mode; dynamically generating a Matter endpoint based on the mapping scheme, and binding the Matter endpoint with the sub-equipment; endpoint information is issued to a control platform through a Matter protocol; and when the state or capability change of the sub-equipment is detected, updating or recycling operation is performed on the endpoint. According to the invention, the non-transformation and adaptive access of the non-Matter sub-equipment to the Matter ecology is realized, and the state synchronization and management of the equipment in the whole life cycle are ensured.

Description

Technical Field

[0001] This invention relates to the field of smart home and Internet of Things (IoT) technology, specifically to a dynamic mapping access method, system, and bridging gateway for sub-devices in a bridging gateway. Background Technology

[0002] With the rapid development of smart home and IoT technologies, the number and variety of smart devices deployed in homes are increasing daily. However, devices from different manufacturers often use different communication protocols (such as Zigbee, Z-Wave, Bluetooth, etc.) and data models, leading to serious ecosystem fragmentation. The Matter protocol, as a universal application layer standard promoted by the Connectivity Standards Alliance (CSA), aims to provide a unified foundation for interconnectivity of smart home devices, but its widespread adoption will still take time, and a large number of existing non-Matter devices exist in the market.

[0003] In existing technologies, common solutions for integrating non-Matter sub-devices into the unified Matter ecosystem mainly fall into two categories: one is to upgrade the sub-device hardware or firmware to directly support the Matter protocol, and the other is to perform protocol conversion and adaptation through a cloud platform. The first solution is costly, time-consuming, and difficult to cover a massive number of existing devices. While the second solution avoids device-side modifications, it typically relies on fixed, predefined device model mapping tables, lacking flexibility. When sub-devices are diverse, functionally complex, or their capabilities change dynamically (e.g., new features added after firmware upgrades), fixed mapping rules are difficult to adapt, easily leading to mapping failures or missing functions. More importantly, existing solutions lack effective management of the entire sub-device lifecycle. When sub-devices are added, removed, go offline, or their capabilities change, the device information on the control platform often fails to be updated in a timely and automatic manner, resulting in inconsistencies between the platform's displayed status and the actual device status, affecting user control experience and system reliability.

[0004] Therefore, there is an urgent need for an access solution that can achieve flexible and adaptive mapping on the gateway side and intelligently manage the lifecycle of sub-devices, so as to seamlessly connect heterogeneous non-Matter sub-devices to the unified Matter control ecosystem at low cost and high efficiency. Summary of the Invention

[0005] To address the problems of inflexible mapping, high access costs, and difficult lifecycle management in existing technologies when non-Matter sub-devices access the Matter ecosystem, this invention provides a dynamic mapping access method, system, and bridging gateway for sub-devices in a bridging gateway, thereby resolving the aforementioned technical deficiencies.

[0006] This invention proposes a dynamic mapping access method for sub-devices in a bridging gateway, the method comprising the following steps: S1. The bridging gateway obtains the functional capability information of the connected non-Matter sub-devices; S2. The bridging gateway performs structured parsing of functional capability information to generate a sub-device capability description model; S3. The bridging gateway matches the sub-device capability description model with the preset Matter device model mapping rules to determine the corresponding Matter device model mapping scheme. S4. The bridging gateway dynamically generates Matter endpoints based on the Matter device model mapping scheme and establishes binding relationships between the generated Matter endpoints and non-Matter sub-devices. S5. The bridging gateway publishes Matter endpoint information to the control platform via the Matter protocol; S6. When a change in the status or functionality of a non-Matter sub-device is detected, the bridging gateway performs an update or recycling operation on the Matter endpoint based on the sub-device capability description model and the Matter device model mapping scheme.

[0007] Preferably, in step S1, the bridging gateway obtains the functional capability information of the connected non-Matter sub-devices, including the following sub-steps: S11. The bridging gateway interacts with non-Matter sub-devices via local communication. S12. Obtain at least one control command, at least one reportable attribute, and at least one event type supported by the non-Matter sub-device from the interaction process as functional capability information.

[0008] Preferably, in step S2, the bridging gateway performs structured parsing of the functional capability information, including the following sub-steps: S21. The bridging gateway extracts the device type identifier, function item list, and parameter definition from the functional capability information according to the preset capability resolution rules; S22. Organize the extracted device type identifier, function item list and parameter definition into a structured data model representing the function set, parameter range and status synchronization mode to obtain the sub-device capability description model.

[0009] Preferably, in step S3, the bridging gateway matches the sub-device capability description model with the preset Matter device model mapping rules, including the following sub-steps: S31. Using the device type identifier and / or function item contained in the sub-device capability description model as the matching basis, query the preset mapping rule library to obtain one or more related mapping rules; S32. Based on the queried mapping rules, determine the target Matter device type, number of endpoints, and cluster combination method corresponding to the non-Matter sub-devices to form a Matter device model mapping scheme.

[0010] More preferably, in step S32, if multiple related mapping rules are found, they are sorted according to their respective priority order, and the target mapping definitions of the multiple mapping rules are applied sequentially according to the sorted priority order. The definition conflicts during the application process are handled according to the preset conflict resolution strategy to generate a unified Matter device model mapping scheme.

[0011] More preferably, the process of forming the Matter device model mapping scheme further includes at least one of the following processes: Based on the queried mapping rules, the functional item parameters in the capability description model of the mapped sub-devices are transformed. Based on preset capability trimming rules, the functional items in the sub-device capability description model are trimmed.

[0012] Preferably, in step S6, the bridging gateway performs an update or recycling operation on the Matter endpoint, including the following sub-steps: S61. When a non-Matter sub-device is detected to be offline, the attribute value of the Matter endpoint used to characterize the reachability of the device in the Matter protocol is set to unreachable, and the status reporting to the control platform based on the status changes of the offline non-Matter sub-device is suspended. S62. When an offline non-Matter sub-device is subsequently detected to be online again, the attribute value in the Matter endpoint used to characterize the device reachability is set to reachable status, and the current status data of the non-Matter sub-device is read to initiate a status synchronization report to the control platform. S63. When a change in the functionality of a non-Matter sub-device is detected, the sub-device capability description model is regenerated based on the changed capability information. The regenerated sub-device capability description model is matched with the Matter device model mapping rules to obtain an updated Matter device model mapping scheme. The set of clusters supported by the Matter endpoint is updated or a new Matter endpoint is created and bound to the non-Matter sub-device based on the updated Matter device model mapping scheme. S64. When it is determined that a non-Matter sub-device has been removed or has been offline for a period of time exceeding a preset recycling threshold, the identification information of the Matter endpoint is removed from the list of bridging device components published by the bridging gateway to the control platform, and the binding relationship between the Matter endpoint and the non-Matter sub-device is released.

[0013] This invention also proposes a dynamic mapping access system for sub-devices in a bridging gateway, used to implement the method described above, the system comprising: The information acquisition module is configured to acquire the functional capability information of connected non-Matter sub-devices; The capability parsing module is configured to perform structured parsing of the functional capability information acquired by the information acquisition module, and generate a sub-device capability description model. The rule matching module is configured to match the sub-device capability description model generated by the capability parsing module with the preset Matter device model mapping rules to determine the corresponding Matter device model mapping scheme. The endpoint management module is configured to dynamically generate Matter endpoints based on the Matter device model mapping scheme determined by the rule matching module, and to establish a binding relationship between the generated Matter endpoints and non-Matter sub-devices. When a change in the status or functional capabilities of a non-Matter sub-device is detected, the module will perform update or recycling operations on the Matter endpoints. The protocol interaction module is configured to publish Matter endpoint information generated by the endpoint management module to the control platform via the Matter protocol.

[0014] The present invention also proposes a smart home bridging gateway, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the dynamic mapping access method for sub-devices in the bridging gateway as described above.

[0015] The present invention also proposes a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the dynamic mapping access method for sub-devices in a bridging gateway as described above.

[0016] Compared with the prior art, the beneficial effects of the present invention are as follows: (1) This invention achieves accurate modeling and mapping of diverse heterogeneous non-Matter sub-devices by collecting the original capabilities of sub-devices, parsing and generating structured capability models, and intelligently matching them with a configurable mapping rule base. Unlike fixed mapping tables, the mapping rule base of this invention supports dynamic loading and updating, and can handle complex capability adaptation through mechanisms such as parameter conversion and capability pruning, thereby greatly expanding the types and range of accessible devices and effectively solving the problems of fixed device models and insufficient scalability.

[0017] (2) By dynamically generating standard Matter endpoints within the bridging gateway and automatically publishing them to the control platform, this invention enables non-Matter sub-devices to be recognized as standard Matter devices and controlled by the control platform without any hardware or firmware upgrades. This avoids expensive equipment modification costs and complex deployment processes, providing an efficient bridging solution for a large number of existing devices to access the Matter ecosystem.

[0018] (3) This invention establishes a complete endpoint lifecycle management mechanism, which can detect the online status (e.g., offline, online again) and functional changes of sub-devices in real time, and automatically trigger the corresponding Matter endpoint's status freeze, attribute update, structural reconstruction, or recycling cleanup operations. This ensures that the device information, status, and capabilities displayed on the control platform are always synchronized with the actual situation of the physical sub-devices, fundamentally solving the problem of information asynchrony on the platform side caused by dynamic changes in devices, and improving the system's reliability and user experience.

[0019] (4) The entire dynamic mapping and lifecycle management process is completed locally on the bridging gateway without relying on real-time decisions from the cloud server. This not only reduces the dependence on network continuity and improves the response speed and reliability of local control, but also reduces the computational and adaptation pressure on the cloud platform, making the system architecture more efficient and robust. Attached Figure Description

[0020] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments, taken with reference to the accompanying drawings: Figure 1 This is a flowchart of the dynamic mapping access method for sub-devices in a bridging gateway; Figure 2 This is an architecture diagram showing the connection between the Matter bridging gateway and non-Matter sub-devices. Figure 3 This is a structural diagram of the dynamic mapping access system for sub-devices in a bridging gateway; Figure 4 This is a schematic diagram of the structure of a computer system suitable for implementing the embodiments of the present invention. Detailed Implementation

[0021] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0022] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0023] Figure 1 A flowchart illustrating the dynamic mapping access method for sub-devices in a bridging gateway is shown. Figure 2 This diagram illustrates the architecture of the Matter bridging gateway and its connection to non-Matter sub-devices. (Refer to the reference.) Figure 1 and Figure 2 The system architecture of this invention mainly includes a control platform (Matter Controller) supporting the Matter protocol, a smart home bridging gateway, and various non-Matter ecosystem devices (sub-devices). The control platform communicates with the bridging gateway via the Matter protocol to achieve device discovery and control. The bridging gateway is the core processing unit, which internally includes functional modules such as sub-device management, capability parsing, mapping rule engine, endpoint management, and protocol interaction layer, working together to complete the access, mapping, and status synchronization of lower-level non-Matter sub-devices. The non-Matter sub-devices refer to smart devices that use non-Matter communication protocols such as Zigbee, Z-Wave, and Bluetooth, requiring protocol conversion through the bridging gateway to access the Matter ecosystem, such as smart locks, lighting, and sensors. This architecture clearly demonstrates the division of data flow and functional modules in this invention; the following steps will elaborate on the specific workflow of each module.

[0024] S1. The bridging gateway obtains the functional capability information of the connected non-Matter sub-devices.

[0025] In this step, the bridging gateway, through its integrated sub-device management module, collects functional capability information of various connected non-Matter sub-devices. The specific implementation includes the following sub-steps: S11. The bridging gateway interacts with non-Matter sub-devices via local communication.

[0026] The bridging gateway supports multiple local communication protocols, including but not limited to: Zigbee 3.0, Bluetooth Low Energy (BLE), Wi-Fi (based on the IEEE 802.11 standard), and various proprietary communication protocols. The gateway establishes a stable data connection with the sub-devices through the corresponding communication interface and conducts bidirectional communication based on this connection.

[0027] S12. Obtain at least one control command, at least one reportable attribute, and at least one event type supported by the non-Matter sub-device from the interaction process as functional capability information.

[0028] The gateway obtains the functional capability information of the sub-device through one or more of the following methods: Device announcement message parsing: When a sub-device powers on, joins the network, or reconnects, it will proactively send a device announcement message to the gateway. The gateway parses this message and extracts information such as the device type identifier, the list of supported functions, the parameter range, and the firmware version.

[0029] Active query and response parsing: The gateway can actively send capability query commands (such as reading device descriptors, function lists, etc.) to sub-devices according to the preset query strategy, and parse the response messages of the sub-devices to extract the set of control commands, the set of reportable attributes, and the set of event types that they support.

[0030] Communication process monitoring and learning: The gateway monitors the messages sent by the sub-devices under normal working conditions, and infers the functional capabilities supported by the sub-devices by analyzing the message structure, command words, attribute IDs and event identifiers.

[0031] Pre-configured capability template matching: For sub-devices with known models or types, the gateway can perform matching within a locally stored pre-configured capability template library. This template library defines standard capability sets for various sub-devices in a structured format, including commands, attributes, events, and their parameter definitions. Upon successful matching, the gateway can directly load the corresponding capability information.

[0032] In implementation, functional capability information includes at least: control commands (operation instructions and parameter structures that the sub-device can respond to), reportable attributes (status or measurement values ​​that the sub-device can report and their units and ranges), and event types (notification messages that the sub-device can trigger and their formats). Simultaneously, the gateway can also acquire and store basic information such as the sub-device's online status and signal strength.

[0033] Continue to refer to Figure 1 and Figure 2 The present invention proposes a dynamic mapping access method for sub-devices in a bridging gateway, which further includes the following steps: S2. The bridging gateway performs structured parsing of functional capability information to generate a sub-device capability description model.

[0034] In this step, the bridging gateway, through its capability resolution module, standardizes the raw functional capability information obtained in step S1, generating a structured, machine-readable capability description model. The specific implementation includes the following sub-steps: S21. The bridging gateway extracts the device type identifier, function item list, and parameter definition from the functional capability information according to the preset capability resolution rules.

[0035] The gateway has a pre-configured or dynamically loaded set of capability resolution rules. These rules define how to identify and extract key capability elements from raw data from different sources: device type identifiers (such as smart color-changing lights), a list of function items (standardized commands, attributes, and event identifiers), and parameter definitions associated with each function item (parameter name, data type, value range, unit, etc.).

[0036] S22. Organize the extracted device type identifier, function item list and parameter definition into a structured data model representing the function set, parameter range and status synchronization mode to obtain the sub-device capability description model.

[0037] The gateway organizes the extracted elements into a unified structured data model. The core of this model includes: a device identifier field (device type, manufacturer, version), a function set field (detailed descriptions of each function item, such as command parameters, attribute units, and reporting conditions), and a status synchronization strategy field (defining polling or reporting preferences). This model abstracts heterogeneous capabilities into a standardized structure, laying the foundation for subsequent intelligent mapping.

[0038] Continue to refer to Figure 1 and Figure 2 The present invention proposes a dynamic mapping access method for sub-devices in a bridging gateway, which further includes the following steps: S3. The bridging gateway matches the sub-device capability description model with the preset Matter device model mapping rules to determine the corresponding Matter device model mapping scheme, which includes the Matter device type, the number of endpoints, and the cluster combination method.

[0039] In this step, the bridging gateway uses its mapping rule module to find the most suitable standard Matter device form factor representation for the sub-device. The specific implementation includes the following sub-steps: S31. Using the device type identifier and / or function item contained in the sub-device capability description model as the matching basis, query the preset mapping rule library to obtain one or more related mapping rules.

[0040] The gateway maintains a Matter device model mapping rule base. This base is stored locally on the gateway in the form of configurable rule tables. Each mapping rule includes fields such as rule identifier, version number, enable flag, priority, source device type, capability identifier, target Matter device type, target cluster identifier, target attribute / command / event identifier, parameter mapping relationship, and optional parameter conversion function identifier. This rule base supports dynamically loading, enabling, or disabling individual rules during runtime and can be remotely updated and versioned via OTA (Over-The-Air), thus expanding support for new device types or functions without upgrading the gateway's main system firmware. The gateway searches this base using elements from the sub-device capability description model as keys, typically matching multiple rules.

[0041] Each rule in the mapping rule base contains structured field definitions to enable fine-grained, configurable mapping from non-Matter sub-device capabilities to the standard Matter device model. Each rule defines at least the following fields: Rule identification and control fields include rule ID, version number, enable flag, and priority.

[0042] Source-side matching fields: These include the source device type and capability identifier. The capability identifier is used to precisely locate a specific capability of the sub-device and consists of "command / attribute / event" types and their parameter structures.

[0043] Target mapping fields include the target Matter device type, target cluster identifier, and the target attribute ID, command ID, or event ID corresponding to the capability, thereby mapping the sub-device capability to a specific functional point defined by the Matter protocol.

[0044] Parameter mapping and conversion fields: This includes parameter field mapping relationships, enumeration value mapping tables, and optional parameter conversion functions. Parameter conversion functions are pre-defined by the platform and can be described using expressions or scripts. They are interpreted and executed by the gateway at runtime to perform unit conversions, enumeration mappings, numerical range clipping, scaling, offset corrections, or data type conversions. For example, when a sub-device reports a temperature in Fahrenheit or with 0.1°C precision, the conversion function can convert it to the Celsius standard unit and precision required by the Matter cluster.

[0045] S32. Based on the queried mapping rules, determine the target Matter device type, number of endpoints, and cluster combination method corresponding to the non-Matter sub-devices to form a Matter device model mapping scheme.

[0046] The gateway performs comprehensive calculations and processing on multiple matched rules to form a final, executable mapping scheme: Rule stacking and conflict resolution: Rules are sorted and stacked according to the priority field configured in the rule configuration. High-priority rules determine the core mapping, while low-priority rules supplement details. Conflicts are resolved according to a preset strategy (such as high-priority rules overriding).

[0047] Parameter conversion processing: When performing mapping, the parameter conversion function defined in the rules is called to perform real-time conversion of sub-device parameters, such as unit conversion (Fahrenheit to Celsius), precision adjustment, enumeration value mapping, or scaling.

[0048] Capability pruning: Based on capability pruning rules, sub-device capabilities are selectively exposed or hidden. Pruning strategies include: pruning based on control platform interface limitations, pruning based on different user role permissions, pruning of specific unstable or sensitive functions, and when too many sub-device capabilities cause the mapped Matter endpoints to exceed the gateway's resource capacity or platform model constraints, the strategy of retaining core capabilities while pruning secondary capabilities according to functional priority.

[0049] Specific strategies for capability pruning also include: Security and permission-based tailoring: Advanced or sensitive capabilities involving security or core device configuration, such as firmware upgrades, factory resets, and door lock management password settings, are either hidden by default or strictly opened according to user role permissions.

[0050] Stability and compatibility-based tailoring: When a certain capability is detected to frequently report anomalies or control failures under a specific sub-device model or firmware version, the gateway can temporarily hide the capability according to rules and record logs to avoid causing status jitter or control failure on the control platform side.

[0051] Resource and model constraint-based pruning: When the capabilities of a sub-device are too complex, and the cluster combination of the endpoints formed after mapping exceeds the gateway's memory resource limit or the complexity of the device model that the control platform can handle, the gateway will retain and expose only the most core basic capability set according to the predefined functional priority, and prune the remaining capabilities.

[0052] Based on the limitations of the control platform UI display: When the platform UI does not support the display or interaction of certain advanced capabilities (such as diagnosis, calibration, maintenance, debugging, etc.), the gateway only exposes the set of capabilities that the platform can recognize and reliably control, and hides the remaining capabilities or maps them as more basic capabilities.

[0053] User-configured customization: Users / administrators can select between a simplified mode and an advanced mode in the App or gateway configuration, or selectively expose capabilities based on family member roles (such as regular members and administrators). For example, regular members may only expose basic capabilities such as on / off, mode, and temperature, while administrators may additionally expose advanced capabilities such as calibration and reset.

[0054] Capability trimming rules can also be configured as rule tables, whose fields may include: "PlatformType, UIProfile, UserRole, CapabilityKey, Trimming Action, Priority, Enable, Trimming ReasonCode, etc." Final Solution Formulation: Based on the above processing, the following are determined: target Matter device type (e.g., dimmable lighting fixture), number of endpoints (usually 1), and the combination of Matter clusters that the endpoint needs to include (e.g., switch cluster, level control cluster, etc.), as well as the attributes, commands, and events that need to be processed within each cluster.

[0055] Continue to refer to Figure 1 and Figure 2 The present invention proposes a dynamic mapping access method for sub-devices in a bridging gateway, which further includes the following steps: S4. The bridging gateway dynamically generates Matter endpoints based on the Matter device model mapping scheme and establishes binding relationships between the generated Matter endpoints and non-Matter sub-devices.

[0056] In this step, the endpoint management module of the bridging gateway instantiates specific logical devices based on the scheme determined in the previous step. The specific implementation is as follows: The gateway dynamically assigns a unique endpoint ID to the sub-device in memory or persistent storage. Then, based on the device type and cluster combination determined in the mapping scheme, it constructs the internal data structure of the endpoint, fully describing the supported Matter clusters, attributes, and commands. Next, the gateway establishes and records a strong binding relationship between the endpoint ID and non-Matter sub-device instances (such as network addresses), while also recording the generation time, binding status, and lifecycle identifiers (such as active), providing a basis for subsequent management.

[0057] Continue to refer to Figure 1 and Figure 2 The present invention proposes a dynamic mapping access method for sub-devices in a bridging gateway, which further includes the following steps: S5, the bridging gateway publishes Matter endpoint information to the control platform via the Matter protocol.

[0058] In this step, the protocol interaction module of the bridging gateway is responsible for informing the external control platform of the logical devices created internally. The specific implementation is as follows: The gateway utilizes the device discovery and announcement mechanisms of the Matter protocol (such as mDNS / DNS-SD, i.e., multicast domain name system / domain name system service discovery) to publish the newly generated Matter endpoint as a component of itself (the bridging device) to the control platform within the MatterFabric (security domain) it has joined. Upon discovery, the control platform recognizes and presents it as a standard Matter device, completing the virtual access.

[0059] Continue to refer to Figure 1 and Figure 2 The present invention proposes a dynamic mapping access method for sub-devices in a bridging gateway, which further includes the following steps: S6. When a change in the status or functionality of a non-Matter sub-device is detected, the bridging gateway performs an update or recycling operation on the Matter endpoint based on the sub-device capability description model and the Matter device model mapping scheme.

[0060] In this step, the endpoint management module of the bridging gateway continuously monitors and intelligently maintains the endpoint lifecycle to ensure that the platform view is consistent with reality. The specific implementation includes the following sub-steps: S61. When a non-Matter sub-device is detected to be offline, the attribute value of the Matter endpoint used to characterize the reachability of the device in the Matter protocol is set to unreachable, and the status reporting to the control platform based on the status changes of the offline non-Matter sub-device is suspended.

[0061] The gateway maintains the communication health status of each sub-device, using a heartbeat mechanism (actively queried by the gateway or actively reported by the sub-device) or a polling mechanism for online determination. Offline determination is based on a preset heartbeat cycle and fault tolerance mechanism, with an offline timeout threshold. Determined by the following formula:

[0062] in, For the preset heart rate cycle, The threshold for determining the number of consecutive lost heartbeats. This is the fault tolerance time. The threshold can be configured differently based on the sub-device type. For example: Constantly powered equipment (such as smart lights and sockets): configurable Second, , seconds, then Second.

[0063] Low-power sleep devices (such as door magnets, sensors): configurable Second, , seconds, then Second.

[0064] When the duration of continuous unresponsiveness of the sub-device reaches When the endpoint is offline, the gateway immediately determines that it is offline. After the determination, the gateway immediately sets the "Reachable" or "Available" attribute of the corresponding endpoint to false and suspends the active reporting of the sub-device's status changes to the platform.

[0065] S62. When an offline non-Matter sub-device is subsequently detected to be online again, the attribute value in the Matter endpoint used to characterize the device's reachability is set to reachable status, and the current status data of the non-Matter sub-device is read to initiate a status synchronization report to the control platform.

[0066] When the gateway receives a valid response from the sub-device (e.g., two consecutive heartbeats), it determines that the sub-device has returned to online status. The gateway sets the endpoint reachability attribute to true (a truth value) and actively reads the key current status of the sub-device. If there is a discrepancy, a status report is triggered to resynchronize the status on the platform side.

[0067] S63. When a change in the functionality of a non-Matter sub-device is detected, the sub-device capability description model is regenerated based on the changed capability information. The regenerated sub-device capability description model is matched with the Matter device model mapping rules to obtain an updated Matter device model mapping scheme. The set of clusters supported by the Matter endpoint is updated or a new Matter endpoint is created and bound to the non-Matter sub-device based on the updated Matter device model mapping scheme.

[0068] The gateway detects device announcement message changes or calculates capability fingerprints (by hashing the device type set, capability identifier (Key) list, commands / attributes / events corresponding to each capability and their parameter structure (field name, type, enumeration, range, unit), firmware version / capability version number, etc., in the capability description model to obtain the fingerprint F). cap The system compares the changes to identify capability changes (such as new features added in firmware upgrades). Once a change is detected, the gateway re-executes steps S1 to S3 to generate a new capability description model and mapping scheme. Depending on the severity of the change, two update strategies are employed: Method 1 (In-situ Update): While keeping the endpoint identifier unchanged, update the internal description information of the endpoint (such as the device type list and cluster list in the descriptor cluster) and trigger the control platform to re-identify or refresh the device information.

[0069] Method 2 (Endpoint Reconstruction): First, mark the original endpoint as unreachable (i.e., set the Reachable / Available attribute of the original endpoint to false). Then, create a new endpoint identifier based on the new mapping scheme and establish a binding. Finally, publish the new endpoint information to the platform. This method is suitable for scenarios where there are significant changes in capabilities or where in-situ updates may cause platform compatibility issues.

[0070] S64. When it is determined that a non-Matter sub-device has been removed or has been offline for a period of time exceeding a preset recycling threshold, the identification information of the Matter endpoint is removed from the list of bridging device components published by the bridging gateway to the control platform, and the binding relationship between the Matter endpoint and the non-Matter sub-device is released.

[0071] For sub-devices that are actively removed or remain offline for more than a certain period (e.g., 24 or 72 hours, configurable), the gateway performs failover. First, at the Matter protocol level, the endpoint's ID is removed from the component list attributes of the bridging device; simultaneously, service exposure and attribute reporting for all clusters connected to that endpoint are stopped. Second, internally within the gateway, binding relationships are broken, and related mappings, subscriptions, and cached states are cleaned up. The reclaimed endpoint identifier will enter a configurable cooldown period (e.g., 10 minutes). During this cooldown period, the identifier will not be immediately assigned to a new sub-device to avoid short-term fluctuations in the device identifier perceived by the control platform due to frequent device online / offline cycles.

[0072] Further reference Figure 3 As an implementation of the above method, this invention also proposes a dynamic mapping access system for sub-devices in a bridging gateway, which can be specifically applied to various electronic devices. The dynamic mapping access system 300 for sub-devices in the bridging gateway includes the following modules: Information acquisition module 310 is configured to acquire functional capability information of connected non-Matter sub-devices; The capability parsing module 320 is configured to perform structured parsing of the functional capability information acquired by the information acquisition module and generate a sub-device capability description model. The rule matching module 330 is configured to match the sub-device capability description model generated by the capability parsing module with the preset Matter device model mapping rules to determine the corresponding Matter device model mapping scheme. The endpoint management module 340 is configured to dynamically generate Matter endpoints based on the Matter device model mapping scheme determined by the rule matching module, and to establish a binding relationship between the generated Matter endpoints and non-Matter sub-devices. When a change in the status or functional capabilities of a non-Matter sub-device is detected, the Matter endpoints are updated or reclaimed. The protocol interaction module 350 is configured to publish Matter endpoint information generated by the endpoint management module to the control platform via the Matter protocol.

[0073] The present invention also proposes a smart home bridging gateway, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the dynamic mapping access method for sub-devices in the bridging gateway as described above.

[0074] The present invention also proposes a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the dynamic mapping access method for sub-devices in a bridging gateway as described above.

[0075] The following is for reference. Figure 4 It shows a schematic diagram of the structure of a computer system 400 suitable for implementing terminal devices or servers in the embodiments of this application. Figure 4 The terminal device or server shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0076] like Figure 4 As shown, the computer system 400 includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 402 or programs loaded from storage section 408 into random access memory (RAM) 403. The RAM 403 also stores various programs and data required for the operation of the computer system 400. The CPU 401, ROM 402, and RAM 403 are interconnected via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0077] The following components are connected to I / O interface 405: input section 406 including keyboard, mouse, etc.; output section 407 including liquid crystal display (LCD) and speakers, etc.; storage section 408 including hard disk, etc.; and communication section 409 including network interface card such as LAN card, modem, etc. Communication section 409 performs communication processing via a network such as the Internet. Drive 410 is also connected to I / O interface 405 as needed. Removable media 411, such as disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 410 as needed so that computer programs read from them can be installed into storage section 408 as needed.

[0078] Specifically, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by central processing unit (CPU) 401, it performs the functions defined in the methods of this application. It should be noted that the computer-readable medium described in this application can be a computer-readable signal medium or a computer-readable medium or any combination thereof. The computer-readable medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable 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 application, a computer-readable medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. Program code contained on a computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0079] 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++, and conventional procedural programming languages ​​such as C or similar 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).

[0080] 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.

[0081] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A dynamic mapping access method for sub-devices in a bridging gateway, characterized in that, Includes the following steps: S1. The bridging gateway obtains the functional capability information of the connected non-Matter sub-devices; S2. The bridging gateway performs structured parsing of the functional capability information to generate a sub-device capability description model; S3. The bridging gateway matches the sub-device capability description model with the preset Matter device model mapping rules to determine the corresponding Matter device model mapping scheme. S4. The bridging gateway dynamically generates Matter endpoints based on the Matter device model mapping scheme, and establishes a binding relationship between the generated Matter endpoints and the non-Matter sub-devices; S5. The bridging gateway publishes the Matter endpoint information to the control platform via the Matter protocol; S6. When a change in the status or functionality of the non-Matter sub-device is detected, the bridging gateway performs an update or recycling operation on the Matter endpoint according to the sub-device capability description model and the Matter device model mapping scheme.

2. The dynamic mapping access method for sub-devices in a bridging gateway according to claim 1, characterized in that, In step S1, the bridging gateway obtains the functional capability information of the connected non-Matter sub-devices, including the following sub-steps: S11. The bridging gateway interacts with the non-Matter sub-device via local communication. S12. Obtain from the interaction process at least one control command, at least one reportable attribute, and at least one event type supported by the non-Matter sub-device as the functional capability information.

3. The dynamic mapping access method for sub-devices in a bridging gateway according to claim 1, characterized in that, In step S2, the bridging gateway performs structured parsing of the functional capability information, including the following sub-steps: S21. The bridging gateway extracts the device type identifier, function item list, and parameter definition from the functional capability information according to the preset capability parsing rules; S22. The extracted device type identifier, function item list and parameter definition are organized into a structured data model representing the function set, parameter range and state synchronization mode to obtain the sub-device capability description model.

4. The dynamic mapping access method for sub-devices in a bridging gateway according to claim 1, characterized in that, In step S3, the bridging gateway matches the sub-device capability description model with the preset Matter device model mapping rules, including the following sub-steps: S31. Using the device type identifier and / or function item contained in the sub-device capability description model as the matching basis, query the preset mapping rule library to obtain one or more related mapping rules; S32. Based on the queried mapping rules, determine the target Matter device type, number of endpoints, and cluster combination method corresponding to the non-Matter sub-device, and form the Matter device model mapping scheme.

5. The dynamic mapping access method for sub-devices in a bridging gateway according to claim 4, characterized in that, In step S32, if multiple related mapping rules are found, they are sorted according to their respective priority order. The target mapping definitions of the multiple mapping rules are applied sequentially according to the sorted priority order, and the definition conflicts during the application process are handled according to the preset conflict resolution strategy to generate a unified Matter device model mapping scheme.

6. The dynamic mapping access method for sub-devices in a bridging gateway according to claim 4 or 5, characterized in that, The process of forming the Matter device model mapping scheme also includes at least one of the following processes: Based on the queried mapping rules, the functional item parameters in the sub-device capability description model to which it is mapped are transformed. According to preset capability trimming rules, the functional items in the sub-device capability description model are trimmed.

7. The dynamic mapping access method for sub-devices in a bridging gateway according to claim 1, characterized in that, In step S6, the bridging gateway performs an update or recycling operation on the Matter endpoint, including the following sub-steps: S61. When the non-Matter sub-device is detected to be offline, the attribute value of the Matter endpoint used to characterize the reachability of the device in the Matter protocol is set to unreachable, and the status reporting to the control platform based on the status change of the offline non-Matter sub-device is suspended. S62. When the offline non-Matter sub-device is subsequently detected to be online again, the attribute value in the Matter endpoint used to characterize the device reachability is set to reachable status, and the current status data of the non-Matter sub-device is read to initiate a status synchronization report to the control platform. S63. When a change in the functional capabilities of the non-Matter sub-device is detected, the sub-device capability description model is regenerated based on the changed functional capability information. The regenerated sub-device capability description model is matched with the Matter device model mapping rule to obtain an updated Matter device model mapping scheme. The set of clusters supported by the Matter endpoint is updated or a new Matter endpoint is created and bound to the non-Matter sub-device based on the updated Matter device model mapping scheme. S64. When it is determined that the non-Matter sub-device has been removed or the continuous offline time exceeds the preset recycling threshold, the identification information of the Matter endpoint is removed from the list of bridging device components published by the bridging gateway to the control platform, and the binding relationship between the Matter endpoint and the non-Matter sub-device is released.

8. A dynamic mapping access system for sub-devices in a bridging gateway, characterized in that, The system for implementing the method of any one of claims 1 to 7 comprises: The information acquisition module is configured to acquire the functional capability information of connected non-Matter sub-devices; The capability parsing module is configured to perform structured parsing of the functional capability information acquired by the information acquisition module to generate a sub-device capability description model; The rule matching module is configured to match the sub-device capability description model generated by the capability parsing module with the preset Matter device model mapping rules to determine the corresponding Matter device model mapping scheme. The endpoint management module is configured to dynamically generate Matter endpoints based on the Matter device model mapping scheme determined by the rule matching module, establish a binding relationship between the generated Matter endpoints and the non-Matter sub-devices, and perform update or recycling operations on the Matter endpoints when a change in the status or functional capabilities of the non-Matter sub-devices is detected. The protocol interaction module is configured to publish Matter endpoint information generated by the endpoint management module to the control platform via the Matter protocol.

9. A smart home bridging gateway, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the dynamic mapping access method for sub-devices in a bridging gateway as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the dynamic mapping access method for sub-devices in the bridging gateway as described in any one of claims 1 to 7.

Images