CN110995566A - Message data pushing method, system and device - Google Patents

Message data pushing method, system and device Download PDF

Info

Publication number
CN110995566A
CN110995566A CN201911044147.XA CN201911044147A CN110995566A CN 110995566 A CN110995566 A CN 110995566A CN 201911044147 A CN201911044147 A CN 201911044147A CN 110995566 A CN110995566 A CN 110995566A
Authority
CN
China
Prior art keywords
message
data
data information
user client
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.)
Pending
Application number
CN201911044147.XA
Other languages
Chinese (zh)
Inventor
邱浩翔
卫宣安
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Genew Technologies Co Ltd
Original Assignee
Shenzhen Genew Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Genew Technologies Co Ltd filed Critical Shenzhen Genew Technologies Co Ltd
Priority to CN201911044147.XA priority Critical patent/CN110995566A/en
Publication of CN110995566A publication Critical patent/CN110995566A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21Monitoring or handling of messages
    • H04L51/214Monitoring or handling of messages using selective forwarding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1044Group management mechanisms 
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/55Push-based network services

Abstract

The invention discloses a message data pushing method, a system and a device, wherein a Canal component is utilized to monitor whether data information in a database of an acquisition server changes, if so, the changed data information is acquired, the changed data information is sent to a message middleware, and the changed data information is pushed to each user client through the message middleware. The message data pushing method disclosed by the invention starts with the configuration of the acquisition server, automatically pushes the information corresponding to the table name subscribed by the user client for the user client, thereby realizing the real-time pushing of the data, establishes an information channel between the user client and the acquisition server by using the message middleware, has wide application range, not only supports web application, but also can be applied to application scenes that other message middleware supports transmission, thereby obtaining better message data pushing effect and improving the pushing efficiency of the message data.

Description

Message data pushing method, system and device
Technical Field
The present invention relates to the field of information push technologies, and in particular, to a method, a system, and a device for pushing message data.
Background
The collection server is a server specially used for collecting and receiving information reported by the terminal and storing collected data into the server, for example: the system comprises a GPS positioning information acquisition server, an air conditioner parameter information acquisition server, a water meter information acquisition server and the like, wherein the GPS positioning information acquisition server is connected with the acquisition server when acquiring appointed data information, and the acquisition server pushes the appointed data information, so that the pressure of the acquisition server is improved, the data pushing efficiency is low, and the data acquisition server cannot acquire the data in real time due to the fact that query needs a certain time. In order to solve the problem of low data pushing efficiency, a common solution is that other servers query the database of the acquisition server each time, but this method only relieves the pressure of data pushing, and also has the problems that certain query time is required and real-time data acquisition cannot be realized, and the requirement that a user needs to synchronously acquire message data cannot be met.
Therefore, the prior art is subject to further improvement.
Disclosure of Invention
In view of the defects in the prior art, the invention provides a message data pushing method, a system and a device, which overcome the defects that a plurality of user clients are connected with an acquisition server at the same time, and the data processing task pressure of an inquiry server is overlarge when inquiring specified information, so that the data inquiry is failed, the data inquiry efficiency is low, and the real-time performance of the inquired data is low.
The embodiment of the invention discloses a message data pushing method, which comprises the following steps:
when the local component monitors that the data information in the database of the acquisition server changes, acquiring the changed data information, and sending the changed data information to the message middleware;
and the message middleware pushes the changed data information to a user client.
Optionally, the step of acquiring the changed data information when the cancer component monitors that the data information in the database of the acquisition server changes, and sending the changed data information to the message middleware includes:
and establishing communication connection between the acquisition server and the Canal component, and establishing communication connection between the acquisition server, the user client and the message middleware.
Optionally, after the step of establishing communication connection among the collection server, the user client, and the message middleware, the method further includes:
and the user client sends subscription information and the message queue name of the message middleware to the acquisition server.
Optionally, the step of acquiring the changed data information when the cancer component monitors that the data information in the database of the acquisition server changes, and sending the changed data information to the message middleware includes:
the acquisition server acquires subscription information and a message queue name sent by the user client and stores the subscription information and the message queue name in a connection library;
and the connection library sends the changed data information to the message middleware according to the subscription information and the message queue name.
Optionally, the step of sending the changed data information to the message middleware by the connection library according to the subscription information and the message queue name further includes:
according to the table names contained in the received user subscription information, performing data integration on the data information, and enabling the content contained in the data information to correspond to each table name in the subscription information;
and distributing the integrated data columns corresponding to the table names according to the message queue names corresponding to the table names.
Optionally, the number of the user clients is multiple, each user client corresponds to one message queue, and the names of any two message queues are different.
Optionally, the step of distributing the integrated data columns corresponding to the table names according to the message queue names corresponding to the table names includes:
and acquiring a callback function corresponding to the table name according to the table name corresponding to the subscription information, and calling the callback function to realize distribution of each data column.
Optionally, after the step of pushing the changed data information to the user client by the message middleware, the method further includes:
and each user client monitors the data information pushed by the message middleware and receives the message queue name in the data information and the corresponding data column.
The embodiment also discloses a message data pushing system, which includes: the system comprises an acquisition server, a user client and a message middleware which is in communication connection with the acquisition server and the user client;
a Canal component and a database; the message middleware is arranged on the acquisition server or the user client side or is independent of the acquisition server or the user client side;
the local component is used for monitoring the change of data information in the database of the acquisition server; when the data information in the database is monitored to be changed, the changed data information is obtained, and the changed data information is sent to a message middleware;
and the message middleware is used for pushing the changed data information to the user client.
The embodiment also discloses a message data pushing terminal, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method when executing the computer program.
The invention discloses a message data pushing method, a system and a device, which utilize a Canal component to monitor whether data information in a database of an acquisition server changes, if so, obtain the changed data information, send the changed data information to a message middleware, and push the changed data information to each user client through the message middleware. The message data pushing method disclosed by the invention starts with the configuration of the acquisition server, automatically pushes the information corresponding to the table name subscribed by the user client for the user client, thereby realizing the real-time pushing of the data, establishes an information channel between the user client and the acquisition server by using the message middleware, has wide application range, not only supports web application, but also can be applied to application scenes that other message middleware supports transmission, thereby obtaining better message data pushing effect and improving the pushing efficiency of the message data.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a block diagram of an exemplary application scenario in an embodiment of the present invention;
FIG. 2 is a flowchart illustrating steps of a message data pushing method according to an embodiment of the present invention;
FIG. 3 is a flow chart of the steps of an initialization process in an embodiment of the method of the present invention;
FIG. 4 is a flowchart of the steps of message data push in a particular embodiment of a method according to an embodiment of the present invention;
fig. 5 is a block diagram of the schematic structure of the system in the embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer and clearer, the present invention is further described in detail below with reference to the accompanying drawings and examples. 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 inventor finds that, for the existing collection server, because each user client needs to acquire data information from the collection server, when a plurality of user clients send query requests to the collection server synchronously, the data push of the collection server generates a large pressure, and certain information processing time is needed for querying the data information and pushing the queried data information, and the longer the data processing time of the collection server is, the lower the real-time performance of data query is, for example: when a user client inquires the GPS positioning information, if the inquiry time is long, the displayed GPS positioning information may be inaccurate, and the inquired GPS positioning information has a lag phenomenon.
In order to solve the above problem, in the embodiment of the present invention, when a message middleware that establishes a connection with both the acquisition server and the user client is used, the push of message data from the acquisition server to each user client is implemented. The method comprises the steps that a Canal component used for monitoring whether message data stored in a database changes or not is arranged in an acquisition server, when the Canal component monitors that the message data stored in the database changes, the acquisition server can send data information to a user client through a message middleware according to the table name subscribed by the user client if the changed message data contains the data information corresponding to the table name subscribed by each user client.
For example, the embodiment of the present invention may be applied to a scenario as shown in fig. 1, in which a communication connection is established between a user client 101 and an acquisition server 102, and a cancer component and a database are disposed on the acquisition server; the message middleware is arranged on the acquisition server or the user client side or is independent of the acquisition server or the user client side; the method is used for connecting the acquisition server on the client side and connecting a message middleware, and after the user client is connected to the acquisition server, the message queue name of the message middleware connected with the user client and the table name which the user client wants to subscribe are sent to the acquisition server. And the database for storing the message data information on the acquisition server is connected with a Canal component, the Canal component monitors whether the data information stored in the database changes, when the stored data information changes, the data is pushed to a message middleware connected with the user client according to a subscribed table name provided by the user client, and the message middleware transmits the received data information to the user client. The pushed data information can be GPS positioning data collected by a collection server, or water flow on a water meter, collected temperature values or other collected data.
It should be noted that the above application scenarios are only presented to facilitate understanding of the present invention, and the embodiments of the present invention are not limited in any way in this respect. Rather, embodiments of the present invention may be applied to any scenario where applicable.
Various non-limiting embodiments of the present invention are described in detail below with reference to the accompanying drawings.
Exemplary method
Referring to fig. 2, an embodiment of the present invention discloses a message data pushing method, and in this embodiment, the method may include the following steps:
and step S1, when the cancer component monitors that the data information in the database of the acquisition server changes, acquiring the changed data information, and sending the changed data information to the message middleware.
Specifically, the method includes the steps of disguising the local copy as mysql slave through an interaction protocol simulating mysql slave, sending a dump protocol mysql master to the mysql master to receive a dump request, starting pushing a binary log to the slave (namely, Canal), and analyzing a binary log object (originally a byte stream) by the Canal so as to obtain incremental data information of the database. In the step, incremental data information generated in a database in an acquisition server is monitored by using a Canal component, the data information is acquired, and the data information is sent to a message middleware.
The message middleware is non-bottom operating system software and non-business application software, is used for sending and receiving data, and can send messages between two application programs or in a distributed system to carry out asynchronous communication, so that the message middleware can be installed on a user client, or an acquisition server, or can be installed on third terminal equipment except the user client and the acquisition server, as long as the message middleware is kept capable of receiving data information pushed by a Canal component in the acquisition server and sending the data information to the user client.
Specifically, the step of acquiring the changed data information when the cancer component monitors that the data information in the database of the acquisition server changes, and sending the changed data information to the message middleware includes:
and establishing communication connection between an acquisition server and the Canal component, and establishing communication connection between the acquisition server and the user client.
And step S2, the message middleware pushes the changed data information to the user client.
The message middleware is in a queue mode, and can receive the data information pushed by the Canal component in the step S1, and send the data information to the user client.
In an embodiment, the number of the user clients may be several, and after connecting the user clients to the message middleware, the table names subscribed by the user clients are sent to the message middleware, and a message queue is monitored to obtain the names of the monitored message queue.
Specifically, after the step of establishing a communication connection between the acquisition server and the user client, the method further includes:
and the user client sends subscription information and the message queue name of the message middleware to the acquisition server.
After the user client establishes communication connection with the acquisition server, the user client sends the list name subscribed by the acquisition server and the message queue name of the message middleware monitored by the acquisition server through the Restful interface, and then after the local component monitors that the data in the database in the acquisition server changes, the changed data information is sent to the user client according to the list name subscribed by the user client and the message queue name monitored by the user client.
Specifically, the step of acquiring the changed data information when the cancer component monitors that the data information in the database of the acquisition server changes, and sending the changed data information to the message middleware includes:
the acquisition server acquires subscription information and a message queue name sent by the user client and stores the subscription information and the message queue name in a connection library;
and the connection library sends the changed data information to the message middleware according to the subscription information and the message queue name.
In the above steps, a connection library is used to store the subscription information and the message queue name sent to the collection server by the user, and after the collection server receives the subscription information and the message queue name, the information is stored.
Specifically, the number of the user clients is multiple, each user client corresponds to one message queue, and the names of any two message queues are different. The step of sending the changed data information to the message middleware by the link library according to the subscription information and the message queue name further comprises the following steps:
according to the table names contained in the received user subscription information, performing data integration on the data information, and enabling the content contained in the data information to correspond to each table name in the subscription information;
and distributing the integrated data columns corresponding to the table names according to the message queue names corresponding to the table names.
Each user client is in one-to-one correspondence with the table name subscribed by the user client and the message queue name in the connected message middleware, when the Canal component pushes the changed data information to the message middleware, the changed data information is integrated according to the table name subscribed by the user client and the corresponding message queue name, a corresponding callback function is called according to the table name subscribed by each user client, and corresponding data information pushing is carried out according to the corresponding message queue name, so that data distribution is realized.
In a specific implementation, the step of distributing the integrated data columns corresponding to the table names according to the message queue names corresponding to the table names includes:
and acquiring a callback function corresponding to the table name according to the table name corresponding to the subscription information, and calling the callback function to realize distribution of each data column.
Because the Canal component pushes and integrates N rows of data to the message middleware at one time, in order to realize the distribution of each row of data, the name of a database table of the N rows of data and the data are written into a dictionary, the name of the database table is Key, Value is data, then the dictionary is traversed, if the name of the table is subscribed by a user, a callback function provided by the user is called in a multithreading mode, and the parameter is the data transmitted by the Canal.
Specifically, after the step of pushing the changed data information to the user client by the message middleware, the method further includes:
and each user client monitors the data information pushed by the message middleware and receives the message queue name in the data information and the corresponding data column.
A further more detailed description of a specific embodiment of the method of the present invention is provided in connection with fig. 3 and 4.
Step H1, at the beginning, because the cancer component monitors the data change in the database by simulating the interaction protocol of mysql slave, mysql needs to be configured first, and the start of the cancer component is realized by opening the bindlog.
And step H2, establishing connection between the database in the acquisition server and the Canal component, and judging whether the connection is successful, if not, monitoring the data information of the database by using the Canal component cannot be realized, so that if the connection is successful, the next step can be performed, otherwise, the Canal component needs to be reconnected until the connection is successful.
And step H3, the collection server receives the subscribed table names sent by each user client and records callback functions corresponding to the subscribed table names.
And after the steps are completed, the initialization process of the acquisition server is finished.
As shown in fig. 4, after the initialization process is completed, a message data pushing step is executed, which specifically includes the following steps:
g1, the collection server inserts the received message data into the database, and the message data is stored through the database.
G2, the Canal component monitors that the message data in the database are changed by monitoring the log file of the database.
G3, the connection library connected with the cancer component receives that the message data in the database changes.
G4, judging whether the number of the integration data pushed by the Canal component is 0, if so, executing a step G5, otherwise, executing a step G6.
G5, judging whether the length of the table name subscribed by the user client is 0 or not, if so, judging whether the length of the table name is 0 or not, judging whether the data type and the data are both 0 or not, if so, ending, otherwise, executing a step G8.
G6, taking out the table name. The table names herein may be a plurality of preset table names, which include table names that the user client may subscribe to.
G7, adding the message data to the dictionary according to the table name.
G8, traversing the dictionary, and extracting corresponding data from the dictionary according to the table names.
G9, judging whether the table name contained in the extracted data has the table name subscribed by the user client, if so, calling a callback function according to the table name subscribed by the user client to push the data to the client.
The processes of steps G7 to G9 further include a process of extracting or calling a callback function for multiple times, so that all data corresponding to the table name contained in the message data pushed by the Cananl component are written into the dictionary, and according to the table name sent by the user client, all dictionaries are traversed, all data corresponding to the table name subscribed by the user client are found, so that all message data corresponding to the table name subscribed by the user client are pushed successfully.
Exemplary device
The embodiment also discloses a message data pushing system, as shown in fig. 5, including: the system comprises an acquisition server 10, a user client 20 and a message middleware 30 which is in communication connection with the acquisition server and the user client;
the acquisition server 10 is provided with: a Canal component 101 and a database 102;
the Canal component 101 is configured to monitor that data information in the database 102 of the acquisition server 10 changes; when the data information in the database 102 is monitored to be changed, the changed data information is acquired, and the changed data information is sent to the message middleware 30;
the message middleware 30 is configured to push the changed data information to the user client.
The embodiment also discloses a message data pushing terminal, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method when executing the computer program.
The message data pushing method, the message data pushing system and the message data pushing device disclosed by the invention utilize the Canal component to monitor whether the data information in the database of the acquisition server changes or not, if so, the changed data information is obtained, the changed data information is sent to the message middleware, and the changed data information is pushed to each user client through the message middleware. The message data pushing method disclosed by the invention starts with the configuration of the acquisition server, automatically pushes the information corresponding to the table name subscribed by the user client for the user client, thereby realizing the real-time pushing of the data, establishes an information channel between the user client and the acquisition server by using the message middleware, has wide application range, not only supports web application, but also can be applied to application scenes that other message middleware supports transmission, thereby obtaining better message data pushing effect and improving the pushing efficiency of the message data.
It will be understood that the invention is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is only limited by the appended claims
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.

Claims (10)

1. A message data pushing method is characterized by comprising the following steps:
when the local component monitors that the data information in the database of the acquisition server changes, acquiring the changed data information, and sending the changed data information to the message middleware;
and the message middleware pushes the changed data information to a user client.
2. The message data pushing method according to claim 1, wherein the step of acquiring the changed data information when the cancer component monitors that the data information in the database of the collection server changes, and sending the changed data information to the message middleware comprises:
and establishing communication connection between the acquisition server and the Canal component, and establishing communication connection between the acquisition server and the user client.
3. The message data pushing method according to claim 2, wherein after the step of establishing a communication connection between the collection server and the user client, the method further comprises:
and the user client sends subscription information and the message queue name of the message middleware to the acquisition server.
4. The message data pushing method according to claim 3, wherein the step of acquiring the changed data information when the cancer component monitors that the data information in the database of the collection server changes, and sending the changed data information to the message middleware comprises:
the acquisition server acquires subscription information and a message queue name sent by the user client and stores the subscription information and the message queue name in a connection library;
and the connection library sends the changed data information to the message middleware according to the subscription information and the message queue name.
5. The message data pushing method according to claim 4, wherein the step of sending the changed data information to the message middleware by the connection library according to the subscription information and the message queue name further comprises:
according to the table names contained in the received user subscription information, performing data integration on the data information, and enabling the content contained in the data information to correspond to each table name in the subscription information;
and distributing the integrated data columns corresponding to the table names according to the message queue names corresponding to the table names.
6. The message data pushing method according to claim 1, wherein the number of the user clients is plural, each user client corresponds to one message queue, and names of any two message queues are different.
7. The message data pushing method according to claim 5, wherein the step of distributing the integrated data columns corresponding to the table names according to the message queue names corresponding to the table names comprises:
and acquiring a callback function corresponding to the table name according to the table name corresponding to the subscription information, and calling the callback function to realize distribution of each data column.
8. The message data pushing method according to claim 7, wherein after the step of the message middleware pushing the changed data information to the user client, the method further comprises:
and each user client monitors the data information pushed by the message middleware and receives the message queue name in the data information and the corresponding data column.
9. A message data push system, comprising: the method comprises the steps of collecting a server and a user client;
the acquisition server is provided with: a Canal component and a database; the message middleware is arranged on the acquisition server or the user client side or is independent of the acquisition server or the user client side;
the local component is used for monitoring the change of data information in the database of the acquisition server; when the data information in the database is monitored to be changed, the changed data information is obtained, and the changed data information is sent to a message middleware;
and the message middleware is used for pushing the changed data information to the user client.
10. Message data push terminal comprising a memory and a processor, the memory storing a computer program, characterized in that the processor realizes the steps of the method according to any of claims 1 to 8 when executing the computer program.
CN201911044147.XA 2019-10-30 2019-10-30 Message data pushing method, system and device Pending CN110995566A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911044147.XA CN110995566A (en) 2019-10-30 2019-10-30 Message data pushing method, system and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911044147.XA CN110995566A (en) 2019-10-30 2019-10-30 Message data pushing method, system and device

Publications (1)

Publication Number Publication Date
CN110995566A true CN110995566A (en) 2020-04-10

Family

ID=70082639

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911044147.XA Pending CN110995566A (en) 2019-10-30 2019-10-30 Message data pushing method, system and device

Country Status (1)

Country Link
CN (1) CN110995566A (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112256954A (en) * 2020-09-08 2021-01-22 国网宁夏电力有限公司经济技术研究院 Message pushing processing method and related system
CN112738182A (en) * 2020-12-24 2021-04-30 海南车智易通信息技术有限公司 Data pushing system, data pushing method and computing equipment
CN114401315A (en) * 2021-12-31 2022-04-26 广东国腾量子科技有限公司 Message push service system and method based on dynamic decision model
WO2023138185A1 (en) * 2022-01-24 2023-07-27 华为技术有限公司 Information pushing method and server

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080181419A1 (en) * 2007-01-22 2008-07-31 Personics Holdings Inc. Method and device for acute sound detection and reproduction
CN104408132A (en) * 2014-11-28 2015-03-11 北京京东尚科信息技术有限公司 Data push method and system
CN106301972A (en) * 2016-11-16 2017-01-04 北京集奥聚合科技有限公司 A kind of monitoring data push away method and system in real time
CN108763234A (en) * 2018-02-01 2018-11-06 宝付网络科技(上海)有限公司 A kind of real time data synchronization method and system
CN108804237A (en) * 2017-05-05 2018-11-13 北京京东尚科信息技术有限公司 Data real-time statistical method, device, storage medium and electronic equipment
CN109151056A (en) * 2018-09-26 2019-01-04 携程计算机技术(上海)有限公司 Information push method and system based on Canal
CN109241072A (en) * 2018-08-31 2019-01-18 携程计算机技术(上海)有限公司 Buffering updating method and system based on Canal
CN109871406A (en) * 2018-12-28 2019-06-11 北京云杉信息技术有限公司 The design method of universal monitor report platform

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080181419A1 (en) * 2007-01-22 2008-07-31 Personics Holdings Inc. Method and device for acute sound detection and reproduction
CN104408132A (en) * 2014-11-28 2015-03-11 北京京东尚科信息技术有限公司 Data push method and system
CN106301972A (en) * 2016-11-16 2017-01-04 北京集奥聚合科技有限公司 A kind of monitoring data push away method and system in real time
CN108804237A (en) * 2017-05-05 2018-11-13 北京京东尚科信息技术有限公司 Data real-time statistical method, device, storage medium and electronic equipment
CN108763234A (en) * 2018-02-01 2018-11-06 宝付网络科技(上海)有限公司 A kind of real time data synchronization method and system
CN109241072A (en) * 2018-08-31 2019-01-18 携程计算机技术(上海)有限公司 Buffering updating method and system based on Canal
CN109151056A (en) * 2018-09-26 2019-01-04 携程计算机技术(上海)有限公司 Information push method and system based on Canal
CN109871406A (en) * 2018-12-28 2019-06-11 北京云杉信息技术有限公司 The design method of universal monitor report platform

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
周豪: "大数据量下的实时数据报表系统的设计与实现", 《中国优秀硕士学位论文全文数据库》 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112256954A (en) * 2020-09-08 2021-01-22 国网宁夏电力有限公司经济技术研究院 Message pushing processing method and related system
CN112738182A (en) * 2020-12-24 2021-04-30 海南车智易通信息技术有限公司 Data pushing system, data pushing method and computing equipment
CN114401315A (en) * 2021-12-31 2022-04-26 广东国腾量子科技有限公司 Message push service system and method based on dynamic decision model
CN114401315B (en) * 2021-12-31 2023-09-12 广东国腾量子科技有限公司 Message push service system and method based on dynamic decision model
WO2023138185A1 (en) * 2022-01-24 2023-07-27 华为技术有限公司 Information pushing method and server

Similar Documents

Publication Publication Date Title
CN110995566A (en) Message data pushing method, system and device
CN109284334B (en) Real-time database synchronization method and device, electronic equipment and storage medium
CN111555963B (en) Message pushing method and device, electronic equipment and storage medium
CN108737473B (en) Data processing method, device and system
EP3706424A1 (en) Video live broadcast method and apparatus
CN109558065B (en) Data deleting method and distributed storage system
CN108228625B (en) Push message processing method and device
CN111966289B (en) Partition optimization method and system based on Kafka cluster
US20110153651A1 (en) Apparatus and method for remotely monitoring terminal
CN114328618B (en) Cache data synchronization method, device, equipment and storage medium
US11188443B2 (en) Method, apparatus and system for processing log data
CN104243610A (en) Distributed file transmission service method
CN110928934A (en) Data processing method and device for business analysis
CN112351068A (en) Information synchronization method, system, device, computer equipment and storage medium
EP3531640B1 (en) Data stream guiding method, server, and system
CN108063832B (en) Cloud storage system and storage method thereof
CN112052227A (en) Data change log processing method and device and electronic equipment
EP3742697A1 (en) Data transmission scheduling method and system
CN114125489A (en) Data stream distribution method and system
CN111737222A (en) Message queue data packet storage and retrieval method based on one-to-many request response model
EP3026860B1 (en) Method and system for transmission management of full configuration synchronization between eml-nml
CN115473858A (en) Data transmission method and streaming data transmission system
CN112764988B (en) Data segment acquisition method and device
CN103795810A (en) Data distribution system and method and central server of data distribution system
CN110781034B (en) Distributed supervision method and system

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
RJ01 Rejection of invention patent application after publication

Application publication date: 20200410