WO2019205606A1

WO2019205606A1 - Hierarchical group management apparatus, and system and controlled devices thereof

Info

Publication number: WO2019205606A1
Application number: PCT/CN2018/116828
Authority: WO
Inventors: 王镝程; 赖建州; 连怡仲; 林子闵
Original assignee: 天扬精密科技股份有限公司
Priority date: 2018-04-27
Filing date: 2018-11-22
Publication date: 2019-10-31
Also published as: CN110412965A

Abstract

Disclosed are a hierarchical group management apparatus (110, 210), and a system and controlled devices (400, 401) thereof. The system includes: a primary hierarchical group management apparatus (110) for establishing hierarchical group data corresponding to multiple controlled devices (400, 401); a secondary hierarchical group management apparatus (210) for executing management and control on the controlled devices (400, 401) according to the data; and the multiple controlled devices (400, 401), wherein the primary hierarchical group management apparatus (110) inlcudes a sovereignty announcement module (111), a hierarchical group establishment module (112), a control category distinguishing module (113), an identifier transfer type setting module (114), an identifier generation module (115), a node deletion module (118) and a node replication module (119); and the secondary hierarchical group management apparatus (210) mainly includes an identifier replacement module (212), an identifier addition module (213), an authorization/setting module (214) and a hierarchical group integration module (215). Users can set a required security level by themselves, and autonomously set the management and control of multi-functional groups and multi-element cross-authorization.

Description

Hierarchy group management device and system and its controlled device

Technical field

The invention relates to a control management device, in particular to a hierarchical group management device and system with multi-function group management and multi-cross-authorization management and control functions with selectable set security levels, and a controlled device thereof .

Background technique

With the advancement of technology, all electrical equipment is pursuing remote control. There is currently an IR wireless signal control device such as a television remote control, and there is also an RF wireless signal control device such as an iron gate remote controller. In addition, there is also a power control management system for household electric lights or electric appliances developed by, for example, an Apple computer using a mobile phone via a wireless network such as WIFI or Bluetooth, and a network router.

However, a remote controller such as a TV remote control can only control one type of electrical appliance and cannot be controlled by a group; the iron gate remote controller can only control a controlled device such as an iron gate or a control receiver, and different controlled devices need to be used. Different remote controllers do not have a built-in mechanism for multi-group or multi-party control of the remote controller. When controlling multiple controllers, only a plurality of remote controllers can be prepared. Moreover, the remote controllers cannot manage the remote control identifiers by the user, and can only be managed by the manufacturer's settings. Once the remote control identifier is stolen, the security problem will be poor.

For mobile phone remote control electrical switch functions developed by, for example, Apple Computer, it is necessary to remotely control via the Internet. In addition to problems such as unstable network, limited traffic, and short communication distance, it is more likely to be invaded by network hackers and have security. The problem. Moreover, such a system is limited by the fact that the controlled device needs to have functions such as WIFI or Bluetooth, and must provide a wireless network environment when in use. In addition, the controlled appliance must first be implanted with the remote control identifier by the manufacturer. The user can only use the device with the identifier produced by the manufacturer, and can only establish the control system according to the setting, which is not only expensive, but also the identification. The symbol is stolen or known by the person intent, that is, it is easy to be stolen, and there are loopholes in the control. Moreover, although the system has a group control function, it is only used for such a small range of control of the home, and it is necessary to transmit identifiers to each controlled device one by one, and there is no security function.

In addition, although the current control system can control the controllable power by setting the password, but the overall control is still excessively divergent, and the overall control is easy to lose rigor, which is when the system is large. It is easy to cause problems, and the security level cannot be set or changed depending on the environment and equipment used.

Therefore, it would be possible to provide a device or mechanism that has a simple setting mechanism and a low cost, can integrate existing electrical equipment and electronic devices, and can independently select and change the security level. A big demand.

Summary of the invention

In order to solve the above problems, an object of the present invention is to provide a control architecture that can be constructed by a user, and can perform multi-function individual or group control on a plurality of multiple controlled devices, and can be performed within a desired control range. A hierarchical group management system and device and its controlled device that cross-license management and can automatically set and change the security level of the management by the user.

In order to achieve the above object, the present invention discloses a hierarchical group management system for managing a controller and at least one controlled device, and includes a primary hierarchical group management device, a secondary hierarchical group management device, and at least one controlled device. The master group management device includes: a sovereign announcement module for establishing a sovereign announcement, and the sovereign announcement can be written to at least one of the controller and the at least one controlled device to control the hierarchy a group setting right module, configured to correspond to various controlled devices, each of which specifies at least one other node code, and at least one upper-level group node code representing that the individual nodes belong to the same group. To establish hierarchical group data; an identifier generating module, configured to generate at least one of an individual identifier of the individual nodes and a group identifier of the group node, and incorporate the hierarchical group data into the hierarchical group data And a main hierarchical group output/input module for outputting/entering the sovereign announcement and at least a portion of the hierarchical group data.

The hierarchical group management device includes: a secondary hierarchical group output/input module for outputting at least a part of the hierarchical group data, the hierarchical group data including at least one other node code corresponding to each controlled device, a group node code of each upper-level group of the individual nodes, and at least one of the two identifiers of the individual identifier of the individual node and the group identifier of the group node; the control module is configured to Selecting a signal to generate a wireless control signal including an identifier corresponding to the at least one controlled device for managing operation of the controlled device in one of an individual and a group manner; and, an authorization/setting module, The hierarchical group data is stored in the storage unit, and at least a portion of the hierarchical group data is outputted when the device has the sovereign announcement.

The at least one controlled device includes: a storage unit configured to store at least one controlled device identifier; a wireless receiving unit configured to receive a wireless control signal including the at least one controlled device identifier; and a processing control unit, And configured to identify the at least one controlled device identifier, and identify the received wireless control signal, and perform an action corresponding to the control signal; wherein the storage unit is further configured to store the identifier of the controlled device The sovereignty of the right to manage. The processing control unit further includes a rewrite control module for causing the at least one slave identifier to be rewritten only by the device having the sovereign announcement; and the discarding code control module for causing the discarded at least one The slave identifier cannot be written again as a new slave identifier.

By the above system and device, the user can set the hierarchical group relationship data for most types of controlled devices in the main hierarchical group management device, and automatically generate the control identifier, and then have the sovereign announcement. Next, the data is written into the controller or the controlled device, and then the secondary hierarchical group management device in the controller performs management and authorization. The hierarchical group management device can also accept authorizations and settings from the main hierarchical group management device or other controllers, and can also authorize other controllers with sovereign announcements, and can set each controlled device. In this way, it will enable most users to integrate the cross-control capabilities of various controlled devices, and realize a new management system and device, and can limit the power of mutual authorization to a controllable range. And achieve good authorization and control.

Moreover, in order to achieve the above object, the present invention further provides a hierarchical group management apparatus, wherein the hierarchical group management apparatus further includes an identifier transmission type setting module for specifying a correspondence of at least one of the nodes The identifier transfer type. Thereby, the user can set the controller to remotely control various controlled devices with different security levels. The hierarchical group management device further includes a control category distinguishing module for distinguishing the controlled devices of different control categories, and allowing the user to establish the hierarchical group data in at least one of the preset category and the customized category. In this way, multi-function and multi-control can be performed regardless of customization or preset.

Moreover, in order to achieve the above object, the present invention discloses a hierarchical group management apparatus further comprising a node deletion module for deleting a corresponding identifier of a selected node in the hierarchical group, and changing each of the deleted nodes. The group identifier of the hierarchical group node, making it a specific identifier. In addition, a node copying module is further configured to generate a virtual node having an identifier of the node to be copied, and add the virtual node to the sub-hierarchy of the specific node of the hierarchical group to which the copied node is to be added. And in the sub-hierarchy of each upper-level group node of the particular node. In this way, after the group setting is completed, the group setting can still be modified, and each controlled device can be correctly controlled in a group manner.

Moreover, in order to achieve the above object, the present invention discloses a hierarchical group management apparatus further comprising an identifier replacement module for using the selected group when the identifier of the group node of the selected group is a specific identifier. The corresponding identifier of all the nodes in the sub-hierarchy of the group node represents the corresponding identifier of the selected group node, and is programmed into a wireless control signal. In addition, the hierarchical group management apparatus further includes an identifier adding module, configured to add, by the corresponding identifier of the group node, any identifier of the virtual node associated with the group node when a group node is selected. , representing the corresponding identifier of the selected group node, and compiling the wireless signal. In this way, accurate group control of each controlled device can be performed with the modified group relationship.

Moreover, in order to achieve the above object, the present invention discloses a hierarchical group management apparatus further comprising an authorization/setting module for prohibiting the declaration of sovereignty from being written to other controllers and for outputting to the controlled device. When the identifier has been used by the controlled device and discarded, the identifier is prohibited from being written to the controlled device again; and is also used to set the authorization time when the at least part of the hierarchical group data is output, and Different controllers set different authorization times. The authorization/setting module further includes a controller authorization serial number library having a plurality of controller serial numbers for respectively assigning the respective controller serial numbers to each authorized when authorizing the hierarchical group data to other controllers. Controller.

Moreover, in order to achieve the above object, the present invention discloses a hierarchical group management apparatus further comprising a hierarchical group integration module, which, when receiving new hierarchical group data, is in an uppermost node of the newly added hierarchical group. Automatically accumulating a layer of control category attribute nodes representing the control category of the newly added hierarchical group; and, when the existing hierarchical group data already has the hyperactive control category attribute node, the newly added hierarchical group The control category attribute node may be merged into the same node as the control category attribute node of the existing hierarchical group data; in addition, the new hierarchical group may be added to the existing hierarchical group when receiving the new hierarchical group data. One of the groups is under the jurisdiction of the selected node.

Moreover, in order to achieve the above object, the present invention discloses a controlled device including a storage unit for storing at least one controlled device identifier, and a wireless receiving unit for receiving the at least one controlled device identifier. a wireless control signal; and a processing control unit configured to set the at least one controlled identifier and identify the received wireless control signal to perform an action corresponding to the wireless control signal; wherein the storage unit It is also used to store a sovereign declaration representing the management rights of the controlled device identifier.

In summary, the present invention provides an integrated hierarchical group remote controller that allows a user to customize and customize the object and architecture of the remotely controlled device, and to meet different security level requirements, and to conveniently construct a multi-authorized multi-authorization. And realize the ideal of a remote control to pass the world. The present invention will be further described in detail below with reference to the drawings and embodiments.

DRAWINGS

FIG. 1 is a schematic diagram of an application of a hierarchical group management system according to an embodiment of the invention.

FIG. 2 is a block diagram showing the main structure of a main hierarchical group management apparatus according to an embodiment of the present invention.

FIG. 3 is a schematic diagram of a hierarchical group architecture according to an embodiment of the invention.

4 is a schematic diagram of partial hierarchical group data being copied according to an embodiment of the present invention.

FIG. 5 is a schematic diagram of data storage according to an embodiment of the invention.

FIG. 6A is a schematic diagram of deletion of hierarchical group data according to an embodiment of the present invention.

FIG. 6B is a schematic diagram of a hierarchical group data completion node after deletion according to an embodiment of the invention.

FIG. 7A is a schematic diagram of replication of hierarchical group data according to an embodiment of the invention.

FIG. 7B is a schematic diagram of hierarchical group data completion node replication according to an embodiment of the invention.

FIG. 8 is a schematic diagram of node migration of hierarchical group data according to an embodiment of the invention.

FIG. 9 is a block diagram showing the main structure of a secondary hierarchical group management apparatus according to an embodiment of the present invention.

FIG. 10 is a block diagram showing the main structure of a controlled device according to an embodiment of the present invention.

【Symbol Description】

100,101 computer 200,201 main controller

300 sub controller/controller

301

sub-controller

400, 401 slave

110 Main Level Group Management Device 111 Sovereign Declaration Module

112 Hierarchy Group Building Module 113 Control Category Module

114 identifier transfer type setting module

115 identifier generation module 116 data access module

117 Hierarchy Group Output/Entry Module 118 Node Delete Module

119 node replication module 150 storage unit

701, 702, 703, 704 representative nodes

801,811,812,813,8111,8112,8113,8131,8132,911 representative node

8132’ virtual node tag 900,900’, 901 group

210 hierarchical group management devices

211 Control Module 212 Identifier Replaces Module

213 Identifier Add-on Module 214 Authorization/Setup Module

215 hierarchical group integration module 216 data access module

217 Hierarchy Group Output/Entry Module 218 Node Delete Module

219 node replication module 250 storage unit

411 storage unit 413 wireless receiving unit

415 Process Control Unit 417 Output/Incoming Interface

4151 Abandonment Code Control Module 4152 Rewrite Control Module

detailed description

The detailed construction, features, functions, or usage of the hierarchical group management apparatus and system and its controlled devices in accordance with a preferred embodiment of the present invention will be described in the detailed description of the following embodiments. However, it should be understood by those of ordinary skill in the art that the present invention is not limited to the scope of the invention.

