CN113162958B - Method, device, equipment and storage medium for intelligently pushing message - Google Patents
Method, device, equipment and storage medium for intelligently pushing message Download PDFInfo
- Publication number
- CN113162958B CN113162958B CN202010076382.1A CN202010076382A CN113162958B CN 113162958 B CN113162958 B CN 113162958B CN 202010076382 A CN202010076382 A CN 202010076382A CN 113162958 B CN113162958 B CN 113162958B
- Authority
- CN
- China
- Prior art keywords
- terminal
- message
- state
- data
- 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
- 238000000034 method Methods 0.000 title claims abstract description 74
- 230000006399 behavior Effects 0.000 claims description 38
- 230000003068 static effect Effects 0.000 claims description 35
- 230000006870 function Effects 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 10
- 230000004044 response Effects 0.000 claims description 7
- 238000012217 deletion Methods 0.000 claims 1
- 230000037430 deletion Effects 0.000 claims 1
- 238000012545 processing Methods 0.000 abstract description 13
- 238000010586 diagram Methods 0.000 description 18
- 230000007958 sleep Effects 0.000 description 18
- 238000005516 engineering process Methods 0.000 description 12
- 238000013473 artificial intelligence Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 5
- 238000010801 machine learning Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 2
- 238000013135 deep learning Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000013528 artificial neural network Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000005059 dormancy Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006698 induction Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000003058 natural language processing Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000002787 reinforcement Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
- 238000013526 transfer learning Methods 0.000 description 1
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a method, a device, equipment and a storage medium for intelligently pushing messages. The method comprises the following steps: after pushing a message to a first terminal, receiving state data sent by the first terminal, wherein the state data is data acquired by the first terminal when the message is in an unread state on the first terminal; analyzing the reason that the message is in an unread state on the first terminal according to the state data; when the reason is that the first terminal causes the error, pushing the message to at least one second terminal, wherein the second terminal and the first terminal are associated with the same user account. According to the technical scheme provided by the embodiment of the application, the possibility that the user misses the important message is reduced according to the actual situation that the user uses the terminal, so that the effectiveness of the message pushing function is effectively improved, and the processing capability of the message is improved.
Description
Technical Field
The present application relates generally to the field of data processing technologies, and in particular, to a method, an apparatus, a device, and a storage medium for pushing a message intelligently.
Background
Due to living and working needs, a user often has multiple terminals, for example, a user has a mobile phone, a desktop computer, and a notebook computer at the same time. So that the user may install favorite applications on a plurality of terminals at the same time. When the server pushes the message to the application programs with the same account, one of the message receiving ends is selected to push the message. This push method results in a low probability of messages being read.
Disclosure of Invention
In view of the above, the present application provides a method, apparatus, device, and storage medium for intelligently pushing a message, which can improve the reading rate of the message.
In a first aspect, an embodiment of the present application provides a method for pushing a message intelligently, where the method includes:
after pushing a message to a first terminal, receiving state data sent by the first terminal, wherein the state data is data acquired by the first terminal when the message is in an unread state on the first terminal;
analyzing the reason that the message is in an unread state on the first terminal according to the state data;
when the reason is that the first terminal causes the error, pushing the message to at least one second terminal, wherein the second terminal and the first terminal are associated with the same user account.
In a second aspect, an embodiment of the present application provides a method for pushing a message intelligently, where the method includes:
after receiving the message pushed by the server, the first terminal sends state data to the server when the message is in an unread state on the first terminal;
the server analyzes the reason that the message is in an unread state on the first terminal according to the state data;
When the reason is that the first terminal causes the error, the server pushes information to at least one second terminal, and the second terminal and the first terminal are associated with the same user account.
In a third aspect, an embodiment of the present application provides an apparatus for pushing a message intelligently, where the apparatus includes:
The receiving module is used for receiving state data sent by the first terminal after pushing the message to the first terminal, wherein the state data is data acquired by the first terminal when the message is in an unread state on the first terminal;
the analysis module is used for analyzing the reason that the message is in an unread state on the first terminal according to the state data;
And the pushing module is used for pushing the message to at least one second terminal when the first terminal causes the error, and the second terminal and the first terminal are associated with the same user account.
In a fourth aspect, an embodiment of the present application provides a system for intelligently pushing a message, where the system includes: the system comprises a first terminal, a server and at least one second terminal;
the first terminal is used for sending state data to the server after receiving the message pushed by the server and when the message is in an unread state on the first terminal;
the server is used for analyzing the reason that the message is in an unread state on the first terminal according to the state data; when the reason is that the first terminal causes the error, the server pushes information to at least one second terminal, and the second terminal and the first terminal are associated with the same user account.
In a fifth aspect, an embodiment of the present application provides a computer apparatus, including:
one or more processors;
A memory for storing one or more programs;
The one or more programs, when executed by the one or more processors, cause the one or more processors to perform a method embodying the first or second aspects described above.
In a sixth aspect, an embodiment of the present application provides a computer readable storage medium having stored thereon a computer program for implementing the method of the first or second aspect.
According to the method for intelligently pushing the message, after the message is pushed to the first terminal, state data sent by the first terminal is received, wherein the state data are data acquired by the first terminal when the message is in an unread state on the first terminal; analyzing the reason that the message is in an unread state on the first terminal according to the state data; when the reason is that the first terminal causes the error, pushing the message to at least one second terminal, wherein the second terminal and the first terminal are associated with the same user account. Compared with the prior art, the method for pushing the message to one terminal or synchronously pushing the message to a plurality of terminals can reduce the possibility of losing important messages by users according to the actual situation that the users use the terminals, effectively improves the effectiveness of the message pushing function and improves the processing capacity of the message.
Drawings
For a clearer description of an embodiment of the application, the drawings that are necessary for a brief description of the embodiments or of the prior art are presented for the purpose of illustrating a preferred method of implementation and are not to be construed as limiting the application. It should be further noted that, for convenience of description, only some, but not all of the relevant embodiments of the present application are shown in the drawings.
FIG. 1 is a block diagram of an implementation environment of a method for intelligent push messaging according to an embodiment of the present application;
FIG. 2 is a flow chart of a method for intelligent push messaging according to an embodiment of the present application;
FIG. 3 is a flow chart of a method of yet another intelligent push message, according to an embodiment of the present application;
FIG. 4 is a flow chart of a method for delivering a message intelligently according to yet another embodiment of the present application;
fig. 5 is a schematic diagram illustrating a first terminal after receiving a message according to an embodiment of the present application;
FIG. 6 is a diagram illustrating a message being folded according to an embodiment of the present application;
FIG. 7 is a flow chart of a method of determining why a message was not read, according to an embodiment of the application;
FIG. 8 is a flow chart of yet another method of determining why a message was not read, according to an embodiment of the application;
FIG. 9 is a schematic diagram of a second terminal display message, according to an embodiment of the present application;
FIG. 10 is a schematic diagram of yet another second terminal display message, according to an embodiment of the present application;
Fig. 11 is a schematic diagram illustrating a first terminal revocation message according to an embodiment of the present application;
FIG. 12 is a block diagram of an apparatus for intelligent push messaging, according to an embodiment of the present application;
FIG. 13 is a block diagram of another intelligent push message apparatus, according to an embodiment of the present application;
FIG. 14 is a system block diagram illustrating an intelligent push message, according to an embodiment of the present application;
fig. 15 is a schematic diagram of a computer system according to an embodiment of the present application.
Detailed Description
The application is described in further detail below with reference to the drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the present disclosure. It should be noted that, for convenience of description, only the portions related to the application are shown in the drawings.
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The application will be described in detail below with reference to the drawings in connection with embodiments.
Fig. 1 is an architecture diagram of an implementation environment of a method for intelligent push messaging according to an embodiment of the present application. As shown in fig. 1, the implementation environment architecture includes: a first terminal 101, at least one second terminal 102 and a server 103.
Wherein the hardware structure of the first terminal 101 and the second terminal 102 comprises a processor, a memory and a display device, and the software structure comprises a client of an application installed on the first terminal or the second terminal. The client may receive one or more messages pushed by the server.
The first terminal 101 and the second terminal 102 may be terminals that receive the first push message from the server, or may be terminals that receive the message to be synchronized for the second time. For example, the first terminal is a terminal that receives a pushed message from the server for the first time, and the second terminal 102 is a terminal that receives a synchronization message. The synchronization message is a message that is not read on the first terminal due to a miss after the first terminal 101 receives the message pushed by the server, and the server sends the message to the second terminal again.
Types of the first terminal 101 and the second terminal 102 include, but are not limited to, a smart phone, a tablet computer, a television, a notebook computer, a desktop computer, etc., which are not particularly limited in the embodiment of the present application.
The server 103 is configured to receive the collected data sent by the first terminal 101, determine, according to the collected data, a reason why the message pushed to the first terminal 101 is in an unread state, and push the message to the second terminal 102 again when the unread reason is missing.
The server 102 may be a server, a server cluster comprising a plurality of servers, or a cloud computing service center.
The first terminal 101, the second terminal 102 and the server 103 establish communication connection through a wired or wireless network.
In addition, it should be noted that, the method of pushing the message may be performed by the first terminal 101 and the server 103 in cooperation, or may be performed by the first terminal 101 alone.
Fig. 2 is a flow chart of a method for intelligent push messaging according to an embodiment of the present application. The method shown in fig. 2 may be performed by the server 103 in fig. 1, as shown in fig. 2, and comprises the steps of:
step 201, after pushing a message to a first terminal, receiving state data sent by the first terminal, where the state data is data collected by the first terminal when the message is in an unread state on the first terminal.
Step 202, analyzing the reason that the message is in the unread state on the first terminal according to the state data.
And 203, pushing the message to at least one second terminal when the error is caused by the first terminal, wherein the second terminal and the first terminal are associated with the same user account.
In the above steps, the reason that the message is in the unread state is analyzed according to the state data, and the state data can be analyzed by using an artificial intelligence algorithm to identify the behavior data of the user.
Wherein, artificial intelligence (English whole process: ARTIFICIAL INTELLIGENCE, english short: AI) is the theory, method, technique and application system that uses digital computer or the machine controlled by digital computer to simulate, extend and expand human intelligence, sense environment, acquire knowledge and use knowledge to obtain the best result. In other words, artificial intelligence is an integrated technology of computer science that attempts to understand the essence of intelligence and to produce a new intelligent machine that can react in a similar way to human intelligence. Artificial intelligence, i.e. research on design principles and implementation methods of various intelligent machines, enables the machines to have functions of sensing, reasoning and decision.
The artificial intelligence technology is a comprehensive subject, and relates to the technology with wide fields, namely the technology with a hardware level and the technology with a software level. Artificial intelligence infrastructure technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and other directions.
Machine learning (English whole process: MACHINE LEARNING, english short: ML) is a multi-domain interdisciplinary, and relates to multi-domain disciplines such as probability theory, statistics, approximation theory, convex analysis, algorithm complexity theory and the like. It is specially studied how a computer simulates or implements learning behavior of a human to acquire new knowledge or skills, and reorganizes existing knowledge structures to continuously improve own performance. Machine learning is the core of artificial intelligence, a fundamental approach to letting computers have intelligence, which is applied throughout various areas of artificial intelligence. Machine learning and deep learning typically include techniques such as artificial neural networks, confidence networks, reinforcement learning, transfer learning, induction learning, teaching learning, and the like.
In the embodiment of the application, after receiving the state data sent by the first terminal, the server intelligently analyzes the use state of the first terminal according to the state data, so as to identify the reason that the message is in an unread state, and then pushes the message to other terminal devices associated with the user account again according to the reason.
Or searching terminal equipment with higher user frequency from a plurality of terminal equipment by utilizing an artificial intelligence algorithm as a receiving end of the synchronous message.
In summary, in the method for intelligently pushing the message provided by the embodiment of the application, after the message is pushed to the first terminal, state data sent by the first terminal is received, wherein the state data is data acquired by the first terminal when the message is in an unread state on the first terminal; analyzing the reason that the message is in an unread state on the first terminal according to the state data; when the reason is that the first terminal causes the error, pushing the message to at least one second terminal, wherein the second terminal and the first terminal are associated with the same user account. Compared with the prior art, the method for pushing the message to one terminal or synchronously pushing the message to a plurality of terminals can reduce the possibility of losing important messages by users according to the actual situation that the users use the terminals, effectively improves the effectiveness of the message pushing function and improves the processing capacity of the message.
Fig. 3 is a flow chart of another method for intelligent push messaging according to an embodiment of the present application. The method shown in fig. 3 may be performed by the first terminal 101 in fig. 1, as shown in fig. 3, and the method includes the steps of:
In step 301, after receiving a message pushed by the server, the first terminal sends status data to the server when the message is in an unread state on the first terminal.
The state data are acquired by the first terminal when the message is in an unread state on the first terminal, and the first terminal acquires the related data of the equipment state.
Further, after receiving the status data, the server analyzes the reason that the message is in an unread state on the first terminal according to the status data, and when the reason is an error caused by the first terminal, the server generates a message withdrawal instruction and sends the message withdrawal instruction to the first terminal.
Step 302, a withdrawal instruction is received, and the message is not displayed in response to the withdrawal instruction.
In summary, according to the method for intelligently pushing the message provided by the embodiment of the application, when the message pushed to the first terminal is not read due to missing, the server sends the withdrawal instruction to the first terminal, so that the temporary storage space of the first terminal is effectively saved, and the display interface is not occupied.
Fig. 4 is a flow chart of a method for intelligent push messaging according to yet another embodiment of the present application. The method shown in fig. 4 may be interactively performed by the first terminal 101, the at least one second terminal 102 and the server 103 in fig. 1, as shown in fig. 4, the method comprising the steps of:
In step 401, after receiving the message pushed by the server, and when the message is in an unread state on the first terminal, the first terminal collects the state data.
Wherein the pushed message is sent by the server, further referring to fig. 5, after receiving the message pushed by the server, the first terminal may display the pushed message on the screen. As shown in fig. 5, the QQ browser and the nailed server push messages to the first terminal, where the message a is pushed by the server of the QQ browser, the push content is "snowfall" fight in different parts "local snow in northwest regions, and the message B is pushed by the server of the nailed server, and the push content is" the attendance record has an abnormality in your last week, please process in time ". When the first terminal receives the pushed message, whether the message is read or not can be monitored in real time, and whether the message is in an unread state or not can also be detected according to preset time.
Alternatively, the real-time monitoring of whether the message is read can be performed by acquiring the message reading status identifier multiple times. Wherein the message reading status identifier indicates whether the pushed message is read. For example, the message reading status identifier includes 0 and 1, where 0 indicates that the message is read, and 1 indicates that the message is not read, and when the acquired message status identifier is 0, it is determined that the message is read, and if the acquired message status identifier is 1, it indicates that the message is not read.
The state data is data describing the state of the first terminal, and further, the state data comprises dynamic data.
Wherein the dynamic data is non-fixed and invariant data, which may change at different times. For example, the data describing some states of the terminal, for example, the state of charge identifier includes 0 and 1, where 0 indicates that charging is in progress, 1 indicates that charging is not in progress, the value of the obtained state of charge identifier is 0 when the first terminal is in the state of charge, and the value of the obtained state of charge identifier is 1 when the first terminal is in the state of non-charge. Further, the status identifier may also be a sleep status identifier, a lock screen status identifier, an operated status identifier, etc.
The sleep state is understood as a state that the terminal screen processes a black screen, that is, the terminal is not operated by a user temporarily, and the screen locking state is a state that the terminal screen is on and locked. Further, the relation between dormancy and screen locking is: when the terminal is in the dormant state, the terminal can be changed from the dormant state to the screen locking state through a preset triggering mode, and further, after the screen in the screen locking state is unlocked, an operation (at the moment, the operated state identifier is used for indicating that the first terminal is currently operated) can be performed on the screen, for example, information is read, video is watched and the like.
Illustratively, the sleep state identifier, the lock screen state identifier, and the charge state identifier each include 0 and 1. Further, the relationship between each status identifier and the screen status is as follows:
sleep state identification: 0 dormant, 1 not dormant
And (3) screen locking state identification: 0 lock screen, 1 unlock screen
Charge state identification: 0 charging, 1 not charging
Since the dynamic data acquired at different times may be different, it is necessary to acquire the dynamic data multiple times within a first preset period of time to determine whether the dynamic data is changing. The first preset time period is any time period determined according to actual needs, for example, 5 minutes, 10 minutes and the like.
The dynamic data obtained in the first preset time period is as follows:
Sleep state identification: 0
And (3) screen locking state identification: 0
Charge state identification: 0
Optionally, the status data further includes static data, where the static data is relatively fixed, for example, data describing properties of the terminal, such as a first terminal identifier, a first terminal system version identifier, a Read Only Memory (ROM) version, and the like.
Illustratively, when the static data includes the first terminal identifier, the ROM version, and the first terminal system version identifier, the static data is obtained as follows:
Terminal identification: a
ROM version: b01 (B01)
First terminal system version identification: c01
Further, the terminal identification, the ROM version, and the first terminal system version identification may be used to determine whether the first terminal has a message folding function and a message categorizing function. The message folding function is that when the first terminal receives a plurality of messages, only a preset message is displayed, for example, only one message is displayed, other messages are folded, and when corresponding triggering operation is executed, the folded message can be displayed. For example, referring to fig. 6, the terminal has a message folding function, and the QQ browser pushes 5 messages in total, but only one push message is shown at the terminal, the other 4 are folded, and when the down arrow is clicked, the other 4 folded messages are displayed. The message classifying function classifies the message when the message received by the first terminal, for example, as important or unimportant.
Optionally, the status data further includes user usage behavior data, wherein the usage behavior data includes usage behavior identifications, such as delete identifications, categorize as unimportant identifications, categorize as uninteresting identifications; among other things, usage behavior may include deleting message behavior, categorizing as unimportant behavior, categorizing as uninteresting behavior, and the like. Further, the user inputs a deleting instruction, a classifying instruction or a non-interest classifying instruction through the display interface, and the first terminal directly deletes the pushed message according to the received instruction and classifies the message as non-important or non-interest.
When it is described here, the categorization is not important for the user to perform itself, unlike the message categorization function mentioned in the static data, which is the function of the first terminal itself.
Alternatively, step 401 may be: the first terminal monitors the read state of the received message in real time, and when the condition that the unread message exists is monitored, the first terminal collects the state data of the first terminal.
When the first terminal receives the message, the user may be performing other operations using the first terminal without having access to read the message, so that when the first terminal receives the message, it is not immediately determined whether the message is read, but after a second preset period of time, it is determined whether the message is read. Thus, optionally, step 401 may also be: when the first terminal receives the pushed message, waiting for a second preset time period; when the second preset time period is over, judging whether the pushed message is read or not; when not read, the state data of the user is collected.
The second preset time period may be any time period determined according to needs, for example, 5 minutes, 10 minutes, and the like.
In step 402, the first terminal sends status data to the server.
In step 403, the server receives status data.
In step 404, the server analyzes the reason that the message is in an unread state according to the status data.
Alternatively, referring to fig. 7, when the state data received by the server is the dynamic data of the first terminal, the dynamic data may be a state identification.
The status identifier may be a sleep status identifier, a charging status identifier, a screen locking status identifier, etc.
When the status data is a status identifier, step 404 includes:
step 4041, determining whether the first terminal is in an unused state according to the dynamic data.
Alternatively, the process may be carried out in a single-stage,
When the state identifier is the sleep state identifier, determining whether the first terminal is in an unused state according to the dynamic data, including:
And when the sleep state identifier indicates that the first terminal is in the sleep state, determining that the first terminal is in an unused state. Or alternatively
When the state identifier is a charging state identifier and a screen locking state identifier, determining whether the first terminal is in an unused state according to the state identifier includes:
when the screen locking state identifier indicates that the first terminal is in a screen locking state, determining that the first terminal is in an unused state; or alternatively
And when the charging state identifier indicates that the first terminal is in a charging state and the screen locking state identifier indicates that the first terminal is in a screen locking state, determining that the first terminal is in an unused state.
Optionally, when the dynamic data includes three identifiers of the sleep state identifier, the lock screen state identifier, and the charging state identifier, step 4041 includes:
Step one, determining whether the sleep state identifier indicates that the first terminal is in a sleep state;
Step two, when the sleep state identification indicates that the first terminal is in the sleep state, determining that the first terminal is in an unused state or
And when the dormant state identifier is determined to indicate that the first terminal is in a non-dormant state, determining whether the screen locking state identifier and the charging state identifier indicate that the first terminal is in a charging state and the screen locking state.
Step three, when the screen locking state identifier and the charging state identifier indicate that the first terminal is in a charging state and the screen locking state, determining that the first terminal is in an unused state or
And when the screen locking state identifier and the charging state identifier indicate that the first terminal is in a non-charging state and the screen locking state is not achieved, determining that the first terminal is in a used state.
Optionally, when the dynamic data received by the server includes an operation state identifier, and when the operation state identifier characterizes that the first terminal is being operated, then directly determining that the first terminal is being used.
In step 4042, if it is determined that the first terminal is in the unused state, the reason that the message is in the unread state is determined as missing.
In step 4043, if it is determined that the first terminal is in use, the reason that the message is in an unread state is determined as non-missing.
Since the dynamic data characterizes whether the terminal is in use, when the terminal is in use, the message may still be in an unread state due to other configuration parameters. To more accurately identify the behavior habits of the user. Further, the behavior habit of the user can be identified by combining the static data of the first terminal.
When the status data received by the server further includes static data, referring to fig. 8, before step 4043, the method further includes:
step 4044, when it is determined that the first terminal is in use, analyzing whether the message is in a collapsed state or belongs to a non-important message category according to the static data.
Optionally, determining whether the message is in a collapsed state or belongs to a non-important message category according to the static data includes:
Searching message folding attributes and message classifying attributes corresponding to static data in a pre-established strategy library;
when the message folding attribute indicates that the message folding function is provided, the message is indicated to be in a folded state; or alternatively
When the message classification attribute indicates that the message classification attribute is provided, determining that the message belongs to a non-important message category.
Optionally, when the static data includes a terminal identifier, a read-only memory identifier, and an operating system identifier; determining whether a message is folded or classified as unimportant based on static data includes:
1. searching message folding attributes and message classifying attributes corresponding to the terminal identifier, the read-only memory identifier and the operating system identifier in a pre-established strategy library;
2. When the searched message folding attribute and message classifying attribute indicate at least one of a message folding function or a message classifying function, determining that the message is in a folded state or belongs to a non-important message class; or alternatively
3. When the searched message folding attribute and message classifying attribute indicate that the message folding function is not available and the message classifying function is not available, the message is determined to be in an unfolded state and belongs to an unimportant message class.
The policy library is used for collecting a large amount of static data in advance, analyzing the relation between the static data and the terminal attribute, and then establishing the corresponding relation between the static data and the terminal attribute according to the analysis result.
Illustratively, the policy repository includes the following:
Terminal identification: a
ROM version: b01 (B01)
First terminal system version identification: c01
Message fold attribute: support folding
Message classification attribute: support categorization
Terminal identification: b
ROM version: c01
First terminal system version identification: d01
Message fold attribute: without message folding function
Message classification attribute: without message classification
Further, illustratively, the static data obtained is:
Terminal identification: a
ROM version: b01 (B01)
First terminal system version identification: c01
Then the message folding attribute is searched from the strategy library to have the message folding function, and the message classifying attribute is searched from the strategy library to have the message classifying function. And determining that the message folding attribute corresponding to the static data has a message folding attribute, and determining that the message classifying attribute has a message classifying function.
In step 4045, if it is determined that the message is in a folded state or belongs to a non-important category, it is determined that the reason for the message being in an unread state is missing.
In step 4046, if it is determined that the message is in the unfolded state and does not belong to the unimportant class, the reason for determining that the message is in the unread state is not missed.
Alternatively, static data may be used, and then dynamic data may be used to determine the reason why the message is not read.
Alternatively, when the status data received by the server includes user usage behavior data, it may be first determined whether the cause of the unread message is a miss according to the user usage behavior identification. When judging that the reason that the message is not read is non-missing according to the user using behavior data, for example, when judging according to the deleting identification, classifying as the unimportant identification and classifying as the uninteresting identification, the server directly determines that the reason that the message is not read is non-missing when the user using behavior comprises at least one of deleting the message behavior, classifying as the unimportant behavior and classifying as the uninteresting behavior.
Step 405, when the cause is a miss, the server pushes the message to at least one second terminal.
The second terminal and the first terminal are associated with the same user account.
Optionally, the second terminal is a terminal currently on line, further, the second terminal is a terminal with the nearest on line time, or the second terminal may also be a terminal currently on line and with the greatest probability of reading the message, or the second terminal is a terminal with the greatest probability of being used currently.
Further, the probability of being currently used and the probability of the message being read may be derived by data statistical analysis. Therefore, the terminal receiving the message can be ensured to be an online terminal, so that the probability of the message seen by a user is improved, and the probability of the message read is further improved; and the message is pushed to only one terminal, repeated pushing can be reduced, so that the server pressure is reduced, and the trouble that a user repeatedly sees the message is eliminated.
Further, the second terminal is a terminal in a server terminal list, wherein the terminal list includes all terminals associated with the user account, and the online status of each terminal is identified. Illustratively, for a particular individual user, the corresponding terminal list is as follows:
User identification: 0000001
Terminal identification: 00001; on-line status: online line
Terminal identification: 00002; on-line status: online line
Terminal identification: 00003; on-line status: off-line
Optionally, step 405 includes: when the unread reason is a miss, searching a terminal in an online state in the terminal list as a second terminal; pushing the message to the searched second terminal in the online state.
In addition, when the reason that the message is not read is not missed, for example, the user is not interested, the server does not push the message to other terminals.
Step 406, the second terminal receives the message and displays it.
Optionally, referring to fig. 9, when the second terminal receives the message, the message is displayed on a screen in a reminding manner, for example, in fig. 9, only a "QQ browser, a new message is pinned" is displayed on a display interface of the second terminal, so that a user can determine whether to read the pushed message according to the needs of the user.
Alternatively, referring to fig. 10, when the second terminal receives the message, the summary of the message may be displayed on a screen, so that the user may intuitively see the summary, and thus, the user may determine whether to read the message according to the name of the application program, and may determine whether to read the push message according to the summary.
Optionally, still referring to fig. 4, before step 405, the method of intelligent push message further includes steps 407-409:
in step 407, when the reason for being in the unread state is a miss, the server generates a revocation instruction.
The server sends 408 the withdrawal instruction to the first terminal.
In step 409, the first terminal does not display a message in response to the withdrawal instruction.
Referring to fig. 11, the first terminal not displaying the message may delete the message directly from the display interface so that the first terminal is not displaying the message.
Optionally, after withdrawing the push message, a withdrawal reminder may be generated in the display interface of the first terminal to remind the user that the first terminal withdraws one push message.
Illustratively, when the first terminal withdraws a message of application A, the withdrawal reminder may be "withdraw a message of application A".
Further, when the withdrawal reminder is generated, a re-push reminder may also be generated to remind the user that the withdrawn message has been pushed again to the second terminal.
Illustratively, when the terminal of the second terminal is identified as a02, the push again alert may be "one message that has withdrawn application a, and the withdrawn message has been pushed to the terminal identified as a 02".
Alternatively, steps 407-409 may be performed after step 405 to perform the withdraw operation after the message is successfully pushed to the second terminal, so that when the pushing to the second terminal fails and no other terminal can push, the message of the first terminal is not pushed to the first terminal again, because the message of the first terminal has not been withdrawn yet.
Further, when the message is pushed to the second terminal and is still not read, the above steps 401 to 409 may be repeated to increase the probability that the message is read.
In summary, in the method for intelligently pushing the message provided by the embodiment of the application, after the message is pushed to the first terminal, state data sent by the first terminal is received, wherein the state data is data acquired by the first terminal when the message is in an unread state on the first terminal; analyzing the reason that the message is in an unread state on the first terminal according to the state data; when the reason is that the first terminal causes the error, pushing the message to at least one second terminal, wherein the second terminal and the first terminal are associated with the same user account. Compared with the prior art, the method for pushing the message to one terminal or synchronously pushing the message to a plurality of terminals can reduce the possibility of losing important messages by users according to the actual situation that the users use the terminals, effectively improves the effectiveness of the message pushing function and improves the processing capacity of the message.
In addition, according to the method for intelligently pushing the message, when the message pushed to the first terminal is not read due to missing, the server sends the withdrawal instruction to the first terminal, so that the temporary storage space of the first terminal is effectively saved, and the display interface is not occupied.
The embodiments in this specification are all described in a progressive manner, and similar parts between the various embodiments are mutually referred to. The examples at each step focus on the specific method at that step. The above-described embodiments are merely illustrative of the present application, and specific examples are provided for illustration only, and those skilled in the art to which the application pertains will appreciate that numerous modifications and variations can be made without departing from the principles of the application described in the examples.
Fig. 12 is a block diagram of an apparatus for intelligent push messaging according to an embodiment of the present application.
As shown in fig. 12, the apparatus includes:
A receiving module 601, configured to receive, after pushing a message to a first terminal, state data sent by the first terminal, where the state data is data collected by the first terminal when the message is in an unread state on the first terminal;
an analysis module 602, configured to analyze, according to the status data, a cause of the message in an unread state on the first terminal;
And the pushing module 603 is configured to push the message to at least one second terminal when the error is caused by the first terminal, where the second terminal and the first terminal are associated with the same user account.
Optionally, the status data includes a status identifier of the first terminal, and the analysis module 602 is further configured to:
Determining whether the first terminal is in an unused state according to the state identification;
if the first terminal is in an unused state, the cause is determined as a miss by the first terminal.
Optionally, when the status identifier includes a sleep status identifier, the analysis module 602 is further configured to:
when the sleep state identifier indicates that the first terminal is in a sleep state, determining that the first terminal is in an unused state; or alternatively
When the state identifier includes a charging state identifier and a screen locking state identifier, determining whether the first terminal is in an unused state according to the state identifier includes:
when the screen locking state identifier indicates that the first terminal is in a screen locking state, determining that the first terminal is in an unused state; or alternatively
When the charging state identifier indicates that the first terminal is in a charging state and the screen locking state identifier indicates that the first terminal is in a screen locking state, determining that the first terminal is in an unused state; or alternatively
When the state identifier includes a sleep state identifier, a charging state identifier and a screen locking state identifier, determining whether the first terminal is in an unused state according to the state identifier includes:
reading a screen locking state identifier and a charging state identifier when the dormant state identifier indicates that the first terminal is in an un-dormant state;
And when the screen locking state identifier indicates that the first terminal is in the screen locking state and the charged state identifier indicates that the first terminal is in the charged state, determining that the first terminal is in an unused state.
Optionally, the status data further includes static data of the first terminal, where the static data is data for describing properties of the first terminal, and the analysis module 602 is further configured to:
And if the first terminal is in a use state, analyzing the reason that the message is in an unread state on the first terminal according to the static data.
Optionally, the analysis module 602 is further configured to:
Searching message folding attributes and message classifying attributes corresponding to static data in a pre-established strategy library;
when the message folding attribute indicates that the message folding function is provided, the message is in a folded state, and the reason is determined to be the missing caused by the first terminal; or alternatively
And when the message belongs to the unimportant message category according to the message classification attribute, determining the cause as the missing caused by the first terminal.
Optionally, referring to fig. 13, the intelligent push message apparatus further includes:
and the generating module 604 is configured to generate a withdrawal instruction after pushing the message to the at least one second terminal, and send the withdrawal instruction to the first terminal, so that the first terminal does not display the message in response to the withdrawal instruction.
Optionally, the second terminal is found in a terminal list, where the terminal list includes all terminals associated with the user account, and the push module 603 is further configured to:
searching a second terminal in an online state;
pushing the message to the second terminal.
In addition, the relevant content in the device embodiment is referred to the method embodiment, and will not be described herein.
In summary, the device for intelligently pushing the message provided by the embodiment of the application receives the state data sent by the first terminal after pushing the message to the first terminal, wherein the state data is data acquired by the first terminal when the message is in an unread state on the first terminal; analyzing the reason that the message is in an unread state on the first terminal according to the state data; when the reason is that the first terminal causes the error, pushing the message to at least one second terminal, wherein the second terminal and the first terminal are associated with the same user account. Compared with the prior art, the method for pushing the message to one terminal or synchronously pushing the message to a plurality of terminals can reduce the possibility of losing important messages by users according to the actual situation that the users use the terminals, effectively improves the effectiveness of the message pushing function and improves the processing capacity of the message.
Fig. 14 is a system block diagram illustrating an intelligent push message in accordance with an embodiment of the present application. As shown in fig. 14, the system includes: a first terminal 701, a server 702, and at least one second terminal 703.
A first terminal 701, configured to send status data to the server 702 after receiving the message pushed by the server 702 and when the message is in an unread state;
A server 702 for analyzing the reason that the message is in an unread state according to the state data; when the reason is missing, a message is pushed to at least one second terminal, and the second terminal and the first terminal are associated with the same user account.
The server 702 is further configured to generate a revocation instruction, and send the revocation instruction to the first terminal;
The first terminal 701 is further configured to receive a revocation instruction, and delete a message in response to the revocation instruction
A first terminal 701, configured to send status data to the server 702 after receiving the message pushed by the server 702 and when the message is in an unread state on the first terminal 701;
A server 702 for analyzing a cause of the message in an unread state on the first terminal 701 according to the state data;
The server 702 is further configured to push a message to at least one second terminal 703 when the error is caused by the first terminal 701, where the second terminal 703 and the first terminal 701 are associated with the same user account.
Optionally, after the server 702 pushes the message to the at least one second terminal 703, the server 702 is further configured to: generating a withdrawal instruction, and transmitting the withdrawal instruction to the first terminal 701;
The first terminal 701 is further configured to receive a revocation instruction and, in response to the revocation instruction, not to display a message.
In addition, the relevant content in the system embodiment is referred to the method embodiment, and will not be described herein.
In summary, in the system for intelligently pushing messages provided by the embodiment of the application, after a message is pushed to a first terminal, state data sent by the first terminal is received, wherein the state data is data acquired by the first terminal when the message is in an unread state on the first terminal; analyzing the reason that the message is in an unread state on the first terminal according to the state data; when the reason is that the first terminal causes the error, pushing the message to at least one second terminal, wherein the second terminal and the first terminal are associated with the same user account. Compared with the prior art, the method for pushing the message to one terminal or synchronously pushing the message to a plurality of terminals can reduce the possibility of losing important messages by users according to the actual situation that the users use the terminals, effectively improves the effectiveness of the message pushing function and improves the processing capacity of the message.
In addition, in the system for intelligently pushing the message, when the message pushed to the first terminal is not read due to missing, the server sends the withdrawal instruction to the first terminal, so that the temporary storage space of the first terminal is effectively saved, and the display interface is not occupied.
Fig. 15 is a schematic diagram showing a structure of a computer system 900 according to an embodiment of the present application, which includes a Central Processing Unit (CPU) 901, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage section into a Random Access Memory (RAM) 903. In the RAM903, various programs and data required for system operation are also stored. The CPU901, ROM902, and RAM903 are connected to each other through a bus 904. An input/output (I/O) interface 905 is also connected to the bus 904.
The following components are connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, and the like; an output section including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), etc., and a speaker, etc.; a storage portion 908 including a hard disk or the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drives are also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.
In particular, the processes described in the flowcharts according to the embodiments of the present application may be implemented as computer software programs. For example, method embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via a communication portion, and/or installed from a removable medium. The above-described functions defined in the system of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 901.
The computer readable medium shown in the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases. The described units or modules may also be provided in a processor, for example, as: a processor includes a receiving module, an analyzing module, and a pushing module. Wherein the names of the units or modules do not in some cases constitute a limitation of the units or modules themselves.
As another aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to implement the method of intelligent push messaging as described in the above embodiments.
For example, the electronic device may implement the method as shown in fig. 2: step 201, after pushing a message to a first terminal, receiving state data sent by the first terminal, where the state data is data collected by the first terminal when the message is in an unread state on the first terminal. Step 202, analyzing the reason that the message is in the unread state on the first terminal according to the state data. And 203, pushing the message to at least one second terminal when the error is caused by the first terminal, wherein the second terminal and the first terminal are associated with the same user account. As another example, the electronic device may implement the various steps as shown in fig. 3 and 4.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
Furthermore, although the steps of the methods in the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in that particular order, or that all illustrated steps be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware.
In summary, after the intelligent push message is pushed to the first terminal, the computer system or the computer readable medium provided by the embodiment of the application receives the state data sent by the first terminal, where the state data is the data collected by the first terminal when the message is in an unread state on the first terminal; analyzing the reason that the message is in an unread state on the first terminal according to the state data; when the reason is that the first terminal causes the error, pushing the message to at least one second terminal, wherein the second terminal and the first terminal are associated with the same user account. Compared with the prior art, the method for pushing the message to one terminal or synchronously pushing the message to a plurality of terminals can reduce the possibility of losing important messages by users according to the actual situation that the users use the terminals, effectively improves the effectiveness of the message pushing function and improves the processing capacity of the message.
The foregoing description is only illustrative of the principles of the application as it may be embodied in this disclosure. It will be appreciated by persons skilled in the art that the scope of the application is not limited to the specific combinations of the features described above, but also covers other embodiments which may be formed by any combination of the features described above or their equivalents without departing from the spirit of the application. Such as the above-mentioned features and the technical features disclosed in the present application (but not limited to) having similar functions are replaced with each other.
Claims (10)
1. A method for intelligently pushing messages, the method comprising:
After pushing a message to a first terminal, receiving state data sent by the first terminal, wherein the state data is data acquired by the first terminal when the message is in an unread state on the first terminal;
analyzing the reason that the message is in an unread state on the first terminal according to the state data;
When the first terminal is determined to be in a use state according to dynamic data contained in the state data, the contained static data determines that the message is in a folded state or belongs to an unimportant class, and the message is pushed to at least one second terminal when the error caused by the first terminal is determined, wherein the second terminal and the first terminal are associated with the same user account; the second terminal is in an online state; after the message is successfully pushed to at least one second terminal, generating a withdrawal instruction and sending the withdrawal instruction to the first terminal so that the first terminal does not display the message in response to the withdrawal instruction; the static data describes data of the first terminal attribute;
when determining that the user usage behavior comprises at least one of deleting the message behavior, classifying as unimportant behavior and classifying as uninteresting behavior according to the user usage behavior data contained in the state data, determining that the reason that the message is in an unread state on the first terminal is non-missing, and ending the push message operation.
2. The method of intelligent push messaging according to claim 1, wherein the status data comprises a status identification of the first terminal, and wherein the analyzing the reason that the message is in an unread state on the first terminal based on the status data comprises:
Determining whether the first terminal is in an unused state according to the state identifier;
If the first terminal is in an unused state, the cause is determined as a miss caused by the first terminal.
3. The method of intelligent push message according to claim 2, wherein the status data further comprises static data of the first terminal, the static data being data describing attributes of the first terminal, and the method further comprises:
and if the first terminal is in a use state, analyzing the reason that the message is in an unread state on the first terminal according to the static data.
4. A method of intelligent push messaging according to claim 3, wherein said analyzing the cause of the message being in an unread state on the first terminal based on the static data comprises:
searching message folding attributes and message classifying attributes corresponding to the static data in a pre-established strategy library;
When the message folding attribute indicates that the first terminal has a message folding function, the message is in a folded state, and the reason is determined to be the missing caused by the first terminal; or alternatively
And when the first terminal is determined to attribute the message to the unimportant message class according to the message classification attribute, determining the reason as the missing caused by the first terminal.
5. The method of intelligent push messaging according to claim 1, wherein pushing the message to at least one second terminal when the cause is a miss caused by the first terminal comprises:
searching a second terminal in an online state;
Pushing the message to the second terminal.
6. A method for intelligently pushing messages, the method comprising:
after receiving a message pushed by a server, a first terminal sends state data to the server when the message is in an unread state on the first terminal;
the server analyzes the reason that the message is in an unread state on the first terminal according to the state data;
When the first terminal is determined to be in a use state according to dynamic data contained in the state data, the contained static data determines that the message is in a folded state or belongs to an unimportant class, and the server pushes the message to at least one second terminal when determining that the cause is an error caused by the first terminal, wherein the second terminal and the first terminal are associated with the same user account; the second terminal is in an online state; after the message is successfully pushed to at least one second terminal, the server generates a withdrawal instruction and sends the withdrawal instruction to the first terminal; the first terminal receives the withdrawal instruction and responds to the withdrawal instruction without displaying the message; the static data describes data of the first terminal attribute;
when determining that the user usage behavior comprises at least one of deleting the message behavior, classifying as unimportant behavior and classifying as uninteresting behavior according to the user usage behavior data contained in the state data, determining that the reason that the message is in an unread state on the first terminal is non-missing, and ending the push message operation.
7. An apparatus for intelligently pushing messages, the apparatus comprising:
the receiving module is used for receiving state data sent by the first terminal after pushing the message to the first terminal, wherein the state data is data acquired by the first terminal when the message is in an unread state on the first terminal;
the analysis module is used for analyzing the reason that the message is in an unread state on the first terminal according to the state data;
The pushing module is used for pushing the message to at least one second terminal when the first terminal is determined to be in a use state according to dynamic data contained in the state data, the contained static data determines that the message is in a folded state or belongs to an unimportant class, and the message is determined to be missed due to the first terminal, and the second terminal and the first terminal are associated with the same user account; the second terminal is in an online state; after the message is successfully pushed to at least one second terminal, generating a withdrawal instruction and sending the withdrawal instruction to the first terminal so that the first terminal does not display the message in response to the withdrawal instruction; the static data describes data of the first terminal attribute;
when determining that the user usage behavior comprises at least one of deleting the message behavior, classifying as unimportant behavior and classifying as uninteresting behavior according to the user usage behavior data contained in the state data, determining that the reason that the message is in an unread state on the first terminal is non-missing, and ending the push message operation.
8. A system for intelligent push messaging, the system comprising: the system comprises a first terminal, a server and at least one second terminal;
The first terminal is used for sending state data to the server after receiving the message pushed by the server and when the message is in an unread state on the first terminal;
the server is used for analyzing the reason that the message is in an unread state on the first terminal according to the state data;
The server is further configured to push the message to at least one second terminal when the first terminal is determined to be in a use state according to dynamic data included in the state data, the included static data determines that the message is in a folded state or belongs to an unimportant class, and the message is determined to be lost due to the first terminal, and the second terminal and the first terminal are associated with the same user account; the second terminal is in an online state; after the message is successfully pushed to at least one second terminal, the server is further used for generating a withdrawal instruction and sending the withdrawal instruction to the first terminal; the static data describes data of the first terminal attribute;
the first terminal is further configured to receive the withdrawal instruction, and respond to the withdrawal instruction without displaying the message;
The server is further configured to, when determining, according to the user usage behavior data included in the state data, that the user usage behavior includes at least one of a deletion message behavior, a classification as an unimportant behavior, and a classification as an uninteresting behavior, determine that a cause of the message in an unread state on the first terminal is non-missing, and end a push message operation.
9. A computer device, the device comprising:
one or more processors;
A memory for storing one or more programs;
The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-6.
10. A computer-readable storage medium, having stored thereon a computer program for:
the computer program, when executed by a processor, implements the method according to any of claims 1-6.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010076382.1A CN113162958B (en) | 2020-01-23 | 2020-01-23 | Method, device, equipment and storage medium for intelligently pushing message |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010076382.1A CN113162958B (en) | 2020-01-23 | 2020-01-23 | Method, device, equipment and storage medium for intelligently pushing message |
Publications (2)
Publication Number | Publication Date |
---|---|
CN113162958A CN113162958A (en) | 2021-07-23 |
CN113162958B true CN113162958B (en) | 2024-10-18 |
Family
ID=76881935
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010076382.1A Active CN113162958B (en) | 2020-01-23 | 2020-01-23 | Method, device, equipment and storage medium for intelligently pushing message |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN113162958B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114363406B (en) * | 2021-12-10 | 2024-03-26 | 北京达佳互联信息技术有限公司 | Push message processing method, device, equipment and storage medium |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105704307A (en) * | 2016-01-13 | 2016-06-22 | 广东小天才科技有限公司 | Method and system for reminding intelligent terminal message |
CN109088815A (en) * | 2018-08-30 | 2018-12-25 | Oppo广东移动通信有限公司 | Message reminding method and device, storage medium, mobile terminal and wearable device |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104394061B (en) * | 2014-10-31 | 2018-06-19 | 小米科技有限责任公司 | Communication information method for pushing and device |
CN105188037A (en) * | 2015-10-16 | 2015-12-23 | 珠海格力电器股份有限公司 | Message pushing method, mobile terminal and message pushing server |
CN106792578B (en) * | 2015-11-25 | 2020-05-15 | 珠海豹趣科技有限公司 | Event reminding message pushing method and device |
CN106982242A (en) * | 2016-01-19 | 2017-07-25 | 阿里巴巴集团控股有限公司 | The method and device of many registration terminal synchronizing informations |
CN105978971A (en) * | 2016-05-11 | 2016-09-28 | 北京奇虎科技有限公司 | Message pushing method and device, and message pushing server |
CN106330687B (en) * | 2016-10-17 | 2019-09-13 | 腾讯科技(深圳)有限公司 | Message treatment method, apparatus and system |
CN107872380A (en) * | 2017-06-28 | 2018-04-03 | 上海壹账通金融科技有限公司 | Information push method, device and computer-readable recording medium |
CN107483319A (en) * | 2017-07-31 | 2017-12-15 | 广东欧珀移动通信有限公司 | Message sending method, device, storage medium, server and electronic equipment |
CN109039862A (en) * | 2018-07-27 | 2018-12-18 | 努比亚技术有限公司 | Message prompt method, terminal and computer readable storage medium |
CN109067988A (en) * | 2018-08-09 | 2018-12-21 | 珠海格力电器股份有限公司 | Message pushing method and device |
-
2020
- 2020-01-23 CN CN202010076382.1A patent/CN113162958B/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105704307A (en) * | 2016-01-13 | 2016-06-22 | 广东小天才科技有限公司 | Method and system for reminding intelligent terminal message |
CN109088815A (en) * | 2018-08-30 | 2018-12-25 | Oppo广东移动通信有限公司 | Message reminding method and device, storage medium, mobile terminal and wearable device |
Also Published As
Publication number | Publication date |
---|---|
CN113162958A (en) | 2021-07-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10977311B2 (en) | Dynamically modifying elements of user interface based on knowledge graph | |
CN109104620B (en) | Short video recommendation method and device and readable medium | |
KR101830061B1 (en) | Identifying activities using a hybrid user-activity model | |
CN109034993A (en) | Account checking method, equipment, system and computer readable storage medium | |
CN111190888A (en) | Method and device for managing graph database cluster | |
CN107145485B (en) | Method and apparatus for compressing topic models | |
CN111797294A (en) | Visualization method and related equipment | |
CN111352800A (en) | Big data cluster monitoring method and related equipment | |
CN111405030B (en) | Message pushing method and device, electronic equipment and storage medium | |
CN111382228A (en) | Method and apparatus for outputting information | |
CN112860343B (en) | Configuration changing method, system, device, electronic equipment and storage medium | |
CN113988225A (en) | Method and device for establishing representation extraction model, representation extraction and type identification | |
CN115277355A (en) | Method, device, equipment and medium for processing state code data of monitoring system | |
CN113162958B (en) | Method, device, equipment and storage medium for intelligently pushing message | |
Anderson et al. | Architectural Implications of Social Media Analytics in Support of Crisis Informatics Research. | |
CN108809770A (en) | A kind of resource monitoring method and system | |
CN114398343A (en) | Database abnormal key processing method, device, equipment and medium | |
CN110188273B (en) | Information content notification method, device, server and readable medium | |
CN118245285A (en) | Intelligent disaster recovery management and control platform and method for data backup of data center | |
KR102787233B1 (en) | System and method for log monitoring processing based on latent space | |
CN106933449B (en) | Icon processing method and device | |
CN116561402A (en) | Method, device and server for acquiring target content information in webpage | |
CN113704596B (en) | Method and apparatus for generating recall information sets | |
CN115984643A (en) | Model training method, related device and storage medium | |
CN115202643A (en) | Icon resource deleting method and device, electronic equipment and 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: 40049214 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 |