Home network-based device management method, apparatus, device, and storage medium

Abstract

The application discloses a device management method and device based on a home network, equipment and storage medium, the method comprises the following steps: constructing a unified data model in a home access gateway; the data model references network resources through a hierarchical path name, and utilizes local cache to analyze the path name, and does not initiate a query request to an affiliated device based on the path name; passively capturing network protocol packets of a dumb terminal through a network bridge port mirror, determining the running state of the dumb terminal, and communicating with the intelligent terminal through a lightweight publish / subscribe protocol; abstracting the physical topology of a multi-node mesh network into a topology structure with the home access gateway as a root node; the extended nodes and the devices hung below in the multi-node mesh network are abstracted into a single logical device under the root node; in response to a management strategy or a device reported event, adjusting the network configuration by dynamically creating or destroying multiple instance objects in the data model; and pushing state change notifications to the intelligent terminal according to a subscription mechanism.

Description

Technical Field

[0001] This application belongs to the field of Internet of Things (IoT) technology, specifically relating to a device management method, apparatus, device, and storage medium based on a home network. Background Technology

[0002] With the rapid development of the Internet of Things (IoT) and artificial intelligence (AI), the number of various home network electronic devices has surged. Currently, these devices vary greatly in form and are installed in scattered locations, causing routine maintenance to consume too much of the valuable time of ordinary home users. Furthermore, a failure in any part of the network can disrupt the rhythm of digital home life and even increase unnecessary maintenance costs.

[0003] However, the network communication technologies of the various auxiliary devices differ too much, and there is a lack of unified management. Summary of the Invention

[0004] The purpose of this application is to provide a device management method, apparatus, device, and storage medium based on a home network, which can solve the problem of lack of unified management of auxiliary devices in a home network.

[0005] To solve the above-mentioned technical problems, this application is implemented as follows: In a first aspect, embodiments of this application provide a device management method based on a home network, the method comprising: A unified data model is built in the home access gateway; the data model references network resources through hierarchical path names, and uses local caching to parse the path names, without initiating query requests to auxiliary devices based on the path names; By passively capturing network protocol messages of dumb terminals through bridge port mirroring, the operating status of the dumb terminals is determined, and communication with smart terminals is achieved through a lightweight publish-subscribe protocol. The physical topology of the multi-node mesh network is abstracted into a topology structure with the home access gateway as the root node; the extension nodes and downstream devices in the multi-node mesh network are abstracted into a single logical device under the root node; In response to management policies or device-reported events, network configuration is adjusted by dynamically creating or destroying multiple instance objects in the data model; Status change notifications are pushed to the smart terminal according to the subscription mechanism.

[0006] Optionally, the construction of a unified data model in the home access gateway includes: For a request to create a multi-instance object path, a new instance of the multi-instance object is created; the end of the object path indicates that the system automatically assigns an instance identifier; The newly allocated instance identifier is backfilled into the object path to generate a complete instance reference address.

[0007] Optionally, the multi-instance object includes an access control entity, and the step of creating a new instance of the multi-instance object based on a creation request for a path to the multi-instance object includes: Based on the creation request for the access control entity, the sorting parameters of the access control entity are set; the sorting parameters are used to determine the verification priority of the access control entity in the access control chain, so that the home access gateway performs permission verification in the order of the sorting parameters.

[0008] Optionally, creating a new instance of the multi-instance object based on the creation request for the multi-instance object path includes: If the object path of the creation request includes a retrieval expression, the base instance is located in the local cache according to the retrieval expression, and the newly created instance is inserted after the base instance; During the creation process, if the creation request does not provide a complete set of parameters, the instance initialization is completed using preset default values.

[0009] Optionally, the step of pushing status change notifications to the smart terminal according to the subscription mechanism includes: Register a subscription instance in the event subscription table; the subscription instance is associated with a specific event path and notification target; If an event matching the event path is detected, a notification request is generated based on the subscription instance; Without querying the source device status, the notification request is directly distributed to the corresponding notification target.

[0010] Optionally, after constructing a unified data model in the home access gateway, the method further includes: The communication proxy and intelligent control unit deployed inside the home access gateway are encapsulated as independent container images; For resource-constrained terminal devices, the communication protocol stack is integrated in the form of a non-containerized dynamic link library.

[0011] Optionally, the dumb terminal automatically obtains a virtual network address only when accessing the network via Dynamic Host Configuration Protocol (DHCP); or, when DHCP fails, the dumb terminal automatically assigns a private virtual network address; the intelligent control unit does not send any probe or query messages to the dumb terminal.

[0012] Secondly, embodiments of this application provide a device management apparatus based on a home network, the apparatus comprising: The model building module is used to build a unified data model in the home access gateway; the data model references network resources through hierarchical path names and uses local caching to parse the path names, and does not initiate query requests to auxiliary devices based on the path names; The device communication module is used to passively capture network protocol messages of dumb terminals through bridge port mirroring, determine the operating status of the dumb terminals, and communicate with smart terminals through a lightweight publish-subscribe protocol. The topology abstraction module is used to abstract the physical topology of the multi-node mesh network into a topology structure with the home access gateway as the root node; the extension nodes and downstream devices in the multi-node mesh network are abstracted into a single logical device under the root node; The network adjustment module is used to adjust the network configuration by dynamically creating or destroying multiple instance objects in the data model in response to management policies or device-reported events. The notification push module is used to push status change notifications to the smart terminal according to the subscription mechanism.

[0013] Thirdly, embodiments of this application provide an electronic device, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the device management method based on a home network as described in the first aspect.

[0014] Fourthly, embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the device management method based on a home network as described in the first aspect.

