CN115314551B - Equipment data pushing method and equipment data pushing system - Google Patents
Equipment data pushing method and equipment data pushing system Download PDFInfo
- Publication number
- CN115314551B CN115314551B CN202211244220.XA CN202211244220A CN115314551B CN 115314551 B CN115314551 B CN 115314551B CN 202211244220 A CN202211244220 A CN 202211244220A CN 115314551 B CN115314551 B CN 115314551B
- Authority
- CN
- China
- Prior art keywords
- iot
- target
- equipment
- communication server
- parameter information
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to the technical field of computer networks, and discloses a device data pushing method and a device data pushing system under a saas architecture, wherein the method comprises the following steps: generating a message queue theme corresponding to the target equipment through a preset mapping relation, and sending the message queue theme to a service system; acquiring iot information corresponding to target equipment through an information queue theme; acquiring iot identification and equipment parameter information of the target equipment based on the iot message, and sending iot identification and equipment parameter information to the communication server cluster; when the iot identifier is obtained, whether a target communication server subscribed by the target device exists is judged, and if yes, the device parameter information is pushed to a target client instance corresponding to the target device. According to the invention, the device parameter information is pushed to the corresponding client instance through the communication server subscribed by the target device, so that the parameter information acquired by the device can be accurately pushed to the corresponding client.
Description
Technical Field
The invention relates to the technical field of computer networks, in particular to an equipment data pushing method and an equipment data pushing system.
Background
With the rapid development of economic technology and industry, the establishment of intelligent chemical plants is becoming more and more important. In the corrugated paper packing trade, the production line that corresponds can become more and more intelligent along with the time lapse, consequently, corrugated paper packing trade production efficiency's promotion needs more wisdom's system to support.
At present, a management platform in the corrugated paper packaging industry can establish a relationship between production equipment in a production line and corresponding terminals one by one, so that the corresponding production equipment is managed through the terminals, but because more production equipment exists in the corrugated paper packaging industry, parameter information of the equipment cannot be accurately sent to the corresponding terminals, and the butt joint of the equipment and the terminals is realized. Therefore, how to accurately push the parameter information acquired by the device to the corresponding client becomes an urgent problem to be solved.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide an equipment data pushing method and an equipment data pushing system, and aims to solve the technical problem that parameter information acquired by equipment cannot be accurately pushed to a corresponding client in the prior art.
In order to achieve the above object, the present invention provides an apparatus data pushing method, which is applied to a saas architecture, and includes the following steps:
the Iot system generates a message queue theme corresponding to the target equipment through a preset mapping relation and sends the message queue theme to a service system;
the business system acquires iot messages corresponding to the target equipment through the message queue subject;
the business system acquires iot identification and equipment parameter information of the target equipment based on the iot message, and sends the iot identification and the equipment parameter information to a communication server cluster;
and when the communication server cluster acquires the iot identifier, judging whether a target communication server subscribed by the target equipment exists, and if so, pushing the equipment parameter information to a target client instance corresponding to the target equipment.
Optionally, before the step of generating, by the Iot system, a message queue topic corresponding to the target device through a preset mapping relationship and sending the message queue topic to the service system, the method further includes:
the Iot system generates Iot identification of the target equipment and sends the Iot identification to the business system;
and the service system establishes a target mapping based on the iot identifier and the equipment code, and establishes a preset mapping relation based on the target mapping and the current equipment tenant.
Optionally, the step of acquiring, by the service system, iot identifiers and device parameter information of the target device based on the iot message, and sending the iot identifiers and the device parameter information to a communication server cluster includes:
the business system analyzes the iot message to obtain a iot identifier of the target equipment;
the business system queries a corresponding target equipment tenant in the preset mapping relation based on the iot identifier;
the business system acquires the equipment parameter information of the target equipment based on the equipment code corresponding to the target equipment tenant, and sends the iot identifier and the equipment parameter information to a communication server cluster.
Optionally, before the step of analyzing the iot message by the service system and acquiring the iot identifier of the target device, the method further includes:
the business system filters the iot message according to the timestamp corresponding to the iot message;
correspondingly, the step of analyzing the iot message by the service system to obtain the iot identifier of the target device includes:
and the business system analyzes the iot message after filtering to obtain the iot identifier of the target equipment.
Optionally, the step of acquiring, by the service system, device parameter information of the target device based on the device code corresponding to the tenant of the target device, and sending the iot identifier and the device parameter information to the communication server cluster includes:
the service system acquires the equipment parameter information of the target equipment based on the equipment code corresponding to the target equipment tenant;
the business system analyzes the iot message and the equipment parameter information to generate a message pushing format;
and the business system sends the iot identifier and the equipment parameter information to a communication server cluster based on the message push format.
Optionally, before the step of determining whether there is a target communication server subscribed by the target device when the communication server cluster acquires the iot identifier, the method further includes:
a client subscribes a communication server cluster and subscribes corresponding designated equipment to the communication server cluster;
and when detecting that the communication server subscribed by the designated equipment does not exist, the communication server cluster creates the designated equipment and mounts the client instance corresponding to the designated equipment.
Optionally, before the step of determining whether there is a target communication server subscribed by the target device when the communication server cluster acquires the iot identifier, the method further includes:
and when receiving the signal that the communication server is successfully registered, the communication server cluster automatically joins the communication server which is successfully registered.
Optionally, when the communication server cluster obtains the iot identifier, determining whether a target communication server subscribed by the target device exists, and if so, pushing the device parameter information to a target client instance corresponding to the target device, where the step includes:
when the communication server cluster acquires the iot identifier, judging whether a target communication server subscribed by the target device exists, and if so, pushing the device parameter information to a target client instance corresponding to the target device through a gateway to which the communication server cluster belongs.
In addition, to achieve the above object, the present invention further provides an apparatus data pushing system, including: the system comprises an Iot system, a service system and a communication server cluster;
the Iot system is used for generating a message queue theme corresponding to the target equipment through a preset mapping relation and sending the message queue theme to the service system;
the business system is used for acquiring iot messages corresponding to the target equipment through the message queue subject;
the business system is further configured to acquire the iot identifier and the device parameter information of the target device based on the iot message, and send the iot identifier and the device parameter information to a communication server cluster;
the communication server cluster is configured to, when the iot identifier is obtained, determine whether a target communication server subscribed by the target device exists, and if the target communication server subscribed by the target device exists, push the device parameter information to a target client instance corresponding to the target device.
Optionally, the device data pushing system further includes: a client;
the client is used for subscribing the communication server cluster and subscribing the corresponding specified equipment to the communication server cluster;
the communication server cluster is also used for detecting whether a communication server subscribed by the designated equipment exists;
the communication server cluster is further configured to mount a client instance corresponding to the designated device when the communication server subscribed by the designated device is detected to exist.
The invention discloses an Iot system which generates a message queue theme corresponding to target equipment through a preset mapping relation and sends the message queue theme to a service system; the business system acquires iot messages corresponding to the target equipment through the message queue subject; the service system acquires iot identification and equipment parameter information of the target equipment based on iot information, and sends iot identification and equipment parameter information to the communication server cluster; when the communication server cluster acquires the iot identifier, judging whether a target communication server subscribed by the target equipment exists, and if so, pushing the equipment parameter information to a target client instance corresponding to the target equipment; compared with the prior art that the production equipment is connected with the corresponding terminals one by one, and the corresponding production equipment is managed through the terminals, in the invention, an Iot system sends a generated message queue theme corresponding to the target equipment to a service system, the service system obtains Iot messages corresponding to the target equipment through the message queue theme, and sends the obtained Iot identification and equipment parameter information of the target equipment to a communication server cluster, when the communication server cluster obtains Iot identification, whether a communication server subscribed by the target equipment exists is judged, and when the subscribed communication server exists, the equipment parameter information is pushed to a client instance corresponding to the target equipment, so that the technical problem that the parameter information acquired by the equipment cannot be accurately pushed to the corresponding client in the prior art is solved, and accurate butt joint of various equipment and various parameter data with the client is realized.
Drawings
FIG. 1 is a flowchart illustrating a data push method according to a first embodiment of the present invention;
fig. 2 is a schematic diagram of a data push flow in a first embodiment of a data push method of the apparatus according to the present invention;
FIG. 3 is a flowchart illustrating a data pushing method according to a second embodiment of the present invention;
FIG. 4 is a flowchart illustrating a data pushing method according to a third embodiment of the present invention;
FIG. 5 is a block diagram of a first embodiment of a data push system of the present invention;
fig. 6 is a block diagram of a second embodiment of the data push system of the device of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The technical solutions of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments based on the embodiments of the present invention, and all embodiments obtained by a person skilled in the art without creative efforts belong to the protection scope of the present invention.
It should be noted that the descriptions relating to "first", "second", etc. in the embodiments of the present invention are only for descriptive purposes and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present invention.
An embodiment of the present invention provides an apparatus data pushing method, and referring to fig. 1, fig. 1 is a schematic flowchart of a first embodiment of the apparatus data pushing method according to the present invention.
In this embodiment, the device data pushing method includes the following steps:
step S10: the Iot system generates a message queue theme corresponding to the target device through a preset mapping relation and sends the message queue theme to the service system.
It should be noted that the target device may be a device that interfaces with the Iot system, for example, a production device in the corrugated paper packaging industry, and the present embodiment does not limit this.
It should be understood that the preset mapping relationship may be a mapping relationship between the target device and a local service device in the service system, which is pre-established by the service system. In practical application, the Iot system can have functions of acquiring equipment data information of the docking equipment, analyzing the acquired equipment data information and the like, and before acquiring the data information of the Iot system docking equipment, the Iot system needs to generate a Iot identifier of the target equipment and send the Iot identifier to the service system; and the service system establishes a target mapping based on the iot identifier and the equipment code, and establishes a preset mapping relation based on the target mapping and the current equipment tenant.
It is understood that the message queue topic may be address information corresponding to the target device in the Iot system. In practical application, the device parameter data of the corresponding device can be acquired according to the message queue theme.
In specific implementation, when the Iot system collects data information of the docking device, a unique Iot identifier of the docking device can be generated when the docking device is connected with the Iot system, the business system maps a local business device code according to the Iot identifier of the docking device generated by the Iot system, establishes a target mapping, maps a current device tenant according to the device coding data mapped by the Iot identifier (i.e., iot identifier and a target mapping corresponding to the device coding data), establishes a preset mapping relationship, and caches the preset mapping relationship, so that the Iot system can designate the docking device to generate a corresponding message queue theme, and send the generated message queue theme to the business system.
Step S20: and the business system acquires iot messages corresponding to the target equipment through the message queue subject.
It should be noted that the Iot message may be device information of a docking device in an Iot system, where the device information is sent by the Iot system to the service system, and may include a Iot identifier of the docking device, device parameter information of the docking device, and the like, which is not limited in this embodiment.
It should be understood that the business system may configure and subscribe according to a message queue topic generated by the Iot system, subscribe to a specified topic using the message queue, push queue messages to the specified topic by other external data sources, adopt different topics according to different parameter data, implement different parsing logics, and switch different data sources to provide services and switch different device acquisition applications under a specified message format.
Step S30: the service system acquires iot identification and device parameter information of the target device based on the iot message, and sends iot identification and the device parameter information to a communication server cluster.
It is understood that the Iot identification described above may be a unique identification of a device that the Iot system generates from a docked device.
It should be noted that the device parameter information may be related data of the docking device, such as a device power on/off message and a quantity message, which is not limited in this embodiment. In practical application, the acquired data can be stored in a relational database Mysql and a cache database Redis, the relational database Mysql can store the device data information of the target device, and the cache database Redis can cache the device data information, so that the response speed of the system is improved.
Step S40: and when the communication server cluster acquires the iot identifier, judging whether a target communication server subscribed by the target equipment exists, and if so, pushing the equipment parameter information to a target client instance corresponding to the target equipment.
It should be understood that the target communication server may be a communication server to which the target device subscribes. In practical application, a socket communication server can be built by using dubbo and netty to register to a nacos or other registration centers, and a cluster registration service is built.
It is understood that the target client instances may be all client instances in the target device. In practical application, each client can designate corresponding equipment, that is, the equipment can have multiple clients with the same instance, and the communication server can push the equipment parameter data to the client corresponding to the equipment after acquiring the equipment parameter data of the corresponding equipment.
It should be noted that the communication server may register through a registration center constructed by the nacos server, and automatically join the communication server cluster when the registration is successful.
It should be understood that the communication server cluster is uniformly registered in the registration center, so as to realize multi-node connection of the client, and use the service gateway to perform uniform forwarding for load balancing, thereby ensuring service load balancing. Each client instance can balance the strategy to the appointed service according to the appointed load, and the load of each client can be ensured to receive the acquisition information of the current equipment in different servers according to the message pushing strategy.
In a specific implementation, as shown in fig. 2, an Iot system may generate a message queue topic corresponding to a device according to a preset mapping relationship, where the message queue topic of a service system obtains Iot identifiers and device parameter data of the corresponding device, and sends Iot identifiers and the device parameter data to a communication server cluster, and after receiving Iot identifiers and the device parameter data, the communication server cluster may search whether a communication server subscribed by the corresponding device exists according to Iot identifiers, and if so, may push the device parameter data to a client instance corresponding to a device corresponding to Iot identifiers through a unified gateway, so that the device parameter data may be distributed to the client instance connected to each server after being broadcast to the server, thereby implementing accurate push of the parameter data.
The embodiment discloses that an Iot system generates a message queue theme corresponding to target equipment through a preset mapping relation and sends the message queue theme to a service system; the business system acquires iot messages corresponding to the target equipment through the message queue subject; the service system acquires iot identification and equipment parameter information of the target equipment based on iot information, and sends iot identification and equipment parameter information to the communication server cluster; when the communication server cluster acquires the iot identifier, judging whether a target communication server subscribed by the target equipment exists, and if so, pushing the equipment parameter information to a target client instance corresponding to the target equipment; compared with the prior art that the production equipment is connected with the corresponding terminals one by one, and the corresponding production equipment is managed through the terminals, in the embodiment, the Iot system sends the generated message queue theme corresponding to the target equipment to the service system, the service system acquires Iot messages corresponding to the target equipment through the message queue theme, and sends the acquired Iot identifier and the equipment parameter information of the target equipment to the communication server cluster, when the communication server cluster acquires Iot identifier, whether a communication server subscribed by the target equipment exists is judged, and when the subscribed communication server exists, the equipment parameter information is pushed to the client instance corresponding to the target equipment, so that the technical problem that the parameter information acquired by the equipment cannot be accurately pushed to the corresponding client in the prior art is solved, and accurate butt joint of multiple kinds of equipment and multiple kinds of parameter data with the client is realized.
Referring to fig. 3, fig. 3 is a flowchart illustrating a data pushing method according to a second embodiment of the present invention.
Based on the first embodiment, in order to obtain the iot identifier and the device parameter information corresponding to the device through the iot message, in this embodiment, the step S30 includes:
step S301: and the business system analyzes the iot message and acquires the iot identifier of the target equipment.
It should be noted that, in order to ensure the real-time performance of the messages, when the iot messages are analyzed by the service system, only the nearest message is analyzed, and the old message is not analyzed.
In a specific implementation, the service system may obtain a timestamp corresponding to iot message, filter iot message according to the timestamp to obtain latest data, remove accumulated non-real-time messages, and analyze the latest data obtained after filtering to obtain iot identifier of the target device.
Step S302: and the business system queries a corresponding target equipment tenant in the preset mapping relation based on the iot identifier.
It should be understood that the target device tenant may be a company corresponding to the target device, that is, a company currently performing message pushing. Since the preset mapping relationship is established by identifying and mapping the local service device code based on iot and according to iot, identifying and mapping the device tenant of the mapped local service device code, the device tenant corresponding to the acquisition device can be identified through iot.
Step S303: the business system acquires the equipment parameter information of the target equipment based on the equipment code corresponding to the target equipment tenant, and sends the iot identifier and the equipment parameter information to a communication server cluster.
It can be understood that after the target device tenant is obtained, the device parameter data corresponding to the device may be obtained by obtaining iot identifier of the device code corresponding to the target device tenant.
Further, in order to push the message that the target device needs to push to the client instance, the step S303 includes: the service system acquires the equipment parameter information of the target equipment based on the equipment code corresponding to the target equipment tenant; the business system analyzes the iot message and the equipment parameter information to generate a message push format; and the business system sends the iot identifier and the equipment parameter information to a communication server cluster based on the message push format.
It should be noted that the message pushing format may be a format corresponding to specific data of the message that needs to be pushed by the target device and is configured by the service system, for example, the message that needs to be pushed by the target device is an on/off message and a quantity message of the target device, and at this time, the data in the message pushing format is the on/off message and the quantity message of the target device.
In a specific implementation, a business system may preset message formats (for example, two messages, i.e., a startup message and a shutdown message of a device to be pushed) that all docking devices need to push, and since the formats of the push messages of each iot system are different, when device parameter data is pushed to a target device, after a device number corresponding to the target device is obtained, device parameter data of the target device may be obtained according to a device code corresponding to the target device, and the iot message and the device parameter data are analyzed to obtain a corresponding message push format, and extract data in the message push format, so as to convert the data into a message to be pushed, and finally, the message to be pushed by the device may be pushed to a corresponding instance client.
In this embodiment, iot messages are analyzed by the service system to obtain iot identifiers of target devices, corresponding target device tenants are queried in a preset mapping relationship based on iot identifiers, device parameter information of the target devices is obtained based on device codes corresponding to the target device tenants, iot messages and device parameters are analyzed to generate a message push format, and iot identifiers and device parameter information are sent to the communication server cluster based on the message push format, so that messages to be pushed by the devices can be broadcast to the communication server cluster, accurate pushing of parameter data is further achieved, non-real-time data can be removed according to a timestamp, and real-time pushing of the parameter data is achieved.
Referring to fig. 4, fig. 4 is a flowchart illustrating a data pushing method according to a third embodiment of the present invention.
Based on the foregoing embodiments, in order to subscribe the client instance to the messaging server, in this embodiment, before the step S40, the method further includes:
step S401: and the client subscribes the communication server cluster and subscribes the corresponding designated equipment to the communication server cluster.
It should be noted that the specified device may be an object for which the client needs to receive the parameter data, for example, the client a needs to obtain the device parameter data of the device a, and at this time, the device a is the specified device of the client a.
Step S402: and when detecting that the communication server subscribed by the designated equipment does not exist, the communication server cluster creates the designated equipment and mounts the client instance corresponding to the designated equipment.
In a specific implementation, when a client subscribes to a communication server, a specified device is registered and subscribed to the communication server, and at this time, the server queries whether the device is subscribed currently, if so, the client instance is mounted to the device set, and if not, the device set is created, and the client instance is mounted to a newly created device. When the client subscribes the message of the equipment mounted by the client when the message received by the communication server is received by the client, inquiring whether the equipment exists in the current communication server or not, and if so, pushing the message to all client instances corresponding to the equipment to finish pushing data.
In this embodiment, when a client subscribes a communication server, a designated device is subscribed to the communication server, and when a communication server cluster detects that there is no communication server subscribed by the designated device, the designated device is created, and a client instance corresponding to the designated device is mounted to the designated device, so that when receiving a message of the device, the communication server can push the message to all client instances corresponding to the device, thereby implementing accurate pushing of the message.
Referring to fig. 5, fig. 5 is a block diagram of a first embodiment of the data push system of the present invention.
As shown in fig. 5, the device data pushing system according to the embodiment of the present invention includes: the system comprises an Iot system 100, a service system 200 and a communication server cluster 300;
the Iot system 100 is configured to generate a message queue theme corresponding to a target device according to a preset mapping relationship, and send the message queue theme to the service system 200;
the business system 200 is configured to obtain iot messages corresponding to the target device through the message queue topic;
the service system 200 is further configured to obtain iot identifiers and device parameter information of the target devices based on the iot message, and send the iot identifiers and the device parameter information to the communication server cluster 300;
the communication server cluster 300 is configured to, when the iot identifier is obtained, determine whether a target communication server subscribed by the target device exists, and if the target communication server exists, push the device parameter information to a target client instance corresponding to the target device.
The device data pushing system of the embodiment discloses that an Iot system 100 generates a message queue theme corresponding to a target device through a preset mapping relation, and sends the message queue theme to a service system; the business system 200 acquires iot messages corresponding to the target equipment through the message queue subject; the service system 200 acquires iot identification and equipment parameter information of the target equipment based on iot messages, and sends iot identification and equipment parameter information to the communication server cluster; when the communication server cluster 300 obtains the iot identifier, it is determined whether a target communication server subscribed by the target device exists, and if so, the device parameter information is pushed to a target client instance corresponding to the target device; compared with the prior art that the production equipment is connected with the corresponding terminals one by one, and the corresponding production equipment is managed through the terminals, in this embodiment, the Iot system 100 sends the generated message queue theme corresponding to the target equipment to the service system, the service system 200 obtains Iot messages corresponding to the target equipment through the message queue theme, and sends the obtained Iot identifier and the equipment parameter information of the target equipment to the communication server cluster, when the communication server cluster 300 obtains Iot identifier, it is determined whether a communication server subscribed by the target equipment exists, and when the subscribed communication server exists, the equipment parameter information is pushed to the client instance corresponding to the target equipment, so that the technical problem that the parameter information acquired by the equipment cannot be accurately pushed to the corresponding client in the prior art is solved, and accurate butt joint of multiple kinds of equipment and multiple kinds of parameter data with the client is further achieved.
Referring to fig. 6, fig. 6 is a block diagram of a second embodiment of the data push system of the present invention.
As shown in fig. 6, the device data pushing system according to the embodiment of the present invention further includes: a client 400;
the client 400 is configured to subscribe to a communication server cluster, and subscribe a corresponding designated device to the communication server cluster 300;
the communication server cluster 300 is further configured to detect whether a communication server subscribed by the designated device exists;
the communication server cluster 300 is further configured to mount, when it is detected that there is a communication server subscribed by the designated device, a client instance corresponding to the designated device.
In this embodiment, when subscribing to the communication server, the client 400 subscribes the designated device to the communication server 300, and when detecting that there is no communication server subscribed by the designated device, the communication server cluster 300 creates the designated device and mounts the client instance corresponding to the designated device, so that when receiving the message of the device, the communication server can push the message to all the client instances corresponding to the device, thereby implementing accurate pushing of the message.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system 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 system. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are only for description, and do not represent the advantages and disadvantages of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., a rom/ram, a magnetic disk, an optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (8)
1. The device data pushing method is applied to a saas architecture and comprises the following steps:
the Iot system generates a message queue theme corresponding to the target equipment through a preset mapping relation and sends the message queue theme to a service system;
the business system acquires iot messages corresponding to the target equipment through the message queue subject;
the business system acquires iot identification and equipment parameter information of the target equipment based on the iot message, and sends the iot identification and the equipment parameter information to a communication server cluster;
when the communication server cluster acquires the iot identifier, judging whether a target communication server subscribed by the target equipment exists, and if so, pushing the equipment parameter information to a target client instance corresponding to the target equipment;
before the steps of generating a message queue theme corresponding to a target device by the Iot system through a preset mapping relation and sending the message queue theme to a service system, the Iot system further comprises:
the Iot system generates Iot identification of the target equipment and sends the Iot identification to the business system;
the business system establishes a target mapping based on the iot identifier and the equipment code, and establishes a preset mapping relation based on the target mapping and the current equipment tenant;
the business system obtains the iot identifier and the device parameter information of the target device based on the iot message, and sends the iot identifier and the device parameter information to a communication server cluster, including:
the business system analyzes the iot message to obtain a iot identifier of the target equipment;
the business system queries a corresponding target equipment tenant in the preset mapping relation based on the iot identifier;
the business system acquires the equipment parameter information of the target equipment based on the equipment code corresponding to the target equipment tenant, and sends the iot identifier and the equipment parameter information to a communication server cluster.
2. The device data pushing method of claim 1, wherein before the step of parsing the iot message and obtaining the iot identifier of the target device, the service system further comprises:
the business system filters the iot message according to the timestamp corresponding to the iot message;
correspondingly, the step of analyzing the iot message by the service system to obtain the iot identifier of the target device includes:
and the business system analyzes the iot message after filtering to obtain the iot identifier of the target equipment.
3. The device data pushing method according to claim 1, wherein the step of the service system obtaining the device parameter information of the target device based on the device code corresponding to the tenant of the target device, and sending the iot identifier and the device parameter information to the communication server cluster includes:
the service system acquires the equipment parameter information of the target equipment based on the equipment code corresponding to the target equipment tenant;
the business system analyzes the iot message and the equipment parameter information to generate a message pushing format;
and the business system sends the iot identifier and the equipment parameter information to a communication server cluster based on the message push format.
4. The device data pushing method according to claim 1, wherein before the step of determining whether there is a target communication server subscribed by the target device when the communication server cluster acquires the iot identifier, the method further comprises:
a client subscribes a communication server cluster and subscribes corresponding designated equipment to the communication server cluster;
and when detecting that the communication server subscribed by the designated equipment does not exist, the communication server cluster creates the designated equipment and mounts the client instance corresponding to the designated equipment.
5. The device data pushing method according to claim 1, wherein before the step of determining whether there is a target communication server subscribed by the target device when the communication server cluster acquires the iot identifier, the method further comprises:
and when receiving the signal that the communication server is successfully registered, the communication server cluster automatically joins the communication server which is successfully registered.
6. The device data pushing method according to claim 1, wherein the step of, when obtaining the iot identifier, the communication server cluster determining whether there is a target communication server subscribed by the target device, and if there is a target communication server subscribed by the target device, pushing the device parameter information to a target client instance corresponding to the target device includes:
when the communication server cluster acquires the iot identifier, judging whether a target communication server subscribed by the target device exists, and if so, pushing the device parameter information to a target client instance corresponding to the target device through a gateway to which the communication server cluster belongs.
7. A device data push system, characterized in that the device data push system comprises: the system comprises an Iot system, a service system and a communication server cluster;
the Iot system is used for generating a message queue theme corresponding to the target equipment through a preset mapping relation and sending the message queue theme to the service system;
the business system is used for acquiring iot messages corresponding to the target equipment through the message queue subject;
the business system is further configured to acquire iot identifiers and device parameter information of the target devices based on the iot message, and send the iot identifiers and the device parameter information to a communication server cluster;
the communication server cluster is used for judging whether a target communication server subscribed by the target equipment exists or not when the iot identifier is obtained, and if so, pushing the equipment parameter information to a target client instance corresponding to the target equipment;
the Iot system is further used for generating a Iot identifier of the target equipment and sending the Iot identifier to the business system;
the business system is also used for establishing a target mapping based on the iot identifier and the equipment code and establishing a preset mapping relation based on the target mapping and the current equipment tenant; analyzing the iot message to acquire a iot identifier of the target device; querying a corresponding target device tenant in the preset mapping relation based on the iot identifier; and acquiring the equipment parameter information of the target equipment based on the equipment code corresponding to the target equipment tenant, and sending the iot identifier and the equipment parameter information to a communication server cluster.
8. The device data pushing system of claim 7, wherein the device data pushing system further comprises: a client;
the client is used for subscribing the communication server cluster and subscribing the corresponding specified equipment to the communication server cluster;
the communication server cluster is also used for detecting whether a communication server subscribed by the designated equipment exists;
the communication server cluster is further configured to mount a client instance corresponding to the designated device when the communication server subscribed by the designated device is detected to exist.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211244220.XA CN115314551B (en) | 2022-10-12 | 2022-10-12 | Equipment data pushing method and equipment data pushing system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211244220.XA CN115314551B (en) | 2022-10-12 | 2022-10-12 | Equipment data pushing method and equipment data pushing system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115314551A CN115314551A (en) | 2022-11-08 |
| CN115314551B true CN115314551B (en) | 2022-12-20 |
Family
ID=83867897
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211244220.XA Active CN115314551B (en) | 2022-10-12 | 2022-10-12 | Equipment data pushing method and equipment data pushing system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115314551B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021204115A1 (en) * | 2020-04-07 | 2021-10-14 | 添可智能科技有限公司 | Data generation method, data processing method, data execution method and device |
| CN114051055A (en) * | 2022-01-12 | 2022-02-15 | 江苏银承网络科技股份有限公司 | Data transmission method and device in different systems |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110086636B (en) * | 2019-04-17 | 2022-03-25 | 平安科技（深圳）有限公司 | Message distribution method based on mqtt, server and storage medium |
| CN111970315A (en) * | 2019-05-20 | 2020-11-20 | 北京车和家信息技术有限公司 | Method, device and system for pushing message |
| CN112039979B (en) * | 2020-08-27 | 2023-06-20 | 中国平安财产保险股份有限公司 | Distributed data cache management method, device, equipment and storage medium |
| CN114338769B (en) * | 2021-12-22 | 2024-04-12 | 浙江中控技术股份有限公司 | Access request processing method and device |
-
2022
- 2022-10-12 CN CN202211244220.XA patent/CN115314551B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021204115A1 (en) * | 2020-04-07 | 2021-10-14 | 添可智能科技有限公司 | Data generation method, data processing method, data execution method and device |
| CN114051055A (en) * | 2022-01-12 | 2022-02-15 | 江苏银承网络科技股份有限公司 | Data transmission method and device in different systems |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115314551A (en) | 2022-11-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2955953B1 (en) | Device management server, device management client, and method for locating a target operation object | |
| CN112422709B (en) | Identification management method, terminal equipment, identification analysis secondary node and medium | |
| US10009718B2 (en) | Sign-in method and device, sign-in server, and storage medium | |
| CN109756559B (en) | Construction and use method for distributed data distribution service of embedded airborne system | |
| CN112840691B (en) | Apparatus and method for discovering collectable data and analyzing data in network | |
| CN111414416A (en) | Data processing method, device, equipment and storage medium | |
| CN104144098A (en) | Information pushing method and system and pushing server equipment | |
| CN112087468A (en) | Message processing method, related equipment and readable storage medium | |
| EP2051441A1 (en) | A method, system, client end and server for locating operation node in a communication system | |
| EP3001606A1 (en) | Fault processing method, device and system | |
| CN105282682B (en) | Method for realizing resource attribute notification and public service entity | |
| CN112052227A (en) | Data change log processing method and device and electronic equipment | |
| CN112788518B (en) | Location service processing method and related equipment | |
| CN115314551B (en) | Equipment data pushing method and equipment data pushing system | |
| GB2598544A (en) | Network slice analytics | |
| EP2446584B1 (en) | Method and system for use in network management of communications network | |
| CN108833331B (en) | Resource object creating method and device and resource object state reporting method and device | |
| CN114338794B (en) | Service message pushing method and device, electronic equipment and storage medium | |
| CN106649678B (en) | Data processing method and system | |
| CN101977371A (en) | Method, platform and system for querying subscriber home network information | |
| EP4092961A1 (en) | Group updating method, message sending method, and apparatuses | |
| CN111983960A (en) | Monitoring system and method | |
| CN110855785B (en) | Data processing method and device | |
| CN116055458B (en) | Audio and video call method, equipment and medium between cloud platform equipment of Internet of things | |
| EP4040757A1 (en) | Monitoring of communication |
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 |