CN111294382A - Real-time data pushing method and device - Google Patents
Real-time data pushing method and device Download PDFInfo
- Publication number
- CN111294382A CN111294382A CN201911398737.2A CN201911398737A CN111294382A CN 111294382 A CN111294382 A CN 111294382A CN 201911398737 A CN201911398737 A CN 201911398737A CN 111294382 A CN111294382 A CN 111294382A
- Authority
- CN
- China
- Prior art keywords
- real
- time
- data
- scene type
- network client
- 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.)
- Pending
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/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
Abstract
The invention provides a real-time data pushing method and a real-time data pushing device, wherein the method comprises the following steps: receiving and storing a scene type registered by at least one network client through a real-time push data channel and target equipment monitored under the scene type; acquiring real-time monitoring data of a target equipment group; analyzing the real-time monitoring data, and acquiring a scene type and target equipment corresponding to the real-time monitoring data; and pushing the real-time monitoring data to the network client which is registered with the scene type and the target equipment through the real-time pushing data channel. Based on the scheme provided by the invention, the method can receive various scene types and target equipment registered by at least one client, can accurately push the real-time monitoring data to the corresponding network client through the real-time data pushing channel, does not need to develop an information channel and a parameter registering and analyzing method aiming at each scene type, and is low in cost and easy to maintain.
Description
Technical Field
The invention relates to the field of computer application, in particular to a real-time data pushing method and device.
Background
With the rapid development of the internet of things, many systems need to implement a real-time pushing mechanism to meet various service demand scenarios of real-time pushing of users, such as real-time sensing of the state of the internet of things equipment, real-time receiving of identification signals of the internet of things equipment, and the like.
In the prior art, there are network protocols and software components supporting a real-time push mechanism, such as WebSocket, netty, and socket. The existing scheme has the disadvantage that an information channel needs to be established for each type of service scenario. Correspondingly, a set of new parameter registration and analysis methods needs to be developed for each type of service scene. If the business requirement changes, each method traversal needs to be modified. Cost is high overall and maintenance is not facilitated.
Disclosure of Invention
In view of the above, the present invention has been made to provide a data real-time pushing method and apparatus that overcomes or at least partially solves the above problems.
According to an aspect of the present invention, there is provided a method for pushing data in real time, the method including:
receiving and storing a scene type registered by at least one network client through a real-time push data channel and target equipment monitored under the scene type;
acquiring real-time monitoring data of a target equipment group;
analyzing the real-time monitoring data, and acquiring a scene type and target equipment corresponding to the real-time monitoring data;
and pushing the real-time monitoring data to the network client which is registered with the scene type and the target equipment through the real-time pushing data channel.
Optionally, before the receiving and saving the scene type registered by the at least one network client via the real-time push data channel and the target device monitored under the scene type, the method further includes:
receiving a request for establishing long connection sent by at least one network client, and establishing long connection with the network client; and
and receiving a registration request uploaded by the network client through the real-time push data channel, responding to the registration request, generating and storing a unique session ID of the network client.
Optionally, after receiving and storing a scene type registered by at least one network client via a real-time push data channel and a target device monitored under the scene type, the method further includes:
and establishing a mapping relation among the target equipment, the scene type and the session ID and storing the mapping relation in a mapping relation table.
Optionally, pushing the real-time monitoring data to the network client registered with the scene type and the target device via the real-time data pushing channel includes:
searching a session ID corresponding to the scene type of the real-time monitoring data and the target equipment in the mapping relation table;
and pushing the real-time monitoring data to a network client corresponding to the session ID.
Optionally, the scene type includes at least one of:
equipment upgrading, equipment state sensing, equipment name changing, equipment area transferring, equipment parameter changing and gateway equipment scanning progress.
Optionally, the receiving and storing a scene type registered by at least one network client via a real-time push data channel and a target device monitored under the scene type includes:
receiving and storing the scene type and the monitoring card registered by at least one network client through a real-time push data channel; the monitoring card comprises target equipment and parameter types which are monitored under the scene types, and a mapping relation exists between the monitoring card and the target equipment and between the monitoring card and the parameter types.
Optionally, after receiving and storing the scene type and the monitoring card registered by the at least one network client via the real-time push data channel, the method further includes:
and establishing a mapping relation among the monitoring card, the scene type and the session ID and storing the mapping relation in a mapping relation table.
Optionally, analyzing the real-time monitoring data, and acquiring a scene type and a target device corresponding to the real-time monitoring data, includes:
and analyzing the real-time monitoring data, and acquiring a scene type, a target device and a parameter type corresponding to the real-time monitoring data.
Optionally, pushing the real-time monitoring data to the network client registered with the scene type and the target device via the real-time data pushing channel includes:
determining target equipment corresponding to the real-time monitoring data and a monitoring card corresponding to the parameter type;
searching a session ID corresponding to the monitoring card and the scene type in the mapping relation table;
and pushing the real-time monitoring data to a network client corresponding to the session ID.
Optionally, the scene type includes device monitoring; and
the data type includes at least one of: temperature, humidity.
Optionally, the method further comprises:
receiving a disconnection request sent by the network client through the real-time push data channel; and
and according to the disconnection request, logging off the session ID and deleting data related to the session ID.
According to another aspect of the present invention, there is also provided a data real-time pushing apparatus, including:
the receiving module is configured to receive and store a scene type registered by at least one network client through a real-time push data channel and target equipment monitored under the scene type;
the monitoring module is configured to acquire real-time monitoring data of the target equipment group;
the analysis module is configured to analyze the real-time monitoring data and acquire a scene type and target equipment corresponding to the real-time monitoring data;
and the pushing module is configured to push the real-time monitoring data to the network client which is registered with the scene type and the target device through the real-time pushing data channel.
Optionally, the real-time data pushing device further includes: the first establishing module is configured to receive a request for establishing long connection sent by at least one network client and establish long connection with the network client;
and the generating module is configured to receive a registration request uploaded by the network client through the real-time push data channel, respond to the registration request, generate and store a unique session ID with the network client.
Optionally, the real-time data pushing device further includes: and the second establishing module is configured to establish a mapping relation among the target device, the scene type and the session ID and store the mapping relation in a mapping relation table.
Optionally, the pushing module comprises: a first searching unit configured to search the mapping relation table for a session ID corresponding to a scene type of the real-time monitoring data and a target device;
the first pushing unit is configured to push the real-time monitoring data to a network client corresponding to the session ID.
Optionally, the scene type includes at least one of:
equipment upgrading, equipment state sensing, equipment name changing, equipment area transferring, equipment parameter changing and gateway equipment scanning progress.
Optionally, the receiving module is further configured to: receiving and storing the scene type and the monitoring card registered by at least one network client through a real-time push data channel; the monitoring card comprises target equipment and parameter types which are monitored under the scene types, and a mapping relation exists between the monitoring card and the target equipment and between the monitoring card and the parameter types.
Optionally, the real-time data pushing device further includes: and the third establishing module is configured to establish a mapping relation among the monitoring card, the scene type and the session ID and store the mapping relation in a mapping relation table.
Optionally, the parsing module is further configured to: and analyzing the real-time monitoring data, and acquiring a scene type, a target device and a parameter type corresponding to the real-time monitoring data.
Optionally, the pushing module comprises: the determining unit is configured to determine a target device corresponding to the real-time monitoring data and a monitoring card corresponding to the parameter type;
the second searching unit is configured to search the session ID corresponding to the monitoring card and the scene type in the mapping relation table;
and the second pushing unit is configured to push the real-time monitoring data to the network client corresponding to the session ID.
Optionally, the scene type includes device monitoring; and
the data type includes at least one of: temperature, humidity.
Optionally, the real-time data pushing device further includes: a logout deletion module configured to receive a disconnection request sent by the network client via the real-time push data channel; and
and according to the disconnection request, logging off the session ID and deleting data related to the session ID.
In the embodiment of the invention, multiple scene types and target devices registered by at least one client can be received, when the real-time monitoring data of the target device group is obtained, the network client registered with the scene types and the target devices can be determined according to the scene types and the target devices contained in the real-time monitoring data, and then the real-time monitoring data is accurately pushed to the network client through the real-time pushing data channel. Based on the scheme provided by the invention, an information channel and a parameter registration and analysis method do not need to be developed for each scene type, the cost is low, and the maintenance is easy.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
The above and other objects, advantages and features of the present invention will become more apparent to those skilled in the art from the following detailed description of specific embodiments thereof, taken in conjunction with the accompanying drawings.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 shows a flow chart of a data real-time pushing method according to an embodiment of the invention;
fig. 2 is a flowchart illustrating a real-time data pushing method according to an alternative embodiment of the present invention;
fig. 3 is a flowchart illustrating a real-time data pushing method according to another alternative embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a data real-time pushing device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a data real-time pushing device according to an alternative embodiment of the present invention;
fig. 6 shows a schematic structural diagram of a data real-time pushing device according to another alternative embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
It should be noted that the technical features of the embodiments and alternative embodiments of the present invention may be combined with each other without conflict.
The embodiment of the invention provides a real-time data pushing method. Fig. 1 shows a flow diagram of a data real-time pushing method according to an embodiment of the present invention. As shown in fig. 1, the method includes:
step S102: and receiving and storing the scene type registered by at least one network client through the real-time push data channel and the target equipment monitored under the scene type.
Step S104: and acquiring real-time monitoring data of the target equipment group.
Step S106: and analyzing the real-time monitoring data, and acquiring the scene type and the target equipment corresponding to the real-time monitoring data.
Step S108: and pushing the real-time monitoring data to the network client registered with the scene type and the target equipment through a real-time pushing data channel.
In the embodiment of the invention, multiple scene types and target devices registered by at least one client can be received, when the real-time monitoring data of the target device group is obtained, the network client registered with the scene types and the target devices can be determined according to the scene types and the target devices contained in the real-time monitoring data, and then the real-time monitoring data is accurately pushed to the network client through the real-time pushing data channel. Based on the scheme provided by the invention, an information channel and a parameter registration and analysis method do not need to be developed for each scene type, the cost is low, and the maintenance is easy.
The network client may be an APP, a browser, or the like, which is not specifically limited in the present invention.
The scene type in the above embodiment may include at least one of: equipment upgrading, equipment state sensing, equipment name changing, equipment area transferring, equipment parameter changing and gateway equipment scanning progress.
The scene type may be represented by a number, e.g., number 1 for a device upgrade, number 2 for a device name change, etc. The destination device may be represented by an IP address, with different IP addresses representing different destination devices.
The session ID is a read-only value that uniquely identifies the network client currently accessing the server, and may be a string of numeric codes 706616433, or other form of string with a unique identification.
Fig. 2 is a flowchart illustrating a data real-time pushing method according to an alternative embodiment of the present invention. As shown in fig. 2, before step S102, the method provided in the embodiment of the present invention further includes:
step S100: and receiving a connection establishment request sent by at least one network client, and establishing connection with the network client.
Step S101: and receiving a registration request uploaded by the network client through a real-time data pushing channel, responding to the registration request, generating and storing a unique session ID with the network client.
In this embodiment, the server may establish a connection with a plurality of network clients, and generate session IDs corresponding to the plurality of network clients one to one.
In step S100, a request for establishing a long connection from at least one network client is received, and a long connection is established with the network client. Specifically, the method may be to receive a request for establishing a long TCP connection sent by at least one network client, and establish the long TCP connection with the network client.
TCP refers to network communications between a network client and a server that use the TCP protocol. A long connection is one that can continuously transmit a plurality of packets over a TCP long connection, and during the TCP connection hold period, if no packet is transmitted, both sides need to transmit a detection packet to maintain the connection.
It should be noted that, the present invention does not specifically limit the form of the connection established between the server and the network client, and any connection form capable of implementing data transmission with the network client is possible.
Referring to fig. 2, after step S102, the method provided by the embodiment of the present invention further includes: step S103 a: and establishing a mapping relation among the target equipment, the scene type and the session ID and storing the mapping relation in a mapping relation table.
Optionally, step S108 specifically includes: searching a scene type of the real-time monitoring data and a session ID corresponding to the target device in a mapping relation table; and pushing the real-time monitoring data to the network client corresponding to the session ID. .
In this embodiment, the server establishes a mapping relationship among the target device, the scene type, and the session ID, and stores the mapping relationship in the mapping relationship table. When the real-time monitoring data is acquired later, the corresponding session ID can be found in the mapping relation table according to the target device and the scene type corresponding to the real-time monitoring data, so that the real-time monitoring data is accurately pushed to the network client side corresponding to the session ID through the real-time pushing data channel, and the network client side can render on a page by adopting the received data.
The above alternative embodiments will now be further described with an example of a device upgrade scenario. In this example, the session ID between the server and a network client is 706616433, the (scene type, target device) registered by the network client is (1, (192.168.1.6, 2)), the scene type number corresponding to the device upgrade is 1, and the session ID706616433 has a mapping relationship with (1, (192.168.1.6, 2)). Then, after analyzing the real-time monitoring data to determine that the real-time monitoring data (scene type number, target device) corresponds to (1, (192.168.1.6, 2)), namely the real-time monitoring data can be mapped to the session ID706616433 by (1, (192.168.1.6, 2)), the device upgrade status is pushed to the network client corresponding to the session ID 706616433.
The parameter registration and data transmission processes of other scenes are the same as the equipment upgrading scene, the network client only needs to select other scene types during registration, and other steps are the same. Therefore, the present invention is not exemplified herein.
Fig. 3 is a flowchart illustrating a data real-time pushing method according to another alternative embodiment of the present invention. As shown in fig. 3, step S102 specifically includes: receiving scene types and monitoring cards registered by at least one network client through a real-time push data channel; the monitoring card comprises target equipment and parameter types which are monitored under the scene types, and a mapping relation exists between the monitoring card and the target equipment and between the monitoring card and the parameter types.
Wherein the scene type may be device monitoring. The data type includes at least one of: temperature, humidity. Different types of data may be included in this scenario as the device monitors. Therefore, the target device and the data type need to be written into one monitoring card, which may be represented by numbers, such as monitoring card a, monitoring card b, and the like.
As shown in fig. 3, after step S102, the method provided in this embodiment further includes: step S103b, a mapping relation is established among the monitoring cards, the scene types and the session IDs and is stored in a mapping relation table.
As shown in fig. 3, step S106 specifically includes: and analyzing the real-time monitoring data, and acquiring a scene type, a target device and a parameter type corresponding to the real-time monitoring data.
Step S108 specifically includes: determining target equipment corresponding to the real-time monitoring data and a monitoring card corresponding to the parameter type; searching a session ID corresponding to the monitoring card and the scene type in a mapping relation table; pushing real-time monitoring data to network client corresponding to session ID
In this embodiment, a unique mapping relationship exists among the monitoring card, the scene type, and the session ID, and a unique mapping relationship exists among the monitoring card, the target device, and the data type. When the real-time monitoring data is acquired later, the corresponding monitoring card can be determined according to the target device and the parameter type corresponding to the real-time monitoring data, and then the corresponding session ID corresponding to the monitoring card is found in the mapping relation table, so that the real-time monitoring data is accurately pushed to the network client corresponding to the session ID through the real-time pushing data channel, and the network client can adopt the received data to render on the page.
An example is now presented of this scenario of device monitoring to further illustrate the above alternative embodiments. In this example, the session ID with a network client is 706616434, the (scene type, monitoring card) registered by the network client is (2, a), and the corresponding scene type for device monitoring is 2. The network client registers (target device number, data type) as (3, temperature) in the monitoring card with the code of a. Then, when the real-time monitoring data is analyzed to determine that the corresponding (target device number, data type) is (3, temperature), the monitoring card coded as a can be determined, and then the data related to the temperature change can be pushed to the network client corresponding to the session ID706616434 according to the mapping (2, a) corresponding to (scene type, monitoring card) to the session ID 706616434.
In addition, if the data type is humidity, only the humidity needs to be selected during registration, and other steps are the same. Therefore, the present invention is not exemplified herein.
In an alternative embodiment, after step S101, the method provided in the embodiment of the present invention further includes: receiving a disconnection request sent by a network client through a real-time push data channel; according to the disconnection request, the session ID is logged off, and data associated with the session ID is deleted.
In the embodiment, only one set of parameter logout method needs to be developed for different types of scenes, so that resources are saved and management is facilitated.
Based on the same inventive concept, the invention further provides a data real-time pushing device, and fig. 4 shows a schematic structural diagram of the data real-time pushing device according to the embodiment of the invention. The real-time data pushing device 200 includes: and the receiving module 210 is configured to receive and store the scene type registered by the at least one network client via the real-time push data channel and the target device monitored under the scene type.
The monitoring module 220 is configured to obtain real-time monitoring data of the target device group.
The analyzing module 230 is configured to analyze the real-time monitoring data and obtain a scene type and a target device corresponding to the real-time monitoring data.
The pushing module 240 is configured to push the real-time monitoring data to the network client registered with the scene type and the target device via a real-time pushing data channel.
Fig. 5 is a schematic structural diagram of a data real-time pushing device according to an alternative embodiment of the present invention. As shown in fig. 5, the data real-time pushing apparatus 200 further includes: the first establishing module 250 is configured to receive a request for establishing a long connection from at least one network client, and establish the long connection with the network client.
The generating module 260 is configured to receive a registration request uploaded by the network client through the real-time push data channel, and generate and store a unique session ID with the network client in response to the registration request.
Optionally, referring to fig. 5, the data real-time pushing device 200 further includes: and a second establishing module 270 configured to establish a mapping relationship among the target device, the scene type, and the session ID, and store the mapping relationship in the mapping relationship table.
Optionally, referring to fig. 5, the pushing module 240 further includes: the first searching unit 241 is configured to search the mapping relationship table for a session ID corresponding to the scene type of the real-time monitoring data and the target device.
The first pushing unit 242 is configured to push the real-time monitoring data to the network client corresponding to the session ID.
Fig. 6 shows a schematic structural diagram of a data real-time pushing device according to another alternative embodiment of the present invention. As shown in fig. 6, the data real-time pushing apparatus 200 further includes: and a third establishing module 280 configured to establish a mapping relationship among the monitoring card, the scene type and the session ID and store the mapping relationship in the mapping relationship table.
In an alternative embodiment, the parsing module is further configured to: and analyzing the real-time monitoring data, and acquiring a scene type, a target device and a parameter type corresponding to the real-time monitoring data.
Optionally, as shown in fig. 6, the pushing module 240 includes: the determining unit 243 is configured to determine a monitoring card corresponding to the target device and the parameter type corresponding to the real-time monitoring data.
The second lookup unit 244 is configured to lookup a session ID corresponding to the monitoring card and the scene type in the mapping relationship table.
The second pushing unit 245 is configured to push the real-time monitoring data to the network client corresponding to the session ID.
In an alternative embodiment, the scenario type includes device monitoring; and the data type includes at least one of: temperature, humidity.
Optionally, as shown in fig. 5 to 6, the data real-time pushing apparatus 200 further includes: a logout deletion module 290 configured to receive a disconnection request sent by a network client via a real-time push data channel; and according to the disconnection request, logging off the session ID and deleting the data related to the session ID.
The invention provides a real-time data pushing method and a real-time data pushing device, and based on the method provided by the invention, a data channel and a parameter registration, analysis, cancellation and deletion method do not need to be developed for each scene type, and if the service requirement changes, only one set of method needs to be modified, so that the resource waste caused by repeated development is avoided, and the maintainability is higher.
It is clear to those skilled in the art that the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and for the sake of brevity, further description is omitted here.
In addition, the functional units in the embodiments of the present invention may be physically independent of each other, two or more functional units may be integrated together, or all the functional units may be integrated in one processing unit. The integrated functional units may be implemented in the form of hardware, or in the form of software or firmware.
Those of ordinary skill in the art will understand that: the integrated functional units, if implemented in software and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computing device (e.g., a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention when the instructions are executed. And the aforementioned storage medium includes: u disk, removable hard disk, Read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disk, and other various media capable of storing program code.
Alternatively, all or part of the steps of implementing the foregoing method embodiments may be implemented by hardware (such as a computing device, e.g., a personal computer, a server, or a network device) associated with program instructions, which may be stored in a computer-readable storage medium, and when the program instructions are executed by a processor of the computing device, the computing device executes all or part of the steps of the method according to the embodiments of the present invention.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments can be modified or some or all of the technical features can be equivalently replaced within the spirit and principle of the present invention; such modifications or substitutions do not depart from the scope of the present invention.
Claims (12)
1. A real-time data pushing method is characterized by comprising the following steps:
receiving and storing a scene type registered by at least one network client through a real-time push data channel and target equipment monitored under the scene type;
acquiring real-time monitoring data of a target equipment group;
analyzing the real-time monitoring data, and acquiring a scene type and target equipment corresponding to the real-time monitoring data;
and pushing the real-time monitoring data to the network client which is registered with the scene type and the target equipment through the real-time pushing data channel.
2. The real-time data pushing method according to claim 1, wherein before the receiving and saving the scene type registered by the at least one network client via the real-time push data channel and the target device monitored under the scene type, the method further comprises:
receiving a request for establishing long connection sent by at least one network client, and establishing long connection with the network client; and
and receiving a registration request uploaded by the network client through the real-time push data channel, responding to the registration request, generating and storing a unique session ID of the network client.
3. The real-time data pushing method according to claim 2, wherein after receiving and saving the scene type registered by the at least one network client via the real-time push data channel and the target device monitored under the scene type, the method further comprises:
and establishing a mapping relation among the target equipment, the scene type and the session ID and storing the mapping relation in a mapping relation table.
4. The real-time data pushing method according to claim 3, wherein pushing the real-time monitoring data to the network client registered with the scene type and the target device via the real-time data pushing channel comprises:
searching a session ID corresponding to the scene type of the real-time monitoring data and the target equipment in the mapping relation table;
and pushing the real-time monitoring data to a network client corresponding to the session ID.
5. The real-time data pushing method according to claim 3, wherein the scene type includes at least one of:
equipment upgrading, equipment state sensing, equipment name changing, equipment area transferring, equipment parameter changing and gateway equipment scanning progress.
6. The real-time data pushing method according to claim 2, wherein the receiving and saving of the scene type registered by the at least one network client via the real-time push data channel and the target device monitored under the scene type includes:
receiving and storing the scene type and the monitoring card registered by at least one network client through a real-time push data channel; the monitoring card comprises target equipment and parameter types which are monitored under the scene types, and a mapping relation exists between the monitoring card and the target equipment and between the monitoring card and the parameter types.
7. The real-time data pushing method according to claim 6, wherein after receiving and storing the scene type and the monitoring card registered by the at least one network client via the real-time data pushing channel, the method further comprises:
and establishing a mapping relation among the monitoring card, the scene type and the session ID and storing the mapping relation in a mapping relation table.
8. The real-time data pushing method according to claim 7, wherein analyzing the real-time monitoring data to obtain a scene type and a target device corresponding to the real-time monitoring data includes:
and analyzing the real-time monitoring data, and acquiring a scene type, a target device and a parameter type corresponding to the real-time monitoring data.
9. The real-time data pushing method according to claim 8, wherein pushing the real-time monitoring data to the network client registered with the scene type and the target device via the real-time data pushing channel comprises:
determining target equipment corresponding to the real-time monitoring data and a monitoring card corresponding to the parameter type;
searching a session ID corresponding to the monitoring card and the scene type in the mapping relation table;
and pushing the real-time monitoring data to a network client corresponding to the session ID.
10. The real-time data pushing method according to claim 6,
the scene type comprises equipment monitoring; and
the data type includes at least one of: temperature, humidity.
11. The real-time data pushing method according to claim 2, further comprising:
receiving a disconnection request sent by the network client through the real-time push data channel; and
and according to the disconnection request, logging off the session ID and deleting data related to the session ID.
12. A real-time data pushing device is characterized by comprising:
the receiving module is configured to receive and store a scene type registered by at least one network client through a real-time push data channel and target equipment monitored under the scene type;
the monitoring module is configured to acquire real-time monitoring data of the target equipment group;
the analysis module is configured to analyze the real-time monitoring data and acquire a scene type and target equipment corresponding to the real-time monitoring data;
and the pushing module is configured to push the real-time monitoring data to the network client which is registered with the scene type and the target device through the real-time pushing data channel.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911398737.2A CN111294382A (en) | 2019-12-30 | 2019-12-30 | Real-time data pushing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911398737.2A CN111294382A (en) | 2019-12-30 | 2019-12-30 | Real-time data pushing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111294382A true CN111294382A (en) | 2020-06-16 |
Family
ID=71029058
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911398737.2A Pending CN111294382A (en) | 2019-12-30 | 2019-12-30 | Real-time data pushing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111294382A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114064699A (en) * | 2021-10-27 | 2022-02-18 | 北京市农林科学院信息技术研究中心 | Internet of things equipment monitoring index dynamic management and data analysis method and device |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1609853A (en) * | 2003-06-13 | 2005-04-27 | 微软公司 | Context association diagram for computer system architecture |
| CA2595830A1 (en) * | 2007-08-01 | 2009-02-01 | Nortel Networks Limited | A smart communications system for integration into a workflow-engaged clinical environment |
| CN102521885A (en) * | 2011-12-29 | 2012-06-27 | 国网信息通信有限公司 | Method for displaying monitoring data of power grid and device |
| CN104349373A (en) * | 2013-08-07 | 2015-02-11 | 华为终端有限公司 | Terminal monitoring event posting method, application server and home location equipment |
| CN104469315A (en) * | 2014-12-17 | 2015-03-25 | 浙江宇视科技有限公司 | CDN-based video data stream transmission method, device and system |
| US20160164978A1 (en) * | 2014-12-05 | 2016-06-09 | Unify Gmbh & Co. Kg | Method and system for telecommunication device monitoring |
| CN107819748A (en) * | 2017-10-26 | 2018-03-20 | 北京顶象技术有限公司 | A kind of anti-identifying code implementation method cracked and device |
| CN108306953A (en) * | 2018-01-23 | 2018-07-20 | 江苏微物网络科技有限公司 | A kind of strong compatible real time push method presented for Internet of Things application data |
| CN108616606A (en) * | 2018-08-01 | 2018-10-02 | 湖南恒茂高科股份有限公司 | A kind of Internet of Things communication means and device |
| CN109525466A (en) * | 2019-01-03 | 2019-03-26 | 杭州云英网络科技有限公司 | Back end monitor method and device |
| CN109783707A (en) * | 2019-01-23 | 2019-05-21 | 欧普照明股份有限公司 | A kind of moade setting method and device of monitoring system |
| CN110223696A (en) * | 2019-05-22 | 2019-09-10 | 平安科技（深圳）有限公司 | A kind of acquisition method of voice signal, device and terminal device |
-
2019
- 2019-12-30 CN CN201911398737.2A patent/CN111294382A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1609853A (en) * | 2003-06-13 | 2005-04-27 | 微软公司 | Context association diagram for computer system architecture |
| CA2595830A1 (en) * | 2007-08-01 | 2009-02-01 | Nortel Networks Limited | A smart communications system for integration into a workflow-engaged clinical environment |
| CN102521885A (en) * | 2011-12-29 | 2012-06-27 | 国网信息通信有限公司 | Method for displaying monitoring data of power grid and device |
| CN104349373A (en) * | 2013-08-07 | 2015-02-11 | 华为终端有限公司 | Terminal monitoring event posting method, application server and home location equipment |
| US20160164978A1 (en) * | 2014-12-05 | 2016-06-09 | Unify Gmbh & Co. Kg | Method and system for telecommunication device monitoring |
| CN104469315A (en) * | 2014-12-17 | 2015-03-25 | 浙江宇视科技有限公司 | CDN-based video data stream transmission method, device and system |
| CN107819748A (en) * | 2017-10-26 | 2018-03-20 | 北京顶象技术有限公司 | A kind of anti-identifying code implementation method cracked and device |
| CN108306953A (en) * | 2018-01-23 | 2018-07-20 | 江苏微物网络科技有限公司 | A kind of strong compatible real time push method presented for Internet of Things application data |
| CN108616606A (en) * | 2018-08-01 | 2018-10-02 | 湖南恒茂高科股份有限公司 | A kind of Internet of Things communication means and device |
| CN109525466A (en) * | 2019-01-03 | 2019-03-26 | 杭州云英网络科技有限公司 | Back end monitor method and device |
| CN109783707A (en) * | 2019-01-23 | 2019-05-21 | 欧普照明股份有限公司 | A kind of moade setting method and device of monitoring system |
| CN110223696A (en) * | 2019-05-22 | 2019-09-10 | 平安科技（深圳）有限公司 | A kind of acquisition method of voice signal, device and terminal device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114064699A (en) * | 2021-10-27 | 2022-02-18 | 北京市农林科学院信息技术研究中心 | Internet of things equipment monitoring index dynamic management and data analysis method and device |
| CN114064699B (en) * | 2021-10-27 | 2023-12-26 | 北京市农林科学院信息技术研究中心 | Method and device for dynamic management and data analysis of monitoring indexes of Internet of things equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20190075049A1 (en) | Determining Direction of Network Sessions | |
| CN110247784B (en) | Method and device for determining network topology structure | |
| US9379952B2 (en) | Monitoring NAT behaviors through URI dereferences in web browsers | |
| CN110808879B (en) | Protocol identification method, device, equipment and readable storage medium | |
| CN103297270A (en) | Application type recognition method and network equipment | |
| US10003543B2 (en) | Communication device, communication system, and communication method | |
| CN104079571A (en) | Method and device for recognizing Android simulator | |
| CN108156223A (en) | A kind of accurate supplying system of message based on websocket and method | |
| CN109286684B (en) | Communication connection processing method and device, proxy server and storage medium | |
| CN111294382A (en) | Real-time data pushing method and device | |
| Wang et al. | Smart devices information extraction in home wi‐fi networks | |
| US11178593B2 (en) | Terminal, relay apparatus selection apparatus, communication method, relay apparatus selection method, and program | |
| CN103036789B (en) | File transmitting method, device and network gateway devices | |
| CN110572394B (en) | Access control method and device | |
| WO2017005118A1 (en) | Method, device, terminal and server for maintaining communication connection | |
| JP6605149B2 (en) | Method and apparatus for detecting shared terminal | |
| KR20110057529A (en) | A system of measuring server's response time by using a dummy request tag and the method thereof | |
| KR100920528B1 (en) | Method and system of detecting and defensing arp spoofing | |
| CN114070761B (en) | Protocol message detection method and device and electronic equipment | |
| CN111327716B (en) | Service interaction method and device | |
| CN105577433A (en) | ACS cluster management method, apparatus and system | |
| CN105025028A (en) | IP black hole discovering method based on flow analysis | |
| CN110798542A (en) | Method and system for acquiring IP address | |
| CN110868317B (en) | Equipment monitoring method and device, electronic equipment and storage medium | |
| CN117729054B (en) | VPN flow identification method and system based on full flow storage |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200616 |
|
| RJ01 | Rejection of invention patent application after publication |