[0015] The beneficial effects of this application are: In this embodiment, a unified data model centered on locally cached pathname resolution is constructed, transforming pathname resolution from a network input / output operation into a memory lookup operation. This reduces the interference of management plane query traffic on the business plane and lowers memory usage. Secondly, auxiliary devices are divided into dumb terminals and smart terminals, and differentiated communication strategies are adopted. That is, dumb terminals are passively sensed through bridge mirroring, and smart terminals are connected via lightweight publish / subscribe, which is compatible with existing legacy devices while leveraging the ability to finely manage new smart devices. Finally, the node mesh network is flattened and abstracted into a single logical device, and an active push mechanism based on an event subscription table is adopted. This ensures that during the entire push process, the communication agent does not initiate any status confirmation query to the source device, and the pushed content is entirely based on locally cached data, saving bandwidth resources and power consumption of the home access gateway and control terminal. Attached Figure Description

[0016] Figure 1This is a schematic diagram of an application scenario provided in an embodiment of this application.

[0017] Figure 2 This is a flowchart of a device management method based on a home network provided in an embodiment of this application.

[0018] Figure 3 This is a flowchart illustrating the specific steps of a device management method based on a home network, as provided in an embodiment of this application.

[0019] Figure 4 This is a block diagram of a device management device based on a home network provided in an embodiment of this application.

[0020] Figure 5 This is a block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0021] The present application will be further described below with reference to the accompanying drawings and embodiments.

[0022] The following will clearly and completely describe the concept, specific structure, and resulting technical effects of this application in conjunction with embodiments and accompanying drawings, so as to fully understand the purpose, features, and effects of this application. Obviously, the described embodiments are only a part of the embodiments of this application, not all of them. Other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are all within the scope of protection of this application. Furthermore, all connections / linkages involved in the patent do not simply refer to direct contact between components, but rather to the ability to form a better connection structure by adding or reducing connecting accessories according to specific implementation conditions. The various technical features in this application can be combined interactively without contradicting each other.

[0023] In modern home networks, the types of auxiliary devices are mixed and the communication protocols are different. Traditional home access gateway management solutions either require strong coupling management agents on the device side or rely on active polling and probing, which causes the central processing unit (CPU) and bandwidth overhead of the home access gateway control plane to increase linearly with the number of devices.

[0024] For example, in a home network environment, peripheral devices such as children's mobile phones, guest cameras, and smart home hubs typically have different network access permissions. Parents may restrict children's mobile phones from accessing game servers during work hours but allow them to access educational websites; meanwhile, guest devices are usually only allowed to access the internet and not the home's internal storage. Traditional home access gateways typically use hash tables or binary search trees to store access control rules, requiring multiple memory addressing and comparison operations for each data packet forwarding. When the number of rules is large, under high concurrency traffic, the CPU utilization of the home access gateway will increase significantly, leading to increased network latency or even packet loss.

[0025] Secondly, in home network management scenarios, multiple instance objects typically need to be arranged in a specific logical order. However, in dynamic environments, the row number of the target rule may change due to the addition or deletion of other rules, making it difficult for the caller to know the exact insertion position in advance. Furthermore, creation requests reported by auxiliary devices may lack some non-critical parameters due to network packet loss or device capability limitations. Traditional home access gateway management interfaces usually require requests to carry complete parameters; otherwise, they will directly report an error. This results in a low success rate for management transactions and a poor user experience.

[0026] Finally, physical reconfiguration of the wireless mesh network (MESH) causes management topology jitter and complete loss of state visibility for agentless dumb terminals.

[0027] To address the aforementioned issues, this application provides a device management method, apparatus, device, and storage medium based on a home network. First, an application scenario related to an embodiment of this application will be described.

[0028] See Figure 1 The device management method based on a home network provided in this application can be applied to, for example... Figure 1 The system architecture shown includes a home access gateway 1 comprising an embedded system software platform 5, an isolated operating environment 6 running on the system software platform 5, and an intelligent control unit 7 and a communication agent 8 deployed in the isolated operating environment 6.

[0029] In this embodiment, the home access gateway 1 contains an intelligent control unit 7 and a communication agent 8; the intelligent terminal 4 contains a monitoring and publish / subscribe module; the dumb terminal 2 has no agent and is only passively sensed; the control terminal 3 is responsible for display and alarms; each module can run on an embedded platform / isolated operating environment.

[0030] In some embodiments, the intelligent control unit 7 is configured to build and maintain a unified data model, and dynamically create or destroy multi-instance objects in response to management policies or device-reported events. The communication agent 8 is configured to parse hierarchical pathnames based on local caching, receive events, and push status change notifications.

[0031] In some embodiments, the smart terminal 4 includes a corresponding embedded system software platform and an isolated operating environment, wherein a monitoring logic unit and a publish / subscribe communication module are deployed for actively reporting status, subscribing to events, and communicating with the home access gateway-side communication agent 8.

[0032] For example, the smart terminal 4 may include: smart air conditioner, smart range hood, smart refrigerator, smart oven, smart stove, smart washing machine, smart water heater, smart washing equipment, smart dishwasher, smart projector, smart TV, smart clothes rack, smart curtains, smart audio-visual equipment, smart socket, smart speaker, smart speaker box, smart fresh air equipment, smart kitchen and bathroom equipment, smart bathroom equipment, smart robot vacuum cleaner, smart window cleaning robot, smart mopping robot, smart air purifier, smart steam oven, smart microwave oven, smart water heater, smart air purifier, smart water dispenser, smart camera, smart door lock, etc.

[0033] In one possible implementation, the smart terminal 4 includes a Wireless Fidelity (Wi-Fi) module, which receives network account, network password and user account information sent by the user through the application software (APP) module on the home access gateway 1, and automatically connects the device to the designated Wi-Fi network.

[0034] In some embodiments, the smart terminal 4 and the home access gateway 1 are connected via a network. The network may include a wired network or a wireless network; the wired network may include a wide area network (WAN), a metropolitan area network (MAN), or a local area network (LAN); and the wireless network may include Wi-Fi or Bluetooth.

[0035] In one possible implementation, the smart terminal 4 also includes a server module and a status feedback module. The server module is used to upload the device's own device information and user account information to the server after the Wi-Fi module successfully connects to the network. This allows the server to bind the device based on the user account information, establishing an association between the device and the user account. The status feedback module is used to provide network configuration and binding status information to the server and the app, ensuring that the user can view the device status in real time.

[0036] In some embodiments, sensitive data is encrypted using a symmetric encryption algorithm with dynamic key exchange and the AES256 encryption standard is used to ensure the confidentiality and integrity of the data; multiple physical links share a single security association to simplify key management overhead; for non-sensitive data, plaintext transmission is allowed to ensure response speed and throughput performance; a two-way certificate authentication and digital signature mechanism based on the Open Secure Sockets Layer (OpenSSL) 3.0 protocol is used to ensure the integrity and non-repudiation of the data.

[0037] In some embodiments, the intelligent control unit 7 maintains a local database for storing data models and device status history; the control terminal's query operations on the intelligent control unit's database, as well as the intelligent control unit's data push operations based on the subscription mechanism, all follow the rules of local cache resolution path names and do not initiate network requests to auxiliary devices based on query or push operations.

[0038] For example, the local database could be an embedded lightweight database (SQLite), adding AES256 encryption protection to a standard SQLite database. The system periodically saves memory snapshots to handle unexpected scenarios such as abnormal exits; upon normal, proactive exit, it automatically saves the latest data to non-volatile storage for recovery upon the next startup. Data storage is performed using transaction delivery to ensure data integrity within the data model. SQLite is a lightweight, micro-relational database, transaction-based, highly customizable, and in practical applications, it has a very small footprint, fast processing speed, and its data files are memory-based with periodic snapshots, easily handling special situations such as power outages and network interruptions.

[0039] In some embodiments, the dumb terminal 2 does not have an intelligent control unit 7, a communication agent 8, or a publish / subscribe communication module, and only accesses the network through conventional network protocol messages such as Dynamic Host Configuration Protocol (DHCP), Address Resolution Protocol (ARP), and multicast Domain Name System (mDNS); the home access gateway passively captures such messages through bridge port mirroring to determine its operating status, without sending probe or query messages to the dumb terminal 2.

[0040] In some embodiments, the control terminal 3 runs a management client that provides a graphical display interface, a text control / display interface, and message alerts, for subscribing to status change notifications pushed by the home access gateway and presenting the network topology and device status.

[0041] For example, the display interface presents network topology and traffic statistics in chart form; device configuration and log information in text form; and alarms and anomaly notifications in real-time alert messages. The graphical user interface includes two interfaces: a simple mode and an expert mode. Before opening the expert mode to the external network for remote expert analysis and diagnosis, the user must complete the authorization operation in the simple mode. The expert mode requires explicit user authorization to be enabled and automatically closes after a preset time to prevent prolonged exposure of high-risk management interfaces.

[0042] For example, control terminal 3 includes a mobile phone, tablet, personal computer, or embedded touch panel used by home users or maintenance personnel. Control terminal 3 runs a management client program that communicates with the intelligent control unit in the home access gateway via long-connection protocols such as WebSocket. This program is used to subscribe to device events, query data model path names, display real-time topology and alarm information, and issue management commands as authorized. Control terminal 3 itself is not an auxiliary managed device of the home access gateway, does not participate in device-side agent communication in the publish-subscribe protocol, and only serves as a consumer and control end on the management plane.

[0043] In one possible implementation, the home access gateway 1 is equipped with a client program that can work in conjunction with a smart home cloud platform. The client program can be used to provide a user interface, facilitating the management and remote control of at least one smart terminal 4 by the user.

[0044] The device management method based on a home network provided in this application will be described in detail below with reference to the accompanying drawings.

[0045] Figure 2 This is a flowchart of a device management method based on a home network provided in an embodiment of this application. See also... Figure 2 The method includes the following steps.

[0046] Step 101: Build a unified data model in the home access gateway.

[0047] In this embodiment of the application, the data model references network resources through hierarchical path names and uses local caching to resolve path names, without initiating query requests to auxiliary devices based on path names.

[0048] In some embodiments, the data model is set in the intelligent control unit.

[0049] In some embodiments, the data model includes entity objects, parameters, commands, events, and path names. Entities are further divided into single-entity and multi-entity types. A single-entity object does not contain tables or lists, has only one instance, and is used to combine other data for definition and transmission. A multi-entity object contains one or more instances, has object creation and destruction capabilities, and is usually organized in a tabular form, with each instance equivalent to a row of data in this table.

[0050] In some embodiments, parameters are used to define the properties or variables of an object, which have read and write characteristics and have type and value attributes; commands are methods that can be invoked by the controller, which have the ability to call input parameters and return output parameters; events are used to define object-specific notifications; and pathnames are fully qualified references to objects, object instances, or parameters in the proxy instantiated data model or supporting data model, and they follow the syntax definition below.

[0051] In some embodiments, objects and parameters in the data model are referenced through hierarchical path names; when resolving path names, the communication agent completes addressing and retrieval based only on local cache or readily available local data, without initiating network requests to auxiliary devices based on path names.

[0052] In some embodiments, a new instance of a multi-instance object is dynamically created through the Add operation, and an instance identifier is automatically assigned in the object path; a partial parameter setting mode is supported, and when a complete set of parameters is not provided, the instance initialization is completed using preset default values.

[0053] In some embodiments, when creating a multi-instance object of a permission class, a sorting parameter is set for the new instance, and the order of all instances is adjusted based on the sorting parameter to optimize the matching efficiency of access control decisions.

[0054] Step 102: Passively capture the network protocol messages of the dumb terminal through bridge port mirroring to determine the operating status of the dumb terminal, and communicate with the smart terminal through the lightweight publish-subscribe protocol.

[0055] In some embodiments, the bridge module (Linux bridge br0) of the home access gateway is configured with a port mirroring policy to copy the Layer 2 frames flowing through the bridge to the packet capture unit of the communication agent, so that the intelligent control unit can construct the survival state machine of the dumb terminal based on the source physical network (Media Access Control Address, MAC) address, virtual network (Internet Protocol, IP) address allocation information and the transmission and reception time interval of the above-mentioned packets.

[0056] In some embodiments, for dumb terminals without any deployed management agent, their ARP address resolution messages, DHCP dynamic configuration messages, and mDNS service discovery messages are passively captured. If ARP or DHCP keep-alive frames are continuously observed within a preset aging window, the terminal is determined to be online; if the DHCP lease period expires and there is no non-service broadcast, the terminal is determined to be offline. The intelligent control unit does not send any ARP requests, Internet Control Message Protocol (ICMP) probes, or management query messages to the dumb terminal.

[0057] In some embodiments, for auxiliary devices running smart terminal modules, after power-on, they actively establish a lightweight publish-subscribe session with the home access gateway communication agent based on the Transmission Control Protocol (TCP) or Transport Layer Security (TLS). They report their own parameters and events by publishing and receive configuration change or other device event notifications issued by the home access gateway by subscribing.

[0058] For example, the smart terminal receives the Publish from the smart terminal and sends data to the smart control unit to update the data model. The smart terminal subscribes to Device.Host.3.Status. When the dumb terminal goes offline, the agent actively pushes a notification to the smart terminal.

[0059] In some embodiments, the dumb terminal automatically obtains a virtual network address via Dynamic Host Configuration Protocol (DHCP) when accessing the network or assigns a private virtual network (IP) address when DHCP fails; the intelligent control unit does not send any probe or query messages to the dumb terminal.

[0060] In some embodiments, a dumb terminal refers to a network device that does not have a dedicated management communication stack, does not run a communication agent, and does not respond to any management queries.

[0061] For example, when a dumb terminal accesses the network, it automatically obtains a virtual network address according to RFC2131 via Dynamic Host Configuration Protocol. If DHCP interaction fails, it selects a private virtual network address within the 169.254.0.0 / 16 address range according to RFC3927 to complete local link communication. During this process, the dumb terminal only sends regular service and discovery messages and does not actively report its management status to the home access gateway. Discovery messages include ARP, DHCP, and mDNS.

[0062] In some embodiments, the intelligent control unit in the home access gateway strictly adheres to the principle of non-intrusive management and does not send ARP requests, ICMP messages, Simple Network Management Protocol (SNMP) queries, or any proprietary management probe messages to dumb terminals.

[0063] For example, the determination of whether a dumb terminal is online or offline, its IP address, and its service type is based entirely on protocol analysis and timing inference of the messages sent by the dumb terminal itself, captured by the bridge port mirror.

[0064] Step 103: Abstract the physical topology of the multi-node mesh network into a topology structure with the home access gateway as the root node.

[0065] In this embodiment of the application, the extended nodes and downstream devices in the multi-node mesh network are abstracted as a single logical device under the root node.

[0066] In some embodiments, a home network may include multiple wireless mesh network (MESH) extension nodes, physically forming a multi-hop wireless backhaul and dynamic association.

[0067] For example, when constructing a unified data model, the intelligent control unit defines the home access gateway as the only logical root node. All MESH extension nodes are not expanded into independent lower-level network elements in the management model, but are abstracted as a single logical device under the root node. The terminal devices connected to it are uniformly mounted in the Host or Station table on the root node side in the data model, and their physical attachment location is recorded only through a current associated access point attribute.

[0068] In some embodiments, when a MESH extension node undergoes physical reorganization due to signal switching or a terminal device roams at Layer 2, the logical path name remains unchanged, and the event subscription relationship and access control instance are unaffected.

[0069] In some embodiments, a flat logical topology is used to manage the multi-node MESH network, and MESH extension nodes and their downstream devices are uniformly abstracted into a single logical device. Physical link reassembly does not trigger logical topology changes. The communication agent and intelligent control unit are deployed in a containerized manner in the home access router and support dynamic integration of non-containerized smart terminal modules.

[0070] In some embodiments, the communication agent and intelligent control unit are packaged into a standardized lightweight container image and deployed in the isolated operating environment of the home access router, and the resource utilization rate is dynamically adjusted; for resource-constrained smart devices, the smart terminal module is integrated into the original firmware of the device in the form of a non-containerized dynamic link library.

[0071] Step 104: In response to management policies or device-reported events, adjust network configuration by dynamically creating or destroying multi-instance objects in the data model.

[0072] In some embodiments, management policies include adding access rules and setting timed policies, and device-reported events include device online and parameter exceeding limits.

[0073] In some embodiments, the unified data model maintained by the intelligent control unit includes multiple instance objects, such as online device tables, permission tables, event subscription tables, and MESH node tables.

[0074] For example, when a management policy is received from the control terminal or a status change event is reported by the smart terminal, the smart control unit generates a corresponding create (Add) operation or destroy (Delete) operation, and dynamically creates or destroys instances in the corresponding multi-instance objects.

[0075] For example, when a new smart terminal is launched, the system creates a new instance under the Device.Host. table to record the IP and MAC address, and creates a corresponding permission instance under the Permission. table according to the default role policy; when the terminal is offline for more than the aging threshold, the permission instance is destroyed and the associated subscription instance is cleaned up.

[0076] Step 105: Push status change notifications to smart terminals according to the subscription mechanism.

[0077] In some embodiments, events are managed through a subscription table. When the communication agent detects that an event has been triggered, it directly pushes a notification request to the subscriber without initiating a status query to the event source device.

[0078] In some embodiments, notification requests are cached when the subscriber is offline and resumed in sequence after the subscriber reconnects to ensure the timing integrity of event notifications.

[0079] In some embodiments, the Add operation supports locating a baseline instance based on a retrieval expression and inserting a new instance after the baseline instance, thereby achieving conditional ordered insertion.

[0080] In some embodiments, the control terminal subscribes to events from the intelligent control unit via a long connection protocol, and the intelligent control unit actively pushes event data, thus avoiding polling requests from the control terminal.

[0081] In some embodiments, step 105 may include: registering a subscription instance in an event subscription table; associating the subscription instance with a specific event path and a notification target; generating a notification request based on the subscription instance when an event matching the event path is detected; and directly distributing the notification request to the corresponding notification target without querying the source device status.

[0082] In summary, this embodiment constructs a unified data model centered on locally cached path name resolution, transforming path name resolution from a network input / output operation to a memory lookup operation. This reduces the interference of management plane query traffic on the business plane and lowers CPU utilization. Secondly, auxiliary devices are divided into dumb terminals and smart terminals, and differentiated communication strategies are adopted. That is, dumb terminals are passively sensed through bridge mirroring, and smart terminals are connected via lightweight publish / subscribe, which is compatible with existing legacy devices while leveraging the ability to finely manage new smart devices. Finally, the node mesh network is flattened and abstracted into a single logical device, and an active push mechanism based on an event subscription table is adopted. This ensures that during the entire push process, the communication agent does not initiate any status confirmation query to the source device, and the pushed content is entirely based on locally cached data, saving bandwidth resources and power consumption of the home access gateway and control terminal.

[0083] Figure 3 This is a flowchart illustrating the specific steps of a device management method based on a home network, as provided in an embodiment of this application. (See attached flowchart.) Figure 3 The method includes the following steps.

[0084] Step 201: Create a new instance of the multi-instance object based on the creation request for the multi-instance object path.

[0085] In this embodiment, the end of the object path indicates that the system automatically assigns an instance identifier.

[0086] In some embodiments, the path name consists of a hierarchical hierarchy of parent and child objects, separated by periods ".". If it points to a parameter path, the parameter name ends with the path name.

[0087] In some embodiments, the pathnames used to access the proxy data model are divided into the following six categories.

[0088] 1. Object path refers to the path name of a singleton object or a multi-instance object (i.e., a data model table). Object paths end with a period (.), except in reference parameter scenarios. If the path name contains multiple multi-instance objects, a placeholder {i} will be used when accessing data tables within the proxy-supported data model. Object paths and object instance paths are sometimes referred to as "partial paths."

[0089] 2. Object instance path: The path name pointing to a specific row in the data table within the proxy instantiated data model (i.e., a single instance of a multi-instance object). It locates the specified object instance through the instance identifier. By convention, this path ends with a period (.), except in scenarios involving reference parameters. Object instance paths and object paths are sometimes also referred to as "partial paths."

[0090] 3. Parameter path, refers to the path name of the specified parameter under the object.

[0091] 4. Command path, refers to the path name of the object's custom operation.

[0092] 5. Event path, refers to the path name of the object's custom event.

[0093] 6. Search path, which includes search criteria, is used to locate a set of multiple instance objects and their corresponding parameters. It can carry search expressions or wildcards.

[0094] In some embodiments, pathnames serve two main functions: addressing and retrieval. The first five types of pathnames are used to locate specific objects, parameters, commands, or events; searching a path returns a set of object instances and their corresponding parameters through a retrieval operation. In addressing scenarios, the final pathname matching result is zero or one instance; where, depending on the scenario, a matching result of zero instances is usually considered an anomaly. In retrieval scenarios, a search path can match zero or one or more instances; where, in most scenarios, a matching result of zero instances is not considered an anomaly.

[0095] In some embodiments, step 201 includes: setting sorting parameters for the access control entity based on the creation request for the access control entity.

[0096] In this embodiment of the application, the sorting parameter is used to determine the verification priority of the access control entity in the access control chain, so that the home access gateway performs permission verification in the order of the sorting parameter.

[0097] In one possible implementation, access control rules in the data model are abstracted as multi-instance objects `Device.LocalAgent.ControllerTrust.Role.{i}.Permission.`. Here, `Order` (ordering parameter): an integer type used to define the physical position of the rule in the access control chain; `Target` (target address): used to define the IP address, MAC address, or domain name to which the rule applies; `Action`: used to allow or deny; and `Status`: used to enable or disable.

[0098] For example, a user might want a newly added "Block access to social networks" rule to have higher priority than an existing "Allow HTTP access" rule. In this case, the smart control unit sets Order=5 in the Add request, while the existing HTTP rule has Order=10. Upon receiving this request, the communication agent creates a new instance in the permissions table. The system does not determine the verification order based on the instance's numeric identifier; instead, it reads the value of the Order parameter.

[0099] In one possible implementation, after creating a permission instance, the communication agent sorts all instances in the permission table in ascending or descending order according to the Order parameter value. This allows subsequent access control decisions to complete permission matching in a single linear traversal, avoiding the CPU overhead caused by multiple hash lookups.

[0100] This simplifies the traditional lookup process, which involves hash collision handling, into a linear traversal. Since the number of rules N in a home network is typically small, and linear traversal has an excellent hit rate, it reduces memory usage and decreases the failure rate of network behavior.

[0101] In other embodiments, step 201 includes: if the object path of the creation request includes a retrieval expression, locating the base instance in the local cache according to the retrieval expression, and inserting the newly created instance after the base instance; during the creation process, if the creation request does not provide a complete set of parameters, using preset default values ​​to complete instance initialization.

[0102] In one possible implementation, the object path points to the role and permission table and ends with a period to instruct the communication agent to automatically assign an instance identifier; the creation request carries the allow_partial flag with a value of true, allowing only the sorting parameter to be set while the other parameters use preset default values; the sorting parameter is named Order and has a value that determines the verification order of the permission instance in the access control chain; after the communication agent completes instance creation, it inserts the automatically assigned instance identifier into the object path, generating a complete parameter path in the form of "...Permission.{i}.Order".

[0103] For example, a multi-instance entity object is created as follows: add { allow_partial: TRUE create_objs { obj_path: "Device.LocalAgent.ControllerTrust.Role.1.Permission." param_settings { param: "Order" value: "13" Required: FALSE } } } Here, Add indicates that an instance is being created; obj_path is the path name; the parameter name represents the authorization command (granting new permissions), and if a report message is received, it carries an event Device.LocalAgent.ControllerTrust.Role.1.Permission.2.Order; the parameter value is 13.

[0104] In this way, by introducing a search expression-driven insertion mechanism and intelligent default value filling, the problems of difficult instance location and creation failure caused by incomplete parameters in dynamic network environments are solved, significantly improving the adaptability and stability of the home access gateway management system.

[0105] Step 202: Fill the newly allocated instance identifier back into the object path to generate a complete instance reference address.

[0106] In some embodiments, the multi-instance object includes an access control entity.

[0107] In some embodiments, since the instance identifier of the multi-instance object is dynamically allocated by the communication agent at runtime, when the intelligent control unit issues an Add request, the object path ends with a period "."; after the communication agent successfully creates the instance, it inserts the newly allocated instance identifier before the period, thereby generating a complete instance reference address.

[0108] In some embodiments, after step 202, the above-described device management method based on a home network further includes: a communication agent and intelligent control unit deployed inside the home access gateway are encapsulated as independent container images; and for resource-constrained terminal devices, a communication protocol stack is integrated in the form of a non-containerized dynamic link library.

[0109] For example, resource-constrained terminal devices can be low-power sockets.

[0110] In some embodiments, the home access gateway compiles and packages the communication agent and intelligent control unit into an independent container image compliant with the OCI standard, which runs in the container engine of the home access gateway; the communication agent and control unit communicate within the container via local Unix domain sockets or loopback TCP, without relying on an external network.

[0111] For example, for auxiliary smart terminals with limited Flash and RAM resources, instead of introducing a container runtime, the lightweight publish-subscribe protocol stack is compiled into a non-containerized dynamic link library and directly integrated into the device's original firmware main program. The firmware main logic then calls the library interface to complete registration, publishing, and subscription.

[0112] In some embodiments, when a device goes offline without warning, the intelligent control unit passively determines that the device is faulty or offline based on the absence of heartbeat messages, and the communication agent sends a corresponding alarm message to the client that has subscribed to the offline event; wherein, the intelligent control unit is used for data analysis and alarm information generation, and publishes the alarm information to the client that has subscribed to the corresponding event via the communication agent.

[0113] Step 203: Passively capture the network protocol messages of the dumb terminal through bridge port mirroring to determine the operating status of the dumb terminal, and communicate with the smart terminal through the lightweight publish-subscribe protocol.

[0114] The method for this step is similar to that of step 102, and will not be repeated here to avoid repetition.

[0115] In some embodiments, various messages sent by the dumb terminal are passively captured; these messages include ARP messages, DHCP messages, and mDNS messages; without initiating any active query requests to the dumb terminal, the operating status of the dumb terminal is determined based on the sending and receiving sequence and field content of the various messages; based on the operating status of the dumb terminal, the dumb terminal is connected to the bridge port of the router through mirroring.

[0116] In some embodiments, a lightweight publish / subscribe protocol stack is loaded through a smart terminal module to generate a message with a preset header length; the message is then used to communicate with the home access router to access the home network.

[0117] Step 204: Abstract the physical topology of the multi-node mesh network into a topology structure with the home access gateway as the root node.

[0118] The method for this step is similar to that of step 103, and will not be repeated here to avoid repetition.

[0119] In some embodiments, after step 204, the above method may further include: When the intelligent control unit determines that it is necessary to add a child instance for a specified parent object, it sends an Add request to the communication agent. The Add request carries the object path of the target multi-instance object and the set of parameters to be set. The object path ends with a period "." and does not carry an instance identifier, instructing the communication broker to automatically assign a new instance identifier; The Add request further carries the allow_partial flag. When the allow_partial flag is set, it allows only some of the key parameters in the parameter set to be set. The remaining unset parameters are initialized by the communication agent using preset default values. After completing instance creation, the communication agent fills the newly assigned instance identifier back into the object path, generates a complete object instance path, and returns the object instance path as the response content of the Add request to the intelligent control unit. When a newly created instance is referenced, its pathname resolution process follows the local cache resolution rules of claim 3, and no network request is initiated to the auxiliary device.

[0120] Step 205: In response to management policies or device-reported events, adjust network configuration by dynamically creating or destroying multi-instance objects in the data model.

[0121] The method for this step is similar to that of step 104, and will not be repeated here to avoid repetition.

[0122] Step 206: Register the subscription instance in the event subscription table.

[0123] In this embodiment of the application, the subscription instance is associated with a specific event path and notification target.

[0124] In some embodiments, an event subscription table is maintained in the smart control unit of the home access gateway. When a user subscribes to an event through the control terminal, the system registers a subscription instance in the table.

[0125] Step 207: If an event matching the event path is detected, generate a notification request based on the subscribed instance.

[0126] In some embodiments, the home access gateway monitors events actively reported by smart terminals and passively inferred by dumb terminals.

[0127] In some embodiments, a notification request is a structured data block that includes: event source, event type, current value, timestamp, and target address.

[0128] It's important to note that during the generation of notification requests, data is stored locally, rather than without sending any requests or management queries to the auxiliary devices to confirm their operational status. This is because the gateway trusts the consistency of its local data model and does not require secondary confirmation of status from the source device.

[0129] For example, the intelligent control unit detects that the value of Device.Host.5.Status has changed to Offline. The system iterates through the event subscription table, searching for all instances whose event paths match Device.Host.5.Status and whose filter condition ChangedTo=="Offline", resulting in the Sub_001 instance. A notification request is then generated based on the Sub_001 instance.

[0130] In some embodiments, step 207 may include: When the intelligent control unit needs to monitor a specific event, it creates a subscription instance in the event subscription table through the Add operation. The path name of the subscription instance points to the event path to be monitored, and carries the event filtering conditions and notification target information. The communication agent maintains the event subscription table, and when it detects that an event generated by an auxiliary device matches the event path and filtering conditions, it generates a notification request based on the subscription instance. The notification request carries the event type, event timestamp, and event-related information. Without querying the auxiliary devices, the communication agent directly pushes the notification request to the notification target specified by the subscribed instance. The notification targets include intelligent control units and control terminals with established connections. For the same event path, multiple subscription instances are allowed. When an event is triggered, the communication broker generates corresponding notification requests based on the notification targets of each subscription instance, thereby achieving multi-point distribution of the event.

[0131] Step 208: Without querying the source device status, the notification request is directly distributed to the corresponding notification target.

[0132] In some embodiments, without querying the source device status, the notification message is proactively pushed to the notification target via an established communication connection based on the target address in the notification request.

[0133] In some embodiments, the control terminal client subscribes to messages or directly queries the local database of the intelligent control unit via the WebSocket protocol; the intelligent control unit, acting as a server, proactively pushes messages and alerts to the control terminal after the WebSocket session is established; the WebSocket connection remains persistent between the client and the server, requiring only a single handshake for bidirectional data transmission, eliminating the need for long HTTP headers and polling requests, thereby reducing control overhead and bandwidth consumption and improving real-time performance; the WebSocket protocol supports binary payload transmission and context reuse to improve data compression efficiency.

[0134] For example, notification messages can be proactively pushed to the user's mobile app through an established WebSocket connection, without the mobile app needing to initiate an HTTP request.

[0135] In some embodiments, the same event path can be associated with multiple subscription instances.

[0136] For example, in addition to the mobile app, the smart lock may also subscribe to the Device.Host.5.Status event to automatically pause recording when the camera is offline. In this case, when the camera offline event occurs, the system will generate two notification requests based on the two different subscription instances, one pushed to the mobile phone and the other to the lock. This demonstrates the flexibility of the subscription mechanism.

[0137] In this way, for battery-powered dumb terminals or smart terminals, the number of wake-up calls and power consumption caused by responding to gateway queries are reduced. Furthermore, the generation and distribution of notifications are separated and do not depend on the real-time response on the device side, resulting in strong system robustness.

[0138] In some embodiments, after step 208, the method further includes: caching notification requests to be distributed in response to the dumb terminal or smart terminal going offline; and pushing the cached notification requests in the order in which the dumb terminal or smart terminal reconnects.

[0139] In summary, this application embodiment enables rapid and automatic discovery, automatic configuration, real-time statistics, fault diagnosis, and warnings for various wired or wireless electronic devices in a home network, excluding the access router. The unique features of this invention, such as weak hardware dependency, scalability, and dynamic maintenance, effectively eliminate technical differences and barriers between various auxiliary network devices, greatly simplifying the configuration, management, and status monitoring of various network electronic devices within a typical home. This truly achieves the elimination of routine manual maintenance for numerous auxiliary network electronic devices, fully keeping pace with the new developments in artificial intelligence.

[0140] Figure 4 This is a block diagram of a device management device based on a home network provided in an embodiment of this application, such as... Figure 4 As shown, the home network-based device management device 400 includes the following modules.

[0141] The model building module 401 is used to build a unified data model in the home access gateway. The data model references network resources through hierarchical path names and uses local caching to resolve path names, without initiating query requests to auxiliary devices based on path names. The device communication module 402 is used to passively capture network protocol messages of dumb terminals through bridge port mirroring, determine the operating status of dumb terminals, and communicate with smart terminals through a lightweight publish-subscribe protocol. The topology abstraction module 403 is used to abstract the physical topology of a multi-node mesh network into a topology structure with the home access gateway as the root node; in the multi-node mesh network, the extension nodes and downstream devices are abstracted into a single logical device under the root node; The network adjustment module 404 is used to adjust the network configuration by dynamically creating or destroying multiple instance objects in the data model in response to management policies or device-reported events. The notification push module 405 is used to push status change notifications to smart terminals according to the subscription mechanism.

[0142] Optionally, the model building module 401 is specifically used for: For a request to create a multi-instance object path, a new instance of the multi-instance object is created; the end of the object path indicates that the system automatically assigns an instance identifier; The newly allocated instance identifier is populated back into the object path to generate a complete instance reference address.

[0143] Optionally, the multi-instance object includes an access control entity, model building module 401, specifically used for: Based on the creation request for the access control entity, the sorting parameters of the access control entity are set; the sorting parameters are used to determine the verification priority of the access control entity in the access control chain, so that the home access gateway performs permission verification in the order of the sorting parameters.

[0144] Optionally, the model building module 401 is specifically used for: If the object path in the creation request includes a retrieval expression, locate the base instance in the local cache based on the retrieval expression, and insert the newly created instance after the base instance; During the creation process, if the creation request does not provide a complete set of parameters, the instance initialization is completed using preset default values.

[0145] Optionally, the notification push module 405 is specifically used for: Register a subscription instance in the event subscription table; associate the subscription instance with a specific event path and notification target; If an event matching the event path is detected, a notification request is generated based on the subscribed instance; The notification request is directly distributed to the corresponding notification target without querying the status of the source device.

[0146] Optionally, the home network-based device management device 400 also includes a model deployment module for: The communication proxy and intelligent control unit deployed inside the home access gateway are encapsulated as independent container images; For resource-constrained terminal devices, the communication protocol stack is integrated in the form of a non-containerized dynamic link library.

[0147] Optionally, the dumb terminal automatically obtains a virtual network address only when accessing the network via Dynamic Host Configuration Protocol (DHCP); or, when DHCP fails, the dumb terminal automatically assigns a private virtual network address; the intelligent control unit does not send any probe or query messages to the dumb terminal.

[0148] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0149] Figure 5 This is a structural block diagram of an electronic device according to an exemplary embodiment. For example... Figure 5 As shown, the electronic device includes: a processor, a memory, a communication interface, and a communication bus. The processor, memory, and communication interface communicate with each other through the communication bus. The memory is used to store at least one executable instruction, which causes the processor to execute the steps of the device management method based on a home network as described in the preceding embodiment.

[0150] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory including instructions that can be executed by a processor of an electronic device to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0151] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described embodiments of the device management method based on a home network and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0152] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described device management method based on a home network.

[0153] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar parts between the various embodiments can be referred to each other.

[0154] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

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

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

[0158] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present application.

[0159] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0160] The above is a detailed description of the preferred embodiments of this application. However, the invention of this application is not limited to the embodiments described. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A device management method based on a home network, characterized in that, The method includes: A unified data model is built in the home access gateway; the data model references network resources through hierarchical path names, and uses local caching to parse the path names, without initiating query requests to auxiliary devices based on the path names; By passively capturing network protocol messages of dumb terminals through bridge port mirroring, the operating status of the dumb terminals is determined, and communication with smart terminals is achieved through a lightweight publish-subscribe protocol. The physical topology of the multi-node mesh network is abstracted into a topology structure with the home access gateway as the root node; the extension nodes and downstream devices in the multi-node mesh network are abstracted into a single logical device under the root node; In response to management policies or device-reported events, network configuration is adjusted by dynamically creating or destroying multiple instance objects in the data model; Status change notifications are pushed to the smart terminal according to the subscription mechanism.

2. The method according to claim 1, characterized in that, The construction of a unified data model in the home access gateway includes: Based on the creation request for the multi-instance object path, a new instance of the multi-instance object is created; the end of the object path indicates that the system automatically assigns an instance identifier; The newly allocated instance identifier is backfilled into the object path to generate a complete instance reference address.

3. The method according to claim 2, characterized in that, The multi-instance object includes an access control entity, and the step of creating a new instance of the multi-instance object based on a creation request for a path to the multi-instance object includes: Based on the creation request for the access control entity, the sorting parameters of the access control entity are set; the sorting parameters are used to determine the verification priority of the access control entity in the access control chain, so that the home access gateway performs permission verification in the order of the sorting parameters.

4. The method according to claim 2, characterized in that, The step of creating a new instance of the multi-instance object based on the creation request for the multi-instance object path includes: If the object path of the creation request includes a retrieval expression, the base instance is located in the local cache according to the retrieval expression, and the newly created instance is inserted after the base instance; During the creation process, if the creation request does not carry a complete set of parameters, the instance initialization is completed using preset default values.

5. The method according to claim 1, characterized in that, The step of pushing status change notifications to the smart terminal according to the subscription mechanism includes: Register a subscription instance in the event subscription table; the subscription instance is associated with a specific event path and notification target; If an event matching the event path is detected, a notification request is generated based on the subscription instance; Without querying the source device status, the notification request is directly distributed to the corresponding notification target.

6. The method according to claim 1, characterized in that, After constructing a unified data model in the home access gateway, the method further includes: The communication proxy and intelligent control unit deployed inside the home access gateway are encapsulated as independent container images; For resource-constrained terminal devices, the communication protocol stack is integrated in the form of a non-containerized dynamic link library.

7. The method according to any one of claims 1 to 6, characterized in that, The dumb terminal automatically obtains a virtual network address via Dynamic Host Configuration Protocol (DHCP) when accessing the network; or, when DHCP fails, the dumb terminal automatically assigns a private virtual network address; the intelligent control unit does not send any probe or query messages to the dumb terminal.

8. A device management device based on a home network, characterized in that, The device includes: The model building module is used to build a unified data model in the home access gateway; the data model references network resources through hierarchical path names and uses local caching to parse the path names, and does not initiate query requests to auxiliary devices based on the path names; The device communication module is used to passively capture network protocol messages of dumb terminals through bridge port mirroring, determine the operating status of the dumb terminals, and communicate with smart terminals through a lightweight publish-subscribe protocol. The topology abstraction module is used to abstract the physical topology of the multi-node mesh network into a topology structure with the home access gateway as the root node; the extension nodes and downstream devices in the multi-node mesh network are abstracted into a single logical device under the root node; The network adjustment module is used to adjust the network configuration by dynamically creating or destroying multiple instance objects in the data model in response to management policies or device-reported events. The notification push module is used to push status change notifications to the smart terminal according to the subscription mechanism.

9. An electronic device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the device management method based on a home network as described in any one of claims 1-7.

10. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the home network-based device management method as described in any one of claims 1-7.

Images