CN112636977A - Internet of things equipment management method, registration method, device and system and electronic equipment - Google Patents

Internet of things equipment management method, registration method, device and system and electronic equipment Download PDF

Info

Publication number
CN112636977A
CN112636977A CN202011542876.0A CN202011542876A CN112636977A CN 112636977 A CN112636977 A CN 112636977A CN 202011542876 A CN202011542876 A CN 202011542876A CN 112636977 A CN112636977 A CN 112636977A
Authority
CN
China
Prior art keywords
internet
things
things device
unique identifier
trigger event
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202011542876.0A
Other languages
Chinese (zh)
Other versions
CN112636977B (en
Inventor
袁杨
张健
罗阿文
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sichuan Hongwei Technology Co Ltd
Original Assignee
Sichuan Hongwei Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sichuan Hongwei Technology Co Ltd filed Critical Sichuan Hongwei Technology Co Ltd
Priority to CN202011542876.0A priority Critical patent/CN112636977B/en
Publication of CN112636977A publication Critical patent/CN112636977A/en
Application granted granted Critical
Publication of CN112636977B publication Critical patent/CN112636977B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • H04L9/0825—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H04L9/0866—Generation of secret information including derivation or calculation of cryptographic keys or passwords involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0894—Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures

Abstract

The application provides an Internet of things equipment management method, a registration device, a registration system and electronic equipment, wherein the method comprises the following steps: when a trigger event reported by a first Internet of things device is acquired, determining a globally unique identifier and a private key which are distributed for the first Internet of things device in advance according to an intra-domain identifier of the first Internet of things device; generating a signature using a private key; and reporting the trigger event, the signature and the global unique identifier to a cloud service node so that the cloud service node determines a public key of the first internet of things device according to the global unique identifier, verifies the signature by using the public key, and sends the trigger event to the edge device corresponding to the second internet of things device required to be called by the trigger event when the signature passes verification, so that the edge device corresponding to the second internet of things device calls the second internet of things device. Therefore, cross-domain calling of the Internet of things equipment can be safely achieved, the requirement for changing the identification system of each Internet of things domain is not needed, and compatibility of different Internet of things domains can be achieved.

Description

Internet of things equipment management method, registration method, device and system and electronic equipment
Technical Field
The application relates to the technical field of Internet of things, in particular to an Internet of things equipment management method, a registration method, a device and a system and electronic equipment.
Background
In an information system, in order to meet different requirements of authority management, an identity management system is established to manage and verify the identities of different people and objects, which is an important ring in the system concerning the overall security and is paid much attention. Most of the existing identity management systems are established in a centralized manner, and are managed uniformly for the systems in which the identity management systems are located.
With the vigorous development of the internet of things and smart homes, more and more internet of things devices enter the lives of people. However, currently, each core device manufacturer builds a closed internet of things system by using its own core device (in the embodiment of the present application, the internet of things systems built by each manufacturer are collectively referred to as an internet of things domain), and each internet of things device uses its own identifier, which is difficult to interconnect and interact and difficult to cooperate with each other. For example, the user uses the access control system of the manufacturer a and the air conditioner of the manufacturer B at home, the access control system is located in the internet of things domain of the manufacturer a, and the air conditioner is located in the internet of things domain of the manufacturer B, so according to the current technical scheme, the access control system and the air conditioner cannot be interconnected and communicated, and are difficult to cooperate with each other.
Disclosure of Invention
An object of the embodiments of the present application is to provide an internet of things device management method, an internet of things registration method, an internet of things device management system, and an electronic device, so as to solve the problems that different internet of things domains are difficult to be compatible, cannot be interconnected and intercommunicated, and are difficult to cooperate with each other at present.
The embodiment of the application provides an Internet of things equipment management method, which comprises the following steps: when a trigger event reported by a first Internet of things device is acquired, determining a globally unique identifier and a private key which are distributed for the first Internet of things device in advance according to an intra-domain identifier of the first Internet of things device; generating a signature using the private key; reporting the trigger event, the signature and the global unique identifier to a cloud service node, so that the cloud service node determines a public key of the first internet of things device according to the global unique identifier, verifies the signature by using the public key, and sends the trigger event to an edge device corresponding to a second internet of things device required to be called by the trigger event when the signature passes verification, so that the edge device corresponding to the second internet of things device calls the second internet of things device.
The embodiment of the application converts the intra-domain identification of the first internet of things device in the domain into the global unique identification, and signs by using the private key of the first internet of things device, so that the signature, the global unique identification and the reported trigger event of the first internet of things device are reported to the cloud service node, the public key of the first internet of things device is determined by the cloud service node based on the global unique identification, the signature is verified by using the public key, and the trigger event is sent to the corresponding edge device to call the second internet of things device required to be called by the trigger event after the verification is passed. In the implementation process, cross-domain calling among different Internet of things domains (namely different independent Internet of things systems) is realized through the cloud service node, and cross-domain calling of Internet of things equipment among the different Internet of things domains can be realized under the condition that independent identification systems of the different Internet of things domains are not changed, so that the problems that the different Internet of things domains are difficult to be compatible, cannot be interconnected and intercommunicated and are difficult to cooperate with each other at present are solved. And based on the signature verification mode, the reliability of the whole calling process is ensured, and the safety of calling the second networking device in the scheme of the embodiment is ensured.
Further, before determining the globally unique identifier and the private key of the first internet of things device according to the intra-domain identifier of the first internet of things device, the method further includes: and determining that the second networking equipment required to be called by the trigger event is not the Internet of things equipment in the local domain.
In the implementation process, when the second internet-of-things device to be called by the trigger event is not the internet-of-things device in the local domain, the globally unique identifier and the private key of the first internet-of-things device are determined according to the intra-domain identifier of the first internet-of-things device. Therefore, when the second networking equipment required to be called by the trigger event is the networking equipment in the local domain, the second networking equipment can be directly called without being verified at the cloud service node and then returned to the edge equipment in the local domain, and therefore the processing efficiency is improved.
Further, the method further comprises: when a triggering event sent by a cloud service node is received, judging whether a third Internet of things device required to be called by the triggering event sent by the cloud service node belongs to an Internet of things device in the local domain; if so, calling the third Internet of things equipment; otherwise, the triggering event is ignored.
The embodiment of the application further provides an internet of things device management method, which comprises the following steps: when a trigger event of a first Internet of things device, a signature of the first Internet of things device and a global unique identifier of the first Internet of things device, which are reported by an edge device, are received, a public key of the first Internet of things device is determined according to the global unique identifier, and the public key is used for verifying the signature; the signature is generated by the edge device according to a private key of the first Internet of things device; and when the verification is passed, sending the trigger event to the edge device corresponding to the second networking device required to be called by the trigger event, so that the edge device corresponding to the second networking device calls the second networking device.
In the implementation process, after receiving the trigger event of the first internet of things device reported by the edge device, the signature of the first internet of things device and the globally unique identifier of the first internet of things device, the public key corresponding to the first internet of things device can be found based on the globally unique identifier, so that the validity of the trigger event is verified, and after the verification is passed, the trigger event is sent to the edge device corresponding to the second internet of things device required to be called by the trigger event, so that the second internet of things device is called. According to the implementation process, cross-domain calling of the Internet of things equipment can be achieved under the safe and reliable condition, and the requirement for changing the independent identification systems of the Internet of things domains is not needed, so that the problems that different Internet of things domains are difficult to be compatible, cannot be interconnected and intercommunicated and are difficult to cooperate with each other at present are solved.
Further, the sending the trigger event to the edge device corresponding to the second networking device that needs to be called by the trigger event includes: notifying the trigger event on a blockchain; the block chain comprises each edge device and a cloud service node corresponding to each edge device.
In the implementation process, each edge device and the cloud service node corresponding to each edge device form a block chain, so that each edge device on the block chain can quickly verify whether a second networking device required to be called by the trigger event is an internet of things device in the local domain or not by verifying the trigger event passing through the block chain, and quick response to the trigger event is realized. And the information notification is realized by using the block chain technology, so that the risk of information tampering can be reduced, and the safety of the scheme of the embodiment of the application is improved.
The embodiment of the application also provides an internet of things equipment registration method, which comprises the following steps: when a first registration request of the Internet of things equipment is received, generating a public and private key pair for the Internet of things equipment, and initiating a second registration request to a cloud service node; the second registration request comprises a public key in the public and private key pair for being stored by the cloud service node; and receiving a global unique identifier distributed for the Internet of things equipment returned by the cloud service node, and associating the global unique identifier with the public and private key pair and the intra-domain identifier of the Internet of things equipment carried in the first registration request.
In the implementation process, corresponding public and private key pairs and global unique identifiers are generated for the Internet of things equipment, the global unique identifiers, the public and private key pairs and the intra-domain identifiers of the Internet of things equipment are associated, and the public key of the Internet of things equipment is stored at the cloud service node, so that when cross-domain calling is needed, the trusted verification and information forwarding and intra-domain searching of the Internet of things equipment can be realized according to the intra-domain identifiers, the global unique identifiers and the public and private key pairs of the Internet of things equipment, and an implementation basis is provided for cross-domain calling. In addition, the mode reserves the intra-domain identification of the Internet of things equipment, so that the independent identification systems of different Internet of things domains are not changed, good compatibility can be realized with the existing Internet of things domains, and the problem that the different Internet of things domains are difficult to be compatible at present is solved.
Further, after generating a public and private key pair for the internet of things device, the method further comprises: and storing the public and private key pair and the domain identification of the Internet of things equipment carried in the first registration request into a preset trusted execution environment.
In the implementation process, the intra-domain identification of the internet of things equipment carried in the public and private key pair and the first registration request is stored in the preset trusted execution environment, so that the leakage of sensitive information such as the public and private key pair and the intra-domain identification can be effectively prevented, and the safety of the scheme of the embodiment of the application is improved.
The embodiment of the application also provides an internet of things equipment registration method, which comprises the following steps: when a second registration request reported by the edge device is received, generating a global unique identifier of the internet of things device corresponding to the second registration request, and storing the global unique identifier and a public key of the internet of things device in the second registration request in an associated manner; and returning the global unique identifier to the edge device.
In the implementation process, the globally unique identifier is generated for the internet of things device, and the globally unique identifier and the public key of the internet of things device are associated, so that when cross-domain calling is needed, trusted verification and information forwarding of the internet of things device can be achieved according to the globally unique identifier and the public key of the internet of things device, and an implementation basis is provided for the cross-domain calling.
Further, the generating a global unique identifier of the internet of things device corresponding to the second registration request, and storing the global unique identifier in association with the public key of the internet of things device in the second registration request includes: generating a global unique identifier of the internet of things equipment corresponding to the second registration request on a block chain, and storing the global unique identifier in association with a public key of the internet of things equipment in the second registration request; the blockchain comprises a plurality of cloud service nodes.
In the implementation process, the public key is stored in the block chain, so that the public key is prevented from being tampered based on the characteristics of the block chain, and the safety of the scheme of the embodiment of the application is improved.
The embodiment of the application further provides an internet of things device management apparatus, which includes: the device comprises a determining module, a signature module and a reporting module; the determining module is used for determining a globally unique identifier and a private key of a first internet of things device according to an intra-domain identifier of the first internet of things device when a trigger event reported by the first internet of things device is obtained; the signature module is configured to generate a signature by using the private key, and the report module is configured to report the trigger event, the signature, and the global unique identifier to a cloud service node, so that the cloud service node determines a public key of the first internet of things device according to the global unique identifier, verifies the signature by using the public key, and sends the trigger event to an edge device corresponding to a second internet of things device that needs to be called by the trigger event when the signature passes verification, so that the edge device corresponding to the second internet of things device calls the second internet of things device.
The embodiment of the application further provides an internet of things device management apparatus, which includes: the method comprises the following steps: a verification module and a processing module; the verification module is used for determining a public key of the first internet of things device according to the global unique identifier when a trigger event of the first internet of things device, a signature of the first internet of things device and the global unique identifier of the first internet of things device, which are reported by the edge device, are received, and verifying the signature by using the public key; the signature is generated by the edge device according to a private key of the first Internet of things device; and the processing module is used for sending the trigger event to the edge device corresponding to the second networking device required to be called by the trigger event when the verification is passed, so that the edge device corresponding to the second networking device calls the second networking device.
The embodiment of the application further provides an internet of things device registration apparatus, which includes: the device comprises a generating module and a receiving and storing module; the generation module is used for generating a public and private key pair for the Internet of things equipment and sending a second registration request to the cloud service node when receiving a first registration request of the Internet of things equipment; the second registration request comprises a public key in the public and private key pair for being stored by the cloud service node; and the receiving and storing module is used for receiving a global unique identifier which is returned by the cloud service node and distributed to the Internet of things equipment, and associating the global unique identifier with the public and private key pair and the intra-domain identifier of the Internet of things equipment carried in the first registration request.
The embodiment of the application further provides an internet of things device registration apparatus, which includes: a generation and storage module and an association sending module; the generation and storage module is configured to generate a global unique identifier of the internet of things device corresponding to a second registration request when the second registration request reported by the edge device is received, and store the global unique identifier in association with the public key of the internet of things device in the second registration request; and the association sending module is used for returning the global unique identifier to the edge device.
The embodiment of the application further provides an internet of things system, which includes: an Internet of things device; each edge device is connected with at least one piece of Internet of things device and is used for realizing the first Internet of things device registration method and the first Internet of things device management method; and the cloud service node is connected with the edge device and is used for realizing the second Internet of things device registration method and the second Internet of things device management method.
The embodiment of the application also provides electronic equipment, which comprises a processor, a memory and a communication bus; the communication bus is used for realizing connection communication between the processor and the memory; the processor is configured to execute one or more programs stored in the memory to implement any one of the above-described internet-of-things device management methods or implement any one of the above-described internet-of-things device registration methods.
The embodiment of the application also provides a readable storage medium, where one or more programs are stored, and the one or more programs are executable by one or more processors to implement any one of the above methods for managing devices of the internet of things or any one of the above methods for registering devices of the internet of things.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic structural diagram of an internet of things system provided in an embodiment of the present application;
fig. 2 is a schematic flowchart of a method for registering an internet of things device according to an embodiment of the present disclosure;
fig. 3 is a schematic flow chart of a method for managing devices of the internet of things according to an embodiment of the present application;
FIG. 4 is a schematic structural diagram of an exemplary Internet of things system provided by an embodiment of the present application;
fig. 5 is a schematic structural diagram of an internet of things device management apparatus applied to an edge device of an internet of things system provided in an embodiment of the present application;
fig. 6 is a schematic structural diagram of an internet of things device management apparatus applied to a cloud service node of an internet of things system provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of an internet of things device registration apparatus applied to an edge device of an internet of things system provided in an embodiment of the present application;
fig. 8 is a schematic structural diagram of an internet of things device registration apparatus applied to a cloud service node of an internet of things system provided in an embodiment of the present application;
fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
The first embodiment is as follows:
in order to solve the problems that different internet of things domains are difficult to be compatible, cannot be interconnected and cannot cooperate with each other, the embodiment of the application provides an internet of things system, and an internet of things equipment registration method and an internet of things equipment management method which are matched with the internet of things system.
As shown in fig. 1, fig. 1 is a schematic structural diagram of an internet of things system provided in an embodiment of the present application. The Internet of things system provided in the embodiment of the application comprises a cloud service node, edge devices connected with the cloud service node, and Internet of things devices connected under each edge device.
The edge device and the Internet of things device connected with the edge device are an Internet of things domain. Therefore, a plurality of different Internet of things domains can be connected through the cloud service node.
Based on the internet of things system, the embodiment of the application provides an internet of things device registration method and an internet of things device management method.
As shown in fig. 2, the method for registering the internet of things device in the embodiment of the present application includes:
s201: the Internet of things equipment sends a first registration request to the connected edge equipment.
S202: and when the edge equipment receives a first registration request of the equipment of the Internet of things, generating a public and private key pair for the equipment of the Internet of things.
In this embodiment, the edge device may use an existing public and private key generation algorithm, so as to generate a public and private key pair of the internet of things device.
In order to ensure security, in the embodiment of the present application, a TTE (Trusted Execution Environment) may be constructed in the edge device, so that a public-private key pair of the internet of things device is generated in the Trusted Execution Environment.
S203: and initiating a second registration request to the cloud service node.
In this embodiment of the application, the second registration request may include the public key of the internet of things device, so that the cloud service node can store the public key conveniently.
It should be noted that, in this embodiment of the application, each edge device is connected to a corresponding cloud service node, and the second registration request is sent to the cloud service node corresponding to the edge device.
It should be understood that, in an actual application process, a manufacturer of each internet of things device often builds a cloud platform of an internet of things domain of the manufacturer. Therefore, in a feasible implementation manner of the embodiment of the present application, cloud platforms built by manufacturers may be used as cloud service nodes corresponding to edge devices of internet of things domains in the embodiment of the present application, but it should be noted that the plurality of cloud service nodes need to be interconnected, for example, as shown in fig. 1.
In addition, in another possible implementation manner of the embodiment of the application, one or more special cloud platforms can be set up as the cloud service nodes of the edge devices. When a plurality of cloud service nodes are built, each edge device is connected with a corresponding cloud service node, each cloud service node can allow a plurality of edge devices to be connected, and all cloud service nodes are interconnected.
S204: and when receiving a second registration request reported by the edge device, the cloud service node generates a global unique identifier of the internet of things device, and stores the global unique identifier and a public key of the internet of things device carried in the second registration request in an associated manner.
In the embodiment of the application, after the cloud service node generates the global unique identifier, the global unique identifier and a public key in the second registration request can be synchronized to all cloud service nodes for association storage, so that the cloud service node can be used in the subsequent cross-domain calling of the internet of things device.
It should be understood that, in the embodiment of the application, because the globally unique identifier generated by the cloud service node is synchronized to all the cloud service nodes, when each cloud service node generates the globally unique identifier, it is ensured that the generated globally unique identifier is unique in all the internet of things devices accessing the internet of things system based on the stored globally unique identifier.
It should be noted that, in the embodiment of the present application, a specific generation algorithm is not limited, and any existing manner that can generate a globally unique identifier may be used for implementation.
It should be further noted that, in order to facilitate the association storage of the public key and the global unique identifier, in this embodiment of the application, a blockchain technology may be adopted to establish all cloud service nodes into one blockchain, so as to associate and store the public key and the global unique identifier on the blockchain (that is, store the public key and the global unique identifier on each node of the blockchain).
It should be further noted that, in order to facilitate data storage and improve data tamper resistance of the system, in this embodiment of the application, each edge device may also be used as a node of the block chain, and form the block chain together with each cloud service node.
S205: and the cloud service node returns the generated global unique identifier to the edge device sending the second registration request.
S206: and the edge equipment associates the global unique identifier with the public and private key pair and the intra-domain identifier of the equipment of the Internet of things carried in the first registration request.
It should be understood that, in the embodiment of the present application, it may be set that, when the internet of things device is activated, the first registration request is initiated to the edge device of the internet of things domain to which the internet of things device belongs, with the domain identifier of the internet of things device, so as to perform registration.
The intra-domain identifier of the internet of things device may be an identifier of the internet of things device determined according to an identification rule of an internet of things domain to which the internet of things device belongs. Illustratively, when the Identification rule of the internet of things domain to which the internet of things device belongs is that an Identification such as an International Mobile Equipment Identity (IMEI) of the internet of things device is used as an intra-domain Identification, the intra-domain Identification of the internet of things device initiates the first registration request to directly carry its own IMEI Number.
In the embodiment of the application, the globally unique identifier, the public and private key pair and the intra-domain identifier of the internet of things device can be stored in a trusted execution environment of the edge device in a correlated manner, so that the data security is improved.
After the edge device stores the globally unique identifier, the public and private key pair and the intra-domain identifier of the internet of things device in an associated manner, the internet of things device is registered successfully, so that cross-domain cooperative interconnection can be realized according to the internet of things device management method provided in the embodiment of the application.
Referring to fig. 3, fig. 3 is a schematic flow chart of an internet of things device management method provided in an embodiment of the present application, and the method includes:
s301: the first Internet of things device reports a trigger event to a first edge device of the Internet of things domain.
It should be understood that, in this embodiment of the application, the first internet of things device may be any one of the internet of things devices in the internet of things system provided in this embodiment of the application, and as long as the internet of things device reports the trigger event, the internet of things device is the first internet of things device. And the first edge device refers to an edge device to which the first internet of things device is connected.
In the embodiment of the present application, a trigger rule may be preset, for example: "thermometer 1 detects the temperature and is greater than 28 degrees, closes air conditioner 1", "entrance guard opens, opens air conditioner 2", "when intelligent alarm clock reporting time is 19 o' clock, opens intelligent TV and watches one set of central" and so on.
In the embodiment of the application, the trigger rule may be preset by a manufacturer, or may be set by an actual user of the internet of things device.
It should be understood that, in a possible implementation manner of the embodiment of the present application, the trigger rules may be set in the internet of things devices respectively. For example, the trigger rule "thermometer 1 detects that the temperature is higher than 28 degrees, turn off air conditioner 1" may be set in thermometer 1, and the trigger rule "door access is opened, turn on air conditioner 2" may be set in door access. Therefore, each internet of things device performs trigger rule detection according to its own state, and when it is found that the trigger rule is satisfied, reports the operation indicated by the trigger rule to the edge device connected to itself (for example, if the access control detects that the access control is opened, the trigger rule "access control is opened, air conditioner 2 is opened" is satisfied at this time, and thus the operation indicated by the trigger rule "air conditioner 2 is opened" is reported), where the operation indicated by the reported trigger rule is the trigger event described in the embodiment of the present application.
In addition, in another possible implementation manner of the embodiment of the present application, each trigger rule may also be stored in each edge device and each cloud service node. For example, each edge device and the cloud service node may together form a block chain, and each trigger rule is set on the block chain (that is, each node of the block chain has a set trigger rule in synchronization). Each internet of things device can report own state information to the connected edge device, and the edge device carries out trigger rule detection according to the received state information. For example, when the door control is opened, the opened state information of the door control can be reported to the edge device, the edge device detects the trigger rule, and the condition that the door control is opened and the air conditioner 2 is opened meets the trigger rule is found. At this time, the state information meeting the trigger rule reported by the internet of things device is the trigger event.
S302: and the first edge equipment determines the globally unique identifier and the private key of the first Internet of things equipment according to the intra-domain identifier of the first Internet of things equipment.
In this embodiment of the application, the first edge device may find the globally unique identifier and the private key of the first internet of things device according to the intra-domain identifier of the first internet of things device by associating the stored intra-domain identifier, the globally unique identifier, and the private key in advance.
S303: the first edge device generates a signature of the first internet of things device using the private key.
In the embodiment of the present application, the signature may be obtained by using an existing signature algorithm, and the specifically used signature algorithm is not limited in the embodiment of the present application.
S304: the first edge device reports the trigger event, the signature of the first internet of things device and the globally unique identifier of the first internet of things device to the cloud service node.
S305: the cloud service node finds out the public key of the first Internet of things device according to the global unique identifier, and verifies the signature by using the public key.
In the embodiment of the application, the cloud service node can find out the public key associated with the global unique identifier according to the global unique identifier, so that the signature verification is realized based on the public key. If the verification is passed, it indicates that the content reported by the first edge device is authentic, so that the subsequent operation can be performed. If the verification fails, the content reported by the first edge device is deemed to be not credible, so that the content reported this time can be ignored.
S306: and when the verification is passed, sending the trigger event to a second edge device corresponding to a second networking device required to be called by the trigger event.
S307: and the second edge device calls the second networking device according to the trigger event.
In this embodiment of the application, each edge device and the cloud service node may together form a block chain, so that the cloud service node may notify the trigger event on the block chain, so that each edge device may receive the trigger event, and thus each edge device determines whether the second networking device that needs to be called by the trigger event is an internet of things device in the local domain.
In addition, if the block chain is not constructed, the cloud service nodes can broadcast the trigger event to each cloud service node, so that each cloud service node sends the trigger event to the edge device connected with the cloud service node.
It should be understood that if the reported trigger event is an operation indicated by the trigger rule, each edge device may determine, according to the operation, a second networking device that needs to be operated. If the reported trigger event is the state information meeting the trigger rule, the second networking equipment needing to be operated can be determined according to the stored trigger rule.
After the second networking equipment needing to be operated is determined, each edge device can search and determine whether the second networking equipment belongs to the networking equipment in the domain. If yes, the second networking equipment can be directly called to carry out the operation specified in the trigger rule.
It should be noted that, in this embodiment of the application, after acquiring the trigger event reported by the first internet of things device, the first edge device may first determine whether the second internet of things device that needs to be called by the trigger event is an internet of things device in the local domain.
If yes, the second networking equipment can be directly called. If not, the first edge device determines the globally unique identifier and the private key of the first internet of things device according to the intra-domain identifier of the first internet of things device, so as to execute the subsequent operations of steps S303 to S307.
Of course, in this embodiment of the application, after the first edge device obtains the trigger event reported by the first internet of things device, the operations in steps S302 to S307 may also be directly performed. At this time, if the second internet-of-things device that needs to be called by the trigger event and the first internet-of-things device belong to the same internet-of-things domain, the second edge device in step S306 is the first edge device in step S301.
It should be noted that, in this embodiment of the application, the internet of things device may be a device that can access a network to implement network interconnection, the edge device may be a device that can implement interconnection, transfer, and control of the internet of things device, for example, may be a device such as an intelligent gateway, and the cloud service node may be a cloud platform and implemented by hardware devices such as a server.
The Internet of things system, the corresponding Internet of things equipment management method and the corresponding Internet of things equipment registration method can realize cross-domain calling of Internet of things equipment under the safe and reliable condition, and the requirement for changing the independent identification systems of the Internet of things domains is not needed, so that the problems that different Internet of things domains are difficult to be compatible, cannot be interconnected and communicated and are difficult to cooperate with each other at present are solved.
Example two:
based on the first embodiment, the present embodiment takes a specific cross-domain calling procedure as an example to further illustrate the present application.
Referring to the internet of things system structure shown in fig. 4, an internet of things device is connected below the edge device 1: intelligent air conditioner, temperature sensor and intelligent entrance guard are connected with thing networking device under 2 of edge equipment: intelligent washing machine and intelligent TV. The edge device 1, the cloud node 2 and the edge device 2 form a block chain.
Assume that a trigger rule 1 is configured on the blockchain: "the temperature is greater than 28 degrees, opens intelligent air conditioner", triggers rule 2: the entrance guard is opened from the outside and the intelligent television is started.
Suppose that the edge device 1 receives the status information reported by the temperature sensor: the "temperature is 30 degrees", and at this time, the edge device 1 performs trigger rule detection and finds that the trigger rule 1 is satisfied. At this moment, according to the triggering rule 1, it is determined that the internet of things equipment to be called is the intelligent air conditioner 1, the intelligent air conditioner 1 is the internet of things equipment in the local domain, and then the edge equipment 1 directly sends an opening instruction to the intelligent air conditioner 1, so that the intelligent air conditioner 1 is called.
Suppose that the edge device 1 receives the state information reported by the intelligent access control: "the entrance guard is opened from the outside", and edge device 1 carries out the rule detection that triggers this moment, finds to accord with and triggers rule 2. At this time, according to the trigger rule 2, it is determined that the internet of things device to be called is the smart television, the edge device 1 searches for the internet of things device connected in the local domain, and finds that the smart television does not belong to the internet of things device in the local domain, then according to the in-domain identifier of the smart access, a private key and a globally unique identifier corresponding to the smart access are found out in the trusted execution environment, then a signature is generated according to the private key, and the trigger event of 'access being opened from the outside', the generated signature and the globally unique identifier of the smart access are reported to the cloud end node 1.
The cloud node 1 finds out the public key of the intelligent access control according to the global unique identification of the intelligent access control, and verifies the signature by using the public key. After the verification is passed, a trigger event of 'entrance guard is opened from the outside' is broadcasted in the blockchain.
The edge device 2 detects a trigger rule of the trigger event of 'entrance guard is opened from the outside', finds that the trigger rule 2 is met, and determines that the internet of things device required to be called is the smart television. The intelligent television is searched in the domain, and the intelligent television is found to belong to the Internet of things equipment in the domain, so that the starting instruction is issued to the intelligent television, and the intelligent television is called.
Through the scheme, the existing intra-domain identification of each Internet of things domain can be compatible, so that the mutually independent Internet of things domains under the current environment can be opened, an information island is broken, interconnection and intercommunication of cross-domain Internet of things equipment are promoted, linkage cooperation of the cross-domain Internet of things equipment is realized, user experience is improved, and the use cost of a user for the Internet of things equipment is reduced. In addition, in the embodiment of the application, the block chain technology is utilized, effective compatibility to various existing internet of things domains can be achieved, and the safety is high. In addition, the embodiment of the application is combined with the edge technology, and the calling of the intra-domain Internet of things equipment is directly finished in the domain, so that the efficiency can be effectively improved in the face of a large number of Internet of things systems.
Example three:
based on the same inventive concept, the embodiment of the present application further provides an internet of things device management apparatus 100 and an internet of things device registration apparatus 300 that can be applied to the edge device of the internet of things system provided in the embodiment of the present application, and an internet of things device management apparatus 200 and an internet of things device registration apparatus 400 that can be applied to the cloud service node of the internet of things system provided in the embodiment of the present application. Referring to fig. 5 to 8, the method shown in fig. 2 may be implemented by the device management apparatus of the internet of things shown in fig. 5 and 6 in cooperation, and the method shown in fig. 3 may be implemented by the device registration apparatus of the internet of things shown in fig. 7 and 8 in cooperation. It should be understood that the specific functions of the apparatuses 100 to 400 can be referred to the above description, and the detailed description is omitted here as appropriate to avoid redundancy. The devices 100 to 400 include at least one software functional module that can be stored in a memory in the form of software or firmware or solidified in an operating system of the devices 100 to 400. Specifically, the method comprises the following steps:
referring to fig. 5, the apparatus 100 includes: a determining module 101, a signature module 102 and a reporting module 103. Wherein:
the determining module 101 is configured to determine, according to an intra-domain identifier of a first internet of things device, a globally unique identifier and a private key of the first internet of things device when a trigger event reported by the first internet of things device is obtained;
the signature module 102 is configured to generate a signature using the private key
The reporting module 103 is configured to report the trigger event, the signature, and the global unique identifier to a cloud service node, so that the cloud service node determines a public key of the first internet of things device according to the global unique identifier, verifies the signature using the public key, and when the signature passes the verification, sends the trigger event to an edge device corresponding to a second internet of things device that needs to be called by the trigger event, so that the edge device corresponding to the second internet of things device calls the second internet of things device.
In this embodiment of the application, the determining module 101 is further configured to determine that the second internet-of-things device that needs to be invoked by the trigger event is not the internet-of-things device in the local domain before determining the globally unique identifier and the private key of the first internet-of-things device according to the intra-domain identifier of the first internet-of-things device.
In this embodiment of the application, the apparatus 100 further includes a processing unit, configured to determine, when receiving a trigger event sent by a cloud service node, whether a third internet-of-things device that needs to be called by the trigger event sent by the cloud service node belongs to an internet-of-things device in the local domain; if so, calling the third Internet of things equipment; otherwise, the triggering event is ignored.
Referring to fig. 6, the apparatus 200 includes: an authentication module 201 and a processing module 202. Wherein:
the verification module 201 is configured to determine, when receiving a trigger event of a first internet of things device, a signature of the first internet of things device, and a global unique identifier of the first internet of things device, which are reported by an edge device, a public key of the first internet of things device according to the global unique identifier, and verify the signature by using the public key; the signature is generated by the edge device according to a private key of the first Internet of things device;
the processing module 202 is configured to send the trigger event to the edge device corresponding to the second networked device that needs to be called by the trigger event when the verification passes, so that the edge device corresponding to the second networked device calls the second networked device.
In this embodiment of the application, the processing module 202 is specifically configured to notify the trigger event on a blockchain; the block chain comprises each edge device and a cloud service node corresponding to each edge device.
Referring to fig. 7, an apparatus 300, comprising: a generating module 301 and a receiving and storing module 302. Wherein:
the generation module 301 is configured to generate a public and private key pair for an internet of things device and initiate a second registration request to a cloud service node when a first registration request of the internet of things device is received; the second registration request comprises a public key in the public and private key pair for being stored by the cloud service node;
the receiving and storing module 302 is configured to receive a globally unique identifier distributed for the internet of things device and returned by the cloud service node, and associate the globally unique identifier with the public and private key pair and an intra-domain identifier of the internet of things device carried in the first registration request.
In this embodiment of the application, the receiving and storing module 302 is further configured to store, after the generating module 301 generates a public and private key pair for the internet of things device, the public and private key pair and the intra-domain identifier of the internet of things device carried in the first registration request into a preset trusted execution environment.
Referring to fig. 8, an apparatus 400, comprising: a generation saving module 401 and an association sending module 402. Wherein:
the generating and storing module 401 is configured to generate a global unique identifier of the internet of things device corresponding to a second registration request when the second registration request reported by the edge device is received, and store the global unique identifier in association with the public key of the internet of things device in the second registration request;
the association sending module 402 is configured to return the globally unique identifier to the edge device.
In this embodiment of the application, the generating and storing module 401 is specifically configured to generate a global unique identifier of the internet of things device corresponding to the second registration request on a block chain, and store the global unique identifier in association with the public key of the internet of things device in the second registration request; the blockchain comprises a plurality of cloud service nodes.
It should be understood that, for the sake of brevity, the contents described in some embodiments are not repeated in this embodiment.
Example four:
the present embodiment provides an electronic device, which is shown in fig. 9 and includes a processor 901, a memory 902, and a communication bus 903. Wherein:
the communication bus 903 is used for connection communication between the processor 901 and the memory 902.
The processor 901 is configured to execute one or more programs stored in the memory 902, so as to implement the internet of things device management method or the internet of things device registration method executed by the edge device or the cloud service node in the first embodiment and/or the second embodiment.
It will be appreciated that the configuration shown in fig. 9 is merely illustrative and that the electronic device may include more or fewer components than shown in fig. 9 or have a different configuration than shown in fig. 9.
It should be understood that the electronic device in the embodiment of the present application may be a device such as an intelligent gateway, a server, and the like, but is not limited thereto.
The present embodiment also provides a readable storage medium, such as a floppy disk, an optical disk, a hard disk, a flash Memory, a usb (Secure Digital Card), an MMC (Multimedia Card), etc., where one or more programs for implementing the above steps are stored in the readable storage medium, and the one or more programs may be executed by one or more processors to implement the steps of the internet of things device management method executed by the service distribution device in the first embodiment and/or the second embodiment, or to implement the internet of things device management method or the internet of things device registration method executed by the edge device or the cloud service node in the first embodiment and/or the second embodiment. And will not be described in detail herein.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
In addition, units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
Furthermore, the functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
In this context, a plurality means two or more.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims (16)

1. An Internet of things equipment management method is characterized by comprising the following steps:
when a trigger event reported by a first Internet of things device is acquired, determining a globally unique identifier and a private key which are distributed for the first Internet of things device in advance according to an intra-domain identifier of the first Internet of things device;
generating a signature using the private key;
reporting the trigger event, the signature and the global unique identifier to a cloud service node, so that the cloud service node determines a public key of the first internet of things device according to the global unique identifier, verifies the signature by using the public key, and sends the trigger event to an edge device corresponding to a second internet of things device required to be called by the trigger event when the signature passes verification, so that the edge device corresponding to the second internet of things device calls the second internet of things device.
2. The internet-of-things device management method of claim 1, wherein before determining the globally unique identifier and the private key of the first internet-of-things device from the intra-domain identifier of the first internet-of-things device, the method further comprises:
and determining that the second networking equipment required to be called by the trigger event is not the Internet of things equipment in the local domain.
3. The internet of things device management method of claim 1 or 2, wherein the method further comprises:
when a triggering event sent by a cloud service node is received, judging whether a third Internet of things device required to be called by the triggering event sent by the cloud service node belongs to an Internet of things device in the local domain;
if so, calling the third Internet of things equipment;
otherwise, the triggering event is ignored.
4. An Internet of things equipment management method is characterized by comprising the following steps:
when a trigger event of a first Internet of things device, a signature of the first Internet of things device and a global unique identifier of the first Internet of things device, which are reported by an edge device, are received, a public key of the first Internet of things device is determined according to the global unique identifier, and the public key is used for verifying the signature; the signature is generated by the edge device according to a private key of the first Internet of things device;
and when the verification is passed, sending the trigger event to the edge device corresponding to the second networking device required to be called by the trigger event, so that the edge device corresponding to the second networking device calls the second networking device.
5. The device management method for the internet of things of claim 4, wherein the sending the trigger event to the edge device corresponding to the second networked device that needs to be called by the trigger event comprises:
notifying the trigger event on a blockchain; the block chain comprises each edge device and a cloud service node corresponding to each edge device.
6. An Internet of things equipment registration method is characterized by comprising the following steps:
when a first registration request of the Internet of things equipment is received, generating a public and private key pair for the Internet of things equipment, and initiating a second registration request to a cloud service node; the second registration request comprises a public key in the public and private key pair for being stored by the cloud service node;
and receiving a global unique identifier distributed for the Internet of things equipment returned by the cloud service node, and associating the global unique identifier with the public and private key pair and the intra-domain identifier of the Internet of things equipment carried in the first registration request.
7. The method of internet of things device registration of claim 6, wherein after generating a public-private key pair for the internet of things device, the method further comprises:
and storing the public and private key pair and the domain identification of the Internet of things equipment carried in the first registration request into a preset trusted execution environment.
8. An Internet of things equipment registration method is characterized by comprising the following steps:
when a second registration request reported by the edge device is received, generating a global unique identifier of the internet of things device corresponding to the second registration request, and storing the global unique identifier and a public key of the internet of things device in the second registration request in an associated manner;
and returning the global unique identifier to the edge device.
9. The internet-of-things device registration method of claim 8, wherein the generating a globally unique identifier of an internet-of-things device corresponding to the second registration request and storing the globally unique identifier in association with a public key of the internet-of-things device in the second registration request comprises:
generating a global unique identifier of the internet of things equipment corresponding to the second registration request on a block chain, and storing the global unique identifier in association with a public key of the internet of things equipment in the second registration request; the blockchain comprises a plurality of cloud service nodes.
10. An internet of things equipment management device, comprising: the device comprises a determining module, a signature module and a reporting module;
the determining module is used for determining a globally unique identifier and a private key of a first internet of things device according to an intra-domain identifier of the first internet of things device when a trigger event reported by the first internet of things device is obtained;
the signature module is used for generating a signature by using the private key
The reporting module is configured to report the trigger event, the signature and the global unique identifier to a cloud service node, so that the cloud service node determines a public key of the first internet of things device according to the global unique identifier, verifies the signature by using the public key, and sends the trigger event to an edge device corresponding to a second internet of things device that needs to be called by the trigger event when the verification passes, so that the edge device corresponding to the second internet of things device calls the second internet of things device.
11. An internet of things equipment management device, comprising: a verification module and a processing module;
the verification module is used for determining a public key of the first internet of things device according to the global unique identifier when a trigger event of the first internet of things device, a signature of the first internet of things device and the global unique identifier of the first internet of things device, which are reported by the edge device, are received, and verifying the signature by using the public key; the signature is generated by the edge device according to a private key of the first Internet of things device;
and the processing module is used for sending the trigger event to the edge device corresponding to the second networking device required to be called by the trigger event when the verification is passed, so that the edge device corresponding to the second networking device calls the second networking device.
12. An Internet of things equipment registration device, comprising: the device comprises a generating module and a receiving and storing module;
the generation module is used for generating a public and private key pair for the Internet of things equipment and sending a second registration request to the cloud service node when receiving a first registration request of the Internet of things equipment; the second registration request comprises a public key in the public and private key pair for being stored by the cloud service node;
and the receiving and storing module is used for receiving a global unique identifier which is returned by the cloud service node and distributed to the Internet of things equipment, and associating the global unique identifier with the public and private key pair and the intra-domain identifier of the Internet of things equipment carried in the first registration request.
13. An Internet of things equipment registration device, comprising: a generation and storage module and an association sending module;
the generation and storage module is configured to generate a global unique identifier of the internet of things device corresponding to a second registration request when the second registration request reported by the edge device is received, and store the global unique identifier in association with the public key of the internet of things device in the second registration request;
and the association sending module is used for returning the global unique identifier to the edge device.
14. An internet of things system, comprising:
an Internet of things device;
a plurality of edge devices, each of which is connected to at least one internet of things device, and is configured to implement the internet of things device registration method according to claim 6 or 7 and implement the internet of things device management method according to any one of claims 1 to 3;
a cloud service node, connected to the edge device, and configured to implement the method for registering internet of things device according to claim 8 or 9, and implement the method for managing internet of things device according to claim 4 or 5.
15. An electronic device, comprising: a processor, a memory, and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the internet of things device management method according to any one of claims 1 to 3, or the internet of things device management method according to claim 4 or 5, or the internet of things device registration method according to claim 6 or 7, or the internet of things device registration method according to claim 8 or 9.
16. A readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the internet of things device management method of any one of claims 1 to 3, or the internet of things device management method of claim 4 or 5, or the internet of things device registration method of claim 6 or 7, or the internet of things device registration method of claim 8 or 9.
CN202011542876.0A 2020-12-23 2020-12-23 Internet of things equipment management method, registration method, device and system and electronic equipment Active CN112636977B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011542876.0A CN112636977B (en) 2020-12-23 2020-12-23 Internet of things equipment management method, registration method, device and system and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011542876.0A CN112636977B (en) 2020-12-23 2020-12-23 Internet of things equipment management method, registration method, device and system and electronic equipment

Publications (2)

Publication Number Publication Date
CN112636977A true CN112636977A (en) 2021-04-09
CN112636977B CN112636977B (en) 2022-09-27

Family

ID=75321965

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011542876.0A Active CN112636977B (en) 2020-12-23 2020-12-23 Internet of things equipment management method, registration method, device and system and electronic equipment

Country Status (1)

Country Link
CN (1) CN112636977B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113596141A (en) * 2021-07-26 2021-11-02 深圳Tcl新技术有限公司 Method and device for setting equipment control authority, computer equipment and storage medium
CN114500088A (en) * 2022-02-23 2022-05-13 北京中科锐链科技有限公司 Internet of things equipment access authentication method and system based on block chain and edge calculation

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170346848A1 (en) * 2016-05-31 2017-11-30 Ned M. Smith System, Apparatus And Method For Scalable Internet Of Things (IOT) Device On-Boarding With Quarantine Capabilities
CN108833464A (en) * 2018-04-13 2018-11-16 西安电子科技大学 Confederate state's formula multiple domain Internet of Things cooperative system and method, smart city, smart home
US20190166117A1 (en) * 2017-11-30 2019-05-30 Mocana Corporation System and method for securing data transport between a non-ip endpoint device that is connected to a gateway device and a connected service
CN110138560A (en) * 2019-06-04 2019-08-16 北京理工大学 A kind of dual-proxy cross-domain authentication method based on id password and alliance's chain
CN110233850A (en) * 2019-06-20 2019-09-13 浪潮卓数大数据产业发展有限公司 Register method, application server, user terminal and system based on alliance's chain
CN111010376A (en) * 2019-11-28 2020-04-14 国网河南省电力公司信息通信公司 Master-slave chain-based Internet of things authentication system and method
CN111355745A (en) * 2020-03-12 2020-06-30 西安电子科技大学 Cross-domain identity authentication method based on edge computing network architecture
CN111414599A (en) * 2020-02-26 2020-07-14 北京奇艺世纪科技有限公司 Identity authentication method, device, terminal, server and readable storage medium
CN111835528A (en) * 2020-07-16 2020-10-27 广州大学 Decentralized Internet of things cross-domain access authorization method and system
CN112019349A (en) * 2020-08-28 2020-12-01 南京工程学院 Cross-domain authentication method for power internet of things based on cross-chain technology

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170346848A1 (en) * 2016-05-31 2017-11-30 Ned M. Smith System, Apparatus And Method For Scalable Internet Of Things (IOT) Device On-Boarding With Quarantine Capabilities
US20190166117A1 (en) * 2017-11-30 2019-05-30 Mocana Corporation System and method for securing data transport between a non-ip endpoint device that is connected to a gateway device and a connected service
CN108833464A (en) * 2018-04-13 2018-11-16 西安电子科技大学 Confederate state's formula multiple domain Internet of Things cooperative system and method, smart city, smart home
CN110138560A (en) * 2019-06-04 2019-08-16 北京理工大学 A kind of dual-proxy cross-domain authentication method based on id password and alliance's chain
CN110233850A (en) * 2019-06-20 2019-09-13 浪潮卓数大数据产业发展有限公司 Register method, application server, user terminal and system based on alliance's chain
CN111010376A (en) * 2019-11-28 2020-04-14 国网河南省电力公司信息通信公司 Master-slave chain-based Internet of things authentication system and method
CN111414599A (en) * 2020-02-26 2020-07-14 北京奇艺世纪科技有限公司 Identity authentication method, device, terminal, server and readable storage medium
CN111355745A (en) * 2020-03-12 2020-06-30 西安电子科技大学 Cross-domain identity authentication method based on edge computing network architecture
CN111835528A (en) * 2020-07-16 2020-10-27 广州大学 Decentralized Internet of things cross-domain access authorization method and system
CN112019349A (en) * 2020-08-28 2020-12-01 南京工程学院 Cross-domain authentication method for power internet of things based on cross-chain technology

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
陈园等: "IBEXSec：一种面向工业互联网终端的通用安全服务框架", 《电信科学》 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113596141A (en) * 2021-07-26 2021-11-02 深圳Tcl新技术有限公司 Method and device for setting equipment control authority, computer equipment and storage medium
WO2023005525A1 (en) * 2021-07-26 2023-02-02 深圳Tcl新技术有限公司 Configuration method for device control privilege, apparatus, computer device, and storage medium
CN113596141B (en) * 2021-07-26 2023-07-25 深圳Tcl新技术有限公司 Method and device for setting device control authority, computer device and storage medium
CN114500088A (en) * 2022-02-23 2022-05-13 北京中科锐链科技有限公司 Internet of things equipment access authentication method and system based on block chain and edge calculation
CN114500088B (en) * 2022-02-23 2024-02-23 北京中科锐链科技有限公司 Internet of things equipment access authentication method and system based on blockchain and edge calculation

Also Published As

Publication number Publication date
CN112636977B (en) 2022-09-27

Similar Documents

Publication Publication Date Title
US20210149663A1 (en) Data processing method based on intelligent contract, device, and storage medium
CN111163182B (en) Block chain-based device registration method and apparatus, electronic device, and storage medium
CN109257334B (en) Block chain-based data uplink system, method and storage medium
EP2611226B1 (en) Processing method and system for over-the-air bootstrap
CN112636977B (en) Internet of things equipment management method, registration method, device and system and electronic equipment
CN101626368A (en) Device, method and system for preventing web page from being distorted
CN110266872B (en) Address book data management and control method and device, cloud address book system, computer equipment and computer readable storage medium
US11394696B2 (en) Resource request method, device and storage medium
EP3598333B1 (en) Electronic device update management
CN113453213A (en) Authentication data synchronization method and device
CN110597918A (en) Account management method and device and computer readable storage medium
CN102821092A (en) Internet of Things system and Internet of Things service providing and monitoring method
US20170054519A1 (en) Resource Creation Method and Apparatus
CN102137102B (en) Realizing method of service supporting platform for supporting multiclass information publishing modes
CN113286265B (en) CPE device, control device, communication method, communication system and storage medium
CN111510431B (en) Universal terminal access control platform, client and control method
CN116628696A (en) Vulnerability detection method based on proxy client and related equipment
CN109729043B (en) Method, device and system for preventing attack message
CN112926981A (en) Transaction information processing method, device and medium for block chain and electronic equipment
CN114338777B (en) Escape control method and device
CN110597557A (en) System information acquisition method, terminal and medium
CN110868407B (en) Ethernet link detection method, device, electronic equipment and computer medium
CN116029729B (en) Cross-link method and system based on dynamic access application link management contract mode
CN117040929B (en) Access processing method, device, equipment, medium and program product
CN116910704A (en) License verification method, device, equipment and medium of data platform

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant