CN112367246B - Message pushing method and device, electronic equipment and storage medium - Google Patents
Message pushing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112367246B CN112367246B CN202011198143.XA CN202011198143A CN112367246B CN 112367246 B CN112367246 B CN 112367246B CN 202011198143 A CN202011198143 A CN 202011198143A CN 112367246 B CN112367246 B CN 112367246B
- Authority
- CN
- China
- Prior art keywords
- message
- pushed
- identifier
- terminal device
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Abstract
The invention relates to the technical field of big data, and provides a message pushing method, a message pushing device, electronic equipment and a storage medium, wherein the method comprises the following steps: analyzing the push message request to obtain a message body of the message to be pushed and the equipment identifier of the second server; 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; when the message type of the message to be pushed is a first type message, determining the equipment identifier of at least one terminal equipment to be pushed according to at least one pushing address value and the equipment identifier of the second server; and generating a target push message according to the message body of the message to be pushed and the equipment identification of the at least one terminal equipment to be pushed and pushing the target push message to the at least one terminal equipment to be pushed. According to the method and the device, different pushing modes are determined according to different message types of the messages to be pushed, one-time pushing is achieved, the phenomenon that users are missed in the interaction process is avoided, and the message pushing accuracy is improved.
Description
Technical Field
The invention relates to the technical field of big data, in particular to a message pushing method and device, electronic equipment and a storage medium.
Background
The message pushing is one of important channels for third-party application program operation, user attention is obtained by pushing messages, the existing message pushing scheme is simple, information of all users needs to be obtained when the message pushing is carried out, then the message assembly is carried out one by one, and the message pushing is sent in batches.
Disclosure of Invention
In view of the above, it is necessary to provide a message pushing method, a message pushing device, an electronic device, and a storage medium, in which different pushing manners are determined according to different message types of messages to be pushed, so as to implement one-time pushing, avoid a phenomenon of missing users in an interaction process, and improve accuracy of message pushing.
A first aspect of the present invention provides a message pushing method, applied to a first service end, where the method includes:
receiving a push message request sent by a second server;
analyzing the push message request to obtain a message body of the message to be pushed and the equipment identifier of the second server;
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;
when the message type of the message to be pushed is a first type message, determining the equipment identifier of at least one terminal equipment to be pushed according to the at least one pushing address value and the equipment identifier of the second server;
and generating a target push message according to the message body of the message to be pushed and the equipment identifier of at least one terminal equipment to be pushed, and pushing the target push message to the at least one terminal equipment to be pushed according to a preset push rule.
Optionally, the determining, according to the push address value and the device identifier of the second server, the device identifier of at least one terminal device to be pushed includes:
converting each push address value into a corresponding device identifier of the first terminal device according to a preset conversion rule;
acquiring a device identifier of at least one second terminal device associated with the second server;
matching the equipment identifier of each first terminal equipment with the equipment identifier of the at least one second terminal equipment;
and when the equipment identifier of each first terminal equipment is matched with the equipment identifier of any one second terminal equipment in the equipment identifiers of the at least one second terminal equipment, taking the equipment identifier of the any one second terminal equipment as the equipment identifier of the terminal equipment to be pushed.
Optionally, the method further includes:
and when the equipment identifier of each first terminal equipment is not matched with the equipment identifier of any one of the at least one second terminal equipment, identifying the equipment identifier of the first terminal equipment as new first terminal equipment, and sending an acquisition request for acquiring the equipment characteristics of the new first terminal equipment to the second server.
Optionally, the obtaining the message type of the message to be pushed and the at least one push address value according to the message body of the message to be pushed includes:
analyzing a message body of the message to be pushed to obtain an identification field and at least one pushing address value;
matching the identification field with a preset identification field library;
when a target identification field matched with the identification field exists in the preset identification field library, determining the message type corresponding to the target identification field as the message type of the message to be pushed; or
And when the target identification field matched with the identification field does not exist in the preset identification field library, determining the default message type as the message type of the message to be pushed.
Optionally, before determining the device identifier of the at least one terminal device to be pushed according to the at least one pushed address value and the device identifier of the second server, the method further includes:
receiving a plurality of initialization ID acquisition interface requests for calling a plurality of terminal devices, which are sent by the second server, wherein each initialization ID acquisition interface request comprises a device identifier of the second server and a device identifier of a corresponding terminal device;
responding to each initialization ID acquisition interface request, and sending each initialization ID to the second server, so that the second server sends each initialization ID to corresponding target terminal equipment;
and receiving the device characteristics of the target terminal device reported by the target terminal device, wherein the device characteristics are obtained by initializing the device characteristic collection SDK of the target terminal device by the target terminal device according to each initialization ID and collecting the initialized device characteristics.
Optionally, before receiving a plurality of initialization ID obtaining interface requests for invoking a plurality of terminal devices, which are sent by the second server, the method further includes:
acquiring a plurality of initialization IDs sent by the plurality of terminal devices;
receiving login information of each third terminal device, which is acquired by the second server according to each initialization ID, and verifying whether the login identity of each third terminal device is credible according to the login information of each third terminal device;
and when the login identity of each third terminal device is verified to be credible, receiving a plurality of initialization ID acquisition interface requests for calling a plurality of terminal devices, which are sent by the second server.
Optionally, the method further includes:
when the message type of the message to be pushed is a second type message, analyzing a message body of the message to be pushed to obtain a target push address value, and converting the target push address value into a device identifier of a target terminal device according to the preset conversion rule;
and determining the equipment identifier of the target terminal equipment as the equipment identifier of the terminal equipment to be pushed.
A second aspect of the present invention provides a message pushing apparatus, applied to a first service end, the apparatus including:
the receiving module is used for receiving a push message request sent by a second server;
the analysis module is used for analyzing the push message request to obtain a message body of the message to be pushed and the equipment identifier of the second server;
the obtaining module is used for 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;
a determining module, configured to determine, when the message type of the message to be pushed is a first type message, a 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;
and the pushing module is used for generating a target pushing message according to the message body of the message to be pushed and the device identifications of all the at least one terminal device to be pushed, and pushing the target pushing message to the at least one terminal device to be pushed according to a preset pushing rule.
A third aspect of the present invention provides an electronic device comprising a processor and a memory, wherein the processor is configured to implement the message pushing method when executing a computer program stored in the memory.
A fourth aspect of the present invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the message push method.
In summary, according to the message pushing method, the message pushing device, the electronic device and the storage medium of the present invention, on one hand, different pushing manners are determined according to different message types of messages to be pushed, and if the message is a first type message, the message is pushed in full, and only the device identifier of at least one terminal device corresponding to at least one pushing address value in the message pushing request needs to be matched, so that one-time pushing can be realized, the phenomenon that the user message corresponding to each terminal device is pulled one by one according to the pushing address, and then the message assembly and batch sending are performed one by one is avoided, and the message pushing time is reduced; on the other hand, through one-time pushing, the phenomenon of user omission does not occur in the interaction process, and the accuracy of message pushing is improved; finally, after the initialization IDs are associated with the first server, the second server and the terminal device, the device feature collection SDK can collect the device features of the terminal device in time and report the device features to the first server and the second server, so that the timeliness of the device features of the terminal device is improved, and the accuracy of message pushing is improved.
Drawings
Fig. 1 is a flowchart of a message pushing method according to an embodiment of the present invention.
Fig. 2 is a structural diagram of a message pushing apparatus according to a second embodiment of the present invention.
Fig. 3 is a schematic structural diagram of an electronic device according to a third embodiment of the present invention.
Detailed Description
In order that the above objects, features and advantages of the present invention can be more clearly understood, a detailed description of the present invention will be given below in conjunction with the accompanying drawings and specific embodiments. It should be noted that the embodiments of the present invention and features of the embodiments may be combined with each other without conflict.
Unless defined otherwise, at least one of technical and scientific terms used herein has the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.
Example one
Fig. 1 is a flowchart of a message pushing method according to an embodiment of the present invention.
In this embodiment, the message pushing method may be applied to an electronic device, and for an electronic device that needs to perform message pushing, a message pushing function provided by the method of the present invention may be directly integrated on the electronic device, or may be run in the electronic device in the form of a Software Development Kit (SKD).
As shown in fig. 1, the message pushing method, applied to a first service end, specifically includes the following steps, and according to different requirements, the order of the steps in the flowchart may be changed, and some of the steps may be omitted.
The message pushing method is applied to a first service end, the first service end is in communication connection with a second service end and a plurality of terminal devices to be pushed, the first service end receives a message pushing request of the second service end, and the message to be pushed is pushed to the plurality of terminal devices to be pushed according to the message pushing request.
S11, receiving the push message request sent by the second server.
In this embodiment, the second server may be an operation platform, and when the operation platform needs to perform message pushing, the second server may send a push message request to the first server, specifically, the push message request is used to request the first server to perform message pushing in response to the push message request sent by the second server, where the first server may be a third-party push platform, and the third-party push platform receives the push message request sent by the operation platform, where the push message request includes a message body of a message to be pushed, a push message rule, and the like.
S12, the push message request is analyzed to obtain the message body of the message to be pushed and the equipment identification of the second server.
In this embodiment, in the process that the first service side receives the push message request sent by the second service side, the first service side obtains the device identifier of the second service side, associates the device identifier of the second service side with the push message request, and obtains a message body of the message to be pushed and the device identifier of the second service side by analyzing the push message request.
S13, 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.
In this embodiment, the message body includes basic content of the message, and specifically, the basic content of the message includes, but is not limited to, a name of a sent message, a message type, a presentation style, a message title, and a message content.
Optionally, the obtaining the message type of the message to be pushed and the at least one push address value according to the message body of the message to be pushed includes:
analyzing a message body of the message to be pushed to obtain an identification field and at least one pushing address value;
matching the identification field with a preset identification field library;
and when a target identification field matched with the identification field exists in the preset identification field library, determining the message type corresponding to the target identification field as the message type of the message to be pushed.
In this embodiment, the identification field uniquely identifies the message type, and after the message body is analyzed, the identification field and the push address value are obtained, and specifically, the push address value is associated with the device identifier of the terminal device, so that the push address value can be converted into the device identifier of the terminal device.
In this embodiment, an identification field of a message type may be preset, the identification field is associated with the message type, different message types correspond to different identification fields, after the identification field is obtained, the identification field is matched with an identification field in a pre-stored identification field library, and the message type of the message to be pushed is determined according to a matching result.
Further, the method further comprises:
and when the target identification field matched with the identification field does not exist in the preset identification field library, determining the default message type as the message type of the message to be pushed.
In this embodiment, the default message type refers to a message type specifically set by the second server for some specified messages, and in a message pushing process, if it is determined that a target identification field matching the identification field does not exist in the preset identification field library, the default message type is determined as the message type of the message to be pushed.
In the embodiment, because different message types correspond to different pushing strategies, the message type of the message to be pushed is obtained by analyzing the pushing message request, and the diversity and the accuracy of message pushing are improved.
S14, when the message type of the message to be pushed is the first type message, determining the device identifier of the 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.
In this embodiment, the first type message may be an operation type message, and specifically, the operation type message does not relate to user personal information and is a message based on operation setting.
Optionally, the determining, according to the push address value and the device identifier of the second server, the device identifier of at least one terminal device to be pushed includes:
converting each push address value into a corresponding device identifier of the first terminal device according to a preset conversion rule;
acquiring a device identifier of at least one second terminal device associated with the second server;
matching the equipment identifier of each first terminal equipment with the equipment identifier of the at least one second terminal equipment;
and when the device identifier of each first terminal device is matched with the device identifier of any one of the at least one second terminal device, taking the device identifier of any one second terminal device as the device identifier of the terminal device to be pushed.
In this embodiment, the second server pre-stores the acquired device identifier of the second terminal device in a database, converts each push address into a corresponding device identifier of the first terminal device, and matches the device identifier with the device identifier of at least one second terminal device in the database of the second server, if the device identifier of each first terminal device matches the device identifier of any one second terminal device in the database of the second server, it is determined that the device identifier of each first terminal device is the device identifier of the terminal device to be pushed, and the device identifier of at least one first terminal device matching the device identifier of any one second terminal device in the database of the second server is used as the device identifier of the at least one terminal device to be pushed.
Further, the method further comprises:
and when the equipment identifier of each first terminal equipment is not matched with the equipment identifier of any one of the at least one second terminal equipment, identifying the equipment identifier of the first terminal equipment as new first terminal equipment, and sending an acquisition request for acquiring the equipment characteristics of the new first terminal equipment to the second server.
In this embodiment, when the device identifier of each first terminal device is not matched with 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 a second terminal device corresponding to the device identifier of the first terminal device, the device identifier of the first terminal device is determined 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, and the second server acquires the device characteristics corresponding to the new first terminal device from the new first terminal device in response to the acquisition request and stores the device characteristics in the database.
Optionally, before determining the device identifier of the 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 method further includes:
receiving a plurality of initialization ID acquisition interface requests for calling a plurality of terminal devices, which are sent by the second server, wherein each initialization ID acquisition interface request comprises a device identifier of the second server and a device identifier of a corresponding terminal device;
responding to each initialization ID acquisition interface request, and sending each initialization ID to the second server, so that the second server sends each initialization ID to corresponding target terminal equipment;
and receiving the device characteristics of the target terminal device reported by the target terminal device, wherein the device characteristics are obtained by initializing the device characteristic collection SDK of the target terminal device by the target terminal device according to each initialization ID and collecting the initialized device characteristics.
In this embodiment, before determining the device identifier of the 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 device characteristics of the corresponding terminal device reported by the at least one terminal device, before the terminal device collects the corresponding device characteristics, the second server sends an initialization ID acquisition interface request for calling the plurality of terminal devices, and after receiving the initialization ID sent by the second server, the second server determines that the second server has the authority for initializing device characteristic collection SDK.
In this embodiment, the plurality of terminal devices initialize the device feature collection of the plurality of terminal devices according to the initialization ID, automatically collect the device features of the corresponding terminal devices after the initialization is completed, and report the collected device features of the plurality of terminal devices to the first service end, and meanwhile, the second service end may obtain the device features of the plurality of terminal devices.
In this embodiment, the terminal device performs initialization setting on the device feature collection SDK according to the received initialization ID, so as to initialize the device feature collection SDK, and collect the device features of the terminal device after the initialization; the first server is used for receiving the device characteristics reported by the terminal device and synchronizing the device characteristics to the second server, so that the accuracy and efficiency of characteristic device collection are improved.
In this embodiment, because the first service end, the second service end, and the terminal device are associated by initializing IDs, and device characteristics collect device characteristics of the terminal device in time by the SDK and report the device characteristics to the first service end and the second service end, the timeliness of the device characteristics of the terminal device is improved, and the accuracy of message pushing is further improved.
Optionally, before receiving a plurality of initialization ID obtaining interface requests for invoking a plurality of terminal devices, which are sent by the second server, the method further includes:
acquiring a plurality of initialization IDs sent by the plurality of terminal devices;
receiving login information of each third terminal device, which is acquired by the second server according to each initialization ID, and verifying whether the login identity of each third terminal device is credible according to the login information of each third terminal device;
and when the login identity of each third terminal device is verified to be credible, receiving a plurality of initialization ID acquisition interface requests for calling a plurality of terminal devices, which are sent by the second server.
In this embodiment, in order to ensure the security of data in the message pushing interaction process, before the second server sends a request for invoking multiple initialization ID acquisition interfaces of multiple terminal devices, it is verified whether the login identities of the multiple terminal devices are trusted, and the second server sends a request for invoking multiple initialization ID acquisition interfaces of multiple terminal devices to a terminal device whose login identity is trusted, so that the security of data in the message pushing interaction process is improved.
In some other embodiments, the first server may actively obtain a device identifier of the terminal device and then push a message, specifically, 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 method further includes:
acquiring device identifications of a plurality of terminal devices and at least one message body of a message to be pushed corresponding to each terminal device from a plurality of preset data sources by using a web crawler technology at intervals of a preset period;
and associating the equipment identifier of each terminal equipment with the corresponding at least one message body to be pushed, and synchronizing the associated equipment identifier of the at least one terminal equipment to the second server.
In the embodiment, the device identifier of the terminal device is actively acquired, and then the message is pushed, so that the pushing range of the message pushing is increased, and the operation efficiency is further improved.
Optionally, the method further includes:
when the message type of the message to be pushed is a second type message, analyzing a message body of the message to be pushed to obtain a target pushing address value, and converting the target pushing address value into a device identifier of a target terminal device according to the preset conversion rule;
and determining the equipment identifier of the target terminal equipment as the equipment identifier of the terminal equipment to be pushed.
In this embodiment, the second type of message refers to a service type of message, and specifically, the service type of message relates to user information, and the message is pushed according to a device identifier of a terminal device used by the user.
In this embodiment, different push modes are determined according to different message types of messages to be pushed, if the message is a first type message, the message is pushed in full, and only the device identifier of at least one terminal device corresponding to at least one push address value in the push message request needs to be matched, so that one-time pushing can be realized, the phenomenon that user messages corresponding to each terminal device are pulled one by one according to push addresses, and then message assembly and batch sending are performed one by one is avoided, and the message pushing time is reduced. In addition, due to the fact that the message is pushed once, the phenomenon that users are missed in the interaction process is avoided, and the accuracy rate of message pushing is improved.
And S15, generating a target push message according to the message body of the message to be pushed and the device identification of the at least one terminal device to be pushed, and pushing the target push message to the at least one terminal device to be pushed according to a preset push rule.
In this embodiment, a push message rule in the push message request is obtained, a target push message is generated according to a message body of the message to be pushed and a device identifier of at least one terminal device to be pushed, and the target push message is pushed to the push page to the at least one terminal device to be pushed according to the push message rule, where the push message rule specifically includes a specific push time, a push mode, and the like, and for example, the push time may be set as a current time or a time after the current time; the push mode may be set according to the content of the message, including, but not limited to: sending "now", without time zone selection; sending in a timing mode, wherein a time zone needs to be set and sending time needs to be selected; sending every day, namely sending messages at fixed time every day, and setting time zone, sending time and start-stop date; the sending of "weekly", i.e. the messages will be sent periodically every week, the time zone, the sending time and the start and stop date need to be set.
In the embodiment, different pushing rules are preset to push the message, so that the diversity and effectiveness of the message pushing are improved.
In 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 terminal device to be pushed reads the target push message, and determine a push policy of a subsequent message according to a reading condition, so that validity and accuracy of the push message of the second server are improved; the terminal device may be further configured to store, after receiving a target push message pushed by the first server, the target push message into a local message cache, where processing of the target push message may be implemented in the local message cache, and specifically, the processing of the target push message includes: and acquiring a key field in the target push message, identifying the key field to acquire a corresponding push template, embedding the target push message into the push template according to a preset processing mode to acquire a target push message display template to acquire a final target push message, and sending the final target push message to a message notification bar to facilitate the user to read the message.
In other embodiments, due to consideration from the perspective of the user, the target push message is processed in the local message cache through the terminal device, and message reading can be performed according to the setting of the user on the terminal device, so that the experience of the user and the diversity of message display are improved.
To sum up, the message pushing method according to this embodiment receives a push message request sent by the second server; analyzing the push message request to obtain a message body of the message to be pushed and the equipment identifier of the second server; 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; when the message type of the message to be pushed is a first type message, determining the equipment identifier of at least one terminal equipment to be pushed according to the at least one pushing address value and the equipment identifier of the second server; and generating a target push message according to the message body of the message to be pushed and the equipment identifier of at least one terminal equipment to be pushed, and pushing the target push message to the at least one terminal equipment to be pushed according to a preset push rule.
In this embodiment, on one hand, different push modes are determined according to different message types of messages to be pushed, if the message is a first type message, the message is pushed in full, and only the device identifier of at least one terminal device corresponding to at least one push address value in a push message request needs to be matched, so that one-time push can be realized, the phenomenon that user messages corresponding to each terminal device are pulled one by one according to push addresses, then message assembly is performed one by one, and the messages are sent in batches is avoided, and the message push time is reduced; on the other hand, through one-time pushing, the phenomenon of user omission does not occur in the interaction process, and the accuracy of message pushing is improved; finally, after the initialization IDs are associated with the first server, the second server and the terminal device, the device feature collection SDK can collect the device features of the terminal device in time and report the device features to the first server and the second server, so that the timeliness of the device features of the terminal device is improved, and the accuracy of message pushing is improved.
Example two
Fig. 2 is a structural diagram of a message pushing apparatus according to a second embodiment of the present invention.
In some embodiments, the message pushing device 20 may include a plurality of functional modules composed of program code segments. The program codes of the various program segments 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 message pushing function (see 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. The functional module may include: the device comprises a receiving module 201, a parsing module 202, an obtaining module 203, a determining module 204, an obtaining module 205, a synchronizing module 206 and a pushing module 207. The module referred to herein is a series of computer program segments capable of being executed by at least one processor and capable of performing a fixed function and is stored in memory. In the present embodiment, the functions of the modules will be described in detail in the following embodiments.
The message pushing device operates on a first service end, the first service end is in communication connection with a second service end and a plurality of terminal devices to be pushed, the first service end receives a message pushing request of the second service end, and pushes messages to be pushed to the plurality of terminal devices to be pushed according to the message pushing request.
The receiving module 201 is configured to receive a push message request sent by a second server.
In this embodiment, the second server may be an operation platform, and when the operation platform needs to perform message pushing, the second server may send a push message request to the first server, specifically, the push message request is used to request the first server to perform message pushing in response to the push message request sent by the second server, where the first server may be a third-party push platform, and the third-party push platform receives the push message request sent by the operation platform, where the push message request includes a message body of a message to be pushed, a push message rule, and the like.
The parsing module 202 is configured to parse the push message request to obtain a message body of the message to be pushed and the device identifier of the second server.
In this embodiment, in the process that the first service side receives the push message request sent by the second service side, the first service side obtains the device identifier of the second service side, associates the device identifier of the second service side with the push message request, and obtains a message body of the message to be pushed and the device identifier of the second service side by analyzing the push message request.
An obtaining module 203, configured to obtain a message type of the message to be pushed and at least one push address value according to a message body of the message to be pushed.
In this embodiment, the message body includes basic content of the message, and specifically, the basic content of the message includes, but is not limited to, a name of a sent message, a message type, a presentation style, a message title, and a message content.
Optionally, the obtaining, by the obtaining module 203, the message type of the message to be pushed and the at least one push address value according to the message body of the message to be pushed include:
analyzing 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;
and when a target identification field matched with the identification field exists in the preset identification field library, determining the message type corresponding to the target identification field as the message type of the message to be pushed.
In this embodiment, the identification field uniquely identifies the message type, and after the message body is analyzed, the identification field and the push address value are obtained, and specifically, the push address value is associated with the device identifier of the terminal device, so that the push address value can be converted into the device identifier of the terminal device.
In this embodiment, an identification field of a message type may be preset, the identification field is associated with the message type, different message types correspond to different identification fields, after the identification field is obtained, the identification field is matched with an identification field in a pre-stored identification field library, and the message type of the message to be pushed is determined according to a matching result.
Further, the determining module 204 is configured to determine a default message type as the message type of the message to be pushed when the preset identification field library does not have a target identification field matching the identification field.
In this embodiment, the default message type refers to a message type that is specifically set by the second server for some specified messages, and in a message pushing process, if it is determined that a target identification field matching the identification field does not exist 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, because different message types correspond to different push policies, the message type of the message to be pushed is obtained by analyzing the push message request, so that diversity and accuracy of message pushing are improved.
The determining module 204 is further configured to determine, when the message type of the message to be pushed is a first type message, the device identifier of the 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.
In this embodiment, the first type message may be an operation type message, and specifically, the operation type message does not relate to user personal information and is a message based on operation setting.
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, where the determining module includes:
converting each push address value into a corresponding device identifier of the first terminal device according to a preset conversion rule;
acquiring a device identifier of at least one second terminal device associated with the second server;
matching the equipment identifier of each first terminal equipment with the equipment identifier of the at least one second terminal equipment;
and when the device identifier of each first terminal device is matched with the device identifier of any one of the at least one second terminal device, taking the device identifier of any one second terminal device as the device identifier of the terminal device to be pushed.
In this embodiment, the second server pre-stores the acquired device identifier of the second terminal device in a database, converts each push address into a corresponding device identifier of the first terminal device, and matches the device identifier with the device identifier of at least one second terminal device in the database of the second server, if the device identifier of each first terminal device matches the device identifier of any one second terminal device in the database of the second server, it is determined that the device identifier of each first terminal device is the device identifier of the terminal device to be pushed, and the device identifier of at least one first terminal device matching the device identifier of any one second terminal device in the database of the second server is used as the device identifier of the at least one terminal device to be pushed.
Further, when the device identifier of each first terminal device is not matched with the device identifier of any one of the at least one second terminal device, identifying that the device identifier of the first terminal device is a new first terminal device, and sending 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 is not matched with 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 a second terminal device corresponding to the device identifier of the first terminal device, the device identifier of the first terminal device is determined 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, and the second server acquires the device characteristics corresponding to the new first terminal device from the new first terminal device in response to the acquisition request and stores the device characteristics in the database.
Optionally, before the determining module 204 determines 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, receive multiple initialization ID acquisition interface requests for calling multiple terminal devices, where each initialization ID acquisition interface request includes the device identifier of the second server and the device identifier of a corresponding terminal device; responding to each initialization ID acquisition interface request, and sending each initialization ID to the second server, so that the second server sends each initialization ID to corresponding target terminal equipment; and receiving the device characteristics of the target terminal device reported by the target terminal device, wherein the device characteristics are obtained by initializing the device characteristic collection SDK of the target terminal device by the target terminal device according to each initialization ID and collecting the initialized device characteristics.
In this embodiment, before determining the device identifier of the 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 device features of the corresponding terminal device reported by the at least one terminal device, before the terminal device collects the corresponding device features, the second server sends an initialization ID acquisition interface request for calling the plurality of terminal devices, and after receiving the initialization ID sent by the second server, the second server determines that the second server has the right to initialize the device feature collection SDK.
In this embodiment, the plurality of terminal devices initialize the device feature collection of the plurality of terminal devices according to the initialization ID, automatically collect the device features of the corresponding terminal devices after the initialization is completed, and report the collected device features of the plurality of terminal devices to the first service end, and meanwhile, the second service end may obtain the device features of the plurality of terminal devices.
In this embodiment, the terminal device performs initialization setting on the device feature collection SDK according to the received initialization ID, so as to initialize the device feature collection SDK, and collect the device features of the terminal device after initialization; the first server is used for receiving the device characteristics reported by the terminal device and synchronizing the device characteristics to the second server, so that the accuracy and efficiency of characteristic device collection are improved.
In this embodiment, because the first service end, the second service end, and the terminal device are associated by initializing IDs, and device characteristics collect device characteristics of the terminal device in time by the SDK and report the device characteristics to the first service end and the second service end, the timeliness of the device characteristics of the terminal device is improved, and the accuracy of message pushing is further improved.
Optionally, before the determining module 204 receives a plurality of initialization ID obtaining interface requests for calling a plurality of terminal devices sent by the second server, the obtaining module 205 is configured to obtain a plurality of initialization IDs sent by the plurality of terminal devices;
the receiving module 201 is further configured to receive login information of each third terminal device, which is obtained by the second server according to each initialization ID, and verify whether the login identity of each third terminal device is trusted according to the login information of each third terminal device;
the receiving module 201 is further configured to receive, when it is verified that the login identity of each third terminal device is trusted, a plurality of initialization ID obtaining interface requests for calling a plurality of terminal devices, which are sent by the second server.
In this embodiment, in order to ensure the security of data in the message pushing interaction process, before the second server sends a request for invoking multiple initialization ID acquisition interfaces of multiple terminal devices, it is verified whether the login identities of the multiple terminal devices are trusted, and the second server sends a request for invoking multiple initialization ID acquisition interfaces of multiple terminal devices to a terminal device whose login identity is trusted, so that the security of data in the message pushing interaction process is improved.
In some other embodiments, the first server may actively obtain a device identifier of the terminal device and then push a message, specifically, 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 second server sends a push request after the terminal device logs in, the second server sends a request for calling a plurality of initialization ID acquisition interfaces of a plurality of terminal devices to the first server according to the push request sent by the terminal device, and the first server receives the collected corresponding device identifier of the terminal device reported by at least one terminal device.
The obtaining module 205 is configured to obtain, every preset period, device identifiers of a plurality of terminal devices and at least one message body of a message to be pushed corresponding to each terminal device from a plurality of preset data sources by using a web crawler technology.
A synchronization module 206, configured to associate the device identifier of each terminal device with the corresponding at least one message body to be pushed, and synchronize the device identifier of the associated at least one terminal device to the second server.
In the embodiment, the device identifier of the terminal device is actively acquired, and then the message is pushed, so that the pushing range of the message pushing is increased, and the operation efficiency is further improved.
Optionally, when the message type of the message to be pushed is a second type message, analyzing a message body of the message to be pushed to obtain a target push address value, and converting the target push address value into a device identifier of a target terminal device according to the preset conversion rule; and determining the equipment identifier of the target terminal equipment as the equipment identifier of the terminal equipment to be pushed.
In this embodiment, the second type of message refers to a service type of message, and specifically, the service type of message relates to user information, and the message is pushed according to a device identifier of a terminal device used by the user.
In this embodiment, different push modes are determined according to different message types of messages to be pushed, if the message is a first type message, the message is pushed in full, and only the device identifier of at least one terminal device corresponding to at least one push address value in the push message request needs to be matched, so that one-time pushing can be realized, the phenomenon that user messages corresponding to each terminal device are pulled one by one according to push addresses, and then message assembly and batch sending are performed one by one is avoided, and the message pushing time is reduced. In addition, due to one-time pushing, the phenomenon of user omission does not occur in the interaction process, and the accuracy of message pushing is improved.
The pushing module 207 is configured to generate a target pushing message 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 push the target pushing message to the at least one terminal device to be pushed according to a preset pushing rule.
In this embodiment, a push message rule in the push message request is obtained, a target push message is generated according to a message body of the message to be pushed and a device identifier of at least one terminal device to be pushed, and the target push message is pushed to the push page to the at least one terminal device to be pushed according to the push message rule, where the push message rule specifically includes a specific push time, a push mode, and the like, and for example, the push time may be set as a current time or a time after the current time; the push mode may be set according to the content of the message, including, but not limited to: sending "now", without time zone selection; sending in a timing mode, wherein a time zone needs to be set and sending time needs to be selected; sending every day, namely sending messages at fixed time every day, and setting time zone, sending time and start-stop date; the sending of "weekly", i.e. the messages will be sent periodically every week, the time zone, the sending time and the start and stop date need to be set.
In the embodiment, the message is pushed by presetting different pushing rules, so that the diversity and effectiveness of message pushing are improved.
In 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 terminal device to be pushed reads the target push message, and determine a push policy of a subsequent message according to a reading condition, so that validity and accuracy of a push message of the second server are improved; the terminal device may be further configured to store, after receiving a target push message pushed by the first server, the target push message into a local message cache, where processing of the target push message may be implemented in the local message cache, and specifically, the processing of the target push message includes: and acquiring a key field in the target push message, identifying the key field to acquire a corresponding push template, embedding the target push message into the push template according to a preset processing mode to acquire a target push message display template to acquire a final target push message, and sending the final target push message to a message notification bar to facilitate the user to read the message.
In other embodiments, due to consideration from the perspective of the user, the target push message is processed in the local message cache through the terminal device, and message reading can be performed according to the setting of the user on the terminal device, so that the experience of the user and the diversity of message display are improved.
To sum up, the message pushing apparatus according to this embodiment receives a push message request sent by the second server; analyzing the push message request to obtain a message body of the message to be pushed and the equipment identifier of the second server; 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; when the message type of the message to be pushed is a first type message, determining the equipment identification of at least one terminal equipment to be pushed according to the at least one pushing address value and the equipment identification of the second server; and generating a target push message according to the message body of the message to be pushed and the equipment identifier of at least one terminal equipment to be pushed, and pushing the target push message to the at least one terminal equipment to be pushed according to a preset push rule.
In this embodiment, on one hand, different push modes are determined according to different message types of messages to be pushed, if the message is a first type message, the message is pushed in full, and only the device identifier of at least one terminal device corresponding to at least one push address value in a push message request needs to be matched, so that one-time push can be realized, the phenomenon that user messages corresponding to each terminal device are pulled one by one according to push addresses, then message assembly is performed one by one, and the messages are sent in batches is avoided, and the message push time is reduced; on the other hand, through one-time pushing, the phenomenon of user omission does not occur in the interaction process, and the accuracy of message pushing is improved; finally, after the initialization IDs are associated with the first server, the second server and the terminal device, the device feature collection SDK can collect the device features of the terminal device in time and report the device features to the first server and the second server, so that the timeliness of the device features of the terminal device is improved, and the accuracy of message pushing is improved.
EXAMPLE III
Fig. 3 is a schematic structural diagram of an electronic device according to a third embodiment of the present invention. In the preferred embodiment of the present invention, the electronic device 3 comprises a memory 31, at least one processor 32, at least one communication bus 33 and a transceiver 34.
It will be appreciated by those skilled in the art that the configuration of the electronic device shown in fig. 3 does not constitute a limitation of the embodiment of the present invention, and may be a bus-type configuration or a star-type configuration, and the electronic device 3 may include more or less other hardware or software than those shown, or a different arrangement of components.
In some embodiments, the electronic device 3 is an electronic device capable of automatically performing numerical calculation and/or information processing according to instructions set or stored in advance, and the hardware thereof includes but is not limited to a microprocessor, an application specific integrated circuit, a programmable gate array, a digital processor, an embedded device, and the like. The electronic device 3 may also include a client device, which includes, but is not limited to, any electronic product that can interact with a client through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device, for example, a personal computer, a tablet computer, a smart phone, a digital camera, and the like.
It should be noted that the electronic device 3 is only an example, and other existing or future electronic products, such as those that can be adapted to the present invention, should also be included in the scope of the present invention, and are included herein by reference.
In some embodiments, the memory 31 is used for storing program codes and various data, such as the message pushing apparatus 20 installed in the electronic device 3, and realizes high-speed and automatic access to programs or data during the operation of the electronic device 3. The Memory 31 includes a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), a One-time Programmable Read-Only Memory (OTPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), an EEPROM, a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, a magnetic disk storage, a tape storage, or any other medium capable of being used to carry or store data and readable by a computer.
In some embodiments, the at least one processor 32 may be composed of an integrated circuit, for example, a single packaged integrated circuit, or may be composed of a plurality of integrated circuits packaged with the same or different functions, including one or more Central Processing Units (CPUs), microprocessors, digital Processing chips, graphics processors, and combinations of various control chips. The at least one processor 32 is a Control Unit (Control Unit) of the electronic device 3, connects various components of the whole electronic device 3 by using various interfaces and lines, and executes various functions of the electronic device 3 and processes data by running or executing programs or modules stored in the memory 31 and calling data stored in the memory 31.
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 or the like.
Although not shown, the electronic device 3 may further include a power supply (such as a battery) for supplying power to each component, and optionally, the power supply may be logically connected to the at least one processor 32 through a power management device, so as to implement functions of managing charging, discharging, and power consumption through the power management device. The power supply may also include any component of one or more dc or ac power sources, recharging devices, power failure detection circuitry, power converters or inverters, power status indicators, and the like. The electronic device 3 may further include various sensors, a bluetooth module, a Wi-Fi module, and the like, which are not described herein again.
It is to be understood that the described embodiments are for purposes of illustration only and that the scope of the appended claims is not limited to such structures.
The integrated unit implemented in the form of a software functional module may be stored in a computer-readable storage medium. The software functional module is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, an electronic device, or a network device) or a processor (processor) to execute parts of the methods according to the embodiments of the present invention.
In a further embodiment, in conjunction with fig. 2, the at least one processor 32 may execute an operating device of the electronic device 3 and various installed application programs (such as the message pushing device 20), program codes, and the like, for example, the above modules.
The memory 31 has program code stored therein, and the at least one processor 32 can call the program code stored in the memory 31 to perform related functions. For example, the modules illustrated in fig. 2 are program codes stored in the memory 31 and executed by the at least one processor 32, so as to implement the functions of the modules for the purpose of message pushing.
In one embodiment of the present invention, the memory 31 stores a plurality of instructions that are executed by the at least one processor 32 to implement the message push functionality.
Specifically, the at least one processor 32 may refer to the description of the relevant steps in the embodiment corresponding to fig. 1, and details are not repeated here.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is only one logical functional division, and other divisions may be realized in practice.
Further, the computer-readable storage medium mainly includes a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the blockchain node, and the like.
The block chain referred by the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a string of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, which is used for verifying the validity (anti-counterfeiting) of the information and generating a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional module.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and at least one variation falling within the meaning and range of equivalency of the claims is therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or that the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.
Finally, it should be noted that the above embodiments are only for illustrating the technical solutions of the present invention and not for limiting, and although the present invention is described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions may be made on the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.
Claims (9)
1. A message pushing method is applied to a first service end, and is characterized in that the method comprises the following steps:
receiving a push message request sent by a second server;
analyzing the push message request to obtain a message body of the message to be pushed and the equipment identifier of the second server;
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;
when the message type of the message to be pushed is a first type message, 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, wherein 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 comprises: converting each push address value into a corresponding device identifier of the first terminal device according to a preset conversion rule; acquiring a device identifier of at least one second terminal device associated with the second server; matching the equipment identifier of each first terminal equipment with the equipment identifier of the at least one second terminal equipment; when the device identifier of each first terminal device is matched with the device identifier of any one of the at least one second terminal device, taking the device identifier of any one second terminal device as the device identifier of the terminal device to be pushed;
and generating a target push message according to the message body of the message to be pushed and the equipment identifier of at least one terminal equipment to be pushed, and pushing the target push message to the at least one terminal equipment to be pushed according to a preset push rule.
2. The message pushing method of claim 1, wherein the method further comprises:
and when the equipment identifier of each first terminal equipment is not matched with the equipment identifier of any one of the at least one second terminal equipment, identifying that the equipment identifier of the first terminal equipment is a new first terminal equipment, and sending an acquisition request for acquiring the equipment characteristics of the new first terminal equipment to the second server.
3. The message pushing method according to claim 1, wherein the obtaining the message type and the at least one pushing address value of the message to be pushed according to the message body of the message to be pushed comprises:
analyzing a message body of the message to be pushed to obtain an identification field and at least one pushing address value;
matching the identification field with a preset identification field library;
when a target identification field matched with the identification field exists in the preset identification field library, determining the message type corresponding to the target identification field as the message type of the message to be pushed; or
And when the target identification field matched with the identification field does not exist in the preset identification field library, determining the default message type as the message type of the message to be pushed.
4. The message pushing method according to claim 1, wherein before determining the device identifier of at least one terminal device to be pushed according to the at least one pushing address value and the device identifier of the second server, the method further comprises:
receiving a plurality of initialization ID acquisition interface requests for calling a plurality of terminal devices, which are sent by the second server, wherein each initialization ID acquisition interface request comprises a device identifier of the second server and a device identifier of a corresponding terminal device;
responding to each initialization ID acquisition interface request, and sending each initialization ID to the second server, so that the second server sends each initialization ID to corresponding target terminal equipment;
and receiving the device characteristics of the target terminal device reported by the target terminal device, wherein the device characteristics are obtained by initializing the device characteristic collection SDK of the target terminal device by the target terminal device according to each initialization ID and collecting the initialized device characteristics.
5. The message pushing method of claim 4, wherein before receiving a plurality of initialization ID acquisition interface requests for invoking a plurality of terminal devices sent by the second server, the method further comprises:
acquiring a plurality of initialization IDs sent by the plurality of terminal devices;
receiving login information of each third terminal device, which is acquired by the second server according to each initialization ID, and verifying whether the login identity of each third terminal device is credible according to the login information of each third terminal device;
and when the login identity of each third terminal device is verified to be credible, receiving a plurality of initialization ID acquisition interface requests for calling a plurality of terminal devices, which are sent by the second server.
6. Message push method according to any of claims 1 to 5, characterised in that the method further comprises:
when the message type of the message to be pushed is a second type message, analyzing a message body of the message to be pushed to obtain a target pushing address value, and converting the target pushing address value into a device identifier of a target terminal device according to the preset conversion rule;
and determining the equipment identifier of the target terminal equipment as the equipment identifier of the terminal equipment to be pushed.
7. A message pushing apparatus applied to a first service end, the apparatus comprising:
the receiving module is used for receiving a push message request sent by a second server;
the analysis module is used for analyzing the push message request to obtain a message body of the message to be pushed and the equipment identifier of the second server;
the obtaining module is used for 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;
a determining module, configured to determine, when the message type of the message to be pushed is a first type message, an equipment identifier of at least one terminal device to be pushed according to the at least one push address value and the equipment identifier of the second server, where determining the equipment identifier of the at least one terminal device to be pushed according to the push address value and the equipment identifier of the second server includes: converting each push address value into a corresponding device identifier of the first terminal device according to a preset conversion rule; acquiring a device identifier of at least one second terminal device associated with the second server; matching the equipment identifier of each first terminal equipment with the equipment identifier of the at least one second terminal equipment; when the device identifier of each first terminal device is matched with the device identifier of any one of the at least one second terminal device, taking the device identifier of any one second terminal device as the device identifier of the terminal device to be pushed;
and the pushing module is used for generating a target pushing message according to the message body of the message to be pushed and the equipment identifier of the at least one terminal equipment to be pushed, and pushing the target pushing message to the at least one terminal equipment to be pushed according to a preset pushing rule.
8. An electronic device, characterized in that the electronic device comprises a processor and a memory, the processor being configured to implement the message pushing method according to any one of claims 1 to 6 when executing the computer program stored in the memory.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the message push method according to any one of claims 1 to 6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011198143.XA CN112367246B (en) | 2020-10-30 | 2020-10-30 | Message pushing method and device, electronic equipment and storage medium |
| PCT/CN2021/109393 WO2022088804A1 (en) | 2020-10-30 | 2021-07-29 | Message pushing method and apparatus, and electronic device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011198143.XA CN112367246B (en) | 2020-10-30 | 2020-10-30 | Message pushing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112367246A CN112367246A (en) | 2021-02-12 |
| CN112367246B true CN112367246B (en) | 2022-06-17 |
Family
ID=74513174
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011198143.XA Active CN112367246B (en) | 2020-10-30 | 2020-10-30 | Message pushing method and device, electronic equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112367246B (en) |
| WO (1) | WO2022088804A1 (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112367246B (en) * | 2020-10-30 | 2022-06-17 | 深圳壹账通智能科技有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN113691618B (en) * | 2021-08-23 | 2022-07-15 | 北京三快在线科技有限公司 | Message notification method, device, message center and storage medium |
| CN113873037B (en) * | 2021-09-29 | 2023-05-19 | 四川长虹网络科技有限责任公司 | Data pushing method, device, computer equipment and storage medium |
| CN114915652B (en) * | 2022-03-30 | 2024-03-15 | 北京奇艺世纪科技有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN114979308B (en) * | 2022-05-11 | 2024-04-16 | 北京沃东天骏信息技术有限公司 | Message processing method and device |
| CN115052035A (en) * | 2022-05-13 | 2022-09-13 | 北京大豪工缝智控科技有限公司 | Message pushing method, device and storage medium |
| CN114979256A (en) * | 2022-05-19 | 2022-08-30 | 北京京东乾石科技有限公司 | Message pushing method and device, electronic equipment and computer readable medium |
| CN115297162B (en) * | 2022-06-27 | 2024-03-22 | 青岛海尔科技有限公司 | Message sending method and device, storage medium and electronic device |
| CN116055551A (en) * | 2022-11-18 | 2023-05-02 | 北京奇艺世纪科技有限公司 | Information pushing method, device and system, electronic equipment and storage medium |
| CN117176793A (en) * | 2023-08-31 | 2023-12-05 | 广州市玄武无线科技股份有限公司 | Automatic forwarding method, system, device, equipment and medium for uplink message |
| CN117097793B (en) * | 2023-10-19 | 2023-12-15 | 荣耀终端有限公司 | Message pushing method, terminal and server |
| CN117560417A (en) * | 2023-11-20 | 2024-02-13 | 上海万雍科技股份有限公司 | Queue control method and device for message transmission, electronic equipment and medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101370033A (en) * | 2008-09-26 | 2009-02-18 | 成都市华为赛门铁克科技有限公司 | Method and equipment for propelling message |
| KR20160100421A (en) * | 2015-02-13 | 2016-08-24 | 주식회사 톡스 | System and method for push service combined with messaging service |
| CN106412018A (en) * | 2016-08-31 | 2017-02-15 | 百度在线网络技术（北京）有限公司 | Information pushing method and device |
| CN110149363A (en) * | 2019-04-15 | 2019-08-20 | 深圳壹账通智能科技有限公司 | A kind of information push method, device and storage medium |
| CN110365497A (en) * | 2019-05-29 | 2019-10-22 | 平安科技（深圳）有限公司 | Information push method, device, electronic equipment and storage medium |
| CN111555963A (en) * | 2020-04-30 | 2020-08-18 | 北京思特奇信息技术股份有限公司 | Message pushing method and device, electronic equipment and storage medium |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105991412B (en) * | 2015-02-12 | 2019-03-19 | 阿里巴巴集团控股有限公司 | Information push method and device |
| CN105516259B (en) * | 2015-11-27 | 2019-06-04 | 北京奇虎科技有限公司 | A kind of method for sending information and device |
| CN105577777B (en) * | 2015-12-18 | 2019-12-13 | 腾讯科技（深圳）有限公司 | message processing method, device and system |
| CN107645524B (en) * | 2016-07-21 | 2020-09-01 | 腾讯科技（深圳）有限公司 | Message pushing processing method and device |
| US10404746B1 (en) * | 2017-08-09 | 2019-09-03 | Robert B O'Dell | Rendering spoofed electronic mail harmless |
| CN110417884B (en) * | 2019-07-23 | 2021-10-08 | 腾讯科技（深圳）有限公司 | Message pushing method, device, equipment and storage medium |
| CN111416763A (en) * | 2020-02-21 | 2020-07-14 | 北京值得买科技股份有限公司 | Message pushing method |
| CN111447185B (en) * | 2020-03-10 | 2023-07-28 | 平安科技（深圳）有限公司 | Push information processing method and related equipment |
| CN112367246B (en) * | 2020-10-30 | 2022-06-17 | 深圳壹账通智能科技有限公司 | Message pushing method and device, electronic equipment and storage medium |
-
2020
- 2020-10-30 CN CN202011198143.XA patent/CN112367246B/en active Active
-
2021
- 2021-07-29 WO PCT/CN2021/109393 patent/WO2022088804A1/en unknown
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101370033A (en) * | 2008-09-26 | 2009-02-18 | 成都市华为赛门铁克科技有限公司 | Method and equipment for propelling message |
| KR20160100421A (en) * | 2015-02-13 | 2016-08-24 | 주식회사 톡스 | System and method for push service combined with messaging service |
| CN106412018A (en) * | 2016-08-31 | 2017-02-15 | 百度在线网络技术（北京）有限公司 | Information pushing method and device |
| CN110149363A (en) * | 2019-04-15 | 2019-08-20 | 深圳壹账通智能科技有限公司 | A kind of information push method, device and storage medium |
| CN110365497A (en) * | 2019-05-29 | 2019-10-22 | 平安科技（深圳）有限公司 | Information push method, device, electronic equipment and storage medium |
| CN111555963A (en) * | 2020-04-30 | 2020-08-18 | 北京思特奇信息技术股份有限公司 | Message pushing method and device, electronic equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 面向现场作业的消息推送机制研究;金风明等;《机电产品开发与创新》;20180328(第02期);22-25 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112367246A (en) | 2021-02-12 |
| WO2022088804A1 (en) | 2022-05-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112367246B (en) | Message pushing method and device, electronic equipment and storage medium | |
| CN111694840A (en) | Data synchronization method, device, server and storage medium | |
| CN112131224B (en) | Application installation package processing and installation source determining method, device and traceability system | |
| CN102054214A (en) | Laboratory equipment management system and method | |
| CN112702228B (en) | Service flow limit response method, device, electronic equipment and readable storage medium | |
| CN112615945B (en) | Domain name resolution record management method and device, computer equipment and storage medium | |
| CN112948723A (en) | Interface calling method and device and related equipment | |
| CN112017007A (en) | User behavior data processing method and device, computer equipment and storage medium | |
| CN113094674A (en) | Page display method and device, electronic equipment and storage medium | |
| CN111984601A (en) | Log file deleting method and device, electronic equipment and storage medium | |
| WO2022088803A1 (en) | System information analysis method and apparatus based on cloud environment, electronic device, and medium | |
| CN114722437A (en) | Cross-APP unique identifier generation method, device, equipment and storage medium | |
| CN112163009A (en) | User side data acquisition method and device, electronic equipment and storage medium | |
| CN112416875B (en) | Log management method, device, computer equipment and storage medium | |
| CN114691782A (en) | Database table increment synchronization method and device and storage medium | |
| CN114331661A (en) | Data verification method and device, electronic equipment and storage medium | |
| CN115102770A (en) | Resource access method, device and equipment based on user permission and storage medium | |
| CN114615325A (en) | Message pushing method and device, computer equipment and storage medium | |
| CN112711518B (en) | Log uploading method and device | |
| CN112055011A (en) | User side data acquisition method and device, electronic equipment and storage medium | |
| CN112000945B (en) | Authorization method, device, equipment and medium based on artificial intelligence | |
| CN117455613B (en) | Intelligent hotel data information management system and method | |
| CN112612451B (en) | Interface generation method, device, equipment and computer readable storage medium | |
| CN109684158A (en) | Method for monitoring state, device, equipment and the storage medium of distributed coordination system | |
| CN113438598B (en) | Terminal positioning method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40045401 Country of ref document: HK |
|
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |