Equipment identifier construction system and method based on physical space relationship

Abstract

The invention provides an equipment identifier construction system and method based on a physical space relationship, and the system comprises a plurality of Internet of Things equipment and equipment management modules which respectively correspond to a plurality of physical space levels which are refined step by step, and each equipment management module is in communication connection with the Internet of Things equipment located in the corresponding physical space level; the equipment management module is used for distributing a first equipment identifier for the Internet of Things equipment, so that the Internet of Things equipment obtains a second equipment identifier based on a first module identifier corresponding to the equipment management module, a second module identifier corresponding to a superior equipment management module of the equipment management module and the first equipment identifier; and other Internet of Things equipment in communication connection with the equipment management module accesses the Internet of Things equipment based on the second equipment identifier. The identification system of the Internet equipment is established on the basis of the hierarchical relationship of the physical space, so that the trusted network communication requirement based on the physical space is met, and the security of communication between the Internet of Things equipment is improved.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) technology, and in particular to a device identification construction system and method based on physical spatial relationships. Background Technology

[0002] With the development of intelligent technology, more and more IoT devices are being deployed in various physical spaces, such as smart homes, smart buildings, smart office environments, etc. In fact, various physical environments have natural hierarchical relationships. For example, a community contains multiple residential buildings, each residential building has multiple floors, each floor contains multiple households, and each household contains multiple rooms.

[0003] Currently, IoT devices deployed to a node in these physical spaces typically use communication protocols from the Internet era, such as TCP / IP. Such protocols do not accurately reflect the hierarchical relationships of physical spaces and cannot establish a reliable communication mechanism between IoT devices based on the hierarchical distribution of physical spaces. Summary of the Invention

[0004] This invention provides a device identification construction system and method based on physical space relationships, which solves the defect in the prior art that the Internet of Things (IoT) devices cannot establish a trusted communication mechanism based on the hierarchical distribution of physical space. It realizes the need for trusted network communication based on physical space and improves the security of communication between IoT devices.

[0005] The present invention provides a device identification construction system based on physical space relationship, comprising: a plurality of Internet of Things (IoT) devices, and a device management module corresponding to a plurality of progressively refined physical space levels, wherein each of the device management modules is communicatively connected to the IoT device located in the corresponding physical space level. The device management module is used to assign a first device identifier to the IoT device, so that the IoT device obtains a second device identifier based on the first module identifier corresponding to the device management module, the second module identifier corresponding to the parent device management module of the device management module, and the first device identifier.

[0006] Other IoT devices that are communicatively connected to the device management module can access the IoT device based on the second device identifier.

[0007] According to a device identifier construction system based on physical spatial relationships provided by the present invention, the device management module is further configured to assign a third device identifier to the IoT device, so that the IoT device obtains a fourth device identifier based on the first module identifier corresponding to the device management module and the third device identifier.

[0008] Other IoT devices that are communicatively connected to the device management module can access the IoT device based on the fourth device identifier.

[0009] According to a device identifier construction system based on physical spatial relationships provided by the present invention, the device management module is specifically used to assign the first device identifier to the Internet of Things device after receiving a first device identifier request sent by the Internet of Things device to the device management module.

[0010] According to a device identifier construction system based on physical spatial relationships provided by the present invention, the device management module is specifically used to assign the third device identifier to the Internet of Things device after receiving a request for a third device identifier from the Internet of Things device to the device management module.

[0011] According to the device identifier construction system based on physical space relationship provided by the present invention, the device management modules corresponding to several progressively refined physical space levels are communicatively connected, and the first module identifier corresponding to the device management module is assigned by the superior device management module of the device management module.

[0012] According to the present invention, a device identifier construction system based on physical spatial relationships is provided. The device management module is specifically used to forward access requests from other IoT devices to the IoT device based on the second device identifier, and to forward the return results of the IoT device in response to the access requests. The other IoT devices and the IoT device perform mutual trust authentication through the device management module.

[0013] The present invention also provides a method for constructing device identifiers based on physical spatial relationships, comprising the following steps.

[0014] The device management module is invoked to assign a first device identifier to the IoT device, so that the IoT device obtains a second device identifier based on the first module identifier corresponding to the device management module, the second module identifier corresponding to the parent device management module of the device management module, and the first device identifier.

[0015] This enables other IoT devices that are communicatively connected to the device management module to access the IoT device based on the second device identifier; The device management module corresponds to a preset physical space hierarchy, and the device management module is communicatively connected to the IoT device located in the preset physical space hierarchy.

[0016] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the device identifier construction method based on physical spatial relationship as described above.

[0017] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the device identifier construction method based on physical spatial relationships as described above.

[0018] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the device identifier construction method based on physical spatial relationships as described above.

[0019] The device identifier construction system and method based on physical space relationships provided by this invention assigns a first device identifier to IoT devices through a device management module. This allows IoT devices to obtain a second device identifier based on the first module identifier corresponding to the device management module, the second module identifier corresponding to the upper-level device management module, and the first device identifier. Other IoT devices communicating with the device management module access the IoT devices based on the second device identifier. Since each device management module corresponds to several progressively refined physical space levels, and each device management module communicates with IoT devices located in its corresponding physical space level, the second device identifier simultaneously includes IoT device information and physical space level information. Therefore, it establishes an identification system for Internet devices based on the hierarchical relationship of physical space, fulfilling the need for trusted network communication based on physical space and improving the security of communication between IoT devices. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced one by one below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0021] Figure 1 This is a schematic diagram of the device identification construction system based on physical spatial relationships provided by the present invention.

[0022] Figure 2 This is a schematic diagram of the logical structure of the physical space hierarchy provided by the present invention.

[0023] Figure 3 This is a schematic diagram of the allocation process for the first device identifier provided by the present invention.

[0024] Figure 4 This is a schematic diagram of the communication process between IoT devices provided by the present invention.

[0025] Figure 5 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0027] Figure 1 This is a schematic diagram of the device identification construction system based on physical spatial relationships provided by the present invention. For example... Figure 1 As shown, the system includes several IoT devices 101 and several device management modules 102 corresponding to several progressively refined physical space levels. Each device management module 102 is communicatively connected to the IoT devices 101 located in the corresponding physical space level.

[0028] The device management module 102 is used to assign a first device identifier to the IoT device 101, so that the IoT device 101 obtains a second device identifier based on the first module identifier corresponding to the device management module 102, the second module identifier corresponding to the upper-level device management module of the device management module 102, and the first device identifier, and enables other IoT devices that are communicatively connected to the device management module 102 to access the IoT device 101 based on the second device identifier.

[0029] In some embodiments, see Figure 2 , Figure 2 This is a schematic diagram of the logical structure of the physical space hierarchy provided by the present invention, such as... Figure 2 As shown, Figure 2 The diagram illustrates the connection between IoT devices and device management modules in two levels of physical space.

[0030] For example, physical space 1 can be compared to a higher-level physical space, such as a family or a province, while physical space 1.1 can be compared to a lower-level physical space, such as a room in the family or a prefecture-level city in the province.

[0031] There are several IoT devices at each level of the physical space, for example... Figure 2Devices D1, D2, and Dn shown in the diagram all belong to the IoT devices at physical space level 1; devices D1.1, D1.2, and D1.n all belong to the IoT devices at physical space level 1.1. Furthermore, a device management module is deployed at each level of the physical space, for example... Figure 2 The device management module shown is the device management module at the physical space 1 level, which is used to manage IoT devices such as device D1, device D2, and device Dn located at this level; Figure 2 The Device Management 1.1 shown is the device management module for the Physical Space 1.1 level, which is used to manage IoT devices located at this level, such as Device D1.1, Device D1.2, and Device D1.n.