Please refer to FIG. 1. FIG. 1 is a schematic diagram of an application of a hierarchical group management system according to an embodiment of the present invention. As shown in FIG. 1, a hierarchical group management organization according to a preferred embodiment of the present invention includes a computer device 100, a main controller 200, a sub-controller 300, and a majority of the controlled devices 400. The computer device 100, for example, a PC computer, is provided with a main hierarchical group management device 110 for establishing hierarchical group data for managing the majority of the controlled devices 400, and writing the established hierarchical group data to the main In the controller 200. The main controller 200 has a sub-hierarchy group management device 210 for transmitting wireless remote control signals through the wireless module and each controlled device identifier established by the user to manage and control most of the controlled devices. 400; and all or part of the hierarchical group data may be authorized to one or more sub-controllers 300, so that the sub-controller 300 may also be authorized to control each of the controlled devices 400. The main hierarchical group management device 110, the secondary hierarchical group management device 210, and the controlled device 400 constitute a hierarchical group management system of the present invention. Each of the controlled devices 400 may be a relay control device that is connected or combined to, for example, a lamp, an electric curtain, an iron shutter door, an electric door, an electronic lock, a car lock, an air conditioner, and the like.

FIG. 1 and also illustrates a second hierarchical group management organization including a computer device 101, a main controller 201, a sub-controller 301, and a plurality of slaves 401. The main device group management device 110 is built in the computer device 101 for establishing a second hierarchical group data for managing the majority of the controlled devices 401, and writing the created second hierarchical group data to the main In the controller 201. The main controller 201 also has a sub-hierarchy group management device 210 for managing and controlling the majority of the controlled devices 401, and can authorize all or part of the hierarchical group data to the sub-controller 301, and let the sub-controllers 301 can also be authorized to control the slave 401.

In the two organizations shown in FIG. 1, the main controller 200 can partially or fully cross-authorize the sub-controller 301 or the main controller 201 in addition to the sub-controller 300. Similarly, the main controller 201 can also partially or fully cross-authorize the sub-controller 300 or the main controller 200 in addition to the management function to the sub-controller 301. The slave 400 can be controlled by the master 200, the master 201, the sub-controller 300, and the sub-controller 301 by cross-authorization between different organizations. Thereby, when the user holds the sub-controller 300 or 301, part or all of the authorizations from the various hierarchical group management systems can be accepted, and the user is controlled by the controller he holds to control his needs. Authorized multiple controlled devices.

FIG. 2 illustrates the main components of the main hierarchical group management device 110 in a block diagram. The main hierarchical group management device 110 mainly includes: a sovereign announcement module 111, a hierarchical group establishing module 112, a control category distinguishing module 113, an identifier transfer type setting module 114, an identifier generating module 115, a data access module 116, and a hierarchy. The group output/input module 117, the node deletion module 118, and the node copy module 119. Each module may be composed of software and firmware, or may be composed of hardware circuits. Those skilled in the art may implement the following functions according to the functions described below, and thus the details thereof are omitted herein.

The sovereign announcement module 111 is used to announce the sovereignty of the primary hierarchical group management device 110 used and the generated hierarchical group. In this embodiment, when the user first uses the main hierarchical group management device 110 to establish the hierarchical group to which the user belongs, the user is named as the sovereign announcement. And it is best that this sovereignty declaration cannot be changed. Thereafter, when the main hierarchical group management device 110 outputs the generated hierarchical group to the main controller 200, the naming can be output to the main controller 200 together, so that the main controller 200 can have the name as shown in the figure. As shown in Figure 1, various authorizations or cross-authorizations are performed for each master or sub-controller. However, after obtaining the naming, the main controller 200 cannot output the naming to each sub-controller 300, or other main controllers such as 201, to ensure that the sovereignty is located. The main controller 201 has a name from the main hierarchical group management device 110 to which it cooperates. In other words, each controller can only obtain the naming from its primary hierarchical group management device 110. In addition, the primary hierarchical group management device 110 can be used to set at least one backup primary controller, so that if the primary controller is not visible, the data of the hierarchical group can be returned to the primary hierarchical group by using the backup primary controller. The management device 110 further sets the main controller by the main hierarchical group management device 110, and can omit all the troubles of resetting. When the hierarchical group data is written back to the main hierarchical group management device 110, only the primary controller having the sovereign announcement can be used. Since the backup main controller also carries the sovereign announcement, after the main hierarchical group management device 110 receives the sovereign announcement, the hierarchical group data can be written back to the main hierarchical group management device 110. Incidentally, in the present embodiment, although the name is used as an example of the declaration of sovereignty, in other embodiments, other methods may be used as the declaration of sovereignty. In addition, the aforementioned sovereignty declaration may also be automatically given by the system, such as downloading the serial number, without requiring the user to perform the setting of the sovereign announcement.

When the main controller 200 sets each of the controlled devices 400, the naming is also written into each of the controlled devices 400, so that each of the controlled devices 400 knows that the only owner is the main controller 200, not the main Controller 201. Only the main controller 200 can perform the setting data of the controlled device 400, such as rewriting or deleting of the identifier, collectively referred to as rewriting. In this way, each of the controlled devices 400 can be controlled by the main controller 200 to the sub-controller 300 and the cross-authorization to the main controller 201 or the sub-controller 301, but cannot be controlled by the main control. The device 201 or sub-controllers 300 and 301 are modified.

With such a sovereign announcement setting, the present embodiment can be made to disclose that a hierarchical power management system fully grasps the integrity and security of system authorization when performing individual authorization or cross-authorization. That is to say, this method is similar to providing only a key from the main hierarchical group management device, and the main controller to which the key is issued can modify the settings of each controlled device and authorize it to other controllers without being The controller that provides this key can no longer be shared, nor can it modify the settings of each controlled device. Thereby, the right of setting modification under each cross-authorization can be properly managed, and the editing right control in the shared object disclosed by the prior art is significantly different.

The sovereign declaration module 111 can be used to set the serial number of the main controller 200. Although it is not necessary, the user can determine the serial number of the main controller 200. When a special system that needs to encrypt and transmit the password is specified, The serial number can be used. In an embodiment, this serial number designation may also be performed by another independent serial number designation module.

The hierarchical group establishing module 112 is configured to allow a user to input its name, and its other controlled devices 400, through various input devices 400, such as lights, through input devices (not shown) of the computer device 100, for example. Correlation or group, and each designates at least one individual node code representing each controlled device, and at least one upper hierarchical group node code representing that each individual node belongs to the same group to establish hierarchical group data, And stored in the storage unit 150, and according to the group relationship. FIG. 3 illustrates each of the controlled devices 400, such as lights, in a group relationship, organized into a group control relationship diagram having a hierarchical group of three levels, and the

individual nodes

