Building Intelligent IoT Control Methods and Gateways

By generating target authorization identifiers and files, the problem of software version incompatibility in the smart gateway system is resolved, maintenance costs are reduced, and data security is improved.

CN117040807BActive Publication Date: 2026-11-17BEIJING INST OF ARCHITECTURAL DESIGN +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310888476.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-07-19
Publication Date
2026-11-17
Estimated Expiration
2043-07-19

AI Technical Summary

Technical Problem

Existing smart gateway systems suffer from high maintenance costs due to version incompatibility during the software porting phase.

Method used

By obtaining the identity identifier of the gateway itself, and using the pre-defined correspondence between identifier data, software version data, and authorization time limit data, a target authorization identifier is generated, and a target authorization file is generated after successful key verification, thus avoiding incompatibility between software version and system version.

Benefits of technology

It reduces maintenance costs, avoids the need for software recompilation, and improves data security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117040807B_ABST
    Figure CN117040807B_ABST
Patent Text Reader

Abstract

This invention provides a building intelligent IoT control method and gateway, relating to the field of intelligent gateway technology. The building intelligent IoT control method includes: obtaining the gateway's identity identifier; determining the software version information and authorization validity information corresponding to the identity identifier based on a preset correspondence between identifier data, software version data, and authorization validity information; and obtaining a target authorization identifier for generating a target authorization file based on preset authorization identifier generation rules, preset verification information, and the corresponding identity identifier, software version information, and authorization validity information. Through the embodiments provided in this application, the offline authorization method avoids the problem of incompatibility between software versions and the gateway's system version, eliminating the need for re-cross-compiling ported software as in existing technologies, thereby reducing maintenance costs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of smart gateway technology, and in particular to a building intelligent Internet of Things control method and gateway. Background Technology

[0002] A smart gateway is a network device and a key component of a local area network (LAN) for intelligent operation. It typically supports virtual network access, Wi-Fi access, wired broadband access, and other functions. Through it, it can collect, input, output, centrally control, remotely control, and coordinate the control of various sensors, network devices, cameras, and hosts within the LAN.

[0003] In existing products, executable files are deployed on the smart gateway's system platform. However, incompatibility issues exist between the smart gateway system version and the software version. Typically, during the software porting phase, the software to be ported is recompiled to avoid software and system incompatibility. However, recompilation increases maintenance costs, resulting in higher maintenance costs. Summary of the Invention

[0004] This application addresses the shortcomings of existing methods by providing a building intelligent IoT control method and gateway. This method solves the technical problem of high maintenance costs caused by recompiling the ported software due to the incompatibility between software and system versions during the software porting phase.

[0005] In a first aspect, embodiments of this application provide a building intelligent Internet of Things control method applied to a host computer. The method includes: obtaining the identity identifier of the gateway body; determining the software version information and authorization validity information corresponding to the identity identifier based on a preset correspondence between identifier data, software version data, and authorization validity information; and obtaining a target authorization identifier for generating a target authorization file based on preset authorization identifier generation rules, preset verification information, and the corresponding identity identifier, software version information, and authorization validity information.

[0006] As an optional implementation, obtaining the target authorization identifier for generating the target authorization file based on the preset authorization identifier generation rules, preset verification information, and the corresponding identity identifier, software version information, and authorization validity information includes: concatenating concatenated data according to the preset concatenation order, the identity identifier, the software version information, and the authorization validity information; and encrypting the concatenated data to obtain encrypted data.

[0007] The encrypted data and the information to be verified are concatenated and encrypted to obtain the target authorization identifier.

[0008] As an optional implementation, the splicing order includes: the authorization validity information, the software version information, and the identity identifier are spliced ​​together in sequence.

