CN103973461A - Notification message pushing method and message server - Google Patents
Notification message pushing method and message server Download PDFInfo
- Publication number
- CN103973461A CN103973461A CN201310048776.6A CN201310048776A CN103973461A CN 103973461 A CN103973461 A CN 103973461A CN 201310048776 A CN201310048776 A CN 201310048776A CN 103973461 A CN103973461 A CN 103973461A
- Authority
- CN
- China
- Prior art keywords
- message
- template
- sending
- user
- type
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a notification message pushing method and a message server so as to be applicable to different types and time zones terminals supporting different languages. The notification message pushing method includes receiving notification messages including message headers, parameter key values and template number of various terminal types; analyzing the message headers of the notification messages to obtain receiver identifiers and looking up terminal types and language types corresponding to the receiver identifiers; calling corresponding template messages from a template register according to the lookup terminal types, wherein the template messages include different language types of template messages; renewing parameters in the template messages according to the parameter key values and generating pushing messages according to the lookup language types; transmitting the pushing messages to terminals where the receivers are located. The notification message pushing method can be self-adaptive to types and languages and can realize self-adaptive time zones.
Description
Technical Field
The present application relates to the field of network technologies, and in particular, to a notification message pushing method and a message server.
Background
At present, a message publisher can send service messages such as reminding and notification to a user terminal through a message server, and with the diversification of the user terminal, the message presentation mode also needs to be diversified correspondingly. For example, the message presented at the mobile phone end is different from the message presented at the PC end, and the message presented at the PC pop-up window and the PC service window may be different. Meanwhile, with the continuous internationalization of enterprise services, enterprise users are distributed all over the world, and the presentation of messages at user terminals also needs to support the change of different languages and different time zones. And for users in different regions, the message publisher is required to send messages in different languages to the user terminal at different time periods.
Since the message published by the message publisher is pushed to the user terminal through the message server, in order to display different message styles on different types of user terminals or to meet the requirements of different time zones and different languages, the message server needs to send different messages to the user terminal according to the type of the user terminal, the region where the user terminal is located and the supported language.
Disclosure of Invention
The application provides a pushing method of a notification message and a message server, which are suitable for terminals with different types, different time zones and different languages.
In order to solve the above problem, the present application discloses a notification message pushing method, including:
receiving a notification message, wherein the notification message comprises a message header, a parameter key value and a template number corresponding to each terminal type;
analyzing the message header of the notification message to obtain a receiver identification, and searching a terminal type and a language type corresponding to the receiver identification;
calling corresponding template information from a template registry according to the template number corresponding to the searched terminal type, wherein the template information comprises template information of different language types;
replacing parameters in the template message according to the parameter key values, and generating a push message according to the searched language type;
and sending the push message to a terminal where the receiver is located.
Optionally, before receiving the notification message, the method further includes:
receiving a template registration message, the template registration message comprising: the template information comprises template information of different language types;
and registering and storing the template registration message in a template registry.
Optionally, before receiving the notification message, the method further includes:
receiving user login information, wherein the user login information comprises: user authentication information, a user name, a terminal type, a language type, a time zone in which the user is located and last login time;
verifying according to the user verification information, and judging whether the user name is located in an online information table or not for the user passing the verification;
if the user name is located in an online information table, updating a terminal type, a language type, a time zone where the user name is located and the last login time corresponding to the user name in the online information table;
and if the user name is not located in an online information table, storing the user login information into the online information table.
Optionally, the searching for the terminal type and the language type corresponding to the recipient identifier includes:
looking up the recipient identification from the presence information table;
the method further comprises the following steps:
and when the receiver identification cannot be searched in the online information table, analyzing the message header of the notification message to obtain a default terminal type and a default language type, and generating a push message according to the default terminal type and the default language type.
Optionally, before the invoking the corresponding template message from the template registry according to the template number corresponding to the found terminal type, the method further includes:
analyzing the message header of the notification message to obtain the message type;
when the message type of the notification message is a timing message, analyzing a message header to obtain timing sending time and whether to use a local time zone for pushing;
if the local time zone is used for pushing, searching the local time zone corresponding to the receiver identification from an online information table, and if the searching is successful, converting the timing sending time into the corresponding local time according to the local time zone; setting a timer according to the corresponding local time, adding the notification message into a timing queue, and executing the step of calling the corresponding template message from the template registry according to each template number when the corresponding local time is reached; if the search fails, executing a step of pushing without using the local time zone;
if the local time zone is not used for pushing, setting a timer according to the timing sending time, adding the notification message into a timing queue, and executing the step of calling the corresponding template message from the template registry according to each template number when the timing sending time is reached.
Optionally, when the message type of the notification message is an online message, the sending the push message to the terminal where the recipient is located includes:
searching the receiver identification from an online information table, if the search is successful, putting the push message into a sending queue, and sending the push message to a terminal where the receiver is located; if the search fails, the transmission is finished.
Optionally, when the message type of the notification message is an ordinary message, the sending the push message to the terminal where the recipient is located includes:
searching the receiver identification from an online information table, if the search is successful, putting the push message into a sending queue, and sending the push message to a terminal where the receiver is located; and if the search fails, putting the push message into an offline queue, and sending the push message when the receiver identification is on line.
The application also discloses a message server, including:
a notification message receiving module, configured to receive a notification message, where the notification message includes a message header, a parameter key value, and a template number corresponding to each terminal type;
the searching module is used for analyzing the message header of the notification message to obtain a receiver identifier and searching the terminal type and the language type corresponding to the receiver identifier;
the calling module is used for calling corresponding template information from the template registry according to the template number corresponding to the searched terminal type, wherein the template information comprises template information of different language types;
the generating module is used for replacing parameters in the template message according to the parameter key values and generating a push message according to the searched language type;
and the sending module is used for sending the push message to the terminal where the receiver is located.
Optionally, the method further comprises:
the template registration module is used for receiving the template registration message before receiving the notification message, registering and storing the template registration message in a template registration library; the template registration message includes: the template information comprises template information of different language types.
Optionally, the method further comprises:
a login information receiving module, configured to receive user login information before receiving a notification message, where the user login information includes: user authentication information, a user name, a terminal type, a language type, a time zone in which the user is located and last login time;
the user authentication module is used for authenticating according to the user authentication information and judging whether the user name is located in an online information table or not for the user passing the authentication;
the updating module is used for updating the terminal type, the language type, the time zone in which the user name is located and the last login time corresponding to the user name in the online information table when the user name is located in the online information table;
and the storage module is used for storing the user login information into the online information table when the user name is not located in the online information table.
Optionally, the method further comprises:
a message header analyzing module, configured to analyze a message header of the notification message to obtain a message type before calling a corresponding template message from a template registry according to a template number corresponding to the found terminal type;
the message header analyzing module is further used for analyzing the message header to obtain the timing sending time and whether to use the local time zone for pushing when the message type of the notification message is the timing message;
the local pushing module is used for searching a local time zone corresponding to the receiver identification from an online information table when the local time zone is used for pushing, and converting the timing sending time into corresponding local time according to the local time zone when the searching is successful; setting a timer according to the corresponding local time, adding the notification message into a timing queue, and calling the corresponding template message from a template registry according to each template number by the calling module when the corresponding local time is reached;
and the local pushing module is used for pushing without using a local time zone or when the local pushing module fails to search the local time zone corresponding to the receiver identifier from an online information table, setting a timer according to the timed sending time, adding the notification message into a timed queue, and calling the corresponding template message from the template registry according to each template number when the timed sending time is reached.
Optionally, the sending module is further configured to, when the message type of the notification message is an online message, search for the recipient identifier from an online information table, and if the search is successful, place the push message in a sending queue and send the push message to a terminal where the recipient is located; if the search fails, the transmission is finished.
Optionally, the sending module is further configured to, when the message type of the notification message is a common message, search for the recipient identifier from an online information table, and if the search is successful, place the push message in a sending queue and send the push message to a terminal where the recipient is located; and if the search fails, putting the push message into an offline queue, and sending the push message when the receiver identification is on line.
Compared with the prior art, the method has the following advantages:
the notification message pushing method provided by the embodiment of the application can be in a self-adaptive mode, namely different message display can be carried out according to different terminal types, and due to the fact that the template message is set, different templates can be directly called to generate the pushing message to be sent, and the workload is reduced when the message display is adjusted. And the template message is set, and only the parameters in the template message need to be replaced according to the parameter key values when the push message is generated.
In addition, the embodiment of the application can also adapt to languages, namely, when the message server pushes the message, the message server can select the template of the corresponding language according to the language type of the receiver stored in the online information table to generate the push message, and only the push message of the corresponding language is sent to the terminal, so that the multi-language capability is provided. Correspondingly, the set template has multiple languages. The template of the message format can also greatly improve the sending efficiency of the message for the same type of message.
The embodiment of the application can also realize self-adaption time zone, and for the notification message which requires to adapt to the local time zone, the timing sending time can be converted into the corresponding local time pushing message according to the local time zone where the user is located. For example, if a user needs to see a message at 8 am of the day, the message is adaptively adjusted according to the time zone information saved when the user logs in, that is, the message is converted into the corresponding local time at 8 am of the location of the user, and then pushed when the corresponding local time is reached.
Of course, it is not necessary for any product to achieve all of the above-described advantages at the same time for practicing the present application.
Drawings
Fig. 1 is a flowchart of a notification message pushing method according to an embodiment of the present application;
fig. 2 is a flowchart illustrating a process of sending a message according to a message type according to an embodiment of the present application;
FIG. 3 is a flowchart illustrating interaction among a message publisher, a message server, and a recipient according to an embodiment of the present application;
fig. 4 is a block diagram illustrating a message server according to an embodiment of the present application;
FIG. 5 is a block diagram of a message server according to another embodiment of the present application;
fig. 6 is a schematic diagram of a message server according to another embodiment of the present application.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.
The method for pushing the notification message can set the template message, format and define multi-language content, set whether auxiliary parameters such as the need to go to the local time, judge the language type of the user when the notification message is sent by the server, convert the notification message into the local time and then enter a queue to wait for sending the notification message for sending according to the local time, and solve the problem of sending the notification message in multiple modes, multiple languages and multiple time zones.
The following describes the implementation process of the method of the present application in detail by way of examples.
Referring to fig. 1, which shows a flowchart of a notification message pushing method according to an embodiment of the present application, the embodiment may specifically include the following steps:
step 100, receiving a notification message, wherein the notification message comprises a message header, a parameter key value and a template number corresponding to each terminal type;
the message server receives the notification message sent by the publisher as shown in the following table 1:
TABLE 1 Notification message schematic
As shown in table 1, the notification message may specifically include a message header, a parameter key value, and a template number (terminal information) corresponding to each terminal type, where,
the message header includes: a message publisher identifier, a recipient identifier, a message type, whether a local time zone is used, a timed sending time, a default language type and a default terminal type;
the parameter key values include parameters and key values corresponding to the parameters, for example, in table 1, the key value corresponding to the parameter USER is Jerry, the key value corresponding to the parameter NAME is American football jersey and pan, and the key value corresponding to the parameter URL is Jerryhttp://www.XXXX.com/1574824.html；
The template number corresponding to each terminal type, i.e. the terminal information in table 1, the terminal types are divided into PC, Mobile and IPad, and different terminal types correspond to different template numbers.
It should be noted that, the message publisher may first send the template number corresponding to each terminal type and the template message corresponding to each template number to the message server for registration, and the message server stores the template number, so that the message publisher may directly call the template for use according to the template number next time. Namely, before the receiving the notification message, the following steps can be further included:
step one, receiving a template registration message, wherein the template registration message comprises: the template information comprises template information of different language types;
the template registration message is shown in table 2:
TABLE 2 template registration message schematic
As shown in table 2, the template number corresponding to the terminal type PC is 1001, and the template message corresponding to the template number 1001 includes a chinese template message (# USER # issues a new product # NAME #, and the address is # URL #) and an english template message (# USER # Published a new product: # NAME #, clickhere: # URL #). It should be noted that the template message may include template messages of various language types, and this embodiment only takes the chinese template message and the english template message as examples for description, and may also include template messages of french, korean, and the like, and this embodiment should not be construed as a limitation to the present application.
And step two, registering and storing the template registration message in a template registration library.
The message server stores the template registration message in a template registry, such that the template registry of the message server stores a plurality of template registration messages.
It should be noted that, the message publisher may first send the template registration message to the message server for registration in the manner of table 2, or may include new template information when sending the notification message, as shown in table 3 below:
TABLE 3 new template information included when sending notification messages
The message header in table 3 is identical to the message header in table 1 (not shown), and in table 3, both template 1001 and template 1002 are new template information (not previously registered in the message server) and thus contain specific template contents, while template 3078 has been previously registered in the message server and thus given a template number, and the message server can find the template content corresponding to template number 3078 from the template registry.
In a preferred embodiment of the present application, before the message server receives the template registration message, the method may further include:
and receiving the message publisher identification, and registering and storing the message publisher identification in an identification registry.
After the message server receives the notification message sent by the message publisher, it needs to verify the message publisher, that is, after the message server receives the notification message, it further includes:
analyzing the message header to obtain a message publisher identification, verifying in an identification registry according to the publisher identification, and if the message publisher identification obtained by analyzing the message header is in the identification registry, indicating that the verification is passed; if the message publisher identification obtained by analyzing the message header is not in the identification registry, the verification fails, and the notification message is not pushed for the message publisher with the failed verification.
102, analyzing the message header of the notification message to obtain a receiver identifier, and searching a terminal type and a language type corresponding to the receiver identifier;
before the message server receives the notification message in the embodiment of the application, the method further includes the following steps:
step one, receiving user login information, wherein the user login information comprises: user authentication information, a user name, a terminal type, a language type, a time zone in which the user is located and last login time;
as shown in table 4 below, the user login information may use a user name as the user authentication information, or use a user name and a corresponding password as the user authentication information, which is not limited in this embodiment.
In addition, the user sending the user login information in this embodiment may be a recipient designated by the recipient identifier of the notification message, and receive the push message sent by the server. In addition, the recipient identifier of the notification message may adopt a user name in the user login information, and it should be noted that, in this embodiment, the recipient identifier is adopted instead of the recipient terminal, because the user corresponding to the recipient identifier may use the same user name to log in different types of terminals, the types of the logged-in terminals are different, and the display modes of the received push message may also be different. That is, one recipient identification may correspond to a plurality of terminals.
| User name | Terminal type | Language type | Time zone of residence | Last time of logging in |
| Usr1 | PC | Chinese character | GMT+8 | |
| Usr2 | Mobile | English | GMT-6 | |
| Usr3 | Ipad | French language | GMT+1 |
TABLE 4 user Login information
Step two, verifying according to the user verification information, and judging whether the user name is located in an online information table or not for the user passing the verification;
the online information table records information such as the user name, the terminal type, the language type, the time zone in which the user is located, the last login time and the like of the current online user, so that whether the user is online can be judged according to whether the user name exists in the online information table.
Step three, if the user name is located in an online information table, updating a terminal type, a language type, a time zone where the user name is located and the last login time corresponding to the user name in the online information table;
for the user with the user name in the online information table, the user name is indicated to be online before, and the message server updates the information of the user, such as the terminal type, the language type, the time zone where the user is located, the last login time and the like, so that the validity of the information of the terminal type, the language type and the like stored by the message server is ensured. If the user changes the setting of the information such as the terminal type, the language type and the like, the message is also required to be sent to the message server, and the message server stores the message.
And step four, if the user name is not located in an online information table, storing the user login information into the online information table.
And for the user whose user name is not in the online information table, indicating that the user is not online before, and inserting the login information of the user into the online information table for storage as a newly logged-in user.
Through the description of the first step to the third step, the message server stores the login information such as the terminal type, the language type and the like of the current online User, the step 102 analyzes the message header of the notification message shown in the table 1 to obtain the recipient identification User1, and then the terminal type corresponding to the User1 is found from the online information table to be PC, and the language type is Chinese. It should be noted that, in this embodiment, the user name of the recipient may be used as the recipient identifier, and the terminal type and the language type corresponding to the recipient identifier (user name) are searched in the online information table.
104, calling corresponding template information from a template registry according to the template number corresponding to the searched terminal type, wherein the template information comprises template information of different language types;
if the user name corresponding to the receiver identification is on line currently, the corresponding login information such as the terminal type, the language type and the like of the user can be searched from the on-line information table. For example, the found terminal type is PC, the corresponding template number is 1001 can be clearly found from the notification message diagram shown in table 1, and then a specific template message corresponding to the template number 1001 can be called from the template registry (see table 2) as shown in table 5:
TABLE 5 template message corresponding to template number 1001
Step 106, replacing parameters in the template message according to the parameter key values, and generating a push message according to the searched language type;
according to the parameter keys Jerry (USER), American football jersey and pot (NAME) in Table 1http://www.XXXX.com/1574824.html(URL) replaces the parameters USER, NAME and URL in the template message corresponding to the template number 1001 in table 5, with the following results:
chinese: jerry issued a new product, American football jersey and pot, addressed ashttp://www.XXXX.com/1574824.html；
English: jerry Published a new product: american football jersey and pant, click here:http://www.XXXX.com/1574824.html。
step 102, parsing the message header of the notification message shown in table 1 to obtain the recipient identification User1, and then finding out that the terminal type corresponding to User1 is PC and the language type is chinese from the online information table. Therefore, selecting the Chinese template generates a notification message: jerry issued a new product, American football jersey and pot, with the address beinghttp://www.XXXX.com/1574824.html。
If the recipient identification User7 is not online currently, the corresponding login information such as the terminal type and language type of the User cannot be searched from the online information table, at this time, the message header of the notification message shown in table 1 is analyzed to obtain the default terminal type (mobile phone) and default language type (English), and the push message generated according to the default terminal type and default language type is as follows:
Latest Product：<a href＝http://www.XXXX.com/1574824.html>Americanfootball jersey and pant</a>(Jerry)。
step 108, sending the push message to the terminal where the receiver is located.
The push message generated in step 106 is sent to the terminal where the receiver is located, and the push message can be displayed at the terminal where the receiver is located.
It should be noted that, for the receiver, a user name may be used to log in different types of terminals, the types of the logged-in terminals are different, and the display modes of the received push message may also be different.
For example, if the user logs in at the PC, the received chinese push message is:
jerry issued a new product, American football jersey and pot, addressed ashttp://www.XXXX.com/1574824.html；
If the user logs in the mobile phone, the received Chinese message is as follows: the latest product is as follows:<ahref＝http://www.XXXX.com/1574824.html>American football jersey andpant</a>(Jerry)。
therefore, the notification message pushing method provided by the embodiment of the application can be in a self-adaptive mode, namely different message display can be carried out according to different terminal types. And the template message is set, and only the parameters in the template message need to be replaced according to the parameter key values when the push message is generated. In addition, the embodiment of the application can also adapt to languages, namely, when the message server pushes the message, the message server can select the template of the corresponding language according to the language type of the receiver stored in the online information table to generate the push message, and only the push message of the corresponding language is sent to the terminal, so that the multi-language capability is provided. Correspondingly, the set template has multiple languages. The template of the message format can also greatly improve the sending efficiency of the message for the same type of message.
In a preferred embodiment of the present application, the message server may send the push message to the terminal where the recipient is located in different manners according to the message type, specifically as follows:
the message type may be obtained by parsing the message header shown in table 1, and the message type includes: online messages, normal messages, and timed messages. Wherein,
online messaging: the description is only sent when the user is online, and the description is ignored when the user is not online, that is, the description is not sent when the user is not online. And if the user name corresponding to the receiver is found from the online information table, the message is put into a sending queue for sending, and if the user name cannot be found, the message is ignored.
Specifically, when the message type of the notification message is an online message, the sending the push message to the terminal where the recipient is located includes: searching the receiver identification from an online information table, if the search is successful, putting the push message into a sending queue, and sending the push message to a terminal where the receiver is located; if the search fails, the transmission is finished.
And (3) common message: the description can be sent when the user is online, and if the user is not online, the user can wait for the next login (the user is online when logging in next time) to send. Searching the user from the online information table, and sending the message in a sending queue; and if the user does not find the information, the information is put into an offline information queue and is sent when the user logs in next time.
Specifically, when the message type of the notification message is an ordinary message, the sending the push message to the terminal where the recipient is located may include:
searching the receiver identification from an online information table, if the search is successful, putting the push message into a sending queue, and sending the push message to a terminal where the receiver is located; and if the search fails, putting the push message into an offline queue, and sending the push message when the receiver identification is on line.
Timing messages: the message header is described as having set a time for the timer transmission, and the message needs to be transmitted at the timer transmission time. And the timing message also has the timing transmission time whether to adopt the local time zone or adopt the local time zone to transmit, if adopt the local, still need to carry on the time conversion according to the user's time zone in the online information table, convert the local transmission time into the corresponding local time. The timing message is sent to the above steps 104, 105 and 106 after the timing transmission time is reached.
Specifically, before the invoking of the corresponding template message from the template registry according to the template number corresponding to the found terminal type, the method may further include:
analyzing the message header of the notification message to obtain the message type;
when the message type of the notification message is a timing message, analyzing a message header to obtain timing sending time and whether to use a local time zone for pushing;
if the local time zone is used for pushing, searching the local time zone corresponding to the receiver identification from an online information table, and if the searching is successful, converting the timing sending time into the corresponding local time according to the local time zone; setting a timer according to the corresponding local time, adding the notification message into a timing queue, and executing the step of calling the corresponding template message from the template registry according to each template number when the corresponding local time is reached; if the search fails, executing a step of pushing without using the local time zone;
if the local time zone is not used for pushing, setting a timer according to the timing sending time, adding the notification message into a timing queue, and executing the step of calling the corresponding template message from the template registry according to each template number when the timing sending time is reached.
The embodiment can achieve the purpose of adapting to the time zone, and for the notification message that requires to adapt to the local time zone, for example, the message that the user needs to see at 8 am of the day, the sending time can be adaptively adjusted according to the time zone information saved when the user logs in.
The different ways of sending the online messages, the ordinary messages and the timing messages described above can be understood with reference to fig. 2. As shown in fig. 2, the method may specifically include the following steps:
step 200, receiving a notification message;
step 201, verifying the message publisher identification;
step 202, for the notification message passing the verification, determining whether the message type is a timing message, if so, executing step 203, otherwise, executing step 207;
step 203, if the message type of the notification message is a timing message, determining whether to use local time zone push, if so, executing step 204, otherwise, executing step 206;
step 204, searching a time zone corresponding to the user from the online information table, if the searching is successful, executing step 205, otherwise, executing step 206;
step 205, converting the timed sending time into local time according to the searched local time zone;
step 206, setting a timer, and putting the notification message into a timing queue;
step 207, after the timing sending time is reached, step 208 is executed;
step 208, searching the corresponding terminal type and language type from the online information table, if the search is successful, executing step 209, otherwise executing step 212;
step 209, obtaining the message content corresponding to the terminal type and the language type, and generating a push message;
step 210, putting the push message into a message queue;
step 211, calling the sending interfaces to send in sequence;
step 212, judging whether the message type of the notification message is an online message, if so, finishing sending, otherwise, executing step 213;
step 213, obtaining the message content corresponding to the default terminal type and language type, and generating a push message;
step 214, putting the push message into an offline queue;
step 215, when waiting for the user to log in next time, putting the push message into the message queue.
The interaction process among the message publisher, the message server, and the recipient is described in detail below. Referring to fig. 3, a message publisher a calls a message interface to send a multi-style notification message to a message server B, the message server B queries the language type and the terminal type of a user according to an online information table, then parses a message header of the notification message to obtain a template number corresponding to a terminal of a receiver, then obtains a template message from a template registry according to the language type of the user, replaces a parameter key value, generates a push message, and sends the push message to a corresponding receiver C or receiver D. The receiver C or D can log in the message server B to receive the push message sent by the message server B.
If the notification message does not specify the template number corresponding to different terminal types, the template corresponding to the terminal type and the language type of the user is directly obtained from the template library and sent. If the message content of the corresponding language type is not found, the message can be sent according to the default language type; similarly, if the message content corresponding to the terminal type is not found, the message content may be sent according to the default terminal type. If the default language type and the default terminal type are not set, the transmission request is ignored.
It should be noted that the foregoing method embodiments are described as a series of acts or combinations for simplicity in explanation, but it should be understood by those skilled in the art that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.
Based on the description of the above method embodiment, the present application also provides a corresponding message server to implement the content described in the above method embodiment.
Referring to fig. 4, a block diagram of a structure of a message server according to an embodiment of the present application is shown, where the embodiment may specifically include: a notification message receiving module 400, a lookup module 401, a calling module 402, a generating module 403, and a sending module 404, wherein,
a notification message receiving module 400, configured to receive a notification message, where the notification message includes a message header, a parameter key value, and a template number corresponding to each terminal type;
the searching module 401 is configured to parse the message header of the notification message to obtain a recipient identifier, and search for a terminal type and a language type corresponding to the recipient identifier;
a calling module 402, configured to call a corresponding template message from a template registry according to a template number corresponding to a found terminal type, where the template message includes template messages of different language types;
a generating module 403, configured to replace a parameter in the template message according to the parameter key value, and generate a push message according to the found language type;
a sending module 404, configured to send the push message to a terminal where the recipient is located.
In a preferred embodiment of the present application, the message server further includes:
a template registration module 405, configured to receive a template registration message before receiving the notification message, and register and store the template registration message in a template registry; the template registration message includes: the template information comprises template information of different language types.
In the preferred embodiment shown in fig. 5 of the present application, the message server further includes:
a login information receiving module 406, configured to receive user login information before receiving the notification message, where the user login information includes: user authentication information, a user name, a terminal type, a language type, a time zone in which the user is located and last login time;
the user verification module 407 is configured to perform verification according to the user verification information, and determine whether the user name is located in an online information table for a user who passes the verification;
an updating module 408, configured to update, when the user name is located in the online information table, a terminal type, a language type, a time zone where the user name is located, and last login time that correspond to the user name in the online information table;
a saving module 409, configured to save the user login information to the online information table when the user name is not located in the online information table.
In the preferred embodiment shown in fig. 5 of the present application, the message server further includes:
a message header parsing module 410, configured to parse a message header of the notification message to obtain a message type before the corresponding template message is called from the template registry according to the template number corresponding to the found terminal type;
the message header parsing module 410 is further configured to, when the message type of the notification message is a timing message, parse the message header to obtain a timing sending time, and determine whether to use a local time zone for pushing;
a local push module 411, configured to search a local time zone corresponding to the recipient identifier from an online information table when pushing is performed using the local time zone, and convert the timing sending time into a corresponding local time according to the local time zone when the search is successful; setting a timer according to the corresponding local time, adding the notification message into a timing queue, and calling the corresponding template message from a template registry according to each template number by the calling module when the corresponding local time is reached;
the local pushing module 412 is configured to set a timer according to the timing sending time when pushing is performed without using the local time zone or when the local pushing module fails to find the local time zone corresponding to the recipient identifier from the online information table, add the notification message to the timing queue, and when the timing sending time is reached, the invoking module invokes the corresponding template message from the template registry according to each template number.
In another preferred embodiment of the present application, the searching module 401 may search for the recipient identifier from an online information table;
the message header parsing module 410 is further configured to, when the recipient identifier is not found in the online information table, parse the message header of the notification message to obtain a default terminal type and a default language type, and generate a push message according to the default terminal type and the default language type;
in another preferred embodiment of the present application, the sending module 404 is further configured to, when the message type of the notification message is an online message, search for the identifier of the recipient from an online information table, and if the search is successful, place the push message into a sending queue and send the push message to a terminal where the recipient is located; if the search fails, the transmission is finished.
In another preferred embodiment of the present application, the sending module 404 is further configured to, when the message type of the notification message is a common message, search for the identifier of the recipient from an online information table, and if the search is successful, place the push message into a sending queue and send the push message to a terminal where the recipient is located; and if the search fails, putting the push message into an offline queue, and sending the push message when the receiver identification is on line.
As for the above message server embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and relevant points can be referred to the partial description of the method embodiment shown in fig. 1.
The interaction process among the message server, the message publisher and the recipient is described below with reference to fig. 6, as shown in fig. 6:
the server is composed of a login service, a message interface (comprising a template registration interface and a message sending interface), a timing queue, an offline message queue, a sending interface, a sending service, a user online information table and a template registry. The login service may be implemented in the login information receiving module 406, the user authentication module 407, the update module 408, and the storage module 409, and specifically, the login service provides user authentication and records of additional information. The message interface is provided for the application side to call, receive and process the sending request and the configuration information of the multi-style notification information. The timing queue is used for storing messages needing to be sent regularly. The send queue holds the contents of messages that will need to be sent to ensure that they are not lost when the number of sends is large. And the sending interface completes the actual sending task and sequentially sends the messages in the sending queue to the terminal of the receiver B. The off-line message queue stores the common messages which need to be sent to the receiver, but the receiver is not on line currently, when the receiver logs in next time, the off-line message queue sends the stored common messages to the sending queue, and then the sending queue calls the sending interface to send the common messages to the terminal where the receiver is located. In addition, both receiver a and receiver B can log in through the login service, and can receive messages after logging in.
The message server provided by the embodiment of the application can be in a self-adaptive mode, namely different message display can be carried out according to different terminal types, and due to the fact that the template message is set, different templates can be directly called to generate the push message to be sent, and the workload is reduced when the message display is adjusted. And the template message is set, and only the parameters in the template message need to be replaced according to the parameter key values when the push message is generated. In addition, the embodiment of the application can also adapt to languages, namely, when the message server pushes the message, the message server can select the template of the corresponding language according to the language type of the receiver stored in the online information table to generate the push message, and only the push message of the corresponding language is sent to the terminal, so that the multi-language capability is provided. Correspondingly, the set template has multiple languages. The template of the message format can also greatly improve the sending efficiency of the message for the same type of message.
As for the above message server embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and relevant points can be referred to the partial description of the method embodiment shown in fig. 1.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As is readily imaginable to the person skilled in the art: any combination of the above embodiments is possible, and thus any combination between the above embodiments is an embodiment of the present application, but the present disclosure is not necessarily detailed herein for reasons of space.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
The above detailed description is given to a notification message pushing method and a message server provided by the present application, and a specific example is applied in the present application to explain the principle and the implementation of the present application, and the description of the above embodiment is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (13)
1. A method for pushing a notification message, comprising:
receiving a notification message, wherein the notification message comprises a message header, a parameter key value and a template number corresponding to each terminal type;
analyzing the message header of the notification message to obtain a receiver identification, and searching a terminal type and a language type corresponding to the receiver identification;
calling corresponding template information from a template registry according to the template number corresponding to the searched terminal type, wherein the template information comprises template information of different language types;
replacing parameters in the template message according to the parameter key values, and generating a push message according to the searched language type;
and sending the push message to a terminal where the receiver is located.
2. The method of claim 1, wherein prior to receiving the notification message, further comprising:
receiving a template registration message, the template registration message comprising: the template information comprises template information of different language types;
and registering and storing the template registration message in a template registry.
3. The method of claim 1, wherein prior to receiving the notification message, further comprising:
receiving user login information, wherein the user login information comprises: user authentication information, a user name, a terminal type, a language type, a time zone in which the user is located and last login time;
verifying according to the user verification information, and judging whether the user name is located in an online information table or not for the user passing the verification;
if the user name is located in an online information table, updating a terminal type, a language type, a time zone where the user name is located and the last login time corresponding to the user name in the online information table;
and if the user name is not located in an online information table, storing the user login information into the online information table.
4. The method of claim 3, wherein the searching for the terminal type and the language type corresponding to the recipient identifier comprises:
looking up the recipient identification from the presence information table;
the method further comprises the following steps:
and when the receiver identification cannot be searched in the online information table, analyzing the message header of the notification message to obtain a default terminal type and a default language type, and generating a push message according to the default terminal type and the default language type.
5. The method according to claim 3, wherein before the invoking of the corresponding template message from the template registry according to the template number corresponding to the found terminal type, further comprises:
analyzing the message header of the notification message to obtain the message type;
when the message type of the notification message is a timing message, analyzing a message header to obtain timing sending time and whether to use a local time zone for pushing;
if the local time zone is used for pushing, searching the local time zone corresponding to the receiver identification from an online information table, and if the searching is successful, converting the timing sending time into the corresponding local time according to the local time zone; setting a timer according to the corresponding local time, adding the notification message into a timing queue, and executing the step of calling the corresponding template message from the template registry according to each template number when the corresponding local time is reached; if the search fails, executing a step of pushing without using the local time zone;
if the local time zone is not used for pushing, setting a timer according to the timing sending time, adding the notification message into a timing queue, and executing the step of calling the corresponding template message from the template registry according to each template number when the timing sending time is reached.
6. The method of claim 5, wherein when the message type of the notification message is an online message, the sending the push message to the terminal where the recipient is located comprises:
searching the receiver identification from an online information table, if the search is successful, putting the push message into a sending queue, and sending the push message to a terminal where the receiver is located; if the search fails, the transmission is finished.
7. The method according to claim 5, wherein when the message type of the notification message is a normal message, the sending the push message to the terminal where the recipient is located comprises:
searching the receiver identification from an online information table, if the search is successful, putting the push message into a sending queue, and sending the push message to a terminal where the receiver is located; and if the search fails, putting the push message into an offline queue, and sending the push message when the receiver identification is on line.
8. A message server, comprising:
a notification message receiving module, configured to receive a notification message, where the notification message includes a message header, a parameter key value, and a template number corresponding to each terminal type;
the searching module is used for analyzing the message header of the notification message to obtain a receiver identifier and searching the terminal type and the language type corresponding to the receiver identifier;
the calling module is used for calling corresponding template information from the template registry according to the template number corresponding to the searched terminal type, wherein the template information comprises template information of different language types;
the generating module is used for replacing parameters in the template message according to the parameter key values and generating a push message according to the searched language type;
and the sending module is used for sending the push message to the terminal where the receiver is located.
9. The message server of claim 8, further comprising:
the template registration module is used for receiving the template registration message before receiving the notification message, registering and storing the template registration message in a template registration library; the template registration message includes: the template information comprises template information of different language types.
10. The message server of claim 8, further comprising:
a login information receiving module, configured to receive user login information before receiving a notification message, where the user login information includes: user authentication information, a user name, a terminal type, a language type, a time zone in which the user is located and last login time;
the user authentication module is used for authenticating according to the user authentication information and judging whether the user name is located in an online information table or not for the user passing the authentication;
the updating module is used for updating the terminal type, the language type, the time zone in which the user name is located and the last login time corresponding to the user name in the online information table when the user name is located in the online information table;
and the storage module is used for storing the user login information into the online information table when the user name is not located in the online information table.
11. The message server of claim 10, further comprising:
a message header analyzing module, configured to analyze a message header of the notification message to obtain a message type before calling a corresponding template message from a template registry according to a template number corresponding to the found terminal type;
the message header analyzing module is further used for analyzing the message header to obtain the timing sending time and whether to use the local time zone for pushing when the message type of the notification message is the timing message;
the local pushing module is used for searching a local time zone corresponding to the receiver identification from an online information table when the local time zone is used for pushing, and converting the timing sending time into corresponding local time according to the local time zone when the searching is successful; setting a timer according to the corresponding local time, adding the notification message into a timing queue, and calling the corresponding template message from a template registry according to each template number by the calling module when the corresponding local time is reached;
and the local pushing module is used for pushing without using a local time zone or when the local pushing module fails to search the local time zone corresponding to the receiver identifier from an online information table, setting a timer according to the timed sending time, adding the notification message into a timed queue, and calling the corresponding template message from the template registry according to each template number when the timed sending time is reached.
12. The message server of claim 11, wherein:
the sending module is further configured to, when the notification message is an online message, search for the recipient identifier from an online information table, and if the search is successful, place the push message in a sending queue and send the push message to a terminal where the recipient is located; if the search fails, the transmission is finished.
13. The message server of claim 11, wherein:
the sending module is further configured to, when the notification message is a general message, search for the recipient identifier from an online information table, and if the search is successful, place the push message in a sending queue and send the push message to a terminal where the recipient is located; and if the search fails, putting the push message into an offline queue, and sending the push message when the receiver identification is on line.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310048776.6A CN103973461A (en) | 2013-02-06 | 2013-02-06 | Notification message pushing method and message server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310048776.6A CN103973461A (en) | 2013-02-06 | 2013-02-06 | Notification message pushing method and message server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103973461A true CN103973461A (en) | 2014-08-06 |
Family
ID=51242531
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310048776.6A Pending CN103973461A (en) | 2013-02-06 | 2013-02-06 | Notification message pushing method and message server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103973461A (en) |
Cited By (38)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104917834A (en) * | 2015-06-09 | 2015-09-16 | 北京金山安全软件有限公司 | Information pushing method and device |
| CN105162838A (en) * | 2015-07-30 | 2015-12-16 | 青岛海尔智能家电科技有限公司 | Message pushing method, and method and device for receiving pushed message |
| CN105578431A (en) * | 2016-01-20 | 2016-05-11 | 北京智驾互联信息服务有限公司 | Reminding message sending device and method |
| CN105635291A (en) * | 2015-12-31 | 2016-06-01 | 联想(北京)有限公司 | Information pushing method, information pushing device, information displaying method and information displaying device |
| CN105763584A (en) * | 2014-12-17 | 2016-07-13 | 金蝶软件（中国）有限公司 | Message processing method and apparatus |
| CN106201543A (en) * | 2016-07-20 | 2016-12-07 | 青岛海信电器股份有限公司 | The display packing of notification message and smart machine in smart machine |
| CN106533903A (en) * | 2016-10-28 | 2017-03-22 | 北京奇虎科技有限公司 | Long connection message release method, platform device and system |
| CN106780162A (en) * | 2016-12-19 | 2017-05-31 | 湖北省建筑工程质量监督检验测试中心 | A kind of hot rolled ribbed bars testing process real-time tracking system and method |
| CN107302597A (en) * | 2017-08-17 | 2017-10-27 | 北京小度信息科技有限公司 | Message official documents and correspondence method for pushing and device |
| CN107465759A (en) * | 2017-09-07 | 2017-12-12 | 武汉楚鼎信息技术有限公司 | A kind of message server, message issuing method and terminal |
| CN107592334A (en) * | 2017-07-17 | 2018-01-16 | 阿里巴巴集团控股有限公司 | A kind of information popularization method, apparatus and equipment |
| CN107748688A (en) * | 2017-09-30 | 2018-03-02 | 微梦创科网络科技（中国）有限公司 | A kind of information displaying method and device |
| CN108023903A (en) * | 2016-10-31 | 2018-05-11 | 北京乐知行软件有限公司 | One kind notice dissemination method and system |
| CN108768837A (en) * | 2018-05-31 | 2018-11-06 | 中国建设银行股份有限公司 | Message treatment method and relevant apparatus |
| CN109190075A (en) * | 2018-08-20 | 2019-01-11 | 国云科技股份有限公司 | Message sending method based on multiple cloud platform message types |
| CN109347898A (en) * | 2018-08-20 | 2019-02-15 | 深圳市梦网科技发展有限公司 | Scene information sending method, display method, server and mobile terminal |
| CN109558199A (en) * | 2018-11-29 | 2019-04-02 | 广州市百果园信息技术有限公司 | A kind of information-pushing method, device, equipment and storage medium |
| CN109672608A (en) * | 2018-12-21 | 2019-04-23 | 腾讯音乐娱乐科技（深圳）有限公司 | The method for sending message according to the time |
| CN109815408A (en) * | 2019-02-01 | 2019-05-28 | 百度在线网络技术（北京）有限公司 | Method and apparatus for pushed information |
| WO2019105318A1 (en) * | 2017-11-28 | 2019-06-06 | 阿里巴巴集团控股有限公司 | Method for processing message time and related device |
| CN110012051A (en) * | 2018-12-19 | 2019-07-12 | 香港乐蜜有限公司 | Notify method for pushing, device, terminal device, server and system |
| CN110049118A (en) * | 2019-04-12 | 2019-07-23 | 深圳乐信软件技术有限公司 | Information push method, device, equipment and storage medium |
| CN110460512A (en) * | 2019-08-01 | 2019-11-15 | 北京达佳互联信息技术有限公司 | System message generation method, device, server and storage medium |
| CN110460602A (en) * | 2019-08-15 | 2019-11-15 | 中国银行股份有限公司 | It can support the SWIFT message processing method and system of multi-bank zone |
| CN110533456A (en) * | 2019-07-30 | 2019-12-03 | 威富通科技有限公司 | A kind of coupon information method for pushing, system and server |
| CN110572434A (en) * | 2019-08-05 | 2019-12-13 | 威富通科技有限公司 | Push method and device of voice broadcast message, push server and storage medium |
| CN110601952A (en) * | 2018-06-12 | 2019-12-20 | 北京京东尚科信息技术有限公司 | Multi-channel message notification sending method and device |
| CN111049871A (en) * | 2018-10-15 | 2020-04-21 | 广州虎牙信息科技有限公司 | Message pushing method, message management system, server and computer storage medium |
| CN111049727A (en) * | 2019-11-22 | 2020-04-21 | 用友网络科技股份有限公司 | Message processing method, message processing apparatus, and computer-readable storage medium |
| CN111049723A (en) * | 2018-10-15 | 2020-04-21 | 广州虎牙信息科技有限公司 | Message pushing method, message management system, server and computer storage medium |
| CN111756620A (en) * | 2020-06-28 | 2020-10-09 | 中国银行股份有限公司 | Message pushing method and device |
| CN111935111A (en) * | 2020-07-27 | 2020-11-13 | 北京字节跳动网络技术有限公司 | Interaction method and device and electronic equipment |
| CN112866979A (en) * | 2020-12-31 | 2021-05-28 | 恒安嘉新（北京）科技股份公司 | User information association method, device, equipment and medium based on 5G service interface |
| CN112925512A (en) * | 2021-01-29 | 2021-06-08 | 北京字节跳动网络技术有限公司 | Message sending method and device, electronic equipment and storage medium |
| CN112995248A (en) * | 2019-12-12 | 2021-06-18 | 阿里巴巴集团控股有限公司 | Information pushing method, device and equipment |
| WO2021179265A1 (en) * | 2020-03-12 | 2021-09-16 | 深圳市欢太科技有限公司 | Information pushing method and apparatus, server, and storage medium |
| CN113992622A (en) * | 2021-09-08 | 2022-01-28 | 上海易立德信息技术股份有限公司 | Multi-template aggregation message notification sending system and method based on unified model |
| CN114390452A (en) * | 2022-01-18 | 2022-04-22 | 平安科技（深圳）有限公司 | Message sending method and related equipment |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030106022A1 (en) * | 2001-12-05 | 2003-06-05 | Goodacre Anthony John | Outputting dynamic local content on mobile devices |
| CN1863174A (en) * | 2006-01-12 | 2006-11-15 | 华为技术有限公司 | Instant message system and message processing method |
| CN101175234A (en) * | 2006-10-31 | 2008-05-07 | 报联新动力（北京）科技有限公司 | System and method for implementing data propelling movement by mobile information terminal |
| CN101656928A (en) * | 2008-08-20 | 2010-02-24 | 华为软件技术有限公司 | Short message processing method, system and assembly program unit |
| CN101997894A (en) * | 2009-08-14 | 2011-03-30 | 阿里巴巴集团控股有限公司 | Information pushing method, system and network system thereof |
| CN102263851A (en) * | 2010-05-31 | 2011-11-30 | 北京迅捷英翔网络科技有限公司 | Message conversion method |
| CN102480674A (en) * | 2010-11-26 | 2012-05-30 | 中国移动通信集团北京有限公司 | Data push method, state awareness and push module, and data push system |
| CN102546471A (en) * | 2011-12-31 | 2012-07-04 | 深圳中兴网信科技有限公司 | Message sending method for serving overall process of business travel |
| CN102724324A (en) * | 2012-06-28 | 2012-10-10 | 用友软件股份有限公司 | Information pushing and integrating device and information pushing and integrating method |
-
2013
- 2013-02-06 CN CN201310048776.6A patent/CN103973461A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030106022A1 (en) * | 2001-12-05 | 2003-06-05 | Goodacre Anthony John | Outputting dynamic local content on mobile devices |
| CN1863174A (en) * | 2006-01-12 | 2006-11-15 | 华为技术有限公司 | Instant message system and message processing method |
| CN101175234A (en) * | 2006-10-31 | 2008-05-07 | 报联新动力（北京）科技有限公司 | System and method for implementing data propelling movement by mobile information terminal |
| CN101656928A (en) * | 2008-08-20 | 2010-02-24 | 华为软件技术有限公司 | Short message processing method, system and assembly program unit |
| CN101997894A (en) * | 2009-08-14 | 2011-03-30 | 阿里巴巴集团控股有限公司 | Information pushing method, system and network system thereof |
| CN102263851A (en) * | 2010-05-31 | 2011-11-30 | 北京迅捷英翔网络科技有限公司 | Message conversion method |
| CN102480674A (en) * | 2010-11-26 | 2012-05-30 | 中国移动通信集团北京有限公司 | Data push method, state awareness and push module, and data push system |
| CN102546471A (en) * | 2011-12-31 | 2012-07-04 | 深圳中兴网信科技有限公司 | Message sending method for serving overall process of business travel |
| CN102724324A (en) * | 2012-06-28 | 2012-10-10 | 用友软件股份有限公司 | Information pushing and integrating device and information pushing and integrating method |
Cited By (56)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105763584A (en) * | 2014-12-17 | 2016-07-13 | 金蝶软件（中国）有限公司 | Message processing method and apparatus |
| CN104917834A (en) * | 2015-06-09 | 2015-09-16 | 北京金山安全软件有限公司 | Information pushing method and device |
| CN104917834B (en) * | 2015-06-09 | 2018-07-10 | 北京金山安全软件有限公司 | Information push method and device |
| CN105162838A (en) * | 2015-07-30 | 2015-12-16 | 青岛海尔智能家电科技有限公司 | Message pushing method, and method and device for receiving pushed message |
| CN105635291A (en) * | 2015-12-31 | 2016-06-01 | 联想(北京)有限公司 | Information pushing method, information pushing device, information displaying method and information displaying device |
| CN105578431B (en) * | 2016-01-20 | 2019-09-06 | 北京智驾互联信息服务有限公司 | Reminder message sending device and method |
| CN105578431A (en) * | 2016-01-20 | 2016-05-11 | 北京智驾互联信息服务有限公司 | Reminding message sending device and method |
| CN106201543A (en) * | 2016-07-20 | 2016-12-07 | 青岛海信电器股份有限公司 | The display packing of notification message and smart machine in smart machine |
| CN106201543B (en) * | 2016-07-20 | 2020-03-24 | 青岛海信电器股份有限公司 | Display method of notification message in intelligent device and intelligent device |
| CN106533903A (en) * | 2016-10-28 | 2017-03-22 | 北京奇虎科技有限公司 | Long connection message release method, platform device and system |
| CN106533903B (en) * | 2016-10-28 | 2019-12-24 | 北京奇虎科技有限公司 | A persistent connection message publishing method, platform device and system |
| CN108023903A (en) * | 2016-10-31 | 2018-05-11 | 北京乐知行软件有限公司 | One kind notice dissemination method and system |
| CN108023903B (en) * | 2016-10-31 | 2021-08-17 | 北京讯飞乐知行软件有限公司 | Notification issuing method and system |
| CN106780162A (en) * | 2016-12-19 | 2017-05-31 | 湖北省建筑工程质量监督检验测试中心 | A kind of hot rolled ribbed bars testing process real-time tracking system and method |
| CN107592334A (en) * | 2017-07-17 | 2018-01-16 | 阿里巴巴集团控股有限公司 | A kind of information popularization method, apparatus and equipment |
| CN107302597B (en) * | 2017-08-17 | 2020-06-16 | 北京星选科技有限公司 | Message file pushing method and device |
| CN107302597A (en) * | 2017-08-17 | 2017-10-27 | 北京小度信息科技有限公司 | Message official documents and correspondence method for pushing and device |
| CN107465759A (en) * | 2017-09-07 | 2017-12-12 | 武汉楚鼎信息技术有限公司 | A kind of message server, message issuing method and terminal |
| CN107465759B (en) * | 2017-09-07 | 2019-03-12 | 武汉楚鼎信息技术有限公司 | A kind of message server, message issuing method and terminal |
| CN107748688A (en) * | 2017-09-30 | 2018-03-02 | 微梦创科网络科技（中国）有限公司 | A kind of information displaying method and device |
| CN107748688B (en) * | 2017-09-30 | 2021-05-11 | 微梦创科网络科技（中国）有限公司 | Information display method and device |
| WO2019105318A1 (en) * | 2017-11-28 | 2019-06-06 | 阿里巴巴集团控股有限公司 | Method for processing message time and related device |
| CN108768837A (en) * | 2018-05-31 | 2018-11-06 | 中国建设银行股份有限公司 | Message treatment method and relevant apparatus |
| CN110601952B (en) * | 2018-06-12 | 2022-12-27 | 北京京东尚科信息技术有限公司 | Multi-channel message notification sending method and device |
| CN110601952A (en) * | 2018-06-12 | 2019-12-20 | 北京京东尚科信息技术有限公司 | Multi-channel message notification sending method and device |
| CN109347898B (en) * | 2018-08-20 | 2021-04-30 | 深圳市梦网科技发展有限公司 | Scene information sending method, scene information display method, server and mobile terminal |
| CN109347898A (en) * | 2018-08-20 | 2019-02-15 | 深圳市梦网科技发展有限公司 | Scene information sending method, display method, server and mobile terminal |
| CN109190075A (en) * | 2018-08-20 | 2019-01-11 | 国云科技股份有限公司 | Message sending method based on multiple cloud platform message types |
| CN111049723A (en) * | 2018-10-15 | 2020-04-21 | 广州虎牙信息科技有限公司 | Message pushing method, message management system, server and computer storage medium |
| CN111049871B (en) * | 2018-10-15 | 2023-04-07 | 广州虎牙信息科技有限公司 | Message pushing method, message management system, server and computer storage medium |
| CN111049871A (en) * | 2018-10-15 | 2020-04-21 | 广州虎牙信息科技有限公司 | Message pushing method, message management system, server and computer storage medium |
| CN109558199A (en) * | 2018-11-29 | 2019-04-02 | 广州市百果园信息技术有限公司 | A kind of information-pushing method, device, equipment and storage medium |
| CN110012051A (en) * | 2018-12-19 | 2019-07-12 | 香港乐蜜有限公司 | Notify method for pushing, device, terminal device, server and system |
| CN109672608B (en) * | 2018-12-21 | 2021-12-31 | 腾讯音乐娱乐科技（深圳）有限公司 | Method for transmitting messages according to time |
| CN109672608A (en) * | 2018-12-21 | 2019-04-23 | 腾讯音乐娱乐科技（深圳）有限公司 | The method for sending message according to the time |
| CN109815408B (en) * | 2019-02-01 | 2021-03-16 | 百度在线网络技术（北京）有限公司 | Method and device for pushing information |
| CN109815408A (en) * | 2019-02-01 | 2019-05-28 | 百度在线网络技术（北京）有限公司 | Method and apparatus for pushed information |
| CN110049118A (en) * | 2019-04-12 | 2019-07-23 | 深圳乐信软件技术有限公司 | Information push method, device, equipment and storage medium |
| CN110533456A (en) * | 2019-07-30 | 2019-12-03 | 威富通科技有限公司 | A kind of coupon information method for pushing, system and server |
| CN110460512B (en) * | 2019-08-01 | 2021-10-22 | 北京达佳互联信息技术有限公司 | System message generation method, device, server and storage medium |
| CN110460512A (en) * | 2019-08-01 | 2019-11-15 | 北京达佳互联信息技术有限公司 | System message generation method, device, server and storage medium |
| CN110572434A (en) * | 2019-08-05 | 2019-12-13 | 威富通科技有限公司 | Push method and device of voice broadcast message, push server and storage medium |
| CN110460602A (en) * | 2019-08-15 | 2019-11-15 | 中国银行股份有限公司 | It can support the SWIFT message processing method and system of multi-bank zone |
| CN110460602B (en) * | 2019-08-15 | 2022-01-07 | 中国银行股份有限公司 | SWIFT message processing method and system capable of supporting multiple banks and multiple time zones |
| CN111049727A (en) * | 2019-11-22 | 2020-04-21 | 用友网络科技股份有限公司 | Message processing method, message processing apparatus, and computer-readable storage medium |
| CN112995248A (en) * | 2019-12-12 | 2021-06-18 | 阿里巴巴集团控股有限公司 | Information pushing method, device and equipment |
| WO2021179265A1 (en) * | 2020-03-12 | 2021-09-16 | 深圳市欢太科技有限公司 | Information pushing method and apparatus, server, and storage medium |
| CN115023922A (en) * | 2020-03-12 | 2022-09-06 | 深圳市欢太科技有限公司 | Information pushing method and device, server and storage medium |
| CN115023922B (en) * | 2020-03-12 | 2024-05-03 | 深圳市欢太科技有限公司 | Information pushing method, device, server and storage medium |
| CN111756620A (en) * | 2020-06-28 | 2020-10-09 | 中国银行股份有限公司 | Message pushing method and device |
| CN111935111A (en) * | 2020-07-27 | 2020-11-13 | 北京字节跳动网络技术有限公司 | Interaction method and device and electronic equipment |
| CN112866979B (en) * | 2020-12-31 | 2022-09-09 | 恒安嘉新（北京）科技股份公司 | User information association method, device, equipment and medium based on 5G service interface |
| CN112866979A (en) * | 2020-12-31 | 2021-05-28 | 恒安嘉新（北京）科技股份公司 | User information association method, device, equipment and medium based on 5G service interface |
| CN112925512A (en) * | 2021-01-29 | 2021-06-08 | 北京字节跳动网络技术有限公司 | Message sending method and device, electronic equipment and storage medium |
| CN113992622A (en) * | 2021-09-08 | 2022-01-28 | 上海易立德信息技术股份有限公司 | Multi-template aggregation message notification sending system and method based on unified model |
| CN114390452A (en) * | 2022-01-18 | 2022-04-22 | 平安科技（深圳）有限公司 | Message sending method and related equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103973461A (en) | Notification message pushing method and message server | |
| US10795629B2 (en) | Text and custom format information processing method, client, server, and computer-readable storage medium | |
| CN104580406B (en) | A kind of method and apparatus of synchronous logging state | |
| CN103139048B (en) | Group's message prompt method and system | |
| CN108432200B (en) | Method for protecting and controlling access to private personal information | |
| CN111460356B (en) | Automatic login method, device, medium and equipment | |
| EP3002927A1 (en) | Page redirection method, routing device, terminal device and system | |
| CN102647482A (en) | A method and system for accessing a website | |
| WO2015101320A1 (en) | Account number generation method, terminal and background server | |
| US10873640B2 (en) | Information exchange method and server | |
| US20100075641A1 (en) | Computer based method and system for logging in a user mobile device at a server computer system | |
| US9876776B2 (en) | Methods for generating and publishing a web site based on selected items and devices thereof | |
| CN101115180B (en) | Electronic program menu system and functional module dynamic load operating method | |
| US20070180143A1 (en) | Translation Web Services For Localizing Resources | |
| CN103412944A (en) | Internet addressing method and device | |
| CN110417919A (en) | Method and device for traffic hijacking | |
| CN103561063A (en) | Method and terminal for logging onto set top box | |
| CN107566270A (en) | The processing method and processing device that a kind of resource accesses | |
| CN106210159B (en) | Domain name resolution method and device | |
| CN108696549B (en) | Load balancing method, device and system | |
| US8565733B2 (en) | Computer-based method and system for processing a file request in response to a message received from a user mobile device | |
| CN107404515A (en) | The processing method and processing device of asynchronous http request | |
| CN108337317B (en) | Method and device for processing route request | |
| US20160036766A1 (en) | Method and system for synchronizing program masks | |
| HK1197507A (en) | Method for pushing notification message, and message server |
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: 1197507 Country of ref document: HK |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140806 |
|
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: WD Ref document number: 1197507 Country of ref document: HK |