CN108234631A - Message pushes platform and information push method - Google Patents
Message pushes platform and information push method Download PDFInfo
- Publication number
- CN108234631A CN108234631A CN201711480979.7A CN201711480979A CN108234631A CN 108234631 A CN108234631 A CN 108234631A CN 201711480979 A CN201711480979 A CN 201711480979A CN 108234631 A CN108234631 A CN 108234631A
- Authority
- CN
- China
- Prior art keywords
- push
- message
- client
- pushed
- end node
- 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
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
-
- 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/56—Provisioning of proxy services
Abstract
The present invention provides a kind of message push platform and information push methods.Message push platform includes front end unit, routing unit, database and backend unit, by cooperating to PUSH message between front end unit, routing unit, database and backend unit, Partition of role is clear and definite, be easily achieved with O＆M dilatation, can improve message push efficiency and accuracy.And, the embodiment of the present invention extracts link information dynamic between front end node and client from front end unit, database and backend unit, it is recorded in real time by routing unit, the access pressure of database and front end unit, the load of backend unit can be effectively reduced.
Description
Technical field
The present invention relates to technical field of internet application, particularly a kind of message push platform and information push method.
Background technology
Message push is the time searched on network user to be reduced to be used for by automatically delivering information to user.Its root
It searches for according to the interest of user, filter information, and it is periodically pushed to user, user is helped expeditiously to excavate valuable letter
Breath.Therefore, how to realize that easily message push becomes the technical issues of urgently to be resolved hurrily.
Invention content
In view of the above problems, it is proposed that the present invention overcomes the above problem in order to provide one kind or solves at least partly
State the message push platform and information push method of problem.
One side according to embodiments of the present invention provides a kind of message push platform, including：Front end unit, routing are single
Member, database and backend unit；
The front end unit is made of one or more front end nodes, suitable in the connection request for receiving client,
It is established and connected, and link information is registered to the routing unit by the corresponding front end node of the connection request and client；
The routing unit, suitable for the link information between record front end node and client；
The database treats PUSH message and its correspondence between identifying suitable for storage；And
The backend unit pushes order suitable for receiving the message from push end, parses the message push and orders
To the mark for treating PUSH message, searched from the database according to the mark for treating PUSH message and treat that push disappears accordingly
Breath and according to the message push order and the routing unit record link information, determine it is at least one treat push visitor
Family end and at least one front end node to be pushed treat PUSH message to described at least one front end node transmission to be pushed,
So as to treat PUSH message at least one client to be pushed as described at least one front end node push to be pushed.
Optionally, the backend unit is further adapted for：
At least one client to be pushed is determined according to message push order, is recorded from the routing unit
The front end node that at least one client to be pushed respectively connects is searched in link information, at least one waits to push away as described
Send front end node.
Optionally, the backend unit is further adapted for：
Parsing obtains at least one client to be pushed from message push order；Or
Parsing obtains the correlated condition of client to be pushed from message push order, in the client built in advance
Lookup and the matched client of the correlated condition in list, as at least one client to be pushed.
Optionally, the correlated condition includes at least one following：
Area information, access network type, place terminal current state.
Optionally, the backend unit is further adapted for：
Parsing obtains at least one front end node to be pushed from message push order, from the routing unit
The client that at least one front end node to be pushed respectively connects is searched in the link information of record, as described at least one
A client to be pushed.
Optionally, each front end node in the front end unit records the link information of itself and client.
Optionally, the backend unit is further adapted for：
Parsing obtains at least one front end node to be pushed from message push order, to described at least one
Front end node to be pushed treats PUSH message described in sending, so as to wait to push away as described at least one front end node transmission to be pushed
Message is sent to the client of self record.
Optionally, the multiple front end node is distributed in one or more server clusters.
Optionally, the message push platform further includes：
Database broker treats the mark of PUSH message from the database suitable for receiving the backend unit according to
The search request for treating PUSH message accordingly is searched, is searched in the database according to the search request and waits to push accordingly
Message, and it is sent to the backend unit.
Optionally, the database broker is further adapted for：
Searched in the database according to the search request it is corresponding treat PUSH message after, wait to push away described in caching
Message is sent, is searched when the search request of PUSH message so that the backend unit next time sends, first in the message of caching
It searches whether to exist and treats PUSH message, if in the presence of caching directly being treated, PUSH message is sent to the backend unit；If no
In the presence of then being searched in the database according to the search request and treat PUSH message accordingly, and it is single to be sent to the rear end
Member.
Optionally, the front end unit is further adapted for：
When the connection with client meets disconnection condition, will be noted with the link information of client from the routing unit
Pin, so as to which the routing unit deletes the link information between front end node and client.
Optionally, the disconnection condition includes at least one following：
Receive the request disconnected of client transmission；
Client heartbeat timeout.
Optionally, the backend unit is further adapted for：
It is determining described at least one after client is pushed being ordered according to message push, if from the routing unit
The front end node of one or more of described at least one client to be pushed connection is not found in the link information of record,
Then determine that one or more of clients to be pushed are in off-line state, thus ought one or more of clients to be pushed
Again after reaching the standard grade, in the link information recorded from the routing unit one or more of clients to be pushed are searched respectively to connect
The front end node connect treats PUSH message to one or more of clients to be pushed as described in the front end node push found
End, wherein, the off-line state refers to that front end node is disconnected with client.
Optionally, the backend unit is further adapted for：
It is determining one or more of when pushing client and being in off-line state, is establishing and one or more of wait to push away
Send respectively client to be pushed and the deferred information list treated between PUSH message in client；
When one or more of after push client is reached the standard grade again, found from the deferred information list described
Treat PUSH message.
Optionally, the backend unit is further adapted for：
As find front end node push described in treat PUSH message to one or more of clients to be pushed it
Before, it treats whether PUSH message is expired described in judgement, if without expired, performs push operation；If expired, do not perform and push away
Send operation.
Optionally, the backend unit is further adapted for：
Determine it is one or more of wait push client be in off-line state when, by it is described treat PUSH message with it is expired
Time, which corresponds to, to be preserved, so as to treat that PUSH message is waited to push to one or more of as described in the front end node push found
Before client, the expired time and current time of preservation are compared, treats whether PUSH message is expired described in judgement.
Another aspect according to embodiments of the present invention additionally provides a kind of information push method, flat applied to message push
Front end unit on platform, the front end unit are made of one or more front end nodes, including：
In the connection request for receiving client, established and connected by the corresponding front end node of the connection request and client
It connects, and link information is registered to the routing unit on the message push platform；And
When the backend unit transmission on receiving the message push platform is when PUSH message, treat that push disappears by described
Breath pushes to corresponding client.
Optionally, each front end node in the front end unit records the link information of itself and client.
Optionally, the multiple front end node is distributed in one or more server clusters.
Optionally, the information push method further includes：
When the connection with client meets disconnection condition, will be noted with the link information of client from the routing unit
Pin, so as to which the routing unit deletes the link information between front end node and client.
Optionally, the disconnection condition includes at least one following：
Receive the request disconnected of client transmission；
Client heartbeat timeout.
Another aspect according to embodiments of the present invention, additionally provides a kind of information push method, flat applied to message push
Backend unit on platform, including：
It receives the message from push end and pushes order, parse the mark that the message push order obtains treating PUSH message
Know；
It is searched from the database on message push platform according to the mark for treating PUSH message and waits to push away accordingly
Message is sent, wherein, the database purchase needs PUSH message and its correspondence between identifying；
According to the link information that the routing unit in message push order and message push platform records, determine
At least one client to be pushed and at least one front end node to be pushed, wherein, the routing unit record has front end node
Link information between client；And
To at least one front end node to be pushed send described in treat PUSH message, so as at least one wait to push away by described
Send treats PUSH message at least one client to be pushed described in front end node push.
Optionally, the company that the routing unit according in message push order and message push platform records
The step of connecing information, determining at least one client to be pushed and at least one front end node to be pushed further comprises：
At least one client to be pushed is determined according to message push order, is recorded from the routing unit
The front end node that at least one client to be pushed respectively connects is searched in link information, at least one waits to push away as described
Send front end node.
Optionally, it is described that the step of determining at least one client to be pushed is ordered into one according to message push
Step includes：
Parsing obtains at least one client to be pushed from message push order；Or
Parsing obtains the correlated condition of client to be pushed from message push order, in the client built in advance
Lookup and the matched client of the correlated condition in list, as at least one client to be pushed.
Optionally, the correlated condition includes at least one following：
Area information, access network type, place terminal current state.
Optionally, the company that the routing unit according in message push order and message push platform records
The step of connecing information, determining at least one client to be pushed and at least one front end node to be pushed further comprises：
Parsing obtains at least one front end node to be pushed from message push order, from the routing unit
The client that at least one front end node to be pushed respectively connects is searched in the link information of record, as described at least one
A client to be pushed.
Optionally, each front end node in the front end unit records the link information of itself and client, described
According to the link information that the routing unit in message push order and message push platform records, at least one treat is determined
The step of push client and at least one front end node to be pushed, further comprises：
Parsing obtains at least one front end node to be pushed from message push order, to described at least one
Front end node to be pushed treats PUSH message described in sending, so as to wait to push away as described at least one front end node transmission to be pushed
Message is sent to the client of self record.
Optionally, treat that the mark of PUSH message is searched from the database on message push platform described in the basis
Corresponding the step for the treatment of PUSH message, further comprises：
Database broker on message push platform is sent treats the mark of PUSH message from the number according to
Treat the search request of PUSH message accordingly according to lookup in library；
It receives the described of database broker return and treats PUSH message.
Optionally, the database broker is waited to push being searched in the database according to the search request accordingly
After message, PUSH message is treated described in caching, is asked so that sending the backend unit next time and searching the lookup for treating PUSH message
It when asking, first searches whether to exist in the message of caching and treats PUSH message, if in the presence of caching directly being treated, PUSH message is sent out
Give the backend unit；If being not present, searched in the database according to the search request and treat that push disappears accordingly
Breath, and it is sent to the backend unit.
Optionally, the information push method further includes：
It is determining described at least one after client is pushed being ordered according to message push, if from the routing unit
The front end node of one or more of described at least one client to be pushed connection is not found in the link information of record,
Then determine that one or more of clients to be pushed are in off-line state, thus ought one or more of clients to be pushed
Again after reaching the standard grade, in the link information recorded from the routing unit one or more of clients to be pushed are searched respectively to connect
The front end node connect treats PUSH message to one or more of clients to be pushed as described in the front end node push found
End, wherein, the off-line state refers to that front end node is disconnected with client.
Optionally, the information push method further includes：
It is determining one or more of when pushing client and being in off-line state, is establishing and one or more of wait to push away
Send respectively client to be pushed and the deferred information list treated between PUSH message in client；
When one or more of after push client is reached the standard grade again, found from the deferred information list described
Treat PUSH message.
Optionally, the information push method further includes：
As find front end node push described in treat PUSH message to one or more of clients to be pushed it
Before, it treats whether PUSH message is expired described in judgement, if without expired, performs push operation；If expired, do not perform and push away
Send operation.
Optionally, the information push method further includes：
Determine it is one or more of wait push client be in off-line state when, by it is described treat PUSH message with it is expired
Time, which corresponds to, to be preserved, so as to treat that PUSH message is waited to push to one or more of as described in the front end node push found
Before client, the expired time and current time of preservation are compared, treats whether PUSH message is expired described in judgement.
Message provided in an embodiment of the present invention pushes platform, it include front end unit, routing unit, database and after
End unit, specifically, front end unit are made of one or more front end nodes, suitable in the connection request for receiving client
When, it is established and connected, and link information is registered to routing unit by the corresponding front end node of connection request and client；Routing is single
Member, suitable for the link information between record front end node and client；Database treats PUSH message and between it identifies suitable for storage
Correspondence；And backend unit, order is pushed suitable for receiving the message from push end, parsing message push order obtains
Treat the mark of PUSH message, according to the mark for treating PUSH message searched from database it is corresponding treat PUSH message and according to
Message push order and the link information of routing unit record, determine at least one client to be pushed and at least one wait to push
Front end node treats PUSH message, so as to by least one front end node to be pushed at least one front end node transmission to be pushed
Push treats PUSH message at least one client to be pushed.It follows that message push platform provided in an embodiment of the present invention
By the PUSH message that cooperates between front end unit, routing unit, database and backend unit, Partition of role is bright
Really, it is easy to accomplish and O＆M dilatation, efficiency and accuracy that message pushes can be improved.Also, the embodiment of the present invention is by front end
Dynamic link information is extracted from front end unit, database and backend unit between node and client, by routing unit Lai
Record in real time, can effectively reduce the access pressure of database and front end unit, the load of backend unit.
Above description is only the general introduction of technical solution of the present invention, in order to better understand the technological means of the present invention,
And it can be implemented in accordance with the contents of the specification, and in order to allow above and other objects of the present invention, feature and advantage can
It is clearer and more comprehensible, below the special specific embodiment for lifting the present invention.
According to the accompanying drawings to the detailed description of the specific embodiment of the invention, those skilled in the art will be brighter
The above and other objects, advantages and features of the present invention.
Description of the drawings
By reading the detailed description of hereafter preferred embodiment, it is various other the advantages of and benefit it is common for this field
Technical staff will become clear.Attached drawing is only used for showing the purpose of preferred embodiment, and is not considered as to the present invention
Limitation.And throughout the drawings, the same reference numbers will be used to refer to the same parts.In the accompanying drawings：
Fig. 1 shows the structure diagram of message push platform according to an embodiment of the invention；
Fig. 2 shows the structure diagrams of message according to another embodiment of the present invention push platform；
Fig. 3 shows the message push of the front end unit according to an embodiment of the invention applied on message push platform
The flow chart of method；And
Fig. 4 shows the message push of the backend unit according to an embodiment of the invention applied on message push platform
The flow chart of method.
Specific embodiment
The exemplary embodiment of the disclosure is more fully described below with reference to accompanying drawings.Although the disclosure is shown in attached drawing
Exemplary embodiment, it being understood, however, that may be realized in various forms the disclosure without should be by embodiments set forth here
It is limited.On the contrary, these embodiments are provided to facilitate a more thoroughly understanding of the present invention, and can be by the scope of the present disclosure
Completely it is communicated to those skilled in the art.
In order to solve the above technical problems, an embodiment of the present invention provides a kind of message to push platform.Fig. 1 is shown according to this
Invent the structure diagram of the message push platform of an embodiment.As shown in Figure 1, before message push platform 100 can include
End unit 110, routing unit 120, database 130 and backend unit 140, specifically：
Front end unit 110 is made of one or more front end nodes, suitable in the connection request for receiving client,
It is established and connected, and link information is registered to routing unit 120 by the corresponding front end node of connection request and client；
Routing unit 120, suitable for the link information between record front end node and client；
Database 130 treats PUSH message and its correspondence between identifying suitable for storage；And
Backend unit 140 pushes order suitable for receiving the message from push end, and parsing message push order obtains waiting to push away
The mark of message is sent, is searched from database 130 according to the mark for treating PUSH message and corresponding treats PUSH message and according to disappearing
The link information that breath push order and routing unit 120 record, determines at least one client to be pushed and at least one waits to push away
Front end node is sent, PUSH message is treated at least one front end node transmission to be pushed, so as to wait to push preceding end segment by least one
Point push treats PUSH message at least one client to be pushed.
Message push platform 100 provided in an embodiment of the present invention passes through front end unit 110, routing unit 120, database
PUSH message is cooperated between 130 and backend unit 140, Partition of role is clear and definite, it is easy to accomplish and O＆M dilatation, energy
Enough improve the efficiency and accuracy of message push.Also, the embodiment of the present invention will dynamically connect between front end node and client
Information is extracted from front end unit 110, database 130 and backend unit 140, is recorded in real time by routing unit 120, can
Effectively reduce the access pressure of database 130 and front end unit 110, the load of backend unit 140.
In the alternative embodiment of the present invention, multiple front end nodes in front end unit 110 can be distributed in one or more
A server cluster.For example, multiple front end nodes in front end unit 110 are divided into cluster P1, P2, P3 etc. according to different products
Deng, P1 includes front end node A1, A2, A3, A4, A5 etc., and P2 includes front end node B1, B2, B3, B4, B5 etc., and so on, i.e.,：
P1 (front end node A1, A2, A3, A4, A5 ...)
P2 (front end node B1, B2, B3, B4, B5 ...)
P3 (front end node C1, C2, C3, C4, C5 ...)
……
Assuming that client a is connected to front end node A1, then the link information is recorded on front end node A1, and connection is believed
Breath is registered to routing unit 120；Can also similarly operate similarly, for client b, c, d etc..Need what is illustrated
It is to enumerate being only illustrative herein, the embodiment of the present invention is not limited.
In the alternative embodiment of the present invention, backend unit 140 is recorded according to message push order and routing unit 120
Link information, determine at least one when push client and at least one when front end node is pushed, can specifically pass through two
Kind of mode is realized, will be described in detail respectively below.
Mode one, backend unit 140 determines at least one client to be pushed according to message push order, from routing unit
The front end node that at least one client to be pushed respectively connects is searched in the link information of 120 records, is treated as at least one
Push front end node.
In mode one, backend unit 140 can push parsing in order from message and obtain at least one client to be pushed
End；Or
Backend unit 140 can push parsing in order from message and obtain the correlated condition of client to be pushed, advance
Lookup and the matched client of correlated condition in the client side list of structure, as at least one client to be pushed.Here
Correlated condition can be area information, the network type of access, place terminal current state etc., the embodiment of the present invention is to this
It is not restricted.
For example, message push order is " sending message 123 to Chaoyang District Beijing user ", " Chaoyang District Beijing " here is i.e.
For area information, then backend unit 140 can be searched in client side list with " Chaoyang District Beijing " matched client, as
At least one client to be pushed.In another example message push order is " by video push to the user for being currently wifi states ",
Here " wifi states " is the network type accessed, then backend unit 140 can search and " wifi in client side list
The matched client of state ", as at least one client to be pushed.
Mode two, backend unit 140 can push parsing in order from message and obtain at least one front end node to be pushed,
The client that at least one front end node to be pushed respectively connects is searched in the link information recorded from routing unit 120, as
At least one client to be pushed.
In mode two, for example, message push order is the " connections such as front end node A1, A2, A3, A4, A5 to cluster P1
Client push message 234 ", then backend unit 140 parsing in order can be pushed from message and obtains at least one waiting to push
Front end node be " front end node A1, A2, A3, A4, A5 etc. ", then from routing unit 120 record link information in search to
The client that a few front end node to be pushed respectively connects, as at least one client to be pushed.
In the alternative embodiment of the present invention, each front end node in front end unit 110 records itself and client
Link information, then backend unit 140 can also push parsing in order from message and obtain at least one front end node to be pushed,
And directly PUSH message is treated at least one front end node transmission to be pushed, so as to be sent by least one front end node to be pushed
Treat PUSH message to the client of self record.
In the alternative embodiment of the present invention, as shown in Fig. 2, the message push platform 100 of figure 1 above displaying can also wrap
Database broker 210 is included, which is suitable for receiving backend unit 140 according to treating the mark of PUSH message from data
The search request for treating PUSH message accordingly is searched in library 130, is searched in database 130 according to search request and waits to push away accordingly
Message is sent, and is sent to backend unit 140.
Further, database broker 210 is further adapted for waiting to push away accordingly being searched in database 130 according to search request
After sending message, caching treats PUSH message, so that backend unit sends the search request searched and treat PUSH message 140 next time
When, it first searches whether to exist in the message of caching and treats PUSH message, if in the presence of caching directly being treated, PUSH message is sent
To backend unit 140；If being not present, searched in database 130 according to search request and treat PUSH message, and send accordingly
To backend unit 140.In this way, the efficiency of message reading can be improved by way of caching, and database 130 can be mitigated
Access pressure.
In the alternative embodiment of the present invention, front end unit 110 is further adapted for meeting disconnection condition in the connection with client
When, it will be nullified with the link information of client from routing unit 120, so as to which routing unit 120 deletes front end node and client
Between link information.Here disconnection condition can receive the request disconnected or the visitor of client transmission
Family end heartbeat timeout, i.e., for online client, platform is interior at the appointed time does not receive from the client for message push
Any message at end, then it is assumed that the client has gone offline.In this way, routing unit 120 can record the connection letter of real-time update
Breath can improve the accuracy of message push.
In the alternative embodiment of the present invention, backend unit 140 is further adapted for determining at least one according to message push order
It is a after client is pushed, if from routing unit 120 record link information in do not find at least one client to be pushed
One or more of connection front end node, it is determined that one or more client push be in off-line state, thus ought
One or more is searched one or more after push client is reached the standard grade again in the link information recorded from routing unit 120
The front end node that client to be pushed respectively connects treats that PUSH message to one or more is treated by the front end node push found
Client is pushed, wherein, off-line state refers to that front end node is disconnected with client.Here it is possible to by front end unit 110
Whether monitoring one or more client to be pushed reaches the standard grade again, and front end unit 110 monitors one or more client to be pushed
Backend unit 140 is notified when end is reached the standard grade again.In this way, after the embodiment of the present invention still can realize client off-line, again on
Message push during line.
In the alternative embodiment of the present invention, backend unit 140 is further adapted for determining one or more client to be pushed
During in off-line state, establish in one or more clients to be pushed respectively client to be pushed and treat offline between PUSH message
Messaging list, so when one or more wait push client reach the standard grade again after, found from deferred information list and wait to push
Message.
In the alternative embodiment of the present invention, some expired message can also be filtered so that when the message of push meets
Effect property, that is, backend unit 140 is further adapted for treating that PUSH message is waited to push to one or more in the front end node push by finding
Before client, judgement treats whether PUSH message is expired, if without expired, performs push operation；If expired, do not hold
Row push operation.
In the alternative embodiment of the present invention, backend unit 140 is being judged when whether PUSH message is expired, specifically can be with
Be determine one or more wait push client be in off-line state when, will treat PUSH message it is corresponding with expired time preservation,
So as to before PUSH message to one or more client to be pushed is treated in the front end node push by finding, compare preservation
Expired time and current time, judgement treat whether PUSH message is expired.If comparison result is that the expired time preserved is more than current
Time, it is determined that treat that PUSH message is expired；If comparison result, which is the expired time preserved, is less than current time, it is determined that waits to push away
Send message not out of date.
It should be noted that in practical application, combination may be used in above-mentioned all optional embodiments arbitrary group of mode
It closes, forms the alternative embodiment of the present invention, this is no longer going to repeat them.
Based on same inventive concept, the embodiment of the present invention also provides a kind of information push method.Fig. 3 is shown according to this hair
The flow chart of the information push method of the front end unit being applied on message push platform of a bright embodiment.It as shown in figure 3, should
Method may comprise steps of S302 and step S304.
Step S302, in the connection request for receiving client, by the corresponding front end node of connection request and client
Connection is established, and link information is registered to the routing unit on message push platform.
Step S304 when the backend unit transmission on receiving message push platform is when PUSH message, will wait to push
Message pushes to corresponding client.
In embodiments of the present invention, front end unit can be made of one or more front end nodes.In optional embodiment
In, multiple front end nodes can be distributed in one or more server clusters.For example, multiple front end nodes in front end unit are pressed
It is divided into cluster P1, P2, P3 etc. according to different products, P1 includes front end node A1, A2, A3, A4, A5 etc., and P2 includes preceding end segment
Point B1, B2, B3, B4, B5 etc., and so on, i.e.,：
P1 (front end node A1, A2, A3, A4, A5 ...)
P2 (front end node B1, B2, B3, B4, B5 ...)
P3 (front end node C1, C2, C3, C4, C5 ...)
……
Assuming that client a is connected to front end node A1, then the link information is recorded on front end node A1, and connection is believed
Breath is registered to the routing unit on message push platform；Can also similarly grasp similarly, for client b, c, d etc.
Make.It is only illustrative, the embodiment of the present invention is not limited it should be noted that enumerate herein.
In the alternative embodiment of the present invention, each front end node in front end unit can record itself and client
Link information, the routing unit being later registered to link information on message push platform.
In the alternative embodiment of the present invention, front end unit can be incited somebody to action when the connection with client meets disconnection condition
It nullifies from routing unit with the link information of client, believes so as to which routing unit deletes the connection between front end node and client
Breath.Here disconnection condition can be receive client transmission the request disconnected or client heartbeat surpass
When, i.e., for online client, message push platform at the appointed time it is interior do not receive from the client any disappear
Breath, then it is assumed that the client has gone offline.In this way, routing unit can record the link information of real-time update, it can improve and disappear
Cease the accuracy of push.
Fig. 4 shows the message push of the backend unit according to an embodiment of the invention applied on message push platform
The flow chart of method.As shown in figure 4, this method may comprise steps of S402, step S404, step S406 and step
S408。
Step S402 receives the message from push end and pushes order, and parsing message push order obtains treating PUSH message
Mark.
Step S404 is searched from the database on message push platform according to the mark for treating PUSH message and is waited to push away accordingly
Message is sent, wherein, database purchase needs PUSH message and its correspondence between identifying.
Step S406 pushes the link information that the routing unit on platform records according to message push order and message, really
Fixed at least one client push and at least one front end node push, wherein, routing unit record have front end node and
Link information between client.
Step S408 treats PUSH message, so as to wait to push by least one at least one front end node transmission to be pushed
Front end node push treats PUSH message at least one client to be pushed.
The push end referred in above step S402 can be the operators such as business, administrator, and message push order can be with
It is for whole users of single user, batch user or product etc..
In the alternative embodiment of the present invention, the object that message push order is directed to is different, basis in above step S406
Message push order and the link information of the routing unit record on message push platform, determine at least one client to be pushed
It is also different with the mode of at least one front end node to be pushed, it will describe in detail respectively below.
Situation one, when message push order is for single user or batch user, step S406 can be further basis
Message push order determines at least one client to be pushed, and at least one treat is searched in the link information recorded from routing unit
The front end node that push client respectively connects, as at least one front end node to be pushed.
In an alternate embodiment of the invention, at least one when client is pushed, Ke Yishi is being determined according to message push order
Parsing obtains at least one client to be pushed or parses from message push order to obtain from message push order
The correlated condition of client to be pushed is searched and the matched client of correlated condition, work in the client side list built in advance
For at least one client to be pushed.Here correlated condition can be area information, the network type of access, place terminal
Current state etc., the embodiment of the present invention are not restricted this.
For example, message push order is " sending message 123 to Chaoyang District Beijing user ", " Chaoyang District Beijing " here is i.e.
For area information, then can be searched in client side list with " Chaoyang District Beijing " matched client, treated as at least one
Push client.In another example message push order is " by video push to the user for being currently wifi states ", here
" wifi states " is the network type accessed, then can be searched in client side list and " wifi states " matched client
End, as at least one client to be pushed.
Situation two, when message push order is directed to whole users of product, step S406 can be pushed away from message
Parsing in enabling of losing one's life obtains at least one front end node to be pushed, and is searched in the link information recorded from routing unit at least one
The client that front end node to be pushed respectively connects, as at least one client to be pushed.
For example, message push order is " client of the connections such as front end node A1, A2, A3, A4, A5 to cluster P1 pushes away
Send message 234 ", then can from message push order in parsing obtain at least one front end node push be " front end node A1,
A2, A3, A4, A5 etc. " then searches at least one front end node to be pushed from the link information that routing unit records and respectively connects
The client connect, as at least one client to be pushed.
In the alternative embodiment of the present invention, each front end node in front end unit records the connection of itself and client
Information, then step S406 can be further that parsing obtains at least one front end node to be pushed from message push order, and
Directly PUSH message is treated at least one front end node transmission to be pushed, so as to be treated by least one front end node transmission to be pushed
PUSH message to self record client.
It is searched accordingly from the database on message push platform according to the mark for treating PUSH message in above step S404
Treat PUSH message, can push platform to message in this scenario an embodiment of the present invention provides a kind of optional scheme
On database broker send and the corresponding lookup for treating PUSH message is searched from database according to the mark for treating PUSH message ask
Ask, so receive database broker return treat PUSH message.
Further, database broker searched in the database according to search request it is corresponding treat PUSH message after,
Caching treats PUSH message, so that backend unit sends lookup when the search request of PUSH message next time, first disappearing in caching
It searches whether to exist in breath and treats PUSH message, if in the presence of caching directly being treated, PUSH message is sent to backend unit；If no
In the presence of then being searched in the database according to search request and treat PUSH message, and be sent to backend unit accordingly.In this way, pass through
The mode of caching can improve the efficiency of message reading, and can mitigate the access pressure of database.
In the alternative embodiment of the present invention, after can also realizing client off-line, message push when reaching the standard grade again.Tool
Body, it is determining at least one after client is pushed being ordered according to message push, if the link information recorded from routing unit
In do not find one or more of at least one client to be pushed connection front end node, it is determined that one or more is treated
Push client is in off-line state, thus when one or more is after push client is reached the standard grade again, is recorded from routing unit
Link information in search the front end node that one or more clients to be pushed respectively connect, pushed away by the front end node found
It send and treats PUSH message to one or more client to be pushed, wherein, off-line state refers to that front end node is disconnected with client and connects
It connects.
In the alternative embodiment of the present invention, determining that one or more, can when push client is in off-line state
To establish in one or more clients to be pushed respectively client to be pushed and treat the deferred information list between PUSH message, and then
When one or more wait push client reach the standard grade again after, found from deferred information list and treat PUSH message.
In the alternative embodiment of the present invention, some expired message can also be filtered so that when the message of push meets
Effect property specifically, before PUSH message to one or more client to be pushed is treated in the front end node push by finding, is sentenced
It is disconnected to treat whether PUSH message is expired, if without expired, perform push operation；If expired, push operation is not performed.
In the alternative embodiment of the present invention, judging when whether PUSH message is expired, can be specifically to determine one
It is a or multiple when push client is in off-line state, it will treat that PUSH message is corresponding with expired time and preserve, so as to by looking into
Find front end node push treat PUSH message to one or more client push before, compare preservation expired time and
Current time, judgement treat whether PUSH message is expired.If comparison result is that the expired time preserved is more than current time, it is determined that
Treat that PUSH message is expired；If comparison result, which is the expired time preserved, is less than current time, it is determined that treats the non-mistake of PUSH message
Phase.
According to the combination of any one above-mentioned alternative embodiment or multiple alternative embodiments, the embodiment of the present invention can reach
Following advantageous effect：
Message provided in an embodiment of the present invention pushes platform, it include front end unit, routing unit, database and after
End unit, specifically, front end unit are made of one or more front end nodes, suitable in the connection request for receiving client
When, it is established and connected, and link information is registered to routing unit by the corresponding front end node of connection request and client；Routing is single
Member, suitable for the link information between record front end node and client；Database treats PUSH message and between it identifies suitable for storage
Correspondence；And backend unit, order is pushed suitable for receiving the message from push end, parsing message push order obtains
Treat the mark of PUSH message, according to the mark for treating PUSH message searched from database it is corresponding treat PUSH message and according to
Message push order and the link information of routing unit record, determine at least one client to be pushed and at least one wait to push
Front end node treats PUSH message, so as to by least one front end node to be pushed at least one front end node transmission to be pushed
Push treats PUSH message at least one client to be pushed.It follows that message push platform provided in an embodiment of the present invention
By the PUSH message that cooperates between front end unit, routing unit, database and backend unit, Partition of role is bright
Really, it is easy to accomplish and O＆M dilatation, efficiency and accuracy that message pushes can be improved.Also, the embodiment of the present invention is by front end
Dynamic link information is extracted from front end unit, database and backend unit between node and client, by routing unit Lai
Record in real time, can effectively reduce the access pressure of database and front end unit, the load of backend unit.
In the specification provided in this place, numerous specific details are set forth.It is to be appreciated, however, that the implementation of the present invention
Example can be put into practice without these specific details.In some instances, well known method, structure is not been shown in detail
And technology, so as not to obscure the understanding of this description.
Similarly, it should be understood that in order to simplify the disclosure and help to understand one or more of each inventive aspect,
Above in the description of exemplary embodiment of the present invention, each feature of the invention is grouped together into single implementation sometimes
In example, figure or descriptions thereof.However, the method for the disclosure should be construed to reflect following intention：I.e. required guarantor
Shield the present invention claims the more features of feature than being expressly recited in each claim.More precisely, as following
Claims reflect as, inventive aspect is all features less than single embodiment disclosed above.Therefore,
Thus the claims for following specific embodiment are expressly incorporated in the specific embodiment, wherein each claim is in itself
Separate embodiments all as the present invention.
Those skilled in the art, which are appreciated that, to carry out adaptively the module in the equipment in embodiment
Change and they are arranged in one or more equipment different from the embodiment.It can be the module or list in embodiment
Member or component be combined into a module or unit or component and can be divided into addition multiple submodule or subelement or
Sub-component.Other than such feature and/or at least some of process or unit exclude each other, it may be used any
Combination is disclosed to all features disclosed in this specification (including adjoint claim, abstract and attached drawing) and so to appoint
Where all processes or unit of method or equipment are combined.Unless expressly stated otherwise, this specification is (including adjoint power
Profit requirement, abstract and attached drawing) disclosed in each feature can be by providing the alternative features of identical, equivalent or similar purpose come generation
It replaces.
In addition, it will be appreciated by those of skill in the art that although some embodiments described herein include other embodiments
In included certain features rather than other feature, but the combination of the feature of different embodiments means in of the invention
Within the scope of and form different embodiments.For example, in detail in the claims, embodiment claimed it is one of arbitrary
It mode can use in any combination.
The all parts embodiment of the present invention can be with hardware realization or to be run on one or more processor
Software module realize or realized with combination thereof.It will be understood by those of skill in the art that it can use in practice
Microprocessor or digital signal processor (DSP) come realize in message push platform according to embodiments of the present invention some or
The some or all functions of person's whole component.The present invention is also implemented as perform method as described herein one
Divide either whole equipment or program of device (for example, computer program and computer program product).Such this hair of realization
Bright program can may be stored on the computer-readable medium or can have the form of one or more signal.It is such
Signal can be downloaded from internet website to be obtained either providing on carrier signal or providing in the form of any other.
It should be noted that the present invention will be described rather than limits the invention, and ability for above-described embodiment
Field technique personnel can design alternative embodiment without departing from the scope of the appended claims.In the claims,
Any reference mark between bracket should not be configured to limitations on claims.Word "comprising" does not exclude the presence of not
Element or step listed in the claims.Word "a" or "an" before element does not exclude the presence of multiple such
Element.The present invention can be by means of including the hardware of several different elements and being come by means of properly programmed computer real
It is existing.If in the unit claim for listing equipment for drying, several in these devices can be by same hardware branch
To embody.The use of word first, second, and third does not indicate that any sequence.These words can be explained and run after fame
Claim.
So far, although those skilled in the art will appreciate that detailed herein have shown and described multiple showing for the present invention
Example property embodiment, still, without departing from the spirit and scope of the present invention, still can according to the present disclosure directly
Determine or derive many other variations or modifications consistent with the principles of the invention.Therefore, the scope of the present invention is understood that and recognizes
It is set to and covers other all these variations or modifications.
One side according to embodiments of the present invention provides a kind of message push platforms of a1., including：Front end unit, routing
Unit, database and backend unit；
The front end unit is made of one or more front end nodes, suitable in the connection request for receiving client,
It is established and connected, and link information is registered to the routing unit by the corresponding front end node of the connection request and client；
The routing unit, suitable for the link information between record front end node and client；
The database treats PUSH message and its correspondence between identifying suitable for storage；And
The backend unit pushes order suitable for receiving the message from push end, parses the message push and orders
To the mark for treating PUSH message, searched from the database according to the mark for treating PUSH message and treat that push disappears accordingly
Breath and according to the message push order and the routing unit record link information, determine it is at least one treat push visitor
Family end and at least one front end node to be pushed treat PUSH message to described at least one front end node transmission to be pushed,
So as to treat PUSH message at least one client to be pushed as described at least one front end node push to be pushed.
A2. the message push platform according to a1, wherein, the backend unit is further adapted for：
At least one client to be pushed is determined according to message push order, is recorded from the routing unit
The front end node that at least one client to be pushed respectively connects is searched in link information, at least one waits to push away as described
Send front end node.
A3. the message push platform according to a2, wherein, the backend unit is further adapted for：
Parsing obtains at least one client to be pushed from message push order；Or
Parsing obtains the correlated condition of client to be pushed from message push order, in the client built in advance
Lookup and the matched client of the correlated condition in list, as at least one client to be pushed.
A4. the message push platform according to a3, wherein, the correlated condition includes at least one following：
Area information, access network type, place terminal current state.
A5. the message push platform according to a1, wherein, the backend unit is further adapted for：
Parsing obtains at least one front end node to be pushed from message push order, from the routing unit
The client that at least one front end node to be pushed respectively connects is searched in the link information of record, as described at least one
A client to be pushed.
A6. the message push platform according to a1, wherein, each front end node in the front end unit records itself
With the link information of client.
A7. the message push platform according to a6, wherein, the backend unit is further adapted for：
Parsing obtains at least one front end node to be pushed from message push order, to described at least one
Front end node to be pushed treats PUSH message described in sending, so as to wait to push away as described at least one front end node transmission to be pushed
Message is sent to the client of self record.
A8. the message push platform according to any one of a1-a7, wherein, the multiple front end node is distributed in one
A or multiple server clusters.
A9. the message push platform according to any one of a1-a8, wherein, it further includes：
Database broker treats the mark of PUSH message from the database suitable for receiving the backend unit according to
The search request for treating PUSH message accordingly is searched, is searched in the database according to the search request and waits to push accordingly
Message, and it is sent to the backend unit.
A10. the message push platform according to a9, wherein, the database broker is further adapted for：
Searched in the database according to the search request it is corresponding treat PUSH message after, wait to push away described in caching
Message is sent, is searched when the search request of PUSH message so that the backend unit next time sends, first in the message of caching
It searches whether to exist and treats PUSH message, if in the presence of caching directly being treated, PUSH message is sent to the backend unit；If no
In the presence of then being searched in the database according to the search request and treat PUSH message accordingly, and it is single to be sent to the rear end
Member.
A11. the message push platform according to any one of a1-a10, wherein, the front end unit is further adapted for：
When the connection with client meets disconnection condition, will be noted with the link information of client from the routing unit
Pin, so as to which the routing unit deletes the link information between front end node and client.
A12. the message push platform according to a11, wherein, the disconnection condition includes at least one following：
Receive the request disconnected of client transmission；
Client heartbeat timeout.
A13. the message push platform according to a11, wherein, the backend unit is further adapted for：
It is determining described at least one after client is pushed being ordered according to message push, if from the routing unit
The front end node of one or more of described at least one client to be pushed connection is not found in the link information of record,
Then determine that one or more of clients to be pushed are in off-line state, thus ought one or more of clients to be pushed
Again after reaching the standard grade, in the link information recorded from the routing unit one or more of clients to be pushed are searched respectively to connect
The front end node connect treats PUSH message to one or more of clients to be pushed as described in the front end node push found
End, wherein, the off-line state refers to that front end node is disconnected with client.
A14. the message push platform according to a13, wherein, the backend unit is further adapted for：
It is determining one or more of when pushing client and being in off-line state, is establishing and one or more of wait to push away
Send respectively client to be pushed and the deferred information list treated between PUSH message in client；
When one or more of after push client is reached the standard grade again, found from the deferred information list described
Treat PUSH message.
A15. the message push platform according to a13, wherein, the backend unit is further adapted for：
As find front end node push described in treat PUSH message to one or more of clients to be pushed it
Before, it treats whether PUSH message is expired described in judgement, if without expired, performs push operation；If expired, do not perform and push away
Send operation.
A16. the message push platform according to a15, wherein, the backend unit is further adapted for：
Determine it is one or more of wait push client be in off-line state when, by it is described treat PUSH message with it is expired
Time, which corresponds to, to be preserved, so as to treat that PUSH message is waited to push to one or more of as described in the front end node push found
Before client, the expired time and current time of preservation are compared, treats whether PUSH message is expired described in judgement.
Another aspect according to embodiments of the present invention additionally provides a kind of information push methods of b17., is pushed away applied to message
The front end unit on platform is sent, the front end unit is made of one or more front end nodes, including：
In the connection request for receiving client, established and connected by the corresponding front end node of the connection request and client
It connects, and link information is registered to the routing unit on the message push platform；And
When the backend unit transmission on receiving the message push platform is when PUSH message, treat that push disappears by described
Breath pushes to corresponding client.
B18. the information push method according to b17, wherein, each front end node record in the front end unit is certainly
The link information of body and client.
B19. the information push method according to b17 or b18, wherein, the multiple front end node be distributed in one or
Multiple server clusters.
B20. the information push method according to any one of b17-b19, wherein, it further includes：
When the connection with client meets disconnection condition, will be noted with the link information of client from the routing unit
Pin, so as to which the routing unit deletes the link information between front end node and client.
B21. the information push method according to b20, wherein, the disconnection condition includes at least one following：
Receive the request disconnected of client transmission；
Client heartbeat timeout.
Another aspect according to embodiments of the present invention, additionally provides a kind of information push methods of c22., is pushed away applied to message
The backend unit on platform is sent, including：
It receives the message from push end and pushes order, parse the mark that the message push order obtains treating PUSH message
Know；
It is searched from the database on message push platform according to the mark for treating PUSH message and waits to push away accordingly
Message is sent, wherein, the database purchase needs PUSH message and its correspondence between identifying；
According to the link information that the routing unit in message push order and message push platform records, determine
At least one client to be pushed and at least one front end node to be pushed, wherein, the routing unit record has front end node
Link information between client；And
To at least one front end node to be pushed send described in treat PUSH message, so as at least one wait to push away by described
Send treats PUSH message at least one client to be pushed described in front end node push.
C23. the information push method according to c22, wherein, it is described according to message push order and the message
The link information of the routing unit record on platform is pushed, at least one client to be pushed is determined and at least one waits before pushing
The step of end node, further comprises：
At least one client to be pushed is determined according to message push order, is recorded from the routing unit
The front end node that at least one client to be pushed respectively connects is searched in link information, at least one waits to push away as described
Send front end node.
C24. the information push method according to c23, wherein, it is described according to the message push order determine described in extremely
The step of few client to be pushed, further comprises：
Parsing obtains at least one client to be pushed from message push order；Or
Parsing obtains the correlated condition of client to be pushed from message push order, in the client built in advance
Lookup and the matched client of the correlated condition in list, as at least one client to be pushed.
C25. the information push method according to c24, wherein, the correlated condition includes at least one following：
Area information, access network type, place terminal current state.
C26. the information push method according to c22, wherein, it is described according to message push order and the message
The link information of the routing unit record on platform is pushed, at least one client to be pushed is determined and at least one waits before pushing
The step of end node, further comprises：
Parsing obtains at least one front end node to be pushed from message push order, from the routing unit
The client that at least one front end node to be pushed respectively connects is searched in the link information of record, as described at least one
A client to be pushed.
C27. the information push method according to c22, wherein, each front end node record in the front end unit is certainly
The link information of body and client, the routing unit according in message push order and message push platform are remembered
The link information of record, the step of determining at least one client to be pushed and at least one front end node to be pushed, further wrap
It includes：
Parsing obtains at least one front end node to be pushed from message push order, to described at least one
Front end node to be pushed treats PUSH message described in sending, so as to wait to push away as described at least one front end node transmission to be pushed
Message is sent to the client of self record.
C28. the information push method according to any one of c22-c27, wherein, treat PUSH message described in the basis
Mark from the message push platform on database in search accordingly treat PUSH message the step of further comprise：
Database broker on message push platform is sent treats the mark of PUSH message from the number according to
Treat the search request of PUSH message accordingly according to lookup in library；
It receives the described of database broker return and treats PUSH message.
C29. the information push method according to c28, wherein, the database broker exists according to the search request
It is searched in the database after treating PUSH message accordingly, PUSH message is treated described in caching, so that under the backend unit
Secondary send is searched when the search request of PUSH message, is first searched whether to exist in the message of caching and is treated PUSH message, if depositing
Caching is directly then being treated that PUSH message is sent to the backend unit；If being not present, according to the search request in institute
It states to search in database and treats PUSH message, and be sent to the backend unit accordingly.
C30. the information push method according to c23, wherein, it further includes：
It is determining described at least one after client is pushed being ordered according to message push, if from the routing unit
The front end node of one or more of described at least one client to be pushed connection is not found in the link information of record,
Then determine that one or more of clients to be pushed are in off-line state, thus ought one or more of clients to be pushed
Again after reaching the standard grade, in the link information recorded from the routing unit one or more of clients to be pushed are searched respectively to connect
The front end node connect treats PUSH message to one or more of clients to be pushed as described in the front end node push found
End, wherein, the off-line state refers to that front end node is disconnected with client.
C31. the information push method according to c30, wherein, it further includes：
It is determining one or more of when pushing client and being in off-line state, is establishing and one or more of wait to push away
Send respectively client to be pushed and the deferred information list treated between PUSH message in client；
When one or more of after push client is reached the standard grade again, found from the deferred information list described
Treat PUSH message.
C32. the information push method according to c30, wherein, it further includes：
As find front end node push described in treat PUSH message to one or more of clients to be pushed it
Before, it treats whether PUSH message is expired described in judgement, if without expired, performs push operation；If expired, do not perform and push away
Send operation.
C33. the information push method according to c32, wherein, it further includes：
Determine it is one or more of wait push client be in off-line state when, by it is described treat PUSH message with it is expired
Time, which corresponds to, to be preserved, so as to treat that PUSH message is waited to push to one or more of as described in the front end node push found
Before client, the expired time and current time of preservation are compared, treats whether PUSH message is expired described in judgement.
Claims (10)
1. a kind of message pushes platform, including：Front end unit, routing unit, database and backend unit；
The front end unit is made of one or more front end nodes, suitable in the connection request for receiving client, by institute
It states the corresponding front end node of connection request and establishes connection, and link information is registered to the routing unit with client；
The routing unit, suitable for the link information between record front end node and client；
The database treats PUSH message and its correspondence between identifying suitable for storage；And
The backend unit pushes order suitable for receiving the message from push end, parses the message push order and is treated
The mark of PUSH message searches from the database according to the mark for treating PUSH message and treats PUSH message accordingly, with
And according to the message push order and the routing unit record link information, determine at least one client push with
At least one front end node to be pushed treats PUSH message to described at least one front end node transmission to be pushed, thus by
Treat PUSH message at least one client to be pushed described at least one front end node push to be pushed.
2. message according to claim 1 pushes platform, wherein, the backend unit is further adapted for：
At least one client to be pushed is determined according to message push order, the connection recorded from the routing unit
The front end node that at least one client to be pushed respectively connects is searched in information, at least one is waited before pushing as described
End node.
3. message according to claim 2 pushes platform, wherein, the backend unit is further adapted for：
Parsing obtains at least one client to be pushed from message push order；Or
Parsing obtains the correlated condition of client to be pushed from message push order, in the client side list built in advance
Middle lookup and the matched client of the correlated condition, as at least one client to be pushed.
4. message according to claim 3 pushes platform, wherein, the correlated condition includes at least one following：
Area information, access network type, place terminal current state.
5. message according to claim 1 pushes platform, wherein, the backend unit is further adapted for：
Parsing obtains at least one front end node to be pushed from message push order, is recorded from the routing unit
Link information in search the client that at least one front end node to be pushed respectively connects, at least one treated as described
Push client.
6. message according to claim 1 pushes platform, wherein, each front end node record in the front end unit is certainly
The link information of body and client.
7. message according to claim 6 pushes platform, wherein, the backend unit is further adapted for：
Parsing obtains at least one front end node to be pushed from message push order, at least one waits to push away to described
It send and treats PUSH message described in front end node transmission, so as to treat that push disappears as described at least one front end node transmission to be pushed
It ceases to the client of self record.
8. the message push platform according to any one of claim 1-7, wherein, the multiple front end node is distributed in one
A or multiple server clusters.
9. a kind of information push method, applied to the front end unit on message push platform, the front end unit is by one or more
A front end node is formed, including：
In the connection request for receiving client, established and connected by the corresponding front end node of the connection request and client,
And link information is registered to the routing unit on the message push platform；And
When the backend unit transmission on receiving the message push platform is when PUSH message, treat that PUSH message pushes away by described
It send to corresponding client.
10. a kind of information push method pushes the backend unit on platform applied to message, including：
It receives the message from push end and pushes order, parse the mark that the message push order obtains treating PUSH message；
It is searched from the database on message push platform according to the mark for treating PUSH message and treats that push disappears accordingly
Breath, wherein, the database purchase needs PUSH message and its correspondence between identifying；
According to the link information that the routing unit in message push order and message push platform records, determine at least
One client to be pushed and at least one front end node to be pushed, wherein, the routing unit record has front end node and visitor
Link information between the end of family；And
To at least one front end node to be pushed send described in treat PUSH message, so as at least one be waited before pushing by described
Treat PUSH message at least one client to be pushed described in end node push.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711480979.7A CN108234631B (en) | 2017-12-29 | 2017-12-29 | Message pushing platform and message pushing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711480979.7A CN108234631B (en) | 2017-12-29 | 2017-12-29 | Message pushing platform and message pushing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108234631A true CN108234631A (en) | 2018-06-29 |
| CN108234631B CN108234631B (en) | 2021-06-15 |
Family
ID=62646291
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711480979.7A Active CN108234631B (en) | 2017-12-29 | 2017-12-29 | Message pushing platform and message pushing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108234631B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109376316A (en) * | 2018-11-05 | 2019-02-22 | 珠海格力电器股份有限公司 | Method, system and the server of dynamically load routing |
| CN112468600A (en) * | 2021-02-02 | 2021-03-09 | 上海有孚智数云创数字科技有限公司 | Application message notification method, system and storage medium based on network matrix |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070016663A1 (en) * | 2005-07-14 | 2007-01-18 | Brian Weis | Approach for managing state information by a group of servers that services a group of clients |
| CN103327039A (en) * | 2012-03-20 | 2013-09-25 | 腾讯科技（深圳）有限公司 | Method and device and system for pushing messages |
| CN104980289A (en) * | 2014-04-14 | 2015-10-14 | 阿里巴巴集团控股有限公司 | Message pushing method, device and system |
| CN107395767A (en) * | 2017-08-31 | 2017-11-24 | 北京奇虎科技有限公司 | Message push system and method based on long connection |
-
2017
- 2017-12-29 CN CN201711480979.7A patent/CN108234631B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070016663A1 (en) * | 2005-07-14 | 2007-01-18 | Brian Weis | Approach for managing state information by a group of servers that services a group of clients |
| CN103327039A (en) * | 2012-03-20 | 2013-09-25 | 腾讯科技（深圳）有限公司 | Method and device and system for pushing messages |
| CN104980289A (en) * | 2014-04-14 | 2015-10-14 | 阿里巴巴集团控股有限公司 | Message pushing method, device and system |
| CN107395767A (en) * | 2017-08-31 | 2017-11-24 | 北京奇虎科技有限公司 | Message push system and method based on long connection |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109376316A (en) * | 2018-11-05 | 2019-02-22 | 珠海格力电器股份有限公司 | Method, system and the server of dynamically load routing |
| CN109376316B (en) * | 2018-11-05 | 2020-10-16 | 珠海格力电器股份有限公司 | Method, system and server for dynamically loading route |
| CN112468600A (en) * | 2021-02-02 | 2021-03-09 | 上海有孚智数云创数字科技有限公司 | Application message notification method, system and storage medium based on network matrix |
| CN112468600B (en) * | 2021-02-02 | 2021-04-06 | 上海有孚智数云创数字科技有限公司 | Application message notification method, system and storage medium based on network matrix |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108234631B (en) | 2021-06-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10417066B2 (en) | Adapting legacy endpoints to modern APIs | |
| CN107885187A (en) | A kind of automobile remote diagnostic method, user terminal and server | |
| CN103685603B (en) | Domain name system resolution and equipment | |
| CN108199921A (en) | The method, apparatus and storage medium of a kind of simulation test | |
| CN109729131A (en) | A kind of processing method of application request, device and router | |
| CN107181804B (en) | The method for down loading and device of resource | |
| CN107995304A (en) | A kind of session keeping method and device based on cookie | |
| US9838499B2 (en) | Methods and systems for application controlled pre-fetch | |
| JP2007156569A (en) | Cluster system, load balancer, method of transferring node, and node transfer program | |
| CN106101290A (en) | A kind of method and system of server cluster management | |
| CN108234631A (en) | Message pushes platform and information push method | |
| CN108156274A (en) | Equipment is made to obtain the method and device of domain name mapping result in a kind of VPN network | |
| US20100125640A1 (en) | Traffic Management Apparatus | |
| JP2013015991A (en) | Information processor, server selection method, and program | |
| CN104519138B (en) | A kind of data transmission method and system based on distributed FTP | |
| US20190370293A1 (en) | Method and apparatus for processing information | |
| CN113765774B (en) | Method, device, electronic equipment and medium for synchronizing messages in real time | |
| CN109615393A (en) | The follow-up processing method and processing device of breakpoint | |
| CN104994088B (en) | Data verification method, client, server-side based on WiFi connections and system | |
| CN105577707B (en) | A kind of remote invocation method and equipment | |
| CN104899515B (en) | A kind of variation and device of applications security | |
| CN101500005B (en) | Method for access to equipment on server based on iSCSI protocol | |
| CN112838935A (en) | Electronic data exchange method and system | |
| JP6605149B2 (en) | Method and apparatus for detecting shared terminal | |
| CN108932329A (en) | A kind of data query processing method and processing device |
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 |