CN109905312B - Message pushing method, device and system - Google Patents

Message pushing method, device and system Download PDF

Info

Publication number
CN109905312B
CN109905312B CN201711291885.5A CN201711291885A CN109905312B CN 109905312 B CN109905312 B CN 109905312B CN 201711291885 A CN201711291885 A CN 201711291885A CN 109905312 B CN109905312 B CN 109905312B
Authority
CN
China
Prior art keywords
message
client
message pushing
server
application
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
Application number
CN201711291885.5A
Other languages
Chinese (zh)
Other versions
CN109905312A (en
Inventor
徐立钧
王志新
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Feinno Communication Technology Co Ltd
Original Assignee
Beijing Feinno Communication Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Feinno Communication Technology Co Ltd filed Critical Beijing Feinno Communication Technology Co Ltd
Priority to CN201711291885.5A priority Critical patent/CN109905312B/en
Publication of CN109905312A publication Critical patent/CN109905312A/en
Application granted granted Critical
Publication of CN109905312B publication Critical patent/CN109905312B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Abstract

The embodiment of the invention provides four message pushing methods, four message pushing devices and four message pushing equipment, and a message pushing system, and relates to the technical field of computers. The message pushing method is used for a message pushing server and comprises the following steps: the method comprises the steps that a message pushing server receives a message pushing client login token acquisition request which is sent by an application server and aims at an application user who successfully logs in the application server; obtaining a message pushing client login token of an application user; returning the login token to the application server; receiving a login request including a login token sent by a message pushing client; judging whether the message pushing client has the right to access the message pushing server or not according to the login request; and if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed. By adopting the scheme provided by the embodiment of the invention, the potential safety hazard of the message push server can be reduced.

Description

Message pushing method, device and system
Technical Field
The present application relates to the field of computer technologies, and in particular, to four message pushing methods, four message pushing devices, four message pushing electronic devices, and a message pushing system.
Background
The notification message push service establishes a notification message transmission channel from the application server to the application client (terminal App), so that when the terminal App cannot receive messages, the application can notify the user of the latest information in time, a good user relationship is constructed, and the perception and the activity of the user are improved. The scene of the message push service can be logistics reminding, promotion and publicity, news dynamic push and the like. For example, in a service scenario of logistics reminding, a user purchases a commodity, and sends a message to inform the user at the time of shipment and dispatch, so that the user can grasp the progress of delivery of the commodity and prepare for receiving the commodity.
Currently, a typical message pushing method has the following processing flow. 1) When an application server (application platform) sends a message to a terminal App and finds that the terminal App cannot receive the message, acquiring a user identifier (UserID, UID) of an application user, which is recorded by the application server side, and a client identifier (ClientID, CID) of a message pushing client, acquiring the CID corresponding to the UID, and sending an instruction for sending the message to be pushed to the CID to the message pushing server (message pushing platform); 2) after receiving the indication, the message pushing server sends the message to a message pushing client (pushing SDK) corresponding to the CID, wherein the pushing SDK logs in the message pushing server in a secret-free mode; 3) and pushing the SDK and then sending the message to the terminal App so that the user receives the message.
However, in the process of implementing the invention, the inventor finds that the technical scheme has at least the following problems: because the push SDK directly logs in the message push platform in a password-free login mode and does not pass through the application platform, when a user not authorized by the application platform logs in the message push platform through the fake terminal App integrated push SDK, the message push platform can also pass through the login request, and the processing mode of allowing any user to log in the message push platform through the push SDK brings great potential safety hazards to the message push server.
Disclosure of Invention
The embodiment of the invention provides four message pushing methods and devices, electronic equipment and a message pushing system, which are used for solving the problem that a message pushing server in the prior art has larger potential safety hazard.
In a first aspect, an embodiment of the present invention provides a message pushing method, which is used for a message pushing server, and is characterized by including: receiving a message pushing client login token acquisition request sent by an application server and aiming at an application user who successfully logs in the application server; obtaining a message pushing client login token of the application user; returning the login token to the application server; receiving a login request sent by a message pushing client, wherein the login request comprises a login token; judging whether the message pushing client has the right to access the message pushing server or not according to the login request; and if the message pushing client is judged to have the right to access the message pushing server, constructing a message transmission channel between the message pushing client and the message pushing client.
With reference to the first aspect, in a first implementation manner of the first aspect, the determining, according to the login request, whether the message push client has the right to access the message push server includes: analyzing the login token; and if the user identification carried by the login request is the same as the user identification obtained by analysis, the application identification carried by the login request is the same as the application identification obtained by analysis, and the login token is in the valid period, judging that the message pushing client has the right to access the message pushing server.
With reference to the first aspect or the first implementation manner of the first aspect, in a second implementation manner of the first aspect, the present invention further includes: acquiring a message sending instruction aiming at the application user and sent by the application server; the message sending instruction comprises the user identification of the application user and a message to be sent; and when the message pushing client successfully logs in, forwarding the message to be sent to the message pushing client through the message transmission channel.
With reference to the second implementation manner of the first aspect, in a third implementation manner of the first aspect, the method further includes: and when the message pushing client is not logged in, storing the message to be sent corresponding to the application user.
With reference to the second implementation manner of the first aspect or the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect, before forwarding the message to be sent to the message push client through the message transmission channel, the method further includes: judging whether the message pushing client is running or whether the message transmission channel is normal; and if the message pushing client does not operate or the message transmission channel is abnormal, forwarding the message to be sent to the application user through other message pushing servers.
With reference to the second implementation manner of the first aspect, the third implementation manner of the first aspect, or the fourth implementation manner of the first aspect, in a fifth implementation manner of the first aspect, the message sending indication further includes a sending priority of the message to be sent, and the method further includes: the forwarding the message to be sent to the message push client through the message transmission channel includes: and forwarding the message to be sent to the message pushing client through the message transmission channel according to the sending priority.
With reference to the first aspect or the foregoing various implementation manners of the first aspect, in a sixth implementation manner of the first aspect, the method further includes: receiving batch user registration instructions sent by the application server; the bulk user registration indication comprises at least one application user; and performing user registration on the at least one application user according to the batch user registration instruction.
In a second aspect, an embodiment of the present invention provides a message pushing apparatus, which includes a module for performing the method of the first aspect described above, where the module corresponds to a behavior of the message pushing apparatus. The modules may be software and/or hardware.
In a third aspect, an embodiment of the present invention further provides an electronic device, which includes a processor and a memory, where the processor is configured to support the electronic device to execute corresponding functions in the message pushing method according to the first aspect. The memory is for coupling with the processor and holds program instructions and data necessary to perform the message pushing method of the first aspect described above.
In a fourth aspect, an embodiment of the present invention provides another message pushing method, used for a message pushing client, including: receiving a login instruction sent by an application client; the login instruction comprises a message pushing client login token; and sending a login request to a message pushing server, wherein the login request comprises the login token.
With reference to the fourth aspect, in a first implementation manner of the fourth aspect, the method further includes: receiving a message to be sent, which is forwarded by the message pushing server and sent to an application user by an application server; and forwarding the message to be sent to the application client.
In a fifth aspect, an embodiment of the present invention provides another message pushing apparatus, which includes a module for performing the method of the fourth aspect, where the module corresponds to a behavior of the message pushing apparatus. The modules may be software and/or hardware.
In a sixth aspect, an embodiment of the present invention further provides an electronic device, which includes a processor and a memory, where the processor is configured to support the electronic device to execute corresponding functions in the message pushing method in the fourth aspect. The memory is for coupling with the processor and holds program instructions and data necessary to perform the message pushing method of the fourth aspect described above.
In a seventh aspect, an embodiment of the present invention provides a further message pushing method, used in an application server, including: receiving a login request aiming at an application user and sent by an application client; when the application user is judged to pass login, sending a message pushing client login token acquisition request aiming at the application user to a message pushing server; receiving a message pushing client login token returned by the message pushing server; and sending the login token back to the application client.
With reference to the seventh aspect, in a first implementation manner of the seventh aspect, the method further includes: acquiring a message to be sent for the application user; if the application client cannot receive the message, sending a message sending instruction aiming at the application user to the message pushing server; the message sending instruction comprises the user identification of the application user and a message to be sent.
In an eighth aspect, an embodiment of the present invention provides a further message pushing device, which includes a module for performing the method of the seventh aspect described above, where the module corresponds to a behavior of the message pushing device. The modules may be software and/or hardware.
In a ninth aspect, an embodiment of the present invention further provides another electronic device, which includes a processor and a memory, where the processor is configured to support the electronic device to execute corresponding functions in the message pushing method in the seventh aspect. The memory is configured to be coupled to the processor and stores program instructions and data necessary to execute the message pushing method of the seventh aspect.
In a tenth aspect, an embodiment of the present invention provides a further message pushing method, used for an application client, including: sending a login request aiming at an application user to an application server; receiving a message pushing client login token returned by the application server; sending a login instruction to a message pushing client; the login indication comprises the login token.
With reference to the tenth aspect, in a first implementation manner of the tenth aspect, the method further includes: receiving a message to be sent, which is forwarded by the message pushing client and sent to the application user by the application server; and displaying the message to be sent to the application user.
In an eleventh aspect, an embodiment of the present invention provides a further message pushing device, which includes a module for performing the method of the tenth aspect described above, and the module corresponds to the behavior of the message pushing device. The modules may be software and/or hardware.
In a twelfth aspect, an embodiment of the present invention further provides still another electronic device, which includes a processor and a memory, where the processor is configured to support the electronic device to execute corresponding functions in the message pushing method in the tenth aspect. The memory is for coupling with the processor and holds program instructions and data necessary to perform the message pushing method of the tenth aspect described above.
In a thirteenth aspect, an embodiment of the present invention further provides a message pushing system, which includes: the message pushing device according to the second aspect, the message pushing device according to the fifth aspect, the message pushing device according to the eighth aspect, and the message pushing device according to the eleventh aspect.
In a fourteenth aspect, the present invention provides a computer-readable storage medium, which stores instructions that, when executed on a computer, cause the computer to perform the method of the above aspects.
In a fifteenth aspect, embodiments of the present invention provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.
Compared with the prior art, the scheme provided by the embodiment of the invention receives the message pushing client login token acquisition request aiming at the application user who successfully logs in the application server, which is sent by the application server through the message pushing server; obtaining a message pushing client login token of an application user; returning the login token to an application server; receiving a login request sent by a message pushing client, wherein the login request comprises a login token; judging whether the message pushing client has the right to access the message pushing server or not according to the login request; if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed; by adopting the processing mode, a strict authorization mechanism is adopted when the message pushing client logs in the message pushing server, only the message pushing client of the authorized application user who allows the identity to be verified through the application server can log in the message pushing server, and the message pushing server is prevented from being illegally logged in by a non-application authorized user; therefore, the potential safety hazard of the message push server can be effectively reduced. Meanwhile, the processing mode can also avoid that when the information is pushed to all the application users, the users who illegally log in the information pushing server also receive the pushed information.
These and other aspects of the invention are apparent from and will be elucidated with reference to the embodiments described hereinafter.
Drawings
Fig. 1 is a schematic diagram of a framework of a message pushing system according to an embodiment of the present invention;
fig. 2 is an interaction diagram of a message pushing method according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a message pushing method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a message pushing apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention;
fig. 6 is a flowchart illustrating another message pushing method according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of another message pushing apparatus according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of another electronic device according to an embodiment of the present invention;
fig. 9 is a flowchart illustrating a further message pushing method according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of another message pushing apparatus according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of another electronic device according to an embodiment of the present invention;
fig. 12 is a flowchart illustrating a further message pushing method according to an embodiment of the present invention;
fig. 13 is a schematic structural diagram of another message pushing apparatus according to an embodiment of the present invention;
fig. 14 is a schematic structural diagram of another electronic device according to an embodiment of the present invention.
Detailed Description
The following describes an application scenario and a technical solution in an embodiment of the present invention with reference to the accompanying drawings.
As shown in fig. 1, the terminal device is equipped with an application client (application APP), and the application APP is integrated with a message push client (push SDK), after the push SDK successfully logs in a message push server (message push platform), a message delivery channel (e.g., Tcp long connection) is constructed between the push SDK and the message push platform, and when the application server (third-party application) determines that the application APP cannot receive a message, the third-party application may send a message to be sent for an application user of the application client (e.g., a message broadcasted by the third-party application to all application users, or a message sent by other application users to the application user of the application client) to the message push platform through a message push interface (rest interface). When the network is smooth and the SDK is running, the push SDK keeps Tcp long connection with the message push platform, and push messages are delivered to the push SDK through the long connection; if the push SDK is not running or the network is not smooth, the push message can be delivered to the push SDK through the apple, Huacheng or millet push platform. And the pushing SDK returns the received pushing message to the application APP for display processing.
In this application, the terms "platform" and "server" are often used interchangeably, but those skilled in the art will understand their meaning. The terminal devices related to the present invention include but are not limited to mobile communication devices, that is: also known as cell phones or smart phones, include personal computers, PADs, ipads, etc.
For example, the terminal device is a smart phone, the device is equipped with applications APP such as WeChat, Taobao, Himalayan, and the like, taking WeChat as an example, if a WeChat friend sends a message to a WeChat user operating the device, the application APP of the WeChat friend sends the message to a WeChat server, the WeChat server detects that the application APP of a message sending object is not operating, the message is sent to a message pushing platform, the message pushing platform pushes the message to a pushing SDK of the message sending object, and the pushing SDK recalls the received pushing message to the application APP of the message sending object for display processing.
Fig. 2 shows an interaction diagram of a message pushing system according to an embodiment of the present invention. The message push system includes an application APP, a push SDK, a third-party platform, and a push platform, and in this embodiment, the interaction process between the devices may be as follows:
1) for a plurality of application users which are opened on the third-party platform, the pushing platform provides a batch registration interface, and the plurality of application users can be led into the pushing platform at one time.
2) And after the application APP logs in the third-party platform and is verified successfully, obtaining a message push client login token (push authentication token) from the push platform and sending the message push client login token (push authentication token) to the application APP.
3) The application APP uses the token to call a login interface of the pushing SDK, after the pushing platform receives the login request and verifies that the token is legal and successful, the pushing SDK is successfully logged in, and then the pushing message can be received.
4) The pushing platform establishes the mapping between the token and the user UID, the third-party platform does not need to establish a mapping relation, and when the pushing service is used, the pushing platform only needs to call a pushing interface of the pushing platform according to the UID of the third-party platform for pushing.
5) If the pushing SDK does not log in the pushing platform, but the pushing platform is opened by the application user, the third party platform pushes the message, the pushing platform can automatically cache the pushing message for the application user, and the pushing message can be received when the pushing SDK logs in the pushing platform.
6) The third party platform can also set push priority control, and important messages are pushed preferentially.
The embodiments of the present invention will be described in further detail below based on the common aspects of the present invention described above.
The message pushing method provided by the embodiment of the invention has the following basic ideas: for the message pushing client integrated by the application client, the application client can log in the message pushing server according to a log-in token distributed by the message pushing server, and the log-in token is acquired by the application server through the message pushing server only after an application user successfully verifies the identity through the application server, is returned to the application client by the application server, and is transmitted to the message pushing client by the application client. Because a strict authorization mechanism is adopted when the message pushing client logs in the message pushing server, the message pushing client of an authorized application user who only allows the identity to be verified through the application server can log in the message pushing server, and the message pushing server is prevented from being illegally logged in by a non-application authorized user; therefore, the potential safety hazard of the message push server can be effectively reduced. Meanwhile, the processing mode can also avoid that when the information is pushed to all the application users, the users who illegally log in the information pushing server also receive the pushed information.
A message pushing method provided in an embodiment of the present invention is described in detail below with reference to fig. 3.
In part 301, a message push server receives a message push client login token acquisition request sent by an application server for an application user who successfully logs in the application server.
After the application user successfully logs in the application server, the application server sends a message pushing client login token acquisition request aiming at the application user to the message pushing server, wherein the request at least comprises a user identifier of the application user, such as a micro signal of which the user identifier of the micro-message application is the user. After receiving the request, the message pushing server can enter the next step to acquire a message pushing client login token of the application user.
At element 302, a message push client login token for the application user is obtained.
The message pushing client login token means that when the message pushing client logs in the message pushing server, the message pushing server authenticates the token of the user. The method comprises the steps that an application server sends a message pushing client login token acquisition request aiming at an application user who successfully logs in the application server to a message pushing server, namely the application server informs the message pushing server that the user successfully logs in and is an application authorization user, the message pushing server is requested to distribute a login token for logging in the message pushing server for the user, and the login token is used for logging in the message pushing client. The message pushing server can judge the login state of the message pushing client according to a login token carried in a login request sent by the message pushing client.
The message push server can generate a login token through a preset login token generation algorithm. A typical method is that the message pushing server generates a unique login token in a random manner, then stores the unique login token in a database on the message pushing server side, and after receiving a login request sent by the message pushing client, the message pushing server compares the login token carried in the login request with the login token stored in the database on the message pushing server side, so as to determine the user identity and the login state.
In one example, the message push server generates a login token according to information such as a user identifier, an application identifier, current time and the like carried by the token request, wherein the login token carries authentication information of the user, including but not limited to the user identifier, the application identifier, the generation time and the like; after receiving the login request, the message pushing server can obtain user authentication information such as user identification, application identification, generation time and the like by analyzing the login token, and if the user identification is consistent with the user identification carried by the login request, the message pushing client can be judged to have legal login identity. By adopting the processing mode, the message pushing server does not need to store the login token; therefore, the storage resource of the message push server can be effectively saved.
After the message pushing server obtains the login token of the message pushing client of the application user, the next step can be carried out to send the login token back to the application server.
At element 303, the login token is returned to the application server.
The application server sends the login token back to the application client after receiving the login token, the application client transmits the login token to the message pushing client, and the message pushing client sends a login request to the message pushing server according to the login token.
At element 304, a login request sent by a message push client is received, the login request including the login token.
After receiving the login request, the message pushing server can enter the next step to judge whether the message pushing client side has the right to access the message pushing server according to the login request.
At element 305, it is determined whether the message pushing client has access to the message pushing server based on the login request.
Two available authentication methods are given below according to the generation method of the login token.
The method comprises the following steps: 1) the message pushing server analyzes the login token; 2) if the user identification carried by the login request is the same as the user identification obtained by analysis, the application identification carried by the login request is the same as the application identification obtained by analysis, and the login token is in the valid period, judging that the message pushing client has the right to access the message pushing server; otherwise, the message pushing client is judged not to have the right to access the message pushing server.
The second mode comprises the following steps: 1) the message pushing server acquires the user identification carried by the login request; 2) obtaining a login token recorded by a message push server side according to a user identifier; 3) if the login token carried by the login request is the same as the login token recorded by the message pushing server side, judging that the message pushing client side has the right to access the message pushing server; otherwise, the message pushing client is judged not to have the right to access the message pushing server.
If it is determined that the message push client has the right to access the message push server, a message transmission channel with the message push client is constructed, in 306.
And if the message pushing server judges that the message pushing client has the right to access the message pushing server, constructing a message transmission channel with the message pushing client so as to push the application message sent to the application client by the application server.
The message transmission path may be a TCP long connection or a short connection. When a TCP protocol is adopted during network communication, a connection must be established between a server and a client before real read-write operation, after the read-write operation is completed, the connection can be released when the connection is no longer needed by both sides, the establishment of the connection needs three-way handshake, and the release needs 4 hands to be volatilized, so that the establishment of each connection needs resource consumption and time consumption. A TCP long connection is a connection in which a plurality of packets can be continuously transmitted over one TCP connection, and if no packet is transmitted during the TCP connection holding period, both of them are required to transmit a detection packet to maintain the connection, and it is generally required to maintain online. Long connections are often used for frequent (read-write) operations, point-to-point communications.
In an example, the message pushing method provided in the embodiment of the present invention further includes the following steps: 1) acquiring a message sending instruction aiming at the application user and sent by the application server; the message sending instruction comprises the user identification of the application user and a message to be sent; 2) and when the message pushing client successfully logs in, forwarding the message to be sent to the message pushing client through the message transmission channel.
The application server may send a message sending indication for the application user to the message pushing server through a message pushing interface (e.g., a rest interface), where the message sending indication at least includes a message to be sent, and a user identifier or a message pushing Client Identifier (CID) of the application user.
In one example, the message sending indication comprises a message push client identity, which requires the application server side to record a mapping between the user identity and the message push client identity. By adopting the processing mode, more integration work is required when the application server integrates the message pushing function; therefore, the integration difficulty is large.
In another example, the message sending indication comprises a user identity of the application user, which requires the message push server side to record the mapping between the user identity and the message push client identity. By adopting the processing mode, the application server does not need to record the mapping relation between the user identification and the message pushing client identification, and can send the message sending indication aiming at the application user to the message server only according to the user identification; therefore, the difficulty of integrating the message push service by the application server can be effectively reduced.
When the mapping relation between the user identification and the message pushing client identification is recorded on the message pushing server side, even if the message pushing client does not log in the message pushing server, the message pushing server can store the message sent to the application user corresponding to the user identification of the application user, and the message is used as an offline message. When the message pushing server determines that the message pushing client successfully logs in, the offline message can be sent to the message pushing client, so that the application user can obtain the message. By adopting the processing mode, the message can be pushed to the application user when the message pushing client is not logged in; therefore, the message pushing success rate can be effectively improved.
Before forwarding the message to be sent to the message push client through the message transmission channel, the message push method provided by the embodiment of the present invention may further include the following steps: judging whether the message pushing client is running or whether the message transmission channel is normal; and if the message pushing client does not operate or the message transmission channel is abnormal, forwarding the message to be sent to the application user through other message pushing servers.
Before the message push server sends the message to the message push client, the availability of the message push client can be detected, and when the message push client is detected not to be operated or a message transmission channel is not smooth due to network failure, the message to be sent can be forwarded to the application user through other message push servers.
To implement that a message to be sent is forwarded to an application user through another message push server when a message push client is not running or a message transmission channel is not normal, the message push server needs to acquire device information of a terminal device, such as an operating system type (IOs or Android) of the terminal device running, a device generator (millet, huashi, apple, etc.), and the like. The equipment information of the terminal equipment can be carried in a login request sent by the message pushing client to the message pushing server, and the message pushing server analyzes the login request to obtain the equipment information of the terminal equipment and records the equipment information corresponding to the user identification. And when the message pushing server detects that the message pushing client is not operated or a message transmission channel is not smooth due to network faults, determining which message pushing server to forward the message to be sent to the application user according to the recorded equipment information.
For example, when the identification terminal device is a millet mobile phone, the message can be pushed to a millet pushing platform, the message is pushed to a millet pushing SDK through the millet pushing platform, and an application client is awakened by a message pushing client packaged with the millet pushing SDK and is displayed to an application user; when the terminal equipment is identified to be a Hua-Shi mobile phone, the message can be pushed to a Hua-Shi pushing platform, the message is pushed to a Hua-Shi pushing SDK through the Hua-Shi pushing platform, the message pushing client side of the application client side is awakened by the packaged Hua-Shi pushing SDK, and the message is displayed to the application user; when the terminal equipment is identified as the Apple mobile phone, the message can be pushed to an Apple Push Notification Service (APNs), the message is pushed to a Push Notification prompting device of an Apple system through an Apple Push platform, and the message is displayed to an application user by the Push Notification prompting device of the Apple system.
In one example, the message sending indication includes a sending priority of a message to be sent, a higher-level priority is set for an important message, and a general-level priority is set for a general message; in this case, the message push server may forward the message to be sent to the message push client through the message transmission channel according to the sending priority. By adopting the processing mode, the pushing sequence of the messages can be controlled; therefore, flexibility of message transmission can be effectively provided.
In another example, the message push server may also set a sending priority for the received message, set a higher priority for the important message, and set a general priority for the general message according to a preset message level setting rule.
In one example, the message push server opens an interface of batch registered users to the application server, the application server sends a batch user registration instruction to the message push server by calling the interface and transfers the registered users in the application server to the interface, and the message push server registers the registered users in the application server to the message push server once after receiving the batch user registration instruction. By adopting the processing mode, even if the application user logs in, the application message can be cached for the application user on the message pushing server side.
As can be seen from the foregoing embodiments, in the message pushing method provided in the embodiments of the present invention, a client login token acquisition request is pushed by receiving a message sent by an application server and directed to an application user who successfully logs in the application server; obtaining a message pushing client login token of an application user; returning the login token to an application server; receiving a login request sent by a message pushing client, wherein the login request comprises a login token; judging whether the message pushing client has the right to access the message pushing server or not according to the login request; if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed; by adopting the processing mode, a strict authorization mechanism is adopted when the message pushing client logs in the message pushing server, only the message pushing client of the authorized application user who allows the identity to be verified through the application server can log in the message pushing server, and the message pushing server is prevented from being illegally logged in by a non-application authorized user; therefore, the potential safety hazard of the message push server can be effectively reduced. Meanwhile, the processing mode can also avoid that when the information is pushed to all the application users, the users who illegally log in the information pushing server also receive the pushed information.
The invention also provides a message pushing device corresponding to the message pushing method.
Fig. 4 is a schematic structural diagram of a message pushing apparatus according to the above embodiment, where the message pushing apparatus includes:
a token obtaining request receiving unit 401, configured to receive a token obtaining request, which is sent by an application server and pushed by a client and is for a message of an application user who successfully logs in the application server;
a token obtaining unit 402, configured to obtain a message push client login token of the application user;
a token loopback unit 403, configured to loopback the login token to the application server;
a login request receiving unit 404, configured to receive a login request sent by a message push client, where the login request includes the login token;
a determining unit 405, configured to determine, according to the login request, whether the message push client has the right to access the message push server;
a message transmission channel constructing unit 406, configured to construct a message transmission channel with the message push client if it is determined that the message push client has the right to access the message push server.
Optionally, the determining unit 405 includes:
the token analyzing subunit is used for analyzing the login token;
and the right judging subunit is used for judging that the message pushing client has the right to access the message pushing server if the user identifier carried by the login request is the same as the user identifier obtained through analysis, the application identifier carried by the login request is the same as the application identifier obtained through analysis, and the login token is in the valid period.
Optionally, the apparatus further comprises:
a message sending instruction obtaining unit, configured to obtain a message sending instruction, which is sent by the application server and is for the application user; the message sending instruction comprises the user identification of the application user and a message to be sent;
and the message forwarding unit is used for forwarding the message to be sent to the message pushing client through the message transmission channel when the message pushing client successfully logs in.
Optionally, the apparatus further comprises:
and the message cache unit is used for storing the message to be sent corresponding to the application user when the message pushing client is not logged in.
Optionally, the message forwarding unit further includes:
the judging subunit is used for judging whether the message pushing client is running or the message transmission channel is normal;
and the first forwarding subunit is configured to forward the message to be sent to the application user through another message push server if the message push client is not running or the message transmission channel is not normal.
Optionally, the message sending instruction further includes a sending priority of the message to be sent, and the message forwarding unit is specifically configured to forward the message to be sent to the message push client through the message transmission channel according to the sending priority.
Optionally, the apparatus further comprises:
a batch user registration instruction receiving unit, configured to receive a batch user registration instruction sent by the application server; the bulk user registration indication comprises at least one application user;
and the batch user registration unit is used for carrying out user registration on the at least one application user according to the batch user registration instruction.
As can be seen from the foregoing embodiments, the message pushing apparatus provided in the embodiments of the present invention pushes a client login token acquisition request by receiving a message sent by an application server and directed to an application user who successfully logs in the application server; obtaining a message pushing client login token of an application user; returning the login token to an application server; receiving a login request sent by a message pushing client, wherein the login request comprises a login token; judging whether the message pushing client has the right to access the message pushing server or not according to the login request; if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed; by adopting the processing mode, a strict authorization mechanism is adopted when the message pushing client logs in the message pushing server, only the message pushing client of the authorized application user who allows the identity to be verified through the application server can log in the message pushing server, and the message pushing server is prevented from being illegally logged in by a non-application authorized user; therefore, the potential safety hazard of the message push server can be effectively reduced. Meanwhile, the processing mode can also avoid that when the information is pushed to all the application users, the users who illegally log in the information pushing server also receive the pushed information.
Fig. 5 is a block diagram of an electronic device according to an embodiment of the present invention.
The electronic device comprises a processor 501 and a memory 502. Processor 501 performs the process of pushing messages in fig. 3 and/or other processes for the techniques described herein. The memory 502 is used for program code and data for the message push process.
Optionally, the electronic device may further comprise an input device and/or a display, wherein the display may be used to display the message to be pushed.
Optionally, the electronic device may further include a communication interface, and the communication interface is configured to implement communication between the device and other devices. For example, when the device is an RCS, the communication interface may be a Common Public Radio Interface (CPRI) for enabling communication between the RRS and the RCS.
It will be appreciated that fig. 5 is merely a simplified design of an electronic device. It will be appreciated that the electronic device may contain any number of processors, memories, input devices, displays, communication interfaces.
The invention also provides another message pushing method corresponding to the message pushing method.
Another message pushing method embodiment of the present invention is described below with reference to fig. 6.
In 601, the message pushing client receives a login instruction sent by an application client.
After the application client successfully logs in the application server, the application server sends a request for obtaining a login token to the message pushing server, and after the application server obtains the login token, the application server sends the token back to the application client. The application client can send the login instruction to the message pushing client by calling a login interface provided by the message pushing client, wherein the login instruction at least comprises a login token of the message pushing client, so that the message pushing client can send a login request to the message pushing server according to the login token.
It should be noted that, after the application client successfully logs in the application server, the application server generates a login token for the application client, where the login token is used when the application client logs in the application server, and after the application client successfully logs in the application server once, the application server can subsequently log in according to the login token without inputting a user identifier (user) and a login password. In addition, the message pushing server also generates a login token for the message pushing client, and the login token is only used for the message pushing client to log in the message pushing server. Therefore, the scheme provided by the embodiment of the invention can generate two login tokens, and needs to be clearly distinguished.
And at part 602, a login request is sent to a message pushing server, wherein the login request comprises the login token.
The login request can comprise a user identification and a login token of the application user, so that the message push server can authenticate the application user. For a detailed description of the message push server for performing the identity verification on the application user, reference may be made to the above part 304, which is not described herein again.
In one example, another message pushing method provided by the present invention further includes the following steps: 1) receiving a message to be sent, which is forwarded by the message pushing server and sent to an application user by an application server; 2) and forwarding the message to be sent to the application client.
After the message push client successfully logs in the message push server, the message to be sent, which is forwarded by the message push server and is sent to the application user by the application server, can be received through the message transmission channel, after the message to be sent is received, the application client is awakened by calling a message sending interface provided by the application client to the message push client, and the message to be sent is forwarded to the application client, so that the application user can obtain the message.
As can be seen from the foregoing embodiments, in another message pushing method provided in the embodiments of the present invention, a login instruction sent by an application client is received, where the login instruction includes a login token of a message pushing client, and a login request is sent to a message pushing server, where the login request includes the login token; by adopting the processing mode, a strict authorization mechanism is adopted when the message pushing client logs in the message pushing server, only the message pushing client of the authorized application user who allows the identity to be verified through the application server can log in the message pushing server, and the message pushing server is prevented from being illegally logged in by a non-application authorized user; therefore, the potential safety hazard of the message push server can be effectively reduced. Meanwhile, the processing mode can also avoid that when the information is pushed to all the application users, the users who illegally log in the information pushing server also receive the pushed information.
The invention also provides another message pushing device corresponding to another message pushing method of the invention.
Fig. 7 is a schematic structural diagram of another message pushing apparatus involved in the foregoing embodiments, where the another message pushing apparatus includes:
a login instruction receiving unit 701, configured to receive a login instruction sent by an application client; the login instruction comprises a message pushing client login token;
a login request sending unit 702, configured to send a login request to a message push server, where the login request includes the login token.
Optionally, the apparatus further comprises:
the message receiving unit is used for receiving a message to be sent, which is forwarded by the message pushing server and is sent to an application user by an application server;
and the message forwarding unit is used for forwarding the message to be sent to the application client.
It can be seen from the foregoing embodiment that, in another message pushing apparatus provided in the embodiment of the present invention, by receiving a login instruction sent by an application client, where the login instruction includes a login token of the message pushing client, and sending a login request to a message pushing server, where the login request includes the login token; by adopting the processing mode, a strict authorization mechanism is adopted when the message pushing client logs in the message pushing server, only the message pushing client of the authorized application user who allows the identity to be verified through the application server can log in the message pushing server, and the message pushing server is prevented from being illegally logged in by a non-application authorized user; therefore, the potential safety hazard of the message push server can be effectively reduced. Meanwhile, the processing mode can also avoid that when the information is pushed to all the application users, the users who illegally log in the information pushing server also receive the pushed information.
Fig. 8 is a block diagram of another electronic device according to an embodiment of the present invention.
The electronic device comprises a processor 801 and a memory 802. The processor 801 performs the process of message pushing in fig. 6 and/or other processes for the techniques described herein. The memory 802 is used for storing program codes and data for the message push process.
Optionally, the electronic device may further comprise an input device and/or a display.
Optionally, the electronic device may further include a communication interface, and the communication interface is configured to implement communication between the device and other devices. For example, when the device is an RCS, the communication interface may be a Common Public Radio Interface (CPRI) for enabling communication between the RRS and the RCS.
It will be appreciated that fig. 8 is merely a simplified design of an electronic device. It will be appreciated that the electronic device may contain any number of processors, memories, input devices, displays, communication interfaces.
The invention also provides another message pushing method corresponding to the message pushing method.
Another embodiment of the message pushing method according to the present invention is described below with reference to fig. 9.
In 901, an application server receives a login request sent by an application client for an application user.
And the application user sends a login request to the application server through the application client, and the application user can use the application service after the login request passes.
After receiving a login request aiming at an application user and sent by an application client, the application server can enter the next step to verify the identity of the application user.
At 902, when the application user is determined to be logged in, sending a message pushing client login token acquisition request for the application user to a message pushing server.
And when the application user is judged to be an authorized user through login, sending a message pushing client login token acquisition request aiming at the application user to a message pushing server.
At 903, a message push client login token returned by the message push server is received.
The message pushing server generates a message pushing client login token for the application user who successfully logs in the application server, and sends the token back to the application server. After receiving the token, the application server may proceed to the next step of sending the token to the application client.
At 904, the login token is returned to the application client.
In one example, another message pushing method provided by the present invention further includes the following steps: 1) the application server acquires a message to be sent for the application user; 2) if the application client cannot receive the message, sending a message sending instruction aiming at the application user to the message pushing server; the message sending instruction comprises the user identification of the application user and a message to be sent. And after receiving the message sending instruction, the message pushing server pushes the application message to the application client through the message pushing client.
The message to be sent may be a message sent by one application user to another application user, or may be a message sent by the application server to the application user. For a specific description of the manner in which the application server sends the message sending instruction to the message push server and the manner in which the message push server processes the message sending instruction, reference may be made to the description of the relevant part of the foregoing embodiment, which is not described herein again.
It can be seen from the foregoing embodiments that, in another message pushing method provided in the embodiments of the present invention, a login request for an application user sent by an application client is received; when the application user is judged to pass login, sending a message pushing client login token acquisition request aiming at the application user to a message pushing server; receiving a message pushing client login token returned by the message pushing server; returning the login token to the application client; by adopting the processing mode, a strict authorization mechanism is adopted when the message pushing client logs in the message pushing server, only the message pushing client of the authorized application user who allows the identity to be verified through the application server can log in the message pushing server, and the message pushing server is prevented from being illegally logged in by a non-application authorized user; therefore, the potential safety hazard of the message push server can be effectively reduced. Meanwhile, the processing mode can also avoid that when the information is pushed to all the application users, the users who illegally log in the information pushing server also receive the pushed information.
The invention also provides a message pushing device corresponding to the message pushing method.
Fig. 10 is a schematic structural diagram of another message pushing apparatus according to the foregoing embodiment, where the yet another message pushing apparatus includes:
a login request receiving unit 1001 configured to receive a login request for an application user sent by an application client;
a token obtaining request sending unit 1002, configured to send a message pushing client login token obtaining request for the application user to a message pushing server when it is determined that the application user passes login;
a token receiving unit 1003, configured to receive a message push client login token returned by the message push server;
a token loopback unit 1004 for looping back the login token to the application client.
Optionally, the apparatus further comprises:
a message obtaining unit, configured to obtain a message to be sent for the application user;
a message sending instruction sending unit, configured to send a message sending instruction for the application user to the message push server if it is determined that the application client cannot receive the message; the message sending instruction comprises the user identification of the application user and a message to be sent.
It can be seen from the foregoing embodiments that, in another message pushing method provided in the embodiments of the present invention, a login request for an application user sent by an application client is received; when the application user is judged to pass login, sending a message pushing client login token acquisition request aiming at the application user to a message pushing server; receiving a message pushing client login token returned by the message pushing server; returning the login token to the application client; by adopting the processing mode, a strict authorization mechanism is adopted when the message pushing client logs in the message pushing server, only the message pushing client of the authorized application user who allows the identity to be verified through the application server can log in the message pushing server, and the message pushing server is prevented from being illegally logged in by a non-application authorized user; therefore, the potential safety hazard of the message push server can be effectively reduced. Meanwhile, the processing mode can also avoid that when the information is pushed to all the application users, the users who illegally log in the information pushing server also receive the pushed information.
Fig. 11 is a block diagram of still another electronic device according to an embodiment of the present invention.
The electronic device includes a processor 1101 and a memory 1102. Processor 1101 performs the process of pushing messages in fig. 9 and/or other processes for the techniques described herein. The memory 1102 is used for storing program codes and data for the message push procedure.
Optionally, the electronic device may further comprise an input device and/or a display.
Optionally, the electronic device may further include a communication interface, and the communication interface is configured to implement communication between the device and other devices. For example, when the device is an RCS, the communication interface may be a Common Public Radio Interface (CPRI) for enabling communication between the RRS and the RCS.
It will be appreciated that fig. 11 is merely a simplified design of an electronic device. It will be appreciated that the electronic device may contain any number of processors, memories, input devices, displays, communication interfaces.
The invention also provides another message pushing method corresponding to the message pushing method.
An embodiment of a further message pushing method according to the present invention is described below with reference to fig. 12.
At 1201, the application client sends a login request for the application user to the application server.
The portion 1201 corresponds to the portion 901, and for specific description, reference may be made to the portion 901, which is not described herein again.
At 1202, a message push client login token returned by the application server is received.
The portion 1202 corresponds to the portion 904, and for the specific description, reference may be made to the portion 904, which is not described herein again.
At 1203, sending a login instruction to the message pushing client; the login indication comprises the login token.
Portion 1203 corresponds to portion 601, and for a detailed description, reference may be made to portion 601, which is not described herein again.
In one example, the message pushing method further includes the following steps: 1) receiving a message to be sent, which is forwarded by the message pushing client and sent to the application user by the application server; 2) and displaying the message to be sent to the application user.
As can be seen from the foregoing embodiments, in yet another message pushing method provided in the embodiments of the present invention, a login request for an application user is sent to an application server; receiving a message pushing client login token returned by the application server; sending a login instruction to a message pushing client; the login indication comprises the login token; by adopting the processing mode, a strict authorization mechanism is adopted when the message pushing client logs in the message pushing server, only the message pushing client of the authorized application user who allows the identity to be verified through the application server can log in the message pushing server, and the message pushing server is prevented from being illegally logged in by a non-application authorized user; therefore, the potential safety hazard of the message push server can be effectively reduced. Meanwhile, the processing mode can also avoid that when the information is pushed to all the application users, the users who illegally log in the information pushing server also receive the pushed information.
The invention also provides another message pushing device corresponding to the other message pushing method.
Fig. 13 is a schematic structural diagram of another message pushing apparatus involved in the foregoing embodiment, where the yet another message pushing apparatus includes:
a login request sending unit 1301, configured to send a login request for an application user to an application server;
a token loopback unit 1302, configured to receive a message pushed by the application server to push a client login token;
a login instruction sending unit 1303, configured to send a login instruction to the message push client; the login indication comprises the login token.
Optionally, the apparatus further comprises:
a message receiving unit, configured to receive a message to be sent, which is forwarded by the message push client and sent to the application user by the application server;
and the message display unit is used for displaying the message to be sent to the application user.
As can be seen from the foregoing embodiments, in yet another message pushing method provided in the embodiments of the present invention, a login request for an application user is sent to an application server; receiving a message pushing client login token returned by the application server; sending a login instruction to a message pushing client; the login indication comprises the login token; by adopting the processing mode, a strict authorization mechanism is adopted when the message pushing client logs in the message pushing server, only the message pushing client of the authorized application user who allows the identity to be verified through the application server can log in the message pushing server, and the message pushing server is prevented from being illegally logged in by a non-application authorized user; therefore, the potential safety hazard of the message push server can be effectively reduced. Meanwhile, the processing mode can also avoid that when the information is pushed to all the application users, the users who illegally log in the information pushing server also receive the pushed information.
Fig. 14 is a block diagram of still another electronic device according to an embodiment of the present invention.
The electronic device comprises a processor 1401 and a memory 1402. Processor 1401 performs the process of pushing messages in fig. 12 and/or other processes for the techniques described herein. The memory 1402 is used for storing program codes and data for the message push procedure.
Optionally, the electronic device may further comprise an input device and/or a display.
Optionally, the electronic device may further include a communication interface, and the communication interface is configured to implement communication between the device and other devices. For example, when the device is an RCS, the communication interface may be a Common Public Radio Interface (CPRI) for enabling communication between the RRS and the RCS.
It will be appreciated that fig. 14 is merely a simplified design of an electronic device. It will be appreciated that the electronic device may contain any number of processors, memories, input devices, displays, communication interfaces.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
The same and similar parts in the various embodiments in this specification may be referred to each other. Especially, for embodiments of a message pushing apparatus, the latter three message pushing methods and apparatuses, since they are substantially similar to the first message pushing method embodiment, the description is relatively simple, and for relevant points, reference may be made to the description in the first message pushing method embodiment.
The above-described embodiments of the present invention should not be construed as limiting the scope of the present invention.

Claims (10)

1. A message pushing method is used for a message pushing server, and is characterized by comprising the following steps:
receiving a message pushing client login token acquisition request sent by an application server and aiming at an application user who successfully logs in the application server;
obtaining a message pushing client login token of the application user;
returning the login token to the application server;
receiving a login request sent by a message pushing client, wherein the login request comprises a login token;
judging whether the message pushing client has the right to access the message pushing server or not according to the login request;
if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed;
and pushing the application message sent to the application client by the application server according to the message transmission channel.
2. The method of claim 1, further comprising:
acquiring a message sending instruction aiming at the application user and sent by the application server; the message sending instruction comprises the user identification of the application user and a message to be sent;
and when the message pushing client successfully logs in, forwarding the message to be sent to the message pushing client through the message transmission channel.
3. A message pushing method is used for a message pushing client, and is characterized by comprising the following steps:
receiving a login instruction sent by an application client; the login instruction comprises a message pushing client login token;
sending a login request to a message pushing server, wherein the login request comprises the login token, so that the message pushing server executes:
judging whether a message pushing client has the right to access the message pushing server or not according to the login request; if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed; pushing an application message sent to an application client by an application server according to the message transmission channel;
the message pushing server is further used for executing: acquiring a message sending instruction aiming at an application user and sent by the application server; the message sending instruction comprises the user identification of the application user and a message to be sent;
and when the message pushing client successfully logs in, forwarding the message to be sent to the message pushing client through the message transmission channel.
4. A message pushing method for an application server, comprising:
receiving a login request aiming at an application user and sent by an application client;
when the application user is judged to pass login, sending a message pushing client login token acquisition request aiming at the application user to a message pushing server;
receiving a message pushing client login token returned by the message pushing server;
returning the login token to the application client so that the application client sends a login instruction to a message pushing client, wherein the login instruction comprises the login token;
the message pushing client is used for executing: sending a login request to a message pushing server, wherein the login request comprises the login token, so that the message pushing server executes:
judging whether a message pushing client has the right to access the message pushing server or not according to the login request; if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed; and pushing the application message sent to the application client by the application server according to the message transmission channel.
5. A message pushing method for an application client, comprising:
sending a login request aiming at an application user to an application server;
receiving a message pushing client login token returned by the application server;
sending a login instruction to a message pushing client; the login indication comprises the login token; the message pushing client is used for executing: sending a login request to a message pushing server, wherein the login request comprises the login token, so that the message pushing server executes:
judging whether a message pushing client has the right to access the message pushing server or not according to the login request; if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed; and pushing the application message sent to the application client by the application server according to the message transmission channel.
6. A message push apparatus, comprising:
the system comprises a token obtaining request receiving unit, a token obtaining unit and a token sending unit, wherein the token obtaining request receiving unit is used for receiving a message pushing client login token obtaining request which is sent by an application server and aims at an application user who successfully logs in the application server;
the token acquisition unit is used for acquiring a message pushing client login token of the application user;
a token loopback unit, configured to loopback the login token to the application server;
a login request receiving unit, configured to receive a login request sent by a message push client, where the login request includes the login token;
the judging unit is used for judging whether the message pushing client side has the right to access the message pushing server according to the login request;
the message transmission channel construction unit is used for constructing a message transmission channel between the message pushing client and the message pushing server if the message pushing client is judged to have the right to access the message pushing server;
and pushing the application message sent to the application client by the application server according to the message transmission channel.
7. A message push apparatus, comprising:
a login instruction receiving unit, configured to receive a login instruction sent by an application client; the login instruction comprises a message pushing client login token;
a login request sending unit, configured to send a login request to a message push server, where the login request includes the login token, so that the message push server executes:
judging whether a message pushing client has the right to access the message pushing server or not according to the login request; if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed;
the message pushing server is further used for executing: acquiring a message sending instruction aiming at an application user and sent by an application server; the message sending instruction comprises the user identification of the application user and a message to be sent;
and when the message pushing client successfully logs in, forwarding the message to be sent to the message pushing client through the message transmission channel.
8. A message push apparatus, comprising:
a login request receiving unit, configured to receive a login request for an application user sent by an application client;
a token obtaining request sending unit, configured to send a message pushing client login token obtaining request for the application user to a message pushing server when it is determined that the application user passes login;
the token receiving unit is used for receiving a message pushing client login token returned by the message pushing server;
a token loopback unit, configured to loopback the login token to the application client, so that the application client sends a login instruction to a message push client, where the login instruction includes the login token;
the message pushing client is used for executing: sending a login request to a message pushing server, wherein the login request comprises the login token, so that the message pushing server executes:
judging whether a message pushing client has the right to access the message pushing server or not according to the login request; if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed; and pushing the application message sent to the application client by the application server according to the message transmission channel.
9. A message push apparatus, comprising:
a login request sending unit, configured to send a login request for an application user to an application server;
the token loopback unit is used for receiving the message pushed by the application server and pushing a client login token;
a login instruction sending unit, configured to send a login instruction to the message push client; the login indication comprises the login token; the message pushing client is used for executing: sending a login request to a message pushing server, wherein the login request comprises the login token, so that the message pushing server executes:
judging whether a message pushing client has the right to access the message pushing server or not according to the login request; if the message pushing client is judged to have the right to access the message pushing server, a message transmission channel between the message pushing client and the message pushing client is constructed; and pushing the application message sent to the application client by the application server according to the message transmission channel.
10. A message push system, comprising: the message pushing device according to claim 6, the message pushing device according to claim 7, the message pushing device according to claim 8, or the message pushing device according to claim 9.
CN201711291885.5A 2017-12-08 2017-12-08 Message pushing method, device and system Active CN109905312B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711291885.5A CN109905312B (en) 2017-12-08 2017-12-08 Message pushing method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711291885.5A CN109905312B (en) 2017-12-08 2017-12-08 Message pushing method, device and system

Publications (2)

Publication Number Publication Date
CN109905312A CN109905312A (en) 2019-06-18
CN109905312B true CN109905312B (en) 2021-07-23

Family

ID=66940106

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711291885.5A Active CN109905312B (en) 2017-12-08 2017-12-08 Message pushing method, device and system

Country Status (1)

Country Link
CN (1) CN109905312B (en)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110659006B (en) * 2019-08-20 2023-08-22 北京捷通华声科技股份有限公司 Cross-screen display method and device, electronic equipment and readable storage medium
CN110769064B (en) * 2019-10-29 2023-02-24 广州趣丸网络科技有限公司 System, method and equipment for offline message pushing
CN110691146B (en) * 2019-11-15 2022-09-06 深圳市乐唯科技开发有限公司 Method for rapidly pushing in large batch
CN110855792B (en) * 2019-11-19 2023-04-18 南京领行科技股份有限公司 Message pushing method, device, equipment and medium
CN113014615B (en) * 2019-12-20 2023-11-14 西安诺瓦星云科技股份有限公司 Data synchronization method, device and system
CN112235184B (en) * 2020-09-08 2023-02-10 北京首钢自动化信息技术有限公司 Event-driven information pushing method and device and electronic equipment
CN113302881B (en) * 2020-12-01 2023-05-02 百果园技术(新加坡)有限公司 Method, device, chat terminal, server and storage medium for realizing online chat
CN113315868B (en) * 2021-05-31 2023-03-21 上海祺康科技有限公司 Message receiving method, device and equipment based on mobile phone screen-off state
CN113536134A (en) * 2021-07-30 2021-10-22 北京乐学帮网络技术有限公司 Message pushing method and device, electronic equipment and readable storage medium
CN115914367B (en) * 2023-02-17 2023-05-30 福建联迪商用科技有限公司 Message pushing method and system of intelligent device

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102347967A (en) * 2010-07-30 2012-02-08 华为技术有限公司 Method and device for cooperation between push equipment
CN103051715A (en) * 2012-12-24 2013-04-17 东软熙康健康科技有限公司 Method for releasing notice to terminal, relevant device and system
EP2899945A1 (en) * 2014-01-23 2015-07-29 Deutsche Telekom AG Method for an enhanced communication between a first network node and a second network node of a telecommunications network, and telecommunications network
CN105162838A (en) * 2015-07-30 2015-12-16 青岛海尔智能家电科技有限公司 Message pushing method, and method and device for receiving pushed message
CN105872028A (en) * 2016-03-25 2016-08-17 努比亚技术有限公司 Server, client, and access policy management method
CN106341301A (en) * 2015-07-08 2017-01-18 中兴通讯股份有限公司 Message pushing method and device
CN106385318A (en) * 2016-09-06 2017-02-08 北京叮叮关爱科技有限公司 SDK verification method based on elliptic equation
CN106412138A (en) * 2016-12-21 2017-02-15 广州四三九九信息科技有限公司 Tag-free precise pushing method and equipment
CN106790728A (en) * 2017-03-30 2017-05-31 北京深思数盾科技股份有限公司 information push method and system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016167536A1 (en) * 2015-04-13 2016-10-20 Samsung Electronics Co., Ltd. Method and apparatus for managing a profile of a terminal in a wireless communication system

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102347967A (en) * 2010-07-30 2012-02-08 华为技术有限公司 Method and device for cooperation between push equipment
CN103051715A (en) * 2012-12-24 2013-04-17 东软熙康健康科技有限公司 Method for releasing notice to terminal, relevant device and system
EP2899945A1 (en) * 2014-01-23 2015-07-29 Deutsche Telekom AG Method for an enhanced communication between a first network node and a second network node of a telecommunications network, and telecommunications network
CN106341301A (en) * 2015-07-08 2017-01-18 中兴通讯股份有限公司 Message pushing method and device
CN105162838A (en) * 2015-07-30 2015-12-16 青岛海尔智能家电科技有限公司 Message pushing method, and method and device for receiving pushed message
CN105872028A (en) * 2016-03-25 2016-08-17 努比亚技术有限公司 Server, client, and access policy management method
CN106385318A (en) * 2016-09-06 2017-02-08 北京叮叮关爱科技有限公司 SDK verification method based on elliptic equation
CN106412138A (en) * 2016-12-21 2017-02-15 广州四三九九信息科技有限公司 Tag-free precise pushing method and equipment
CN106790728A (en) * 2017-03-30 2017-05-31 北京深思数盾科技股份有限公司 information push method and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Android应用第三方推送服务安全分析与安全增强";路晔绵,等;《计算机研究与发展》;20161130;第2431-2445页 *

Also Published As

Publication number Publication date
CN109905312A (en) 2019-06-18

Similar Documents

Publication Publication Date Title
CN109905312B (en) Message pushing method, device and system
US10116448B2 (en) Transaction authorization method and system
EP3013086B1 (en) Method, apparatus and electronic device for connection management
CN110351269B (en) Method for logging in open platform through third-party server
US9548975B2 (en) Authentication method, authentication system, and service delivery server
CN104980298B (en) A kind of abnormal prompt method, apparatus and system
CN102572815B (en) Method, system and device for processing terminal application request
CN104052775B (en) Right management method, device and the system of a kind of cloud platform service
US9344896B2 (en) Method and system for delivering a command to a mobile device
CN109474595B (en) Electronic equipment binding method, electronic equipment, mobile terminal and server
CN107484032B (en) Prevent the verification method brushed and device
US9401905B1 (en) Transferring soft token authentication capabilities to a new device
CN107567017B (en) Wireless connection system, device and method
CN105577662B (en) Terminal environments method of controlling security and server
CN109862078B (en) Client login method, device and system, storage medium and electronic device
US9661495B2 (en) Device activation method and system
CN106464502B (en) Method and system for authentication of a communication device
ES2785048T3 (en) Automatic connection to an online service
CN112968892B (en) Information verification method, device, computing equipment and medium
CN108156169A (en) Account login validation method, system and computer readable storage medium
CN114760112B (en) Wireless local area network-oriented intelligent home equipment networking method, system, equipment and storage medium
CN110602133B (en) Intelligent contract processing method, block chain management device and storage medium
CN103312673B (en) Enterprise mobile application system and its application process
CN105577621B (en) Business operation verification method, device and system
CN116208956A (en) Login method and device of intercom terminal, electronic equipment and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information
CB02 Change of applicant information

Address after: Room 810, 8 / F, 34 Haidian Street, Haidian District, Beijing 100080

Applicant after: BEIJING D-MEDIA COMMUNICATION TECHNOLOGY Co.,Ltd.

Address before: 100089 Beijing city Haidian District wanquanzhuang Road No. 28 Wanliu new building block A room 602

Applicant before: BEIJING D-MEDIA COMMUNICATION TECHNOLOGY Co.,Ltd.

GR01 Patent grant
GR01 Patent grant