CN109246220B - Message pushing system and method - Google Patents
Message pushing system and method Download PDFInfo
- Publication number
- CN109246220B CN109246220B CN201811094844.1A CN201811094844A CN109246220B CN 109246220 B CN109246220 B CN 109246220B CN 201811094844 A CN201811094844 A CN 201811094844A CN 109246220 B CN109246220 B CN 109246220B
- Authority
- CN
- China
- Prior art keywords
- client
- pushed
- message
- request
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Abstract
The embodiment of the invention discloses a message pushing system and a method, wherein the system comprises: at least one communication terminal, a message server and a client confirmation module; the communication terminal is used for initiating a message pushing request to the message server; the message server is used for sending a client acquisition request to be pushed to the client confirmation module according to the message pushing request; the client confirmation module is used for determining at least one client identifier to be pushed corresponding to the client acquisition request to be pushed according to the client acquisition request to be pushed and sending the at least one client identifier to be pushed to the message server; the message server is further used for receiving the client identification to be pushed and pushing the message to be pushed to the client to be pushed corresponding to the client identification to be pushed, so that the unification of message pushing interfaces is realized when the client types are different, the pushing of messages of different types is realized on the basis of starting one thread, the power consumption of the communication terminal is saved while the resources are saved.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a message pushing system and a message pushing method.
Background
With the continuous development of mobile terminal devices, the application of mobile terminals in the medical field is also more and more extensive. Affected by the working environment of the hospital, the medical care personnel are inconvenient to communicate by the modes of mobile phones and the like. At present, multimedia communication software oriented to common mobile terminals is developed rapidly, for example, medical staff can communicate through the mobile terminals.
However, most of the existing message pushing technologies are developed on a specific platform and aiming at a specific scene and a specific client, and cannot meet the requirements in a specific environment of a hospital. In addition, in the existing message pushing technology, different calls and processes need to be made for different message pushing modes (such as point-to-point and publish/subscribe), and the pushing and publishing of messages are performed through different threads. And when the systems operated by the client are different (such as android, IOS and other systems), the corresponding message pushing modes are also different, so that application developers need to learn and develop independently aiming at different mobile phone platforms, and further the development efficiency is low. In addition, in the existing message pushing technology, different sending or monitoring threads are required to be started for sending different messages and subscribing different message topics, and different connections are established, and the threads and the connections not only increase the consumption of resources, but also increase the consumption of electric quantity.
Disclosure of Invention
The embodiment of the invention provides a message pushing system and a message pushing method, which aim to realize the unification of message pushing interfaces aiming at different clients, realize the pushing of messages of different types on the basis of starting a thread, save resources and save the power consumption of a communication terminal.
In a first aspect, an embodiment of the present invention provides a message pushing system, including: at least one communication terminal, a message server and a client confirmation module;
the communication terminal is used for initiating a message pushing request containing a message to be pushed to the message server;
the message server is used for sending a client acquisition request to be pushed to the client confirmation module according to the message pushing request;
the client confirmation module is used for determining at least one client identifier to be pushed corresponding to the client acquisition request to be pushed according to the client acquisition request to be pushed sent by the message server and sending the at least one client identifier to be pushed to the message server;
and the message server is also used for receiving the client identifier to be pushed and pushing the message to be pushed to the client to be pushed corresponding to the client identifier to be pushed.
In a second aspect, an embodiment of the present invention further provides a message pushing method, which is applied to the message pushing system provided in any embodiment of the present invention, and includes:
the communication terminal initiates a message pushing request containing the message to be pushed to the message server;
the message server sends a client acquisition request to be pushed to the client confirmation module according to the message pushing request;
the client confirmation module determines at least one client identifier to be pushed corresponding to the client acquisition request to be pushed according to the client acquisition request to be pushed sent by the message server, and sends the client identifier to be pushed to the message server;
and the message server receives the identification of the client to be pushed and pushes the message to be pushed to the client to be pushed corresponding to the identification of the client to be pushed.
The message pushing system provided by the embodiment of the invention comprises: at least one communication terminal, a message server and a client confirmation module; the communication terminal is used for initiating a message pushing request containing the message to be pushed to the message server; the message server is used for sending a client acquisition request to be pushed to the client confirmation module according to the message pushing request; the client confirmation module is used for determining at least one client identifier to be pushed corresponding to the client acquisition request to be pushed according to the client acquisition request to be pushed sent by the message server and sending the at least one client identifier to be pushed to the message server; the message server is further used for receiving the client identification to be pushed, pushing the message to be pushed to the client to be pushed corresponding to the client identification to be pushed, acquiring the client identification to be pushed from the message server to the client confirmation module, realizing unification of message pushing interfaces when the client types are different, realizing pushing of messages of different types on the basis of starting one thread, saving resources and saving power consumption of the communication terminal.
Drawings
Fig. 1 is a schematic structural diagram of a message pushing system according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a message pushing system according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a message pushing system according to a third embodiment of the present invention;
fig. 4a is a schematic structural diagram of a message pushing system according to a fourth embodiment of the present invention;
fig. 4b is a schematic diagram illustrating a relationship between modules in the message pushing system according to the fourth embodiment of the present invention;
fig. 4c is a schematic diagram illustrating a relationship between classes and modules in the message pushing system according to the fourth embodiment of the present invention;
fig. 5a is a flowchart of a message pushing method according to a fifth embodiment of the present invention;
fig. 5b is a schematic flowchart of client registration in the message pushing method according to the fifth embodiment of the present invention;
fig. 5c is a timing diagram of message pushing in the message pushing method according to the fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a schematic structural diagram of a message pushing system according to an embodiment of the present invention, where the message pushing system according to the embodiment can be used for pushing messages among medical staff in a hospital. As shown in fig. 1, the message push system includes: at least one communication terminal 110, a message server 120 and a client confirmation module 130.
The communication terminal 110 is configured to initiate a message pushing request including a message to be pushed to the message server 120;
the message server 120 is configured to send a client acquisition request to be pushed to the client confirmation module 130 according to the message pushing request;
the client confirmation module 130 is configured to determine, according to the to-be-pushed client acquisition request sent by the message server 120, at least one to-be-pushed client identifier corresponding to the to-be-pushed client acquisition request, and send the at least one to-be-pushed client identifier to the message server 120;
the message server 120 is further configured to receive the identifier of the client to be pushed, and push the message to be pushed to the client to be pushed corresponding to the identifier of the client to be pushed.
Optionally, in order to enable medical care personnel in a hospital to contact each other in time, each medical care personnel can wear a mobile terminal, and after logging in by a user, the medical care personnel can contact other medical care personnel at any time, so that the pushing of messages among the medical care personnel and the publishing of the messages are realized.
In this embodiment, when the medical staff pushes a message through the communication terminal 110, after the target to be pushed is selected, the message to be pushed is input in the information input area corresponding to the target to be pushed, and the "send" button is clicked to trigger the message pushing operation. After detecting a message pushing operation triggered by a medical worker, the communication terminal 110 forms a message pushing request according to an acquired message to be pushed and related information, and sends the message pushing request to the message server 120, the message server 120 generates a client acquiring request to be pushed according to the received message pushing request, and sends the generated client acquiring request to be pushed to the client confirmation module 130, the client confirmation module 130 determines a client identifier to be pushed corresponding to the client acquiring request to be pushed according to the received client acquiring request to be pushed, and feeds the determined client identifier to be pushed back to the message server 120, and the message server 120 pushes the message to be pushed to the client to be pushed according to the received client identifier to be pushed, thereby completing the pushing of the message.
Optionally, the message pushing system provided in this embodiment may implement pushing of messages to be pushed of different message pushing types. Optionally, the message pushing system provided in this embodiment may implement not only the pushing of the point-to-point message, but also the pushing of the publish-subscribe message. The push of the point-to-point message refers to pushing a message to be pushed from one communication terminal to another communication terminal, and the push of the publish-subscribe message refers to pushing the message to be pushed from one communication terminal to a plurality of communication terminals related to the message to be pushed.
Optionally, when the medical care personnel needs to push the message point to point through the communication terminal, the user to be pushed may be selected, the message to be pushed is input in the information input area corresponding to the user to be pushed, and the "send" button is clicked to trigger the point to point pushing of the message. When medical care personnel need to realize the publish-subscribe push of the message through the communication terminal, the publish-subscribe theme can be selected, the message to be pushed is input in the information counting area corresponding to the publish-subscribe theme, and the publish-subscribe push of the message is triggered by clicking a 'send' button.
In the embodiment, whether the message push type is the push of a point-to-point message or the push of a publish-subscribe message, the message server acquires the identification of the client to be pushed to the client confirmation module, so that the push modes of different message push types are unified, and the push mode can be realized by only establishing a thread between the communication terminal and the message server, thereby greatly saving the power consumption of the communication terminal while greatly saving resources; and when the user needs to send the message, only the destination of the message needs to be specified, the user does not need to care whether the destination is the client or the topic of the publication subscription, and the user does not need to perform special processing aiming at the two modes, so that the operation of the user is simplified, and the user experience is improved.
Optionally, in this embodiment, the message server calls the client confirmation module to further implement unification of message push interfaces for different client systems, a unified message push related interface is provided externally, differences in push messages between different clients are shielded, multiple types of clients (such as Android, IOS, PC, window phone, and the like) can be supported, and the message server can be conveniently integrated with a third-party message server (such as activeMQ), so that diverse requirements of message push are met, and message push across platforms and clients (message receiving ends) with high efficiency is implemented.
The message pushing system provided by the embodiment of the invention comprises: at least one communication terminal, a message server and a client confirmation module; the communication terminal is used for initiating a message pushing request containing the message to be pushed to the message server; the message server is used for sending a client acquisition request to be pushed to the client confirmation module according to the message pushing request; the client confirmation module is used for determining at least one client identifier to be pushed corresponding to the client acquisition request to be pushed according to the client acquisition request to be pushed sent by the message server and sending the at least one client identifier to be pushed to the message server; the message server is further used for receiving the client identification to be pushed, pushing the message to be pushed to the client to be pushed corresponding to the client identification to be pushed, acquiring the client identification to be pushed from the message server to the client confirmation module, realizing unification of message pushing interfaces when the client types are different, realizing pushing of messages of different types on the basis of starting one thread, saving resources and saving power consumption of the communication terminal.
On the basis of the above scheme, the message server is configured to:
and judging the pushing type of the message pushing request, and sending the client acquisition request to be pushed to a corresponding client determining module according to the pushing type.
In this embodiment, for different message push types, a client acquisition request to be pushed is generated by the message server, and the client identification to be pushed is acquired from the client confirmation module by the client acquisition request to be pushed. Optionally, a corresponding relationship between the type of the message to be pushed and the client determining module may be set, and when the types of the message to be pushed are different, the client obtaining request to be pushed is sent to the client determining module corresponding to the type of the message to be pushed. Different types of the messages to be pushed correspond to different client determining modules, so that the calling logic of the message pushing system is clearer and the management is more convenient.
Example two
Fig. 2 is a schematic structural diagram of a message pushing system according to a second embodiment of the present invention, which is based on the second embodiment and embodies a message server and a client determining module. As shown in fig. 2, the client confirmation module 130 includes a client registration unit 131, and the message server 120 is configured to:
if the push type is point-to-point push, a to-be-pushed client acquisition request is generated according to the message push request, and the to-be-pushed client acquisition request is sent to the client registration unit 131.
In this embodiment, after receiving a message push request initiated by the communication terminal 110, the message server 120 determines a message push type of the message to be pushed according to the message push request, and if the message push type is point-to-point push, the message server 120 generates a client to be pushed acquisition request according to the message push request, sends the client to be pushed acquisition request to the client registration unit 131, receives a client to be pushed identifier fed back by the client registration unit 131, and performs point-to-point push on the message to be pushed according to the received client to be pushed identifier.
Optionally, the message pushing request initiated by the communication terminal 110 includes a message to be pushed and a target identifier to be pushed (i.e. a user identifier to be pushed), and the message server 120 may determine a pushing type of the message to be pushed according to the target identifier to be pushed. Optionally, the preset field of the target identifier to be pushed may be matched with the preset identifier, and the message type corresponding to the preset identifier matched with the target identifier to be pushed is determined as the message type of the message to be pushed. For example, the first digit of the target identifier to be pushed may be matched with a preset identifier, and the message type of the message to be pushed may be determined according to the matching result.
For example, if the preset identifier for point-to-point message pushing is set to be 1, when the first digit of the target identifier to be pushed is 1, it is determined that the message type of the message to be pushed is point-to-point message pushing, and a client acquisition request to be pushed, which is generated according to the message pushing request, is sent to the client registration unit.
On the basis of the above scheme, the client registration unit 131 is configured to:
according to the client-side acquisition request to be pushed sent by the message server 120, the client-side identification to be pushed corresponding to the user identification to be pushed in the client-side acquisition request to be pushed is determined, and the client-side identification to be pushed is sent to the message server 120.
Optionally, the to-be-pushed client obtaining request sent by the message server 120 includes a to-be-pushed user identifier, and the client registering unit 131 determines the to-be-pushed client identifier according to the to-be-pushed user identifier included in the to-be-pushed client obtaining request, and sends the determined to-be-pushed client identifier to the message server 120.
Illustratively, if the user identifier to be pushed contained in the client acquisition request to be pushed sent by the message server is "11", the client registration unit determines, according to the stored association relationship between the user identifier and the client identifier, the client identifier "31" stored in correspondence with the user identifier "11", and sends the client identifier "31" as the client identifier to be pushed to the message server.
On the basis of the above scheme, the client registration unit 131 is further configured to:
receiving a registration request of a user to be registered, acquiring a user identifier and a client identifier contained in the registration request, and establishing an association relation between the client identifier and the user identifier.
In this embodiment, the client registration unit may further respond to a registration request of a new user, and store the relevant information of the user to be registered. Optionally, when a new user needs to be registered, basic user information may be input on a user registration interface of the communication terminal, a "registration" button is clicked to trigger a registration operation of the new user, when the communication terminal detects the registration operation triggered by the user, a user registration request is generated according to the basic information input by the user and in combination with identification information of the communication terminal, the generated user registration request is sent to the message server, the message server sends the user registration request to the client registration unit, the client registration unit obtains a user identification and a client identification in the user registration request, the user identification and the client identification are correspondingly stored, and an association relationship between the user identification and the client identification is established.
According to the technical scheme of the embodiment of the invention, the message server and the client determining module are embodied on the basis of the embodiment, when the message server judges that the pushing type of the message to be pushed is point-to-point pushing, the client acquiring request to be pushed is generated according to the message pushing request and is sent to the client registering unit, the client identifier to be pushed fed back by the client registering unit is acquired, the point-to-point pushing of the message to be pushed is completed according to the acquired client identifier to be pushed, the unification of message pushing interfaces is realized when the types of the message to be pushed are different, and the determination of the client to be pushed is more accurate.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a message pushing system according to a third embodiment of the present invention, which is based on the foregoing embodiment and embodies a message server and a client determining module. As shown in fig. 3, the client confirmation module 130 includes a message subscription unit 132, and the message server 120 is configured to:
if the push type is publish-subscribe, a to-be-pushed client acquisition request is generated according to the message push request, and the to-be-pushed client acquisition request is sent to the message subscribing unit 132.
In this embodiment, after receiving the message push request initiated by the communication terminal 110, the message server 120 determines the message push type of the message to be pushed according to the message push request, and if the message push type is publish-subscribe message push, the message server 120 generates a client acquisition request to be pushed according to the message push request, sends the client acquisition request to be pushed to the message subscription unit 132, receives at least one client identifier to be pushed fed back by the message subscription unit 132, and performs publish-subscribe push on the message to be pushed according to the received at least one client identifier to be pushed.
Optionally, the message pushing request initiated by the communication terminal 110 includes a message to be pushed and a target identifier to be pushed (i.e. a user identifier to be pushed), and the message server 120 may determine a pushing type of the message to be pushed according to the target identifier to be pushed. Optionally, the preset field of the target identifier to be pushed may be matched with the preset identifier, and the message type corresponding to the preset identifier matched with the target identifier to be pushed is determined as the message type of the message to be pushed. For example, the first digit of the target identifier to be pushed may be matched with a preset identifier, and the message type of the message to be pushed may be determined according to the matching result.
Illustratively, if the preset identifier for pushing the publish-subscribe message is set to be 2, when the first digit of the target identifier to be pushed is 2, it is determined that the message type of the message to be pushed is publish-subscribe message pushing, and a client acquisition request to be pushed, which is generated according to the message pushing request, is sent to the message subscription unit.
On the basis of the above scheme, the message subscribing unit 132 is configured to:
according to the to-be-pushed client acquisition request sent by the message server 120, at least one to-be-pushed client identifier corresponding to the to-be-pushed client acquisition request is determined, and the at least one to-be-pushed client identifier is sent to the message server 120.
In this embodiment, the to-be-pushed client acquisition request sent by the message server 120 includes a to-be-pushed target identifier, and the message subscription unit 132 determines, according to the to-be-pushed target identifier, at least one to-be-pushed client identifier corresponding to the to-be-pushed client acquisition request, and sends the determined to-be-pushed client identifier to the message server 120.
On the basis of the above scheme, the message subscribing unit 132 is configured to:
according to the subject identifier included in the client-side acquisition request to be pushed, at least one client-side identifier to be pushed corresponding to the subject identifier is determined, and the at least one client-side identifier to be pushed is sent to the message server 120.
Optionally, the message subscribing unit 132 stores relevant subscription information of each topic, such as a user identifier and a client identifier subscribing to each topic. Optionally, when the push type of the message to be pushed is push of a publish-subscribe message, the target identifier to be pushed may be a topic identifier of a publish-subscribe. The message server 120 sends a to-be-pushed client acquisition request carrying a topic identifier, and the message subscription unit 132 determines at least one to-be-pushed client identifier corresponding to the topic identifier according to the topic identifier contained in the to-be-pushed client acquisition request, and sends the determined to-be-pushed client identifier to the message server 120.
Illustratively, if the topic identifier included in the to-be-pushed client acquisition request sent by the message server is "21", the message subscription unit determines that the client identifiers stored corresponding to the topic identifier "21" are "32" and "33" according to the association relationship between the stored topic identifier and the client identifier, and sends the client identifiers 32 "and" 33 "to the message server as the to-be-pushed client identifiers.
On the basis of the above scheme, the message subscribing unit 132 is further configured to:
receiving a subscription request of a user to be subscribed, acquiring a topic identifier and a client identifier contained in the subscription request, and establishing an association relationship between the topic identifier and the client identifier.
In this embodiment, the message subscribing unit may further respond to a subscription request of the user, and store the subscribed user information of each topic. Optionally, when a user needs to subscribe to a certain topic, a "subscribe" button may be clicked on a subscription interface of the topic on the communication terminal to trigger a subscription operation, when the communication terminal detects the subscription operation triggered by the user, a user subscription request is generated by combining identification information of the communication terminal with a topic identifier subscribed by the user, the generated user subscription request is sent to the message server, the message server sends the user subscription request to the message subscription unit, the message subscription unit obtains the topic identifier and a client identifier in the user subscription request, stores the topic identifier and the client identifier correspondingly, and establishes an association relationship between the topic identifier and the client identifier.
Optionally, the message subscription request may further include a user identifier of the subscribing user, and when the message subscription request includes the user identifier, the message subscription unit may correspondingly store the user identifier, the topic identifier, and the client identifier, and establish an association relationship between the user identifier, the topic identifier, and the client identifier.
According to the technical scheme of the embodiment of the invention, the message server and the client determining module are embodied on the basis of the embodiment, when the message server judges that the push type of the message to be pushed is the push of the publish-subscribe message, the client acquiring request to be pushed is generated according to the message push request, the client acquiring request to be pushed is sent to the message subscribing unit, the client identifier to be pushed fed back by the message subscribing unit is acquired, the publish-subscribe push of the message to be pushed is completed according to the acquired client identifier to be pushed, the unification of message push interfaces is realized when the types of the message to be pushed are different, and the determination of the client to be pushed is more accurate.
Example four
Fig. 4a is a schematic structural diagram of a message pushing system according to a fourth embodiment of the present invention. The present embodiment provides a preferred implementation manner based on the above embodiments.
As shown in fig. 4a, the client accessible by the message push system may be an Android client, an IOS client, a PC client, or the like. The message pushing system comprises: the system comprises an interface service module, a client registration module, a message subscription module, a message receiving and sending module and a configuration management module. Fig. 4b is a schematic relationship diagram of modules in the message pushing system according to the fourth embodiment of the present invention. As shown in fig. 4b, the interface service module encapsulates the functions provided by the client registration module, the message subscription module, and the message receiving and sending module, and provides a uniform interface for calling. The message receiving and sending module acquires registered clients from the client registration module, and acquires a list of clients subscribed to a certain theme from the message subscription module so as to push messages. The message receiving and sending module uses part of the configuration data in the configuration management module when receiving and sending messages.
Fig. 4c is a schematic diagram illustrating a relationship between classes and modules in the message pushing system according to the fourth embodiment of the present invention. As shown in FIG. 4c, the relationship between classes and modules is as follows: the interface service module is divided into the following classes: MessageService, MessageServiceImpl (default implementation of MessageService); the client registration module is divided into the following classes: a Destinationregister; the message subscription module is divided into the following classes: subscriber; the message receiving and sending module is divided into the following classes: MessageManager, MessagePusher, Andriod Pusher, IOSPusher, PCPusher; the configuration management module is divided into the following classes: configuration; the Server is a Server interface, the MessageServer is a message Server, and the message Server can be started or closed.
As can be seen from fig. 4c, the MessageServer starts the message server according to the relevant Configuration in the Configuration; the MessageService is injected into the MessageServer and is exposed to external calling; the MessageManager pushes the message by means of a MessagePusher; the message pushing system provided by the embodiment of the invention can conveniently support the access of a new client by providing different implementations of the MessagePusher; in addition, as long as different implementations are provided for the MessageManager, the third-party message server can be accessed, for example, an ActiveMQ implementation class ActiveMQMessageManager is provided, so that the ActiveMQ of the third-party message server can be conveniently accessed.
EXAMPLE five
Fig. 5a is a flowchart of a message pushing method according to a fifth embodiment of the present invention, and this embodiment is applicable to a situation when the message pushing system according to the foregoing embodiment of the present invention is used for message pushing. As shown in fig. 5a, the method specifically includes:
s510, the communication terminal sends a message pushing request containing the message to be pushed to the message server.
S520, the message server sends a client acquisition request to be pushed to the client confirmation module according to the message pushing request.
S530, the client confirmation module determines at least one client identifier to be pushed corresponding to the client acquisition request to be pushed according to the client acquisition request to be pushed sent by the message server, and sends the client identifier to be pushed to the message server.
And S540, the message server receives the identification of the client to be pushed and pushes the message to be pushed to the client to be pushed corresponding to the identification of the client to be pushed.
In this embodiment, a message push request including a message to be pushed is initiated to a message server through a communication terminal, the message server determines, according to the message push request, at least one to-be-pushed client identifier corresponding to the to-be-pushed client acquisition request according to the to-be-pushed client acquisition request by a message push request confirmation module, and sends the to-be-pushed client identifier to the message server, and the message server receives the to-be-pushed client identifier and pushes the to-be-pushed message to a to-be-pushed client corresponding to the to-be-pushed client identifier.
Fig. 5b is a schematic flowchart of client registration in the message pushing method according to the fifth embodiment of the present invention. As shown in fig. 5b, after the message server is started, a client (which may be an Android, IOS, PC, or other type client) is started, the user triggers a registration request, the client initiates the registration request to the message server, and after the message server receives the registration request initiated by the client, the communication connection between the client and the message server is established. Alternatively, the message server may be started by calling messageserver.
Fig. 5c is a timing diagram of message pushing in the message pushing method according to the fifth embodiment of the present invention. As shown in fig. 5c, the client calls a message push method (messageservice. send ()) of the interface service, and sends the message to the specified destination. Where the specified destination may be another client or some topic. When the designated destination is another client, the MessageService acquires a registered client (destination register.get ()) corresponding to the designated destination from the client registration module; if the registered client exists, sending a message (MessageManager. send ()) to the client, wherein the MessageManager pushes the message to a different client by means of a message pusher (MessagePusher); when the specified destination is a certain topic, the message service acquires the clients subscribed to the topic (topic) from the message subscription module, and if the subscribed clients exist, the message is sent to each subscribed client in a loop (message manager.
Optionally, for more detailed content of using the message pushing system to push the message, reference may be made to the above-mentioned embodiment, which is not described herein again.
The embodiment of the invention uses the communication server to realize the user verification and the feedback of the associable user in the hospital business system through the hospital interface server, realizes the timely communication among medical personnel in the hospital on the basis of not needing the association among the users by all the users, and calls the hospital business system through the hospital interface server, realizes the butt joint of the communication server and the existing business system of the hospital, so that the user data is not needed to be maintained additionally when the system is used, and the use process of the user is simplified.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (7)
1. A message push system, comprising: at least one communication terminal, a message server and a client confirmation module;
the communication terminal is used for initiating a message pushing request containing a message to be pushed to the message server;
the message server is configured to send a client acquisition request to be pushed to the client confirmation module according to the message pushing request, and includes:
the message server is used for judging the pushing type of the message pushing request and sending the client acquisition request to be pushed to a corresponding client determining module according to the pushing type;
wherein the client confirmation module comprises a client registration unit, and the message server is configured to:
if the push type is point-to-point push, generating a client acquisition request to be pushed according to the message push request, and sending the client acquisition request to be pushed to the client registration unit;
the client confirmation module comprises a message subscription unit, and the message server is used for:
if the push type is a publish-subscribe type, generating a client-side acquisition request to be pushed according to the message push request, and sending the client-side acquisition request to be pushed to the message subscription unit;
the client confirmation module is used for determining at least one client identifier to be pushed corresponding to the client acquisition request to be pushed according to the client acquisition request to be pushed sent by the message server and sending the at least one client identifier to be pushed to the message server;
and the message server is also used for receiving the client identifier to be pushed and pushing the message to be pushed to the client to be pushed corresponding to the client identifier to be pushed.
2. The system of claim 1, wherein the client registration unit is configured to:
and determining a client identifier to be pushed corresponding to the user identifier to be pushed in the client obtaining request to be pushed according to the client obtaining request to be pushed sent by the message server, and sending the client identifier to be pushed to the message server.
3. The system of claim 1, wherein the client registration unit is further configured to:
receiving a registration request of a user to be registered, acquiring a user identifier and a client identifier contained in the registration request, and establishing an association relation between the client identifier and the user identifier.
4. The system of claim 1, wherein the message subscribing unit is configured to:
and determining at least one client identifier to be pushed corresponding to the client obtaining request to be pushed according to the client obtaining request to be pushed sent by the message server, and sending the at least one client identifier to be pushed to the message server.
5. The system of claim 4, wherein the message subscribing unit is configured to:
and determining at least one client identifier to be pushed corresponding to the theme identifier according to the theme identifier contained in the client to be pushed acquisition request, and sending the at least one client identifier to be pushed to the message server.
6. The system of claim 1, wherein the message subscribing unit is further configured to:
receiving a subscription request of a user to be subscribed, acquiring a topic identifier and a client identifier contained in the subscription request, and establishing an association relationship between the topic identifier and the client identifier.
7. A message pushing method applied to the message pushing system according to claim 1, comprising:
the communication terminal initiates a message pushing request containing the message to be pushed to the message server;
the message server sends a client acquisition request to be pushed to the client confirmation module according to the message pushing request, and the method comprises the following steps:
the message server judges the pushing type of the message pushing request and sends the client side acquiring request to be pushed according to the pushing type; wherein the content of the first and second substances,
if the push type is point-to-point push, generating a client acquisition request to be pushed according to the message push request, and sending the client acquisition request to be pushed to the client registration unit;
if the push type is a publish-subscribe type, generating a client-side acquisition request to be pushed according to the message push request, and sending the client-side acquisition request to be pushed to the message subscription unit;
the client confirmation module comprises the client registration unit and the message subscription unit;
the client confirmation module determines at least one client identifier to be pushed corresponding to the client acquisition request to be pushed according to the client acquisition request to be pushed sent by the message server, and sends the client identifier to be pushed to the message server;
and the message server receives the identification of the client to be pushed and pushes the message to be pushed to the client to be pushed corresponding to the identification of the client to be pushed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811094844.1A CN109246220B (en) | 2018-09-19 | 2018-09-19 | Message pushing system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811094844.1A CN109246220B (en) | 2018-09-19 | 2018-09-19 | Message pushing system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109246220A CN109246220A (en) | 2019-01-18 |
| CN109246220B true CN109246220B (en) | 2021-08-17 |
Family
ID=65059219
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811094844.1A Active CN109246220B (en) | 2018-09-19 | 2018-09-19 | Message pushing system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109246220B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109889613B (en) * | 2019-04-24 | 2022-03-18 | 广州欢聊网络科技有限公司 | Message pushing method and device and mobile terminal |
| CN112087475B (en) * | 2019-06-13 | 2023-01-24 | 北京东土科技股份有限公司 | Message pushing method and device for cloud platform component application and message server |
| CN111225044B (en) * | 2019-12-31 | 2022-09-23 | 北京奇才天下科技有限公司 | Client message pushing method, device and system |
| CN111464598A (en) * | 2020-03-19 | 2020-07-28 | 中国人民财产保险股份有限公司 | Data pushing method and device |
| CN111555963B (en) * | 2020-04-30 | 2022-08-16 | 北京思特奇信息技术股份有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN111917843A (en) * | 2020-07-16 | 2020-11-10 | 远光软件股份有限公司 | Message pushing method, computer equipment and storage medium |
| CN112287216B (en) * | 2020-10-23 | 2023-02-17 | 微医云(杭州)控股有限公司 | Information pushing method and device, server and storage medium |
| CN114531481A (en) * | 2020-11-03 | 2022-05-24 | 湖南微步信息科技有限责任公司 | Message pushing method and system |
| CN113067853A (en) * | 2021-03-12 | 2021-07-02 | 北京金山云网络技术有限公司 | Data pushing method and device, electronic equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102624912A (en) * | 2012-03-20 | 2012-08-01 | 无锡德思普科技有限公司 | Method for point-to-point information transmission of intelligent terminals |
| CN103095732A (en) * | 2013-03-01 | 2013-05-08 | 畅捷通信息技术股份有限公司 | Information push system and information push method |
| CN103605791A (en) * | 2013-12-04 | 2014-02-26 | 深圳中兴网信科技有限公司 | Information pushing system and information pushing method |
| CN103840950A (en) * | 2014-02-27 | 2014-06-04 | 广东亿迅科技有限公司 | Information pushing method and system |
| CN103905471A (en) * | 2012-12-25 | 2014-07-02 | 腾讯科技（深圳）有限公司 | Social network information push method, server and social network |
| CN105099882A (en) * | 2015-07-09 | 2015-11-25 | 杭州电子科技大学 | MQTT-based cloud pushing method and system |
| CN106060762A (en) * | 2016-05-24 | 2016-10-26 | 中国联合网络通信集团有限公司 | Information pushing method, information pushing device and information pushing system |
| CN106209940A (en) * | 2015-05-05 | 2016-12-07 | 阿里巴巴集团控股有限公司 | Information-pushing method and information push-delivery apparatus |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20150099236A (en) * | 2014-02-21 | 2015-08-31 | 삼성전자주식회사 | Apparatus and method for providing push service based on location |
| US20160014057A1 (en) * | 2014-07-08 | 2016-01-14 | Samsung Electronics Co., Ltd. | Method and system for providing dynamically customized web push messages in a wireless network |
-
2018
- 2018-09-19 CN CN201811094844.1A patent/CN109246220B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102624912A (en) * | 2012-03-20 | 2012-08-01 | 无锡德思普科技有限公司 | Method for point-to-point information transmission of intelligent terminals |
| CN103905471A (en) * | 2012-12-25 | 2014-07-02 | 腾讯科技（深圳）有限公司 | Social network information push method, server and social network |
| CN103095732A (en) * | 2013-03-01 | 2013-05-08 | 畅捷通信息技术股份有限公司 | Information push system and information push method |
| CN103605791A (en) * | 2013-12-04 | 2014-02-26 | 深圳中兴网信科技有限公司 | Information pushing system and information pushing method |
| CN103840950A (en) * | 2014-02-27 | 2014-06-04 | 广东亿迅科技有限公司 | Information pushing method and system |
| CN106209940A (en) * | 2015-05-05 | 2016-12-07 | 阿里巴巴集团控股有限公司 | Information-pushing method and information push-delivery apparatus |
| CN105099882A (en) * | 2015-07-09 | 2015-11-25 | 杭州电子科技大学 | MQTT-based cloud pushing method and system |
| CN106060762A (en) * | 2016-05-24 | 2016-10-26 | 中国联合网络通信集团有限公司 | Information pushing method, information pushing device and information pushing system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109246220A (en) | 2019-01-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109246220B (en) | Message pushing system and method | |
| US11711434B2 (en) | Information transmission method and device | |
| CN103069755B (en) | Use the method and system that the instant message of multiple client instance transmits | |
| US20170048590A1 (en) | Method, device, and system for switching at a mobile terminal of a smart television and acquiring information at a television terminal | |
| KR102472916B1 (en) | System and method for providing conversational contents | |
| US20140323166A1 (en) | Method, device and system for voice communication | |
| CN109391476B (en) | Network communication method, device and system | |
| CN109918268B (en) | System compatible method, apparatus, device and computer readable storage medium | |
| CN113162848B (en) | Method, device, gateway and medium for realizing block chain gateway | |
| WO2016010921A1 (en) | Creating a user group | |
| CN110753129A (en) | Message transmission method, system, device, equipment and computer readable storage medium | |
| CN112689202B (en) | Live broadcast room message processing method and device, server and storage medium | |
| CN106550030B (en) | A kind of data sharing method, apparatus and system | |
| EP2974159B1 (en) | Method, device and system for voice communication | |
| CN109446204B (en) | Data storage method and device for instant messaging, electronic equipment and medium | |
| CN112346751B (en) | Application program installation method and device, electronic equipment and storage medium | |
| CN109275042A (en) | A kind of distribution method, device, terminal and the storage medium of barrage message | |
| KR20110131995A (en) | Server and method for providing device management service and device to be provided the service | |
| CN113641320B (en) | Method and device for sharing screen of Linux compatible with Android | |
| CN111201804B (en) | Method, apparatus and computer readable storage medium for enabling data continuity services | |
| CN110619698B (en) | Information prompting method and device based on Internet of things operating system | |
| CN112733051A (en) | Websocket-based information push management system and method | |
| CN105898596B (en) | Direct broadcasting room display control method and device | |
| CN109040331B (en) | Electronic business card processing method and device, computing equipment and storage medium | |
| CN105681262A (en) | Interaction message allocating 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |