CN115426392B - Equipment network management method, device, equipment and storage medium - Google Patents

Equipment network management method, device, equipment and storage medium Download PDF

Info

Publication number
CN115426392B
CN115426392B CN202211361579.5A CN202211361579A CN115426392B CN 115426392 B CN115426392 B CN 115426392B CN 202211361579 A CN202211361579 A CN 202211361579A CN 115426392 B CN115426392 B CN 115426392B
Authority
CN
China
Prior art keywords
target
node
signaling
message middleware
equipment
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.)
Active
Application number
CN202211361579.5A
Other languages
Chinese (zh)
Other versions
CN115426392A (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.)
OP Retail Suzhou Technology Co Ltd
Original Assignee
OP Retail Suzhou 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 OP Retail Suzhou Technology Co Ltd filed Critical OP Retail Suzhou Technology Co Ltd
Priority to CN202211361579.5A priority Critical patent/CN115426392B/en
Publication of CN115426392A publication Critical patent/CN115426392A/en
Application granted granted Critical
Publication of CN115426392B publication Critical patent/CN115426392B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083Network architectures or network communication protocols for network security for authentication of entities using passwords
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application discloses a device network management method, a device and a storage medium, relates to the technical field of Internet of things, is applied to a target server, and comprises the following steps: when the redirection node acquires a target domain name which is sent by target equipment and is arranged in the target equipment, the redirection node is connected with the target equipment according to the target domain name, and acquires a client identifier of the target equipment uploaded by the target equipment; determining a target message middleware node corresponding to the target equipment according to the client identification, issuing the address of the target message middleware node to the target equipment, acquiring the client identification uploaded by the target equipment, authenticating the legality of the target equipment according to the client identification, and accepting the target equipment and keeping long connection with the target equipment if the authentication is passed. The method and the system can provide real-time and reliable message service for connecting remote equipment with few codes and limited bandwidth through the domain name built in the equipment and the redirection node and the message middleware node in the server.

Description

Equipment network management method, device, equipment and storage medium
Technical Field
The present application relates to the field of internet of things technologies, and in particular, to a method, an apparatus, a device, and a storage medium for managing a device network.
Background
MQTT (Message Queuing Telemetry Transport) is a client-server based Message publishing/subscribing (publish/subscribe) Transmission Protocol, which is constructed on TCP/IP (Transmission Control Protocol/Internet Protocol) Protocol, and has features of light weight, simplicity, openness and easy implementation, so that it has wider applications in aspects of Internet of Things (IoT), small devices, mobile applications, etc., such as Machine to Machine (M2M) communication in a limited environment, satellite link communication sensors, occasionally-dialed medical devices, etc.
However, although there are many MQTT Broker schemes implemented by technologies at present, such as mosquito (an open source message Broker), hiveMQ, emqx, and the like, the MQTT Broker schemes all strictly adopt a CS (Client/Server) architecture, and when applied to a service system, the service system is also used as an MQTT Client to communicate with other devices through the MQTT Broker, that is, the relationship between the service Server and the devices is equal, which causes many problems, such as that a single Server cannot perform fine authority control on topic (subject) of the device, cannot accurately control better load balance of the service system, and the like.
Therefore, how to effectively manage the network of devices by using MQTT Broker is a technical problem to be solved urgently by those skilled in the art.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a device network management method, apparatus, device and storage medium, which can provide a real-time and reliable message service for a connected remote device with very few codes and limited bandwidth. The specific scheme is as follows:
in a first aspect, the present application discloses a device network management method, which is applied to a target server including a redirection node and a message middleware node, and includes:
when the redirection node in the target server obtains a target domain name sent by target equipment, connecting the redirection node with the target equipment according to the target domain name; wherein the target domain name is embedded in the target device;
acquiring a client identifier of the target device uploaded by the target device through the redirection node, and determining a target message middleware node corresponding to the target device according to the client identifier so as to issue an address of the target message middleware node to the target device through the target message middleware node;
and acquiring the client identification uploaded by the target equipment through the target message middleware node, authenticating the legality of the target equipment according to the client identification, and accepting the target equipment if the authentication is passed and keeping long connection with the target equipment.
Optionally, the determining, according to the client identifier, a target message middleware node corresponding to the target device includes:
determining a target message middleware node corresponding to the target equipment from a routing information database according to the client identification; and the routing information database is positioned in the target server and stores message middleware nodes corresponding to each device according to a preset rule.
Optionally, after the long connection with the target device is maintained, the method further includes:
when a signaling proxy node receives a configuration management signaling from a service management system, inquiring configuration authority between the service management system and the target equipment in the routing information database according to the client identification carried in the configuration management signaling to obtain a first inquiry result; wherein the signaling proxy node is located in the target server;
if the first query result indicates that the transceiving between the service management system and the target device is allowed, forwarding the configuration management signaling to the target device;
after the signaling proxy node receives a response signaling returned by the target equipment, inquiring the configuration authority between the service management system and the target equipment in the routing information database according to the client identification carried in the response signaling to obtain a second inquiry result;
and if the second query result indicates that the service management system and the target device are allowed to receive and transmit, responding to the configuration management signaling.
Optionally, the forwarding the configuration management signaling to the target device includes:
and determining the target message middleware node corresponding to the target equipment in the routing information database according to the client identifier carried in the configuration management signaling, sending the configuration management signaling to the target message middleware node through an HTTP (hyper text transport protocol), and forwarding the configuration management signaling to the target equipment through the target message middleware node.
Optionally, the authenticating the legitimacy of the target device according to the client identifier includes:
and authenticating the legality of the target equipment by utilizing a Hash algorithm according to the client identification.
In a second aspect, the present application discloses an apparatus network management method, applied to a target apparatus, where a target domain name is built in the target apparatus, including:
connecting a redirection node in a target server based on the built-in target domain name; the target server comprises the redirection node and a message middleware node;
sending the client identifier of the target equipment to the redirection node so that the redirection node determines a target message middleware node corresponding to the target equipment according to the client identifier and returns the address of the target message middleware node to the target equipment;
after receiving the address returned by the redirection node, uploading the client identifier to the target message middleware node so that the target message middleware node authenticates the legality of the target equipment according to the client identifier;
and if the authentication is passed, maintaining long connection with the target message middleware node.
Optionally, after maintaining the long connection with the target message middleware node, the method further includes:
when receiving a configuration management signaling from a service management system forwarded by a signaling proxy node, sending a response signaling to the signaling proxy node so that the signaling proxy node queries a target configuration authority between the service management system and the target equipment in a routing information database according to the client identifier carried in the response signaling; the signaling agent node and the routing information database are located in the target server, and the routing information database stores message middleware nodes corresponding to each device according to a preset rule;
if the target configuration authority indicates that the service management system and the target equipment are allowed to receive and transmit, determining the target message middleware node corresponding to the target equipment from the routing information database through the signaling proxy node, and responding to the configuration management signaling through the target message middleware node.
In a third aspect, the present application discloses an apparatus for managing a device network, which is applied to a target server including a redirection node and a message middleware node, and includes:
the connection module is used for connecting with the target equipment according to the target domain name when the redirection node in the target server obtains the target domain name sent by the target equipment; wherein the target domain name is built in the target device;
a client identifier obtaining module, configured to obtain, through the redirection node, a client identifier of the target device uploaded by the target device;
the node determining module is used for determining a target message middleware node corresponding to the target equipment according to the client identification;
the address issuing module is used for issuing the address of the target message middleware node to the target equipment through the target message middleware node;
the client identifier acquisition module is used for acquiring the client identifier uploaded by the target equipment through the target message middleware node;
the legality authentication module is used for authenticating the legality of the target equipment according to the client terminal identification;
and the long connection module is used for accepting the target equipment if the authentication is passed and keeping long connection with the target equipment.
In a fourth aspect, the present application discloses an electronic device comprising a processor and a memory; wherein the processor implements the aforementioned device network management method when executing the computer program stored in the memory.
In a fifth aspect, the present application discloses a computer readable storage medium for storing a computer program; wherein the computer program when executed by a processor implements the aforementioned device network management method.
The method is applied to a target server comprising a redirection node and a message middleware node, when the redirection node in the target server obtains a target domain name which is sent by a target device and is arranged in the target device, the redirection node is connected with the target device according to the target domain name, then a client identifier of the target device uploaded by the target device is obtained through the redirection node, the target message middleware node corresponding to the target device is determined according to the client identifier, so that the address of the target message middleware node is sent to the target device through the target message middleware node, the client identifier uploaded by the target device is obtained through the target message middleware node, the legality of the target device is authenticated according to the client identifier, and if the authentication is passed, the target device is accepted and is kept in long connection with the target device. The method uses the traditional MQTT Broker design idea, combines practical services to carry out massive reconstruction and transformation, and designs the equipment network management method which is more suitable for the service production environment. By keeping the target message middleware node and the target equipment in long connection, real-time and reliable message service can be provided for connecting remote equipment by using few codes and limited bandwidth, further refined authority control is performed on the equipment, the authority between services and the equipment is more hierarchical, communication control between the equipment and the equipment is more flexible, a redirection node is connected by using a domain name built in the equipment to determine the target message middleware node, the legality of the target equipment is authenticated by using a client identifier, dynamic password verification is realized, and authentication is safer.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a device network management method disclosed in the present application;
FIG. 2 is a block diagram of a specific device network management method disclosed herein;
FIG. 3 is a flow chart of a specific device network management method disclosed herein;
fig. 4 is a schematic structural diagram of an apparatus network management device disclosed in the present application;
fig. 5 is a schematic structural diagram of an apparatus network management device disclosed in the present application;
fig. 6 is a block diagram of an electronic device disclosed in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The embodiment of the application discloses a device network management method, which is applied to a target server comprising a redirection node and a message middleware node, and is shown in fig. 1, and the method comprises the following steps:
step S11: when the redirection node in the target server obtains a target domain name sent by target equipment, connecting the redirection node with the target equipment according to the target domain name; wherein the target domain name is embedded in the target device.
In this embodiment, when a redirection node in a target server obtains a target domain name which is sent by a target device and is built in the target device, a connection relationship is established with the target device according to the target domain name; the target device includes, but is not limited to, an IPC (IP CAMERA) device, an NVR (Network Video Recorder) device, and the like.
It should be noted that, in this embodiment, in order to prevent a single node device in the target server from being unable to bear a large number of device connections, a redirection node is set in the target server, and the redirection node is only used for a redirection function and has a unique domain name, and the unique domain name is built in when the target device leaves a factory; in addition, the target server further includes a message middleware node, where the number of the message middleware nodes may be one or multiple, and specifically may be a message middleware node supporting the MQTT protocol.
Step S12: and acquiring the client identifier of the target equipment uploaded by the target equipment through the redirection node, and determining a target message middleware node corresponding to the target equipment according to the client identifier so as to issue the address of the target message middleware node to the target equipment through the target message middleware node.
In this embodiment, after a redirection node in a target server is connected to a target device according to a target domain name, the target device uploads a Client identifier (Client ID) of the target device to the redirection node, and after the redirection node acquires the Client identifier uploaded by the target device, a target message middleware node corresponding to the target device may be determined according to the Client identifier, and then, the target device and the target message middleware node perform handshake connection using MQTT protocol, and then, the target message middleware node issues an address of the target message middleware node to the target device.
In a specific implementation manner, the determining, according to the client identifier, a target message middleware node corresponding to the target device may specifically include: determining a target message middleware node corresponding to the target equipment from a routing information database according to the client identification; and the routing information database is positioned in the target server and stores message middleware nodes corresponding to each device according to a preset rule. That is, the corresponding relationship between the client identifier and the message middleware node is pre-stored in the routing information database of the target server, so that after the redirection node acquires the client identifier uploaded by the target device, a target message middleware node corresponding to the target device can be determined from the routing information database directly according to the client identifier.
Step S13: and acquiring the client identification uploaded by the target equipment through the target message middleware node, authenticating the legality of the target equipment according to the client identification, and accepting the target equipment if the authentication is passed and keeping long connection with the target equipment.
In this embodiment, after receiving the address issued by the target message middleware node, the target device sends the client identifier to the target message middleware node, and after receiving the handshake message that includes the client identifier and is uploaded by the target device, the target message middleware node first determines whether the target device is a legitimate device, and if the target device is a legitimate device, accepts the target device, and keeps a long connection between the target message middleware node and the target device, such as a long connection between a TCP and the target device. In this embodiment, a device network management method is designed to be more suitable for a service production environment by using a traditional MQTT Broker design idea and combining with actual services to perform a large amount of reconstruction and reconstruction, and a target message middleware node is kept in long connection with a target device, so that a real-time and reliable message service can be provided for connecting a remote device with few codes and limited bandwidth.
Specifically, the authenticating the legitimacy of the target device according to the client identifier may specifically include: and authenticating the legality of the target equipment by utilizing a Hash algorithm according to the client identification. In a specific implementation manner, the method may first calculate an authentication password of a target device based on a Hash algorithm (Hash) by using key information built in the target device to obtain a first authentication password, and send the first authentication password and the key information to the target message middleware node; and then the target message middleware node calculates an authentication password of the target message middleware node by using the key information and based on the Hash algorithm to obtain a second authentication password, then judges whether the first authentication password is consistent with the second authentication password, and if so, judges that the target equipment is legal. For example, the built-in key information and the current standard time are obtained through the target equipment, the authentication password of the equipment is calculated by using a Hash algorithm to obtain a first authentication password, and then the first authentication password and the key information are sent to the target message middleware node through the target equipment; after the target message middleware node acquires the first authentication password and the key information, firstly, the key information is utilized and an authentication password of the node (namely, the target message middleware node) is calculated based on the Hash algorithm to obtain a second authentication password, then whether the first authentication password and the second authentication password are consistent or not is judged, and if yes, the target equipment is directly judged to be legal equipment. The key information includes, but is not limited to, a client identifier of the target device, a client ID of the MQTT, a preset confusion string, and the like. The method and the device authenticate the legality of the target equipment by using the client identification and utilizing the Hash algorithm, thereby realizing dynamic password verification and ensuring that the authentication is safer.
Further, after the long connection with the target device is maintained, the method specifically includes: when a signaling proxy node receives a configuration management signaling from a service management system, inquiring configuration authority between the service management system and the target equipment in the routing information database according to the client identification carried in the configuration management signaling to obtain a first inquiry result; wherein the signaling proxy node is located in the target server; if the first query result indicates that the transceiving between the service management system and the target device is allowed, forwarding the configuration management signaling to the target device; after the signaling proxy node receives a response signaling returned by the target equipment, inquiring the configuration authority between the service management system and the target equipment in the routing information database according to the client identification carried in the response signaling to obtain a second inquiry result; and if the second query result indicates that the service management system and the target device are allowed to receive and transmit, responding to the configuration management signaling. Specifically, referring to fig. 2, fig. 2 shows a specific process of device networking, where the redirection node is used to connect to a device and transmit a client identifier of an MQTT message middleware node corresponding to the device, the device acquires the client identifier and then connects to the MQTT message middleware node, authenticates the MQTT message middleware node, and after the authentication is passed, the device connects to the MQTT message middleware node. When the signaling proxy node receives the configuration management signaling transmitted from the service group, an MQTT message middleware node is determined, then the configuration management signaling is sent to the equipment which establishes the connection relation through the determined MQTT message middleware node, and after the equipment receives the configuration management signaling sent by the MQTT message middleware node, the equipment can send the message to the service group through the corresponding MQTT message middleware node. In addition, the Broker node can also store the generated log and the alarm information into a log database. In a specific embodiment, after the MQTT message middleware node is in long connection with the target device, when a signaling proxy node in the target server acquires a configuration management signaling (for example, setting a resolution, a code rate, and the like of an IPC device) sent from a service management system, a configuration authority between the service management system and the target device is queried in a routing information database according to a client identifier carried in the configuration management signaling to obtain a corresponding query result, that is, the first query result, if the first query result indicates that transceiving between the service management system and the target device is permitted, the configuration management signaling is directly forwarded to the target device, further, after the signaling proxy node receives a response signaling returned by the target device, the configuration authority between the service management system and the target device is queried in the routing information database according to the client identifier carried in the response signaling to obtain a corresponding second query result, and if the second query result indicates that transceiving between the service management system and the target device is permitted, the configuration management signaling is responded. According to the method and the device, the configuration authority between the service management system and the target device is stored in the routing information database in advance, so that the device can be subjected to refined authority control, the authority between the service and the device is more hierarchical, and the communication control between the device and the device is more flexible.
Specifically, the forwarding the configuration management signaling to the target device may include: and determining the target message middleware node corresponding to the target equipment in the routing information database according to the client identifier carried in the configuration management signaling, sending the configuration management signaling to the target message middleware node through an HTTP (hyper text transport protocol), and forwarding the configuration management signaling to the target equipment through the target message middleware node. It can be understood that, since the target message middleware node and the target device have maintained a long connection, when the service management system and the target device are allowed to receive and transmit, a target message middleware node corresponding to the target device may be determined and initiated with a remote call through a redirection node and according to a client identifier carried in a configuration management signaling, and then the configuration management signaling may be sent to the target message middleware node through an HTTP (Hyper Text Transfer Protocol) Protocol, and then forwarded to the target device through the target message middleware node. It should be noted that, because the service management system sends the signaling Message to the signaling proxy node through the HTTP protocol, and the signaling proxy node may determine a target Message middleware node corresponding to the target device, and the target Message middleware node and the target device may perform data communication through the MQTT protocol, conversion of the HTTP protocol is implemented, that is, the HTTP Message may be converted into an MQTT Message for transmission, and thus, conversion of a Will Message (willmessage) which is provided by the MQTT protocol for a device that may have an unexpected disconnection and provides an ability to send the Will to a third party elegantly, and the unexpected disconnection includes, but is not limited to, a failure of the device to communicate during a connection maintaining period due to a network failure or a network fluctuation, an unexpected connection being closed by a service end, an unexpected power down of the device, an attempt of the device to perform an unauthorized operation, and a connection being closed by the service end, such as subscribing to a theme (topic) other than the service end, may also be implemented.
Furthermore, in order to facilitate subsequent troubleshooting and tracing, the configuration management signaling and all other generated signaling messages can be stored in a log database of the target server; in addition, information such as MQTT message logs, log of online and offline of the target device, HTTP alarm messages pushed online and offline can be stored in the log database.
It should be noted that, multiple listening ports, such as TCP encrypted and TCP unencrypted, sub-signed certificate and TLS (Transport Layer Security protocol) supporting public certificate or private root certificate, may also be configured at the same time by the target server including the redirection node and MQTT message middleware node. In summary, the target server in this embodiment may load more devices by including multiple MQTT message middleware nodes, thereby implementing load balancing. As can be seen from the above, in this embodiment, the target server can be configured with a plurality of monitoring ports simultaneously through the MQTT message middleware node, and fine topic management is also supported, so that the authority between the service and the device is more hierarchical, and the communication control between the devices is more flexible; when a plurality of MQTT message middleware nodes exist, more equipment can be loaded, so that load balance is realized; in addition, the conversion of the HTTP protocol is provided, and the HTTP message can be converted into the MQTT message for transmission.
The method and the device are applied to a target server comprising a redirection node and a message middleware node, when the redirection node in the target server obtains a target domain name which is sent by a target device and is arranged in the target device, the redirection node is connected with the target device according to the target domain name, then a client identifier of the target device uploaded by the target device is obtained through the redirection node, the target message middleware node corresponding to the target device is determined according to the client identifier, so that the address of the target message middleware node is sent to the target device through the target message middleware node, the client identifier uploaded by the target device is obtained through the target message middleware node, the legality of the target device is authenticated according to the client identifier, and if the authentication is passed, the target device is received and is in long connection with the target device. The embodiment of the application uses the traditional MQTT Broker design idea, combines with actual services to carry out a large amount of reconstruction and reconstruction, and designs an equipment network management method which is more suitable for service production environment. By keeping the target message middleware node and the target equipment in long connection, real-time and reliable message service can be provided for connecting remote equipment by using few codes and limited bandwidth, further refined authority control is performed on the equipment, the authority between services and the equipment is more hierarchical, communication control between the equipment and the equipment is more flexible, a redirection node is connected by using a domain name built in the equipment to determine the target message middleware node, the legality of the target equipment is authenticated by using a client identifier, dynamic password verification is realized, and authentication is safer.
The embodiment of the application discloses a specific device network management method, which is applied to a target device, wherein a target domain name is built in the target device, and the method is shown in fig. 3 and comprises the following steps:
step S21: connecting a redirection node in a target server based on the built-in target domain name; wherein, the target server comprises the redirection node and the message middleware node.
In this embodiment, a redirection node in a target server is connected based on a target domain name area built in a target device when the target device leaves a factory. It should be noted that the target server includes a message middleware node in addition to the redirection node, and a one-to-one correspondence exists between the message middleware node and the device; the target device includes, but is not limited to, an IPC device, an NVR device, and the like.
Step S22: and sending the client identifier of the target equipment to the redirection node so that the redirection node determines a target message middleware node corresponding to the target equipment according to the client identifier and returns the address of the target message middleware node to the target equipment.
In this embodiment, after connecting to a redirection node in a target server based on a built-in target domain name, further sending a client identifier of the target device to the redirection node, where after receiving the client identifier sent by the target device, the redirection node may determine a target message middleware node corresponding to the target device according to the client identifier, and then return an address of the target message middleware node to the target device. In a specific implementation manner, the redirection node may determine, according to the client identifier, a target message middleware node corresponding to the target device from a routing information database located in a target server, that is, a correspondence between the message middleware node and the device is pre-stored in the routing information database. It should be noted that the target device may send the client identifier of the target device to the redirection node through the HTTP protocol, that is, information may be transferred between the target device and the redirection node through the HTTP protocol.
Step S23: and after receiving the address returned by the redirection node, uploading the client identifier to the target message middleware node so that the target message middleware node authenticates the legality of the target equipment according to the client identifier.
In this embodiment, after receiving the address returned by the redirection node, the target device further uploads the address to the target message middleware node, and then the target message middleware node may authenticate the legitimacy of the target device according to the client identifier. For example, the target device calculates an authentication password of the target device based on a preset hash algorithm according to the current standard time and by combining built-in key information (such as a client identifier, a preset confusion string and the like), then performs handshake connection with a target MQTT message middleware node by using an MQTT protocol, and reports the authentication password of the target device and the key information to the target MQTT message middleware node.
Step S24: and if the authentication is passed, maintaining long connection with the target message middleware node.
In this embodiment, if the authentication is passed, the target device and the target message middleware node maintain a long TCP connection.
Further, after maintaining the long connection with the target message middleware node, the method specifically further includes: when receiving a configuration management signaling from a service management system forwarded by a signaling proxy node, sending a response signaling to the signaling proxy node so that the signaling proxy node queries a target configuration authority between the service management system and the target equipment in a routing information database according to the client identifier carried in the response signaling; the signaling agent node and the routing information database are located in the target server, and the routing information database stores message middleware nodes corresponding to each device according to a preset rule; if the target configuration authority indicates that the service management system and the target equipment are allowed to receive and transmit, determining the target message middleware node corresponding to the target equipment from the routing information database through the signaling proxy node, and responding to the configuration management signaling through the target message middleware node. For example, when the IPC device receives a configuration management signaling such as resolution, code rate, etc. from the IPC device setting up the IPC device forwarded by the signaling proxy node in the target server, a response signaling receiving the configuration management signaling is sent to the signaling proxy node, after the signaling proxy node receives the response signaling, the signaling proxy node further queries the configuration right between the service management system and the IPC device in the routing information database in the target server according to the client identifier of the IPC device built in the IPC device carried in the response signaling, if the configuration right indicates that transceiving between the service management system and the IPC device is allowed, a target MQTT message middleware node corresponding to the IPC device is determined from the routing information database by the signaling proxy node, and a Remote call is initiated to the target MQTT message middleware node by the signaling proxy node, such as a gRPC (gRPC Remote Procedure call, which is an open source Remote Procedure call system initiated by Google), and then the target MQTT message middleware node responds to the configuration management signaling. It should be noted that, the routing information database stores MQTT message middleware nodes corresponding to each device according to a preset rule, where the preset rule includes, but is not limited to, determining a range of legal instructions or determining a range of illegal instructions that may be issued from a service management system to the device or the device; in addition, the routing information database also stores configuration permissions, such as topic (topic) transceiving permissions, which are allocated to the device by the MQTT message middleware node based on the preset rules, wherein topic (a message type identifier) is a transmission medium between a Pub (Pub) and a Sub (Sub) and the device can send and receive messages through topic, so that the communication between the server and the device is realized, and the control on topic is mainly performed according to database matching of MQTT client IDs of the device and then according to the matched permissions.
In a specific application scene, the transceiving authorities between a plurality of devices and a service management system can be configured, the configuration of the transceiving authorities is fine and hierarchical, and the defect that one device can only be fixedly connected with one server in the prior art can be overcome, so that one device corresponds to one MQTT message middleware node, a plurality of devices correspond to the transceiving authorities of different MQTT message middleware nodes, and the transceiving authorities of a single device are more finely configured; in addition, due to the fact that legal topics are arranged between the service layer and the equipment layer, the authority between the service and the equipment is more hierarchical, and communication control between the equipment is more flexible.
In a specific embodiment, the topic type format may specifically be formed by an instruction defined by a preset rule and a client identifier. If legal instructions from the service management system to the equipment:
subject matter: 12/reboot
Data: { "action": reboot "}
The service can be sent out: elogger/(beginning)
Illegal command issued by the device:
subject matter: 12/topoic _ demo/12
Data: { "password": admin "}
The instructions the device is allowed to issue: monitor (initial)/\8230
The path of the theme determines which devices can send and which devices cannot send, thereby embodying the management of the authority.
For more specific processing procedures of the above steps, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not repeated here.
It can be seen that the embodiment of the present application is applied to a target device with a built-in target domain name, the target device connects to a redirection node in a target server through the built-in target domain name, then sends a client identifier of the target device to the redirection node, then the redirection node determines a target message middleware node corresponding to the target device according to the client identifier, returns an address of the target message middleware node to the target device, and uploads the client identifier to the target message middleware node after the target device receives the address returned by the redirection node, so that the target message middleware node authenticates the legitimacy of the target device according to the client identifier, and actively maintains long connection with the target message middleware node if the authentication is passed. The embodiment of the application uses the traditional MQTT Broker design idea, combines with actual services to carry out a large amount of reconstruction and reconstruction, and designs an equipment network management method which is more suitable for service production environment. The long connection between the target message middleware node and the target device is kept through the redirection node, and the real-time reliable message service can be provided for the connected remote device with few codes and limited bandwidth. Compared with the static password of the traditional MQTT Broker server, the equipment network management scheme provided by the application has the advantages that the domain name is built in the equipment, and the domain name is used for connecting the redirection node so as to determine the message middleware node and authenticate the legality of the target equipment, so that the dynamic password verification is realized, and the authentication is safer.
In a specific implementation manner, a specific process flow for implementing a long connection from a device side to a server side is as follows: the equipment is connected with a redirection node according to a built-in domain name, a client identifier, namely a client id, of the equipment is uploaded, then the redirection node is inquired in a routing information database according to the client id, if the inquiry is received, the address of the MQTT message middleware node is sent to the equipment, after the equipment acquires the address of the MQTT message middleware node, the client id of the equipment is uploaded to the MQTT message middleware node, then the MQTT message middleware node carries out authentication according to the client id, whether the equipment is legal or not is judged, and if the equipment is legal, the equipment is accepted and is kept in long connection with the equipment.
Further, a specific processing flow for realizing signaling forwarding from the server side to the device side is as follows: when a signaling agent node receives a configuration management signaling from a service management system, wherein the configuration management signaling comprises a client id of a device, firstly, a routing information database is inquired for configuration permission according to the client id, whether the configuration permission can be sent to the device is judged, and if the configuration permission can be sent to the device, the configuration management signaling is sent to the corresponding device; after the signaling proxy node receives the response signaling from the equipment, the configuration authority is inquired in the routing information database according to the client id contained in the response signaling, and whether the configuration management signaling is responded or not is judged.
In some specific embodiments, long connection is realized between a plurality of devices with the unique domain name of the built-in redirection node and a plurality of MQTT message middleware nodes through the redirection node, signaling forwarding is realized through the signaling proxy node, and an equipment network management system capable of performing fine authority control, load balancing and high safety on the topic of the equipment is formed.
Correspondingly, an embodiment of the present application further discloses an apparatus for device network management, which is applied to a target server including a redirection node and a message middleware node, and as shown in fig. 4, the apparatus includes:
the connection module 11 is configured to, when the redirection node in the target server obtains a target domain name sent by a target device, connect with the target device according to the target domain name; wherein the target domain name is embedded in the target device;
a client identifier obtaining module 12, configured to obtain, through the redirection node, a client identifier of the target device uploaded by the target device;
a node determining module 13, configured to determine, according to the client identifier, a target message middleware node corresponding to the target device;
an address issuing module 14, configured to issue, by using the target message middleware node, an address of the target message middleware node to the target device;
a client identifier obtaining module 15, configured to obtain, through the target message middleware node, the client identifier uploaded by the target device;
a validity authentication module 16, configured to authenticate the validity of the target device according to the client identifier;
and the long connection module 17 is used for accepting the target equipment if the authentication is passed and keeping long connection with the target equipment.
For the specific work flow of each module, reference may be made to corresponding content disclosed in the foregoing embodiments, and details are not repeated here.
The method and the device are applied to a target server comprising a redirection node and a message middleware node, when the redirection node in the target server obtains a target domain name which is sent by a target device and is arranged in the target device, the redirection node is connected with the target device according to the target domain name, then a client identifier of the target device uploaded by the target device is obtained through the redirection node, the target message middleware node corresponding to the target device is determined according to the client identifier, so that the address of the target message middleware node is sent to the target device through the target message middleware node, the client identifier uploaded by the target device is obtained through the target message middleware node, the legality of the target device is authenticated according to the client identifier, and if the authentication is passed, the target device is received and is in long connection with the target device. The embodiment of the application uses the traditional MQTT Broker design idea, combines with actual services to carry out a large amount of reconstruction and reconstruction, and designs an equipment network management method which is more suitable for service production environment. By keeping the target message middleware node and the target equipment in long connection, real-time and reliable message service can be provided for connecting remote equipment by using few codes and limited bandwidth, further refined authority control is performed on the equipment, the authority between services and the equipment is more hierarchical, communication control between the equipment and the equipment is more flexible, a redirection node is connected by using a domain name built in the equipment to determine the target message middleware node, the legality of the target equipment is authenticated by using a client identifier, dynamic password verification is realized, and authentication is safer.
In some specific embodiments, the node determining module 13 may specifically include:
a first message middleware node determining unit, configured to determine, according to the client identifier, a target message middleware node corresponding to the target device from a routing information database; the routing information database is located in the target server and stores MQTT message middleware nodes corresponding to each device according to a preset rule.
In some specific embodiments, after the long connection module 17, the method may further include:
a first configuration authority query unit, configured to, when a signaling proxy node receives a configuration management signaling from a service management system, query, according to the client identifier carried in the configuration management signaling, a configuration authority between the service management system and the target device in the routing information database, so as to obtain a first query result; wherein the signaling proxy node is located in the target server;
a first signaling sending unit, configured to forward the configuration management signaling to the target device if the first query result indicates that transceiving between the service management system and the target device is allowed;
a second configuration authority query unit, configured to, after the signaling proxy node receives a response signaling returned by the target device, query, according to the client identifier carried in the response signaling, a configuration authority between the service management system and the target device in the routing information database, and obtain a second query result;
a first signaling response unit, configured to respond to the configuration management signaling if the second query result indicates that transceiving is allowed between the service management system and the target device.
In some specific embodiments, the first signaling forwarding unit may specifically include:
a second message middleware node determining unit, configured to determine, according to the client identifier carried in the configuration management signaling, the target message middleware node corresponding to the target device from the routing information database;
a second signaling sending unit, configured to send the configuration management signaling to the target message middleware node through an HTTP protocol;
a third signaling sending unit, configured to forward the configuration management signaling to the target device through the target message middleware node.
In some specific embodiments, the validity authentication module 16 may specifically include:
and the legality authentication unit is used for authenticating the legality of the target equipment by utilizing a Hash algorithm according to the client identification.
In addition, an embodiment of the present application further discloses an apparatus network management device, which is applied to a target device, where a target domain name is built in the target device, as shown in fig. 5, the apparatus includes:
a redirection node connection module 110, configured to connect a redirection node in a target server based on the built-in target domain name; the target server comprises the redirection node and a message middleware node;
a client identifier sending module 112, configured to send the client identifier of the target device to the redirection node;
a middleware node determining module 113, configured to determine, by using the redirection node and according to the client identifier, a target message middleware node corresponding to the target device;
an address return module 114, configured to return the address of the target message middleware node to the target device;
a client identifier uploading module 115, configured to upload the client identifier to the target message middleware node after receiving the address returned by the redirection node;
a validity authentication module 116, configured to authenticate the validity of the target device through the target message middleware node according to the client identifier;
a long connection module 117 for maintaining a long connection with the target message middleware node if authentication passes.
For the specific work flow of each module, reference may be made to corresponding content disclosed in the foregoing embodiments, and details are not repeated here.
It can be seen that, when the embodiment of the present application is applied to a target device, a redirection node in a target server is connected based on a built-in target domain name, then a client identifier of the target device is sent to the redirection node, so that the redirection node determines a target message middleware node corresponding to the target device according to the client identifier, returns an address of the target message middleware node to the target device, and uploads the client identifier to the target message middleware node after receiving the address returned by the redirection node, so that the target message middleware node authenticates the legitimacy of the target device according to the client identifier, and if the authentication is passed, the target device is kept in long connection with the target message middleware node. According to the embodiment of the application, the target message middleware node is kept in long connection with the target equipment through the target domain name arranged in the target equipment and the redirection node arranged in the server, real-time and reliable message service can be provided for connecting remote equipment by using few codes and limited bandwidth, the legality of the target equipment is authenticated by using the client identification, dynamic password verification is realized, and authentication is safer.
In some specific embodiments, after the long connection module 117, the method may further include:
a configuration authority query unit, configured to send a response signaling to a signaling proxy node when receiving a configuration management signaling from a service management system forwarded by the signaling proxy node, so that the signaling proxy node queries a target configuration authority between the service management system and the target device in a routing information database according to the client identifier carried in the response signaling; the signaling agent node and the routing information database are located in the target server, and the routing information database stores message middleware nodes corresponding to each device according to a preset rule;
a message middleware node determining unit, configured to determine, if the target configuration permission indicates that transceiving between the service management system and the target device is permitted, the target message middleware node corresponding to the target device from the routing information database through the signaling proxy node;
and the signaling response unit is used for responding the configuration management signaling through the target message middleware node.
Further, an electronic device is disclosed in the embodiments of the present application, and fig. 6 is a block diagram of an electronic device 20 according to an exemplary embodiment, which should not be construed as limiting the scope of the application.
Fig. 6 is a schematic structural diagram of an electronic device 20 according to an embodiment of the present disclosure. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input output interface 25, and a communication bus 26. Wherein, the memory 22 is used for storing a computer program, and the computer program is loaded and executed by the processor 21 to implement the relevant steps in the device network management method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in the present embodiment may be specifically an electronic computer.
In this embodiment, the power supply 23 is configured to provide a working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and a communication protocol followed by the communication interface is any communication protocol applicable to the technical solution of the present application, and is not specifically limited herein; the input/output interface 25 is configured to obtain external input data or output data to the outside, and a specific interface type thereof may be selected according to specific application requirements, which is not specifically limited herein.
In addition, the storage 22 is used as a carrier for storing resources, and may be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc., and the resources stored thereon may include an operating system 221, a computer program 222, etc., and the storage manner may be a transient storage manner or a permanent storage manner.
The operating system 221 is used for managing and controlling each hardware device on the electronic device 20 and the computer program 222, and may be Windows Server, netware, unix, linux, or the like. The computer program 222 may further include a computer program that can be used to perform other specific tasks in addition to the computer program that can be used to perform the device network management method performed by the electronic device 20 disclosed in any of the foregoing embodiments.
Further, the present application also discloses a computer-readable storage medium for storing a computer program; wherein the computer program when executed by a processor implements the device network management method disclosed above. For the specific steps of the method, reference may be made to the corresponding contents disclosed in the foregoing embodiments, which are not described herein again.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it should also be noted that, herein, 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. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
The above detailed description is provided for a device network management method, apparatus, device and storage medium, and a specific example is applied in the description to explain the principle and implementation of the present application, and the description of the above embodiment is only used to help understanding the method and core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, the specific implementation manner and the application scope may be changed, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims (10)

1. The device network management method is applied to a target server containing a redirection node and an MQTT message middleware node, and comprises the following steps:
when the redirection node in the target server obtains a target domain name sent by target equipment, connecting the redirection node with the target equipment according to the target domain name; wherein the target domain name is embedded in the target device;
acquiring a client identifier of the target device uploaded by the target device through the redirection node, and determining a target MQTT message middleware node corresponding to the target device according to the client identifier so as to issue the address of the target MQTT message middleware node to the target device through the target MQTT message middleware node;
acquiring the client identification uploaded by the target equipment through the target MQTT message middleware node, authenticating the legality of the target equipment according to the client identification, and if the authentication is passed, receiving the target equipment and keeping long connection with the target equipment;
inquiring the configuration authority between a service management system and the target equipment to obtain a first inquiry result, determining whether to allow a configuration management signaling to be forwarded to the target equipment according to the first inquiry result, if so, forwarding the configuration management signaling to the target equipment, inquiring the configuration authority between the service management system and the target equipment to obtain a second inquiry result after receiving a response signaling returned by the target equipment, and determining whether to respond to the configuration management signaling according to the second inquiry result.
2. The device network management method according to claim 1, wherein the determining a target MQTT message middleware node corresponding to the target device according to the client identifier comprises:
determining a target MQTT message middleware node corresponding to the target equipment from a routing information database according to the client identification; the routing information database is located in the target server and stores MQTT message middleware nodes corresponding to each device according to a preset rule.
3. The device network management method according to claim 2, wherein the querying a configuration right between the service management system and the target device to obtain a first query result, and determining whether to allow a configuration management signaling to be forwarded to the target device according to the first query result, if so, forwarding the configuration management signaling to the target device, and after receiving a response signaling returned by the target device, querying the configuration right between the service management system and the target device to obtain a second query result, and determining whether to respond to the configuration management signaling according to the second query result, includes:
when a signaling proxy node receives a configuration management signaling from a service management system, inquiring configuration authority between the service management system and the target equipment in the routing information database according to the client identification carried in the configuration management signaling to obtain a first inquiry result; wherein the signaling proxy node is located in the target server;
if the first query result indicates that the transceiving between the service management system and the target equipment is allowed, forwarding the configuration management signaling to the target equipment;
after the signaling proxy node receives a response signaling returned by the target equipment, inquiring the configuration authority between the service management system and the target equipment in the routing information database according to the client identification carried in the response signaling to obtain a second inquiry result;
and if the second query result indicates that the service management system and the target device are allowed to receive and transmit, responding to the configuration management signaling.
4. The device network management method of claim 3, wherein the forwarding the configuration management signaling to the target device comprises:
and determining the target MQTT message middleware node corresponding to the target equipment in the routing information database according to the client identifier carried in the configuration management signaling, sending the configuration management signaling to the target MQTT message middleware node through an HTTP (hyper text transport protocol), and forwarding the configuration management signaling to the target equipment through the target MQTT message middleware node.
5. The device network management method according to any one of claims 1 to 4, wherein said authenticating the legitimacy of the target device according to the client identifier comprises:
and authenticating the legality of the target equipment by utilizing a Hash algorithm according to the client identification.
6. The device network management method is applied to a target device, wherein a target domain name is built in the target device, and comprises the following steps:
connecting a redirection node in a target server based on the built-in target domain name; the target server comprises the redirection node and an MQTT message middleware node;
sending the client identification of the target equipment to the redirection node so that the redirection node can determine a target MQTT message middleware node corresponding to the target equipment according to the client identification and return the address of the target MQTT message middleware node to the target equipment;
after receiving the address returned by the redirection node, uploading the client identifier to the target MQTT message middleware node so that the target MQTT message middleware node authenticates the legality of the target equipment according to the client identifier;
if the authentication is passed, the long connection is kept with the target MQTT message middleware node;
when receiving a configuration management signaling from a service management system forwarded by a signaling proxy node, sending a response signaling to the signaling proxy node, so that the signaling proxy node queries a target configuration authority between the service management system and the target device according to the response signaling, and determines whether to respond to the configuration management signaling according to the target configuration authority.
7. The device network management method according to claim 6, wherein the sending a response signaling to the signaling proxy node when receiving the configuration management signaling from the service management system forwarded by the signaling proxy node, so that the signaling proxy node queries a target configuration right between the service management system and the target device according to the response signaling, and determines whether to respond to the configuration management signaling according to the target configuration right, comprises:
when receiving a configuration management signaling from a service management system forwarded by a signaling proxy node, sending a response signaling to the signaling proxy node so that the signaling proxy node queries a target configuration authority between the service management system and the target equipment in a routing information database according to the client identifier carried in the response signaling; the signaling proxy node and the routing information database are located in the target server, and the routing information database stores MQTT message middleware nodes corresponding to each device according to a preset rule;
if the target configuration authority indicates that the service management system and the target equipment are allowed to receive and transmit, determining the target MQTT message middleware node corresponding to the target equipment from the routing information database through the signaling proxy node, and responding to the configuration management signaling through the target MQTT message middleware node.
8. The device network management device is applied to a target server containing a redirection node and an MQTT message middleware node, and comprises the following steps:
the connection module is used for connecting with the target equipment according to the target domain name when the redirection node in the target server obtains the target domain name sent by the target equipment; wherein the target domain name is embedded in the target device;
a client identifier obtaining module, configured to obtain, through the redirection node, a client identifier of the target device uploaded by the target device;
the node determining module is used for determining a target MQTT message middleware node corresponding to the target equipment according to the client identification;
the address issuing module is used for issuing the address of the target MQTT message middleware node to the target equipment through the target MQTT message middleware node;
the client identification acquisition module is used for acquiring the client identification uploaded by the target equipment through the target MQTT message middleware node;
the legality authentication module is used for authenticating the legality of the target equipment according to the client terminal identification;
the long connection module is used for accepting the target equipment if the authentication is passed and keeping long connection with the target equipment;
the long connection module is further configured to query a configuration authority between the service management system and the target device to obtain a first query result, determine whether to allow the configuration management signaling to be forwarded to the target device according to the first query result, forward the configuration management signaling to the target device if the configuration management signaling is allowed to be forwarded to the target device, query the configuration authority between the service management system and the target device to obtain a second query result after receiving a response signaling returned by the target device, and determine whether to respond to the configuration management signaling according to the second query result.
9. An electronic device comprising a processor and a memory; wherein the processor, when executing the computer program stored in the memory, implements the device network management method of any of claims 1 to 7.
10. A computer-readable storage medium for storing a computer program; wherein the computer program when executed by a processor implements the device network management method of any of claims 1 to 7.
CN202211361579.5A 2022-11-02 2022-11-02 Equipment network management method, device, equipment and storage medium Active CN115426392B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211361579.5A CN115426392B (en) 2022-11-02 2022-11-02 Equipment network management method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211361579.5A CN115426392B (en) 2022-11-02 2022-11-02 Equipment network management method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN115426392A CN115426392A (en) 2022-12-02
CN115426392B true CN115426392B (en) 2023-03-24

Family

ID=84207657

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211361579.5A Active CN115426392B (en) 2022-11-02 2022-11-02 Equipment network management method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN115426392B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114268667A (en) * 2021-12-20 2022-04-01 中国平安财产保险股份有限公司 Data forwarding method and device, computer equipment and storage medium

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112468527B (en) * 2019-09-06 2022-07-15 比亚迪股份有限公司 Linkage control system and linkage control method
EP3965387A1 (en) * 2020-09-04 2022-03-09 Siemens Aktiengesellschaft Method and system for communication between clients in a distributed industrial environment
CN114490100B (en) * 2020-10-27 2024-06-04 中移物联网有限公司 Message queue telemetry transmission load balancing method, device and server
CN113709263B (en) * 2021-11-01 2022-03-18 深圳市城市交通规划设计研究中心股份有限公司 Data access method of Internet of things protocol MQTT, computer and storage medium
CN114157693A (en) * 2021-11-30 2022-03-08 四川虹美智能科技有限公司 Power-on authentication method of communication equipment, communication module and server

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114268667A (en) * 2021-12-20 2022-04-01 中国平安财产保险股份有限公司 Data forwarding method and device, computer equipment and storage medium

Also Published As

Publication number Publication date
CN115426392A (en) 2022-12-02

Similar Documents

Publication Publication Date Title
US10791506B2 (en) Adaptive ownership and cloud-based configuration and control of network devices
US11936786B2 (en) Secure enrolment of security device for communication with security server
CN107534672B (en) Method, equipment and system for promoting network client to provide network service
EP3073699B1 (en) System and method for controlling mutual access of smart devices
CN102077546B (en) Remote access between UPnP devices
Amoretti et al. A scalable and secure publish/subscribe-based framework for industrial IoT
US20150341313A1 (en) Computerized system and method for deployment of management tunnels
CN109474916B (en) Equipment authentication method, device and machine readable medium
US9204345B1 (en) Socially-aware cloud control of network devices
CN101009561A (en) IMX session control and authentication
US11546305B2 (en) Methods and systems for secure DNS routing
JP2022046436A5 (en)
WO2021002180A1 (en) Relay method, relay system, and relay program
CN101800686A (en) Method, device and system for realizing service
US10594682B2 (en) Obtaining data for connection to a device via a network
CN111131228A (en) MQTT protocol-based gateway dynamic theme and stable operation processing method
CN110290176B (en) Point-to-point information pushing method based on MQTT
CN115426392B (en) Equipment network management method, device, equipment and storage medium
KR20200067089A (en) Device bootstrapping
CN114553414B (en) Intranet penetration method and system based on HTTPS service
CN115460083B (en) Security acceleration service deployment method, device, medium and equipment
EP3580901B1 (en) Connection apparatus for establishing a secured application-level communication connection
CN118316618A (en) Networking communication method and communication system based on zero trust security management platform
CN117319166A (en) Access network equipment management method and computer equipment
CN101997844A (en) Event sending method and system and relevant equipment

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