[0009] Secondly, embodiments of this application provide a building intelligent Internet of Things control method applied to a gateway body. The method includes: obtaining a target authorization identifier provided by a host computer; the target authorization identifier includes preset verification information, as well as the corresponding identity identifier, software version information, and authorization validity information of the gateway body; verifying the target authorization identifier; and, if the verification is successful, obtaining a target authorization file according to the target authorization identifier and preset authorization file generation rules.

[0010] As an optional implementation, the method further includes: receiving an authorization verification signal; determining whether a target authorization file exists in a preset authorization file database based on the response to the authorization verification signal; and outputting the identity identifier of the gateway entity if it is determined that the target authorization file does not exist.

[0011] As an optional implementation, verifying the target authorization identifier includes: decrypting the target authorization identifier to obtain encrypted data and the information to be verified; the encrypted data includes the corresponding identity identifier, the software version information, and the authorization validity information; and verifying the information to be verified according to preset verification rules and preset verification information.

[0012] As an optional implementation, obtaining the target authorization file according to the target authorization identifier and the preset authorization file generation rules includes: writing the target authorization identifier into the generated authorization file to obtain the target authorization file.

[0013] As an optional implementation, the method further includes: outputting the identity identifier of the gateway entity in the event of verification failure.

[0014] As an optional implementation, the identity identifier includes a MAC address and a unique chip identifier.

[0015] Thirdly, this application provides a building intelligent IoT control gateway, comprising: a host computer for executing the building intelligent IoT control method described in any of the foregoing embodiments; and a gateway body for executing the building intelligent IoT control method described in any of the foregoing embodiments.

[0016] This application provides a building intelligent Internet of Things (IoT) control method and gateway. The technical solution provided by the embodiments of this application brings at least the following beneficial effects:

[0017] For both the host computer and the gateway body that are offline, a target authorization identifier is obtained by using preset authorization identifier generation rules, preset verification information, and corresponding identity identifiers, software version information, and authorization validity information. This target authorization identifier is used to generate a target authorization file after successful key verification, in accordance with preset authorization file generation rules. This target authorization file is used to obtain authorization for the specified software version on the software on the gateway body corresponding to the identity identifier. This avoids the problem of incompatibility between the software version and the gateway body system version, eliminates the work of re-cross-compiling the ported software in the prior art, and thus reduces maintenance costs.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0019] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0020] Figure 1 A flowchart illustrating a building intelligent Internet of Things control method provided in an embodiment of this application;

[0021] Figure 2 This application provides a schematic diagram of the specific steps in a building intelligent IoT control method to obtain a target authorization identifier for generating a target authorization file based on preset generation rules, preset verification information, and corresponding identity identifiers, software version information, and authorization validity information.

[0022] Figure 3 A flowchart illustrating another intelligent building IoT control method provided in this application embodiment;

[0023] Figure 4 A flowchart illustrating another intelligent building IoT control method provided in this application embodiment;

[0024] Figure 5 A schematic diagram illustrating the specific steps of verifying a target authorization identifier in a building intelligent IoT control method provided in this application embodiment;

[0025] Figure 6 This is a schematic diagram of the framework structure of a building intelligent Internet of Things control gateway provided in an embodiment of this application.

[0026] Figure labels and corresponding explanations:

[0027] 1: Host computer;

[0028] 2: Gateway itself. Detailed Implementation

[0029] This application is described in detail below. Examples of embodiments of this application are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar components or components having the same or similar functions throughout. Furthermore, detailed descriptions of known technologies that are unnecessary for the features of this application are omitted. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.

[0030] Those skilled in the art will understand that, unless otherwise stated, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the word “comprising” as used in this application’s specification means the presence of the stated features, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0031] Figure 1 This is a flowchart illustrating a building intelligent IoT control method provided in an embodiment of this application. Figure 1 As shown, this application provides a building intelligent Internet of Things control method, which is applied to a host computer 1. The method mainly includes steps S110-S130:

[0032] Step S110: Obtain the identity identifier of gateway body 2.

[0033] Step S120: Based on the preset correspondence between identifier data, software version data, and authorization time limit data, determine the software version information and authorization time limit information corresponding to the identity identifier.

[0034] Step S130: Based on the preset authorization identifier generation rules, the preset verification information, and the corresponding identity identifier, software version information, and authorization validity information, obtain the target authorization identifier used to generate the target authorization file.

[0035] In this embodiment, host computer 1 refers to a computer device that can directly issue control commands. Host computer 1 includes at least one of smartphones, tablets, laptops, desktop computers, and wearable devices. This embodiment does not limit the specific device, but those skilled in the art can determine the appropriate device based on the actual situation.

[0036] Gateway 2 is a smart gateway. This application employs an offline authorization method, where neither gateway 2 nor host computer 1 is connected to the internet; both are offline. Host computer 1 connects to gateway 2 to facilitate information transmission between them. For example, host computer 1 can obtain the identity identifier of gateway 2, which can be read through a pre-installed application programming interface.

[0037] In some embodiments, the gateway body 2 has a display area and the host computer 1 has an operation area. The display area of ​​the gateway body 2 is used to display the identity identifier, and the user can input the displayed identity identifier into the host computer 1 through the operation area of ​​the host computer 1.

[0038] In other embodiments, both the host computer 1 and the gateway body 2 are provided with connection ports for cable connection, and the host computer 1 and the gateway body 2 can transmit information between them through the cable; both the host computer 1 and the gateway body 2 are provided with wireless connection modules, such as Bluetooth, to enable information transmission between them in a wireless connection manner; this method does not require the user to manually input the identity of the gateway body 2, and is suitable for the host computer 1 without an operating area, avoiding the leakage of identity information caused by manual input.

[0039] In this embodiment, the identity identifier of the gateway body 2 includes at least one of the following: device model, manufacturer information, MAC address, and unique chip identifier, serving as the unique identity identifier of the gateway body 2. For example, the identity identifier includes the MAC address and the unique chip identifier. The MAC (Media Access Control) address, also known as a LAN address, Ethernet address, or physical address, is an address used to identify the location of a network device. A MAC address identifies a network interface card (NIC). If a device has one or more NICs, each NIC needs and will have a unique MAC address. The unique chip identifier is a unique identifier code present in the chip; for example, most STM32 series chips have a 96-bit unique identifier code placed in a fixed location, which can serve as the unique chip identifier.

[0040] The correspondence between the identification data, software version data, and authorization time limit data in the aforementioned step S120 is a pre-defined one-to-one correspondence and is pre-stored in the data set of the host computer 1. By searching for the identity identifier within this correspondence, the specific information of the other two corresponding data can be obtained. Specifically, the identity identifier is used to identify the authorized device; this identifier can be called a machine code, used to achieve "one machine, one code" after authorization, so that even if an unauthorized device copies the software, it cannot initiate the authorization process. The software version information includes the software version name or identifier and the corresponding version number, used to determine the specified software version to be authorized. The authorization time limit information is the authorization duration or the authorization time point; the authorization time limit data is used to determine the valid duration of the authorization. If the authorization time limit expires, the software version needs to be re-authorized.

[0041] The information to be verified in step S130 is pre-agreed upon. For example, the information to be verified is a pre-agreed key, which is a parameter input into the algorithm that converts plaintext to ciphertext or vice versa. The key can be a symmetric key or an asymmetric key. The key can be pre-written into the corresponding program on host computer 1 or stored on host computer 1.

[0042] A license document serves as proof that a user has purchased specific software functionality, allowing the user to use a particular software or product. In practice, certain versions of software typically come pre-installed with an evaluation version or a temporary license document. After a period of trial use, a full version license document is usually required to continue using the different features of the software. The target license document in step S130 above is the license document for the specified software version.

[0043] The building intelligent IoT control method provided in this application, for both the host computer 1 and the gateway body 2 in an offline state, obtains a target authorization identifier through preset authorization identifier generation rules, preset verification information, and corresponding identity identifier, software version information, and authorization validity information. This target authorization identifier is used to generate a target authorization file after successful key verification, in conjunction with preset authorization file generation rules. This target authorization file is used to obtain authorization for the specified software version on the software on the gateway body 2 corresponding to the identity identifier, avoiding the problem of incompatibility between the software version and the system version of the gateway body 2, eliminating the work of re-cross-compiling the ported software in the prior art, and thus reducing maintenance costs.

[0044] Figure 2 This document illustrates the detailed steps in step 130 of a building intelligent IoT control method provided in this application, where a target authorization identifier is obtained for generating a target authorization file based on preset generation rules, preset verification information, and corresponding identity identifiers, software version information, and authorization validity information. (See attached flowchart for details.) Figure 2 As shown, in an optional implementation, step S130 above obtains the target authorization identifier for generating the target authorization file based on preset generation rules, preset verification information, and corresponding identity identifiers, software version information, and authorization validity information. This mainly includes steps S131-S133:

[0045] Step S131: Based on the preset splicing order, identity identifier, software version information and authorization validity information, splice the spliced ​​data.

[0046] Step S132: Encrypt and concatenate the data to obtain encrypted data.

[0047] Step S133: Concatenate the encrypted data and the information to be verified, and encrypt them to obtain the authorization identifier.

[0048] The pre-set splicing order in the aforementioned step S131 corresponds to the subsequent parsing order. If the splicing order and the parsing order do not correspond, the required information cannot be parsed and the target authorization file cannot be generated.

[0049] In step S133 above, the encrypted data is concatenated first, followed by the information to be verified; or the information to be verified is concatenated first, followed by the encrypted data.

[0050] The encryption in steps S131, S132, and S136 above uses existing encryption algorithms, such as at least one of MD5, SHA1, and SHA256. MD5, SHA1, and SHA256 are all known as hash algorithms, characterized by input of any length, fixed output length, and one-wayness (the message cannot be reconstructed from the hash value). The encryption algorithm used can be preset. The preset information to be verified, along with the corresponding identity identifier, software version information, and authorization validity information, all constitute the signature information. In the technical solution of this embodiment, the target authorization identifier generation process uses a preset concatenation order and encryption algorithm, making the target authorization identifier difficult to crack and improving data security.

[0051] As an optional implementation, the splicing order in the preceding step S131 includes: sequentially splicing the authorization validity information, software version information, and identity identifier.

[0052] Depending on the concatenation order, in some embodiments, the authorization validity period information, identity identifier, and software version information are concatenated sequentially. In other embodiments, the identity identifier, authorization validity period information, and software version information are concatenated sequentially. In still other embodiments, the identity identifier, software version information, and authorization validity period information are concatenated sequentially. In yet another embodiment, the software version information, authorization validity period information, and identity identifier are concatenated sequentially.

[0053] In one specific embodiment, the key, corresponding identity identifier, software version information, and authorization validity period information correspond to: 3400tur34788812jfuw, 00-2B-67-3C-9D-9F, v00, and 2099-01-01, respectively. These are concatenated in the order of authorization validity period information, software version information, and identity identifier to form a string. This string is then encrypted using the SHA1 algorithm, and the encrypted result is concatenated with the key. Finally, it is encrypted using the MD5 algorithm to form the target authorization identifier.

[0054] Figure 3 This is a flowchart illustrating another intelligent building IoT control method provided in an embodiment of this application. Figure 3 As shown, based on the same inventive concept, this application provides a building intelligent Internet of Things control method, which is applied to the gateway body 2. The method mainly includes steps S210-S230:

[0055] Step S210: Obtain the target authorization identifier provided by the host computer 1.

[0056] Step S220: Verify the target authorization identifier.

[0057] Step S230: If the verification is successful, obtain the target license file according to the target license identifier and the preset license file generation rules.

[0058] The building intelligent IoT control method in this embodiment works in conjunction with the building intelligent IoT control method in the previous embodiments. The specific details of the gateway body 2 have been described in the previous embodiments and will not be repeated here.

[0059] The target authorization identifier in step 210 mentioned above includes preset verification information, as well as the corresponding identity identifier, software version information, and authorization validity information of the gateway entity 2. It should be noted that the target authorization identifier can be a target authorization identifier generated by the host computer 1 or a target authorization identifier forwarded by the host computer 1. The method of provision includes display or transmission.

[0060] As an optional implementation, the identity identifier includes a MAC address and a unique chip identifier.

[0061] In step 220 above, the verification method is preset and corresponds to the generation method of the target authorization identifier. For example, if the target authorization identifier is encrypted data, then the verification method of the target authorization identifier is decryption verification.

[0062] If the verification is successful in step 230 above, it means that the authorization identifier corresponds to the gateway body 2, that is, the authorization identifier includes the identity identifier of the gateway body 2.

[0063] The building intelligent IoT control method provided in this application, for both the host computer 1 and the gateway body 2 which are in an offline state, generates a target authorization file by verifying the target authorization identifier. The target authorization file is used to obtain the authorization of the specified software version for the software on the gateway body 2 corresponding to the identity identifier, avoiding the problem of incompatibility between the software version and the system version of the gateway body 2, saving the work of re-cross-compiling the ported software in the prior art, thereby reducing maintenance costs.

[0064] Figure 4 This is a flowchart illustrating another intelligent building IoT control method provided in an embodiment of this application. Figure 4As shown, as an optional implementation, the building intelligent IoT control method further includes steps S240-S250:

[0065] Step S240: Receive the authorization verification signal.

[0066] Step S250: Based on the response to the authorization verification signal, determine whether the target authorization file exists in the preset authorization file database. If the target authorization file does not exist, output the identity identifier of the gateway body 2.

[0067] The triggering mechanism for the authorization verification signal in step S240 is pre-set in gateway body 2. For example, the authorization verification signal is triggered immediately after gateway body 2 is initialized, or immediately after each power-on. The output identity of gateway body 2 is used to generate the target authorization file.

[0068] In step S250, the authorization file database can be a directory containing authorization files, or a path or folder storing authorization files. If it is determined that the target authorization file does not exist, it means that the authorization for the specified software version has not been obtained. In this case, the identity identifier of the gateway body 2 needs to be output to generate an authorization file for the specified device and the specified software version.

[0069] Figure 5 This is a schematic diagram illustrating the specific steps involved in verifying a target authorization identifier in a building intelligent IoT control method provided in this application embodiment. Figure 5 As shown, as an optional implementation, the verification of the target authorization identifier in step S220 mainly includes steps S221-S222:

[0070] Step S221: Decrypt the target authorization identifier and obtain encrypted data and information to be verified.

[0071] Step S222: Verify the information to be verified according to the preset verification rules and preset verification information.

[0072] The decryption method in step S221 is preset and is the same as the encryption method in the previous embodiment, to facilitate subsequent decryption. The encrypted data includes the corresponding identity identifier, software version information, and authorization validity information.

[0073] The information to be verified in step S222 is the key in the aforementioned embodiment. This key is divided into symmetric key and asymmetric key depending on its type. Therefore, when the key is a symmetric key, the verification information is the same as the information to be verified; when the key is an asymmetric key, the verification information and the information to be verified are a pair.

[0074] Therefore, in some embodiments, the information to be verified is verified according to preset verification rules and preset verification information, including:

[0075] If the key is a symmetric key, the verification information and the information to be verified are compared. If the comparison results are the same, the verification is successful.

[0076] In other embodiments, the information to be verified is verified according to preset verification rules and preset verification information, including:

[0077] When the key is an asymmetric key, the verification information and the information to be verified are compared. If the comparison result is a pair, the verification is successful.

[0078] As an optional implementation, the step 220 described above, which involves obtaining the target license file based on the target license identifier and preset license file generation rules, includes:

[0079] Write the target license identifier into the generated license file to obtain the target license file.

[0080] In this embodiment, an authorization file can be generated first according to preset writing rules, and then the target authorization identifier can be written into the generated authorization file.

[0081] In some embodiments, after obtaining the target authorization identifier, a target authorization file with the target authorization identifier is generated according to preset writing rules.

[0082] In other embodiments, after obtaining the target authorization identifier, the target authorization identifier is written into an existing authorization file according to a preset writing rule to form a target authorization file, and then the newly generated target authorization file overwrites the old authorization file.

[0083] As an optional implementation method, the building intelligent IoT control method also includes: outputting an identity identifier in the event of verification failure.

[0084] By adopting the above technical solution, after verification failure, an identity identifier can be output to re-execute the aforementioned steps S210-S230 to obtain the target authorization file and obtain authorization.

[0085] Figure 6 This application provides a schematic diagram of the framework structure of a building intelligent IoT control gateway, as shown in the embodiment. Figure 6 As shown, based on the same inventive concept, this application provides a building intelligent IoT control gateway, mainly including a host computer 1 and a gateway body 2. The host computer 1 is used to execute any of the building intelligent IoT control methods in the foregoing embodiments; the gateway body 2 is used to execute any of the building intelligent IoT control methods in the foregoing embodiments.

[0086] In this embodiment, the host computer 1 is equipped with a program for executing any of the building intelligent IoT control methods described in the foregoing embodiments, such as a registration key. The gateway 2 can automatically or manually control scene execution (e.g., controlling networked devices such as lights, curtains, and elevators) and collect data from the devices (e.g., data from electricity meters, temperature, humidity, location coordinates, etc.).

[0087] The software architecture of Gateway 2 adopts Docker container technology and local database, MQTT soft bus, to achieve data optimization, real-time response, agile connection and intelligent analysis at IoT edge nodes; it can significantly reduce data traffic between the field and the central end, avoid bottlenecks in cloud data access, reduce the burden of cloud data computing, optimize network architecture, and realize field business more securely, quickly and intelligently.

[0088] Docker is an open-source application container engine that allows developers to package their applications and dependencies into a portable container in a unified way, and then deploy it to any server with the Docker engine installed (including popular Linux and Windows machines), thus achieving virtualization. Containers are completely sandboxed and have no interfaces with each other (similar to iPhone apps).

[0089] Gateway 2 is equipped with a Docker container manager to manage the software running on it. Gateway 2 utilizes container technology to enable independent installation and execution of software applications. Compared to virtual machine technology, Docker containers save significant system resources. Furthermore, the containers themselves employ a sandbox mechanism, with no interfaces between them, achieving complete isolation and ensuring security. User software applications are installed using images. Gateway 2 manages the various layers of business software applications through the Docker container manager, allowing for easy deployment of these applications on different hardware platform gateways. This means that software can be installed directly, eliminating the need for cross-compilation of ported software and thus reducing maintenance costs.

[0090] By applying the embodiments of this application, at least the following beneficial effects can be achieved:

[0091] For both the host computer 1 and the gateway 2, which are both offline, a target authorization identifier is obtained through preset authorization identifier generation rules, preset verification information, and corresponding identity identifiers, software version information, and authorization validity information. This target authorization identifier is used to generate a target authorization file after successful key verification, based on preset authorization file generation rules. The target authorization file is generated by verifying the target authorization identifier. This target authorization file is used to obtain authorization for the specified software version on the software on the gateway 2 corresponding to the identity identifier. This avoids the problem of incompatibility between the software version and the system version of the gateway 2, eliminates the work of re-cross-compiling the ported software in the prior art, and thus reduces maintenance costs.

[0092] Those skilled in the art will understand that the steps, measures, and solutions in the various operations, methods, and processes discussed in this application can be alternated, modified, combined, or deleted. Furthermore, other steps, measures, and solutions in the various operations, methods, and processes discussed in this application can also be alternated, modified, rearranged, decomposed, combined, or deleted. Furthermore, steps, measures, and solutions in the prior art that are similar to those disclosed in this application can also be alternated, modified, rearranged, decomposed, combined, or deleted.

[0093] In the description of this application, it should be noted that, unless otherwise expressly specified and limited, the term "connection" should be interpreted broadly. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a direct connection or an indirect connection through an intermediate medium; it can be a connection within two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0094] In the description of this specification, specific features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments or examples.

[0095] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0096] The above description is only a partial embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A building intelligent Internet of Things (IoT) control gateway, characterized in that, include: The host computer (1) is used to obtain the identity identifier of the gateway body (2); Based on the pre-defined correspondence between identifier data, software version data, and authorization time limit data, determine the software version information and authorization time limit information corresponding to the identity identifier; based on the pre-defined authorization identifier generation rules, the pre-defined information to be verified, and the corresponding identity identifier, software version information, and authorization time limit information, obtain the target authorization identifier used to generate the target authorization file; The gateway body (2) is used to obtain the target authorization identifier provided by the host computer (1); the target authorization identifier includes preset verification information, as well as the corresponding identity identifier, software version information and authorization validity information of the gateway body (2); Verify the target authorization identifier; If the verification is successful, the target authorization file is obtained according to the target authorization identifier and the preset authorization file generation rules; Wherein, the information to be verified is a pre-agreed key; the software version information is used to determine the specified software version to be authorized; the target authorization file is an authorization file for the specified software version, and the target authorization file is used for the software on the gateway body corresponding to the identity to obtain authorization for the specified software version; The step of obtaining the target authorization identifier for generating the target authorization file based on the preset authorization identifier generation rules, preset verification information, and the corresponding identity identifier, software version information, and authorization validity information specifically includes: Based on the preset splicing order, identity identifier, software version information, and authorization validity information, spliced ​​data is obtained; the spliced ​​data is encrypted to obtain encrypted data; the encrypted data and the information to be verified are spliced ​​together and encrypted to obtain the target authorization identifier.

2. The building intelligent IoT control gateway according to claim 1, characterized in that, The splicing sequence includes: The authorization validity period information, the software version information, and the identity identifier are concatenated sequentially.

3. The building intelligent IoT control gateway according to claim 1, characterized in that, The gateway body (2) is also used to perform the following: Receive authorization verification signal; Based on the response to the authorization verification signal, it is determined whether a target authorization file exists in the preset authorization file database. If the target authorization file does not exist, the identity identifier of the gateway body (2) is output.

4. The building intelligent IoT control gateway according to claim 1, characterized in that, The verification of the target authorization identifier includes: Decrypt the target authorization identifier to obtain encrypted data and the information to be verified; the encrypted data includes the corresponding identity identifier, the software version information, and the authorization validity information; The information to be verified is verified according to preset verification rules and preset verification information.

5. The building intelligent IoT control gateway according to claim 1, characterized in that, The step of obtaining the target authorization file based on the target authorization identifier and the preset authorization file generation rules includes: Write the target authorization identifier into the generated authorization file to obtain the target authorization file.

6. The building intelligent IoT control gateway according to claim 1, characterized in that, The gateway body (2) also performs: If the verification fails, the identity identifier of the gateway body (2) is output.

7. The building intelligent IoT control gateway according to any one of claims 1-6, characterized in that, The identity identifier includes the MAC address and the chip's unique identifier.

Citation Information

Patent Citations

  • Authorization control method and device, authorization method and device and computing equipment

    CN113326482A

  • Microservice architecture software authorization management system and method

    CN114238868A