CN116436887A - Method and system for pushing messages - Google Patents

Abstract

The invention discloses a message pushing method and a system, wherein the method comprises the following steps: acquiring a ClientUUID of a client, and generating a main message queue based on a service request containing a message to be pushed of the client; consuming the main Message queue to obtain a Message pushing notification containing a Message to be pushed and a corresponding Message ID and type; judging whether the client is online or not based on the ClientUUID of the client; pushing the message pushing notification to the client under the condition that the client is online; and under the condition that the client is not online, sending the client ClientUUID, the Message ID, the type and the private equipment ID of the client to a platform so as to transfer information based on the client ClientUUID through the platform and a third party platform, and enabling the client to acquire the Message to be pushed in the private equipment based on the Message ID, the type and the private equipment ID. The invention ensures the safety of user data and prevents a third party from acquiring data information.

Description

Method and system for pushing messages

technical field

The present invention relates to the communication field, and in particular designs a method and system for pushing messages.

Background technique

As an important bridge connecting the client and the server, message push is an important interactive way for users to perceive information and experience business functions. Building a message push mechanism in the system enables business operations to transmit the application information of the push module to users in a stable and timely manner. At present, Internet big data is developing rapidly, and the number of user groups is huge. In order to ensure that the majority of user groups can realize functional experience, they usually choose to support push services based on third-party push platforms, which not only realizes efficient information transmission, but also leads to user information leakage. question. The user's personal data does not belong to the individual, the data is changed hands, the information is leaked, and the private information becomes a transaction for various platforms to realize commercial interests.

Contents of the invention

In order to solve the above-mentioned problems in the prior art, the present invention provides a message push method and system. The system protects user data security while ensuring user experience, and prevents the risk of information leakage.

The technical contents of the present invention include:

A method for pushing messages, applied to a private device establishing a trust relationship with a client, the method comprising:

Obtain the ClientUUID of the client, and generate a main message queue based on the client's business request including the message to be pushed;

Consuming the main message queue to obtain the message push notification containing the message to be pushed and the Message ID and type corresponding to the message to be pushed;

Based on the ClientUUID of the client, determine whether the client is online;

When the client is online, push the message push notification to the client;

When the client is not online, send the client's ClientUUID, the Message ID, the type, and the private device ID to the platform, so as to use the platform and a third-party platform based on the client's The ClientUUID performs information transfer, and enables the client to obtain the message to be pushed from the private device based on the Message ID, the type, and the private device ID.

Further, the determining whether the client is online based on the ClientUUID of the client includes:

Establish a long poll with the client;

When the client requests the poll interface to carry an encrypted access token, save the timestamp of the ClientUUID;

In the case that the difference between the current time and the timestamp is greater than a set value, or a preset identifier is found, it is determined that the client is not online; wherein the preset identifier indicates that the client actively disconnects;

If the difference between the current time and the timestamp is less than a set value and no preset identifier is found, it is determined that the client is online.

Further, the pushing the message push notification to the client includes:

Generate a client message queue based on the message push notification;

Pushing the client message queue to the client, so that the client obtains the message to be pushed through the encrypted poll interface.

Further, when the client is not online, sending the client's ClientUUID, the MessageID, the type, and the private device ID to the platform, including:

Generate an offline message queue based on the ClientUUID of the client, the Message ID and type of the message push notification and the private device ID;

Set a preset time range;

Suspend the thread corresponding to the message queue when said offline;

Within the preset time range, if it is determined that the client is online, a client message queue is generated based on the message push notification, and the client message queue is pushed to the client, so that the client Obtain the message to be pushed through the encrypted poll interface;

If it is determined that the client is not online within the preset time range, the offline message queue is sent to the platform.

Further, the platform is based on the ClientUUID of the client, and after passing the Message ID to the client through a third-party platform, the client based on the Message ID, the type and the private device ID Obtaining the message to be pushed in the private device includes:

The platform obtains the deviceTokens of all clients through the calling of the third-party platform SDK interface by the client;

The platform obtains the deviceToken corresponding to the client based on the ClientUUID of the client, and after generating a Push message including the Message ID, the type, and the private device ID, sends the deviceToken and the Push message to the the third-party platform;

The third-party platform pushes the Push message to the client based on the deviceToken;

The client accesses the private device based on the Push message to obtain the message to be pushed.

Further, the third-party platform pushes the Push message to the client based on the deviceToken, including:

Get all Push messages of this client;

For all Push messages, establish the timing of Push messages;

Based on the timing sequence of the Push messages, push the Push messages to the client in turn,

Further, the third-party platform includes: Youmeng Push server or Huawei Push server.

A message push system, characterized in that the system includes:

The client is used to provide the ClientUUID of the client and the service request containing the message to be pushed;

The private device is used to obtain the ClientUUID of the client, and generate a main message queue based on the client's business request containing the message to be pushed; consume the main message queue to obtain a message push notification containing the message to be pushed and the message to be pushed Message ID and type corresponding to the message; based on the ClientUUID of the client, judge whether the client is online; when the client is online, push the message push notification to the client; when the client is not In the case of online, send the ClientUUID, the Message ID, the type and the private device ID of the client to the platform;

The platform is configured to send the ClientUUID of the client, the MessageID, the type, and the private device ID to a third-party platform based on the ClientUUID of the client;

The third-party platform is configured to send the Message ID, the type, and the private device ID to the client based on the ClientUUID of the client.

An electronic device comprising:

processor;

memory for storing said processor-executable instructions;

The processor is configured to read the executable instruction from the memory, and execute the executable instruction to implement any one of the above methods.

A computer-readable storage medium, on which computer program instructions are stored, is characterized in that, when the program instructions are executed by a processor, any one of the above-mentioned methods can be realized.

Compared with the prior art, the present invention has at least the following advantages:

In the message push method and system provided by the present invention, different message push modes are designed according to the state of the client. When the client is online, the end-to-end encrypted in-app push is realized, so that the user can receive the message notification in a timely, fast, efficient, stable and safe manner. When the client is offline, although it relies on the third-party platform to forward and realize the push, the third party cannot obtain the specific push content, so as to ensure the security of user data and prevent the third party from obtaining data information.

Description of drawings

Figure 1. Message push system diagram.

Figure 2 Message push flow chart.

Fig. 3 The specific steps of the operation of the private device processing module.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

The message push system of the present invention includes: a client, a private device, a platform, and a third-party platform. The client is a terminal program through which users can receive push messages, including APP, Web, and PC. The platform is a transfer scheduling management platform for the private device and the client, and is used to manage client device identification, transfer messages, cached data, and other content. The private device is used to store, process business and push messages, and choose whether to access related content such as external third-party platforms (youmeng or other manufacturers' channels) based on the status of the client, so as to realize message push. It may be a hardware device including a processor and a memory in which a computer program is stored, or a storage medium in which a computer program is stored.

1. Construction of the message push system.

As shown in FIG. 1 , message push is divided into in-app push and system push based on the state of the client. When the client is online, in-app push can be implemented. When the client is offline, it needs to use the forwarding message of the platform to push to the channel of the third-party manufacturer for sending.

as shown in picture 2. The message push module of the private device judges the status of the client by referring to the timestamp of the client ClientUUID. When the client is online, the client and the private device directly establish a long poll, and the message push module sends the content of the message to be pushed to the client A separate queue for clientuuid, the private device pushes the message content to the corresponding client, and the client obtains the message data to be pushed to the client through the encrypted poll interface to realize in-app push. The private device belongs to the user's personal storage device, and the poll interface invoked by the client is encrypted with a public-private key encryption negotiated symmetric key, and the contained message data is not read or recorded by the platform to ensure the user's data security .

As shown in Figure 3, the message push module of the private device judges the status of the client by referring to the timestamp of the client ClientUUID. When the client is offline, the message push module sends the content of the message to be pushed to the push_notification_platform (message queue when offline) queue , and send the Message ID, type, and ClientUUID to the platform and third-party vendor channels. What is passed in this forwarding process is the Message ID, type and ClientUUID, but does not contain the specific data content of the message, and the message itself is still stored in the private device. After the third-party vendor channel returns it to the target client, the client requests the private device to obtain specific message content based on the received Message ID.

Specifically, the poll interface of the call message push between the client and the private device presets an encryption scheme to establish a trust relationship. When the client initiates an access request to the private device, it will carry an accessToken for authentication, thereby ensuring data security. .

Specifically, the offline push method will have a slightly smaller delay than the online in-app push method, but the two push methods simultaneously ensure the user's data security.

Specifically, the private device includes a message push module, a service module, and a data storage module. The message push module establishes message long polling with the client sending the request, and is responsible for scheduling messages to be pushed, encrypting push message data, and accurately pushing content to the client side or the platform side; the business module Receive the service request of the request client, convert and generate the push message that needs to be notified and the Message ID corresponding to the message and store it all in the data storage module; the data storage module is used to record and store the message push notification or query the message notification to generate the message queue, and send the received message push notification to the message push module.

Specifically, the service module in the private device will store the generated message to be notified in the message queue of the data storage module; when the message push module obtains the message push notification, it will push it to the corresponding The above platform can handle multiple messages and push requests from multiple clients at the same time.

Specifically, the platform includes a management module, a forwarding module, and a cache module. The forwarding module is used to verify the identity of the private device, receive the forwarded message and send it to the corresponding third-party vendor channel; the cache module is used to cache certain time-sensitive message data, so as to support network abnormalities or third-party vendor channel systems Abnormal situation: the management module is used for coordinating and managing the device identification (deviceToken) and other content of the client.

Specifically, the delivery of the message push will follow the same time sequence, and push in order to avoid the result of chaotic push of multiple messages from the same client.

2. Platform integration.

Taking the client-side APP as an example, the client-side APP will generate a ClientUUID as the unique identification code of the corresponding user equipment, which is used for the connection between the private device side and the platform side for subsequent message push; integration of other optional first Three-party vendor channels, such as Youmeng Push server, Huawei Push server, etc. The platform sets a message push interface for the private device, and verifies the identity information of the private device through boxRegKey authentication; determines the push channel according to the status of the client-side APP, and uses the ClientUUID to identify the target push device to push messages. The platform sets a deviceToken registration interface for the APP side of the client, and the deviceToken corresponds to the ClientUUID previously generated on the App side. The platform side registers the identity certificate. Specifically, the platform relays the pushed message, does not read and record the pushed message data, and only transmits the Message ID in the message. For the channel forwarded by the platform to Youmeng or a third-party manufacturer, the timing of the message is not determined by the platform, but is guaranteed based on the selected Youmeng or third-party manufacturer.

Among them, taking the form of client-side APP as an example, the specific steps for users to implement message push:

1. The APP is preset with the PushSDK of third-party manufacturers such as Youmeng and Huawei. When the user client APP is online, it is directly pushed through the application. When the user client is offline, it will be pushed by connecting to Youmeng or other third-party manufacturer channels; the APP can get the deviceToken by calling the Youmeng SDK interface;

2. The APP reports the obtained deviceToken to the platform;

3. The private device and the platform management module use the saved deviceToken to call the API provided by Youmeng (Push server) to push the Push message.

4. The Umeng Push server will transfer the Push message obtained from the platform through the Push server of other third-party manufacturers, and will send it to the user device corresponding to the deviceToken, and the device will receive the Push message.

Optionally, when the Push server of another third-party manufacturer detects that the device replies with a message, it will send the response status back to the Umeng Push server, and the Umeng Push server can display a notification prompt on the APP.

3. The structure of the message push module of the client and the private device.

The message push module establishes message long polling with the client that sends the request, and is responsible for receiving message push notifications, encrypting push data, and accurately pushing to the platform side. After the message push module receives the service request to push the message from the client, it will store it in the main message queue push_notification. If there are business requirements for multiple clients to send push messages to the private device at the same time, different clients will form a separate message queue, which will be identified by the corresponding ClientUUID.

Specifically, the service request message from the service module will directly enter the main message queue push_notification of the message push module. According to the status of the client, the message is extracted, the message is split and stored in the corresponding message queue, and the automatic storage is carried out at the same time to support subsequent reference and use. If the client (APP) is online, send it to the separate queue of the client ClientUUID; if the client (APP) is offline, send push_notification_platform to push it to the platform, and the platform is based on the second aspect above, Push the message to the corresponding device.

Specifically, the client side is provided with interface polling, which is used to read and judge whether there is a message squeeze in the current ClientUUID individual message queue, and if a message squeeze is detected, it is directly returned to the interface.

Specifically, the time stamp of the ClientUUID is used as a reference for judging the state of the client. When requesting the poll interface to carry an encrypted access token (accestoken), the private device will save the corresponding ClientUUID and timestamp. If the corresponding timestamp is > 1min, the client status at this time is considered to be offline by default. If the user actively disconnects, the timestamp will display a preset identification symbol, which also means offline at this time. After confirming that the client is offline, a preset time (such as 3s) will be used to detect whether there is a message in the push_notification_platform queue to avoid the possibility of missing messages.

Wherein, the specific steps of the operation of the private device processing module are shown in Figure 2:

1. The client sends a message push request to start a thread, the private device business module receives a service request from the client that needs to push a message, and the data storage module records and stores a message push notification or a query message notification to generate a message queue, And send the received message push notification to the message push module.

2. After the message push module receives it, it judges the online status of the client based on the message queue and the timestamp of the ClientUUID of the client. If the client is online, send it to the separate queue of the client ClientUUID; if the client is offline, send push_notification_platform to forward it to the platform;

3. When the client is online, it carries accesToken to access the poll interface. When not blocking, the message push module reads the message from the data storage module, and obtains the ClientUUID from the obtained accesToken. The message read by the message push module will be automatically stored in the database as a historical record, and a message body containing symmetric key encrypted information will be formed and returned to the client. If the message push module does not receive the message, it will adopt a blocking type, and the current thread will be suspended. If there is still no message within the preset time range, an empty message body will be returned overtime; if it is within the preset time range If there is a message, it is the same as the above steps. After reading it, it will be directly returned to the client and stored in the database.

4. When the client is offline, it will set a time period to detect messages in the push_notification_platform queue.

Although specific embodiments and drawings of the present invention are disclosed for the purpose of illustration, the purpose is to help understand the content of the present invention and implement it accordingly, but those skilled in the art can understand that: without departing from the present invention and the appended claims Various substitutions, changes and modifications are possible within the spirit and scope of . Therefore, the present invention should not be limited to the content disclosed in the preferred embodiments and drawings, and the protection scope of the present invention should be defined by the claims.

Claims (10)

1. A message push method, applied to a private device establishing a trust relationship with a client, characterized in that the method comprises: Obtain the ClientUUID of the client, and generate a main message queue based on the client's business request including the message to be pushed; Consuming the main message queue to obtain the message push notification containing the message to be pushed and the Message ID and type corresponding to the message to be pushed; Based on the ClientUUID of the client, determine whether the client is online; When the client is online, push the message push notification to the client; When the client is not online, send the client's ClientUUID, the Message ID, the type, and the private device ID to the platform, so as to use the platform and a third-party platform based on the client's The ClientUUID performs information transfer, and enables the client to obtain the message to be pushed from the private device based on the MessageID, the type, and the private device ID. 2. The method according to claim 1, wherein the determining whether the client is online based on the ClientUUID of the client comprises: Establish a long poll with the client; When the client requests the poll interface to carry an encrypted access token, save the timestamp of the ClientUUID; In the case that the difference between the current time and the timestamp is greater than a set value, or a preset identifier is found, it is determined that the client is not online; wherein the preset identifier indicates that the client actively disconnects; If the difference between the current time and the timestamp is less than a set value and no preset identifier is found, it is determined that the client is online. 3. The method according to claim 1, wherein the pushing the message push notification to the client comprises: Generate a client message queue based on the message push notification; Pushing the client message queue to the client, so that the client obtains the message to be pushed through the encrypted poll interface. 4. The method according to claim 1, wherein when the client is not online, the ClientUUID, the Message ID, the type and the private device ID of the client are sent to the platform ,include: Generate an offline message queue based on the ClientUUID of the client, the Message ID and type of the message push notification and the private device ID; Set a preset time range; Suspend the thread corresponding to the message queue when said offline; Within the preset time range, if it is determined that the client is online, a client message queue is generated based on the message push notification, and the client message queue is pushed to the client, so that the client Obtain the message to be pushed through the encrypted poll interface; If it is determined that the client is not online within the preset time range, the offline message queue is sent to the platform. 5. The method according to claim 1, wherein the platform is based on the ClientUUID of the client, and after passing the MessageID to the client through a third-party platform, the client is based on the MessageID , the type and the private device ID to obtain the message to be pushed in the private device, including: The platform obtains the deviceTokens of all clients through the calling of the third-party platform SDK interface by the client; The platform obtains the deviceToken corresponding to the client based on the ClientUUID of the client, and after generating a Push message including the Message ID, the type, and the private device ID, sends the deviceToken and the Push message to the the third-party platform; The third-party platform pushes the Push message to the client based on the deviceToken; The client accesses the private device based on the Push message to obtain the message to be pushed. 6. The method according to claim 1, wherein the third-party platform pushes the Push message to the client based on the deviceToken, comprising: Get all Push messages of this client; For all Push messages, establish the timing of Push messages; Based on the timing sequence of the Push messages, the Push messages are sequentially pushed to the client. 7. The method according to claim 1, wherein the third-party platform includes: Youmeng Push server, Huawei Push server, Xiaomi Push server, Huawei OAuth service or Xiaomi account service. 8. A message push system, characterized in that the system comprises: The client is used to provide the ClientUUID of the client and the service request containing the message to be pushed; The private device is used to obtain the ClientUUID of the client, and generate a main message queue based on the client's business request containing the message to be pushed; consume the main message queue to obtain a message push notification containing the message to be pushed and the message to be pushed Message ID and type corresponding to the message; based on the ClientUUID of the client, judge whether the client is online; when the client is online, push the message push notification to the client; when the client is not In the case of online, send the ClientUUID, the Message ID, the type and the private device ID of the client to the platform; The platform is configured to send the ClientUUID of the client, the MessageID, the type, and the private device ID to a third-party platform based on the ClientUUID of the client; The third-party platform is configured to send the Message ID, the type, and the private device ID to the client based on the ClientUUID of the client. 9. An electronic device, characterized in that it comprises: processor; memory for storing said processor-executable instructions; The processor is configured to read the executable instruction from the memory, and execute the executable instruction to implement the method in any one of claims 1-7. 10. A computer-readable storage medium, on which computer program instructions are stored, wherein when the program instructions are executed by a processor, the method according to any one of claims 1-7 can be implemented.

Images