CN109246220A - A kind of message push system and method - Google Patents
A kind of message push system and method Download PDFInfo
- Publication number
- CN109246220A CN109246220A CN201811094844.1A CN201811094844A CN109246220A CN 109246220 A CN109246220 A CN 109246220A CN 201811094844 A CN201811094844 A CN 201811094844A CN 109246220 A CN109246220 A CN 109246220A
- Authority
- CN
- China
- Prior art keywords
- client
- message
- pushed
- push
- identification
- 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.)
- Granted
Links
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention discloses a kind of message push system and method, the system comprises: at least one communicating terminal, message server and client confirmation module；Communicating terminal, for initiating message push request to message server；Message server, for sending client acquisition request to be pushed to client confirmation module according to message push request；At least one client identification to be pushed at least one client identification to be pushed according to corresponding to the determining client acquisition request to be pushed of client acquisition request to be pushed, and is sent to message server by client confirmation module；Message server, it is also used to receive client identification to be pushed, and PUSH message is waited for the corresponding client push to be pushed of client identification to be pushed, the unification of message push interface when realizing client type difference, on the basis of opening a thread, the push for realizing different types of message saves the power consumption of communicating terminal while saving resource.
Description
Technical field
The present embodiments relate to communication technique field more particularly to a kind of message push system and methods.
Background technique
With the continuous development of mobile terminal device, mobile terminal is also more and more extensive in the application of medical field.It is cured
The influence of institute's working environment, medical staff's inconvenience are linked up by modes such as mobile phones.Currently, towards common mobile whole
The multi-media communication software development at end is rapid, and e.g., each medical staff can be communicated by mobile terminal.
But in existing message push technology, most of is all on specific platform, for special scenes, specific visitor
The exploitation of family end, the needs being unable to satisfy in hospital's specific environment.Also, in existing message push technology, need for not
Different calling and processing are done in same message push mode (such as point-to-point and publish/subscribe), are disappeared by different threads
The push and publication of breath.And when system different (such as Androids, IOS system) that client is run, corresponding message push
Mode is also different, must individually learn for different cell phone platforms so as to cause application developer, develop, and then cause out
Send out inefficiency.In addition, in existing message push technology, different message is sent, different message subject needs is subscribed to and opens
Different transmission or listening thread are opened, different connections is established, these threads and connection not only increase resource and must consume, and also increase
The consumption of electricity is added.
Summary of the invention
The embodiment of the invention provides a kind of message push system and methods, are disappeared with realizing for different client realizations
The unification of breath push interface, and on the basis of opening a thread, it realizes the push of different types of message, saves resource
While save communicating terminal power consumption.
In a first aspect, the embodiment of the invention provides a kind of message push systems, comprising: at least one communicating terminal disappears
Cease server and client confirmation module；
The communicating terminal, for initiating to include the message push request to PUSH message to message server；
The message server, for being sent to the client confirmation module wait push according to message push request
Client acquisition request；
The client confirmation module, the client acquisition request to be pushed for being sent according to the message server are true
At least one client identification to be pushed corresponding to the client acquisition request to be pushed, and by it is described at least one wait for
Push client identification is sent to the message server；
The message server, is also used to receive the client identification to be pushed, and to the client mark to be pushed
Know corresponding wait push described in client push to PUSH message.
Second aspect is applied to implement as the present invention is any the embodiment of the invention also provides a kind of information push method
Message push system provided by example, comprising:
Communicating terminal initiates to include the message push request to PUSH message to message server；
The message server sends client to be pushed to the client confirmation module according to message push request
Hold acquisition request；
The client confirmation module determines institute according to the client acquisition request to be pushed that the message server is sent
State at least one client identification to be pushed corresponding to client acquisition request to be pushed, and by the client mark to be pushed
Knowledge is sent to the message server；
The message server receives the client identification to be pushed, and corresponding to the client identification to be pushed
Wait push described in client push to PUSH message.
Message push system provided by the embodiment of the present invention, comprising: at least one communicating terminal, message server and visitor
Family end confirmation module；Communicating terminal, for initiating to include the message push request to PUSH message to message server；Message
Server, for sending client acquisition request to be pushed to client confirmation module according to message push request；Client is true
Recognize module, the client acquisition request to be pushed for sending according to message server determines client acquisition request institute to be pushed
At least one corresponding client identification to be pushed, and at least one client identification to be pushed is sent to message server；
Message server, is also used to receive client identification to be pushed, and to the corresponding client to be pushed of client identification to be pushed
Push obtains client identification to be pushed to client confirmation module by message server, realizes client to PUSH message
The unification of message push interface when holding type difference, and on the basis of opening a thread, realize different types of disappear
The push of breath saves the power consumption of communicating terminal while saving resource.
Detailed description of the invention
Fig. 1 is the structural schematic diagram of message push system provided by the embodiment of the present invention one；
Fig. 2 is the structural schematic diagram of message push system provided by the embodiment of the present invention two；
Fig. 3 is the structural schematic diagram of message push system provided by the embodiment of the present invention three；
Fig. 4 a is the structural schematic diagram of message push system provided by the embodiment of the present invention four；
Fig. 4 b is the relation schematic diagram of each module in message push system provided by the embodiment of the present invention four；
Fig. 4 c is the relation schematic diagram in message push system provided by the embodiment of the present invention four between class and module；
Fig. 5 a is the flow chart of information push method provided by the embodiment of the present invention five；
Fig. 5 b is the flow diagram of client registers in information push method provided by the embodiment of the present invention five；
Fig. 5 c is the timing diagram that message pushes in information push method provided by the embodiment of the present invention five.
Specific embodiment
The present invention is described in further detail with reference to the accompanying drawings and examples.It is understood that this place is retouched
The specific embodiment stated is used only for explaining the present invention rather than limiting the invention.It also should be noted that in order to just
Only the parts related to the present invention are shown in description, attached drawing rather than entire infrastructure.
Embodiment one
Fig. 1 is the structural schematic diagram of message push system provided by the embodiment of the present invention one, provided by the present embodiment
Message push system can be used for carrying out situation when message push between medical staff each in hospital.As shown in Figure 1, the message
Supplying system includes: at least one communicating terminal 110, message server 120 and client confirmation module 130.
The communicating terminal 110, for message server 120 initiate include to PUSH message message push ask
It asks；
The message server 120, for being sent according to message push request to the client confirmation module 130
Client acquisition request to be pushed；
The client confirmation module 130, the client to be pushed for being sent according to the message server 120 obtain
Request determines at least one client identification to be pushed corresponding to the client acquisition request to be pushed, and by described at least
One client identification to be pushed is sent to the message server 120；
The message server 120, is also used to receive the client identification to be pushed, and to the client to be pushed
It identifies corresponding wait push described in client push to PUSH message.
Optionally, it can be contacted in time between the medical staff in order to make hospital, each medical staff can body-worn
One mobile terminal, carry out user's login after, can be contacted at any time with other medical staff, realize each medical staff it
Between message push and message publication.
In the present embodiment, it when medical staff carries out the push of message by communicating terminal 110, can choose wait push away
After sending target, " transmission " button, triggering are being clicked to PUSH message wait push input in information input area corresponding to target
The push operation of message.After communicating terminal 110 detects the message push operation of medical staff's triggering, according to acquisition wait push
Message and relevant information form message push request, and message push request is sent to message server 120, messaging service
Device 120 generates client acquisition request to be pushed according to the message push request received, and by the client to be pushed of generation
Acquisition request is sent to client confirmation module 130, and client confirmation module 130 is obtained according to the client to be pushed received
Request determine with should client identification be pushed corresponding to client acquisition request be pushed, and by determining client to be pushed
Hold identification feedback to message server 120, message server 120 is according to the client identification to be pushed received, to wait push
Client push waits for PUSH message, completes the push of message.
Optionally, disappearing wait push for different messages push-type may be implemented in message push system provided by the present embodiment
The push of breath.Optionally, the push of point-to-point message not only may be implemented in message push system provided by the present embodiment, may be used also
To realize the push of distribution subscription formula message.Wherein, the push of point-to-point message refer to will to PUSH message by communication eventually
End pushes to another communicating terminal, and the push of distribution subscription formula message, which refers to, to be pushed to PUSH message by a communicating terminal
Extremely the associated multiple communicating terminals of PUSH message are waited for this.
Optionally, it when medical staff needs to realize the push of peer by communicating terminal, can choose wait push away
User is sent, wait push the input of information input area corresponding to user to PUSH message, " transmission " button is clicked, triggers message
Point-to-point push.When medical staff needs to realize the distribution subscription formula push of message by communicating terminal, hair can be chosen
Cloth subscribes to theme, and the Information Number corresponding to distribution subscription theme goes input in region to click " transmission " button to PUSH message,
Trigger the distribution subscription formula push of message.
In the present embodiment, no matter message push-type is the push or distribution subscription formula message of point-to-point message
Push, obtains client identification to be pushed to client confirmation module by message server, has unified different messages push
The push mode of type, it is only necessary to which a thread is established between communicating terminal and message server can be realized, and money is greatly saved
While source, the power consumption of communicating terminal is also greatly saved；And make when user will send message, it is only necessary to specified to disappear
The destination of breath, without being concerned about that destination is the theme of client or distribution subscription on earth, there are no need to be directed to both
Mode does some specially treateds, simplifies the operation of user, improves user experience.
Optionally, client confirmation module is called to also achieve for different clients by message server in the present embodiment
The unification of the message push interface of end system, externally provides unified message and pushes relevant interface, shield different clients
The difference of PUSH message between end can support a plurality of types of clients (such as Android, IOS, PC, window phone
Deng), and can very easily be integrated with third party's message server (such as activeMQ), the diversification for meeting message push needs
It asks, realizes high efficiency, cross-platform message push across client (message sink end).
Message push system provided by the embodiment of the present invention, comprising: at least one communicating terminal, message server and visitor
Family end confirmation module；Communicating terminal, for initiating to include the message push request to PUSH message to message server；Message
Server, for sending client acquisition request to be pushed to client confirmation module according to message push request；Client is true
Recognize module, the client acquisition request to be pushed for sending according to message server determines client acquisition request institute to be pushed
At least one corresponding client identification to be pushed, and at least one client identification to be pushed is sent to message server；
Message server, is also used to receive client identification to be pushed, and to the corresponding client to be pushed of client identification to be pushed
Push obtains client identification to be pushed to client confirmation module by message server, realizes client to PUSH message
The unification of message push interface when holding type difference, and on the basis of opening a thread, realize different types of disappear
The push of breath saves the power consumption of communicating terminal while saving resource.
On the basis of above scheme, the message server is used for:
Judge the push-type of the message push request, and is obtained the client to be pushed according to the push-type
Request is taken to be sent to corresponding client determining module.
In the present embodiment, for different message push-types, client to be pushed is produced by message server
Acquisition request, and client identification to be pushed is obtained to client confirmation module by client acquisition request to be pushed.It is optional
, the corresponding relationship to push message type and client determining module can be set, it, will when push message type difference
Client acquisition request to be pushed be sent to the corresponding client determining module of push message type.Different disappears wait push
Breath type corresponds to different client determining modules, so that the calling logic of message push system is more clear, more convenient pipe
Reason.
Embodiment two
Fig. 2 is the structural schematic diagram of message push system provided by the embodiment of the present invention two, and the present embodiment is with above-mentioned reality
Based on applying example, message server and client determining module are embodied.As shown in Fig. 2, the client confirmation
Module 130 includes client registers unit 131, and the message server 120 is used for:
If the push-type is point-to-point push, client to be pushed is generated according to message push request and is obtained
Request, and the client acquisition request to be pushed is sent to the client registers unit 131.
In the present embodiment, after the message push that message server 120 receives the initiation of communicating terminal 110 is requested, according to
Message push request judges the message push-type to PUSH message, if message push-type is point-to-point push, message clothes
Business device 120 generates client acquisition request to be pushed according to message push request, and client acquisition request to be pushed is sent to
Client registers unit 131, and the client identification to be pushed of the feedback of client registers unit 131 is received, according to what is received
Client identification to be pushed carries out the point-to-point push to PUSH message.
It optionally, include to PUSH message and target mark to be pushed in the message push request that communicating terminal 110 is initiated
Know (user identifier i.e. to be pushed), message server 120 can judge the push to PUSH message according to target identification to be pushed
Type.Optionally, the preset field of target identification to be pushed can be matched with default mark, it will be with target mark to be pushed
Know type of message corresponding to matched default mark and is determined as type of message to PUSH message.It illustratively, can will be to
The first place number of push target identification is matched with default mark, determines the message class to PUSH message according to matching result
Type.
Illustratively, if point-to-point the default of message push, which is arranged, is identified as 1, when the first number of target identification to be pushed
Word be 1 when, determine to PUSH message type of message be point-to-point message push, by according to message push request generation wait push away
Client acquisition request is sent to be sent to client registers unit.
On the basis of above scheme, the client registers unit 131 is used for:
According to the client acquisition request to be pushed that the message server 120 is sent, the determining and client to be pushed
In the acquisition request of end wait push client identification to be pushed corresponding to user identifier, and by the client identification to be pushed
It is sent to the message server 120.
It optionally, include user identifier to be pushed in the client acquisition request to be pushed that message server 120 is sent,
Client registers unit 131 determines client to be pushed according to the user identifier to be pushed for including in client acquisition request to be pushed
End mark, and determining client identification to be pushed is sent to message server 120.
Illustratively, if the user identifier to be pushed for including in the client acquisition request to be pushed that message server is sent
For " 11 ", then client registers unit is determined and is used according to the incidence relation between the user identifier and client identification of storage
Family identifies the client identification " 31 " of " 11 " corresponding storage, and client identification " 31 " are sent as client identification to be pushed
To message server.
On the basis of above scheme, the client registers unit 131 is also used to:
The registration request of user to be registered is received, and obtains the user identifier for including in the registration request and client mark
Know, establishes the incidence relation between the client identification and the user identifier.
In the present embodiment, client registers unit can also respond the registration request of new user, and store use to be registered
The relevant information at family.Optionally, when needing to register new user, user can be inputted on the user's registration interface of communicating terminal
Essential information, clicks the registration operation that " registration " button triggers new user, and communicating terminal detects the registration operation of user's triggering
When, according to the essential information that user inputs, user's registration request is generated in conjunction with the identification information of itself, and the user of generation is infused
Volume request is sent to message server, and user's registration request is sent to client registers unit, client by message server
Registering unit obtains user identifier and client identification in user's registration request, deposits user identifier is corresponding with client identification
Storage, establishes the incidence relation between user identifier and client identification.
The technical solution of the embodiment of the present invention, determines mould for message server and client on the basis of the above embodiments
Block is embodied, and is judged by message server when the push-type of PUSH message is point-to-point push, according to message
Push request generates client acquisition request to be pushed, and client acquisition request to be pushed is sent to client registers list
Member, obtain client registers unit feedback client identification to be pushed, according to the client identification to be pushed of acquisition complete to
The point-to-point push of PUSH message realizes when push message type difference, and message pushes the unification of interface, and makes
The determination of client to be pushed is more accurate.
Embodiment three
Fig. 3 is the structural schematic diagram of message push system provided by the embodiment of the present invention three, and the present embodiment is with above-mentioned reality
Based on applying example, message server and client determining module are embodied.As shown in figure 3, the client confirmation
Module 130 includes message subscribing unit 132, and the message server 120 is used for:
If the push-type is distribution subscription, client acquisition to be pushed is generated according to message push request and is asked
It asks, and the client acquisition request to be pushed is sent to the message subscribing unit 132.
In the present embodiment, after the message push that message server 120 receives the initiation of communicating terminal 110 is requested, according to
Message push request judges the message push-type to PUSH message, if message push-type is the push of distribution subscription message,
Message server 120 generates client acquisition request to be pushed according to message push request, will client acquisition request be pushed
It is sent to message subscribing unit 132, and receives at least one client identification to be pushed of the feedback of message subscribing unit 132, root
Push to the distribution subscription of PUSH message according at least one client identification to be pushed received.
It optionally, include to PUSH message and target mark to be pushed in the message push request that communicating terminal 110 is initiated
Know (user identifier i.e. to be pushed), message server 120 can judge the push to PUSH message according to target identification to be pushed
Type.Optionally, the preset field of target identification to be pushed can be matched with default mark, it will be with target mark to be pushed
Know type of message corresponding to matched default mark and is determined as type of message to PUSH message.It illustratively, can will be to
The first place number of push target identification is matched with default mark, determines the message class to PUSH message according to matching result
Type.
Illustratively, if the default of setting distribution subscription message push is identified as 2, when the first place of target identification to be pushed
When number is 2, determine that the type of message to PUSH message for the push of distribution subscription message, will push what request generated according to message
Client acquisition request to be pushed is sent to message subscribing unit.
On the basis of above scheme, the message subscribing unit 132 is used for:
According to the client acquisition request to be pushed that the message server 120 is sent, the determining and client to be pushed
At least one corresponding client identification to be pushed of acquisition request is held, and at least one described client identification to be pushed is sent
To the message server 120.
It in the present embodiment, include mesh to be pushed in the client acquisition request to be pushed that message server 120 is sent
Mark mark, message subscribing unit 132 according to target identification to be pushed determine client acquisition request to be pushed corresponding at least
One client identification to be pushed, and determining client identification to be pushed is sent to message server 120.
On the basis of above scheme, the message subscribing unit 132 is used for:
According to the subject identification for including in the client acquisition request to be pushed, it is determining with corresponding to the subject identification
At least one client identification to be pushed, and at least one described client identification to be pushed is sent to the messaging service
Device 120.
Optionally, it is stored with the related subscription information of each theme in message subscribing unit 132, such as subscribes to the user of each theme
Mark, client identification etc..Optionally, when the push-type of PUSH message is that distribution subscription message pushes, mesh to be pushed
Mark mark can be the subject identification of distribution subscription.Message server 120 sends the client to be pushed for carrying subject identification
Acquisition request, message subscribing unit 132 is according to the subject identification determination and theme mark for including in client acquisition request to be pushed
Know at least one corresponding client identification to be pushed, and determining client identification to be pushed is sent to message server
120。
Illustratively, if the subject identification for including in the client acquisition request to be pushed that message server is sent is
" 21 ", then message subscribing unit is according to the incidence relation between the subject identification and client identification of storage, determining and theme mark
The client identification for knowing " 21 " corresponding storage has " 32 ", " 33 ", and regard client identification 32 ", " 33 " as client to be pushed
Mark is sent to message server.
On the basis of above scheme, the message subscribing unit 132 is also used to:
It receives and is requested to the subscription of booking reader, and obtain the subject identification for including in the subscription request and client mark
Know, establishes the incidence relation between the subject identification and the client identification.
In the present embodiment, message subscribing unit can also respond the subscription request of user, and store the subscription of each theme
User information.It optionally, can be on communicating terminal on the subscription interface of the theme when there is user to need to subscribe to a certain theme
It clicks " subscription " button and triggers subscription operation, when communicating terminal detects the subscription operation of user's triggering, according to ordered by user
Subject identification, generate user in conjunction with itself identification information and subscribe to request, and the user of generation is subscribed into request and is sent to and disappears
Server is ceased, which is subscribed to request and be sent to message subscribing unit by message server, and message subscribing unit obtains user and orders
Read request in subject identification and client identification, by subject identification it is corresponding with client identification store, establish subject identification and
Incidence relation between client identification.
Optionally, it can also include the user identifier of booking reader in message subscribing request, be wrapped when in message subscribing request
The corresponding storage of user identifier, subject identification and client identification can be established user by when containing user identifier, message subscribing unit
Incidence relation between mark, subject identification and client identification.
The technical solution of the embodiment of the present invention, determines mould for message server and client on the basis of the above embodiments
Block is embodied, and is judged when the push-type of PUSH message pushes as distribution subscription message by message server, root
Client acquisition request to be pushed is generated according to message push request, and client acquisition request to be pushed is sent to message subscribing
Unit, obtain message subscribing unit feedback client identification to be pushed, according to the client identification to be pushed of acquisition complete to
The distribution subscription of PUSH message pushes, and realizes when push message type difference, and message pushes the unification of interface, and makes
The determination for obtaining client to be pushed is more accurate.
Example IV
Fig. 4 a is the structural schematic diagram of message push system provided by the embodiment of the present invention four.The present embodiment is in above-mentioned reality
On the basis of applying example, a kind of preferred embodiment is provided.
As shown in fig. 4 a, the accessible client of the message push system can be the clients such as Android, IOS, PC.
The message push system include: interface service module, client registers module, message subscribing module, message sink sending module,
Configuration management module.Fig. 4 b is the relation schematic diagram of each module in message push system provided by the embodiment of the present invention four.Such as
Shown in Fig. 4 b, interface service module is to function provided by client registers module, message subscribing module, message sink sending module
It can be carried out encapsulation, externally provided unified interface, for calling.Message sink sending module is obtained from client registers module
Registered client is taken, obtains the client side list for having subscribed to certain theme, from message subscribing module to carry out message push.
Message sink sending module will use the part configuration data in configuration management module when carrying out information receiving and transmitting.
Fig. 4 c is the relation schematic diagram in message push system provided by the embodiment of the present invention four between class and module.Such as
Shown in Fig. 4 c, the relationship between class and module is as follows: the class that interface service module divides are as follows: MessageService,
MessageServiceImpl (default of MessageService is realized)；The class that client registers module divides are as follows:
DestinationRegister；The class that message subscribing module divides are as follows: Subscriber；What message sink sending module divided
Class are as follows: MessageManager, MessagePusher, AndroidPusher, IOSPusher, PCPusher；Configuration management mould
The class that block divides are as follows: Configuration；Server is server interface, and MessageServer is message server, can be opened
Dynamic or closing message server.
MessageServer takes according to the relevant configuration initiation message in Configuration it can be seen from Fig. 4 c
Business device；MessageService is injected into MessageServer, is exposed to external call；MessageManager by
The push of MessagePusher progress message；Message push system provided by the embodiment of the present invention passes through offer
The different of MessagePusher are realized, can easily support the access of new client；As long as in addition, being
MessageManager provides different realizations, so that it may access third party's message server, such as provide an ActiveMQ
Realization class ActiveMQMessageManager i.e. be convenient to access third party's message server ActiveMQ.
Embodiment five
Fig. 5 a is the flow chart of information push method provided by the embodiment of the present invention five, the present embodiment be applicable to using
Message push system provided by the above embodiment of the present invention carries out situation when message push.As shown in Figure 5 a, this method has
Body includes:
S510, communicating terminal initiate to include the message push request to PUSH message to message server.
S520, message server send client acquisition to be pushed to client confirmation module according to message push request and ask
It asks.
The client acquisition request to be pushed that S530, client confirmation module are sent according to message server is determined wait push
At least one client identification to be pushed corresponding to client acquisition request, and client identification to be pushed is sent to message
Server.
S540, message server receive client identification to be pushed, and corresponding wait push to client identification to be pushed
Client push waits for PUSH message.
In the present embodiment, by communicating terminal to message server initiate include to PUSH message message push ask
It asks, message server pushes request confirmation module according to message and determines client to be pushed according to client acquisition request to be pushed
At least one client identification to be pushed corresponding to acquisition request, and client identification to be pushed is sent to messaging service
Device, message server receive client identification to be pushed, and to the corresponding client to be pushed of the client identification to be pushed
Push is to PUSH message.
Fig. 5 b is the flow diagram of client registers in information push method provided by the embodiment of the present invention five.Such as figure
Shown in 5b, after message server starting, starting client (can be the client of the types such as Android, IOS, PC), user's touching
Registration request is sent out, client initiates registration request to message server, and the registration that message server receives client initiation is asked
After asking, it is established that the communication connection between client and message server.Optionally, calling can be passed through
MessageServer.start () initiation message server.
Fig. 5 c is the timing diagram that message pushes in information push method provided by the embodiment of the present invention five.Such as Fig. 5 c institute
Show, the information push method (MessageService.send ()) of client call interface service is sent a message to specified
Destination.Wherein, specified destination can be another client or some theme.When specified destination is another client
When, MessageService obtains registered client corresponding with specified destination to client registers module
(DestinationRegister.get())；If there is registered client, then message is sent to the client
(MessageManager.send ()), MessageManager is by message pusher (MessagePusher) to different
Client push message；When specified destination is some theme, MessageService is obtained to message subscribing module and is subscribed to
The client of the theme (topic) is then recycled if there is client is subscribed to each subscriptions client transmission message
(MessageManager.send())。
Optionally, it can be found in above-described embodiment using the more detailed content that message push system carries out message push,
Details are not described herein.
The embodiment of the present invention realizes user in hospital business system by hospital interface server using communication server
Verifying and can association user feedback, realize on the basis of not needing each user and carrying out associated between user, hospital
Timely communication between interior medical staff, and by hospital interface server calls hospital business system, realize communication garment
Business device is docked with the existing operation system of hospital, so that simplifying when using the system without in addition maintenance user data
The use process of user.
Note that the above is only a better embodiment of the present invention and the applied technical principle.It will be appreciated by those skilled in the art that
The invention is not limited to the specific embodiments described herein, be able to carry out for a person skilled in the art it is various it is apparent variation,
It readjusts and substitutes without departing from protection scope of the present invention.Therefore, although being carried out by above embodiments to the present invention
It is described in further detail, but the present invention is not limited to the above embodiments only, without departing from the inventive concept, also
It may include more other equivalent embodiments, and the scope of the invention is determined by the scope of the appended claims.
Claims (10)
1. a kind of message push system characterized by comprising at least one communicating terminal, message server and client are true
Recognize module；
The communicating terminal, for initiating to include the message push request to PUSH message to message server；
The message server, for sending client to be pushed to the client confirmation module according to message push request
Hold acquisition request；
The client confirmation module, the client acquisition request to be pushed for being sent according to the message server determine institute
State at least one client identification to be pushed corresponding to client acquisition request to be pushed, and by it is described at least one wait pushing
Client identification is sent to the message server；
The message server, is also used to receive the client identification to be pushed, and to the client identification pair to be pushed
Answer wait push described in client push to PUSH message.
2. system according to claim 1, which is characterized in that the message server is used for:
Judge the push-type of the message push request, and is asked the client acquisition to be pushed according to the push-type
It asks and is sent to corresponding client determining module.
3. system according to claim 2, which is characterized in that the client confirmation module includes client registers list
Member, the message server are used for:
If the push-type is point-to-point push, client acquisition to be pushed is generated according to message push request and is asked
It asks, and the client acquisition request to be pushed is sent to the client registers unit.
4. system according to claim 3, which is characterized in that the client registers unit is used for:
It is determining to be asked with the client acquisition to be pushed according to the client acquisition request to be pushed that the message server is sent
That asks is sent to institute wait push client identification to be pushed corresponding to user identifier, and by the client identification to be pushed
State message server.
5. system according to claim 3, which is characterized in that the client registers unit is also used to:
The registration request of user to be registered is received, and obtains the user identifier for including in the registration request and client identification,
Establish the incidence relation between the client identification and the user identifier.
6. system according to claim 2, which is characterized in that the client confirmation module includes message subscribing unit,
The message server is used for:
If the push-type is distribution subscription, client acquisition request to be pushed is generated according to message push request,
And the client acquisition request to be pushed is sent to the message subscribing unit.
7. system according to claim 6, which is characterized in that the message subscribing unit is used for:
It is determining to be asked with the client acquisition to be pushed according to the client acquisition request to be pushed that the message server is sent
At least one corresponding client identification to be pushed is sought, and at least one described client identification to be pushed is sent to described disappear
Cease server.
8. system according to claim 7, which is characterized in that the message subscribing unit is used for:
According to the subject identification for including in the client acquisition request to be pushed, it is determining with corresponding to the subject identification extremely
A few client identification to be pushed, and at least one described client identification to be pushed is sent to the message server.
9. system according to claim 6, which is characterized in that the message subscribing unit is also used to:
It receives and is requested to the subscription of booking reader, and obtain the subject identification for including in the subscription request and client identification,
Establish the incidence relation between the subject identification and the client identification.
10. a kind of information push method is applied to message push system as described in claim 1 characterized by comprising
Communicating terminal initiates to include the message push request to PUSH message to message server；
The message server sends client to be pushed to the client confirmation module according to message push request and obtains
Take request；
The client acquisition request to be pushed that the client confirmation module is sent according to the message server determine it is described to
At least one client identification to be pushed corresponding to client acquisition request is pushed, and the client identification to be pushed is sent out
It send to the message server；
The message server receives the client identification to be pushed, and corresponding wait push away to the client identification to be pushed
It send described in client push to PUSH message.
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 true CN109246220A (en) | 2019-01-18 |
| CN109246220B 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) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109889613A (en) * | 2019-04-24 | 2019-06-14 | 广州吱呀网络科技有限公司 | A kind of information push method, device and mobile terminal |
| CN111225044A (en) * | 2019-12-31 | 2020-06-02 | 北京奇才天下科技有限公司 | Client message pushing method, device and system |
| CN111464598A (en) * | 2020-03-19 | 2020-07-28 | 中国人民财产保险股份有限公司 | Data pushing method and device |
| CN111555963A (en) * | 2020-04-30 | 2020-08-18 | 北京思特奇信息技术股份有限公司 | 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 |
| CN112087475A (en) * | 2019-06-13 | 2020-12-15 | 北京东土科技股份有限公司 | Message pushing method and device for cloud platform component application and message server |
| CN112287216A (en) * | 2020-10-23 | 2021-01-29 | 微医云(杭州)控股有限公司 | Information pushing method and device, server and storage medium |
| CN113067853A (en) * | 2021-03-12 | 2021-07-02 | 北京金山云网络技术有限公司 | Data pushing method and device, electronic equipment and storage medium |
| CN114531481A (en) * | 2020-11-03 | 2022-05-24 | 湖南微步信息科技有限责任公司 | Message pushing method and system |
Citations (10)
| 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 |
| US20150244823A1 (en) * | 2014-02-21 | 2015-08-27 | Samsung Electronics Co., Ltd. | Apparatus and method for providing push service based on location |
| CN105099882A (en) * | 2015-07-09 | 2015-11-25 | 杭州电子科技大学 | MQTT-based cloud pushing method and system |
| 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 |
| 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 |
-
2018
- 2018-09-19 CN CN201811094844.1A patent/CN109246220B/en active Active
Patent Citations (10)
| 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 |
| US20150244823A1 (en) * | 2014-02-21 | 2015-08-27 | Samsung Electronics Co., Ltd. | Apparatus and method for providing push service based on location |
| CN103840950A (en) * | 2014-02-27 | 2014-06-04 | 广东亿迅科技有限公司 | Information pushing method and system |
| 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 |
| 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 |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109889613A (en) * | 2019-04-24 | 2019-06-14 | 广州吱呀网络科技有限公司 | A kind of information push method, device and mobile terminal |
| CN112087475A (en) * | 2019-06-13 | 2020-12-15 | 北京东土科技股份有限公司 | Message pushing method and device for cloud platform component application and message server |
| CN112087475B (en) * | 2019-06-13 | 2023-01-24 | 北京东土科技股份有限公司 | Message pushing method and device for cloud platform component application and message server |
| CN111225044A (en) * | 2019-12-31 | 2020-06-02 | 北京奇才天下科技有限公司 | Client message pushing method, device and system |
| 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 |
| CN111555963A (en) * | 2020-04-30 | 2020-08-18 | 北京思特奇信息技术股份有限公司 | 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 |
| CN112287216A (en) * | 2020-10-23 | 2021-01-29 | 微医云(杭州)控股有限公司 | 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109246220B (en) | 2021-08-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109246220A (en) | A kind of message push system and method | |
| KR102029277B1 (en) | Device Identifier-Dependent Operation Processing for Packet-Based Data Communications | |
| CN102255934B (en) | Cloud service dissemination method and cloud service intermediary | |
| CN102255935B (en) | Cloud service consuming method, cloud service intermediary and cloud system | |
| CN103634382B (en) | A kind of system and method for realizing real-time, interactive on webpage | |
| CN109587044A (en) | Group creating, method for message interaction and device | |
| KR20170006813A (en) | Method and Apparatus for Supporting Secure Chat | |
| US9065788B2 (en) | Method, device and system for voice communication | |
| CN105141506B (en) | communication message processing method and device | |
| CN111611091A (en) | Service calling method, device and medium for business object | |
| EP3017583A1 (en) | Seamless call transitions with escalation-aware notifications | |
| WO2016010921A1 (en) | Creating a user group | |
| EP2974159B1 (en) | Method, device and system for voice communication | |
| KR20150021928A (en) | Transmitting initiation details from a mobile device | |
| CN107995351A (en) | Call method and device | |
| Sneps-Sneppe et al. | M2M applications and open API: What could be next? | |
| CN114513552A (en) | Data processing method, device, equipment and storage medium | |
| WO2015184879A1 (en) | Terminal topology management service method, device, and system for internet of things | |
| CN110619698B (en) | Information prompting method and device based on Internet of things operating system | |
| CN109040331B (en) | Electronic business card processing method and device, computing equipment and storage medium | |
| US20150365133A1 (en) | Touch and Talk Auto-Configuring of Video Conferences Using Near Field Communication (NFC) | |
| CN112256372A (en) | Information processing method and device and electronic equipment | |
| CN103856395A (en) | Method and system for calling friends and making discussion on webpage | |
| CN112839065A (en) | Information processing method and device, first equipment and storage medium | |
| GB2490007A (en) | Tracking message responses by associating calling and recipient phone numbers with a message |
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 |