WO2022088804A1

WO2022088804A1 - Message pushing method and apparatus, and electronic device, and storage medium

Info

Publication number: WO2022088804A1
Application number: PCT/CN2021/109393
Authority: WO
Inventors: 刘慧芳
Original assignee: 深圳壹账通智能科技有限公司
Priority date: 2020-10-30
Filing date: 2021-07-29
Publication date: 2022-05-05
Also published as: CN112367246B; CN112367246A

Abstract

The present application relates to the technical field of big data, and provides a message pushing method and apparatus, and an electronic device, and a storage medium. The method comprises: parsing a message pushing request to obtain a message body of a message to be pushed and a device identifier of a second server; obtaining, according to the message body of said message, a message type of said message and at least one push address value; when the message type of said message is a first type, determining, according to the at least one push address value and the device identifier of the second server, a device identifier of at least one terminal device to which a message is to be pushed; and generating a target push message according to the message body of the message to be pushed and the device identifier of the at least one terminal device to which a message is to be pushed, and pushing the target push message to the at least one terminal device to which a message is to be pushed. According to the present application, different pushing modes are determined according to message types of different messages to be pushed, there by achieving one-time pushing, and missing a user is avoided in the interaction process, thereby improving the message pushing accuracy.

Description

Message push method, device, electronic device and storage medium

This application claims the priority of the Chinese patent application entitled "Message Pushing Method, Device, Electronic Device and Storage Medium" with the application number 202011198143.X, which was filed with the China Patent Office on October 30, 2020, the entire contents of which are by reference Incorporated in this application.

technical field

The present application relates to the technical field of big data, and in particular to a message push method, device, electronic device and storage medium.

Background technique

Message push is one of the important channels for the operation of third-party application programs. It obtains user attention through push messages. The existing message push scheme is relatively simple. When pushing messages, the inventor found that it is necessary to obtain the information of all users, and then send messages one by one. Assembling and sending in batches, especially when the number of users is large, requires high system configuration and takes a long time to push messages. It is easy to cause loss of user information during the interaction process, resulting in a high error rate of message push.

SUMMARY OF THE INVENTION

In view of the above content, it is necessary to propose a message push method, device, electronic device and storage medium. By determining different push methods according to different message types of messages to be pushed, one-time push is realized without omission in the interaction process. The phenomenon of users improves the accuracy of message push.

A first aspect of the present application provides a message push method, which is applied to a first server, and the method includes:

receiving a push message request sent by the second server;

Parsing the push message request to obtain the message body of the message to be pushed and the device identifier of the second server;

Obtain the message type and at least one push address value of the message to be pushed according to the message body of the message to be pushed;

When the message type of the message to be pushed is the first type of message, determine the device identification of at least one terminal device to be pushed according to the at least one push address value and the device identification of the second server;

A target push message is generated according to the message body of the message to be pushed and the device identifier of at least one terminal device to be pushed, and the target push message is pushed to the at least one terminal device to be pushed according to a preset push rule.

A second aspect of the present application provides an electronic device, the electronic device comprising a memory and a processor, the memory for storing at least one computer-readable instruction, the processor for executing the at least one computer-readable instruction to Implement the following steps:

receiving a push message request sent by the second server;

A third aspect of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores at least one computer-readable instruction, and when the at least one computer-readable instruction is executed by a processor, implements the following steps:

receiving a push message request sent by the second server;

A fourth aspect of the present application provides a message push device, which runs on the first server, and the device includes:

a receiving module, configured to receive a push message request sent by the second server;

a parsing module, configured to parse the push message request to obtain the message body of the message to be pushed and the device identifier of the second server;

an obtaining module, configured to obtain the message type and at least one push address value of the message to be pushed according to the message body of the message to be pushed;

a determining module, configured to determine the device identification of at least one terminal device to be pushed according to the at least one push address value and the device identification of the second server when the message type of the message to be pushed is the first type of message;

a push module, configured to generate a target push message according to the message body of the message to be pushed and the device identifier of at least one terminal device to be pushed, and push the target push message to the at least one to be pushed message according to a preset push rule Terminal Equipment.

To sum up, the message push method, device, electronic device and storage medium described in this application, on the one hand, determine different push methods according to the message types of different messages to be pushed, if it is the first type of message, that is, For full push, it only needs to match the device ID of at least one terminal device corresponding to at least one push address value in the push message request, then one-time push can be realized, avoiding pulling the user corresponding to each terminal device one by one according to the push address. The phenomenon that messages are assembled one by one and sent in batches reduces the time for message push; on the other hand, through one-time push, users will not be missed during the interaction process, which improves the accuracy of message push; Finally, according to the first server, the second server and the terminal device by associating the initialization ID, the device feature collection SDK can timely collect the device features of the terminal device and report it to the first service The terminal and the second server improve the timeliness of the device features of the terminal device, thereby improving the accuracy of message push.

Description of drawings

FIG. 1 is a flowchart of a message pushing method provided by Embodiment 1 of the present application.

FIG. 2 is a structural diagram of a message pushing apparatus provided in Embodiment 2 of the present application.

FIG. 3 is a schematic structural diagram of an electronic device provided in Embodiment 3 of the present application.

Detailed ways

In order to more clearly understand the above objects, features and advantages of the present application, the present application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the embodiments of the present application and the features in the embodiments may be combined with each other in the case of no conflict.

Unless otherwise defined, at least one technical and scientific term used herein has the same meaning as commonly understood by one of ordinary skill in the technical field to which this application belongs. The terms used herein in the specification of the application are for the purpose of describing specific embodiments only, and are not intended to limit the application.

Example 1

In this embodiment, the message push method can be applied to an electronic device. For an electronic device that needs to push a message, the message push function provided by the method of the present application can be directly integrated on the electronic device, or a software development Tool kit (Software Development Kit, SKD) form running in electronic equipment.

The embodiments of the present application may acquire and process related data based on artificial intelligence technology. Among them, artificial intelligence (AI) is a theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results. .

The basic technologies of artificial intelligence generally include technologies such as sensors, special artificial intelligence chips, cloud computing, distributed storage, big data processing technology, operation/interaction systems, and mechatronics. Artificial intelligence software technology mainly includes computer vision technology, robotics technology, biometrics technology, speech processing technology, natural language processing technology, machine learning, deep learning and other major directions.

As shown in FIG. 1 , the message push method, applied to the first server, specifically includes the following steps. According to different requirements, the order of the steps in the flowchart can be changed, and some of the steps can be omitted.

The message pushing method described in this application is applied to a first server, the first server is connected to a second server and a plurality of terminal devices to be pushed through communication, and the first server receives the second A message push request from the server, and according to the message push request, the message to be pushed is pushed to the plurality of terminal devices to be pushed.

S11: Receive a push message request sent by the second server.

In this embodiment, the second server may be an operation platform. When the operation platform needs to push messages, it will send a push message request to the first server. Specifically, the push message request is used to request all The first server performs message push in response to a push message request sent by the second server, wherein the first server may be a third-party push platform, and the third-party push platform receives the message sent by the operation platform. A push message request, wherein the push message request includes a message body of a message to be pushed, a push message rule, and the like.

S12: Parse the push message request to obtain the message body of the message to be pushed and the device identifier of the second server.

In this embodiment, when the first server receives the push message request sent by the second server, the first server obtains the device identifier of the second server, and sends the second server The device identification of the terminal is associated with the push message request, and the message body of the message to be pushed and the device identification of the second server are obtained by parsing the push message request.

S13: Obtain the message type and at least one push address value of the message to be pushed according to the message body of the message to be pushed.

In this embodiment, the message body contains the basic content of the message. Specifically, the basic content of the message includes, but is not limited to, the name of the sent message, the message type, the display style, the message title, and the message content.

Optionally, obtaining the message type and at least one push address value of the message to be pushed according to the message body of the message to be pushed includes:

Parse the message body of the message to be pushed to obtain an identification field and at least one push address value;

matching the identification field with a preset identification field library;

When a target identification field matching the identification field exists in the preset identification field library, the message type corresponding to the target identification field is determined as the message type of the message to be pushed.

In this embodiment, the identification field uniquely identifies the message type. After parsing the message body, the identification field and the push address value are obtained. Specifically, the push address value is associated with the device identification of the terminal device. The push address value is converted into the device ID of the terminal device.

In this embodiment, the identification field of the message type can be preset and associated with the message type. Different message types correspond to different identification fields. After the identification field is obtained, the identification field is associated with the preset identification field. The identification fields in the stored identification field library are matched, and the message type of the message to be pushed is determined according to the matching result.

Further, the method also includes:

When there is no target identification field matching the identification field in the preset identification field library, the default message type is determined as the message type of the message to be pushed.

In this embodiment, the default message type refers to a message type specially set by the second server for some specified messages. During the message push process, if it is determined that the preset identification field library does not When there is a target identification field matching the identification field, the default message type is determined as the message type of the to-be-pushed message.

In this embodiment, since different message types correspond to different push policies, the message type of the message to be pushed is obtained by parsing the push message request, which improves the diversity and accuracy of message push.

S14, when the message type of the message to be pushed is the first type of message, determine the device identification of at least one terminal device to be pushed according to the at least one push address value and the device identification of the second server.

In this embodiment, the first type of message may be an operation type message. Specifically, the operation type message does not involve user personal information and is a message based on operation settings.

Optionally, the determining the device identifier of at least one terminal device to be pushed according to the push address value and the device identifier of the second server includes:

Convert each push address value into the device identifier of the corresponding first terminal device according to the preset conversion rule;

acquiring the device identifier of at least one second terminal device associated with the second server;

matching the device identification of each first terminal device with the device identification of the at least one second terminal device;

When the device identification of each first terminal device matches the device identification of any one of the device identifications of the at least one second terminal device, the device identification of any one of the second terminal devices The ID is used as the device ID of the terminal device to be pushed.

In this embodiment, the second server stores the acquired device identifier of the second terminal device in the database in advance, converts each push address into the corresponding device identifier of the first terminal device, and associates it with the device identifier of the first terminal device respectively. The device identifier of at least one second terminal device in the databases of the two servers is matched, if the device identifier of each first terminal device matches the device identifier of any second terminal device in the database of the second server When matching, determine that the device identifier of each first terminal device is the device identifier of the terminal device to be pushed, and match at least one device identifier with any one of the second terminal devices in the database of the second server. The device identifier of the matched first terminal device is used as the device identifier of the at least one terminal device to be pushed.

Further, the method also includes:

When the device identifier of each first terminal device does not match the device identifier of any one of the device identifiers of the at least one second terminal device, the device identifier that identifies the first terminal device is The new first terminal device sends an acquisition request for acquiring the device characteristics of the new first terminal device to the second server.

In this embodiment, when the device identifier of each first terminal device does not match the device identifier of any second terminal device in the database of the second server, it is determined that the second server does not store any The second terminal device corresponding to the device identification of the first terminal device determines the device identification of the first terminal device as the new first terminal device, and sends and obtains the device characteristics of the new first terminal device to the second server, and the second server obtains the device characteristics corresponding to the new first terminal device from the new first terminal device in response to the acquisition request, and stores them in in the database.

Optionally, before determining the device identification of at least one terminal device to be pushed according to the at least one push address value and the device identification of the second server, the method further includes:

Receive multiple initialization ID acquisition interface requests for calling multiple terminal devices sent by the second server, wherein each initialization ID acquisition interface request includes the device identifier of the second server and the corresponding terminal device. equipment identification;

In response to each initialization ID acquisition interface request, sending each initialization ID to the second server, so that the second server sends each initialization ID to the corresponding target terminal device;

Receive the device feature of the target terminal device reported by the target terminal device, wherein the device feature is that the device feature collection SDK of the target terminal device is initialized by the target terminal device according to each initialization ID, and complete Collected after initialization.

In this embodiment, before determining the device identifier of at least one terminal device to be pushed according to the at least one push address value and the device identifier of the second server, the first server receives the collected data reported by the at least one terminal device. The device characteristics of the corresponding terminal equipment, before the terminal equipment collects the corresponding equipment characteristics, the second server sends a request to call the initialization ID acquisition interface of multiple terminal equipment, when the multiple terminal equipment receives the After the initialization ID sent by the second server, it is determined that the second server has the authority to initialize the device feature collection SDK.

In this embodiment, the multiple terminal devices initialize the device feature collection of the multiple terminal devices according to the initialization ID, automatically collect the device features of the corresponding terminal devices after completing the initialization, and collect the collected multiple device features. The device features of the multiple terminal devices are reported to the first server, and at the same time, the second server can acquire the device features of the multiple terminal devices.

In this embodiment, the terminal device initializes the device feature collection SDK according to the received initialization ID, realizes the initialization of the device feature collection SDK, and collects the device features of the terminal device after initialization; the first server uses The device features reported by the terminal device are received and synchronized to the second server, thereby improving the accuracy and efficiency of feature device collection.

In this embodiment, since the first server, the second server, and the terminal device are associated through initialization IDs, the device feature collection SDK collects the device features of the terminal device in a timely manner and reports them to the first service The terminal and the second server improve the timeliness of the device features of the terminal device, thereby improving the accuracy of message push.

Optionally, before receiving multiple initialization ID acquisition interface requests sent by the second server and calling multiple terminal devices, the method further includes:

acquiring multiple initialization IDs sent by the multiple terminal devices;

Receive the login information of each third terminal device obtained by the second server according to each initialization ID, and verify whether the login identity of each third terminal device is based on the login information of each third terminal device. credible;

When verifying that the login identity of each third terminal device is credible, receiving multiple initialization ID acquisition interface requests sent by the second server for calling multiple terminal devices.

In this embodiment, in order to ensure the security of data in the message push interaction process, before the second server sends a request for calling multiple initialization ID acquisition interfaces of multiple terminal devices, the login identities of the multiple terminal devices are verified. Whether it is credible or not, the second server sends a request for calling multiple initialization ID acquisition interfaces of multiple terminal devices to a terminal device with a credible login identity, which improves the security of data during the message push process.

Since the device feature collection SDK requires the terminal device to log in to send a push request, the second server sends a request for calling multiple initialization ID acquisition interfaces of multiple terminal devices to the first service according to the push request sent by the terminal device. The first server receives the collected device characteristics of the corresponding terminal device reported by at least one terminal device, and the terminal devices all make push requests spontaneously. In some other embodiments, the first server The device identification of the terminal device can be actively obtained, and then the message is pushed. Specifically, before the device identification of at least one terminal device to be pushed is determined according to the at least one push address value and the device identification of the second server, the method Also includes:

Obtain the device identifiers of multiple terminal devices and the message body of at least one message to be pushed corresponding to each terminal device from multiple preset data sources by using the web crawler technology every preset period;

Associating the device identification of each terminal device with the corresponding at least one message body to be pushed, and synchronizing the associated device identification of at least one terminal device to the second server.

In this embodiment, the device identifier of the terminal device is actively obtained, and then the message is pushed, which improves the push range of the message push, thereby improving the operation efficiency.

Optionally, the method further includes:

When the message type of the message to be pushed is the second type of message, parse the message body of the message to be pushed to obtain the target push address value, and convert the target push address value to the target terminal according to the preset conversion rule the device identification of the device;

The device identification of the target terminal device is determined as the device identification of the terminal device to be pushed.

In this embodiment, the second type of message refers to a service type message. Specifically, the service type message involves user information, and the message is pushed according to the device identifier of the terminal device used by the user.

In this embodiment, different push modes are determined according to the message types of different messages to be pushed. If it is the first type of message, it is full push, and it only needs to match at least one push address value corresponding to the push message request. The device identification of at least one terminal device can realize one-time push, avoiding the phenomenon of pulling the user messages corresponding to each terminal device one by one according to the push address, and then assembling the messages one by one and sending them in batches, which reduces the time for message push. . In addition, because it is a one-time push, users will not be missed during the interaction process, which improves the accuracy of message push.

S15: Generate a target push message according to the message body of the message to be pushed and the device identifier of at least one terminal device to be pushed, and push the target push message to the at least one terminal device to be pushed according to a preset push rule.

In this embodiment, the push message rules in the push message request are acquired, a target push message is generated according to the message body of the message to be pushed and the device identifier of at least one terminal device to be pushed, and pushed to the target push message according to the push message rules. The push page is sent to the at least one terminal device to be pushed. Specifically, the push message rule includes specific push time, push method, etc. For example, the push time can be set to the current time, or can be set to the current time A certain time after that; the push method can be set according to the content of the message, including, but not limited to: “Now” sending, no time zone selection is required; “Scheduled” sending, need to set the time zone and select the sending time; "Send" means that the message will be sent regularly every day, and you need to set the time zone, sending time, and start and end dates; "Weekly" means that the message will be sent every week, and you need to set the time zone, sending time, and start and end dates.

In this embodiment, by presetting different push rules to push messages, the diversity and effectiveness of push messages are improved.

In some other embodiments, after the target push message is pushed to the at least one terminal device to be pushed according to a preset push rule, the second server may be further configured to monitor whether the at least one device to be pushed is The target push message is read, and the push strategy of the subsequent message is determined according to the reading situation, which improves the validity and accuracy of the push message of the second server; the terminal device can also be used to receive the After the target push message pushed by the first server, the target push message is stored in the local message cache, and the target push message can be processed in the local message cache. Specifically, the processing of the target push message includes: : Acquire key fields in the target push message, identify the key fields to obtain a corresponding push template, and embed the target push message into the push template according to a preset processing method to obtain a target push message display template The final target push message is obtained, and the final target push message is sent to the message notification bar to facilitate the user to read the message.

In some other embodiments, due to consideration from the user's point of view, the terminal device processes the target push message in the local message cache, and the message can be read according to the user's settings on the terminal device, which improves the user's experience. Experience, and the diversity of message display.

To sum up, in the message push method described in this embodiment, the push message request sent by the second server is received; the message body of the message to be pushed and the device identifier of the second server are obtained by parsing the push message request; The message type of the message to be pushed and at least one push address value are obtained according to the message body of the message to be pushed; when the message type of the message to be pushed is the first type of message, the message type and at least one push address value of the message to be pushed are obtained according to the at least one push address value and The device identifier of the second server determines the device identifier of at least one terminal device to be pushed; a target push message is generated according to the message body of the message to be pushed and the device identifier of the at least one terminal device to be pushed, and a preset push rule is applied. Pushing the target push message to the at least one terminal device to be pushed.

In this embodiment, on the one hand, different push modes are determined according to the message types of different messages to be pushed. If it is the first type of message, it is full push, and it only needs to match at least one push address value in the push message request. The device identification of at least one corresponding terminal device can realize a one-time push, avoiding the phenomenon of pulling the user messages corresponding to each terminal device one by one according to the push address, and then assembling the messages one by one and sending them in batches, reducing the phenomenon of message push On the other hand, through one-time push, the phenomenon of missing users will not occur in the interaction process, which improves the accuracy of message push; finally, according to the first server, the second server and all After the terminal device associates the initialization ID, the device feature collection SDK can collect the device features of the terminal device in time and report it to the first server and the second server, which improves the device features of the terminal device. The timeliness, thereby improving the accuracy of message push.

Embodiment 2

In some embodiments, the message pushing apparatus 20 may include a plurality of functional modules composed of program code segments. The program codes of each program segment in the message pushing apparatus 20 may be stored in the memory of the electronic device and executed by the at least one processor to perform the function of message pushing (see description in FIG. 1 for details).

In this embodiment, the message pushing apparatus 20 may be divided into a plurality of functional modules according to the functions performed by the message pushing apparatus 20 . The functional modules may include: a receiving module 201 , a parsing module 202 , an obtaining module 203 , a determining module 204 , an obtaining module 205 , a synchronization module 206 and a pushing module 207 . A module referred to in this application refers to a series of computer-readable instruction segments that can be executed by at least one processor and can perform fixed functions, and are stored in a memory. In this embodiment, the functions of each module will be described in detail in subsequent embodiments.

The message pushing device described in this application runs on a first server, the first server is connected to the second server and a plurality of terminal devices to be pushed through communication, and the first server receives the second A message push request from the server, and according to the message push request, the message to be pushed is pushed to the plurality of terminal devices to be pushed.

The receiving module 201 is configured to receive a push message request sent by a second server.

The parsing module 202 is configured to parse the push message request to obtain the message body of the message to be pushed and the device identifier of the second server.

The obtaining module 203 is configured to obtain the message type and at least one push address value of the message to be pushed according to the message body of the message to be pushed.

Optionally, the obtaining module 203 obtains the message type and at least one push address value of the message to be pushed according to the message body of the message to be pushed, including:

matching the identification field with a preset identification field library;

Further, the determining module 204 is configured to determine the default message type as the message type of the message to be pushed when there is no target identification field matching the identification field in the preset identification field library.

The determining module 204 is further configured to determine, according to the at least one push address value and the device identifier of the second server, the message type of the at least one terminal device to be pushed when the message type of the message to be pushed is the first type of message. Equipment Identity.

Optionally, the determining module 204 determines the device identifier of at least one terminal device to be pushed according to the push address value and the device identifier of the second server, including:

Further, when the device identification of each first terminal device does not match the device identification of any second terminal device among the device identifications of the at least one second terminal device, identify the first terminal device. The device is identified as a new first terminal device, and an acquisition request for acquiring the device characteristics of the new first terminal device is sent to the second server.

Optionally, before the determining module 204 determines the device identification of at least one terminal device to be pushed according to the at least one push address value and the device identification of the second server, receive the calling number sent by the second server. Multiple initialization ID acquisition interface requests for each terminal device, wherein each initialization ID acquisition interface request includes the device identification of the second server and the device identification of the corresponding terminal device; in response to each initialization ID acquisition interface request, sending each initialization ID to the second server, so that the second server sends each initialization ID to the corresponding target terminal device; receiving the report from the target terminal device The device feature of the target terminal device, wherein the device feature is obtained by the target terminal device initializing the device feature collection SDK of the target terminal device according to each initialization ID, and collecting after completing the initialization.

Optionally, before the determining module 204 receives multiple initialization ID acquisition interface requests sent by the second server to call multiple terminal devices, the obtaining module 205 is configured to obtain the multiple terminal devices sent by the multiple terminal devices. an initialization ID;

The receiving module 201 is further configured to receive the login information of each third terminal device obtained by the second server according to each initialization ID, and verify the login information of each third terminal device according to the login information of each third terminal device. Whether the login identity of the third terminal device is credible;

The receiving module 201 is further configured to receive, when verifying that the login identity of each third terminal device is credible, receive multiple initialization ID acquisition interface requests sent by the second server for calling multiple terminal devices.

Since the device feature collection SDK requires the terminal device to log in to send a push request, the second server sends a request for calling multiple initialization ID acquisition interfaces of multiple terminal devices to the first service according to the push request sent by the terminal device. The first server receives the collected device characteristics of the corresponding terminal device reported by at least one terminal device, and the terminal devices all make push requests spontaneously. In some other embodiments, the first server The device identification of the terminal device may be actively acquired, and then the message is pushed, specifically, before the device identification of at least one terminal device to be pushed is determined according to the at least one push address value and the device identification of the second server.

The obtaining module 205 is configured to obtain the device identifiers of multiple terminal devices and the message body of at least one message to be pushed corresponding to each terminal device from multiple preset data sources by using the web crawler technology every preset period.

The synchronization module 206 is configured to associate the device identification of each terminal device with the corresponding at least one message body to be pushed, and synchronize the associated device identification of the at least one terminal device to the second server.

Optionally, when the message type of the message to be pushed is the second type of message, parse the message body of the message to be pushed to obtain the target push address value, and convert the target push address according to the preset conversion rule. The value is converted to the device identification of the target terminal device; the device identification of the target terminal device is determined as the device identification of the terminal device to be pushed.

The push module 207 is configured to generate a target push message according to the message body of the message to be pushed and the device identifier of at least one terminal device to be pushed, and push the target push message to the at least one to-be-pushed message according to a preset push rule. Push terminal equipment.

In this embodiment, the push message rules in the push message request are acquired, a target push message is generated according to the message body of the message to be pushed and the device identifier of at least one terminal device to be pushed, and pushed to the target push message according to the push message rules. The push page to the at least one terminal device to be pushed, specifically, the push message rule includes a specific push time, push method, etc. For example, the push time can be set to the current time, or can be set to the current time A certain time after that; the push method can be set according to the content of the message, including, but not limited to: “Now” sending, no time zone selection is required; “Scheduled” sending, need to set the time zone and select the sending time; "Send" means that the message will be sent regularly every day, and you need to set the time zone, sending time, and start and end dates; "Weekly" means that the message will be sent every week, and you need to set the time zone, sending time, and start and end dates.

To sum up, the message pushing device of this embodiment receives the push message request sent by the second server; and parses the push message request to obtain the message body of the message to be pushed and the device identifier of the second server; The message type of the message to be pushed and at least one push address value are obtained according to the message body of the message to be pushed; when the message type of the message to be pushed is the first type of message, the message type and at least one push address value of the message to be pushed are obtained according to the at least one push address value and The device identifier of the second server determines the device identifier of at least one terminal device to be pushed; a target push message is generated according to the message body of the message to be pushed and the device identifier of the at least one terminal device to be pushed, and a preset push rule is used. Pushing the target push message to the at least one terminal device to be pushed.

In this embodiment, on the one hand, different push methods are determined according to the message types of different messages to be pushed. If it is the first type of message, it is full push, and it only needs to match at least one push address value in the push message request. The device identification of at least one corresponding terminal device can realize a one-time push, avoiding the phenomenon of pulling the user messages corresponding to each terminal device one by one according to the push address, and then assembling the messages one by one and sending them in batches, reducing the phenomenon of message push On the other hand, through one-time push, the phenomenon of missing users will not occur in the interaction process, which improves the accuracy of message push; finally, according to the first server, the second server and all After the terminal device associates the initialization ID, the device feature collection SDK can collect the device features of the terminal device in time and report it to the first server and the second server, which improves the device features of the terminal device. The timeliness, thereby improving the accuracy of message push.

Embodiment 3

Referring to FIG. 3 , it is a schematic structural diagram of an electronic device according to Embodiment 3 of the present application. In a preferred embodiment of the present application, the electronic device 3 includes a memory 31 , at least one processor 32 , at least one communication bus 33 and a transceiver 34 .

Those skilled in the art should understand that the structure of the electronic device shown in FIG. 3 does not constitute a limitation of the embodiments of the present application, and may be a bus-type structure or a star-shaped structure, and the electronic device 3 may also include a schematic more or less other hardware or software, or a different arrangement of components is shown.

In some embodiments, the electronic device 3 is an electronic device that can automatically perform numerical calculation and/or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application-specific integrated circuits , programmable gate arrays, digital processors and embedded devices. The electronic device 3 may also include a client device, which includes but is not limited to any electronic product that can perform human-computer interaction with a client through a keyboard, a mouse, a remote control, a touchpad, or a voice-activated device, for example, Personal computers, tablets, smartphones, digital cameras, etc.

It should be noted that the electronic device 3 is only an example, and other existing or future electronic products, if applicable to the present application, should also be included within the protection scope of the present application, and incorporated herein by reference .

In some embodiments, the memory 31 is used to store program codes and various data, such as the message push device 20 installed in the electronic device 3 , and realize high-speed and automatic completion during the operation of the electronic device 3 access to programs or data. Described memory 31 comprises read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM) , One-time Programmable Read-Only Memory (OTPROM), Electronically-Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read- Only Memory, CD-ROM) or other optical disk storage, magnetic disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.

In some embodiments, the at least one processor 32 may be composed of integrated circuits, for example, may be composed of a single packaged integrated circuit, or may be composed of multiple integrated circuits packaged with the same function or different functions, including one Or a combination of multiple central processing units (Central Processing units, CPUs), microprocessors, digital processing chips, graphics processors, and various control chips. The at least one processor 32 is the control core (Control Unit) of the electronic device 3, and uses various interfaces and lines to connect various components of the entire electronic device 3, by running or executing the program stored in the memory 31 or modules, and call data stored in the memory 31 to perform various functions of the electronic device 3 and process data.

In some embodiments, the at least one communication bus 33 is arranged to enable connection communication between the memory 31 and the at least one processor 32 and the like.

Although not shown, the electronic device 3 may also include a power source (such as a battery) for supplying power to various components. Optionally, the power source may be logically connected to the at least one processor 32 through a power management device, so that the power management device Implement functions such as managing charging, discharging, and power consumption. The power source may also include one or more DC or AC power sources, recharging devices, power failure detection circuits, power converters or inverters, power status indicators, and any other components. The electronic device 3 may further include a variety of sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.

It should be understood that the embodiments are only used for illustration, and are not limited by this structure in the scope of the patent application.

The above-mentioned integrated units implemented in the form of software functional modules may be stored in a computer-readable storage medium. The above-mentioned software function modules are stored in a storage medium, and include several instructions to make a computer device (which may be a personal computer, an electronic device, or a network device, etc.) or a processor (processor) to execute the methods described in the various embodiments of the present application. part.

In a further embodiment, with reference to FIG. 2 , the at least one processor 32 can execute the operating device of the electronic device 3 and various installed applications (such as the message pushing device 20 ), program codes, etc., For example, the various modules mentioned above.

Program codes are stored in the memory 31, and the at least one processor 32 can call the program codes stored in the memory 31 to perform related functions. For example, each module described in FIG. 2 is a program code stored in the memory 31 and executed by the at least one processor 32, so as to realize the functions of the various modules to achieve the purpose of message push.

In an embodiment of the present application, the memory 31 stores a plurality of computer-readable instructions, and the plurality of computer-readable instructions are executed by the at least one processor 32 to implement the function of message push.

Exemplarily, the computer program may be divided into one or more modules/units, and the one or more modules/units are stored in the memory 31 and executed by the processor 32 to complete the present invention. Apply. The one or more modules/units may be a series of computer-readable instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device 3 . For example, the computer program can be divided into a receiving module 201 , a parsing module 202 , an obtaining module 203 , a determining module 204 , an obtaining module 205 , a synchronization module 206 and a pushing module 207 .

Specifically, for the specific implementation method of the above instruction by the at least one processor 32, reference may be made to the description of the relevant steps in the embodiment corresponding to FIG. 1 , and details are not described herein.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the modules is only a logical function division, and there may be other division manners in actual implementation.

Further, the computer-readable storage medium mainly includes a storage program area and a storage data area, wherein the storage program area can store an operating system, an application program required by at least one function, and the like; using the created data, etc.

The computer-readable storage medium may be a volatile storage medium or a non-volatile storage medium.

The blockchain referred to in this application is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain, essentially a decentralized database, is a series of data blocks associated with cryptographic methods. Each data block contains a batch of network transaction information to verify its Validity of information (anti-counterfeiting) and generation of the next block. The blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.

The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, and may be located in one place or distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional module in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware, or can be implemented in the form of hardware plus software function modules.

It will be apparent to those skilled in the art that the present application is not limited to the details of the above-described exemplary embodiments, but that the present application can be implemented in other specific forms without departing from the spirit or essential characteristics of the present application. Accordingly, the embodiments are to be regarded in all respects as illustrative and not restrictive, and the scope of the application is to be defined by the appended claims rather than the foregoing description, which is therefore intended to fall within the scope of the claims. At least one variation within the meaning and range of the equivalents of , is intended to be embraced within this application. Any reference signs in the claims shall not be construed as limiting the involved claim. Furthermore, it is clear that the word "comprising" does not exclude other units or, and the singular does not exclude the plural. A plurality of units or devices stated in this application may also be implemented by one unit or device through software or hardware. The terms first, second, etc. are used to denote names and do not denote any particular order.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application rather than limitations. Although the present application has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present application can be Modifications or equivalent substitutions can be made without departing from the spirit and scope of the technical solutions of the present application.

Claims

A message push method, wherein the message push method includes:

receiving a push message request sent by the second server;

Parsing the push message request to obtain the message body of the message to be pushed and the device identifier of the second server;

Obtain the message type and at least one push address value of the message to be pushed according to the message body of the message to be pushed;

When the message type of the message to be pushed is the first type of message, determine the device identification of at least one terminal device to be pushed according to the at least one push address value and the device identification of the second server;

A target push message is generated according to the message body of the message to be pushed and the device identifier of at least one terminal device to be pushed, and the target push message is pushed to the at least one terminal device to be pushed according to a preset push rule.
The message pushing method according to claim 1, wherein the determining the device identification of at least one terminal device to be pushed according to the push address value and the device identification of the second server comprises:

Convert each push address value into the device identifier of the corresponding first terminal device according to the preset conversion rule;

acquiring the device identifier of at least one second terminal device associated with the second server;

matching the device identification of each first terminal device with the device identification of the at least one second terminal device;

When the device identification of each first terminal device matches the device identification of any one of the device identifications of the at least one second terminal device, the device identification of any one of the second terminal devices The ID is used as the device ID of the terminal device to be pushed.
The message pushing method according to claim 2, wherein the method further comprises:

When the device identifier of each first terminal device does not match the device identifier of any one of the device identifiers of the at least one second terminal device, the device identifier that identifies the first terminal device is The new first terminal device sends an acquisition request for acquiring the device characteristics of the new first terminal device to the second server.
The message push method according to claim 1, wherein the obtaining the message type and at least one push address value of the to-be-pushed message according to the message body of the to-be-pushed message comprises:

Parse the message body of the message to be pushed to obtain an identification field and at least one push address value;

matching the identification field with a preset identification field library;

When there is a target identification field matching the identification field in the preset identification field library, determine the message type corresponding to the target identification field as the message type of the message to be pushed; or

When there is no target identification field matching the identification field in the preset identification field library, the default message type is determined as the message type of the message to be pushed.
The message pushing method according to claim 1, wherein before determining the device identification of at least one terminal device to be pushed according to the at least one push address value and the device identification of the second server, the method further comprises: :

Receive multiple initialization ID acquisition interface requests for calling multiple terminal devices sent by the second server, wherein each of the initialization ID acquisition interface requests includes the device identifier of the second server and the corresponding terminal device. equipment identification;

In response to each initialization ID acquisition interface request, sending each initialization ID to the second server, so that the second server sends each initialization ID to the corresponding target terminal device;

Receive the device feature of the target terminal device reported by the target terminal device, wherein the device feature is that the device feature collection SDK of the target terminal device is initialized by the target terminal device according to each initialization ID, and complete Collected after initialization.
The method for pushing a message according to claim 5, wherein before receiving a request sent by the second server for calling multiple initialization ID acquisition interfaces of multiple terminal devices, the method further comprises:

acquiring multiple initialization IDs sent by the multiple terminal devices;

Receive the login information of each third terminal device obtained by the second server according to each initialization ID, and verify whether the login identity of each third terminal device is based on the login information of each third terminal device. credible;

When verifying that the login identity of each third terminal device is credible, receiving multiple initialization ID acquisition interface requests sent by the second server for calling multiple terminal devices.
The message pushing method according to any one of claims 1 to 6, wherein the method further comprises:

When the message type of the message to be pushed is the second type of message, parse the message body of the message to be pushed to obtain the target push address value, and convert the target push address value to the target terminal according to the preset conversion rule the device identification of the device;

The device identification of the target terminal device is determined as the device identification of the terminal device to be pushed.
An electronic device, wherein the electronic device comprises a memory and a processor, the memory is used to store at least one computer-readable instruction, and the processor is used to execute the at least one computer-readable instruction to implement the following steps:

receiving a push message request sent by the second server;

Parsing the push message request to obtain the message body of the message to be pushed and the device identifier of the second server;

Obtain the message type and at least one push address value of the message to be pushed according to the message body of the message to be pushed;

When the message type of the message to be pushed is the first type of message, determine the device identification of at least one terminal device to be pushed according to the at least one push address value and the device identification of the second server;

A target push message is generated according to the message body of the message to be pushed and the device identifier of at least one terminal device to be pushed, and the target push message is pushed to the at least one terminal device to be pushed according to a preset push rule.
The electronic device according to claim 8, wherein the processor executes the at least one computer-readable instruction to implement the determining of at least one terminal to be pushed according to the push address value and the device identification of the second server When specifying the device identification of the device, it specifically includes:

Convert each push address value into the device identifier of the corresponding first terminal device according to the preset conversion rule;

acquiring the device identifier of at least one second terminal device associated with the second server;

matching the device identification of each first terminal device with the device identification of the at least one second terminal device;

When the device identification of each first terminal device matches the device identification of any one of the device identifications of the at least one second terminal device, the device identification of any one of the second terminal devices The ID is used as the device ID of the terminal device to be pushed.
The electronic device of claim 9, wherein the processor executes the at least one computer-readable instruction to further implement the following steps:

When the device identifier of each first terminal device does not match the device identifier of any one of the device identifiers of the at least one second terminal device, the device identifier that identifies the first terminal device is The new first terminal device sends an acquisition request for acquiring the device characteristics of the new first terminal device to the second server.
The electronic device according to claim 8, wherein the processor executes the at least one computer-readable instruction to implement the obtaining of the message type and at least one of the message to be pushed according to the message body of the message to be pushed When pushing the address value, it includes:

Parse the message body of the message to be pushed to obtain an identification field and at least one push address value;

matching the identification field with a preset identification field library;

When there is a target identification field matching the identification field in the preset identification field library, determine the message type corresponding to the target identification field as the message type of the message to be pushed; or

When there is no target identification field matching the identification field in the preset identification field library, the default message type is determined as the message type of the message to be pushed.
The electronic device according to claim 8, wherein before the device identification of the at least one terminal device to be pushed is determined according to the at least one push address value and the device identification of the second server, the processor executes the The at least one computer-readable instruction is also used to implement the following steps:

Receive multiple initialization ID acquisition interface requests for calling multiple terminal devices sent by the second server, wherein each of the initialization ID acquisition interface requests includes the device identifier of the second server and the corresponding terminal device. equipment identification;

In response to each initialization ID acquisition interface request, sending each initialization ID to the second server, so that the second server sends each initialization ID to the corresponding target terminal device;

Receive the device feature of the target terminal device reported by the target terminal device, wherein the device feature is that the device feature collection SDK of the target terminal device is initialized by the target terminal device according to each initialization ID, and complete Collected after initialization.
The electronic device according to claim 12, wherein the processor executes the at least one computer-readable instruction before receiving multiple initialization ID acquisition interface requests sent by the second server to invoke multiple terminal devices Also used to implement the following steps:

acquiring multiple initialization IDs sent by the multiple terminal devices;

Receive the login information of each third terminal device obtained by the second server according to each initialization ID, and verify whether the login identity of each third terminal device is based on the login information of each third terminal device. credible;

When it is verified that the login identity of each third terminal device is credible, multiple initialization ID acquisition interface requests for calling multiple terminal devices sent by the second server are received.
A computer-readable storage medium, wherein the computer-readable storage medium stores at least one computer-readable instruction, and the at least one computer-readable instruction implements the following steps when executed by a processor:

receiving a push message request sent by the second server;

Parsing the push message request to obtain the message body of the message to be pushed and the device identifier of the second server;

Obtain the message type and at least one push address value of the message to be pushed according to the message body of the message to be pushed;

When the message type of the message to be pushed is the first type of message, determine the device identification of at least one terminal device to be pushed according to the at least one push address value and the device identification of the second server;

A target push message is generated according to the message body of the message to be pushed and the device identifier of at least one terminal device to be pushed, and the target push message is pushed to the at least one terminal device to be pushed according to a preset push rule.
The storage medium of claim 14, wherein the at least one computer-readable instruction is executed by the processor to implement the determining of the at least one to-be-pushed item according to the push address value and the device identification of the second server When the device identification of the terminal device is used, it specifically includes:

Convert each push address value into the device identifier of the corresponding first terminal device according to the preset conversion rule;

acquiring the device identifier of at least one second terminal device associated with the second server;

matching the device identification of each first terminal device with the device identification of the at least one second terminal device;

When the device identification of each first terminal device matches the device identification of any one of the device identifications of the at least one second terminal device, the device identification of any one of the second terminal devices The ID is used as the device ID of the terminal device to be pushed.
The storage medium of claim 15, wherein the at least one computer-readable instruction, when executed by the processor, is further configured to implement the following steps:

When the device identifier of each first terminal device does not match the device identifier of any one of the device identifiers of the at least one second terminal device, the device identifier that identifies the first terminal device is The new first terminal device sends an acquisition request for acquiring the device characteristics of the new first terminal device to the second server.
The storage medium of claim 14, wherein the at least one computer-readable instruction is executed by the processor to implement the obtaining of the message type and at least the message body of the message to be pushed according to the message body of the message to be pushed When a push address value, it specifically includes:

Parse the message body of the message to be pushed to obtain an identification field and at least one push address value;

matching the identification field with a preset identification field library;

When there is a target identification field matching the identification field in the preset identification field library, determine the message type corresponding to the target identification field as the message type of the message to be pushed; or

When there is no target identification field matching the identification field in the preset identification field library, the default message type is determined as the message type of the message to be pushed.
The storage medium according to claim 14, wherein before the device identification of the at least one terminal device to be pushed is determined according to the at least one push address value and the device identification of the second server, the at least one computer can The read instruction is also used to implement the following steps when executed by the processor:

Receive multiple initialization ID acquisition interface requests for calling multiple terminal devices sent by the second server, wherein each of the initialization ID acquisition interface requests includes the device identifier of the second server and the corresponding terminal device. equipment identification;

In response to each initialization ID acquisition interface request, sending each initialization ID to the second server, so that the second server sends each initialization ID to the corresponding target terminal device;

Receive the device feature of the target terminal device reported by the target terminal device, wherein the device feature is that the device feature collection SDK of the target terminal device is initialized by the target terminal device according to each initialization ID, and complete Collected after initialization.
The storage medium of claim 18, wherein the at least one computer-readable instruction is executed by the processor before receiving multiple initialization ID acquisition interface requests sent by the second server to invoke multiple terminal devices Also used to implement the following steps:

acquiring multiple initialization IDs sent by the multiple terminal devices;

Receive the login information of each third terminal device obtained by the second server according to each initialization ID, and verify whether the login identity of each third terminal device is based on the login information of each third terminal device. credible;

When it is verified that the login identity of each third terminal device is credible, multiple initialization ID acquisition interface requests for calling multiple terminal devices sent by the second server are received.
A message pushing device, running on a first server, wherein the message pushing device includes:

a receiving module, configured to receive a push message request sent by the second server;

a parsing module, configured to parse the push message request to obtain the message body of the message to be pushed and the device identifier of the second server;

an obtaining module, configured to obtain the message type and at least one push address value of the message to be pushed according to the message body of the message to be pushed;

a determining module, configured to determine the device identification of at least one terminal device to be pushed according to the at least one push address value and the device identification of the second server when the message type of the message to be pushed is the first type of message;

a push module, configured to generate a target push message according to the message body of the message to be pushed and the device identifier of at least one terminal device to be pushed, and push the target push message to the at least one to be pushed message according to a preset push rule Terminal Equipment.