CN105227595A - A kind of message method and equipment - Google Patents
A kind of message method and equipment Download PDFInfo
- Publication number
- CN105227595A CN105227595A CN201410253563.1A CN201410253563A CN105227595A CN 105227595 A CN105227595 A CN 105227595A CN 201410253563 A CN201410253563 A CN 201410253563A CN 105227595 A CN105227595 A CN 105227595A
- Authority
- CN
- China
- Prior art keywords
- message
- user
- sendaisle
- push
- content
- 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
Abstract
This application discloses a kind of message method and equipment, the method comprises: push server obtains to be waited to push content; For multiple message sendaisle, described push server obtains the at the appointed time interior login probability of each message sendaisle, and determines to log in the highest message sendaisle of probability; Wait to push the message of content described in described push server utilizes the highest message sendaisle of described login probability to send to carry.In the embodiment of the present application, can improve and push the probability of context notification to user by waiting, and the waste causing system resource and Internet resources can be avoided, save system resource and Internet resources, and can avoid causing harassing and wrecking to user, thus the use sense improving user is subject to.
Description
Technical field
The application relates to Internet technical field, especially relate to a kind of message method and equipment.
Background technology
In prior art, when needs will in time pushing content (as: market content or product information etc.) and inform to user, service server can send by a particular message sendaisle message carrying and wait to push content to subscriber equipment.But, when service server sends message by a particular message sendaisle to subscriber equipment, cannot ensure that this message is bound to be sent on subscriber equipment, thus cause to push context notification to user by waiting, then directly have influence on development and the popularization of business.
In order to wait to push context notification to user, need to ensure to be sent to carrying the message waiting to push content on subscriber equipment.Based on this, in prior art, service server needs to send by multiple message sendaisle the message carrying and wait to push content to subscriber equipment simultaneously, thus ensures to push context notification to user by waiting.But, when service server sends message by multiple message sendaisle to subscriber equipment simultaneously, the waste of system resource and Internet resources can be caused, and subscriber equipment receive multiple carry identical in time pushing the message of content, user also can be made to have by harassing and wrecking sense, affect user's use sense and be subject to.
Summary of the invention
The embodiment of the present application provides a kind of message method and equipment, will wait to push context notification to user, and avoid the waste causing system resource and Internet resources, and the use sense improving user is subject to.
For achieving the above object, the embodiment of the present application provides a kind of message method, and described method comprises:
Push server obtains to be waited to push content;
For multiple message sendaisle, described push server obtains the at the appointed time interior login probability of each message sendaisle, and determines to log in the highest message sendaisle of probability;
Wait to push the message of content described in described push server utilizes the highest message sendaisle of described login probability to send to carry.
Described push server obtains to be waited to push content, specifically comprises:
Send at needs in time pushing content to user, described push server receives the message from waiting to push content described in the carrying of service server, and waits described in obtaining from described message to push content.
Wait to push the message of content described in described push server utilizes the highest message sendaisle of described login probability to send to carry, also comprise before:
Described push server judges whether the highest login probability is greater than default value; If so, then described push server perform utilize the highest message sendaisle of described login probability to send to carry described in wait the process of the message pushing content; If not, then described push server determination particular message sendaisle, and wait to push the message of content described in utilizing described particular message sendaisle to send to carry.
Before described push server obtains the at the appointed time interior login probability of each message sendaisle, described method also comprises:
Send at needs in time pushing content to user, described push server obtains the user ID of described user in multiple message sendaisle difference correspondence;
For each message sendaisle, described push server utilizes described user to inquire about described user in the user ID that message sendaisle is corresponding and whether be in logging status under described message sendaisle;
If described user is and is not in logging status under all message sendaisles, then described push server perform obtain each message sendaisle at the appointed time in login probability, and utilize log in the highest message sendaisle of probability send carry described in wait the process of the message pushing content.
Described push server utilizes described user to inquire about after whether described user be in logging status under described message sendaisle in the user ID that message sendaisle is corresponding, and described method also comprises:
If described user is only in logging status under a message sendaisle, then described push server by this message sendaisle send carry described in wait to push the message of content;
If described user is in logging status under multiple message sendaisle, then described push server utilizes and presets selection strategy selects a message sendaisle from described multiple message sendaisle, and treats the message of propelling movement content described in utilizing this selection message sendaisle to send to carry.
Described push server obtains the process of described user in the user ID of multiple message sendaisle difference correspondence, specifically comprises:
Described push server receives the message carrying user profile from service server;
When described user profile is user in the user ID that multiple message sendaisle is corresponding respectively, described push server obtains described user in the corresponding respectively user ID of multiple message sendaisle from the message from described service server; Or when described user profile is user name, described push server inquires about the user ID list item of local maintenance by described user name, to obtain the user ID of described user in multiple message sendaisle difference correspondence; Wherein, described user ID list item is used for recording user name and the corresponding relation of user between the user ID that multiple message sendaisle is corresponding respectively.
For each message sendaisle, described push server utilizes described user to inquire about in the user ID that message sendaisle is corresponding the process whether described user is in logging status under described message sendaisle, specifically comprises:
Described push server sends to application server corresponding to message sendaisle and carries the request message of user in user ID corresponding to described message sendaisle, utilizes described user ID to inquire about described user whether be in logging status by described application server under described message sendaisle;
Described push server receives and carries from described application server the response message that described user is in logging status or is not in logging status under described message sendaisle;
By the information of carrying in described response message, described push server determines that described user is in logging status or is not in logging status under described message sendaisle under described message sendaisle.
Wait the process of the message pushing content described in described push server is carried by the transmission of message sendaisle, specifically comprise:
Described push server generates each application server source template corresponding respectively, and the source template that each application server is corresponding is respectively sent to described each application server respectively;
Described in being carried by the transmission of message sendaisle in time pushing the message of content, by described, described push server waits that pushing content sends to the application server that described message sendaisle is corresponding, utilize source template and described waiting to push content generating messages by described application server, and send described message.
The embodiment of the present application provides a kind of push server, and described Push Service implement body comprises:
Obtaining module, waiting to push content for obtaining;
Determination module, for for multiple message sendaisle, obtains the login probability that each message sendaisle is at the appointed time interior, and determines to log in the highest message sendaisle of probability;
Sending module, sends the message waiting to push content described in carrying for utilizing the highest message sendaisle of described login probability.
Described acquisition module, specifically for sending in time pushing content to user at needs, receiving and waiting to push the message of content from carrying of service server, and waiting described in obtaining from described message to push content.
Described sending module, is further used for judging whether the highest login probability is greater than default value;
If so, then perform utilize the highest message sendaisle of described login probability to send to carry described in wait to push the process of message of content; If not, then determine particular message sendaisle, and wait to push the message of content described in utilizing described particular message sendaisle to send to carry.
Described acquisition module, also for sending in time pushing content to user at needs, obtains the user ID of described user in multiple message sendaisle difference correspondence;
Described determination module, also for for each message sendaisle, utilizes described user under described message sendaisle, whether to be in logging status at the user ID inquiring user that message sendaisle is corresponding;
Described sending module, if be further used for described user to be under all message sendaisles and not to be in logging status, then execution obtains the at the appointed time interior login probability of each message sendaisle, waits the process of the message pushing content described in the message sendaisle transmission utilizing login probability the highest carries.
Described sending module, if be also only in logging status under a message sendaisle for described user, then waits to push the message of content described in being carried by this message sendaisle transmission;
If described user is in logging status under multiple message sendaisle, then utilize and preset selection strategy selects a message sendaisle from described multiple message sendaisle, and treat the message of propelling movement content described in utilizing this selection message sendaisle to send to carry.
Described acquisition module, specifically for receiving the message carrying user profile from service server;
When described user profile is user in the user ID that multiple message sendaisle is corresponding respectively, from the message from described service server, obtain described user in the corresponding respectively user ID of multiple message sendaisle; Or, when described user profile is user name, inquired about the user ID list item of described push server local maintenance by described user name, to obtain the user ID of described user in multiple message sendaisle difference correspondence; Wherein, described user ID list item is used for recording user name and the corresponding relation of user between the user ID that multiple message sendaisle is corresponding respectively.
Described determination module, carrying the request message of user in user ID corresponding to described message sendaisle specifically for sending to application server corresponding to message sendaisle, utilizing described user ID to inquire about described user by described application server and whether being in logging status under described message sendaisle;
Receive and carry from described application server the response message that described user is in logging status or is not in logging status under described message sendaisle;
Determine that described user is in logging status or is not in logging status under described message sendaisle under described message sendaisle by the information of carrying in described response message.
Described sending module, is further used for generating each application server source template corresponding respectively, and the source template that each application server is corresponding is respectively sent to described each application server respectively;
Described in being carried by the transmission of message sendaisle in time pushing the message of content, wait that pushing content sends to the application server that described message sendaisle is corresponding by described, utilize source template and described waiting to push content generating messages by described application server, and send described message.
Compared with prior art, the embodiment of the present application at least has the following advantages: in the embodiment of the present application, the message of carrying and waiting to push content can be sent to subscriber equipment by logging in the highest message sendaisle of probability, thus will wait to push context notification to user as far as possible, improve and push the probability of context notification to user by waiting, and the waste causing system resource and Internet resources can be avoided, save system resource and Internet resources, and can avoid causing harassing and wrecking to user, thus the use sense improving user is subject to.
Accompanying drawing explanation
In order to be illustrated more clearly in the technical scheme of the embodiment of the present application, below the accompanying drawing used required in describing the embodiment of the present application is briefly described, apparently, accompanying drawing in the following describes is only some embodiments of the application, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings of the embodiment of the present application.
Fig. 1 is the application scenarios schematic diagram that the embodiment of the present application one proposes;
Fig. 2 is a kind of message method schematic flow sheet that the embodiment of the present application one proposes;
Fig. 3 is the structural representation of a kind of push server that the embodiment of the present application two proposes.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present application, be clearly and completely described the technical scheme in the application, obviously, described embodiment is only a part of embodiment of the application, instead of whole embodiments.Based on the embodiment in the application, those of ordinary skill in the art are not making the every other embodiment obtained under creative work prerequisite, all belong to the scope of the application's protection.
Embodiment one
For problems of the prior art, the embodiment of the present application one proposes a kind of message method, take Fig. 1 as the application scenarios schematic diagram of the embodiment of the present application, this message method is applied in the system comprising push server, service server and application server.Push server is the server for decision information sendaisle (sendaisle also can be described as channel) that the embodiment of the present application proposes, service server is need to push content to need to send to the server of user, application server is the server of each application correspondence, the server etc. that server as corresponding in mail, the server of micro-letter correspondence, note are corresponding.
Under above-mentioned application scenarios, as shown in Figure 2, this message method can comprise the following steps:
Step 201, push server obtains to be waited to push content.
In the embodiment of the present application, push server obtains the process waiting to push content, specifically include but not limited to: need to send in time pushing content to user at service server, push server receives to be waited to push the message of content from carrying of service server, and obtains from this message and wait to push content.
Step 202, for multiple message sendaisle, push server obtains the at the appointed time interior login probability of each message sendaisle, and determines to log in the highest message sendaisle of probability.
Wherein, message sendaisle includes but not limited to: prosperous passage, Email Channel, short message channel, station, website internal information passage, applications client passage, QQ passage, micro-letter passage, MSN passage etc.
Step 203, push server utilizes the message sendaisle transmission logging in probability the highest to carry the message waiting to push content, namely push server sends to corresponding subscriber equipment by logging in the highest message sendaisle of probability by carrying the message waiting to push content, will wait that pushing content is shown to user by subscriber equipment.
In the embodiment of the present application, push server utilizes the message sendaisle transmission logging in probability the highest to carry the message waiting to push content, also comprises: push server judges whether the highest login probability is greater than default value before; If so, then push server performs the message sendaisle transmission utilizing login probability the highest and carries the process waiting the message pushing content; If not, then push server determination particular message sendaisle, and utilize particular message sendaisle to send the message carrying and treat propelling movement content.
Concrete, push server obtains the login probability of each message sendaisle at the appointed time in (as 7 days); If the highest login probability is greater than default value (as 50%), then push server is selected to log in the highest message sendaisle of probability from all message sendaisles, and utilizes the message sendaisle transmission logging in probability the highest to carry the message waiting to push content; If the highest login probability is not more than default value, then push server selects particular message sendaisle (as short message channel) from all message sendaisles, and utilizes particular message sendaisle to send the message carrying and treat propelling movement content.
Such as, push server obtains the login probability of each message sendaisle (as micro-letter passage, prosperous passage, Email Channel, short message channel etc.) at the appointed time in (as 7 days); Suppose that the probability that user logged in micro-letter passage in nearest 7 days is 50%, the probability logging in prosperous passage in nearest 7 days is 40%, and the probability logging in Email Channel in nearest 7 days is 30%, and the probability logging in short message channel in nearest 7 days is 30%.Suppose that default value is 40%, then the highest login probability (namely 50%) is greater than default value (as 40%), and now push server is selected to log in the highest message sendaisle (i.e. micro-letter passage) of probability from all message sendaisles; Afterwards, push server sends the message of carrying and waiting to push content A by micro-letter passage, namely by carrying, push server waits that the message pushing content A sends to the mobile terminal at the current place of micro-signal code 1 by micro-letter passage, and will wait that pushing content A is shown to user by mobile terminal.Suppose that default value is 50%, then the highest login probability (namely 50%) is not more than default value (as 50%), and now push server selects particular message sendaisle (as short message channel) from all message sendaisles; Afterwards, push server sends the message of carrying and waiting to push content A by short message channel, namely by carrying, push server waits that the message pushing content A sends to the mobile terminal at the current place of phone number 1 by short message channel, and will wait that pushing content A is shown to user by this mobile terminal.
In the embodiment of the present application, before push server obtains the at the appointed time interior login probability of each message sendaisle, namely before performing step 202 and step 203, send at needs in time pushing content to user, push server also will obtain the user ID of user in multiple message sendaisle difference correspondence.For each message sendaisle, push server utilizes user under message sendaisle, whether to be in logging status at the user ID inquiring user that message sendaisle is corresponding.If user is under all message sendaisles be not in logging status (as when all message sendaisles comprise prosperous passage, Email Channel, short message channel and micro-letter passage, user is is not in logging status in micro-letter passage, prosperous passage, Email Channel, short message channel), then push server performs and obtains the at the appointed time interior login probability of each message sendaisle, and utilize the message sendaisle transmission logging in probability the highest to carry the process waiting the message pushing content, namely perform the process of step 202 and step 203.If user is only in logging status (as when all message sendaisles comprise prosperous passage, Email Channel, short message channel and micro-letter passage under a message sendaisle, user is in logging status at micro-letter passage, be be not in logging status in prosperous passage, Email Channel, short message channel), then push server sends the message carrying and wait to push content by this message sendaisle.If user is in logging status (as when all message sendaisles comprise prosperous passage, Email Channel, short message channel and micro-letter passage under multiple message sendaisle, user is is in logging status in micro-letter passage, prosperous passage, Email Channel, short message channel), then push server utilizes default selection strategy to select a message sendaisle from multiple message sendaisle, and utilizes this selection message sendaisle to send the message carrying and treat propelling movement content.
In the embodiment of the present application, push server obtains user in the process of the user ID of multiple message sendaisle difference correspondence, and corresponding acquisition pattern specifically includes but not limited to as under type: push server receives the message carrying user profile from service server; When user profile is user in the user ID that multiple message sendaisle is corresponding respectively, push server is from from obtaining user the message of service server in the corresponding respectively user ID of multiple message sendaisle; Or when user profile is user name, push server inquires about the user ID list item of local maintenance by user name, to obtain the user ID of user in multiple message sendaisle difference correspondence; Wherein, user ID list item is used for recording user name and the corresponding relation of user between the user ID that multiple message sendaisle is corresponding respectively.
Specifically, need to send in time pushing content to user at service server, push server obtains this and waits to push content, and obtains the user ID of user in multiple message sendaisle difference correspondence.
Wherein, message sendaisle includes but not limited to: prosperous passage, Email Channel, short message channel, station, website internal information passage, applications client passage, QQ passage, micro-letter passage, MSN passage.User includes but not limited in the user ID that message sendaisle is corresponding: user is prosperous number in the user ID that prosperous passage is corresponding, user is email address in the user ID that Email Channel is corresponding, user is phone number in the user ID that short message channel is corresponding, user is website login name in the user ID that station, website internal information passage is corresponding, user is application identities in the user ID that applications client passage is corresponding, user is QQ number in the user ID that QQ passage is corresponding, user is micro-signal code in the user ID that micro-letter passage is corresponding, user is MSN number in the user ID that MSN passage is corresponding.Certainly, in actual applications, message sendaisle and user are not limited to above-mentioned situation in the user ID that message sendaisle is corresponding, and above-mentioned situation is the embodiment of the present application example for convenience of description, can select arbitrarily in practical application.
In the embodiment of the present application, need to send in time pushing content (as: market content or product information etc.) to user at service server, service server can push content by waiting and user profile informs to push server, is completed sending to user the process waiting to push content by push server in subsequent process.
In the embodiment of the present application, push server obtains to be waited to push content, and obtains the process of user in the user ID of multiple message sendaisle difference correspondence, specifically includes but not limited to as under type:
Mode one, push server receive and carry from service server the message waiting to push content and user profile, and wait to push content from from obtaining the message of service server.In mode once, this user profile is the user ID of user in multiple message sendaisle difference correspondence, therefore, when user profile is user in the user ID that multiple message sendaisle is corresponding respectively, push server is directly from from obtaining user the message of service server in the corresponding respectively user ID of multiple message sendaisle.
Such as, when service server 1 needs to send in time pushing content A to user 1, service server 1 sends message to push server, carry in this message and wait to push content A, and carry user 1 in the corresponding respectively user ID of multiple message sendaisle, as user 1 prosperous passage corresponding prosperous number 1, user 1 email address 1 corresponding to Email Channel, user 1 phone number 1 corresponding to short message channel, user 1 at micro-signal code 1 corresponding to micro-letter passage.Push server is after receiving the message from service server 1, directly obtain from the message from service server 1 and wait to push content A, and from the message from service server 1, directly obtain user 1 in the corresponding respectively user ID of multiple message sendaisle, namely user 1 prosperous passage corresponding prosperous number 1, user 1 email address 1 corresponding to Email Channel, user 1 phone number 1 corresponding to short message channel, user 1 at micro-signal code 1 corresponding to micro-letter passage.
Mode two, push server are at local maintenance user ID list item, and this user ID list item is used for recording user name and the corresponding relation of user between the user ID that multiple message sendaisle is corresponding respectively.Push server receives and carries from service server the message waiting to push content and user profile, and waits to push content from from obtaining the message of service server.Mode two times, this user profile is user name, therefore, when user profile is user name, push server by the user ID list item of user name inquiry local maintenance, to obtain user in the corresponding respectively user ID of multiple message sendaisle.
Such as, push server is as shown in table 1 at the user ID list item of local maintenance.When service server 1 needs to send in time pushing content A to user 1, service server 1 sends message to push server, carries and waits to push content A, and carry the user name (i.e. user name 1) of user 1 in this message.Push server, after receiving the message from service server 1, directly obtains and waits to push content A from the message from service server 1.In addition, push server is by the user ID list item shown in user name 1 question blank 1, to obtain user 1 in the corresponding respectively user ID of multiple message sendaisle, namely user 1 prosperous passage corresponding prosperous number 1, user 1 email address 1 corresponding to Email Channel, user 1 phone number 1 corresponding to short message channel, user 1 at micro-signal code 1 corresponding to micro-letter passage.
Table 1
In the embodiment of the present application, for each message sendaisle, push server can utilize user under this message sendaisle, whether to be in logging status at the user ID inquiring user that message sendaisle is corresponding.Such as, be prosperous passage, Email Channel, short message channel and micro-letter passage for message sendaisle.For prosperous passage, push server utilizes user 1 under prosperous passage, whether to be in logging status at prosperous number 1 inquiring user 1 that prosperous passage is corresponding; For Email Channel, push server utilizes user 1 whether to be in logging status at email address 1 inquiring user 1 that Email Channel is corresponding at Email Channel; For short message channel, push server utilizes user 1 whether to be in logging status at phone number 1 inquiring user 1 that short message channel is corresponding in short message channel; For micro-letter passage, push server utilizes user 1 whether to be in logging status at micro-signal code 1 inquiring user 1 that micro-letter passage is corresponding at micro-letter passage.
In the embodiment of the present application, push server utilizes user under message sendaisle, whether to be in the process of logging status at the user ID inquiring user that message sendaisle is corresponding, specifically include but not limited to as under type: for each message sendaisle, push server sends to application server corresponding to message sendaisle and carries the request message of user in user ID corresponding to this message sendaisle, utilizes this user ID inquiring user whether to be in logging status under this message sendaisle by this application server; Afterwards, application server returns the response message carrying user and be in logging status or be not in logging status under this message sendaisle to push server; Afterwards, push server receives and carries from application server the response message that user is in logging status or is not in logging status under this message sendaisle; Afterwards, by the information of carrying in this response message, push server determines that user is in logging status under this message sendaisle or user is not in logging status under this message sendaisle.
Such as, for prosperous passage, push server sends to application server (as prosperous server) corresponding to prosperous passage and carries user 1 at the request message of prosperous number 1 corresponding to prosperous passage.Whether prosperous server by utilizing prosperous number 1 inquiring user 1 is in logging status under prosperous passage, and the mode whether this inquiring user 1 is in logging status under prosperous passage does not repeat them here.Prosperous server returns the response message carrying user 1 and be in logging status or be not in logging status under prosperous passage to push server.Push server receives and carries from prosperous server the response message that user 1 is in logging status or is not in logging status under prosperous passage.By the information of carrying in response message, push server determines that user 1 is in logging status under prosperous passage or user 1 is not in logging status under prosperous passage, namely determine whether user 1 is in logging status under prosperous passage.
In addition, for the processing procedure of Email Channel, short message channel and micro-letter passage, similar with the processing procedure of above-mentioned prosperous passage, just corresponding application server is different, and therefore at this, it is no longer repeated.
In the embodiment of the present application, if user is and is not in logging status under all message sendaisles, then push server utilizes default selection strategy to select a message sendaisle from all message sendaisles, and utilize this selection message sendaisle to send the message of carrying and treating propelling movement content, namely push server sends to corresponding subscriber equipment by a message sendaisle of current selection by carrying the message waiting to push content, will wait that pushing content is shown to user by this subscriber equipment.Further, push server utilizes presets the process that the second selection strategy selects a message sendaisle from all message sendaisles, specifically includes but not limited to as under type: push server obtains the at the appointed time interior login probability of each message sendaisle; If the highest login probability is greater than default value, then push server is selected to log in the highest message sendaisle of probability from all message sendaisles; If the highest login probability is not more than default value, then push server selects particular message sendaisle (as short message channel) from all message sendaisles.Such as, if user is is not in logging status in micro-letter passage, prosperous passage, Email Channel, short message channel, then push server obtains the login probability of each message sendaisle (i.e. micro-letter passage, prosperous passage, Email Channel, short message channel) at the appointed time in (as 7 days); Suppose that the probability that user logged in micro-letter passage in nearest 7 days is 50%, the probability logging in prosperous passage in nearest 7 days is 40%, and the probability logging in Email Channel in nearest 7 days is 30%, and the probability logging in short message channel in nearest 7 days is 30%.Suppose that default value is 40%, then the highest login probability (namely 50%) is greater than default value (as 40%), and now push server is selected to log in the highest message sendaisle (i.e. micro-letter passage) of probability from all message sendaisles; Afterwards, push server sends the message of carrying and waiting to push content A by micro-letter passage, namely by carrying, push server waits that the message pushing content A sends to the mobile terminal at the current place of micro-signal code 1 by micro-letter passage, and will wait that pushing content A is shown to user by mobile terminal.Suppose that default value is 50%, then the highest login probability (namely 50%) is not more than default value (as 50%), and now push server selects particular message sendaisle (as short message channel) from all message sendaisles; Afterwards, push server sends the message of carrying and waiting to push content A by short message channel, namely by carrying, push server waits that the message pushing content A sends to the mobile terminal at the current place of phone number 1 by short message channel, and mobile terminal will wait that pushing content A is shown to user.
In above-mentioned processing procedure, push server utilizes presets the second selection strategy when selecting a message sendaisle from all message sendaisles, be Effect-based operation sendaisle at the appointed time in login probability realize, certainly, be not limited to login probability in actual applications, as can also the number of times etc. opening PUSH message corresponding to Effect-based operation sendaisle, in the embodiment of the present application, this be repeated no more.
In the embodiment of the present application, if user is only in logging status under a message sendaisle, then push server sends the message of carrying and treating propelling movement content by the message sendaisle message sendaisle of logging status (namely unique be in), namely push server sends to corresponding subscriber equipment by message sendaisle by carrying the message waiting to push content, is shown to user by subscriber equipment.Such as, if user is in logging status at micro-letter passage, be be not in logging status in prosperous passage, Email Channel, short message channel, then push server sends the message of carrying and waiting to push content A by micro-letter passage, namely by carrying, push server waits that the message pushing content A sends to the mobile terminal at the current place of micro-signal code 1 by micro-letter passage, and will wait that pushing content A is shown to user by mobile terminal.
In the embodiment of the present application, if user is in logging status under multiple message sendaisle, then (this default selection strategy can rule of thumb be arranged arbitrarily the default selection strategy of push server utilization, be the minimum strategy of cost as arranged default selection strategy) from multiple message sendaisle (i.e. the current multiple message sendaisles being in logging status), select a message sendaisle, and utilize this selection message sendaisle to send the message of carrying and treating propelling movement content, namely push server sends to corresponding subscriber equipment by a message sendaisle (being in the message sendaisle of logging status) of current selection by carrying the message waiting to push content, user is shown to by subscriber equipment.Such as, if user is at micro-letter passage, prosperous passage, Email Channel, short message channel is and is in logging status, then push server is from micro-letter passage, prosperous passage, Email Channel, the message sendaisle that a cost is minimum is selected in short message channel, suppose that Email Channel is the message sendaisle that cost is minimum, then push server selects Email Channel, and the message of carrying and waiting to push content A is sent by Email Channel, namely by carrying, push server waits that the message pushing content A sends to the subscriber equipment (as PC) at the current place of addresses of items of mail 1 by Email Channel, to wait that pushing content A is shown to user by this subscriber equipment.
In the embodiment of the present application, push server can also generate each application server source template corresponding respectively, and the source template that each application server is corresponding is respectively sent to each application server respectively.Further, carry in the process waiting the message pushing content in push server by the transmission of message sendaisle, when being sent the message of carrying until propelling movement content by message sendaisle, this push server needs to wait that pushing content sends to the application server that message sendaisle is corresponding, utilize source template by this application server afterwards and wait to push content generating messages, and sending the message carrying and wait to push content.
Such as, push server generates the source template 1 of application server corresponding to micro-letter passage, and source template 1 is sent to the application server that micro-letter passage is corresponding; Push server generates the source template 2 of application server corresponding to prosperous passage, and source template 2 is sent to the application server that prosperous passage is corresponding; Push server generates the source template 3 of application server corresponding to Email Channel, and by application server that source template 3 sends to Email Channel corresponding; Push server generates the source template 4 of application server corresponding to short message channel, and by application server that source template 4 sends to short message channel corresponding.
Suppose that push server needs to send the message of carrying and waiting to push content A by micro-letter passage, then push server will wait that pushing content A sends to the application server that micro-letter passage is corresponding, utilize source template 1 by the application server that micro-letter passage is corresponding and wait to push content A generating messages, and sending this message.Suppose that push server needs to send the message of carrying and waiting to push content A by prosperous passage, then push server will wait that pushing content A sends to the application server that prosperous passage is corresponding, utilize source template 2 by the application server that prosperous passage is corresponding and wait to push content A generating messages, and sending this message.
In sum, in the embodiment of the present application, the message of carrying and waiting to push content can be sent to subscriber equipment by logging in the highest message sendaisle (as micro-letter passage, prosperous passage, Email Channel, short message channel etc.) of probability, thus will wait to push context notification to user as far as possible, improve and push the probability of context notification to user by waiting, and the waste causing system resource and Internet resources can be avoided, save system resource and Internet resources, and can avoid causing harassing and wrecking to user, thus the use sense improving user is subject to.
Embodiment two
Based on the application same with said method design, additionally provide a kind of push server in the embodiment of the present application, as shown in Figure 3, described Push Service implement body comprises:
Obtaining module 11, waiting to push content for obtaining;
Determination module 12, for for multiple message sendaisle, obtains the login probability that each message sendaisle is at the appointed time interior, and determines to log in the highest message sendaisle of probability;
Sending module 13, sends the message waiting to push content described in carrying for utilizing the highest message sendaisle of described login probability.
Described acquisition module 11, specifically for sending in time pushing content to user at needs, receiving and waiting to push the message of content from carrying of service server, waiting to push content from described message described in obtaining.
Described sending module 13, is further used for judging whether the highest login probability is greater than default value;
If so, then perform utilize the highest message sendaisle of described login probability to send to carry described in wait to push the process of message of content; If not, then determine particular message sendaisle, and wait to push the message of content described in utilizing described particular message sendaisle to send to carry.
Described acquisition module 11, also for sending in time pushing content to user at needs, obtains the user ID of described user in multiple message sendaisle difference correspondence; Described determination module 12, also for for each message sendaisle, utilizes described user under described message sendaisle, whether to be in logging status at the user ID inquiring user that message sendaisle is corresponding; Described sending module 13, if be further used for described user to be under all message sendaisles and not to be in logging status, then execution obtains the at the appointed time interior login probability of each message sendaisle, waits the process of the message pushing content described in the message sendaisle transmission utilizing login probability the highest carries.
Described sending module 13, if be also only in logging status under a message sendaisle for described user, then waits to push the message of content described in being carried by this message sendaisle transmission;
If described user is in logging status under multiple message sendaisle, then utilize and preset selection strategy selects a message sendaisle from described multiple message sendaisle, and treat the message of propelling movement content described in utilizing this selection message sendaisle to send to carry.
Described acquisition module 11, specifically for receiving the message carrying user profile from service server; When described user profile is user in the user ID that multiple message sendaisle is corresponding respectively, from the message from described service server, obtain described user in the corresponding respectively user ID of multiple message sendaisle; Or, when described user profile is user name, inquired about the user ID list item of described push server local maintenance by described user name, to obtain the user ID of described user in multiple message sendaisle difference correspondence; Wherein, described user ID list item is used for recording user name and the corresponding relation of user between the user ID that multiple message sendaisle is corresponding respectively.
Described determination module 12, carrying the request message of user in user ID corresponding to described message sendaisle specifically for sending to application server corresponding to message sendaisle, utilizing described user ID to inquire about described user by described application server and whether being in logging status under described message sendaisle;
Receive and carry from described application server the response message that described user is in logging status or is not in logging status under described message sendaisle;
Determine that described user is in logging status or is not in logging status under described message sendaisle under described message sendaisle by the information of carrying in described response message.
Described sending module 13, is further used for generating each application server source template corresponding respectively, and the source template that each application server is corresponding is respectively sent to described each application server respectively;
Described in being carried by the transmission of message sendaisle in time pushing the message of content, wait that pushing content sends to the application server that described message sendaisle is corresponding by described, utilize source template and described waiting to push content generating messages by described application server, and send described message.
Wherein, the modules of the application's device can be integrated in one, and also can be separated deployment.Above-mentioned module can merge into a module, also can split into multiple submodule further.
Through the above description of the embodiments, those skilled in the art can be well understood to the mode that the application can add required general hardware platform by software and realize, and can certainly pass through hardware, but in a lot of situation, the former is better execution mode.Based on such understanding, the technical scheme of the application can embody with the form of software product the part that prior art contributes in essence in other words, this computer software product is stored in a storage medium, comprising some instructions in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) perform method described in each embodiment of the application.It will be appreciated by those skilled in the art that accompanying drawing is the schematic diagram of a preferred embodiment, the module in accompanying drawing or flow process might not be that enforcement the application is necessary.It will be appreciated by those skilled in the art that the module in the device in embodiment can carry out being distributed in the device of embodiment according to embodiment description, also can carry out respective change and be arranged in the one or more devices being different from the present embodiment.The module of above-described embodiment can merge into a module, also can split into multiple submodule further.Above-mentioned the embodiment of the present application sequence number, just to describing, does not represent the quality of embodiment.Be only several specific embodiments of the application above, but the application is not limited thereto, the changes that any person skilled in the art can think of all should fall into the protection range of the application.
Claims (16)
1. a message method, is characterized in that, said method comprising the steps of:
Push server obtains to be waited to push content;
For multiple message sendaisle, described push server obtains the at the appointed time interior login probability of each message sendaisle, and determines to log in the highest message sendaisle of probability;
Wait to push the message of content described in described push server utilizes the highest message sendaisle of described login probability to send to carry.
2. the method for claim 1, is characterized in that, described push server obtains to be waited to push content, specifically comprises:
Send at needs in time pushing content to user, described push server receives the message from waiting to push content described in the carrying of service server, and waits described in obtaining from described message to push content.
3. the method for claim 1, is characterized in that, waits to push the message of content, also comprise before described in described push server utilizes the highest message sendaisle of described login probability to send to carry:
Described push server judges whether the highest login probability is greater than default value; If so, then described push server perform utilize the highest message sendaisle of described login probability to send to carry described in wait the process of the message pushing content; If not, then described push server determination particular message sendaisle, and wait to push the message of content described in utilizing described particular message sendaisle to send to carry.
4. the method for claim 1, is characterized in that, before described push server obtains the at the appointed time interior login probability of each message sendaisle, described method also comprises:
Send at needs in time pushing content to user, described push server obtains the user ID of described user in multiple message sendaisle difference correspondence;
For each message sendaisle, described push server utilizes described user to inquire about described user in the user ID that message sendaisle is corresponding and whether be in logging status under described message sendaisle;
If described user is and is not in logging status under all message sendaisles, then described push server perform obtain each message sendaisle at the appointed time in login probability, and utilize log in the highest message sendaisle of probability send carry described in wait the process of the message pushing content.
5. method as claimed in claim 4, is characterized in that, described push server utilizes described user to inquire about after whether described user be in logging status under described message sendaisle in the user ID that message sendaisle is corresponding, and described method also comprises:
If described user is only in logging status under a message sendaisle, then described push server by this message sendaisle send carry described in wait to push the message of content;
If described user is in logging status under multiple message sendaisle, then described push server utilizes and presets selection strategy selects a message sendaisle from described multiple message sendaisle, and treats the message of propelling movement content described in utilizing this selection message sendaisle to send to carry.
6. method as claimed in claim 4, is characterized in that, described push server obtains the process of described user in the user ID of multiple message sendaisle difference correspondence, specifically comprises:
Described push server receives the message carrying user profile from service server;
When described user profile is user in the user ID that multiple message sendaisle is corresponding respectively, described push server obtains described user in the corresponding respectively user ID of multiple message sendaisle from the message from described service server; Or when described user profile is user name, described push server inquires about the user ID list item of local maintenance by described user name, to obtain the user ID of described user in multiple message sendaisle difference correspondence; Wherein, described user ID list item is used for recording user name and the corresponding relation of user between the user ID that multiple message sendaisle is corresponding respectively.
7. method as claimed in claim 4, it is characterized in that, for each message sendaisle, described push server utilizes described user to inquire about in the user ID that message sendaisle is corresponding the process whether described user is in logging status under described message sendaisle, specifically comprises:
Described push server sends to application server corresponding to message sendaisle and carries the request message of user in user ID corresponding to described message sendaisle, utilizes described user ID to inquire about described user whether be in logging status by described application server under described message sendaisle;
Described push server receives and carries from described application server the response message that described user is in logging status or is not in logging status under described message sendaisle;
By the information of carrying in described response message, described push server determines that described user is in logging status or is not in logging status under described message sendaisle under described message sendaisle.
8. the method according to any one of claim 1,3,5, is characterized in that, waits the process of the message pushing content, specifically comprise described in described push server is carried by the transmission of message sendaisle:
Described push server generates each application server source template corresponding respectively, and the source template that each application server is corresponding is respectively sent to described each application server respectively;
Described in being carried by the transmission of message sendaisle in time pushing the message of content, by described, described push server waits that pushing content sends to the application server that described message sendaisle is corresponding, utilize source template and described waiting to push content generating messages by described application server, and send described message.
9. a push server, is characterized in that, described Push Service implement body comprises:
Obtaining module, waiting to push content for obtaining;
Determination module, for for multiple message sendaisle, obtains the login probability that each message sendaisle is at the appointed time interior, and determines to log in the highest message sendaisle of probability;
Sending module, sends the message waiting to push content described in carrying for utilizing the highest message sendaisle of described login probability.
10. push server as claimed in claim 9, is characterized in that,
Described acquisition module, specifically for sending in time pushing content to user at needs, receiving and waiting to push the message of content from carrying of service server, and waiting described in obtaining from described message to push content.
11. push server as claimed in claim 9, is characterized in that,
Described sending module, is further used for judging whether the highest login probability is greater than default value;
If so, then perform utilize the highest message sendaisle of described login probability to send to carry described in wait to push the process of message of content; If not, then determine particular message sendaisle, and wait to push the message of content described in utilizing described particular message sendaisle to send to carry.
12. push server as claimed in claim 9, is characterized in that,
Described acquisition module, also for sending in time pushing content to user at needs, obtains the user ID of described user in multiple message sendaisle difference correspondence;
Described determination module, also for for each message sendaisle, utilizes described user under described message sendaisle, whether to be in logging status at the user ID inquiring user that message sendaisle is corresponding;
Described sending module, if be further used for described user to be under all message sendaisles and not to be in logging status, then execution obtains the at the appointed time interior login probability of each message sendaisle, waits the process of the message pushing content described in the message sendaisle transmission utilizing login probability the highest carries.
13. push server as claimed in claim 12, is characterized in that,
Described sending module, if be also only in logging status under a message sendaisle for described user, then waits to push the message of content described in being carried by this message sendaisle transmission;
If described user is in logging status under multiple message sendaisle, then utilize and preset selection strategy selects a message sendaisle from described multiple message sendaisle, and treat the message of propelling movement content described in utilizing this selection message sendaisle to send to carry.
14. push server as claimed in claim 12, is characterized in that,
Described acquisition module, specifically for receiving the message carrying user profile from service server;
When described user profile is user in the user ID that multiple message sendaisle is corresponding respectively, from the message from described service server, obtain described user in the corresponding respectively user ID of multiple message sendaisle; Or, when described user profile is user name, inquired about the user ID list item of described push server local maintenance by described user name, to obtain the user ID of described user in multiple message sendaisle difference correspondence; Wherein, described user ID list item is used for recording user name and the corresponding relation of user between the user ID that multiple message sendaisle is corresponding respectively.
15. push server as claimed in claim 12, is characterized in that,
Described determination module, carrying the request message of user in user ID corresponding to described message sendaisle specifically for sending to application server corresponding to message sendaisle, utilizing described user ID to inquire about described user by described application server and whether being in logging status under described message sendaisle;
Receive and carry from described application server the response message that described user is in logging status or is not in logging status under described message sendaisle;
Determine that described user is in logging status or is not in logging status under described message sendaisle under described message sendaisle by the information of carrying in described response message.
16. push server according to any one of claim 9,11,13, is characterized in that,
Described sending module, is further used for generating each application server source template corresponding respectively, and the source template that each application server is corresponding is respectively sent to described each application server respectively;
Described in being carried by the transmission of message sendaisle in time pushing the message of content, wait that pushing content sends to the application server that described message sendaisle is corresponding by described, utilize source template and described waiting to push content generating messages by described application server, and send described message.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410253563.1A CN105227595B (en) | 2014-06-09 | 2014-06-09 | A kind of message method and equipment |
| HK16103736.5A HK1215830A1 (en) | 2014-06-09 | 2016-04-01 | Method and device for sending message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410253563.1A CN105227595B (en) | 2014-06-09 | 2014-06-09 | A kind of message method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105227595A true CN105227595A (en) | 2016-01-06 |
| CN105227595B CN105227595B (en) | 2019-09-03 |
Family
ID=54996270
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410253563.1A Active CN105227595B (en) | 2014-06-09 | 2014-06-09 | A kind of message method and equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105227595B (en) |
| HK (1) | HK1215830A1 (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106790688A (en) * | 2017-02-17 | 2017-05-31 | 乌镇互联网医院（桐乡）有限公司 | Message push system and its method for pushing |
| CN107864082A (en) * | 2016-09-22 | 2018-03-30 | 腾讯科技（深圳）有限公司 | Message method and device |
| CN108183933A (en) * | 2017-12-04 | 2018-06-19 | 深圳开思时代科技有限公司 | Information push method, apparatus and system, electronic equipment and computer storage media |
| CN109104357A (en) * | 2018-07-10 | 2018-12-28 | 携程旅游信息技术（上海）有限公司 | The processing method and system of PUSH message |
| CN109788326A (en) * | 2019-01-11 | 2019-05-21 | 北京奇艺世纪科技有限公司 | A kind of video resource pre-push method, apparatus and system |
| CN110460638A (en) * | 2019-07-11 | 2019-11-15 | 深圳职业技术学院 | Information push method and device |
| CN110855548A (en) * | 2019-10-18 | 2020-02-28 | 深圳前海微众银行股份有限公司 | Message pushing method and device |
| CN111835837A (en) * | 2020-06-28 | 2020-10-27 | 中国船舶重工集团公司第七一六研究所 | Message pushing method and system with multi-terminal adaptation |
| CN113423075A (en) * | 2021-05-18 | 2021-09-21 | 北京达佳互联信息技术有限公司 | Short message sending control method and device, electronic equipment, storage medium and product |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102480674A (en) * | 2010-11-26 | 2012-05-30 | 中国移动通信集团北京有限公司 | Data pushing method and state perceiving and pushing module as well as data pushing system |
| CN103001941A (en) * | 2012-08-29 | 2013-03-27 | 五八同城信息技术有限公司 | Multipoint login based message distribution method and multipoint login based message distribution device |
| US8509834B1 (en) * | 2009-05-22 | 2013-08-13 | Nextel Communications Inc. | Method and computer-readable medium for social circle push-to-talk service |
| CN103684988A (en) * | 2013-11-22 | 2014-03-26 | 深圳市迈桥科技有限公司 | Cross-mobile-terminal message pushing method and device |
| CN103685502A (en) * | 2013-12-09 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Message pushing method, device and system |
-
2014
- 2014-06-09 CN CN201410253563.1A patent/CN105227595B/en active Active
-
2016
- 2016-04-01 HK HK16103736.5A patent/HK1215830A1/en unknown
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8509834B1 (en) * | 2009-05-22 | 2013-08-13 | Nextel Communications Inc. | Method and computer-readable medium for social circle push-to-talk service |
| CN102480674A (en) * | 2010-11-26 | 2012-05-30 | 中国移动通信集团北京有限公司 | Data pushing method and state perceiving and pushing module as well as data pushing system |
| CN103001941A (en) * | 2012-08-29 | 2013-03-27 | 五八同城信息技术有限公司 | Multipoint login based message distribution method and multipoint login based message distribution device |
| CN103684988A (en) * | 2013-11-22 | 2014-03-26 | 深圳市迈桥科技有限公司 | Cross-mobile-terminal message pushing method and device |
| CN103685502A (en) * | 2013-12-09 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Message pushing method, device and system |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107864082A (en) * | 2016-09-22 | 2018-03-30 | 腾讯科技（深圳）有限公司 | Message method and device |
| CN107864082B (en) * | 2016-09-22 | 2020-08-21 | 腾讯科技（深圳）有限公司 | Message sending method and device |
| CN106790688A (en) * | 2017-02-17 | 2017-05-31 | 乌镇互联网医院（桐乡）有限公司 | Message push system and its method for pushing |
| CN108183933A (en) * | 2017-12-04 | 2018-06-19 | 深圳开思时代科技有限公司 | Information push method, apparatus and system, electronic equipment and computer storage media |
| CN109104357A (en) * | 2018-07-10 | 2018-12-28 | 携程旅游信息技术（上海）有限公司 | The processing method and system of PUSH message |
| CN109788326A (en) * | 2019-01-11 | 2019-05-21 | 北京奇艺世纪科技有限公司 | A kind of video resource pre-push method, apparatus and system |
| CN110460638A (en) * | 2019-07-11 | 2019-11-15 | 深圳职业技术学院 | Information push method and device |
| CN110855548A (en) * | 2019-10-18 | 2020-02-28 | 深圳前海微众银行股份有限公司 | Message pushing method and device |
| CN111835837A (en) * | 2020-06-28 | 2020-10-27 | 中国船舶重工集团公司第七一六研究所 | Message pushing method and system with multi-terminal adaptation |
| CN113423075A (en) * | 2021-05-18 | 2021-09-21 | 北京达佳互联信息技术有限公司 | Short message sending control method and device, electronic equipment, storage medium and product |
Also Published As
| Publication number | Publication date |
|---|---|
| HK1215830A1 (en) | 2016-09-15 |
| CN105227595B (en) | 2019-09-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105227595A (en) | A kind of message method and equipment | |
| CN103117915B (en) | The method and apparatus that a kind of message sends | |
| CN105337837A (en) | Message transmitting method and device | |
| CN102625287A (en) | Method for downloading mobile phone application software | |
| CN103346974A (en) | Controlling method of service process and network device | |
| CN108965107B (en) | Friend adding method, device, system, client and server | |
| US11165899B1 (en) | Techniques to manage contact records | |
| CN105141789A (en) | Strange number marking method and device | |
| CN102594912A (en) | Data processing method under server architecture, server and server architecture | |
| CN105897888A (en) | Client connection method and system | |
| CN102081626B (en) | Data inquiring method and data inquiring server | |
| CN104601742A (en) | Message transmission method and device | |
| CN1845616A (en) | Short message service interface and channel adapting method for the same | |
| CN107342929B (en) | Method, device and system for sending new message notification | |
| WO2017133487A1 (en) | Service scheduling method and device, and computer storage medium | |
| US9473430B2 (en) | Method and system for group number-based microblog aggregation | |
| CN105743891A (en) | Networking method and device, server and router | |
| CN104869571A (en) | Rapid portal authentication method and device | |
| WO2019119962A1 (en) | Information processing method, system, terminal, and computer readable storage medium | |
| CN113596105B (en) | Content acquisition method, edge node and computer readable storage medium | |
| CN104852986A (en) | Method and device for providing newly-added function | |
| CN113014610B (en) | Remote access method, device and system | |
| CN112954084B (en) | Edge computing processing method, network function example and edge service management and control center | |
| CN105991450A (en) | MAC address table updating method and device | |
| CN105227435A (en) | The method and apparatus of transmission of messages |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1215830 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20191210 Address after: P.O. Box 31119, grand exhibition hall, hibiscus street, 802 West Bay Road, Grand Cayman, Cayman Islands Patentee after: Innovative advanced technology Co., Ltd Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Co., Ltd. |
|
| TR01 | Transfer of patent right |