CN112787906A - Message pushing system based on cloud desktop platform - Google Patents
Message pushing system based on cloud desktop platform Download PDFInfo
- Publication number
- CN112787906A CN112787906A CN201911084847.1A CN201911084847A CN112787906A CN 112787906 A CN112787906 A CN 112787906A CN 201911084847 A CN201911084847 A CN 201911084847A CN 112787906 A CN112787906 A CN 112787906A
- Authority
- CN
- China
- Prior art keywords
- message
- server
- message pushing
- client
- cloud desktop
- 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
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/216—Handling conversation history, e.g. grouping of messages in sessions or threads
-
- 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
-
- 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
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- 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
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a message pushing system based on a cloud desktop platform, which belongs to the field of computers and comprises an application server, a load balancing server, a message pushing system server cluster, a client and a database. The invention can provide a good message interaction mode for managers and users of the cloud desktop platform, and the message pushing system can integrate the message notification function in the existing business system of an enterprise, so that the message is actively pushed to the user in time when the user uses the cloud desktop system, and better user experience is provided.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a message pushing system based on a cloud desktop platform.
Background
With the pace of information-based construction of enterprises, the I T infrastructure investment is also increasing. A series of problems such as complex configuration and deployment, high software and hardware upgrading cost, dispersed confidential data, incomplete data security guarantee mechanism and the like easily occur in the traditional I T infrastructure construction process, centralized management and maintenance of data are inconvenient, and an effective solution is provided for the cloud desktop platform.
However, a built-in message pushing system is not integrated in the cloud desktop platform in the current market, which brings great inconvenience to cloud desktop platform managers and users. For managers, the cloud desktop platform is large in scale, and the number of related users is large. In the maintenance process, when the daily work of a thin terminal user needs to be interrupted temporarily for some necessary operation and maintenance work, the user needs to be informed urgently. For a user, due to the novel use mode of the current cloud desktop, convenience is brought to the user, and meanwhile, some operation habits or other problems exist, and the operation habits or other problems need to be fed back to an administrator in time. Meanwhile, the cloud desktop system manages hundreds of software systems on the client side, and from the perspective of centralized management of a cloud desktop platform, it is also desirable to be able to integrate the commonalities of business systems. Therefore, the message notifications in the service systems can be accessed uniformly by means of the cloud desktop, and are presented once when the user uses the cloud desktop.
Chinese patent with application number CN201710053257.7 discloses a message push system based on MQTT and MYSQL, the system includes a server and a client, the server includes an MQTT server, a server service processing unit and a server MYSQL database, the client includes an MQTT client, a client service processing unit and a client MYSQL database, the server MYSQL database and the client MYSQL database are used for storing data, and the server service processing unit and the client service processing unit are used for service instruction and data processing. The invention adopts MQTT to maintain the connection mapping between the server and the client, realizes that a plurality of clients are connected with the server through one TCP long connection, and simplifies the connection mapping between the client and the server. The reliable pushing of the message is ensured through a repeated confirmation mechanism of the server and a repeated pulling mechanism of the client.
In the patent, the MYSQL database is used for reading data, but when messages are sent frequently and in large quantity, the messages may be lost, and meanwhile, when the data are sent, the database needs to be operated repeatedly, and frequent operation on the database reduces the efficiency of message pushing.
Disclosure of Invention
In view of the technical deficiencies, the present invention provides a message pushing system based on a cloud desktop platform, and aims to solve the problems that the current cloud desktop platform has no built-in message pushing system, and the patent mentioned in the background art may cause message loss when messages are frequently sent and the number of messages is large, and meanwhile, when data is sent, operations need to be repeated on a database, and the efficiency of message pushing is reduced when the databases are frequently operated.
In order to solve the technical problems, the invention adopts the following technical scheme:
the invention provides a message pushing system based on a cloud desktop platform, which comprises an application server, a load balancing server, a message pushing system server cluster, a client and a database, wherein the application server is connected with the load balancing server; the message pushing system server cluster is connected with the load balancing server, and the load balancing server is in communication connection with the client through an MQTT protocol and is used for actively pushing messages to the client; the message pushing system server cluster is also connected with the application server and used for receiving messages sent by the application server; the message pushing server cluster is in communication connection with the database and is used for calling data stored in the database.
Preferably, the load balancing server is configured to connect the client to any node in the message push server cluster.
Preferably, the system has a low-coupling layered architecture, specifically:
an application layer: the method is mainly a Web management interface facing a system administrator, and the system administrator can perform some service operations, such as theme management, manual message pushing, message management, message statistics, terminal feedback and the like
And a service logic layer: the core of the system is that the message push system can complete the function of actively pushing messages, and mainly depends on the processing of the layer, and the layer mainly has the following functions:
1) connection management: when the client applies for connection, the message system server can verify the account and the password input by the user, only the client subjected to authority verification is allowed to access the message system, and otherwise serious security threat can be caused to the whole message pushing system and even the whole cloud desktop platform.
2) Theme management: the method comprises the following steps that a message pushing system has topics which can be subscribed/unsubscribed by a user, and when a new topic is applied, how to add the topic to a proper position for storage; when a theme is no longer needed, how to delete, etc., proper operations need to be performed. According to the characteristics of the MQTT protocol, the message system adopts a multi-level hierarchical theme design mode, for example, under the theme of "/news", the/"/news/political theme can be provided, and simultaneously, the"/news/life "theme can also be provided, and all lower-layer themes under the"/news "theme can be matched simultaneously by using"/news/# ".
3) Subscription management of users: responsible for processing the logic associated with the topic subscription. Users can subscribe to topics of interest and unsubscribe to topics of no interest, and subscribers under each topic may be constantly changing. The subscription/unsubscription of the subscriber to the topic can happen successfully only by the message system returning the confirmation message, and the message pushing system maintains the subscriber list of each topic according to the received subscription/unsubscription request.
4) Message management: after the message push system receives the message, how to determine to which users the message needs to be forwarded and how to ensure that the message reliably reaches the users need to be processed strictly according to certain rules.
5) Storage management: and the message persistence is carried out, so that a system administrator can be helped to master the messages sent within a period of time and check the sending condition of the messages under each theme. Meanwhile, in the sending process, when the user is off-line or the message sending fails, a certain mechanism can be adopted to ensure that the message is reliably sent by the message persistence. The storage module uses two different databases of Red i s and Mysq l, and provides a more perfect message storage mechanism through the combination of the two databases. Storing data which is frequent and has low real-time requirement by using a Mysq l database; the Red is used as a cache layer for storing data with high real-time requirement. Red i s acts as a cache, and may be considered in addition to Mysq l.
An access layer: the client (including a message sender and a message subscriber) is accessed to an inlet of the message pushing system server cluster, and the client is in long connection with the message pushing system server cluster through an MQTT protocol so as to receive messages pushed by the message pushing system server cluster in time.
The invention has the beneficial effects that: compared with the prior art, the message pushing system based on the cloud desktop platform can provide a good message interaction mode for managers and users of the cloud desktop platform, can integrate the message notification function in the existing business system of an enterprise by using the message pushing system, can effectively push messages to the users in time when the users use the cloud desktop system, and provides better user experience.
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 of 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 a message pushing system based on a cloud desktop platform according to the present invention;
fig. 2 is a layered architecture diagram of a message push system based on a cloud desktop platform according to the present invention;
fig. 3 is an implementation flowchart of a message pushing system based on a cloud desktop platform according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments 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 of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, a message push system based on a cloud desktop platform includes an application server, a load balancing server, a message push system server cluster, a client, and a database; the message pushing system server cluster is connected with the load balancing server, and the load balancing server is in communication connection with the client through an MQTT protocol and is used for actively pushing messages to the client; the message pushing system server cluster is also connected with the application server and used for receiving messages sent by the application server; the message push server cluster is in communication connection with the database and is used for calling data stored in the database.
Further, the load balancing server is used for connecting the client to any node in the message push server cluster.
Further, as shown in fig. 2, the system has a low-coupling layered architecture, specifically:
an application layer: the method is mainly a Web management interface facing a system administrator, and the system administrator can perform some service operations, such as theme management, manual message pushing, message management, message statistics, terminal feedback and the like
And a service logic layer: the core of the system is that the message push system can complete the function of actively pushing messages, and mainly depends on the processing of the layer, and the layer mainly has the following functions:
6) connection management: when the client applies for connection, the message system server can verify the account and the password input by the user, only the client subjected to authority verification is allowed to access the message system, and otherwise serious security threat can be caused to the whole message pushing system and even the whole cloud desktop platform.
7) Theme management: the method comprises the following steps that a message pushing system has topics which can be subscribed/unsubscribed by a user, and when a new topic is applied, how to add the topic to a proper position for storage; when a theme is no longer needed, how to delete, etc., proper operations need to be performed. According to the characteristics of the MQTT protocol, the message system adopts a multi-level hierarchical theme design mode, for example, under the theme of "/news", the/"/news/political theme can be provided, and simultaneously, the"/news/life "theme can also be provided, and all lower-layer themes under the"/news "theme can be matched simultaneously by using"/news/# ".
8) Subscription management of users: responsible for processing the logic associated with the topic subscription. Users can subscribe to topics of interest and unsubscribe to topics of no interest, and subscribers under each topic may be constantly changing. The subscription/unsubscription of the subscriber to the topic can happen successfully only by the message system returning the confirmation message, and the message pushing system maintains the subscriber list of each topic according to the received subscription/unsubscription request.
9) Message management: after the message push system receives the message, how to determine to which users the message needs to be forwarded and how to ensure that the message reliably reaches the users need to be processed strictly according to certain rules.
10) Storage management: and the message persistence is carried out, so that a system administrator can be helped to master the messages sent within a period of time and check the sending condition of the messages under each theme. Meanwhile, in the sending process, when the user is off-line or the message sending fails, a certain mechanism can be adopted to ensure that the message is reliably sent by the message persistence. The storage module uses two different databases of Red i s and Mysq l, and provides a more perfect message storage mechanism through the combination of the two databases. Storing data which is frequent and has low real-time requirement by using a Mysq l database; the Red is used as a cache layer for storing data with high real-time requirement. Red i s acts as a cache, and may be considered in addition to Mysq l.
An access layer: clients (including message senders, message subscribers) access portals of the messaging system. The client side is in long connection with the message system through the MQTT protocol so as to receive the messages pushed by the message pushing system in time.
As shown in fig. 3, an implementation process of a message pushing system based on a cloud desktop platform specifically includes the following steps:
the method comprises the following steps: the application server issues the message to a message push system server cluster;
step two: after the message pushing system server cluster receives the message, firstly, a message analysis module is called to convert the message into a format conforming to a communication protocol;
step three: the message push system server cluster persists the analyzed message to a database so as to support offline users and management of historical sent messages;
step four: after the message is stored in the database, according to the topic subscription condition recorded in the database, querying the subscription user under the message topic;
step five: if the subscribing user is online, turning to step six; if the subscribing user is offline, updating an offline user message record table in the database, after the user logs in, firstly detecting whether a message exists in the offline user message record table by the server, and if so, pushing the message to the user;
step six: copying the message to a queue to be pushed of each online user, and calling a message pushing module to sequentially push the message to a target terminal;
step seven: after receiving the message, the target terminal needs to send a message Acknowledgement (ACK) to the application server, and after receiving the ACK, the application server considers that the message is successfully pushed and deletes the message from the pushing queue; if the pushing fails or the ACK confirmation is not received due to network failure and the like, the message is retransmitted according to a certain rule.
In summary, the message pushing system based on the cloud desktop platform provided by the invention can provide a good message interaction mode for managers and users of the cloud desktop platform, and the message notification function in the existing business system of an enterprise can be integrated by using the message pushing system, so that when the user uses the cloud desktop system, the message is actively pushed to the user in time and effectively, and better user experience is provided.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (3)
1. A message pushing system based on a cloud desktop platform is characterized by comprising an application server, a load balancing server, a message pushing system server cluster, a client and a database; the message pushing system server cluster is connected with the load balancing server, and the load balancing server is in communication connection with the client through an MQTT protocol and is used for actively pushing messages to the client; the message pushing system server cluster is also connected with the application server and used for receiving messages sent by the application server; the message pushing server cluster is in communication connection with the database and is used for calling data stored in the database.
2. The cloud desktop platform-based message pushing system of claim 1, wherein the load balancing server is configured to connect the client to any node in the message pushing server cluster.
3. The message pushing system based on the cloud desktop platform as claimed in claim 1, wherein the layered architecture with low coupling specifically comprises:
the application layer, namely a Web management interface facing a system administrator, comprises a theme management unit, a manual message pushing operation unit, a message management unit, a message statistical unit and a terminal feedback unit;
the business logic layer comprises a connection management unit, a theme management unit, a user subscription management unit, a message management unit and a storage unit;
an access layer: and an entrance for the client to access the system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911084847.1A CN112787906A (en) | 2019-11-08 | 2019-11-08 | Message pushing system based on cloud desktop platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911084847.1A CN112787906A (en) | 2019-11-08 | 2019-11-08 | Message pushing system based on cloud desktop platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112787906A true CN112787906A (en) | 2021-05-11 |
Family
ID=75748107
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911084847.1A Pending CN112787906A (en) | 2019-11-08 | 2019-11-08 | Message pushing system based on cloud desktop platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112787906A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113468430A (en) * | 2021-07-21 | 2021-10-01 | 深圳市亿诺德科技有限公司 | Industrial application-based multi-system unified message transmission and interaction method and device |
| CN115514731A (en) * | 2022-09-22 | 2022-12-23 | 中国农业银行股份有限公司 | Message pushing method, device, medium and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104935674A (en) * | 2015-07-08 | 2015-09-23 | 成都梦工厂网络信息有限公司 | Cloud push system |
| CN106713124A (en) * | 2017-01-24 | 2017-05-24 | 深圳市启仑智能科技有限公司 | Message push method and system based on MQTT and MYSQL |
| CN206413026U (en) * | 2017-01-24 | 2017-08-15 | 深圳市启仑智能科技有限公司 | A kind of message push system based on MQTT and MYSQL |
| CN108509507A (en) * | 2018-02-11 | 2018-09-07 | 北京原点时空信息技术有限公司 | The account management system and its implementation of unified entrance |
-
2019
- 2019-11-08 CN CN201911084847.1A patent/CN112787906A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104935674A (en) * | 2015-07-08 | 2015-09-23 | 成都梦工厂网络信息有限公司 | Cloud push system |
| CN106713124A (en) * | 2017-01-24 | 2017-05-24 | 深圳市启仑智能科技有限公司 | Message push method and system based on MQTT and MYSQL |
| CN206413026U (en) * | 2017-01-24 | 2017-08-15 | 深圳市启仑智能科技有限公司 | A kind of message push system based on MQTT and MYSQL |
| CN108509507A (en) * | 2018-02-11 | 2018-09-07 | 北京原点时空信息技术有限公司 | The account management system and its implementation of unified entrance |
Non-Patent Citations (1)
| Title |
|---|
| 童俊领: "云平台中消息系统的设计与实现", 《中国优秀硕士学位论文全文数据库 (信息科技辑)》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113468430A (en) * | 2021-07-21 | 2021-10-01 | 深圳市亿诺德科技有限公司 | Industrial application-based multi-system unified message transmission and interaction method and device |
| CN115514731A (en) * | 2022-09-22 | 2022-12-23 | 中国农业银行股份有限公司 | Message pushing method, device, medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9615223B2 (en) | Electronic messaging technology | |
| CN101426726B (en) | System and method for optimizing inter-domain event services | |
| US7941495B2 (en) | Management capabilities for real-time messaging networks | |
| US8688854B2 (en) | Messenger notification system and method using synchronization server | |
| US8051057B2 (en) | Processing of network content and services for mobile or fixed devices | |
| US8060562B2 (en) | Real time update notification | |
| EP3734913A1 (en) | Communication method and communication apparatus | |
| US9634966B2 (en) | Integrated two-way communications between database client users and administrators | |
| US20070005711A1 (en) | System and method for building instant messaging applications | |
| US20030061365A1 (en) | Service-to-service communication for network services | |
| US7328247B2 (en) | Self-contained instant messaging appliance | |
| CN103916296B (en) | A kind of communication system for merging LAN | |
| CA2707536A1 (en) | Processing of network content and services for mobile or fixed devices | |
| CN102299810A (en) | Method and system for notifying group change event | |
| CN102484617A (en) | Method and system for reducing the number of presence events within a network | |
| CN112787906A (en) | Message pushing system based on cloud desktop platform | |
| US20030172077A1 (en) | Device-independent notification system | |
| CN101242376A (en) | A method for adding contact in enterprise instant messaging tool | |
| US20020138605A1 (en) | Message tracking system and method | |
| KR100702704B1 (en) | Notification System and Method Using Messenger | |
| CN105245621B (en) | Enterprise message supplying system and information push method based on MQTT | |
| CN113254050A (en) | Micro front-end system | |
| CN116405547A (en) | Message pushing method and device, processor, electronic equipment and storage medium | |
| US20180041460A1 (en) | Aggregation in a Communication System or Service | |
| CN108470042A (en) | A kind of O＆M problem automatic answering 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: 20210511 |