[0032] It should be noted that each level of the device management module provides power and data communication capabilities to the IoT devices at that level through bus or star-shaped wires (such as power line carrier technology). When the IoT device's wires are inserted into the socket in the physical space of that level, the IoT device can obtain power supply and data communication capabilities with the device management module at that level.

[0033] In this embodiment of the invention, by establishing a management system for Internet devices based on the hierarchical relationship of physical space, it is convenient to manage and communicate Internet of Things (IoT) devices based on the physical space hierarchy, thereby improving the efficiency of IoT device management and communication.

[0034] In some embodiments, the device management module is specifically configured to assign a first device identifier to the IoT device after receiving a first device identifier request sent by the IoT device to the device management module.

[0035] When the wire of an IoT device is inserted into a socket in the physical space of this level, the device management module of this level assigns a first device identifier to the IoT device, namely the OpenID of the IoT device. Within the scope of the device management module of this level, the OpenID is used to distinguish different IoT devices.

[0036] See Figure 3 , Figure 3 This is a schematic diagram of the allocation process for the first device identifier provided by the present invention, as shown below. Figure 3As shown, when an IoT device is inserted into the socket corresponding to a certain level of physical space, the IoT device actively broadcasts a message requesting an OpenID from the local device management module. Upon receiving the request message, the local device management module assigns an OpenID to the IoT device according to a preset allocation principle and returns it to the IoT device. For example, it calculates the hash value of the IoT device's User Identification (UID) to obtain the OpenID assigned to the IoT device. Since the UID of an IoT device is unique, the OpenID assigned to the IoT device by the device management module is also unique.

[0037] It should be noted that if the IoT device is not intelligent and cannot actively send broadcast messages, the local device management module will actively read the UID from the IoT device and then assign it an OpenID according to the above allocation rules.

[0038] In this embodiment of the invention, the device management module sends a first device identifier to the IoT device, which facilitates the management of IoT devices at the same level through the device management module, thereby improving the communication efficiency between IoT devices and the management efficiency of IoT devices.

[0039] In some embodiments, the device management modules corresponding to several progressively refined physical space levels are interconnected, and the first module identifier corresponding to the device management module is assigned by the superior device management module of the device management module.

[0040] Specifically, when a lower-level device management module's wire is inserted into the socket corresponding to a higher-level device management module, the higher-level module assigns a first module identifier, i.e., the OpenID, to that module. The allocation rule is similar to the OpenID allocation rule for IoT devices described above: obtain the UID of the inserted device management module, then calculate the hash value of that UID to obtain the OpenID assigned to that module. When a device management module has no higher-level module, it is considered the top-level module, and its default first module identifier, i.e., the OpenID, is a special value.

[0041] For example, suppose Figure 2 The device management module 1 shown is the top-level device management module. Its default first module identifier is a preset special value, such as 0. When the wire of the device management module 1.1 is inserted into the socket of device management 1, device management 1 will assign an OpenID to device management 1.1 according to the OpenID allocation rules mentioned above, such as 1.1.

[0042] In this embodiment of the invention, the upper-level device management module sends a first module identifier to the lower-level device management module, which facilitates the management of the lower-level device management module and IoT devices by the device management module, thereby improving the communication efficiency between IoT devices and the management efficiency of IoT devices.

[0043] In some embodiments, after assigning a first device identifier to an IoT device connected to the device management module, a second device identifier, namely the ShareID of the IoT device, can be obtained based on the first module identifier of the device management module at that level, the second module identifier corresponding to the device management module above the device management module at that level, and the first device identifier of the IoT device. The ShareID is used for addressing other IoT devices outside the same level.

[0044] In some embodiments, the device management module is further configured to assign a third device identifier to the IoT device, so that the IoT device obtains a fourth device identifier based on the first module identifier and the third device identifier corresponding to the device management module, and enables other IoT devices that communicate with the device management module to access the IoT device based on the fourth device identifier.

[0045] Specifically, when a device management module is located at the top level of the physical space, it assigns a third device identifier (i.e., the IoT device's OpenID) to the IoT devices plugged into sockets at that level. The IoT devices then obtain a fourth device identifier, the ShareID, based on the first module identifier and the third device identifier corresponding to the top-level device management module. Since the top-level device management module does not have a superior device management module assigning it an OpenID, and its OpenID is a preset value, the IoT devices at that level only need the OpenID of the top-level device management module and their own OpenID to form their fourth device identifier, the ShareID.

[0046] For example, in Figure 2 In this context, physical space 1 is the top-level physical space, and the corresponding device management 1 is the top-level device management module. For IoT devices such as device D1, device D2, and device Dn located in this physical space, only the OpenID assigned by device management 1 and the OpenID of device management 1 itself are needed to combine and generate the fourth device identifier of the IoT device, namely the ShareID of the IoT device.

[0047] In the above embodiments, the device management module is specifically used to assign a third device identifier to the IoT device after receiving a request for a third device identifier from the IoT device.

[0048] Specifically, when an IoT device is plugged into the socket corresponding to the top-level physical space, the IoT device proactively broadcasts a message requesting an OpenID from its local device management module. Upon receiving the request, the local device management module assigns an OpenID to the IoT device according to a preset allocation principle and returns it to the IoT device. For example, it calculates the hash value of the IoT device's UID to obtain the assigned OpenID. The returned result includes the assigned OpenID for the IoT device and the local device management module's ShareID. This ShareID is an absolute address, obtained by combining the OpenIDs of all its parent device management modules.

[0049] Specifically, see Table 1 below, which shows examples of OpenID and ShareID for each level of device management module and IoT device in a three-level physical space.

[0050] Table 1. Examples of Device Identifiers in Level 3 Physical Space

[0051] As shown in Table 1 above, a device management module is deployed at each level of the physical space. The OpenID of the device management module is a relative value, which is assigned by its parent device management module. Here, it is assumed that the OpenID of the device management module corresponding to the three levels of physical space is 1.

[0052] Assuming that an IoT device is deployed in each level of physical space, the OpenID of the IoT device is assigned by the device management module at the same level. The OpenID of the IoT device is also a relative value. Here, we assume that each IoT device is assigned an OpenID of 2.

[0053] In the example above, the physical space numbered 1 is the top level. Assuming this level represents a residential building, its device management module's ShareID is 1 (the ShareID of a device management module is a combination of the OpenID of the upper-level device management module and the OpenID of the current-level device management module; if it is the top-level device management module, then its ShareID is its own OpenID). In the next level, the physical space numbered 1.1, assuming this level represents a household on this floor, its device management module's ShareID is composed of the OpenIDs of two levels of device management modules, namely, the OpenID value "1" of the upper-level (physical space numbered 1) device management module and the OpenID value "1" of the current level (physical space numbered 1.1) device management module. Therefore, the ShareID value of this level's device management module is 1.1. Similarly, for physical space number 1.1.1, the ShareID of its device management module is composed of the OpenID of the three levels of device management modules. That is, it is composed of the OpenID value "1" of the device management module corresponding to level 1 of physical space, the OpenID value "1" of the device management module corresponding to level 1.1 of physical space, and the OpenID "1" of the device management module at this level. Therefore, the ShareID value of the device management module corresponding to this level is 1.1.1.

[0054] An IoT device is deployed in physical space number 1. Its OpenID is assigned by the local device management module. Assuming the OpenID value is 2, its ShareID contains two parts: the OpenID "1" of the local (physical space number 1) device management module and the OpenID "2" of the IoT device. The combined ShareID value is 1.2. Similarly, an IoT device deployed in physical space number 1.1, assuming its OpenID value is also 2, has a ShareID containing three parts: the OpenID "1" of the local (physical space number 1) device management module, the OpenID "1" of the higher-level (physical space number 1) device management module, and the OpenID "2" of the IoT device. The combined ShareID is 1.1.2. An IoT device deployed in physical space number 1.1.1, assuming its OpenID value is also 2, has a ShareID consisting of four parts: the OpenID "1" of the device management module at this level (physical space number 1.1.1), the OpenID "1" of the device management module at the next higher level (physical space level number 1.1), the OpenID "1" of the device management modules at the two levels above (physical space level number 1), and the OpenID "2" of the IoT device. The combined ShareID is 1.1.1.2.

[0055] In some embodiments, refer to Table 2 below, which is a device identifier design table for a multi-level physical space. The table below shows an example of OpenID for the device management module of a multi-level physical space.

[0056] Table 2. Design Table of Device Identifiers for Multi-level Physical Spaces

[0057] Globally, there is a complete physical space from top to bottom. For a complete physical space, a corresponding hierarchy needs to be designed. IoT devices can then achieve mutual trust access based on authentication through the device management module. An example of the hierarchy design is shown in Table 2 above. Each level has a device management module deployed to assign OpenIDs to IoT devices at that level and to the device management modules at the next level.

[0058] In the example above, the address (i.e., ShareID) of an IoT device can be represented in two ways. One is a relative address, which takes the device management module of the layer into which the IoT device is inserted as the starting point, and connects the OpenID of the device management module of that layer with the OpenID assigned to the IoT device. This is the externally visible ShareID.

[0059] Taking Level 4 (Nanshan District) as an example, the OpenID of the device management module deployed at this level is 2. An IoT device is inserted into Level 5 (XX Community) managed by this module. This IoT device is assigned an OpenID of 124, so the relative address ShareID of this inserted IoT device is 2.124. Taking Level 7 (20 floors) as an example, the OpenID of the device management module deployed at this level is 22. An IoT device is inserted into Level 8 (Household 2001) managed by this module. This IoT device is assigned an OpenID of 36, so the relative address ShareID of this inserted IoT device is 22.36.

[0060] Another method is the absolute address, which starts from the root address (located at the first-level national level), and combines the OpenIDs of the device management modules at each level in sequence until the level corresponding to the IoT device, and then combines it with the OpenID of the IoT device to form the absolute address ShareID.

[0061] Continuing with the example of Level 4, Nanshan District, the device management module deployed at this level has an OpenID of 2. An IoT device is inserted into Level 5 (XX Community) under its management. This IoT device is assigned an OpenID of 124, and its absolute address ShareID is 1.12.33.2.124. Taking Level 7, 20-story building as an example, the device management module deployed at this level has an OpenID of 22. An IoT device is inserted into Level 8 (Household 2001) under its management. This IoT device is assigned an OpenID of 36, and its absolute address ShareID is 1.12.33.2.123.12.22.36.

[0062] In this embodiment of the invention, by establishing an identification system for Internet devices based on the hierarchical relationship of physical space, the need for trusted network communication based on physical space is realized, and the security of communication between Internet of Things devices is improved.

[0063] In some embodiments, the device management module is specifically used to forward access requests from other IoT devices to the IoT device based on the second device identifier, and to forward the return results of the IoT device in response to the access requests, wherein other IoT devices perform mutual trust authentication with the IoT device through the device management module.

[0064] Specifically, see Figure 4 , Figure 4This is a schematic diagram of the communication process between IoT devices provided by this invention. IoT device A can access IoT device B only if both devices have been assigned an OpenID by the same device management module. This establishes a trusted authentication between the two IoT devices, and each IoT device has stored its own OpenID and ShareID absolute addresses. Typical scenarios include: IoT device A has previously been plugged into a socket at the same level as IoT device B, automatically obtaining mutual trust authentication; or IoT device A has stored the ShareID absolute address of the device management module at the same level as IoT device B; or IoT device A has installed the control program for IoT device B and used the program at the same level as IoT device B (this allows IoT device A to address IoT device B). IoT device A cannot directly access IoT device B; instead, it must access it through the device management module at the same level as IoT device B, and IoT device A uses the ShareID absolute address of IoT device B to identify the destination address.

[0065] like Figure 4 As shown, IoT device A starts from the root address and calls the device management modules level by level until it reaches the device management module of the level where IoT device B is located. The device management module of the level where IoT device B is located then dispatches the control request issued by IoT device A to device B. In a preferred solution, it is possible to first determine which level the socket currently inserted by IoT device A belongs to, and then select the nearest target address, thus avoiding addressing from the root address and improving addressing efficiency. For example, suppose IoT device A is currently inserted into a socket in the "Shenzhen" physical level, while the physical level where IoT device B is located is XX community under Nanshan District. Then, the request of IoT device A can be directly sent to the device management module corresponding to the "Shenzhen" physical space level. The device management module of the "Shenzhen" physical space level automatically intercepts the ShareID starting from Nanshan District, and continues until it reaches the device management module corresponding to the physical space level where IoT device B is located.

[0066] Then, the device management module at the level where IoT device B resides sends the control command from IoT device A to the device management module at the physical space level where IoT device B resides. The device management module at the physical space level of IoT device B performs a trusted verification of the request from IoT device A. In practice, this can be achieved through mutual authentication using asymmetric keys. Based on this, it verifies whether the OpenID of IoT device A was assigned by the device management module at the physical space level of IoT device B. If IoT device A passes the verification, it forwards the request to IoT device B. IoT device B then executes the control command and returns the result of the command execution to device A through the device management module at the physical space level of IoT device B.

[0067] In this embodiment of the invention, since the device management module corresponds to several progressively refined physical space levels, and each device management module communicates with IoT devices located in the corresponding physical space level, the ShareID of the IoT device includes both IoT device information and physical space level information. Thus, an identification system for Internet devices is established based on the hierarchical relationship of physical space, enabling addressing and mutual calling of networked devices. This overcomes the drawback of neglecting the binding of physical space and IoT devices in previous Internet models, and improves the efficiency and security of communication between IoT devices.

[0068] The following describes a device identifier construction method based on physical spatial relationships provided by the present invention. The device identifier construction method based on physical spatial relationships described below can be referred to in correspondence with the device identifier construction system based on physical spatial relationships described above.

[0069] The device management module is invoked to assign a first device identifier to the IoT device, so that the IoT device obtains a second device identifier based on the first module identifier corresponding to the device management module, the second module identifier corresponding to the upper-level device management module of the device management module, and the first device identifier, and enables other IoT devices that communicate with the device management module to access the IoT device based on the second device identifier; wherein, the device management module corresponds to a preset physical space hierarchy, and the device management module communicates with the IoT devices located in the preset physical space hierarchy.

[0070] Specifically, the device identifier construction method based on physical spatial relationship provided by the present invention can realize all the operations implemented in the above-mentioned device identifier construction system embodiment based on physical spatial relationship, and can achieve the same technical effect. Here, the parts that are the same as those in the system embodiment and the beneficial effects will not be described in detail.

[0071] Figure 5 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 5As shown, the electronic device may include: a processor 510, a communications interface 520, a memory 530, and a communication bus 540, wherein the processor 510, the communications interface 520, and the memory 530 communicate with each other through the communication bus 540. The processor 510 can call logical instructions in the memory 530 to execute a device identifier construction method based on physical space relationships. This method includes: calling a device management module to assign a first device identifier to an IoT device, so that the IoT device obtains a second device identifier based on the first module identifier corresponding to the device management module, the second module identifier corresponding to the upper-level device management module of the device management module, and the first device identifier; and enabling other IoT devices communicatively connected to the device management module to access the IoT device based on the second device identifier; wherein the device management module corresponds to a preset physical space hierarchy, and the device management module is communicatively connected to the IoT devices located in the preset physical space hierarchy.

[0072] Furthermore, the logical instructions in the aforementioned memory 530 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0073] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the device identifier construction method based on physical space relationship provided by the above methods. The method includes: calling a device management module to assign a first device identifier to an IoT device, so that the IoT device obtains a second device identifier based on the first module identifier corresponding to the device management module, the second module identifier corresponding to the upper-level device management module of the device management module, and the first device identifier, and enabling other IoT devices communicatively connected to the device management module to access the IoT device based on the second device identifier; wherein, the device management module corresponds to a preset physical space hierarchy, and the device management module is communicatively connected to the IoT device located in the preset physical space hierarchy.

[0074] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements a device identifier construction method based on physical space relationships provided by the above methods. The method includes: calling a device management module to assign a first device identifier to an IoT device, so that the IoT device obtains a second device identifier based on the first module identifier corresponding to the device management module, the second module identifier corresponding to the upper-level device management module of the device management module, and the first device identifier; and enabling other IoT devices communicatively connected to the device management module to access the IoT device based on the second device identifier; wherein the device management module corresponds to a preset physical space hierarchy, and the device management module is communicatively connected to the IoT devices located in the preset physical space hierarchy.

[0075] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0076] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0077] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A device identification construction system based on physical spatial relationships, characterized in that, include: A plurality of Internet of Things (IoT) devices, and a plurality of device management modules corresponding to a plurality of progressively refined physical space levels, wherein each of the device management modules is communicatively connected to the IoT devices located in the corresponding physical space level. The device management module is used to assign a first device identifier to the IoT device, so that the IoT device obtains a second device identifier based on the first module identifier corresponding to the device management module, the second module identifier corresponding to the parent device management module of the device management module, and the first device identifier. Other IoT devices that are communicatively connected to the device management module can access the IoT device based on the second device identifier.

2. The device identification construction system based on physical spatial relationships according to claim 1, characterized in that, The device management module is further configured to assign a third device identifier to the IoT device, so that the IoT device obtains a fourth device identifier based on the first module identifier corresponding to the device management module and the third device identifier. Other IoT devices that are communicatively connected to the device management module can access the IoT device based on the fourth device identifier.

3. The device identification construction system based on physical spatial relationships according to claim 1, characterized in that, The device management module is specifically used to assign the first device identifier to the IoT device after receiving a first device identifier request sent by the IoT device to the device management module.

4. The device identification construction system based on physical spatial relationships according to claim 2, characterized in that, The device management module is specifically used to assign the third device identifier to the IoT device after receiving a request for a third device identifier from the IoT device.

5. The device identification construction system based on physical spatial relationships according to claim 1, characterized in that, The communication connection is between the device management modules corresponding to several progressively refined physical space levels, and the first module identifier corresponding to the device management module is assigned by the superior device management module of the device management module.

6. The device identification construction system based on physical spatial relationships according to claim 1, characterized in that, The device management module is specifically used to forward access requests from other IoT devices to the IoT device based on the second device identifier, and to forward the return results from the IoT device in response to the access requests. The other IoT devices and the IoT device perform mutual trust authentication through the device management module.

7. A method for constructing device identifiers based on physical spatial relationships, characterized in that, include: The device management module is invoked to assign a first device identifier to the IoT device, so that the IoT device obtains a second device identifier based on the first module identifier corresponding to the device management module, the second module identifier corresponding to the parent device management module of the device management module, and the first device identifier. This enables other IoT devices that are communicatively connected to the device management module to access the IoT device based on the second device identifier; The device management module corresponds to a preset physical space hierarchy, and the device management module is communicatively connected to the IoT device located in the preset physical space hierarchy.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the device identifier construction method based on physical spatial relationships as described in claim 7.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the device identifier construction method based on physical spatial relationships as described in claim 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the device identifier construction method based on physical spatial relationships as described in claim 7.

Images