8111, 8112, and 8113 at the lowest level are each There are codenames FAE, organization, R&D, and the three individual nodes are in the same group and have a group node 811 located at the upper parent class thereof, and the code number is 18-5. The group node 811 has a group node 801 of its previous parent class, codenamed Tianyang. The group node 801 serves as the root node of this hierarchical group. The same level as the group node 811, there are also individual nodes 812 and group nodes 813. Among the sub-levels under the group node 813, there is only one other node 8131. In a preferred embodiment, the hierarchy can be set up to 10 orders, and 10,000 nodes.

The control category distinguishing module 113 is configured to distinguish the groups to be constructed by the controlled device 400 according to different wireless signal categories or different control architectures, or distinguish various control categories in the established group, which may be The demand changes. In this embodiment, the main hierarchical group management apparatus 110 has some specific categories to be selected by default in the stored data structure, such as an RF category, an IR category, a context category, and a user-defined comprehensive category of each category. Wait, and can achieve multi-function control function. In the RF category, various types such as lamps, locks, sockets, roller blinds, and the like are pre-set. The IR category is provided with, for example, a television, an air conditioner, a fan, a projector, etc., which can command a device with a standard code without special security control, and achieve good commonality with existing electrical equipment. In a preferred embodiment, each of the above-described hierarchical groups is constructed according to control categories or various types of various controlled devices. The context category is used to allow the user to set a series of controls, such as "going home" or "going out", etc., for each tree node to be set, such as opening or closing, according to time or time. The control can include opening the door lock, turning on the living room lights, and turning on the air conditioner.

The custom comprehensive category is used to allow the user to copy the information of the nodes corresponding to each controlled device in the respective RF category or IR category, and then combine and delete and combine them to set the authorization to each. Hierarchical group data for different primary controllers or sub-controllers. For example, some of the lights and lock nodes in the RF category, and the televisions in the IR category can be established under the root node set by the user as the name/code of the authorized person B, so that the authorized person B can The group of slaves are controlled after the controllers they own are authorized to the group. Moreover, the hierarchical group data contains the control category attributes of the respective controlled devices. Thus, in a preferred embodiment, the customized integrated category receives the copied hierarchical group data, for example, the group 900 shown in FIG. When the hierarchical group data 900' is formed, a control category attribute node representing a control category of the copied hierarchical group named "light" is accumulating on the uppermost node 811 of the copied hierarchical group. 911. In another preferred embodiment, when two groups of the same category are copied, the top-level control category attribute nodes of the two groups may be merged under the same control category attribute node, for example, Below the light 911 of Figure 4. In addition, in an embodiment, a non-merging manner may be adopted, but a group under the entire light category, for example, all nodes including the node 801, may be copied, and then unnecessary nodes, such as node 812, may be deleted. . In addition, each setting under this category can also be added to the data structure to set the effective time when it is to be authorized to the main controller 200 or the sub-controller 300 in the future. Of course, in an application embodiment, a portion of the established hierarchical group data in each category may also be directly authorized to the sub-controller 300.

Moreover, in addition to the default category, the control category distinguishing module 113 also provides establishment of a user-defined category or category, for example, the user adds a name whose name is "extension line". The above is only an example. In actual use, it can be set according to requirements. For example, there may be only one preset category, or the user may customize the category. Therefore, the module can be defined as a user who creates hierarchical group data in at least one of a preset category and a custom category.

The identifier transfer type setting module 114 is configured to set the transfer type of the identifier of each of the controlled devices 400 and integrate it into the aforementioned hierarchical group data. In the present embodiment, six types are set for setting when the data structure is established. The first type is a one-to-one fixed code transmission, that is, when the wireless remote control signal is transmitted, the controlled identifier is not encrypted, and the original identifier can be directly transmitted, and can be applied to, for example, a lamp, an electric curtain, and the like. . The second type is a one-to-many fixed code transmission that can be applied, for example, to sharing an identifier for a plurality of outlets. The third type is one-to-one rolling code transmission, that is, the wireless control signal containing the controlled identifier is given after the default rolling code deformation, which can be applied to, for example, a public door lock, an iron door, and an electric motor. Doors and others need safety a little, but the level is lower. The fourth type is one-to-many rolling code transmission, and the wireless control signal including the controlled identifier is given to the default rolling code and then transmitted, but multiple controlled devices can be set to be the same. The identifiers are turned on together, or selectively opened, such as locomotive central locking, and individual fuel hole locks, seat cushion locks, faucet locks, and the like. The fifth type is one-to-one transmission of name code plus rolling code, that is, in addition to rolling code encryption, the user's name data is added for recording, which can be applied to, for example, access control records and other security requirements are low. At the same time, the entry and exit is recorded. The sixth type is a one-to-one rolling code transmission of two identifiers, that is, for the controlled device, two or more identifiers are used, and the signals are transmitted after being encoded, which can be applied to security requirements. High such as high security door locks, safes, vehicles and others. Since this type of signal has privacy and security considerations, in a preferred embodiment, the user will be prompted to require or not to establish a password. If "Yes" is selected, it is necessary to input, for example, 8 words of English letters and Arabic numerals. A password within or below, and this password is retained and displayed in this hierarchical group management device. This password will be used for controller control. In the future, the controller needs to input this password before entering the type control screen for control, copying and reading. The above types are merely examples, and the actual types may be combined and changed with each other as needed to generate other types.

In an embodiment, the identifier transfer type setting module 114 may also be an automatic setting. That is, for example, when the "light" under the default RF category is selected in the control category distinguishing module 113, this type is automatically set to the fixed transmission type. When the preset "safe" is selected, it is automatically set to the sixth type of transfer type. And so on, but for the type of user-built, the user chooses which type to transmit with the function of the controlled device.

The identifier generating module 115 is configured to, after the hierarchical group establishing module 112 sets the upper and lower parent-child relationship and the same-order node relationship of each node, and assign each node a single identifier representing each controlled device through a random number generating mechanism. Symbol or group identifier and integrate it into the hierarchical group data. The identifier can be, for example, 8 digits, which can result in up to more than 60,000 combinations or more digits to produce more combinations. If a controlled device requires higher security and requires two identifiers, two nodes are given, and there are two identifiers, such as the sixth type described above. If multiple slaves share a node identifier for one-to-many control, the same identifier is given as the second as described above by specifying the same node in the data field or giving the same node reference. , four types of transfer settings. Incidentally, in this embodiment, the identifier generating module generates the identifier mainly based on the nodes specified in the RF category and the IR category, and does not repeat the integration in the context category and the custom comprehensive category. The node repeatedly generates the identifier, so the group in the context category and the custom integrated category can also be established after the corresponding identifier of each node is generated.

FIG. 3 exemplifies the generated node identifiers corresponding to the respective slaves, such as lights, in addition to the node numbers of the respective nodes. For example, the identifier of the group node 811 is AB9D, which corresponds to a group of three controlled devices, which are code-named R&D, organization, and FAE, as long as the identifier of the group node 811 is transmitted, the three The slave will be controlled at the same time. After the identifiers of the nodes are set, the identifiers can be written into the respective controlled devices 400 via the computer device 100, or the complete hierarchical group data can be written into the controller 200, and then written by the controller 200. Each of the controlled devices 400 is provided such that each of the controlled devices has an individual identifier corresponding to the controller, and a group identifier, which can be remotely controlled individually or in groups by the controller 200. In the example given here, when group control is to be performed, each of the controlled devices 400 in the group is controlled by the identifier of the transfer group node. However, in an embodiment, control may also be performed by the identifier of the respective slave 400 in the first transfer group when the group control is selected. Therefore, the present invention is not limited to the transmission group identifier. For the generation and writing of the identifiers, only the individual identifiers written to the respective controlled devices may be generated, and the group written to each group node may not be generated. Group identifier.

As shown in FIG. 5, the data access module 116 has a hash function for generating hierarchical group data about each node generated by each module, such as

nodes

701, 702, 703, and 704. The storage or change is made to each of the storage blocks 0, 1, 2, etc. of the storage component 150, and a connection between the nodes is established. Each storage block will store its name, identifier, upper and lower level reference, same level reference, category distinction, identifier transfer type, etc. for each node with an appropriate data structure.

The hierarchical group output/input module 117 is configured to selectively output at least a portion of the hierarchical group data of each category that has been generated and stored in the storage unit 150, and write to the main controller 200 or the controlled device 400. Or, the set hierarchical group data is read back from the main controller 200. When writing to the controlled device 400, it may be only data related to the individual controlled device, and the data written to the main controller 200 may be all or part of the hierarchical group data. In a preferred embodiment, the data to be written to each sub-controller 300 and the slave 400 is written to the main controller 200 first, and then output to the sub-controller 300 by the main controller 200. Each of the slaves 400 is written to the slave 400 instead of the master group management device 110.

The node deletion module 118 is used to delete a certain node after the identifier setting and writing of each controlled device 400 has been completed, as shown in FIG. 6A and FIG. 6B. FIG. 6A shows the case where the node 8113 is to be deleted under the hierarchical group structure shown in FIG. 3 that has been completed. As shown in FIG. 6B, when the node 8113 is to be deleted, the node deletion module 118 deletes the node 8113 related data stored in the storage unit 150, and associates each parent hierarchical group node 811 in the storage unit with the node 8113. The group identifier of 801 and 801 changes to a specific code, such as FFFF shown in FIG. 6B. In an embodiment, the related group identifiers may be deleted. Therefore, the change here is a specific code, including changing to a specific value, or deleting the group identifier. Moreover, the deletion of the node may be to modify the group data of the original category, or to modify the group data copied to the custom comprehensive category, depending on the requirements. After the modification is completed, the new hierarchical group data is again written into the main controller 200 or the sub-controller 300, so that the main controller 200 or the sub-controller 300 performs a specific control signal transmission according to the specific value. Said later. In an embodiment, the modification may be performed after the partial group data is written into the controller, and then modified in the controller. In this case, it will be described later as the hierarchical group management device. The hierarchical group management device will include this node deletion module. In this way, each of the slaves 400 is not required to be changed by the original setting, so that the programs for which the slaves are to be rewritten can be reduced. In another embodiment, only the related data of the node 8113 itself may be deleted without modifying the identifier of its associated group node. At this time, the group identifier data in the related controlled device 400 needs to be deleted or rewritten. .

The node copying module 119 is configured to, after the identifier setting and writing of each controlled device 400 has been completed, want to partially modify the group relationship and copy a certain node to other nodes, such as 7A and 7B are shown. FIG. 7A shows a situation in which node 8113 is to be copied to node 813 to establish node 8132 under the hierarchical group architecture shown in FIG. As shown in FIG. 7B, when the node 8113 is to be copied, the node copying module 119 copies the related data of the node 8113 stored in the storage unit 150 to the data block associated with the node 813 in the storage unit 150, and adds A virtual node flag 8132' having an identifier of the node 8113 is included as a corresponding identifier of the copied node, under the node 813, and in each sub-level of each parent hierarchical group node of the node 813. As shown in Fig. 7B, the virtual node flag 8132' of the copied node 8132 is also added to the node 813 and the sub-hierarchy of the upper parent node 801. The virtual node tag has no code and is therefore not displayed in the main hierarchical group management device 110, but is stored in each sub-hierarchy node storage block associated with each associated parent hierarchical group node in the storage unit. The copying of the node may be the modification of the group structure data of the original category, or the modification of the group data copied into the custom comprehensive category, depending on the requirements.

After the modification is completed, the new hierarchical group data is again written into the main controller 200 or the sub-controller 300, so that the main controller 200 or the sub-controller 300 performs a specific control signal transmission according to the virtual node flag. Details are given later. In this way, each of the slaves 400 no longer needs to be changed to write a new group node identifier, thereby reducing the number of programs that each slave is to be overwritten. In another embodiment, only the related data of the node 8113 itself may be copied without adding a virtual copy node flag. In this case, new group identifier data, such as AB4D, needs to be added to the corresponding node 8113. In the controlled device 400, this applies to a small number of controlled devices that are easily repaired and rewritten.

Incidentally, the node deletion module 118 and the node replication module 119 respectively delete and add a specific node, and if the group relationship of the specific node is to be moved, the two modules can be executed. That is, after the node copy module 119 performs the copy operation in the new group for the specific node, the node delete module 118 performs the delete operation of the specific node in the original group to complete the move processing. . FIG. 8 illustrates the moving situation of the group 901. The cluster node 901 headed by the group node code 10 is to be moved under the node code 11. At this time, the parent group node node code 02 of the node code 10 is changed to the node code number 11, and is copied to the node code number 11, and is added to the child class under the node code number 11 and the child class of each parent class. The virtual node tag of node code 10 (not shown), that is, the virtual node tag of node code 10 is added in the same level as

node code

02, 08, 11, and 10. In addition, from the sub-level node related data of the group node code 02, the code number 10 is deleted to be disconnected from the original node code 02, and the identifiers of the

node codes

02 and 01 are changed to a specific value (not shown).

Hereinafter, the main constituent components of the sub-hierarchy group management device 210 established in the

controller

200 or 300 will be described next. As shown in FIG. 9, the secondary hierarchical group management device 210 mainly includes: a control module 211, an identifier replacement module 212, an identifier addition module 213, an authorization/setting module 214, a hierarchical group integration module 215, and a data access module. 216. A hierarchical group output/input module 217, a node deleting module 218, and a node copying module 219.

The control module 211 is configured to generate, by the circuit according to the selection signal sent by the user, a control signal including a corresponding identifier of the selected controlled device 400, and identify and receive the controlled device 400 having the corresponding identifier, and manage the At least one controlled device 400 operates.

The identifier substitution module 212 is configured to represent the selected group with the corresponding identifier of all the child nodes included in the selected group node code when determining that the identifier of the selected group node code is a specific group identifier. The corresponding identifier of the node is programmed into the wireless control signal. Referring again to FIG. 6B, after the hierarchical group has been modified, if each controlled device 400 under the group node 811 is selected, since the identifier of the node 811 has been changed to the specific code FFFF, then the

controller

200 or 300 will not issue the original identifier of the node 811, but instead will transmit the identifiers of the nodes in the bottom sub-layer, that is, the identifiers ABD0 and AB0D of the transmitting

nodes

8111 and 8112, which are called substitutions. Similarly, if node 801 is selected, its original identifier will not be transmitted, and the identifiers of transmitting

nodes

8111, 8112, 812, and 813 will be changed.

The identifier adding module 213 is configured to use the identifier of the virtual node of the group node and the identifier of the virtual node associated with the node to be copied when the group node is selected, and represent the The corresponding identifier of the group node is selected and the wireless signal is programmed. In a preferred embodiment, when the identifier appending module 213 is to attach the corresponding identifier of the copied node, check whether there is a virtual node tag in the sub-level to which the group node belongs, and find the identifier of the copied node. . Taking FIG. 7B as an example, if the node 813 is selected, in addition to issuing the identifier AB4D of the node 813, it will search for a virtual node tag in the sub-level below the node 813, and the tag 8132' will be found. The identifier A1BD will then be transmitted along with the identifier AB4D.

The authorization/setting module 214 is configured to select at least a part of the hierarchical group data and output to the sub-control when the controller 200 has the sovereign announcement of the main hierarchical group management device 110 that inputs the hierarchical group data. The 300 is declared and the sovereign announcement is prohibited from being written into the sub-controller 300. At this time, after the uppermost layer of the group to be authorized is selected and designated, under appropriate control, for example, receiving a signal of pressing a double button, the authorization screen is displayed, and then receiving the YES button and pressing the confirm button is received. After the signal, the relevant group data in the storage unit will be marked, and the authorized partial group can be output. Additionally, as previously discussed, the authorization/setting module 214 can also be used to write hierarchical group data back to the primary hierarchical group management device 110 when having a sovereign announcement. In other words, the

controller

200 or 300 is basically the same configuration, one directly receives the controller from the main hierarchical group management device 110 as a main controller, and one controller that receives data from each main controller acts as a sub-controller The controller can only cause the main hierarchical group management device 110 to write a sovereign announcement. In this way, when the secondary hierarchical group management device is built in the

controller

200 or 300, it can be determined whether the

controller

200 or 300 can also copy and authorize at least a part of the group to other controllers.

In addition, the authorization/setting module 214 is used to rewrite the settings of the controlled devices 400 when the secondary hierarchical group management device has a sovereign announcement, and the rewriting includes rewriting and deleting, thereby controlling each receiving The controller 400 is modified to prevent the authorized sub-controller 300 from making modifications. As can be appreciated, the sovereign announcement is also written to each of the slaves 400 for comparison and authentication. Moreover, the authorization/setting module can be used to actively check the used identifier stored by the controlled device 400 when the identifier to be output to the controlled device has been used by the controlled device, and prohibit the This identifier is written to the slave again. In an embodiment, the authorization/setting module 214 can also be controlled by any other specific tag, and is not necessarily controlled by the sovereign announcement of the main hierarchical group management device 110. Sovereignty declaration. In addition, in a preferred embodiment, the authorization/setting module 214 also sets the authorization time when the at least part of the hierarchical group data is allowed to be output, and different authorization times can be set for different controllers.

The authorization/setting module 214 is further configured to write the preset controller serial number into the written controller when the identifier transmission type includes a specific security type. That is, the authorization/setting module further includes a controller authorization serial number library having a majority of the controller serial numbers. When the main controller 200 is to be authorized to the plurality of sub-controllers 300, since some specific security types require the specification of the controller serial number, Therefore, different controller serial numbers are written to each sub-controller 300, and the serial number can be monitored for the number of regulations. For example, if the number of the serial number is 200, then after authorizing 199 sub-controllers, no more authorization can be authorized. . In a preferred embodiment, when the identifiers of the slaves are reprogrammed and updated, the controller numbers can be restarted and again written to the respective authorized controllers by respective assignments.

The hierarchical group integration module 215 is configured to select the second hierarchical group data when the primary controller 200 or the sub-controller 300 receives the second hierarchical group data from other primary controllers, such as the primary controller 201. One of the original hierarchical group data is merged under the selected node, usually under the root node of the original hierarchical group. Of course, in an embodiment, the second hierarchical group data and the original hierarchical group data may be juxtaposed into two separate files, and the display screen sees two separate hierarchical groups. In the case of a practical application, for example, after the hierarchical group data of the home is authorized to a sub-controller, the sub-controller can receive authorization from the main controller of the company for some electrical devices, such as lights or locks. In addition, in the same sub-controller, in addition to having control of various devices in the home, it also has control of some electrical equipment in the company, and achieves multiple authorization functions.

Incidentally, in a preferred embodiment, the hierarchical group integration module 215 combines the received modes of the received groups in the same manner as the custom integrated categories of the control category distinguishing module 113 described above. That is, when receiving the authorized hierarchical group data, for example, receiving the hierarchical group data 900' copied by the group 900 as shown in FIG. 4, it will be on the uppermost node 811 of the authorized hierarchical group. A layer of control attribute attribute 911 representing a control category of the copied hierarchy group. In a preferred embodiment, when groups having the same category exist, the top-level control category attribute nodes of the two groups may be merged under the same control category attribute node, for example, in FIG. 4 The lights are below 911. Moreover, in an embodiment, the non-integration manner may also be adopted, but divided into two independent groups, or two groups under the root node of the original group, for example, under the root node 01 of FIG. The two codes are coded 02 and 03.

The other data access module 216, the hierarchical group output/input module 217, the node deletion module 218, the node copying module 219, and the storage unit 250 are substantially the same as the data stored in the foregoing for the primary hierarchical group management device 110. The module 116, the hierarchical group output/input module 117, the node deletion module 118, and the node copying module 119 are taken, and thus the detailed description thereof is omitted here.

Although the configuration of the secondary hierarchical group management device 210 is different from that of the primary hierarchical group management device 110, it will be understood by those skilled in the art that the primary hierarchical group management can be implemented without departing from the spirit of the present invention. The modules in the device 110 may also be selectively combined individually or entirely in the secondary hierarchical group management device 210, and executed uniformly in the primary controller 200. Further, each of the modules of the main hierarchical group management device 110 and the secondary hierarchical group management device 210 may be selectively provided not necessarily all. In a preferred embodiment, the secondary hierarchical group management device 210 has only the node deletion module 218 and no node replication module 219. In another embodiment, the secondary hierarchical group management device 210 also has a custom integrated category in the control category distinguishing module 113 to facilitate the selection of authorizations. Therefore, the primary and secondary hierarchical group management devices may be simply referred to as hierarchical group management devices, and the main components of the hierarchical group management device are subject to the content of the request.

Finally, FIG. 10 shows that the controlled device 400 in the hierarchical group management system includes: a storage unit 411 for storing at least one controlled device identifier; and a wireless receiving unit 413 for receiving the at least one controlled a wireless control signal of the identifier; the processing control unit 415 is configured to set the at least one controlled identifier, and identify the received wireless control signal to perform an action corresponding to the control signal; and output/input The interface 417 is configured to receive settings of each identifier. And the storage unit 411 is further configured to store a sovereign announcement representing the management right of the controlled identifier, as the management right check when the identifier setting is to be rewritten, and the at least one controlled identifier is used. The token can only be overwritten by the device with the declaration of sovereignty.

Moreover, in a further embodiment, the processing control unit 415 further includes a rewrite control module 4152 and an obsolete code control module 4151; wherein the rewrite control module 4152 is configured to cause the at least one controlled device identifier stored in the storage unit 411 , can only be overwritten by the device with the declaration of sovereignty; that is, after the controlled device is first written with the identifier and the declaration of sovereignty, only the controller or hierarchical group management device with the sovereign announcement can The controller performs the rewriting of the identifier and/or the declaration of sovereignty. The discarding code control module 4151 is configured to store the at least one controlled identifier that has been rewritten and discarded in another location of the storage unit 411, so that at least one new controlled identifier is to be When the controlled device 400 is written, it is checked whether it is the same as the discarded identifier, and when the check result is the same, the discarded at least one controlled device identifier cannot be written into the controlled device 400 again. The new slave identifier. Moreover, the rewrite control function and the discard code control function described above may be executed by the authorization/setting module 214 of the hierarchical group management device 210, as described above, in addition to being executed by the slave 400 itself. The action of checking, and the action of the authorization/setting module 214 to output at least a portion of the hierarchical group data also includes rewriting of the identifier. Therefore, the focus of the two functions is that as long as the process control unit 415 of the slave 400 allows the slave 400 to store the sovereign announcement and the discarded identifier, the two control modules do not have to be provided.

In summary, by the spirit of the present invention and the hierarchical group management device disclosed, each main controller 200 and sub-controller 300 can perform multi-function control, multi-authorization control, and custom control, and each controlled device can be Under strict control, a hierarchical group management structure that can be widely applied is implemented.

The above is only the embodiment of the present invention, and is not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformations made by the description of the invention and the drawings are directly or indirectly applied to other related technologies. The fields are all included in the scope of patent protection of the present invention.

Claims

A hierarchical group management system, characterized in that it comprises a main hierarchical group management device, and

a hierarchical group management device and at least one controlled device; wherein

The main hierarchical group management device includes:

a sovereign declaration module, configured to establish a sovereign announcement, and the sovereign announcement can be written to one of the controller and the at least one controlled device to control the hierarchical group setting right;

a hierarchical group establishing module, configured to correspond to various controlled devices, each designating at least one other node code, and at least one upper hierarchical group node code representing the same group of the individual nodes to establish hierarchical group data ;

An identifier generating module, configured to generate at least one of an individual identifier of the individual nodes and a group identifier of the group node, and incorporate the same into the hierarchical group data; and

a main group group output/input module for outputting/entering at least a part of the sovereign announcement and the hierarchical group data;

The hierarchical group management device includes:

a secondary hierarchical group output/input module for outputting/entering at least a portion of the hierarchical group data;

a control module, configured to generate, according to the selection signal, a control signal including an identifier corresponding to the at least one controlled device to manage operation of the at least one controlled device;

An authorization/setting module for storing the hierarchical group data in the storage unit, and when having the sovereign announcement, outputting at least a part of the hierarchical group data; and wherein

The at least one controlled device stores at least one of an individual identifier and a group identifier corresponding to at least one of the individual nodes.
The hierarchical group management system according to claim 1, wherein the at least one controlled device accepts only at least one of the primary hierarchical group management device and the secondary hierarchical group management device having the sovereign announcement. Rewriting; and the identifier stored by the at least one controlled device cannot be written again as an identifier after it has been changed and discarded.
The hierarchical group management system according to claim 1, wherein the main hierarchical group management device further comprises:

The control category distinguishing module is configured to distinguish the controlled devices of different control categories, and let the user establish the hierarchical group data level in at least one of the preset category and the custom category;

An identifier transfer type setting module for specifying a corresponding identifier transfer type of at least one of the nodes.
A hierarchical group management device, configured to manage at least one of a controller and at least one controlled device, and includes:

a sovereign declaration module, configured to establish a sovereign announcement, and the sovereign announcement can be written to at least one of the controller and the at least one controlled device to control the hierarchical group setting right;

a hierarchical group establishing module, configured to correspond to various controlled devices, each designating at least one other node code, and at least one upper hierarchical group node code representing the same group of the individual nodes to establish hierarchical group data ;

An identifier generating module, configured to generate at least one of an individual identifier of the individual nodes and a group identifier of the group node, and incorporate the same into the hierarchical group data; and

A hierarchical group output/input module for outputting/entering at least a portion of the sovereign announcement and the hierarchical group data.
The hierarchical group management device according to claim 4, further comprising a control category distinguishing module, configured to distinguish different controlled categories of controlled devices, and let the user select one of a preset category and a custom category. , the establishment of the hierarchical group data.
The hierarchical group management apparatus according to claim 5, wherein the control category distinguishing module comprises a custom integrated category for copying at least a part of the hierarchical groups grouped by the other different categories. In the category, the group data is copied, and a common root node is set, and the code of the common root node can be set.
The hierarchical group management apparatus according to claim 6, wherein the hierarchical group data includes a control category attribute of the at least one controlled device, and the customized comprehensive category receives the copied hierarchical group data. A control class attribute node representing a control category of the copied hierarchical group data is accumulating on the uppermost node of the copied hierarchical group data.
The hierarchical group management apparatus according to claim 4, further comprising an identifier transfer type setting module for specifying a corresponding identifier transfer type of at least one of the nodes.
The hierarchical group management apparatus according to claim 8, wherein the identifier transmission type setting module automatically sets one of various transmission types according to a control type to which each of the nodes belongs.
The hierarchical group management apparatus according to claim 4, further comprising a node deleting module, configured to delete a corresponding identifier of the selected deleted node in the hierarchical group data, and change the selected deleted node The group identifier of each upper-level group node is made a specific identifier.
The hierarchical group management apparatus according to claim 4, further comprising a node copying module, configured to generate a virtual node having an identifier of the copied node, and add the virtual node to the hierarchical group In the data, the sub-hierarchy of the specific node of the copied node and the sub-hierarchy of each upper-level group node of the specific node are added.
The hierarchical group management apparatus according to claim 4, wherein the sovereign announcement module is further configured to set a preset controller serial number to the managed controller.
The hierarchical group management apparatus according to claim 4, wherein the sovereign announcement module is further configured to accept at least a part of the hierarchical group data when the hierarchical group management device receives the sovereign announcement. Write.
The hierarchical group management apparatus according to claim 4, further comprising an identifier replacement module for when the group node is selected for control and the group identifier of the group node is a specific identifier A control signal is generated by the corresponding identifier of all nodes in the sub-hierarchy of the group node, representing the group identifier of the group node.
The hierarchical group management apparatus according to claim 4, further comprising an identifier adding module, configured to add a corresponding identifier of the group node to the group when the group node is selected An identifier of a virtual node associated with the group node, representing a corresponding identifier of the group node, and configured to control a wireless signal; and the identifier adding module finds the virtual node by checking a sub-level of the group node .
The hierarchical group management apparatus according to claim 4, further comprising an authorization/setting module for allowing at least the hierarchical group data when the hierarchical group management device has the sovereign announcement a portion is output and is also used to control the writing of the hierarchical group data, and only accepts the writing of another hierarchical group management device having the sovereign announcement; and the output object of at least a portion of the hierarchical group data, At least one of the another hierarchical group management device and the at least one controlled device is included.
A hierarchical group management device, configured to manage at least one of at least one controller and at least one controlled device, the hierarchical group management device comprising:

a hierarchical group output/input module for outputting at least a part of the hierarchical group data, the hierarchical group data including at least one other node code corresponding to each controlled device, and each upper hierarchical group of the individual nodes Group node code, and at least one of the individual identifiers of the individual nodes and the group identifier of the group node;

a control module, configured to generate, according to the selection signal, a control signal including an identifier corresponding to the at least one controlled device, to manage the operation of the at least one controlled device in one of an individual and a group manner; and

And an authorization/setting module for storing the hierarchical group data in the storage unit, and at least a part of the hierarchical group data is outputted when the hierarchical group management device has a sovereign announcement.
The hierarchical group management apparatus according to claim 17, wherein the authorization/setting module is further configured to control writing of the hierarchical group data, and only accept another hierarchical group management having the sovereign announcement. The writing of the device, and the output object of at least a portion of the hierarchical group data, includes at least one of the another hierarchical group management device and the at least one controlled device.
The hierarchical group management apparatus according to claim 17, wherein the authorization/setting module is further configured to prohibit the sovereign announcement from being written to other controllers.
The hierarchical group management apparatus according to claim 17, wherein the authorization/setting module is configured to discard the identifier to be output to the at least one controlled device that has been used by the at least one controlled device When the identifier is again written to the at least one controlled device as its identifier.
The hierarchical group management apparatus according to claim 17, wherein the authorization/setting module is further configured to set an authorization time when the at least part of the hierarchical group data is output, and can be set for different controllers. Different authorization times.
The hierarchical group management apparatus according to claim 17, wherein the authorization/setting module further comprises a controller authorization serial number library having a majority controller number, and is used to authorize the hierarchical group data to other In the case of the controller, the individual controller serial numbers are assigned to the respective authorized controllers.
The hierarchical group management apparatus according to claim 22, wherein the authorization/setting module is used to: after all controller serial numbers have been allocated, after the corresponding identifiers of the nodes are updated, The controller numbers are again assigned to each of the authorized controllers.
The hierarchical group management apparatus according to claim 17, further comprising a node deletion module for deleting an original corresponding identifier of the selected deleted node in the hierarchical group data, and changing the selected deletion The group identifier of each upper-level group node of the node, making it a specific identifier.
The hierarchical group management apparatus according to claim 17, further comprising an identifier replacement module for when the group node is selected for control and the group identifier of the group node is a specific identifier The control signal is programmed by the corresponding identifier of all the nodes in the sub-hierarchy of the group node, representing the group identifier of the group node.
The hierarchical group management apparatus according to claim 17, further comprising a node copying module, configured to generate a virtual node having an identifier of the copied node, and add the virtual node to the hierarchical group In the data, the sub-hierarchy of the specific node of the copied node and the sub-hierarchy of each upper-level group node of the specific node are added.
The hierarchical group management apparatus according to claim 17, further comprising an identifier adding module, configured to add any one of the group nodes to the group when the group node is selected The identifier of the virtual node associated with the group node, representing the corresponding identifier of the group node, is programmed into the control signal.
The hierarchical group management apparatus according to claim 27, wherein the identifier adding module finds the virtual node by checking a sub-hierarchy of the group node.
The hierarchical group management device according to claim 17, wherein the hierarchical group data includes a control category attribute of the controlled device, and the hierarchical group management device further includes a hierarchical group integration module, which is receiving When the hierarchical group data is newly added, a control category attribute node of the control category representing the newly added hierarchical group data is automatically accumulated at the uppermost node of the newly added hierarchical group data.
The hierarchical group management apparatus according to claim 29, wherein when there is an existing hierarchical group data and the control category attribute node is already present, the control category attribute node of the newly added hierarchical group data, The control category attribute nodes of the existing hierarchical group data are merged into the same node.
The hierarchical group management apparatus according to claim 17, further comprising a hierarchical group integration module, configured to: when there is already existing hierarchical group data and receive new hierarchical group data, The new hierarchical group data is added to one of the existing hierarchical group data to be under the selected node.
A controlled device, characterized in that it comprises:

a storage unit, configured to store at least one controlled device identifier;

a wireless receiving unit, configured to receive a wireless control signal including the at least one controlled identifier;

a processing control unit configured to set the at least one controlled device identifier, and identify the received wireless control signal to perform an action corresponding to the wireless control signal;

The storage unit is further configured to store a sovereign announcement representing management rights of the at least one controlled device identifier.
The controlled device according to claim 32, wherein the storage unit is further configured to store the at least one controlled device identifier after being overwritten to become an abandoned at least one controlled device identifier At least one controlled device identifier discarded.
A controlled device according to claim 32, wherein the processing control unit further comprises a rewrite control module for comparing the sovereign declaration with the at least one slave identifier only having the sovereignty The announced device was rewritten.
The controlled device according to claim 33, wherein the processing control unit further comprises an obsolete code control module for comparing the discarded at least one controlled device identifier with the discarded at least one The slave identifier cannot be written again as the new at least one slave identifier.