CN112671844A - Registration method and system of equipment - Google Patents
Registration method and system of equipment Download PDFInfo
- Publication number
- CN112671844A CN112671844A CN202011448895.7A CN202011448895A CN112671844A CN 112671844 A CN112671844 A CN 112671844A CN 202011448895 A CN202011448895 A CN 202011448895A CN 112671844 A CN112671844 A CN 112671844A
- Authority
- CN
- China
- Prior art keywords
- equipment
- server
- edge
- information
- cloud
- 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
Links
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The embodiment of the disclosure provides a device registration method and system. The method comprises the following steps: the edge side server receives an online notification sent by the side equipment and sends the online notification of the side equipment to the cloud server; the online notification comprises information of the end-side equipment corresponding to the side-side equipment; the cloud server receives the online notification, checks the state of the end-side equipment according to the information of the end-side equipment, and if the state is unregistered, issues a registration message to the edge-side server to register the unregistered end-side equipment; the edge side server receives a login request sent by registered side equipment, establishes communication with the side equipment, and issues data to the side equipment and/or monitors the state of the side equipment. In this way, it can be ensured that the data of the cloud server is completely issued to the edge side server, and meanwhile, authentication information is provided for the connection of the end side device.
Description
Technical Field
Embodiments of the present disclosure relate generally to the field of smart trains, and more particularly, to a method and system for registering a device.
Background
The end-side equipment in the field of intelligent trains often does not have the public network communication capability, and needs to be connected to the side equipment, so that the side equipment is used as a center to transmit data.
At this time, in order to ensure the security of the end-side device, the corresponding device needs to be registered. The registration information is maintained by the cloud side, and the end-side device is connected to the side, so that data on the cloud side needs to be reliably transmitted to the side.
In practical applications, there are possibilities of network interruption and device power failure, so how to ensure that data stably and efficiently reaches the side device is an urgent problem to be solved at present.
Disclosure of Invention
The present disclosure is directed to solving at least one of the technical problems of the related art or related art.
To this end, in a first aspect of the present disclosure, a method of registration of a device is provided. The method comprises the following steps:
the edge side server receives an online notification sent by the side equipment and sends the online notification of the side equipment to the cloud server; the online notification comprises information of the end-side equipment corresponding to the side-side equipment;
the cloud server receives the online notification, checks the state of the end-side equipment according to the information of the end-side equipment, and if the state is unregistered, issues a registration message to the edge-side server to register the unregistered end-side equipment;
the edge side server receives a login request sent by registered side equipment, establishes communication with the side equipment, and issues data to the side equipment and/or monitors the state of the side equipment.
Further, the issuing, by the cloud server, the registration message to the edge side server includes:
and the cloud server stores the information of the end-side equipment into an equipment information table to be registered in a cloud-side database, and issues a registration message to the edge-side server.
Further, before the cloud server issues the registration message to the edge side server, the method further includes:
and the cloud server receives the recorded information of the end-side equipment and registers the end-side equipment.
Further, the cloud server receives the entered information of the peer-to-peer device, and performing peer-to-peer device registration includes:
the cloud server stores the information of the end-side equipment into an equipment information table to be registered in a cloud-side database, and issues registration information to the edge-side server, wherein the registration information comprises the information of the end-side equipment;
the edge side server receives the registration information, writes the registration information into a side database, and sends a registration completion notification to the cloud server;
and the cloud server receives the registration completion notification, writes the information of the end-side equipment into a registered equipment information table in a side database, and deletes the information of the end-side equipment from an equipment information table to be registered in the cloud side database.
Further, the edge side server receives a login request sent by a registered end side device, and establishing communication with the end side device includes:
the edge side server receives a login request sent by a registered side device, authenticates the login request through the side registered device information table, and establishes communication with the side device if the authentication is passed; the login request comprises a login key acquired by the device through registration.
Further, monitoring the status of the end-side device comprises:
and sending the data of the end-side equipment to a cloud server.
Further, the cloud server, the edge side server and the end side device communicate through an MQTT protocol.
In a second aspect of the present disclosure, a registration system of a device is presented, comprising:
the system comprises a cloud server, an edge side server and an end side device;
the cloud server comprises a cloud EMQ Broker, a first MQTT Client, a web application server and a cloud side database;
the cloud EMQ Broker is used for realizing communication between the first MQTT Client and the edge side server;
the first MQTT Client is used for processing data sent by the web application server and the edge side server;
the web application server is used for processing a request of a front-end page;
the cloud side database is used for storing an information table of the equipment to be registered;
the edge side server comprises an edge EMQ Broker, an edge MQTT Client, a second MQTT Client and a side database;
the edge EMQ Broker is used for realizing communication between the edge MQTT Client and the end-side equipment;
the edge MQTT Client is used for receiving data sent by the processing end-side equipment;
the second MQTT Client is used for carrying out data transmission with the cloud server;
and the side database is used for storing a registered equipment information table.
Further, the first MQTT Client is specifically configured to:
receiving end-side equipment information sent by the Web server, storing the end-side equipment information into an equipment information table to be registered in the cloud side database, and sending the end-side equipment information to the second MQTT Client;
and receiving a registration completion notification sent by the second MQTT Client, writing the end-side equipment information into a registered equipment information table in a cloud side database, deleting the end-side equipment information from an equipment information table to be registered in the side database, and sending the registration completion notification to the Web server.
Further, the second MQTT Client is specifically configured to:
and receiving the end-side equipment information sent by the first MQTT Client, inquiring whether the end-side equipment is registered from a registered equipment information table in an end-side database, and if so, sending a registration completion notification to the first MQTT Client.
According to the device registration method provided by the embodiment of the application, the edge side server receives the online notification sent by the side device, and sends the online notification of the side device to the cloud server; the online notification comprises information of the end-side equipment corresponding to the side-side equipment; the cloud server receives the online notification, checks the state of the end-side equipment according to the information of the end-side equipment, and if the state is unregistered, issues a registration message to the edge-side server to register the unregistered end-side equipment; the edge side server receives a login request sent by the side equipment, establishes communication with the side equipment, issues data to the side equipment and/or monitors the state of the side equipment, solves the problem that registration information cannot be completely transmitted due to network or equipment and the like, and simultaneously realizes authentication and authorization functions based on an MQTT protocol and an EMQ Broker.
It should be understood that the statements herein reciting aspects are not intended to limit the critical or essential features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. In the drawings, like or similar reference characters designate like or similar elements, and wherein:
FIG. 1 shows a block diagram of a registration system for a device in accordance with an embodiment of the present disclosure;
FIG. 2 shows a block diagram of a registration system for a device according to another embodiment of the present disclosure;
FIG. 3 illustrates a flow chart of a method of operation of a registration system of a device in accordance with an embodiment of the present disclosure;
FIG. 4 shows a flow chart of a method of registration of a registration system of a device according to an embodiment of the disclosure;
FIG. 5 shows a flow diagram of a method of authentication of a registration system of a device in accordance with an embodiment of the present disclosure;
FIG. 6 shows a flow diagram of a method of authentication of a registration system of a device in accordance with an embodiment of the present disclosure;
FIG. 7 illustrates a block diagram of an exemplary electronic device capable of implementing embodiments of the present disclosure.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be described clearly and completely with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are some, but not all embodiments of the present disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
In addition, the term "and/or" herein is only one kind of association relationship describing an associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
The first embodiment is as follows:
fig. 1 shows a block diagram of a registration system 100 of a device according to an embodiment of the disclosure. As shown in fig. 1, includes:
optionally, the cloud server 110 is used for device registration information entry, information issue (edge side server), and the like;
the edge side server 120 is used for managing the end side device 130, receiving authentication information and the like, and is a bridge between the cloud server 110 and the end side device 130;
the end-side device 130 is an edge-specific device, and different classes of devices may implement different functions, such as temperature sensors, cameras, etc.
Example two:
as shown in fig. 2, which shows a block diagram of a registration system 200 of a device according to another embodiment of the present disclosure, the cloud server 110 (cloud) includes a cloud EMQ Broker, a first MQTT Client, a web application server, and a cloud-side database;
the cloud EMQ Broker is an open source MQTT server and is used for realizing communication between a first MQTT Client and an edge side server;
the first MQTT Client is a Client based on an MQTT protocol and is used for processing data sent by the web application server and the edge side server;
the web application server is used for processing a request of a front-end page;
the cloud side database is used for storing an information table of the equipment to be registered.
The edge side server 120 (side) comprises an edge EMQ Broker, an edge MQTT Client, a second MQTT Client and a side database;
the edge EMQ Broker is an open source MQTT server and has authentication and authorization functions, and all MQTT clients (specific end-side devices) connected to the same edge EMQ Broker can realize topic publishing and subscribing and can also be used for realizing communication between the edge MQTT clients and the end-side device 230;
the edge MQTT Client is a Client based on an MQTT protocol and is used for receiving data sent by the processing end-side equipment;
the second MQTT Client is a Client based on an MQTT protocol and is used for carrying out data transmission with the cloud server;
and the side database is used for storing a registered equipment information table.
The end-side devices 130 (terminals) are various specific devices, each of which is equivalent to an MQTT Client (Client based on MQTT protocol), and can be connected to the edge EMQ Broker to publish and subscribe topics to the edge EMQ Broker.
Optionally, the first MQTT Client and the second MQTT Client perform data communication through a cloud EMQ Broker in the server.
The foregoing is a description of system embodiments, and the following is a further description of the aspects of the disclosure by way of method embodiments.
Example three:
fig. 3 shows a flow chart of a method 300 of operation of a registration system of a device according to an embodiment of the disclosure. As shown in fig. 3, the method 300 includes:
and S310, the edge side server receives the online notification sent by the side equipment and sends the online notification of the side equipment to the cloud server.
In this embodiment, the edge side server, the cloud server, and/or the edge side device may establish communication in a wired manner or a wireless connection manner.
Optionally, information of all the end-side devices corresponding to the side device is stored in the side device, and the end-side device information includes a device name, a device identification (id), a software version, and/or the like of the end-side device.
Further, the peer-side device is typically a device that is not able to communicate directly with the cloud server. The end-side devices include temperature sensors, cameras, and the like.
Optionally, after the side device is powered on, the application is restarted or disconnected and reconnected, an online notification is sent to the edge side server, and the edge side server receives the online notification sent by the side device and sends the online notification of the side device to the cloud server.
Further, the online notification includes information of the end-side device corresponding to the side-side device.
And S320, the cloud server receives the online notification, checks the state of the end-side equipment according to the information of the end-side equipment, and if the state is unregistered, issues a registration message to the edge-side server to register the unregistered end-side equipment.
Optionally, after receiving the online notification, the cloud server checks the status of the peer device according to the information of the peer device in the online notification, that is, determines whether the peer device is a registered device, if the status is unregistered, the cloud server issues a registration message to the edge server to register the unregistered peer device, and if the status is registered, the cloud server continues to perform the subsequent steps (S330).
Optionally, the cloud server stores the information of the end-side device in an information table of the device to be registered in a cloud-side database, and issues a registration message to the edge-side server.
Specifically, the cloud server acquires information of the end-side device according to the online notification, verifies validity of the end-side device (e.g., whether a device name is legal), determines whether the end-side device conforms to a preset registration rule, registers the end-side device if the end-side device conforms to the preset registration rule, generates a login key of the end-side device, writes the key and the information of the end-side device into a registered device information table in a side database, and meanwhile deletes the information of the end-side device from a device information table to be registered in the cloud side database to change the state of the end-side device into registered; if not, registration failure information is returned to the administrator (front end), including a reason for the registration failure (e.g., device name is not legitimate).
Optionally, the preset registration rule is preset according to an actual application scenario, for example, if the name of the device only includes letters according to a requirement, the device with the name including the number cannot be registered.
Optionally, the cloud server may also directly register the entered information of the end-side device. That is, the registration of the end-side device is not performed at the beginning, and when the status inquiry is performed on the end-side device after the side-side device (corresponding to the end-side device) is online, the above-mentioned registration step is performed if the end-side device is not registered.
Specifically, the cloud server performs validity verification on the logged-in end-side device, where the validity verification includes verifying whether a registration state and a device name of the device are legal or not, and if the verification is passed, the information of the end-side device is stored in a device information table to be registered in a cloud-side database, and a registration message is issued to the edge-side server, where the registration message includes information of the end-side device;
the edge side server receives the registration information, writes the registration information into a side database, and sends a registration completion notification to the cloud server;
and the cloud server receives the registration completion notification, writes the information of the end-side equipment into a registered equipment information table in a side database, deletes the end-side equipment information from an equipment information table to be registered in the cloud side database, and updates the equipment state to be registered.
Optionally, the entered information of the end-side device may be entered by an administrator, may be sent by an electronic device connected to the end-side device, or may be pre-stored locally.
Optionally, the keys in the above steps each include device _ id and device _ secret, i.e. id and login password of the device.
S330, the edge side server receives a login request sent by the registered side equipment, establishes communication with the side equipment, and issues data to the side equipment and/or monitors the state of the side equipment.
Optionally, the edge side server receives a login request sent by an end side device, where the end side device sending the login request is a registered device, the login request includes a key of the end side device, after receiving the login request, the edge side server verifies the key in the login request through an edge side registered device information table, and if the verification passes, the edge side server establishes communication with the end side device.
Optionally, after the communication is established, the edge side server receives a message topic published or subscribed by the end side device, verifies the published or subscribed message topic, determines whether the topic meets a preset publishing or subscribing rule, if so, sends an audit passing message to the end side device, and after receiving the audit passing message, the end side device can publish or subscribe a related topic: if not, returning the information that the audit is not passed or not sending any information, and when the end-side equipment receives the information that the audit is not passed or does not receive any feedback information, not publishing or subscribing the related theme.
Optionally, after the communication is established, the edge side server may monitor the state and/or function of the end side device, and know the operation state of the end side device in time.
Further, in order to better supervise the end-side device, the edge-side server may also send the state information of the end-side device to a cloud server, and the cloud server supervises the end-side device.
Example four:
the present embodiment discloses a method 400 for registration of a registration system 200 of a device. As shown in fig. 4, the method 400 includes:
s410, the Web server verifies the recorded end-side equipment information, if the verification is passed, a secret key of the end-side equipment is generated, and meanwhile, the end-side equipment information comprising the end-side equipment login secret key is sent to a first MQTT Client in the server;
s420, the first MQTT Client receives the end-side equipment information sent by the Web server, stores the end-side equipment information into an equipment information table to be registered in a cloud-side database, and simultaneously sends the end-side equipment information to a second MQTT Client in the side server;
s430, after receiving the information of the end-side equipment, the second MQTT Client inquires whether the end-side equipment is registered from a registered equipment information table in a side database, and if so, a registration completion notification is sent to the first MQTT Client;
s440, the first MQTT Client receives the registration completion notification, writes the end-side equipment information into a registered equipment information table in a cloud side database, deletes the end-side equipment information from a to-be-registered equipment information table in the side database, and sends the registration completion notification to the Web server;
s450, the Web server receives the registration completion notification sent by the first MQTT Client and updates the equipment state to be registered.
Example five:
the present embodiment discloses a method 500 for authentication of a registration system 200 of a device. As shown in fig. 5, the method 500 includes:
s510, after the side equipment is powered on, the application is restarted or disconnected and reconnected, the second MQTT Client in the side server receives the online notification of the side equipment and sends the online notification of the side equipment to the first MQTT Client in the server.
S520, the first MQTT Client in the server receives an online notification of the side device sent by the second MQTT Client in the side server, inquires the state of the side device corresponding to the side device according to the upper limit notification of the side device, and if the state is unregistered, the first MQTT Client re-issues a registration message to the second MQTT Client.
S530, the edge EMQ Broker in the side server receives a login request sent by the registered side equipment, authenticates the login request through the side registered equipment information table, and if the login request passes the authentication, the side server is connected with the side equipment; the login request includes a key of the device.
And S540, after the edge side server and the end side device are connected, the edge EMQ Broker receives the message theme sent by the end side device and verifies the message theme, if the verification is passed, theme verification passing information is sent to the end side device, and after the end side device receives the verification passing information, the end side device can publish or subscribe the corresponding theme.
Example six:
the present embodiment discloses a method 600 for monitoring a registration system 200 of a device. As shown in fig. 6, method 600 includes:
and S610, monitoring the end-side equipment through the edge MQTT Client and the cloud MQTT Client 2.
The edge MQTT Client is used for issuing data to specific equipment (end-side equipment establishing connection) and monitoring the state of the equipment.
Further, the edge MQTT Client and the cloud MQTT Client 2 may share a memory, that is, the cloud MQTT Client 2 may send monitoring data acquired by the edge MQTT Client to the cloud server, and the cloud server monitors the end-side device.
According to the embodiment of the disclosure, the following technical effects are achieved:
the present disclosure employs a cloud-edge-side architecture for device registration, i.e., a cloud server-edge side server (edge side server) -end side device architecture. Under the framework, the device registration information is managed by the cloud server, the edge side server transfers data for the cloud server and the end side device, and the data of the cloud server can be completely transmitted to the edge side server. The problem that registration information cannot be completely transmitted due to network or equipment and the like is solved, authentication and authorization functions are achieved based on the MQTT protocol and the EMQ Broker, and authentication information can be efficiently and stably provided for connection of end-side equipment.
It should be noted that, in order to reduce the computing storage resource occupation of the internet of things device, the text file may be used in place of the database in the edge side server in the present disclosure. Meanwhile, the cloud server, the edge side server and the end side device in the disclosure communicate through an MQTT protocol.
FIG. 7 illustrates a schematic block diagram of an electronic device 700 that may be used to implement embodiments of the present disclosure. As shown, device 700 includes a Central Processing Unit (CPU)701 that may perform various appropriate actions and processes in accordance with computer program instructions stored in a Read Only Memory (ROM)702 or computer program instructions loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the device 700 can also be stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
Various components in the device 700 are connected to the I/O interface 705, including: an input unit 706 such as a keyboard, a mouse, or the like; an output unit 707 such as various types of displays, speakers, and the like; a storage unit 708 such as a magnetic disk, optical disk, or the like; and a communication unit 709 such as a network card, modem, wireless communication transceiver, etc. The communication unit 709 allows the device 700 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The processing unit 701 performs the various methods and processes described above, such as the methods 300, 400, 500, 600. For example, in some embodiments, the methods 300, 400, 500, 600 may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as the storage unit 708. In some embodiments, part or all of a computer program may be loaded onto and/or installed onto device 700 via ROM 702 and/or communications unit 709. When the computer program is loaded into the RAM 703 and executed by the CPU 701, one or more steps of the methods 300, 400, 500, 600 described above may be performed. Alternatively, in other embodiments, the CPU 701 may be configured to perform the methods 300, 400, 500, 600 by any other suitable means (e.g., by way of firmware).
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a load programmable logic device (CPLD), and the like.
Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
Further, while operations are depicted in a particular order, this should be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (10)
1. A method for registering a device, comprising:
the edge side server receives an online notification sent by the side equipment and sends the online notification of the side equipment to the cloud server; the online notification comprises information of the end-side equipment corresponding to the side-side equipment;
the cloud server receives the online notification, checks the state of the end-side equipment according to the information of the end-side equipment, and if the state is unregistered, issues a registration message to the edge-side server to register the unregistered end-side equipment;
the edge side server receives a login request sent by registered side equipment, establishes communication with the side equipment, and issues data to the side equipment and/or monitors the state of the side equipment.
2. The method of claim 1, wherein the cloud server issuing a registration message to the edge side server comprises:
and the cloud server stores the information of the end-side equipment into an equipment information table to be registered in a cloud-side database, and issues a registration message to the edge-side server.
3. The method of claim 2, wherein before the cloud server issues the registration message to the edge side server, the method further comprises:
and the cloud server receives the recorded information of the end-side equipment and registers the end-side equipment.
4. The method according to claim 3, wherein the cloud server receives the entered information of the peer-to-peer device, and performing peer-to-peer device registration comprises:
the cloud server stores the information of the end-side equipment into an equipment information table to be registered in a cloud-side database, and issues registration information to the edge-side server, wherein the registration information comprises the information of the end-side equipment;
the edge side server receives the registration information, writes the registration information into a side database, and sends a registration completion notification to the cloud server;
and the cloud server receives the registration completion notification, writes the information of the end-side equipment into a registered equipment information table in a side database, and deletes the information of the end-side equipment from an equipment information table to be registered in the cloud side database.
5. The method of claim 4, wherein the edge side server receives a login request sent by a registered end side device, and wherein establishing communication with the end side device comprises:
the edge side server receives a login request sent by a registered side device, authenticates the login request through the side registered device information table, and establishes communication with the side device if the authentication is passed; the login request comprises a login key acquired by the device through registration.
6. The method of claim 5, wherein monitoring the status of the end-side device comprises:
and sending the data of the end-side equipment to a cloud server.
7. The method of claim 6, wherein the cloud server, the edge side server, and the end side device communicate via MQTT protocol.
8. A registration system for a device, the system comprising:
the system comprises a cloud server, an edge side server and an end side device;
the cloud server comprises a cloud EMQ Broker, a first MQTT Client, a web application server and a cloud side database;
the cloud EMQ Broker is used for realizing communication between the first MQTT Client and the edge side server;
the first MQTT Client is used for processing data sent by the web application server and the edge side server;
the web application server is used for processing a request of a front-end page;
the cloud side database is used for storing an information table of the equipment to be registered;
the edge side server comprises an edge EMQ Broker, an edge MQTT Client, a second MQTT Client and a side database;
the edge EMQ Broker is used for realizing communication between the edge MQTT Client and the end-side equipment;
the edge MQTT Client is used for receiving data sent by the processing end-side equipment;
the second MQTT Client is used for carrying out data transmission with the cloud server;
and the side database is used for storing a registered equipment information table.
9. The system of claim 8, wherein the first MQTT Client is specifically configured to:
receiving end-side equipment information sent by the Web server, storing the end-side equipment information into an equipment information table to be registered in the cloud side database, and sending the end-side equipment information to the second MQTT Client;
and receiving a registration completion notification sent by the second MQTT Client, writing the end-side equipment information into a registered equipment information table in a cloud side database, deleting the end-side equipment information from an equipment information table to be registered in the side database, and sending the registration completion notification to the Web server.
10. The system of claim 9, wherein the second MQTT Client is specifically configured to:
and receiving the end-side equipment information sent by the first MQTT Client, inquiring whether the end-side equipment is registered from a registered equipment information table in an end-side database, and if so, sending a registration completion notification to the first MQTT Client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011448895.7A CN112671844B (en) | 2020-12-09 | 2020-12-09 | Equipment registration method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011448895.7A CN112671844B (en) | 2020-12-09 | 2020-12-09 | Equipment registration method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112671844A true CN112671844A (en) | 2021-04-16 |
| CN112671844B CN112671844B (en) | 2023-07-25 |
Family
ID=75402315
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011448895.7A Active CN112671844B (en) | 2020-12-09 | 2020-12-09 | Equipment registration method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112671844B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116015747A (en) * | 2022-12-07 | 2023-04-25 | 四川长虹电器股份有限公司 | Safety authentication system and method for end-to-end encryption chat of edge computing equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080144605A1 (en) * | 2006-12-15 | 2008-06-19 | Chaoxin Charles Qiu | FAULT TOLERANT VOICE OVER INTERNET PROTOCOL (VoIP) SYSTEMS AND METHODS TO OPERATE THE SAME |
| CN105721306A (en) * | 2016-02-04 | 2016-06-29 | 杭州数梦工场科技有限公司 | Configuration information transmission method and device |
| US20170195332A1 (en) * | 2015-12-31 | 2017-07-06 | General Electric Company | Device enrollment in a cloud service using an authenticated application |
| CN110429708A (en) * | 2019-06-20 | 2019-11-08 | 中国电力科学研究院有限公司 | A kind of method and system for realizing controller switching equipment plug and play |
| WO2019242007A1 (en) * | 2018-06-22 | 2019-12-26 | 深圳前海达闼云端智能科技有限公司 | Device configuration method and apparatus, client terminal device, and cloud server |
| WO2020133655A1 (en) * | 2018-12-26 | 2020-07-02 | 中国科学院沈阳自动化研究所 | Lightweight authentication method supporting anonymous access of heterogeneous terminal in edge computing scenario |
-
2020
- 2020-12-09 CN CN202011448895.7A patent/CN112671844B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080144605A1 (en) * | 2006-12-15 | 2008-06-19 | Chaoxin Charles Qiu | FAULT TOLERANT VOICE OVER INTERNET PROTOCOL (VoIP) SYSTEMS AND METHODS TO OPERATE THE SAME |
| US20170195332A1 (en) * | 2015-12-31 | 2017-07-06 | General Electric Company | Device enrollment in a cloud service using an authenticated application |
| CN105721306A (en) * | 2016-02-04 | 2016-06-29 | 杭州数梦工场科技有限公司 | Configuration information transmission method and device |
| WO2019242007A1 (en) * | 2018-06-22 | 2019-12-26 | 深圳前海达闼云端智能科技有限公司 | Device configuration method and apparatus, client terminal device, and cloud server |
| WO2020133655A1 (en) * | 2018-12-26 | 2020-07-02 | 中国科学院沈阳自动化研究所 | Lightweight authentication method supporting anonymous access of heterogeneous terminal in edge computing scenario |
| CN110429708A (en) * | 2019-06-20 | 2019-11-08 | 中国电力科学研究院有限公司 | A kind of method and system for realizing controller switching equipment plug and play |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116015747A (en) * | 2022-12-07 | 2023-04-25 | 四川长虹电器股份有限公司 | Safety authentication system and method for end-to-end encryption chat of edge computing equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112671844B (en) | 2023-07-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9769266B2 (en) | Controlling access to resources on a network | |
| US20200067903A1 (en) | Integration of Publish-Subscribe Messaging with Authentication Tokens | |
| US8997187B2 (en) | Delegating authorization to applications on a client device in a networked environment | |
| US9247432B2 (en) | Systems and methods for controlling network access | |
| CN112534792A (en) | Method and system for providing secure access to cloud services in a cloud computing environment | |
| US10701053B2 (en) | Authentication and approval control system for distributed ledger platform | |
| US11277404B2 (en) | System and data processing method | |
| CN111416822A (en) | Method for access control, electronic device and storage medium | |
| CN111104675A (en) | Method and device for detecting system security vulnerability | |
| CN113360882A (en) | Cluster access method, device, electronic equipment and medium | |
| US10505784B2 (en) | Techniques for accessing logical networks via a virtualized gateway | |
| KR20130111807A (en) | System for remote monitoring of programmable logic controller using mobile device | |
| CN112182522A (en) | Access control method and device | |
| CN112862487A (en) | Digital certificate authentication method, equipment and storage medium | |
| CN111726328B (en) | Method, system and related device for remotely accessing a first device | |
| CN112671844B (en) | Equipment registration method and system | |
| CN112087475B (en) | Message pushing method and device for cloud platform component application and message server | |
| US20190222582A1 (en) | Decentralized method of tracking user login status | |
| KR101395830B1 (en) | Session checking system via proxy and checkhing method thereof | |
| CN108228280A (en) | The configuration method and device of browser parameters, storage medium, electronic equipment | |
| CN113014610B (en) | Remote access method, device and system | |
| CN110048864B (en) | Method and apparatus for authenticating an administrator of a device-specific message group | |
| CN113489695A (en) | Private cloud networking method, device and system, computer equipment and storage medium | |
| CN111783044B (en) | Method and device for sharing login state | |
| CN115297066B (en) | Resource dynamic cooperation method, device, server and medium |
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 |