CN110971690A - Push message processing method, device and equipment of IOS client - Google Patents

Push message processing method, device and equipment of IOS client Download PDF

Info

Publication number
CN110971690A
CN110971690A CN201911206059.5A CN201911206059A CN110971690A CN 110971690 A CN110971690 A CN 110971690A CN 201911206059 A CN201911206059 A CN 201911206059A CN 110971690 A CN110971690 A CN 110971690A
Authority
CN
China
Prior art keywords
ios
push message
log file
ios client
client
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.)
Granted
Application number
CN201911206059.5A
Other languages
Chinese (zh)
Other versions
CN110971690B (en
Inventor
祝威
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Advanced Nova Technology Singapore Holdings Ltd
Original Assignee
Alipay Labs Singapore Pte Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Labs Singapore Pte Ltd filed Critical Alipay Labs Singapore Pte Ltd
Priority to CN201911206059.5A priority Critical patent/CN110971690B/en
Publication of CN110971690A publication Critical patent/CN110971690A/en
Application granted granted Critical
Publication of CN110971690B publication Critical patent/CN110971690B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • 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/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5683—Storage of data provided by user terminals, i.e. reverse caching
    • 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/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The embodiment of the specification provides a push message processing method, a push message processing device and push message processing equipment for an IOS client. The method comprises the following steps: when a push message is received, reading a user identifier from a shared sandbox by using a connection between an extension component of a pre-established IOS client and the shared sandbox built by depending on the IOS client to generate a log file; and sending the log file to a server, and informing the server that the push message touches the IOS client so as to allow the server to statistically analyze the real touch condition of the push message.

Description

Push message processing method, device and equipment of IOS client
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for processing a push message of an IOS client.
Background
The push message refers to active message pushing performed by a service party on the user equipment through a product or a third-party tool of the service party, and the push reach refers to the push message reaching the user equipment or the client. Currently, the service party is generally informed of the arrival of the message pushed by the service party by the IOS server.
Therefore, there is a need to provide a more reliable solution.
Disclosure of Invention
An embodiment of the present specification provides a push message processing method for an IOS client, which is used for accurately analyzing a real reach condition of a push message.
An embodiment of the present specification further provides a method for processing a push message of an IOS client, including:
receiving a push message sent by an IOS system, wherein the push message is generated by a server corresponding to an IOS client;
reading a user identifier cached in a shared sandbox corresponding to the IOS client, wherein the shared sandbox is used for caching the user identifier of a user logging in the IOS client;
generating a first log file based on the push message and the user identifier, wherein the first log file is used for representing that the push message reaches the IOS client;
and uploading the first log file to a server so that the server can perform statistical analysis on the reaching condition of the push message.
An embodiment of the present specification further provides a method for processing a push message of an IOS client, including:
receiving a first log file sent by a first IOS client, wherein the first log file is used for representing that a push message of the server touches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier for logging in the first IOS client;
determining a number of the first IOS clients based on the first log file;
determining a reach of the push message based on the number of the first IOS clients and the number of second IOS clients, the second IOS clients being IOS clients expected to reach the push message.
An embodiment of the present specification further provides a push message processing apparatus for an IOS client, including:
the system comprises a receiving module, a sending module and a sending module, wherein the receiving module is used for receiving a push message sent by an IOS system, and the push message is generated by a server corresponding to an IOS client;
the reading module is used for reading the user identification cached in the shared sandbox corresponding to the IOS client, and the shared sandbox is used for caching the user identification of the user logging in the IOS client;
the processing module generates a first log file based on the push message and the user identifier, wherein the first log file is used for representing that the push message reaches the IOS client;
and the first uploading module uploads the first log file to a server so that the server can perform statistical analysis on the reach condition of the push message.
An embodiment of the present specification further provides a push message processing apparatus for an IOS client, including:
the system comprises a receiving module, a sending module and a sending module, wherein the receiving module is used for receiving a first log file sent by a first IOS client, the first log file is used for representing that a push message of a server reaches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier for logging in the first IOS client;
a first processing module that determines a number of the first IOS clients based on the first log file;
and the second processing module is used for determining the reaching condition of the push message based on the number of the first IOS clients and the number of second IOS clients, and the second IOS clients are IOS clients expected to be reached by the push message.
An embodiment of the present specification further provides an electronic device, including:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
receiving a push message sent by an IOS system, wherein the push message is generated by a server corresponding to an IOS client;
reading a user identifier cached in a shared sandbox corresponding to the IOS client, wherein the shared sandbox is used for caching the user identifier of a user logging in the IOS client;
generating a first log file based on the push message and the user identifier, wherein the first log file is used for representing that the push message reaches the IOS client;
and uploading the first log file to a server so that the server can perform statistical analysis on the reaching condition of the push message.
Embodiments of the present specification further provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the following operations:
receiving a push message sent by an IOS system, wherein the push message is generated by a server corresponding to an IOS client;
reading a user identifier cached in a shared sandbox corresponding to the IOS client, wherein the shared sandbox is used for caching the user identifier of a user logging in the IOS client;
generating a first log file based on the push message and the user identifier, wherein the first log file is used for representing that the push message reaches the IOS client;
and uploading the first log file to a server so that the server can perform statistical analysis on the reaching condition of the push message.
An embodiment of the present specification further provides an electronic device, including:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
receiving a first log file sent by a first IOS client, wherein the first log file is used for representing that a push message of the server touches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier for logging in the first IOS client;
determining a number of the first IOS clients based on the first log file;
determining a reach of the push message based on the number of the first IOS clients and the number of second IOS clients, the second IOS clients being IOS clients expected to reach the push message.
Embodiments of the present specification further provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the following operations:
receiving a first log file sent by a first IOS client, wherein the first log file is used for representing that a push message of the server touches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier for logging in the first IOS client;
determining a number of the first IOS clients based on the first log file;
determining a reach of the push message based on the number of the first IOS clients and the number of second IOS clients, the second IOS clients being IOS clients expected to reach the push message.
One embodiment of the present specification realizes that, when receiving a push message, an IOS client reads a user identifier for logging in the IOS client from a corresponding shared sandbox, assembles the user identifier and the push message into a log file, and uploads the log file to a server to inform the server that the push message touches the IOS client, so that the server statistically analyzes a real touch condition of the push message.
Drawings
The accompanying drawings, which are included to provide a further understanding of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the description serve to explain the specification and not to limit the specification in a non-limiting sense. In the drawings:
fig. 1 is a schematic diagram of an application scenario of a push message processing method of an IOS client provided in this specification;
fig. 2 is a flowchart illustrating a push message processing method of an IOS client according to an embodiment of the present specification;
fig. 3 is a schematic diagram of a push right registration process provided in an embodiment of the present specification;
FIG. 4 is a flow chart illustrating a message reach procedure provided in an embodiment of the present specification;
fig. 5 is a flowchart illustrating a push message processing method of an IOS client according to another embodiment of the present specification;
fig. 6 is a schematic diagram of a click reporting process according to another embodiment of the present specification;
fig. 7 is a flowchart illustrating a push message processing method of an IOS client according to yet another embodiment of the present specification;
fig. 8 is a schematic structural diagram of a push message processing apparatus of an IOS client according to an embodiment of the present specification;
fig. 9 is a schematic structural diagram of a push message processing apparatus of an IOS client according to another embodiment of the present specification;
fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the present disclosure more clear, the technical solutions of the present disclosure will be clearly and completely described below with reference to the specific embodiments of the present disclosure and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person skilled in the art without making any inventive step based on the embodiments in this description belong to the protection scope of this document.
In combination with the description of the background art, the IOS is a closed platform, so that when the server sends push messages to the IOS client through the IOS server, it cannot be counted how many push messages actually reach the IOS client, thereby affecting subsequent decisions. Based on this, this specification provides a push message processing method for an IOS client, where when receiving a push message, the IOS client reads a user identifier from a corresponding shared sandbox, assembles the user identifier with the push message into a log file, and reports the log file to a server to notify the server that the push message reaches the IOS client.
An application scenario of the present specification is exemplarily described below with reference to fig. 1.
The application scene comprises the following steps: an IOS client 101, a server 102 corresponding to the IOS client 101, a user equipment 103 installed with the IOS client, and an IOS server 104, wherein:
the server 102, which is generally a service server of a third party, initiates a push request to the IOS server 104, where the push request carries a push message and a push plan thereof, and the push plan refers to a 'white paper' formulated by a service party to push the push message, and may include: push time, push crowd, etc.;
the IOS server 104, which generally refers to an IOS platform corresponding to the user equipment 103, responds to the push request, and pushes the push message to the user equipment 103 according to the push plan through wireless communication, where the wireless communication refers to long-distance transmission communication performed without conductor or cable propagation, and may be performed through radio, and the like;
and the user equipment 103 transmits the push message to the IOS client 101, and the IOS client 101 displays the push message to complete the touch of the push message.
The user equipment 103 is a terminal device based on an IOS operating system, and may be a mobile terminal (such as a smart phone and a tablet computer), or a wearable device (such as a smart watch and a bracelet), and the like; the IOS client 101 refers to a client installed in the user equipment 103; the server 102 corresponds to the IOS client 101, and is configured to receive a request from the IOS client 101 and provide a corresponding service.
The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.
Fig. 2 is a flowchart illustrating a push message processing method of an IOS client according to an embodiment of the present specification, which can be executed by the IOS client in fig. 1, and referring to fig. 2, the method may specifically include the following steps:
step 202, receiving a push message sent by the IOS system, where the push message is generated by a server corresponding to the IOS client;
it is understood that sending a push message to an IOS client needs to satisfy a condition that the IOS client has registered a push right, otherwise, the IOS server cannot send the push message to the IOS client. The implementation manner of registering the push authority may be:
after login is successful, sending a registration request to the server, wherein the registration request carries a device identifier of the user device provided with the IOS client, and the registration request is used for requesting to register the push permission of the IOS client; and receiving a registration result returned by the server.
Referring to fig. 3, the implementation may specifically be exemplified as:
step 302, logging in the ISO client by a user;
step 304, after the login is successful, sending a registration request to the server;
the registration request carries an equipment identifier (devicetoken) of user equipment for installing the IOS client, and is used for requesting to register the pushing permission of the IOS client; specifically, the reported data security can be protected by https uploading, Sspning prevention and other modes, and the device token is prevented from being leaked for use.
Step 306, the server sends the device identifier to an IOS server for registration;
step 308, the IOS server registers the push authority for the user equipment based on the equipment identifier and returns a registration result;
step 310, the server receives the registration result and forwards the registration result to the IOS client;
step 312, the IOS client receives the registration result returned by the server and displays it to the user.
Based on this, in the embodiment of the present specification, the server of the service party performs the push authority registration of the IOS client, so that the service party can count the number of IOS clients successfully registering the push authority, and further provide data support for subsequent accurate statistics of push authority.
Step 204, reading a user identifier cached in a shared sandbox corresponding to the IOS client, where the shared sandbox is used to cache the user identifier of the user who logs in the IOS client;
with reference to fig. 3, after the user completes login, the IOS client may cache the user identifier of the user who logs in the IOS client in the APP Groups shared sandbox, so as to be called by the server of the service party or the IOS server.
Step 206, generating a first log file based on the push message and the user identifier, wherein the first log file is used for representing that the push message reaches the IOS client; one implementation may be:
and performing data assembly processing on the push message and the user identifier through a first buried point component of the IOS client to generate a first log file.
The first embedded point component can be embedded into the IOS client and used for collecting and recording push messages corresponding to the IOS client, assembling log files and reporting the log files to a server in real time or in a delayed manner through the IOS client; further, the point buying component can encrypt the recorded data to obtain an encrypted log file. The specific assembly method and encryption method are not limited herein.
And step 208, uploading the first log file to a server, so that the server can perform statistical analysis on the arrival situation of the push message.
The first log file may carry a user identifier of a logged-in IOS client, an equipment identifier of a user equipment on which the IOS client is installed, and the like. Thus, the server can determine the IOS clients actually reached by the push message and the number thereof based on the first log file.
In addition, with reference to fig. 3, after the IOS client successfully registers the push right, the state of the IOS client may be reported to the server after the user successfully logs in, or before or while reporting the first log file; specific examples can be:
example 1, reporting first state information to the server, where the first state information is used to characterize a push permission of a user to open the IOS client. Thus, the server may determine the number of IOS clients that open push privileges. The authority state of the pushing authority can be collected by the first embedded point component and provided for the server.
Example 2, reporting second state information to the server, where the second state information is used to represent that the IOS client is in an operating state. Thus, the server may determine the number of IOS clients that are running.
Based on example 1 and example 2, the server may determine that the push message may statistically analyze the number of IOS clients expected to reach, preferably the number of IOS clients in a running state and with a push permission being turned on, and may further analyze a real trigger rate of the push message based on the number of IOS clients really reaching and the number of IOS clients expected to reach, thereby providing accurate data support for a subsequent push policy.
The push-to-reach procedure of the push message is explained in detail below with reference to fig. 4:
step 402, a service party operates and makes an initial push message, and sends and broadcasts the initial push message to a server of the service party;
step 404, the server performs content addition processing on the initial push message to obtain a complete push message;
the content added by the content adding process may include information such as a push task ID and a template ID used by a push message;
step 406, the server initiates a push request to the IOS server, where the push request carries a complete push message to request the IOS server to push the push message to an IOS client corresponding to the server;
step 408, the IOS server pushes the push message to the user equipment of the IOS operating system;
step 410, the user equipment transmits the push message to an extension component server extension of the IOS client;
step 412, when the extension component of the IOS client receives the push message, reading the user identifier of the IOS client from the shared sandbox corresponding to the IOS client;
step 414, a buried point component of the IOS client collects and records the user identifier and the push message, and performs assembly processing and encryption processing on the user identifier and the push message to generate a first log file; the encryption process is preferably performed using the RSA algorithm.
Step 416, the buried point component of the IOS client sends the first log file to the extension component of the IOS client;
step 418, the extension component of the IOS client reports the first log to the server of the service side to inform the server that the IOS client receives the push message, that is, the push message reaches the IOS client.
The display timing of the push message may be that the push message is sent to the IOS client for display after the user equipment receives the push message, or the push message is displayed while the extension component reports the first log file.
Therefore, when receiving the push message, the present embodiment reads, by the IOS client, the user identifier logged in the IOS client from the corresponding shared sandbox, assembles the user identifier into a log file together with the push message, and uploads the log file to the server to notify the server that the push message touches the IOS client, so that the server can statistically analyze the actual touch condition of the push message.
Fig. 5 is a flowchart illustrating a push message processing method of an IOS client according to another embodiment of the present specification, which can be executed by the IOS client in fig. 1, and referring to fig. 5, the method further includes the following steps based on the corresponding embodiment in fig. 1:
step 502, when detecting that the user clicks the input of the push message, generating a second log file, wherein the second log file is used for representing that the user clicks the push message; specifically, data assembly processing can be performed on the push message and the user identifier through a second embedded point component of the IOS client, so as to generate a second log file; the second buried point component and the first buried point component may be the same buried point component.
And step 504, uploading the second log file to the server so that the server can perform statistical analysis on the click rate of the push message.
Referring to fig. 6, the implementation of step 502 and step 504 may be:
after the IOS client displays the push message, the user can click the push message; the IOS client records click related information of a user and sends the click related information to the embedded point component; and the embedded point component assembles point-click related information and the push message and carries out encryption processing to generate a second log file, and reports the second log file to the server so as to inform a server user that the push message is clicked. The click related information may include click time, position information of the user when the click behavior occurs, click times, and the like.
Further, in order to facilitate data statistics of the push message by the server, the method further comprises:
generating a third log file, wherein the third log file is used for reporting characteristics related to clicking the push message; and uploading the third log file to the server so that the server can decide the optimal push scheme of the push message based on a preset deep learning algorithm.
Wherein, the content in the third log file can also be reported by the second log file; the characteristics related to the push message comprise a module ID (such as pictures and texts, links and the like) used by the push message, a push message type (such as discount coupons, recharge and the like) and the like; and then, combining click related information in the second log file, the server can perform statistical analysis on characteristics such as portrait, time and dwell time for opening the IOS client, time and dwell time for clicking the push message, position information when the IOS client is opened or the push message is clicked, and the like, and then, learning is performed by using a preset deep learning algorithm so as to decide an optimal push scheme with higher conversion rate and less interference to users.
Therefore, in the embodiment, after the user clicks the push message, the second log file is assembled through the point burying component of the IOS client and uploaded to the server, so that the server is informed that the user clicks the push message, and the server can statistically analyze the real conversion condition (such as click rate) of the push message.
Fig. 7 is a flowchart illustrating a push message processing method of an IOS client according to another embodiment of the present specification, which can be executed by the server in fig. 1, and referring to fig. 7, the method may specifically include the following steps:
step 702, receiving a first log file sent by a first IOS client;
the first log file is used for representing that a push message of the server reaches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier for logging in the first IOS client;
it will be understood that, before step 702, corresponding to the description related to the corresponding embodiment of fig. 1, with reference to fig. 3, the method further comprises: registering a push authority for the IOS client, which may specifically be:
receiving a registration request sent by the first IOS client, wherein the registration request carries a device identifier of a user device provided with the first IOS client, and the registration request is used for requesting to register the push permission of the first IOS client; and sending the equipment identifier to an IOS server for registration, and returning a registration result to the IOS client.
Step 704, determining the number of the first IOS clients based on the first log file;
step 706, determining a reach condition of the push message based on the number of the first IOS clients and the number of second IOS clients, where the second IOS clients are IOS clients expected to reach the push message.
The second IOS client may be an IOS client that opens a push right; specifically, if first state information reported by an IOS client is received, the IOS client is determined to be an IOS client that opens a push right, and the first state information is used for representing that a user has opened the push right of the IOS client.
The second IOS client may also be an IOS client in an operating state, and specifically, if second state information reported by the IOS client is received, it is determined that the IOS client is the IOS client in the operating state, and the second state information is used to represent that the IOS client is in the operating state.
The second IOS client may also be an IOS client that is running and opens push privileges.
Referring to fig. 6, after step 706, the method further comprises: the step of counting the click rate may specifically be:
receiving a second log file sent by a third IOS client, wherein the second log file is used for representing that a user corresponding to the third IOS client clicks the push message; determining a number of the third IOS clients based on the second log file; determining a click-through rate for the push message based on the number of third IOS clients.
Based on this, the embodiment of the present specification statistically analyzes the situation that the user clicks the push message by using the second log file reported by the IOS client, so as to analyze the real conversion situation (such as click rate) of the push message.
In addition, in order to achieve the purpose of intelligent pushing, the method may further include: the method comprises the steps of intelligently generating a push scheme, and the implementation mode of the steps can be as follows:
receiving a third log file sent by the third IOS client, wherein the third log file is used for reporting characteristics related to clicking the push message; analyzing the relevant features based on a preset deep learning algorithm to decide an optimal push scheme of the push message; the characteristics carried in the third log file can also be reported to the server by the first log file and/or the second log file. The step may be specifically exemplified by:
first, the push message related features may include: the number of times that the user opens the IOS client, the duration that the user uses the IOS client, the number of times that the IOS client opens the push message, the duration that the user browses the push message, the model of the user equipment, the network type used by the user equipment, and the like are recorded as the feature set corresponding to the push message.
Secondly, based on the feature set corresponding to the push message, the push related features of the user are determined by combining with a preset analysis rule. Wherein the push related features may comprise at least: fatigue tolerance, push interest time distribution, intention time period for opening a push message, etc.; the fatigue tolerance refers to the tolerance of a user to the push message, and the higher the score is, the higher the tolerance is, otherwise, the lower the tolerance is; the push interested time distribution refers to a time period in which the user is interested in pushing messages within a certain time (such as one day); the intention time period for opening the push message refers to a time period within a certain time (such as a day) in which the user has an intention to open the push message.
Because the push related characteristics required to be determined are different and the corresponding analysis rules are different, the following detailed description takes fatigue tolerance as an example:
the analysis rule corresponding to the fatigue tolerance may be: opening the IOS client for 5 minutes, opening the IOS client for 1-5 times for 10 minutes, and opening the IOS client for 5-20 times for 20 minutes; the IOS client stays for more than 2 minutes and gives 3 minutes, stays for more than 2-10 minutes and gives 10 minutes, and gives more than 10 minutes and gives 20 minutes; opening the push message once for 10 minutes, opening the push message 2-5 times for 20 minutes, and opening the push message 5-10 times or more for 50 minutes; the low-end machine gives 10 minutes, and the high-end machine gives 20 minutes; the WIFI network is given 30 points, the 4G or 5G network is given 20 points, and the others are given 10 points.
Based on the analysis rule, when pushing messages, the fatigue tolerance of the user every day is calculated by multiplying the score of the fatigue dimension by a corresponding coefficient, so that different pushing strategies are formulated for the users with different fatigue tolerances, if: for users with high fatigue tolerance, a proper amount of more push messages can be pushed, and conversely, a few push messages are pushed.
In addition, for the interested time distribution, the determination method can be as follows: based on characteristics such as a time point when the user starts an IOS client, a time point when the user opens the push message, a time length when the user browses the push message and the like in the characteristic set corresponding to the push message, a time period in which the user is interested in each push message is learned through a machine learning algorithm, and then an optimal push scheme for pushing in the interested time period is made.
Similarly, for the intention time period for opening the push message, the determination method may be as follows: the time period that the user intends to open each pushed message can be learned through a machine learning algorithm based on the characteristics of the time point when the user opens the pushed message, the position where the user opens the pushed message and the like, and an optimal pushing scheme for pushing in the time period that the user intends to open is further formulated.
Further, based on the deep learning process, the server may perform a directional pushing scheme, which may specifically be exemplified as:
example 1, when the oriented geographic location is pushed (for example, in a western style area), according to address location information reported by a user, aggregation may be performed in lbs information latitude, so as to obtain a user group in the western style area, and a push message is pushed to the user group, thereby reducing interference to other users.
Example 2, according to a time law curve of the user starting the IOS client, an effective card can be directionally pushed at a meal point of the user or a place where the user frequently sits in a public bus and purchases goods.
Based on this, in the embodiments of the present description, AI modeling is performed through deep learning based on relevant features reported by the IOS client, so as to intelligently make an optimal push scheme corresponding to each dimension, thereby providing a push effect and reducing traffic loss caused by data transmission.
Therefore, when receiving the push message, the IOS client reads the user identifier of the logged IOS client from the corresponding shared sandbox, assembles the user identifier with the push message into a log file, and uploads the log file to the server, so as to inform the server that the push message reaches the IOS client, and allow the server to statistically analyze the actual reaching condition of the push message.
Fig. 8 is a schematic structural diagram of a push message processing apparatus of an IOS client according to an embodiment of the present specification, and referring to fig. 8, the apparatus may specifically include: a receiving module 801, a reading module 802, a processing module 803, and a first uploading module 804, wherein:
a receiving module 801, configured to receive a push message sent by an IOS system, where the push message is generated by a server corresponding to an IOS client;
a reading module 802, configured to read a user identifier cached in a shared sandbox corresponding to the IOS client, where the shared sandbox is used to cache a user identifier of a user logging in the IOS client;
a processing module 803, configured to generate a first log file based on the push message and the user identifier, where the first log file is used to represent that the push message reaches the IOS client;
the first uploading module 804 uploads the first log file to a server, so that the server can statistically analyze the reach condition of the push message.
Optionally, the processing module 803 includes:
and the processing unit is used for performing data assembly processing on the push message and the user identifier through a first buried point component of the IOS client to generate a first log file.
Optionally, the apparatus further comprises:
the registration module sends a registration request to the server after login is successful, wherein the registration request carries the equipment identifier of the user equipment provided with the IOS client, and the registration request is used for requesting to register the push permission of the IOS client; and receiving a registration result returned by the server.
Optionally, the apparatus further comprises:
and the first reporting module is used for reporting first state information to the server, wherein the first state information is used for representing the pushing permission of the user for opening the IOS client.
Optionally, the apparatus further comprises:
and the second reporting module is used for reporting second state information to the server, wherein the second state information is used for representing that the IOS client is in an operating state.
Optionally, the apparatus further comprises:
the second uploading module is used for generating a second log file when the input that the user clicks the push message is detected, wherein the second log file is used for representing that the user clicks the push message; and uploading the second log file to the server so that the server can perform statistical analysis on the click rate of the push message.
Optionally, the click reporting module includes:
and the reporting unit is used for performing data assembly processing on the push message and the user identifier through a second embedded point component of the IOS client to generate the second log file.
Optionally, the apparatus further comprises:
the third uploading module is used for generating a third log file, and the third log file is used for reporting the characteristics related to clicking the push message; and uploading the third log file to the server so that the server can decide the optimal push scheme of the push message based on a preset deep learning algorithm.
Therefore, when receiving the push message, the embodiment reads the user identifier logged in the IOS client from the corresponding shared sandbox by the IOS client, assembles the user identifier into a log file together with the push message, and uploads the log file to the server to inform the server that the push message touches the IOS client, so that the server can statistically analyze the real touch condition of the push message; and after the user clicks the push message, a second log file is assembled through a point-buried component of the IOS client and uploaded to the server to inform the server that the user clicks the push message, so that the server can count and analyze the real conversion condition (such as click rate) of the push message.
Fig. 9 is a schematic structural diagram of a push message processing apparatus of an IOS client according to another embodiment of the present specification, and referring to fig. 9, the apparatus may specifically include: a receiving module 901, a first processing module 902 and a second processing module 903, wherein:
a receiving module 901, configured to receive a first log file sent by a first IOS client, where the first log file is used to represent that a push message of the server reaches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier logged in the first IOS client;
a first processing module 902 that determines a number of the first IOS clients based on the first log file;
the second processing module 903 determines, based on the number of the first IOS clients and the number of second IOS clients, a reach condition of the push message, where the second IOS client is an IOS client that is expected to reach the push message.
Optionally, the second IOS client includes:
opening an IOS client side with a push authority; alternatively, the first and second electrodes may be,
an IOS client in a running state; alternatively, the first and second electrodes may be,
and the IOS client is in a running state and opens the push authority.
Optionally, the apparatus further comprises:
the first determining module determines that the IOS client is the IOS client for opening the push permission if first state information reported by the IOS client is received, wherein the first state information is used for representing that a user opens the push permission of the IOS client.
Optionally, the apparatus further comprises:
and the second determining module is used for determining that the IOS client is in the running state if second state information reported by the IOS client is received, and the second state information is used for representing that the IOS client is in the running state.
Optionally, the apparatus further comprises:
a registration corresponding module, configured to receive a registration request sent by the first IOS client, where the registration request carries an equipment identifier of a user equipment on which the first IOS client is installed, and the registration request is used to request to register a push permission of the first IOS client; and sending the equipment identifier to an IOS server for registration, and returning a registration result to the IOS client.
Optionally, the apparatus further comprises:
the third processing module is used for receiving a second log file sent by a third IOS client, wherein the second log file is used for representing that a user corresponding to the third IOS client clicks the push message; determining a number of the third IOS clients based on the second log file; determining a click-through rate for the push message based on the number of third IOS clients.
Optionally, the apparatus further comprises:
a fourth processing module, configured to receive a third log file sent by the third IOS client, where the third log file is used to report a feature related to clicking the push message; and analyzing the relevant characteristics based on a preset deep learning algorithm to decide an optimal push scheme of the push message.
Therefore, when receiving the push message, the IOS client reads the user identifier of the logged IOS client from the corresponding shared sandbox, assembles the user identifier with the push message into a log file, and uploads the log file to the server, so as to inform the server that the push message reaches the IOS client, and allow the server to statistically analyze the actual reaching condition of the push message.
In addition, as for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to part of the description of the method embodiment. Further, it should be noted that, among the respective components of the apparatus of the present specification, the components thereof are logically divided according to the functions to be implemented, but the present specification is not limited thereto, and the respective components may be newly divided or combined as necessary.
Fig. 10 is a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure, and referring to fig. 10, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include hardware required by other services. The processor reads the corresponding computer program from the nonvolatile memory to the memory and then runs the computer program, and the pushing message processing device of the IOS client is formed on the logic level. Of course, besides the software implementation, the present specification does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may be hardware or logic devices.
The network interface, the processor and the memory may be interconnected by a bus system. The bus may be an ISA (Industry Standard Architecture) bus, a PCI (peripheral component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 10, but this does not indicate only one bus or one type of bus.
The memory is used for storing programs. In particular, the program may include program code comprising computer operating instructions. The memory may include both read-only memory and random access memory, and provides instructions and data to the processor. The Memory may include a Random-Access Memory (RAM) and may also include a non-volatile Memory (non-volatile Memory), such as at least 1 disk Memory.
The processor is used for executing the program stored in the memory and specifically executing:
receiving a push message sent by an IOS system, wherein the push message is generated by a server corresponding to an IOS client;
reading a user identifier cached in a shared sandbox corresponding to the IOS client, wherein the shared sandbox is used for caching the user identifier of a user logging in the IOS client;
generating a first log file based on the push message and the user identifier, wherein the first log file is used for representing that the push message reaches the IOS client;
and uploading the first log file to a server so that the server can perform statistical analysis on the reaching condition of the push message.
Alternatively, the first and second electrodes may be,
receiving a first log file sent by a first IOS client, wherein the first log file is used for representing that a push message of the server touches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier for logging in the first IOS client;
determining a number of the first IOS clients based on the first log file;
determining a reach of the push message based on the number of the first IOS clients and the number of second IOS clients, the second IOS clients being IOS clients expected to reach the push message.
The methods performed by the push message processing apparatus or manager (Master) node of the IOS client according to the embodiments of fig. 8 to 9 of the present specification can be applied to or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present specification may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present specification may be embodied directly in a hardware decoding processor, or in a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
The push message processing device of the IOS client may also perform the methods of fig. 2-7 and implement the methods performed by the administrator node.
Based on the same inventive creation, the present specification also provides a computer-readable storage medium storing one or more programs, which when executed by an electronic device including a plurality of application programs, cause the electronic device to execute the push message processing method of the IOS client provided in the corresponding embodiments of fig. 2 to 5.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification.

Claims (21)

1. A push message processing method of an IOS client comprises the following steps:
receiving a push message sent by an IOS system, wherein the push message is generated by a server corresponding to an IOS client;
reading a user identifier cached in a shared sandbox corresponding to the IOS client, wherein the shared sandbox is used for caching the user identifier of a user logging in the IOS client;
generating a first log file based on the push message and the user identifier, wherein the first log file is used for representing that the push message reaches the IOS client;
and uploading the first log file to a server so that the server can perform statistical analysis on the reaching condition of the push message.
2. The method of claim 1, the generating a first log file based on the push message and the user identification, comprising:
and performing data assembly processing on the push message and the user identifier through a first buried point component of the IOS client to generate a first log file.
3. The method of claim 1, prior to receiving the push message sent by the IOS system, further comprising:
after login is successful, sending a registration request to the server, wherein the registration request carries a device identifier of the user device provided with the IOS client, and the registration request is used for requesting to register the push permission of the IOS client;
and receiving a registration result returned by the server.
4. The method of claim 3, further comprising, before or while transmitting the first log file to a server if the registration is successful:
and reporting first state information to the server, wherein the first state information is used for representing the pushing permission of the user for opening the IOS client.
5. The method of claim 4, further comprising:
and reporting second state information to the server, wherein the second state information is used for representing that the IOS client is in an operating state.
6. The method of claim 1, further comprising:
when the input that the user clicks the push message is detected, generating a second log file, wherein the second log file is used for representing that the user clicks the push message;
and uploading the second log file to the server so that the server can perform statistical analysis on the click rate of the push message.
7. The method of claim 6, the generating a second log file, comprising:
and performing data assembly processing on the push message and the user identifier through a second embedded point component of the IOS client to generate a second log file.
8. The method of claim 6, further comprising:
generating a third log file, wherein the third log file is used for reporting characteristics related to clicking the push message;
and uploading the third log file to the server so that the server can decide the optimal push scheme of the push message based on a preset deep learning algorithm.
9. A push message processing method of an IOS client comprises the following steps:
receiving a first log file sent by a first IOS client, wherein the first log file is used for representing that a push message of the server touches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier for logging in the first IOS client;
determining a number of the first IOS clients based on the first log file;
determining a reach of the push message based on the number of the first IOS clients and the number of second IOS clients, the second IOS clients being IOS clients expected to reach the push message.
10. The method of claim 9, the second IOS client comprising:
opening an IOS client side with a push authority; alternatively, the first and second electrodes may be,
an IOS client in a running state; alternatively, the first and second electrodes may be,
and the IOS client is in a running state and opens the push authority.
11. The method of claim 10, further comprising:
if first state information reported by the IOS client is received, the IOS client is determined to be the IOS client for opening the pushing authority, and the first state information is used for representing that a user opens the pushing authority of the IOS client.
12. The method of claim 10, further comprising:
and if second state information reported by the IOS client is received, determining that the IOS client is the IOS client in the running state, wherein the second state information is used for representing that the IOS client is in the running state.
13. The method of claim 9, prior to receiving the first log file sent by the first IOS client, further comprising:
receiving a registration request sent by the first IOS client, wherein the registration request carries a device identifier of a user device provided with the first IOS client, and the registration request is used for requesting to register the push permission of the first IOS client;
and sending the equipment identifier to an IOS server for registration, and returning a registration result to the IOS client.
14. The method of claim 9, further comprising:
receiving a second log file sent by a third IOS client, wherein the second log file is used for representing that a user corresponding to the third IOS client clicks the push message;
determining a number of the third IOS clients based on the second log file;
determining a click-through rate for the push message based on the number of third IOS clients.
15. The method of claim 14, further comprising:
receiving a third log file sent by the third IOS client, wherein the third log file is used for reporting characteristics related to clicking the push message;
and analyzing the relevant characteristics based on a preset deep learning algorithm to decide an optimal push scheme of the push message.
16. A push message processing apparatus of an IOS client, comprising:
the system comprises a receiving module, a sending module and a sending module, wherein the receiving module is used for receiving a push message sent by an IOS system, and the push message is generated by a server corresponding to an IOS client;
the reading module is used for reading the user identification cached in the shared sandbox corresponding to the IOS client, and the shared sandbox is used for caching the user identification of the user logging in the IOS client;
the processing module generates a first log file based on the push message and the user identifier, wherein the first log file is used for representing that the push message reaches the IOS client;
and the first uploading module uploads the first log file to a server so that the server can perform statistical analysis on the reach condition of the push message.
17. A push message processing apparatus of an IOS client, comprising:
the system comprises a receiving module, a sending module and a sending module, wherein the receiving module is used for receiving a first log file sent by a first IOS client, the first log file is used for representing that a push message of a server reaches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier for logging in the first IOS client;
a first processing module that determines a number of the first IOS clients based on the first log file;
and the second processing module is used for determining the reaching condition of the push message based on the number of the first IOS clients and the number of second IOS clients, and the second IOS clients are IOS clients expected to be reached by the push message.
18. An electronic device, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
receiving a push message sent by an IOS system, wherein the push message is generated by a server corresponding to an IOS client;
reading a user identifier cached in a shared sandbox corresponding to the IOS client, wherein the shared sandbox is used for caching the user identifier of a user logging in the IOS client;
generating a first log file based on the push message and the user identifier, wherein the first log file is used for representing that the push message reaches the IOS client;
and uploading the first log file to a server so that the server can perform statistical analysis on the reaching condition of the push message.
19. A computer-readable storage medium having a computer program stored thereon, which when executed by a processor, performs operations comprising:
receiving a push message sent by an IOS system, wherein the push message is generated by a server corresponding to an IOS client;
reading a user identifier cached in a shared sandbox corresponding to the IOS client, wherein the shared sandbox is used for caching the user identifier of a user logging in the IOS client;
generating a first log file based on the push message and the user identifier, wherein the first log file is used for representing that the push message reaches the IOS client;
and uploading the first log file to a server so that the server can perform statistical analysis on the reaching condition of the push message.
20. An electronic device, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
receiving a first log file sent by a first IOS client, wherein the first log file is used for representing that a push message of the server touches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier for logging in the first IOS client;
determining a number of the first IOS clients based on the first log file;
determining a reach of the push message based on the number of the first IOS clients and the number of second IOS clients, the second IOS clients being IOS clients expected to reach the push message.
21. A computer-readable storage medium having a computer program stored thereon, which when executed by a processor, performs operations comprising:
receiving a first log file sent by a first IOS client, wherein the first log file is used for representing that a push message of the server touches the first IOS client, and the first log file is generated by the first IOS client based on the push message and a user identifier for logging in the first IOS client;
determining a number of the first IOS clients based on the first log file;
determining a reach of the push message based on the number of the first IOS clients and the number of second IOS clients, the second IOS clients being IOS clients expected to reach the push message.
CN201911206059.5A 2019-11-29 2019-11-29 Push message processing method, device and equipment of IOS client Active CN110971690B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911206059.5A CN110971690B (en) 2019-11-29 2019-11-29 Push message processing method, device and equipment of IOS client

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911206059.5A CN110971690B (en) 2019-11-29 2019-11-29 Push message processing method, device and equipment of IOS client

Publications (2)

Publication Number Publication Date
CN110971690A true CN110971690A (en) 2020-04-07
CN110971690B CN110971690B (en) 2022-10-04

Family

ID=70032563

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911206059.5A Active CN110971690B (en) 2019-11-29 2019-11-29 Push message processing method, device and equipment of IOS client

Country Status (1)

Country Link
CN (1) CN110971690B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112000570A (en) * 2020-07-29 2020-11-27 北京达佳互联信息技术有限公司 Application testing method, device, server and storage medium
CN112346884A (en) * 2020-10-12 2021-02-09 口碑(上海)信息技术有限公司 Message reach data processing method and device
CN114374736A (en) * 2021-12-10 2022-04-19 厦门立林科技有限公司 APP notification-based user behavior analysis method, device and platform

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030081621A1 (en) * 2001-10-26 2003-05-01 Godfrey James A. System and method for controlling configuration settings for mobile communication devices and services
CN105391803A (en) * 2015-12-15 2016-03-09 腾讯科技（深圳）有限公司 Message pushing method and device
CN106033419A (en) * 2015-03-10 2016-10-19 深圳市腾讯计算机系统有限公司 An information real-time push method, device and system
CN107273266A (en) * 2017-06-09 2017-10-20 上海艾融软件股份有限公司 A kind of processing method and processing device of application daily record
CN107979820A (en) * 2016-10-25 2018-05-01 腾讯科技（北京）有限公司 A kind of method and device, equipment for testing PUSH message
CN108337296A (en) * 2018-01-12 2018-07-27 深圳壹账通智能科技有限公司 Message push processing method, device, computer equipment and storage medium
US20190045067A1 (en) * 2017-08-03 2019-02-07 Bullhead Innovations Ltd. Automatic configuration of communication app on user device upon arrival at hospitality establishment
CN109510859A (en) * 2018-08-27 2019-03-22 北京奇虎科技有限公司 A kind of statistical method and device of the amount of reach of PUSH message

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030081621A1 (en) * 2001-10-26 2003-05-01 Godfrey James A. System and method for controlling configuration settings for mobile communication devices and services
CN106033419A (en) * 2015-03-10 2016-10-19 深圳市腾讯计算机系统有限公司 An information real-time push method, device and system
CN105391803A (en) * 2015-12-15 2016-03-09 腾讯科技（深圳）有限公司 Message pushing method and device
CN107979820A (en) * 2016-10-25 2018-05-01 腾讯科技（北京）有限公司 A kind of method and device, equipment for testing PUSH message
CN107273266A (en) * 2017-06-09 2017-10-20 上海艾融软件股份有限公司 A kind of processing method and processing device of application daily record
US20190045067A1 (en) * 2017-08-03 2019-02-07 Bullhead Innovations Ltd. Automatic configuration of communication app on user device upon arrival at hospitality establishment
CN108337296A (en) * 2018-01-12 2018-07-27 深圳壹账通智能科技有限公司 Message push processing method, device, computer equipment and storage medium
CN109510859A (en) * 2018-08-27 2019-03-22 北京奇虎科技有限公司 A kind of statistical method and device of the amount of reach of PUSH message

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SANDIPAN SIKDAR, MARCIN BODYCHY: ""On the broadcast of segmented messages in dynamic networks"", 《2015 IEEE CONFERENCE ON COMPUTER COMMUNICATIONS WORKSHOPS》 *
何世俊: ""基于Syslog的网络信息日志管理系统"", 《中国优秀硕士学位论文全文数据库 信息科技辑》 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112000570A (en) * 2020-07-29 2020-11-27 北京达佳互联信息技术有限公司 Application testing method, device, server and storage medium
CN112346884A (en) * 2020-10-12 2021-02-09 口碑(上海)信息技术有限公司 Message reach data processing method and device
CN114374736A (en) * 2021-12-10 2022-04-19 厦门立林科技有限公司 APP notification-based user behavior analysis method, device and platform
CN114374736B (en) * 2021-12-10 2023-04-28 厦门立林科技有限公司 User behavior analysis method, device and platform based on APP notification

Also Published As

Publication number Publication date
CN110971690B (en) 2022-10-04

Similar Documents

Publication Publication Date Title
US11682032B2 (en) Methods and apparatus to estimate population reach from different marginal ratings and/or unions of marginal ratings based on impression data
CN109862018B (en) Anti-crawler method and system based on user access behavior
CN110874440B (en) Information pushing method and device, model training method and device, and electronic equipment
CN110032880B (en) Screen recording evidence obtaining method and system based on block chain and electronic equipment
CN113840012B (en) Block chain-based screen recording evidence obtaining method and system and electronic equipment
CN110971690B (en) Push message processing method, device and equipment of IOS client
CN111104664B (en) Risk identification method of electronic equipment and server
US20160379246A1 (en) Methods and apparatus to estimate an unknown audience size from recorded demographic impressions
US9203905B1 (en) Sessionization of visitor activity
CN110875933B (en) Information matching confirmation method and device
US11887132B2 (en) Processor systems to estimate audience sizes and impression counts for different frequency intervals
CN107733786B (en) Friend recommendation method and device
CN110309669B (en) Data labeling method, device and equipment
WO2021162946A1 (en) Methods and apparatus to estimate cardinality of users represented in arbitrarily distributed bloom filter arrays
CN109241733A (en) Crawler Activity recognition method and device based on web access log
US11687967B2 (en) Methods and apparatus to estimate the second frequency moment for computer-monitored media accesses
CN113516503A (en) Advertisement delivery region calibration method and related equipment
CN111625721A (en) Content recommendation method and device
CN111582954A (en) False data identification method and device
CN111431918A (en) Method and system for determining state label of target user based on block chain
CN115114603B (en) Base station equipment data management method and device and electronic equipment
CN116719717A (en) Buried point testing method, buried point testing device, electronic equipment and computer readable storage medium
KR101785169B1 (en) Beacon data aggregation and management platform
CN117725311A (en) Information processing method and device, storage medium and electronic equipment
CN116993352A (en) Service control method and device, storage medium and electronic device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20240219

Address after: Guohao Times City # 20-01, 128 Meizhi Road, Singapore

Patentee after: Advanced Nova Technology (Singapore) Holdings Ltd.

Country or region after: Singapore

Address before: 45-01 Anson Building, 8 Shanton Avenue, Singapore

Patentee before: Alipay laboratories (Singapore) Ltd.

Country or region before: Singapore