CN105491092B - Message pushing method and device - Google Patents
Message pushing method and device Download PDFInfo
- Publication number
- CN105491092B CN105491092B CN201410480113.6A CN201410480113A CN105491092B CN 105491092 B CN105491092 B CN 105491092B CN 201410480113 A CN201410480113 A CN 201410480113A CN 105491092 B CN105491092 B CN 105491092B
- Authority
- CN
- China
- Prior art keywords
- message
- client
- reading
- version
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 230000006870 function Effects 0.000 claims description 8
- 238000006243 chemical reaction Methods 0.000 claims description 3
- 238000004590 computer program Methods 0.000 claims description 2
- 239000000725 suspension Substances 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000001914 filtration Methods 0.000 description 4
- 230000006978 adaptation Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention discloses a message pushing method, which comprises the following steps: before a target message is pushed to a client, acquiring version identification information of the client; acquiring the message reading capacity of the client according to the version identification information; judging whether the client supports reading the target message or not according to the message reading capability of the client; if the client does not support reading the target message, performing version compatibility processing on the target message; and pushing the target message subjected to version compatibility processing to the client. The embodiment of the invention also discloses a message pushing device. By adopting the invention, the version compatibility processing can be carried out when the target message is sent to the client, and the client can be ensured to successfully process the received message.
Description
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a message pushing method and apparatus.
Background
With the rapid development of the internet technology, more and more clients can be used for acquiring internet services in life, and a plurality of clients of different versions can be provided for different version numbers, different machine type adaptations and different language adaptations. In the face of increasingly diversified versions of clients and historical versions of various clients, when a message type which cannot be supported is received, the message type cannot be displayed, or the client is automatically closed or stopped running due to an error, even an operating system is crashed, and the normal use of the client is seriously influenced.
Disclosure of Invention
The technical problem to be solved by the embodiments of the present invention is to provide a message pushing method and device, which can push a target message subjected to version-compatible processing to a client, and ensure that the client can perform normal processing on the received message.
In order to solve the above technical problem, an embodiment of the present invention provides a message pushing method, where the method includes:
before a target message is pushed to a client, acquiring version identification information of the client;
acquiring the message reading capacity of the client according to the version identification information;
judging whether the client supports reading the target message or not according to the message reading capability of the client;
if the client does not support reading the target message, performing version compatibility processing on the target message;
and pushing the target message subjected to version compatibility processing to the client.
Correspondingly, an embodiment of the present invention further provides a message pushing apparatus, including:
the version identification acquisition module is used for acquiring the version identification information of the client before pushing the target message to the client;
a reading capability obtaining module, configured to obtain, according to the version identification information, a message reading capability of the client;
the reading capacity judging module is used for judging whether the client supports reading the target message according to the message reading capacity of the client;
the version compatibility processing module is used for performing version compatibility processing on the target message if the reading capability judging module judges that the client does not support reading of the target message;
and the message pushing module is used for pushing the target message subjected to the version compatibility processing to the client.
The embodiment of the invention acquires the message reading capability of the target client before sending the target message, and performs version compatible processing on the target message when the client does not support reading the target message, thereby ensuring that the client can successfully process the received message and avoiding the situations of error reporting or work suspension of the client and the like.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart of a message pushing method in an embodiment of the present invention;
fig. 2 is a schematic flow chart of a message pushing method in another embodiment of the present invention;
fig. 3 is a flowchart illustrating a message pushing method according to another embodiment of the present invention;
fig. 4 is a schematic structural diagram of a message pushing apparatus in an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a reading capability determining module of a message pushing apparatus according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a version-compatible processing module of a message pushing apparatus according to an embodiment of the present invention;
FIG. 7 is one representation of the message reading capabilities of a client in an embodiment of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The message pushing method in the embodiment of the present invention may be implemented by a message pushing device, for example, a message pushing server or other network unit that can push a message to a client, such as another client, or a network message forwarding device. For example, the message pushing device in the embodiment of the present invention may be an instant messaging server, an application background server, a web server, or an SNS (Social Networking Services) server, and may be an individual server device, or a server cluster composed of a plurality of server devices that implement specific functions.
Fig. 1 is a schematic flow chart of a message pushing method in an embodiment of the present invention, where as shown in the figure, the message pushing method in the embodiment may include:
s101, before a target message is pushed to a client, version identification information of the client is obtained.
The target message may be an instant messaging message, an application event message, a system message, an SNS message, or a web message, etc. Specifically, after determining that the target message needs to be pushed to the client, the message pushing apparatus first determines whether the client supports reading the target message by executing S101 to S103 in this embodiment. The version identification information of the client may include any one of a platform type (e.g., android version, ios version, windows version), a language type (chinese version, english version, japanese version), a main function type (e.g., light chat version, real-time talk version, standard version), and a version number (e.g., 1.0, 2.0, 3.0).
In an optional embodiment, the message pushing apparatus may obtain the version identification information of the client by obtaining login status information of the client, where the login status information may be reported by the client at any time during or after login, and may include a login account, an online status, and version identification information of the client. In an optional embodiment, the login state management server may be responsible for managing login state information of the client corresponding to each user, and the login state information of the corresponding client may be acquired from the login state management server when the message push device needs the message push device.
And S102, acquiring the message reading capability of the client according to the version identification information.
Specifically, when the clients of the respective versions are pushed out, the message reading capability of the client of each version and the version identification information of the version are recorded, so that a corresponding relationship between the version identification information and the message reading capability of the client of the version is established, and before the message pushing device pushes the target message to the client, the message reading capability of the client of the version corresponding to the obtained version identification information can be searched in the corresponding relationship between the preset version identification information and the message reading capability of the client of the version according to the obtained version identification information. An exemplary message reading capability of a version client may be as shown in fig. 7, which includes at least one reading capability supported by the version client, and is outlined in the figure to indicate that the version client supports the reading capability.
In an optional embodiment, the version capability management server may be responsible for managing the message reading capability of each version client, and when the message pushing device needs, the message reading capability of the client may be acquired from the version capability management server according to the acquired version identification information.
S103, judging whether the client supports reading the target message according to the message reading capability of the client.
Namely, whether the client can display the target message is judged according to the message reading capability of the client. If the target message is a voice message, if the message pushing device determines that the client supports playing the voice message according to the message reading capability of the client, the client is determined to support reading the target message, otherwise, the client is determined not to support reading the target message.
In an optional embodiment, the message pushing device may first obtain a message type of the target message, further obtain at least one reading capability required by the target message according to a correspondence between a preset message type and a reading capability required by the preset message type, then determine whether the message reading capability of the client includes all the reading capabilities required by the target message, determine that the client supports reading the target message if the message reading capability of the client includes all the reading capabilities required by the target message, and otherwise determine that the client does not support reading the target message. In this embodiment, the developer may define or set the reading capability that the client needs to support in order to display the message of the type when each new message type is defined, so that the message pushing device may obtain the reading capability required by different message types when needed.
And S104, if the client does not support reading the target message, performing version compatibility processing on the target message.
In a specific implementation, the message pushing device may convert the target message into a message type of a specific format, where the message type of the specific format may be, for example, a text message or a message type that can be supported by the client, or may generate a notification message according to the type or content of the target message as a target message subjected to version compatibility processing, where the target message is, for example, a voice message, and if the client does not support a corresponding reading capability, the message pushing device may generate a text message, "friend AA has sent a voice message to you, and because the current version of the client does not support successful reception"; for another example, the target message is a video sharing message, which carries target video data or can call a video playing function of the receiver client to play specified video data, if the client does not support the corresponding reading capability, the message pushing device can generate a text message carrying an access link or address of the specified video data, so that the client can play the specified video data in other ways according to the access link or address after receiving the text message.
S105, pushing the target message subjected to the version compatibility processing to the client.
The embodiment of the invention acquires the message reading capability of the target client before sending the target message, and performs version compatible processing on the target message when the client does not support reading the target message, thereby ensuring that the client can successfully process the received message and avoiding the situations of error reporting or work suspension of the client and the like.
Fig. 2 is a schematic flow chart of a message pushing method in another embodiment of the present invention, as shown in the figure, the message pushing method in this embodiment may include:
s201, obtaining login state information of the client, wherein the login state information comprises a login account number, an online state and version identification information of the client.
The login state information may be reported by the client at any time during or after login, and may include a login account, an online state, version identification information, and the like of the client. In an optional embodiment, the login state management server may be responsible for managing login state information of the client corresponding to each user, and the login state information of the corresponding client may be acquired from the login state management server when the message push device needs the message push device. Specifically, after determining that a target message needs to be pushed to a client, the message pushing device first obtains login state information of the client to determine whether the client supports reading the target message. In an optional embodiment, the message pushing apparatus may first determine, according to a message filtering or shielding rule preset by the client, whether to perform message filtering or shielding processing on the target message for the client, and after determining that the target message needs to be pushed to the client, execute the message pushing method in this embodiment.
S202, obtaining the message reading capability of the client according to the version identification information, wherein the message reading capability comprises at least one reading capability supported by the client.
Specifically, when the clients of the respective versions are pushed out, the message reading capability of the client of each version and the version identification information of the version are recorded, so that a corresponding relationship between the version identification information and the message reading capability of the client of the version is established, and before the message pushing device pushes the target message to the client, the message reading capability of the client of the version corresponding to the obtained version identification information can be searched in the corresponding relationship between the preset version identification information and the message reading capability of the client of the version according to the obtained version identification information. An exemplary message reading capability of a version client may be as shown in fig. 7, which is outlined to indicate that the version client supports the reading capability.
In an optional embodiment, the version capability management server may be responsible for managing the message reading capability of each version client, and when the message pushing device needs, the message reading capability of the client may be acquired from the version capability management server according to the acquired version identification information.
S203, obtaining the message type of the target message.
The message type may include a text message, a voice message, a video message, a rich text message, or any of the above messages carrying a particular message format, such as a text message with a message tail, a rich text message with user signature information (a photograph or text content), and so forth.
For example, the message pushing apparatus may determine the message type of the target message according to a message type identifier carried by the target message.
S204, acquiring at least one reading capability required by the target message according to the corresponding relation between the preset message type and the required reading capability.
In this embodiment, a developer may define or set, in advance, the reading capability that the client needs to support in order to display a message of a new message type each time the new message type is defined, so that the message pushing device may acquire the reading capability that is needed by different message types when needed.
S205, determine whether the message reading capability of the client includes all reading capabilities required by the target message. If so, S209 is performed, otherwise, S206 is performed.
S206, determining that the client does not support reading the target message.
And S207, performing version compatibility processing on the target message.
In a specific implementation, the message pushing device may convert the target message into a message type of a specific format, where the message type of the specific format may be, for example, a text message or a message type that can be supported by the client, or may generate a notification message according to the type or content of the target message as a target message subjected to version compatibility processing, where the target message is, for example, a voice message, and if the client does not support a corresponding reading capability, the message pushing device may generate a text message, "friend AA has sent a voice message to you, and because the current version of the client does not support successful reception"; for another example, the target message is a video sharing message, which carries target video data or can call a video playing function of the receiver client to play specified video data, if the client does not support the corresponding reading capability, the message pushing device can generate a text message carrying an access link or address of the specified video data, so that the client can play the specified video data in other ways according to the access link or address after receiving the text message.
In an optional embodiment, the message pushing apparatus may determine the message type supported by the client according to the message reading capability of the client and a correspondence between a preset message type and a required reading capability thereof, and further convert the target message into the message type supported by the client. For example, the message reading capability of the client includes a reading capability a, a reading capability B, and a reading capability C supported by the client, and further, according to a correspondence between a preset message type and a reading capability required by the client, if it is found that the reading capability required by the voice message is the reading capability a, the reading capability B, and the reading capability C, it is determined that the client supports the message type of the voice message, the message pushing device may convert the target message into the voice message when the client does not support the message type of the target message, and if the target message is originally a video message, the voice data may be extracted from the video message, and the converted target message is the voice message carrying the extracted voice data.
S208, pushing the target message subjected to the version compatibility processing to the client.
S209, determining that the client supports reading the target message.
S210, pushing the target message to the client. I.e. push the targeted message directly to the client.
The embodiment of the invention acquires the message reading capability of the target client before sending the target message, and performs version compatible processing on the target message when the client does not support reading the target message, thereby ensuring that the client can successfully process the received message and avoiding the situations of error reporting or work suspension of the client and the like.
Fig. 3 is a schematic flow chart of a message pushing method in another embodiment of the present invention, where as shown in the figure, the message pushing method in this embodiment may include:
s301, obtaining login state information of the client, wherein the login state information comprises a login account number, an online state and version identification information of the client.
The login state information may be reported by the client at any time during or after login, and may include a login account, an online state, version identification information, and the like of the client. In an optional embodiment, the login state management server may be responsible for managing login state information of the client corresponding to each user, and the login state information of the corresponding client may be acquired from the login state management server when the message push device needs the message push device. Specifically, after determining that a target message needs to be pushed to a client, the message pushing device first obtains login state information of the client to determine whether the client supports reading the target message. In an optional embodiment, the message pushing apparatus may first determine, according to a message filtering or shielding rule preset by the client, whether to perform message filtering or shielding processing on the target message for the client, and after determining that the target message needs to be pushed to the client, execute the message pushing method in this embodiment.
S302, obtaining the message reading capability of the client according to the version identification information, wherein the message reading capability comprises at least one reading capability supported by the client.
Specifically, when the clients of the respective versions are pushed out, the message reading capability of the client of each version and the version identification information of the version are recorded, so that a corresponding relationship between the version identification information and the message reading capability of the client of the version is established, and before the message pushing device pushes the target message to the client, the message reading capability of the client of the version corresponding to the obtained version identification information can be searched in the corresponding relationship between the preset version identification information and the message reading capability of the client of the version according to the obtained version identification information. An exemplary message reading capability of a version client may be as shown in fig. 7, which is outlined to indicate that the version client supports the reading capability.
In an optional embodiment, the version capability management server may be responsible for managing the message reading capability of each version client, and when the message pushing device needs, the message reading capability of the client may be acquired from the version capability management server according to the acquired version identification information.
S303, obtaining the message type of the target message.
The message type may include a text message, a voice message, a video message, a rich text message, or any of the above messages carrying a particular message format, such as a text message with a message tail, a rich text message with user signature information (a photograph or text content), and so forth.
For example, the message pushing apparatus may determine the message type of the target message according to a message type identifier carried by the target message.
S304, acquiring at least one reading capability required by the target message according to the corresponding relation between the preset message type and the reading capability required by the preset message type.
In this embodiment, a developer may define or set, in advance, the reading capability that the client needs to support in order to display a message of a new message type each time the new message type is defined, so that the message pushing device may acquire the reading capability that is needed by different message types when needed.
S305, determining that all reading capabilities required by the target message are not included in the message reading capabilities of the client.
S306, determining that the client does not support reading the target message
S307, determining the message type supported by the client according to the corresponding relation between the preset message type and the reading capability required by the preset message type.
Specifically, the message pushing device may determine the message type supported by the client according to the message reading capability of the client and a corresponding relationship between a preset message type and the required reading capability, for example, the message reading capability of the client includes a reading capability a, a reading capability B, and a reading capability C supported by the client, and further, according to the corresponding relationship between the preset message type and the required reading capability, if it is found that the reading capability required by the voice message is the reading capability a, the reading capability B, and the reading capability C, it determines the message type that the client supports the voice message, and further, may obtain all the message types supported by the client according to the above determination method.
S308, converting the target message into the message type supported by the client.
The message pushing device may convert the target message into the message type supported by the client after determining the message type supported by the client, for example, convert the target message into a text message if determining that the client supports a text message. Furthermore, in an optional embodiment, the optional substitute types of each message type may be preset, and priorities of a plurality of optional substitute types may also be set, for example, the optional substitute types of the video message are a voice message and a text message, and the priority of the voice message is higher than the priority of the text message, if it is determined that the client does not currently support the video message but supports the voice message and the text message, the message pushing apparatus may convert the target message into the voice message according to the priority when it is determined that the target message whose message type is the video message needs to be pushed to the client, for example, may extract voice data from the video message, and the converted target message is a voice message carrying the extracted voice data.
S309, pushing the converted target message to the client.
The embodiment of the invention acquires the message reading capability of the target client before sending the target message, and performs version compatible processing on the target message when the client does not support reading the target message, thereby ensuring that the client can successfully process the received message and avoiding the situations of error reporting or work suspension of the client and the like.
Fig. 4 is a schematic structural diagram of a message pushing apparatus in an embodiment of the present invention, where the message pushing apparatus in the embodiment of the present invention at least includes:
the version identifier obtaining module 410 is configured to obtain version identifier information of a client before pushing a target message to the client.
The target message may be an instant messaging message, an application event message, a system message, an SNS message, or a web message, etc. The version identification information of the client may include any one of a platform type (e.g., android version, ios version, windows version), a language type (chinese version, english version, japanese version), a main function type (e.g., light chat version, real-time talk version, standard version), and a version number (e.g., 1.0, 2.0, 3.0).
In an optional embodiment, the version identifier obtaining module 410 may obtain the version identifier information of the client by obtaining login status information of the client, where the login status information may be reported by the client at any time during or after login, and may include a login account, an online status, version identifier information, and the like of the client. In an alternative embodiment, the login status management server may be responsible for managing the login status information of the client corresponding to each user, and the version identifier obtaining module 410 obtains the login status information of the corresponding client from the login status management server.
A reading capability obtaining module 420, configured to obtain, according to the version identification information, a message reading capability of the client.
Specifically, when the clients of the respective versions are pushed out, the message reading capability of each version client and the version identification information of the version may be recorded, so as to establish a corresponding relationship between the version identification information and the message reading capability of the version client, and the reading capability obtaining module 420 may search the message reading capability of the version client corresponding to the obtained version identification information in the corresponding relationship between the preset version identification information and the message reading capability of the version client according to the obtained version identification information. An exemplary message reading capability of a version client may be as shown in fig. 7, which includes at least one reading capability supported by the version client, and is outlined in the figure to indicate that the version client supports the reading capability.
In an alternative embodiment, the version capability management server may be responsible for managing the message reading capability of each version client, and the reading capability obtaining module 420 may obtain the message reading capability of the client from the version capability management server according to the obtained version identification information.
A reading capability judging module 430, configured to judge, according to the message reading capability of the client, whether the client supports reading the target message.
Namely, whether the client can display the target message is judged according to the message reading capability of the client. If the target message is a voice message, if it is determined that the client supports playing the voice message according to the message reading capability of the client, the reading capability determining module 430 determines that the client supports reading the target message, otherwise, it is determined that the client does not support reading the target message.
Further in an optional embodiment, the reading capability determining module 430 further includes:
a message type obtaining unit 431, configured to obtain a message type of the target message.
The message type may include a text message, a voice message, a video message, a rich text message, or any of the above messages carrying a particular message format, such as a text message with a message tail, a rich text message with user signature information (a photograph or text content), and so forth.
For example, the message type obtaining unit 431 may determine the message type of the target message according to the message type identifier carried by the target message.
A reading capability obtaining unit 432, configured to obtain at least one reading capability required by the target message according to a correspondence between a preset message type and a reading capability required by the preset message type;
in this embodiment, the developer may define or set the reading capability that the client needs to support in order to display the message of the type in advance when each new message type is defined, so that the reading capability acquiring unit 432 may acquire the reading capability required by different message types when needed.
A reading capability judging unit 433, configured to judge whether all reading capabilities required for reading the target message are included in the message reading capability of the client, if so, determine that the client supports reading the target message, and otherwise, determine that the client does not support reading the target message.
The version compatibility processing module 440 is configured to perform version compatibility processing on the target message if the reading capability determining module determines that the client does not support reading the target message.
In a specific implementation, the version-compatible processing module 440 may convert the target message into a message type of a specific format, where the message type of the specific format may be, for example, a text message or a message type that can be supported by the client, or may generate a notification message according to the type or content of the target message as a target message after version-compatible processing, where for example, the target message is a voice message, and if the client does not support a corresponding reading capability, the version-compatible processing module 440 converts the target message into a text message, "friend AA has sent a voice message to you, because your client does not support the current version to successfully receive"; for another example, the target message is a video sharing message, which carries target video data or can call a video playing function of the receiver client to play specified video data, if the client does not support the corresponding reading capability, the version compatibility processing module 440 may generate a text message carrying an access link or address of the specified video data, so that the client can play the specified video data in other manners according to the access link or address after receiving the text message.
In an alternative embodiment, the version-compatible processing module 440, as shown in fig. 6, may further include:
the message type obtaining unit 441 is configured to determine the message type supported by the client according to the message reading capability of the client and a corresponding relationship between a preset message type and a required reading capability of the preset message type.
For example, the message reading capability of the client includes a reading capability a, a reading capability B, and a reading capability C supported by the client, and then the reading capability required by the voice message is determined to be the reading capability a, the reading capability B, and the reading capability C according to the correspondence between the preset message type and the reading capability required by the preset message type, then the message type obtaining unit 441 may determine the message type that the client supports the voice message, and further may obtain all the message types supported by the client according to the above determination method.
A message converting unit 442, configured to convert the target message into a message type supported by the client.
The message conversion unit 442 may convert the target message into the message type supported by the client after determining the message type supported by the client, for example, convert the target message into a text message if determining that the client supports a text message. Further, in an optional embodiment, the optional substitute types of each message type may be preset, and priorities of a plurality of optional substitute types may also be set, for example, the optional substitute types of the video message are a voice message and a text message, and the priority of the voice message is higher than the priority of the text message, if it is determined that the client does not currently support the video message but supports the voice message and the text message, the message conversion unit 442 may convert the target message into the voice message according to the priority when it is determined that the target message whose message type is the video message needs to be pushed to the client, for example, voice data may be extracted from the video message, and the converted target message is a voice message carrying the extracted voice data.
The message pushing module 450 is configured to push the target message subjected to the version compatibility processing to the client.
The message pushing device of the embodiment of the invention acquires the message reading capability of the target client before sending the target message, and performs version compatibility processing on the target message when the client does not support reading the target message, thereby ensuring that the client can successfully process the received message and avoiding the situations of error reporting or work suspension of the client and the like.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.
Claims (11)
1. A message pushing method, the method comprising:
before a target message is pushed to a client, acquiring version identification information of the client;
acquiring the message reading capacity of the client according to the version identification information;
judging whether the client supports reading the target message or not according to the message reading capability of the client;
if the client does not support reading the target message, performing version compatibility processing on the target message, wherein the performing version compatibility processing on the target message comprises: converting the target message into a selectable alternative type with the highest priority supported by the client according to the priorities of a plurality of selectable alternative types of the message type of the target message;
and pushing the target message subjected to version compatibility processing to the client.
2. The message pushing method of claim 1, wherein the message reading capability comprises at least one reading capability supported by the client;
the optional alternative types of translating the target message to the highest priority supported by the client include:
determining the message types supported by the client according to the message reading capability of the client and the corresponding relation between the preset message types and the required reading capability;
and converting the target message into an optional alternative type of the highest priority supported by the client.
3. The message pushing method of claim 1, wherein the obtaining of the version identification information of the client comprises:
and acquiring login state information of the client, wherein the login state information comprises a login account number, an online state and version identification information of the client.
4. The message pushing method of claim 1, wherein the message reading capability comprises at least one reading capability supported by the client;
the judging whether the client supports reading the target message according to the message reading capability of the client comprises the following steps:
acquiring the message type of the target message;
acquiring at least one reading capability required by the target message according to a corresponding relation between a preset message type and the required reading capability;
and judging whether the message reading capability of the client comprises all reading capabilities corresponding to the target message, if so, determining that the client supports reading the target message, and otherwise, determining that the client does not support reading the target message.
5. The message pushing method according to any one of claims 1 to 4, wherein the version identification information of the client includes any one of a platform type, a language type, a main printing function type, and a version number.
6. A message push apparatus, comprising:
the version identification acquisition module is used for acquiring the version identification information of the client before pushing the target message to the client;
a reading capability obtaining module, configured to obtain, according to the version identification information, a message reading capability of the client;
the reading capacity judging module is used for judging whether the client supports reading the target message according to the message reading capacity of the client;
a version compatibility processing module, configured to perform version compatibility processing on the target message if the reading capability determining module determines that the client does not support reading the target message, where the performing version compatibility processing on the target message includes: converting the target message into a selectable alternative type with the highest priority supported by the client according to the priorities of a plurality of selectable alternative types of the message type of the target message;
and the message pushing module is used for pushing the target message subjected to the version compatibility processing to the client.
7. The message pushing device of claim 6, wherein the message reading capability comprises at least one reading capability supported by the client;
the reading capability judging module includes:
a message type obtaining unit, configured to obtain a message type of the target message;
the reading capacity obtaining unit is used for obtaining at least one reading capacity required by the target message according to the corresponding relation between the preset message type and the required reading capacity;
a reading capability judging unit, configured to judge whether all reading capabilities required for reading the target message are included in the message reading capability of the client, if so, determine that the client supports reading the target message, and otherwise, determine that the client does not support reading the target message.
8. The message pushing device of claim 6, wherein the message reading capability comprises at least one reading capability supported by the client;
the version-compatible processing module includes:
the message type acquisition unit is used for determining the message types supported by the client according to the message reading capability of the client and the corresponding relation between the preset message types and the required reading capability;
and the message conversion unit is used for converting the target message into the selectable alternative type with the highest priority supported by the client.
9. The message pushing device of claim 6, wherein the version identification obtaining module is configured to:
and acquiring login state information of the client, wherein the login state information comprises a login account number, an online state and version identification information of the client.
10. The message pushing apparatus according to any one of claims 6 to 9, wherein the version identification information of the client includes any one of a platform type, a language type, a main printing function type, and a version number.
11. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program comprising program instructions; the program instructions, when executed by a processor, cause the processor to perform the message push method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410480113.6A CN105491092B (en) | 2014-09-18 | 2014-09-18 | Message pushing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410480113.6A CN105491092B (en) | 2014-09-18 | 2014-09-18 | Message pushing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105491092A CN105491092A (en) | 2016-04-13 |
| CN105491092B true CN105491092B (en) | 2020-05-26 |
Family
ID=55677802
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410480113.6A Active CN105491092B (en) | 2014-09-18 | 2014-09-18 | Message pushing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105491092B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106685798B (en) * | 2016-12-08 | 2020-09-01 | 蓝信移动（北京）科技有限公司 | Message generation method and device and mobile terminal |
| CN108667710B (en) * | 2017-03-28 | 2022-03-11 | 腾讯科技（深圳）有限公司 | Information processing method and device |
| CN107154931B (en) * | 2017-03-31 | 2020-02-18 | 北京奇艺世纪科技有限公司 | Method and device for client version compatibility |
| CN111181836B (en) * | 2019-10-25 | 2023-03-24 | 腾讯科技（深圳）有限公司 | Message pushing method and device |
| CN112015993B (en) * | 2020-09-01 | 2023-12-08 | 中国银行股份有限公司 | Information query method and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100417073C (en) * | 2004-05-31 | 2008-09-03 | 北京邮电大学 | Web Content Adaptation Method Based on Terminal Capability Classification |
| CN100571268C (en) * | 2005-11-29 | 2009-12-16 | 华为技术有限公司 | A protocol compatibility processing method and device |
| CN101388881A (en) * | 2007-09-13 | 2009-03-18 | 华为技术有限公司 | Method, network element and system for communication protocol version negotiation |
| US9203912B2 (en) * | 2007-11-14 | 2015-12-01 | Qualcomm Incorporated | Method and system for message value calculation in a mobile environment |
| US8925021B2 (en) * | 2011-07-11 | 2014-12-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system for trick play in over-the-top video delivery |
-
2014
- 2014-09-18 CN CN201410480113.6A patent/CN105491092B/en active Active
Non-Patent Citations (1)
| Title |
|---|
| 我用的电脑版微信，朋友发来了个信息，他说无法显示此消息，你目前使用的微信版本暂时不支持此类型的信息;百度;《https://zhidao.baidu.com/question/519706599.html》;20130124;第1页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105491092A (en) | 2016-04-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20180270182A1 (en) | Message notification method, system, and device for a communication account | |
| CN110392054B (en) | Login verification method, device, system, equipment and readable storage medium | |
| CN105491092B (en) | Message pushing method and device | |
| US20170329565A1 (en) | Information processing method, client, server, and computer-readable storage medium | |
| CN106959852B (en) | Method, device and terminal for displaying corner label of application icon | |
| US9612886B2 (en) | Method and device for monitoring API function scheduling in mobile terminal | |
| CN111726456B (en) | Data processing method and related device | |
| EP3258653A1 (en) | Message pushing method and device | |
| US10320729B2 (en) | Method, apparatus, and system for shielding harassment by mention in user generated content | |
| EP3198521B1 (en) | Method and apparatus of processing a doi (digital object unique identifier) in interaction information | |
| CN113765714B (en) | Equipment network distribution method and device, storage medium and electronic equipment | |
| CN111641554B (en) | A message processing method, device and computer-readable storage medium | |
| CN108880972B (en) | Information processing method, server and terminal | |
| CN106571942B (en) | Configuration data updating method, client and server | |
| CN106685800B (en) | The based reminding method and device of information | |
| CN105634909B (en) | Message display method and message display device | |
| CN112346751A (en) | Application program installation method and device, electronic equipment and storage medium | |
| EP3432559A1 (en) | System and method for contextually based fulfillment of communicated service requests via a telephony platform | |
| CN106412296B (en) | Terminal equipment control method and device | |
| CN106790716B (en) | Picture pushing method and system based on screen locking state | |
| CN106604244B (en) | Method and device for prompting notification message | |
| CN117311892B (en) | Remote assistance method, system, electronic device and storage medium | |
| CN110119871B (en) | Information interaction platform and method | |
| CN109040937B (en) | Microphone blockage reminding method and related device | |
| CN113613239B (en) | Network mode switching method, network mode switching device, medium, and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |