CN113162958A - Method, device and equipment for intelligently pushing message and storage medium - Google Patents
Method, device and equipment for intelligently pushing message and storage medium Download PDFInfo
- Publication number
- CN113162958A CN113162958A CN202010076382.1A CN202010076382A CN113162958A CN 113162958 A CN113162958 A CN 113162958A CN 202010076382 A CN202010076382 A CN 202010076382A CN 113162958 A CN113162958 A CN 113162958A
- Authority
- CN
- China
- Prior art keywords
- terminal
- message
- state
- data
- reason
- 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.)
- Pending
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
Abstract
The application discloses a method, a device, equipment and a storage medium for intelligently pushing messages. The method comprises the following steps: after a message is pushed to a first terminal, receiving state data sent by the first terminal, wherein the state data is data collected by the first terminal when the message is in an unread state on the first terminal; analyzing the reason why the message is in the unread state on the first terminal according to the state data; and when the reason is a mistake caused by the first terminal, the message is pushed to at least one second terminal, and 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 method reduces the possibility that the user misses the important message according to the actual condition that the user uses the terminal, effectively improves the effectiveness of the message pushing function, and improves the message processing capacity.
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 owns a plurality of terminals, for example, a user owns 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 simultaneously. When the server pushes the message to the application program with the same account number, one of the messages is selected as a receiving end of the message to push the message for the receiving end. This push method results in a low probability of the message being read.
Disclosure of Invention
In view of the above, the present application provides a method, an apparatus, a device, and a storage medium for pushing a message intelligently, 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 a message is pushed to a first terminal, receiving state data sent by the first terminal, wherein the state data is data collected by the first terminal when the message is in an unread state on the first terminal;
analyzing the reason why the message is in the unread state on the first terminal according to the state data;
and when the reason is a mistake caused by the first terminal, the message is pushed to at least one second terminal, and 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 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 the unread state on the first terminal according to the state data;
and when the reason is a mistake caused by the first terminal, the server pushes a message 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 intelligently pushing a message, where the apparatus includes:
the receiving module is used for receiving state data sent by the first terminal after the message is pushed to the first terminal, wherein the state data is data collected 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 the 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 reason is a mistake caused by the first terminal, 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 the unread state on the first terminal according to the state data; and when the reason is a mistake caused by the first terminal, the server pushes a message 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 device, 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 that implements the first or second aspects described above.
In a sixth aspect, embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, the computer program being configured to implement the method of the first aspect or the 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 are received, wherein the state data are data collected by the first terminal when the message is in an unread state on the first terminal; analyzing the reason why the message is in the unread state on the first terminal according to the state data; and when the reason is a mistake caused by the first terminal, the message is pushed to at least one second terminal, and 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 the terminal or the terminals synchronously can reduce the possibility that the user misses the important message according to the actual situation that the user uses the terminal, effectively improves the effectiveness of the message pushing function and improves the message processing capacity.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments or the prior art are briefly introduced below, and it is apparent that the drawings are only for the purpose of illustrating a preferred implementation method and are not to be considered as limiting the present application. It should be further noted that, for the convenience of description, only the relevant portions of the present application, not all of them, are shown in the drawings.
Fig. 1 is an architecture diagram of an implementation environment of a method for pushing a message intelligently according to an embodiment of the present application;
fig. 2 is a flowchart illustrating a method for pushing a message intelligently according to an embodiment of the present application;
fig. 3 is a flowchart illustrating another method for pushing a message intelligently according to an embodiment of the present application;
fig. 4 is a flowchart illustrating another method for pushing a message intelligently according to an 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 schematic diagram illustrating a message being collapsed according to an embodiment of the present application;
FIG. 7 is a flow chart illustrating a method for determining a reason why a message was not read according to an embodiment of the present application;
FIG. 8 is a flow chart illustrating yet another method for determining a reason why a message was not read according to an embodiment of the present application;
FIG. 9 is a diagram illustrating a second terminal displaying a message according to an embodiment of the application;
fig. 10 is a schematic diagram illustrating yet another second terminal displaying a 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 illustrating an apparatus for intelligently pushing messages according to an embodiment of the present application;
fig. 13 is a block diagram illustrating another apparatus for intelligently pushing messages according to an embodiment of the present application;
fig. 14 is a block diagram of a system for intelligent push messaging according to an embodiment of the present application;
fig. 15 is a schematic structural diagram of a computer system according to an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant disclosure and are not limiting of the disclosure. It should be noted that, for the convenience of description, only the portions relevant to the application are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 is an architecture diagram of an implementation environment of a method for pushing a message intelligently 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.
The hardware structure of the first terminal 101 and the second terminal 102 includes a processor, a memory, and a display device, and the software structure includes a client of an application installed on the first terminal or the second terminal. Wherein, the client can receive one or more messages pushed by the server.
The first terminal 101 and the second terminal 102 may be terminals that receive a first push message from a server, or terminals that receive a message to be synchronized twice. For example, the first terminal is a terminal that first receives a pushed message from the server, 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.
The 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, and the like, which is not particularly limited in this 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 that 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 reason that the unread message is wrong.
The server 102 may be a server, a server cluster composed of 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 for pushing the message may be executed by the first terminal 101 and the server 103 cooperatively, or may be executed by the first terminal 101 alone.
Fig. 2 is a flowchart illustrating a method for pushing a message intelligently 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, the method comprising the steps of:
The reason why the message is in the unread state on the first terminal is analyzed according to the state data, step 202.
In the above steps, the reason why 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.
The Artificial Intelligence (AI) is a theory, a method, a technology and an application system which simulate, extend and expand human Intelligence by using a digital computer or a machine controlled by the digital computer, sense the environment, acquire knowledge and use the knowledge to acquire an optimal result. In other words, artificial intelligence is a comprehensive technique of computer science that attempts to understand the essence of intelligence and produce a new intelligent machine that can react in a manner similar to human intelligence. Artificial intelligence is the research of the design principle and the realization method of various intelligent machines, so that the machines have the functions of perception, reasoning and decision making.
The artificial intelligence technology is a comprehensive subject and relates to the field of extensive technology, namely the technology of a hardware level and the technology of a software level. The artificial intelligence infrastructure generally includes 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 the like.
Machine Learning (ML for short in the whole English process) is a multi-field cross subject, and relates to multiple subjects such as probability theory, statistics, approximation theory, convex analysis, algorithm complexity theory and the like. The special research on how a computer simulates or realizes the learning behavior of human beings so as to acquire new knowledge or skills and reorganize the existing knowledge structure to continuously improve the performance of the computer. Machine learning is the core of artificial intelligence, is the fundamental approach for computers to have intelligence, and is applied to all fields of artificial intelligence. Machine learning and deep learning generally include techniques such as artificial neural networks, belief networks, reinforcement learning, transfer learning, inductive learning, and formal education learning.
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 that the reason that the message is in the unread state is identified, and then the message is pushed to other terminal devices associated with the user account again according to the reason.
Or searching the terminal equipment with higher user use frequency from the plurality of terminal equipment by using an artificial intelligence algorithm to serve as the receiving end of the synchronous message.
To sum up, the method for intelligently pushing a message provided by the embodiment of the application receives state data sent by a first terminal after the message is pushed to the first terminal, wherein the state data is data collected by the first terminal when the message is in an unread state on the first terminal; analyzing the reason why the message is in the unread state on the first terminal according to the state data; and when the reason is a mistake caused by the first terminal, the message is pushed to at least one second terminal, and 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 the terminal or the terminals synchronously can reduce the possibility that the user misses the important message according to the actual situation that the user uses the terminal, effectively improves the effectiveness of the message pushing function and improves the message processing capacity.
Fig. 3 is a flowchart illustrating another method for pushing a message intelligently 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, the method comprising the steps of:
The state data is obtained by the first terminal by collecting the relevant data of the equipment state when the message is in an unread state on the first terminal.
Further, after receiving the state data, the server analyzes the reason that the message is in the unread state on the first terminal according to the state data, and when the reason is a mistake caused by the first terminal, the server generates a message withdrawal instruction and sends the message withdrawal instruction to the first terminal.
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 a miss, the server sends the withdrawal instruction to the first terminal, so that the temporary storage space of the first terminal is effectively saved, and a display interface is not occupied.
Fig. 4 is a flowchart illustrating another method for pushing a message intelligently according to an 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, and as shown in fig. 4, the method includes the following steps:
step 401, after the first terminal receives the message pushed by the server, and when the message is in an unread state on the first terminal, the first terminal collects state data.
Wherein the pushed message is sent by the server, and 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 server corresponding to the QQ browser and the nail, the server corresponding to the two applications all push messages to the first terminal, the message a is pushed by the server of the QQ browser, the push content is "snowfall" for transwar "local snowfall in northeast and northwest region", the message B is pushed by the nail server, and the push content is "you have an exception in the last week attendance record, please handle 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 be detected according to preset time.
Optionally, monitoring whether the message is read in real time may be performed by obtaining the message reading status identifier multiple times. Wherein the message reading state identification indicates whether the pushed message is read or not. For example, the message reading status flag includes 0 and 1, where 0 indicates that the message is read, and 1 indicates that the message is not read, it is determined that the message is read when the acquired message status flag is 0, and if the acquired message status flag is 1, it indicates that the message is not read.
The state data is data describing the self state of the first terminal, and further includes dynamic data.
Dynamic data is data that is not fixed and constant, and the data may change at different times. For example, the charging status flag may include 0 and 1, where 0 indicates charging and 1 indicates non-charging, and the value of the charging status flag is 0 when the first terminal is in the charging status and 1 when the first terminal is in the non-charging status. Further, the state identifier may also be a sleep state identifier, a screen locking state identifier, an operated state identifier, or the like.
The dormant state can be understood as a terminal screen processing black screen state, that is, the terminal is not operated by a user temporarily, and the screen locking state is a terminal screen in a bright screen and locked state. Further, the relationship between the sleep mode and the screen locking mode is as follows: when the terminal is in the dormant state, the dormant state of the terminal can be changed into the screen locking state through a preset triggering mode, and further, after the screen in the screen locking state is unlocked, operation (the operated state identifier is used for indicating that the first terminal is currently operated) can be executed on the screen, for example, information reading, video watching and the like.
Illustratively, the sleep state flag, the lock screen state flag, and the charge state flag each include 0 and 1. Further, the relationship between each state identifier and the screen state is as follows:
and (3) sleep state identification: 0 dormant, 1 not dormant
Screen locking state identification: 0 lock screen, 1 unlock screen
And (3) charging state identification: in 0 charging, 1 is not charged
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 time period to determine whether the dynamic data is changing. The first preset time period is any time period determined according to actual needs, such as 5 minutes, 10 minutes and the like.
Illustratively, the dynamic data acquired in the first preset time period is always:
and (3) sleep state identification: 0
Screen locking state identification: 0
And (3) charging state identification: 0
Optionally, the status data further includes static data, where the static data is relatively fixed and unchangeable data, such as data for describing attributes of the terminal, for example, 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 a first terminal identifier, a ROM version, and a first terminal system version identifier, the obtained static data is:
and (3) terminal identification: a. the
Version of ROM: b01
The 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 classification 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 trigger operation is executed, the folded message can be displayed. For example, referring to fig. 6, the terminal has a message folding function, the QQ browser pushes 5 messages in total, but only one pushed message is shown in the terminal, the other 4 messages are folded, and when a downward arrow is clicked, the other 4 messages which are folded are displayed. The message classification function classifies the message as received by the first terminal, for example, as important or unimportant.
Optionally, the status data further comprises user usage behavior data, wherein the usage behavior data comprises usage behavior identifiers, such as a delete identifier, a classified insignificant identifier; the usage behavior may include, among other things, a delete message behavior, a classification as an unimportant behavior, a classification as an uninteresting behavior, and so on. Further, the user inputs a deletion instruction, a classification as an unimportant instruction or a classification as a disinterest instruction through the display interface, and the first terminal directly deletes the pushed message according to the received instruction, so that the message is classified as unimportant or disinterest.
Here, when it is to be noted that the classification is not important is a classification operation performed by the user himself, and unlike the message classification function mentioned in the static data, the message classification function in the static data is a 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 acquires the state data of the first terminal when monitoring that the unread message exists.
When the first terminal receives the message, the user may be performing other operations using the first terminal without having to read the message, and thus, when the first terminal receives the message, it is not immediately determined whether the message is read, but it is determined whether the message is read after a second preset time period. Therefore, optionally, step 401 may also be: when the first terminal receives the pushed message, waiting for a second preset time period; judging whether the pushed message is read or not after a second preset time period; when not being read, the state data of the user is collected.
The second preset time period may be any time period determined as required, for example, 5 minutes, 10 minutes, and the like.
Step 402, the first terminal sends the state data to the server.
At step 403, the server receives status data.
The server analyzes the reason the message is in an unread state based on the state data, step 404.
Alternatively, referring to fig. 7, when the status data received by the server is the dynamic data of the first terminal, the dynamic data may be the status identifier.
The state identifier may be a sleep state identifier, a charging state identifier, a screen locking state identifier, or the like.
When the state data is a state identification, step 404 includes:
Alternatively,
when the state identifier is the dormant state identifier, determining whether the first terminal is in an unused state according to the dynamic data, including:
and when the sleep state identification indicates that the first terminal is in the sleep state, determining that the first terminal is in the unused state. Alternatively, the first and second electrodes may be,
when the state identifier is the charging state identifier and the screen locking state identifier, determining whether the first terminal is in an unused state according to the state identifier comprises:
when the screen locking state identification shows that the first terminal is in a screen locking state, determining that the first terminal is in an unused state; alternatively, the first and second electrodes may be,
and when the charging state identifier indicates that the first terminal is in the charging state and the screen locking state identifier indicates that the first terminal is in the screen locking state, determining that the first terminal is in the unused state.
Optionally, when the dynamic data includes three identifiers, namely a sleep status identifier, a lock screen status identifier, and a charging status identifier, step 4041 includes:
step one, determining whether a dormant state identifier indicates that a first terminal is in a dormant state;
step two, when the sleep state identification is determined to represent that the first terminal is in the sleep state, determining that the first terminal is in the unused state, or,
and when the sleep state identification indicates that the first terminal is in the non-sleep state, determining whether the screen locking state identification and the charging state identification indicate that the first terminal is in the charging and screen locking state.
Step three, when the screen locking state mark and the charging state mark indicate that the first terminal is in the charging and screen locking state, determining that the first terminal is in the 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 a non-screen locking state, determining that the first terminal is in a used state.
Optionally, when the dynamic data received by the server includes the operation state identifier, and when the operation state identifier indicates that the first terminal is being operated, it is directly determined 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 to be a miss.
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. The behavior habit of the user can be identified more accurately. Furthermore, 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 comprises static data, referring to fig. 8, before step 4043, the method further comprises:
Optionally, determining from the static data whether the message is in a collapsed state or belongs to an unimportant message category comprises:
searching a message folding attribute and a message classification attribute 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; alternatively, the first and second electrodes may be,
when the message classification attribute indicates that the message classification attribute is present, determining that the message belongs to an unimportant message class.
Optionally, when the static data includes a terminal identifier, a read-only memory identifier, and an operating system identifier; determining whether the message is collapsed or classified as unimportant based on the static data includes:
firstly, searching a message folding attribute and a message classification attribute corresponding to a terminal identifier, a read-only memory identifier and an operating system identifier in a pre-established strategy library;
when the searched message folding attribute and the searched message classification attribute indicate that the message folding function or the message classification function is at least one, determining that the message is in a folded state or belongs to an unimportant message category; alternatively, the first and second electrodes may be,
and thirdly, when the searched message folding attribute and the searched message classification attribute indicate that the message folding function is not provided and the message classification function is not provided, determining that the message is in an unfolded state and belongs to the unimportant message category.
The strategy 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 result obtained by analysis.
Illustratively, the policy repository includes the following:
and (3) terminal identification: a. the
Version of ROM: b01
The first terminal system version identification: c01
Message folding attribute: supporting folding
Message classification attributes: supporting categorization
And (3) terminal identification: b is
Version of ROM: c01
The first terminal system version identification: d01
Message folding attribute: without message folding function
Message classification attributes: without message classification function
Further, illustratively, the obtained static data is:
and (3) terminal identification: a. the
Version of ROM: b01
The first terminal system version identification: c01
And finding out that the message folding attribute is with the message folding function and the message classification attribute is with the message classification function from the strategy library. Determining that the message folding attribute corresponding to the static data is a message folding attribute, and the message classification attribute is a message classification function.
If it is determined that the message is in an unfolded state and does not belong to the unimportant category, the reason that the message is in an unread state is determined to be non-missing, step 4046.
Optionally, static data may be selected and then dynamic data may be used to determine the reason why the message is not read, which is not limited in the embodiment of the present application and the specific process is not described in detail.
Alternatively, when the status data received by the server includes the user usage behavior data, it may be determined whether the reason why the message is not read is a miss according to the user usage behavior identifier. When the reason that the message is not read is judged to be non-missing according to the user usage behavior data, for example, when the reason that the message is not read is judged to be non-missing according to the deletion identifier, the classification as the unimportant identifier and the classification as the uninteresting identifier, the user usage behavior comprises at least one of the actions of deleting the message, the classification as the unimportant behavior and the classification as the uninteresting behavior, and then the server directly determines that the reason that the message is not read is non-missing.
And step 405, when the reason is wrong, 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 online, further, the second terminal is a terminal whose online time is the latest, or the second terminal may also be a terminal which is currently online and has the highest probability of reading a message, or the second terminal is a terminal which is currently being used and has the highest probability.
Further, the probability of being currently used and the probability of the message being read can be derived from statistical analysis of the data. Therefore, the terminal for receiving the message can be ensured to be an online terminal, so that the probability of the user seeing the message is improved, and the probability of the message being read is improved; and only push to a terminal, can also reduce and push repeatedly, thus reduce the server pressure, and save the trouble that users see the message repeatedly.
Further, the second terminal is a terminal in a server terminal list, where the terminal list includes all terminals associated with the user account, and identifies the online status of each terminal. Illustratively, for a certain user, the corresponding terminal list is as follows:
and (3) user identification: 0000001
And (3) terminal identification: 00001; and (3) online state: on-line
And (3) terminal identification: 00002; and (3) online state: on-line
And (3) terminal identification: 00003; and (3) online state: out of line
Optionally, step 405 comprises: when the reason that the reading is not carried out is wrong, searching the terminal in the online state in the terminal list to serve as a second terminal; and pushing the message to the second terminal of the searched online state.
In addition, when the reason that the message is not read is non-missing, for example, the user is not interested in, the server does not push the message to other terminals.
And 406, the second terminal receives and displays the message.
Optionally, referring to fig. 9, when the second terminal receives the message, the message is displayed on the screen in a reminding manner, for example, in fig. 9, only "a QQ browser and a new message is pinned" is displayed on the display interface of the second terminal, so that the user can determine whether to read the pushed message according to the need of the user.
Alternatively, referring to fig. 10, when the second terminal receives the message, the summary of the message may also be displayed on the screen, so that the user may visually see the content of the summary, and thus the user may determine whether to read the message according to the name of the application program, and may also determine whether to read the push message according to the summary.
Optionally, still referring to fig. 4, before step 405, the method for pushing a message intelligently further includes steps 407 to 409:
in step 407, when the reason for the unread status is wrong, the server generates a withdrawal instruction.
In step 408, the server sends the revocation instruction to the first terminal.
In step 409, the first terminal responds to the withdrawal instruction without displaying a message.
Referring to fig. 11, the first terminal not displaying the message may be deleting 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 within the display interface of the first terminal to remind the user that the first terminal has withdrawn one push message.
Illustratively, when the first terminal revokes a message of the application a, the revocation alert may be "revoke a message of the application a".
Further, when the withdrawal reminder is generated, a re-forwarding reminder may also be generated to remind the user that the withdrawn message has been pushed to the second terminal again.
Illustratively, when the terminal of the second terminal is identified as a02, the push reminder again may be "one message for application a was revoked, and the revoked message has already been pushed to the terminal identified as a 02".
Optionally, after step 405, steps 407 to 409 may be executed to perform the withdrawal 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, the message of the first terminal does not need to be pushed again because the message of the first terminal has not been withdrawn yet.
Further, when the message is not read after being pushed to the second terminal, the above steps 401 to 409 may be repeated to increase the probability that the message is read.
To sum up, the method for intelligently pushing a message provided by the embodiment of the application receives state data sent by a first terminal after the message is pushed to the first terminal, wherein the state data is data collected by the first terminal when the message is in an unread state on the first terminal; analyzing the reason why the message is in the unread state on the first terminal according to the state data; and when the reason is a mistake caused by the first terminal, the message is pushed to at least one second terminal, and 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 the terminal or the terminals synchronously can reduce the possibility that the user misses the important message according to the actual situation that the user uses the terminal, effectively improves the effectiveness of the message pushing function and improves the message processing capacity.
In addition, 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 a miss, the server sends a withdrawal instruction to the first terminal, so that the temporary storage space of the first terminal is effectively saved, and a display interface is not occupied.
The embodiments in this specification are described in a progressive manner, and similar parts between the various embodiments are referred to each other. The examples below each step focus on the specific method below that step. The above-described embodiments are merely illustrative, and the specific examples are only illustrative of the present application, and those skilled in the art can make several improvements and modifications without departing from the principle described in the examples of the present application, and these improvements should be construed as the scope of the present application.
Fig. 12 is a block diagram illustrating an apparatus for intelligently pushing messages according to an embodiment of the present application.
As shown in fig. 12, the apparatus includes:
the receiving module 601 is configured to receive status data sent by a first terminal after a message is pushed to the first terminal, where the status 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 reason why the message is in an unread status on the first terminal;
the pushing module 603 is configured to, when the cause is a failure caused by the first terminal, push the message to at least one second 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 identifier;
if the first terminal is in an unused state, the cause is determined to be a miss by the first terminal.
Optionally, when the state identifier includes a sleep state identifier, the analysis module 602 is further configured to:
when the dormant state identifier indicates that the first terminal is in a dormant state, determining that the first terminal is in an unused state; alternatively, the first and second electrodes may be,
when the state identifier includes the charging state identifier and the 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 identification shows that the first terminal is in a screen locking state, determining that the first terminal is in an unused state; alternatively, the first and second electrodes may be,
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; alternatively, the first and second electrodes may be,
when the state identifier includes the sleep state identifier, the charging state identifier and the screen locking state identifier, determining whether the first terminal is in an unused state according to the state identifier, including:
reading a screen locking state identifier and a charging state identifier when the sleep state identifier indicates that the first terminal is in an un-sleep state;
and when the screen locking state identification shows that the first terminal is in the screen locking state and the charged state identification shows that the first terminal is in the charged state, determining that the first terminal is in the unused state.
Optionally, the status data further includes static data of the first terminal, and the static data is data for describing attributes of the first terminal, then the analysis module 602 is further configured to:
if the first terminal is in the use state, the reason why the message is in the unread state on the first terminal is analyzed according to the static data.
Optionally, the analysis module 602 is further configured to:
searching a message folding attribute and a message classification attribute 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 error caused by the first terminal; alternatively, the first and second electrodes may be,
and when the message is determined to belong to the unimportant message category according to the message classification attribute, determining the reason to be the error caused by the first terminal.
Optionally, referring to fig. 13, the smart push messaging device further includes:
the generating module 604 is configured to generate a withdrawal instruction after the message is pushed 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 obtained by searching in a terminal list, where the terminal list includes all terminals associated with the user account, and the pushing module 603 is further configured to:
searching a second terminal in an online state;
and pushing the message to the second terminal.
In addition, please refer to the method embodiment for related contents in the device embodiment, which are not described herein again.
To sum up, the device for intelligently pushing messages provided in the embodiment of the present application receives state data sent by a first terminal after pushing a message to 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; analyzing the reason why the message is in the unread state on the first terminal according to the state data; and when the reason is a mistake caused by the first terminal, the message is pushed to at least one second terminal, and 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 the terminal or the terminals synchronously can reduce the possibility that the user misses the important message according to the actual situation that the user uses the terminal, effectively improves the effectiveness of the message pushing function and improves the message processing capacity.
Fig. 14 is a system block diagram illustrating an intelligent push message according to 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.
The first terminal 701 is 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 status;
the server 702 is used for analyzing the reason that the message is in the unread state according to the state data; and when the reason is wrong, pushing a message to at least one second terminal, wherein the second terminal and the first terminal are associated with the same user account.
The server 702 is further configured to generate a withdrawal instruction, and send the withdrawal instruction to the first terminal;
the first terminal 701 is further configured to receive a revocation instruction and, in response to the revocation instruction, delete the message
The first terminal 701 is 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 status on the first terminal 701;
a server 702, configured to analyze, according to the status data, a reason why the message is in an unread status on the first terminal 701;
the server 702 is further configured to push a message to at least one second terminal 703 when the cause is a mistake 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 sending the withdrawal instruction to the first terminal 701;
the first terminal 701 is further arranged to receive a revocation instruction and, in response to the revocation instruction, not display a message.
In addition, please refer to the method embodiment for related contents in the system embodiment, which are not described herein.
To sum up, the system for intelligently pushing messages receives state data sent by a first terminal after the messages are pushed to the first terminal, wherein the state data is data collected by the first terminal when the messages are in an unread state on the first terminal; analyzing the reason why the message is in the unread state on the first terminal according to the state data; and when the reason is a mistake caused by the first terminal, the message is pushed to at least one second terminal, and 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 the terminal or the terminals synchronously can reduce the possibility that the user misses the important message according to the actual situation that the user uses the terminal, effectively improves the effectiveness of the message pushing function and improves the message processing capacity.
In addition, according to the system 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 a miss, the server sends a withdrawal instruction to the first terminal, so that the temporary storage space of the first terminal is effectively saved, and a display interface is not occupied.
Fig. 15 is a schematic structural diagram of a computer system 900 according to an embodiment of the present application, which includes a Central Processing Unit (CPU)901 that can execute various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage portion into a Random Access Memory (RAM) 903. In the RAM903, various programs and data necessary for system operation are also stored. The CPU901, ROM902, and RAM903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.
The following components are connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and 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 mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.
In particular, the processes described by 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 illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section, and/or installed from a removable medium. The above-described functions defined in the system of the present application are executed when the computer program is executed by a Central Processing Unit (CPU) 901.
It should be noted that 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. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination 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 present application, 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 this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. 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 flowchart 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 described 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 disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves. The described units or modules may also be provided in a processor, and may be described as: a processor includes a receiving module, an analyzing module, and a pushing module. Wherein the designation of a unit or module does not in some way constitute a limitation of the unit or module itself.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs, which when executed by an electronic device, cause the electronic device to implement the method for pushing messages intelligently as described in the above embodiments.
For example, the electronic device may implement the following as shown in fig. 2: step 201, after pushing a message to a first terminal, receiving status data sent by the first terminal, where the status data is data collected by the first terminal when the message is in an unread state on the first terminal. The reason why the message is in the unread state on the first terminal is analyzed according to the state data, step 202. Step 203, when the reason is a mistake caused by the first terminal, pushing the message to at least one second 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 shown in fig. 3 and 4.
It should be noted that although in the above detailed description several modules or units of the 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, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware.
To sum up, the computer system or the computer-readable medium for intelligently pushing a message provided in the embodiment of the present application receives status data sent by a first terminal after the message is pushed to the first terminal, where the status data is data collected by the first terminal when the message is in an unread state on the first terminal; analyzing the reason why the message is in the unread state on the first terminal according to the state data; and when the reason is a mistake caused by the first terminal, the message is pushed to at least one second terminal, and 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 the terminal or the terminals synchronously can reduce the possibility that the user misses the important message according to the actual situation that the user uses the terminal, effectively improves the effectiveness of the message pushing function and improves the message processing capacity.
The foregoing is considered as illustrative only of the preferred embodiments of the invention and illustrative only of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the application referred to in the present application is not limited to the embodiments with a particular combination of the above-mentioned features, but also encompasses other embodiments with any combination of the above-mentioned features or their equivalents without departing from the scope of the application. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (12)
1. A method for pushing a message intelligently, the method comprising:
after a message is pushed to a first terminal, receiving state data sent by the first terminal, wherein the state data is data collected by the first terminal when the message is in an unread state on the first terminal;
analyzing the reason why the message is in an unread state on the first terminal according to the state data;
and when the reason is a mistake caused by the first terminal, pushing the message to at least one second terminal, wherein the second terminal and the first terminal are associated with the same user account.
2. The method according to claim 1, wherein the status data includes a status identifier of the first terminal, and the analyzing the reason why the message is in an unread status on the first terminal according to the status data includes:
determining whether the first terminal is in an unused state according to the state identifier;
the cause is determined to be a miss by the first terminal if the first terminal is in an unused state.
3. The method of intelligently pushing messages according to claim 2, wherein the status data further includes static data of the first terminal, the static data being data for describing attributes of the first terminal, the method further comprising:
and if the first terminal is in a use state, analyzing the reason why the message is in an unread state on the first terminal according to the static data.
4. The method according to claim 3, wherein the analyzing the reason why the message is in the unread state on the first terminal according to the static data comprises:
searching a message folding attribute and a message classification attribute 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 a miss caused by the first terminal; alternatively, the first and second electrodes may be,
and when the first terminal determines that the message belongs to the unimportant message category according to the message classification attribute, determining the reason as the miss caused by the first terminal.
5. The method for pushing messages intelligently as claimed in any one of claims 1-4, wherein after said pushing the message to at least one second terminal, the method further comprises:
and 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.
6. The method for intelligently pushing a message according to claim 1, wherein the pushing the message to at least one second terminal when the reason is a failure caused by the first terminal comprises:
searching a second terminal in an online state;
and pushing the message to the second terminal.
7. A method for pushing a message intelligently, the method comprising:
the method comprises the steps that after a first terminal receives a message pushed by a server, and when the message is in an unread state on the first terminal, state data are sent to the server;
the server analyzes the reason that the message is in the unread state on the first terminal according to the state data;
and when the reason is a mistake caused by the first terminal, the server pushes the message to at least one second terminal, and the second terminal and the first terminal are associated with the same user account.
8. The method of intelligently pushing messages as claimed in claim 7, wherein after the server pushes the message to at least one second terminal, the method further comprises:
the server generates a withdrawal instruction and sends the withdrawal instruction to the first terminal;
the first terminal receives the withdrawal instruction and, in response to the withdrawal instruction, does not display the message.
9. An apparatus for intelligently pushing messages, the apparatus comprising:
the receiving module is used for receiving state data sent by a first terminal after a message is pushed to the first terminal, wherein the state data is data collected 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 the 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 reason is a mistake caused by the first terminal, and the second terminal and the first terminal are associated with the same user account.
10. A system for intelligently pushing messages, 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 the 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 cause is a mistake caused by the first terminal, where the second terminal and the first terminal are associated with the same user account.
11. 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-8.
12. A computer-readable storage medium, having stored thereon a computer program for:
the computer program, when executed by a processor, implements the method of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010076382.1A CN113162958A (en) | 2020-01-23 | 2020-01-23 | Method, device and equipment for intelligently pushing message and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010076382.1A CN113162958A (en) | 2020-01-23 | 2020-01-23 | Method, device and equipment for intelligently pushing message and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113162958A true CN113162958A (en) | 2021-07-23 |
Family
ID=76881935
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010076382.1A Pending CN113162958A (en) | 2020-01-23 | 2020-01-23 | Method, device and equipment for intelligently pushing message and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113162958A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114363406A (en) * | 2021-12-10 | 2022-04-15 | 北京达佳互联信息技术有限公司 | Push message processing method, device, equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104394061A (en) * | 2014-10-31 | 2015-03-04 | 小米科技有限责任公司 | Communication message pushing method and device |
| CN105704307A (en) * | 2016-01-13 | 2016-06-22 | 广东小天才科技有限公司 | Intelligent terminal message prompting method and system thereof |
| CN106330687A (en) * | 2016-10-17 | 2017-01-11 | 腾讯科技（深圳）有限公司 | Information processing method, device and system |
| CN106792578A (en) * | 2015-11-25 | 2017-05-31 | 珠海市君天电子科技有限公司 | 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 |
| CN107483319A (en) * | 2017-07-31 | 2017-12-15 | 广东欧珀移动通信有限公司 | Message method, device, storage medium, server and electronic equipment |
| CN109088815A (en) * | 2018-08-30 | 2018-12-25 | Oppo广东移动通信有限公司 | Message prompt method, device, storage medium, mobile terminal and wearable device |
-
2020
- 2020-01-23 CN CN202010076382.1A patent/CN113162958A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104394061A (en) * | 2014-10-31 | 2015-03-04 | 小米科技有限责任公司 | Communication message pushing method and device |
| CN106792578A (en) * | 2015-11-25 | 2017-05-31 | 珠海市君天电子科技有限公司 | Event reminding message pushing method and device |
| CN105704307A (en) * | 2016-01-13 | 2016-06-22 | 广东小天才科技有限公司 | Intelligent terminal message prompting method and system thereof |
| CN106982242A (en) * | 2016-01-19 | 2017-07-25 | 阿里巴巴集团控股有限公司 | The method and device of many registration terminal synchronizing informations |
| CN106330687A (en) * | 2016-10-17 | 2017-01-11 | 腾讯科技（深圳）有限公司 | Information processing method, device and system |
| CN107483319A (en) * | 2017-07-31 | 2017-12-15 | 广东欧珀移动通信有限公司 | Message method, device, storage medium, server and electronic equipment |
| CN109088815A (en) * | 2018-08-30 | 2018-12-25 | Oppo广东移动通信有限公司 | Message prompt method, device, storage medium, mobile terminal and wearable device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114363406A (en) * | 2021-12-10 | 2022-04-15 | 北京达佳互联信息技术有限公司 | Push message processing method, device, equipment and storage medium |
| CN114363406B (en) * | 2021-12-10 | 2024-03-26 | 北京达佳互联信息技术有限公司 | Push message processing method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3244312A1 (en) | A personal digital assistant | |
| CN110347716B (en) | Log data processing method, device, terminal equipment and storage medium | |
| KR101830061B1 (en) | Identifying activities using a hybrid user-activity model | |
| CN111190888A (en) | Method and device for managing graph database cluster | |
| 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 | |
| CN115269877A (en) | Method, system and equipment for constructing domain entity and event double-center knowledge graph | |
| CN114625597A (en) | Monitoring operation and maintenance system, method and device, electronic equipment and storage medium | |
| CN114091704B (en) | Alarm suppression method and device | |
| Anderson et al. | Architectural Implications of Social Media Analytics in Support of Crisis Informatics Research. | |
| CN113162958A (en) | Method, device and equipment for intelligently pushing message and storage medium | |
| CN114461792A (en) | Alarm event correlation method, device, electronic equipment, medium and program product | |
| CN116756616A (en) | Data processing method, device, computer readable medium and electronic equipment | |
| CN111145907A (en) | Physical examination data processing method, physical examination data processing device, physical examination data processing medium and electronic equipment | |
| CN106933449B (en) | Icon processing method and device | |
| CN115202643A (en) | Icon resource deleting method and device, electronic equipment and medium | |
| CN115277355A (en) | Method, device, equipment and medium for processing state code data of monitoring system | |
| CN111612280B (en) | Data analysis method and device | |
| CN110188273B (en) | Information content notification method, device, server and readable medium | |
| CN113282455A (en) | Monitoring processing method and device | |
| Merzougui | Adaptation of an intelligent mobile assistant medical (IMAM) of the heterogeneous data for the telemedicine services: Design and implementation | |
| CN113449230A (en) | Method and system for determining exposure element, client and server | |
| CN112417259A (en) | Media resource processing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40049214 Country of ref document: HK |
|
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |