CN114443160A - Message pushing method and device, electronic equipment and storage medium - Google Patents

Message pushing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN114443160A
CN114443160A CN202111674458.1A CN202111674458A CN114443160A CN 114443160 A CN114443160 A CN 114443160A CN 202111674458 A CN202111674458 A CN 202111674458A CN 114443160 A CN114443160 A CN 114443160A
Authority
CN
China
Prior art keywords
target task
message
session
change notification
notification message
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
Application number
CN202111674458.1A
Other languages
Chinese (zh)
Inventor
贺勇
魏哲鹏
陈荣
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Dajia Internet Information Technology Co Ltd
Original Assignee
Beijing Dajia Internet Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Dajia Internet Information Technology Co Ltd filed Critical Beijing Dajia Internet Information Technology Co Ltd
Priority to CN202111674458.1A priority Critical patent/CN114443160A/en
Publication of CN114443160A publication Critical patent/CN114443160A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44505Configuring for program initiating, e.g. using registry, configuration files
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/542Event management; Broadcasting; Multicasting; Notifications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/54Indexing scheme relating to G06F9/54
    • G06F2209/547Messaging middleware

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The present disclosure relates to a message pushing method, device, electronic device and storage medium, including: responding to the change of the target task, and generating a change notification message of the target task; and under the condition that the change notification message is matched with the preset message type of the target task, pushing the change notification message to the session address associated with the target task, so that the client corresponding to the session address associated with the target task displays the change notification message. Therefore, when the target task changes, the session address associated with the target task is pushed only under the condition that the change notification message is matched with the preset message type of the target task, the client of each user only receives the notification message of the preset message type of the target task, and the probability that the user receives useless notification messages can be reduced through setting the preset message type, so that the density of the user receiving effective messages is improved.

Description

Message pushing method and device, electronic equipment and storage medium
Technical Field
The present disclosure relates to the field of internet, and in particular, to a method and an apparatus for pushing a message, an electronic device, and a storage medium.
Background
Through the association between the IM (Instant Messaging) software and the task management software, the notification message in the task management software can be sent in the IM software.
In the prior art, the IM software has a single rule for pushing notification messages, for example, when the state of a certain task changes, a corresponding notification message is generated, and then the state notification message is pushed to all clients related to the task. For example, if a task is deferred, all clients associated with the task receive notification messages that the task is deferred.
However, in an actual working scenario, different users may be responsible for different parts of a task, and if all notification messages of a task are pushed to all clients related to the task, each user may receive many useless notification messages, which is a disturbance to the user, and at the same time, the density of valid messages received by the user is also reduced.
Disclosure of Invention
The present disclosure provides a message pushing method, device, electronic device and storage medium, to at least solve the problem in the related art that each user receives many useless notification messages, and the density of receiving effective messages by the user is reduced. The technical scheme of the disclosure is as follows:
according to a first aspect of the embodiments of the present disclosure, a message pushing method is provided, including:
generating a change notification message of a target task in response to a change of the target task;
and under the condition that the change notification message is matched with the preset message type of the target task, pushing the change notification message to the session address associated with the target task, so that the client corresponding to the session address associated with the target task displays the change notification message.
Optionally, the method further includes:
and responding to the configuration instruction of the target task, and determining the preset message type of the target task and the session address associated with the target task.
Optionally, the determining, in response to the configuration instruction for the target task, a preset message type of the target task includes:
displaying a first configuration page of the target task, wherein the first configuration page comprises a plurality of message types;
and in response to the selection operation of any one or more message types in the first configuration page, determining the selected message type as a preset message type of the target task.
Optionally, the determining, in response to the configuration instruction for the target task, a session address associated with the target task includes:
calling a preset communication interface, and displaying at least one candidate session on a second configuration page;
and in response to the selection operation of any candidate session on the second configuration page, determining the session address of the selected candidate session as the session address associated with the target task.
Optionally, the determining, in response to the selection operation of any candidate session on the second configuration page, a session address of the selected candidate session as the session address associated with the target task includes: :
and in response to the selection operation of any candidate session on the second configuration page, creating a session object in any candidate session, recording a callback address of the session object, and determining the callback address of the session object as the session address associated with the target task.
According to a second aspect of the embodiments of the present disclosure, there is provided a message pushing apparatus, including:
a generation unit configured to perform a change notification message in response to a change of a target task, the change notification message of the target task being generated;
the pushing unit is configured to push the change notification message to a session address associated with the target task under the condition that the change notification message is matched with a preset message type of the target task, so that a client corresponding to the session address associated with the target task displays the change notification message.
Optionally, the apparatus further comprises:
the configuration unit is configured to execute a configuration instruction responding to the target task, and determine a preset message type of the target task and a session address associated with the target task.
Optionally, the configuration unit is specifically configured to perform:
displaying a first configuration page of the target task, wherein the first configuration page comprises a plurality of message types;
and in response to the selection operation of any one or more message types in the first configuration page, determining the selected message type as a preset message type of the target task.
Optionally, the configuration unit is specifically configured to perform:
calling a preset communication interface, and displaying at least one candidate session on a second configuration page;
and in response to the selection operation of any candidate session in the second configuration page, determining the session address of the selected candidate session as the session address associated with the target task.
Optionally, the configuration unit is specifically configured to perform:
and in response to the selection operation of any candidate session on the second configuration page, creating a session object in any candidate session, recording a callback address of the session object, and determining the callback address of the session object as the session address associated with the target task.
According to a third aspect of the embodiments of the present disclosure, there is provided a message push electronic device, including:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement any one of the above message push methods.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, wherein instructions, when executed by a processor of a message pushing electronic device, enable the message pushing electronic device to perform any one of the message pushing methods described above.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising computer programs/instructions which, when executed by a processor, implement the message push method of any one of the above.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
generating a change notification message of the target task in response to the change of the target task; and under the condition that the change notification message is matched with the preset message type of the target task, pushing the change notification message to the session address associated with the target task, so that the client corresponding to the session address associated with the target task displays the change notification message.
Therefore, when the target task changes, the session address associated with the target task is pushed only under the condition that the change notification message is matched with the preset message type of the target task, the client of each user only receives the notification message of the preset message type of the target task, and the probability that the user receives useless notification messages can be reduced through setting the preset message type, so that the density of the user receiving effective messages is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
Fig. 1 is a flowchart illustrating a message pushing method according to an exemplary embodiment.
Fig. 2 is a flow chart illustrating another message pushing method in accordance with an example embodiment.
FIG. 3 is an interface screen shot of a target task detail page in accordance with an exemplary embodiment.
FIG. 4 is an interface screenshot of a first configuration page, according to an example embodiment.
FIG. 5 is an interface screenshot of a second configuration page, according to an example embodiment.
Fig. 6 is a block diagram illustrating a message pushing device according to an example embodiment.
Fig. 7 is a block diagram illustrating an electronic device for message push according to an example embodiment.
Fig. 8 is a block diagram illustrating an apparatus for message push in accordance with an example embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a flowchart illustrating a message pushing method according to an exemplary embodiment, where the message pushing method may be applied to a server, as shown in fig. 1, and specifically includes the following steps.
In step S11, a change notification message for the target task is generated in response to the change of the target task.
In the present disclosure, the target task may be any one task in a task management system, where the task management system includes a plurality of projects, each project may include a plurality of tasks, and the tasks may be independent of each other or may have overlapping portions, and are not limited in particular.
The server can monitor the target task, and when the target task changes, a change notification message of the target task is generated according to the change of the target task. For example, if the target task has not expired, a change notification message may be generated indicating that the target task has expired.
The change notification message may be classified into a notification message of task overdue, a notification message of a task replacement executor, a notification message of task completion update, and the like according to different message types, and is not particularly limited. The change notification message can be processed in real time, and after the change notification message is processed, the change notification message can be deleted so as to save a system memory, or the change notification message can be stored in a preset database for backup.
In step S12, when the change notification message matches the preset message type of the target task, the change notification message is pushed to the session address associated with the target task, so that the client corresponding to the session address associated with the target task displays the change notification message.
In this step, if the change notification message matches the preset message type of the target task, the notification message may be pushed to the session address associated with the target task, so that the client corresponding to the session address may receive the change notification message and display the received change notification message.
The preset message type and the associated session address of the target task can be stored in the preset database corresponding to the identification information of the target task, so that query and call are facilitated. The change notification message is matched with the preset message type of the target task, that is, the message type of the change notification message is the preset message type of the target task. The preset message type of the target task may include one or more types, and the preset message types of different target tasks may be different, for example, the preset message type of the target task A may include a notification message that the task is overdue and a notification message of a task replacement performer, and the preset message type of the target task B may include only a notification message that the task is overdue, and so on. The session address associated with the target task may also include one or more, and is not limited specifically.
Therefore, for different target tasks, the change notification messages of different preset message types of each target task can be paid attention to respectively, and each change notification message of each target task does not need to be paid attention to; and the change notification message of each target task preset message type is pushed to the session address associated with the target task, and other session addresses not associated with the target task will not receive the change notification message. Therefore, the configuration of the push message is more flexible, the user can follow different target tasks in different sessions, and the information flooding caused by pushing all the change notification messages of all the target tasks to one session is avoided.
In addition, in an implementation manner, under the condition that it is determined that the change notification message matches the preset message type of the target task, each preset message type may be further limited, and the change notification message meeting the limited condition is pushed to the session address associated with the target task.
For example, it may be limited that, when the number of received change notification messages of a certain preset message type exceeds a preset threshold, the change notification messages of the preset message type are pushed to the session address associated with the target task. For example, the preset threshold may be set to 3, then, when receiving the change notification message of the preset message type for the first 3 times, push is not performed, and after receiving the change notification message of the preset message type for the 4 th time, push is performed, so that the density of receiving effective messages by the user may be further improved.
In the present disclosure, the change notification message may be pushed by using IM software, a plurality of sessions may be maintained in the IM software, each session is participated in by a plurality of clients, and a session address of a client corresponding to each session is stored in a preset database. Therefore, after the change notification message of a certain target task is pushed to the session address of the target task associated session according to the association relationship between the target task and the session, the client participating in the session can receive the change notification message, and further, the client can display the change notification message. The session address of the client may be a webhook (web page callback) address of a session object created by the IM software for the client.
In one implementation, for each target task, a preset message type of the target task and a session address associated with the target task may be determined in response to a configuration instruction for the target task. That is to say, the preset message type of the target task and the session address associated with the target task can be configured at any time according to the user requirement, so that the flexibility is strong, and the probability that the user receives useless notification messages is further reduced.
As can be seen from the above, according to the technical scheme provided by the embodiment of the disclosure, when the target task changes, the session address associated with the target task is pushed only when the change notification message matches the preset message type of the target task, the client of each user only receives the notification message of the preset message type of the target task, and the probability that the user receives the useless notification message is reduced by setting the preset message type, so that the density of the user receiving the effective message is increased.
Fig. 2 is a flowchart illustrating a message push method according to an exemplary embodiment, and the message push method includes the following steps, as shown in fig. 2.
In step S21, in response to the configuration instruction for the target task, the preset message type of the target task and the session address associated with the target task are determined.
That is to say, the preset message type of the target task and the session address associated with the target task can be configured at any time according to the user requirement, so that the flexibility is strong, and the probability that the user receives useless notification messages is further reduced. In this step, the configuration instruction for the target task may be a click operation on a configuration control of the target task, and after the server detects a click operation on the configuration control of the target task by the client, the server may display a configuration interface of the target task to the client, and determine a preset message type of the target task and a session address associated with the target task in response to the configuration operation on the preset configuration interface by the client.
As shown in fig. 3, the interface screenshot is a target task detail page, where the configuration control of the target task may be a first icon from left to right below a target task title in the page, that is, after the server detects that the client clicks the icon, the configuration page of the target task may be displayed to the client, and then, the user may configure the preset message type of the target task and the session address associated with the target task in the configuration page displayed by the client. In addition, the title, task description information, and a plurality of field information of the target task may also be displayed and edited on the target task detail page, where the field information may include "performer", "deadline", "participant", and "plan submission date" of the target task, and the like, which is not limited specifically.
The configuration page of the target task may be a single configuration interface, and the user may complete the configuration of the preset message type of the target task and the session address associated with the target task, or multiple configuration interfaces of the target task may be provided, and the preset message type of the target task and the session address associated with the target task are configured on each configuration page. In the present disclosure, the configuration page may be presented in a floating window form, and a new page may also be skipped as the configuration page, which is not limited specifically.
Specifically, in one implementation, the preset message type of the target task may be determined through the first configuration page: and then, responding to the selection operation of any one or more message types in the first configuration page, and determining the selected message type as the preset message type of the target task.
The first configuration page comprises a plurality of message types, namely the message types of the change notification messages possibly generated by the target task, and a user can select the message types which the user wants to pay attention to from the first configuration page according to requirements, so that the configuration of the preset message types of the target task can be realized, and the flexibility is strong.
As shown in fig. 4, in an interface screenshot of a first configuration page, message types that may be generated by a target task corresponding to the first configuration page include "task due incomplete", "task performer change", "new subtask added under task", "new defect associated with task", and "task end", and a preset message type of the target task may be selected by sliding a sliding control on the left side of the message type shown in the first configuration page.
In one implementation, the session address associated with the target task may be determined through the second configuration page: and calling a preset communication interface, displaying at least one candidate session on a second configuration page, and determining the session address of the selected candidate session as the session address associated with the target task in response to the selection operation of any candidate session on the second configuration page.
The candidate session may be a session in which the client displaying the second configuration page participates, or may also be a session that the target task allows to be associated with, and in the second configuration page, the candidate session may be displayed in a list form, or may also be displayed in a pull-down menu form, which is not limited specifically. Therefore, the user can select the session of the change notification message of the preset message type of the target task to be received on the second configuration page according to the requirement, and further, the configuration of the session address associated with the target task can be realized in response to the selection operation of any candidate session, so that the flexibility is strong.
In response to the selection operation of any candidate session on the second configuration page, determining the session address of the selected candidate session as the session address associated with the target task may specifically include the following steps: in response to the selection operation of any candidate session on the second configuration page, creating a session object in the candidate session, wherein the session object can be a session robot; and then, recording the callback address of the session object, and determining the callback address of the session object as the session address associated with the target task. Therefore, under the condition that the change notification message is matched with the preset message type of the target task, the change notification message can be pushed to the callback address of the session object, and then the session object can receive the change notification message and display the change notification message to the client.
As shown in fig. 5, the interface of the second configuration page is a screenshot, wherein after a click operation on the "please select group chat" menu bar is detected, at least one candidate session of the target task may be displayed in a drop-down menu, and in addition, "recently used" sessions, such as "project group 1", "task group 1", and "task group 2", may also be displayed in the second configuration page. A "recently used" session is a session in which the client presenting the second configuration page has recently participated, or a session previously associated with the target task, etc.
In the present disclosure, the order of presentation of the first configuration page and the second configuration page is not limited, for example, in the first configuration page shown in fig. 4, if a click operation on the "next" button at the lower right corner is detected, the user can jump from the first configuration page to the second configuration page.
In this step, after the preset message type and the associated session address of the target task are determined, the preset message type, the associated session address and the identification information of the target task may be correspondingly stored in a preset database, which is convenient for query and call.
In step S22, a change notification message for the target task is generated in response to the change of the target task.
This step is the same as step S11 in the embodiment shown in fig. 1, and is not described here again.
In step S23, when the change notification message matches the preset message type of the target task, the change notification message is pushed to the session address associated with the target task, so that the client corresponding to the session address associated with the target task displays the change notification message.
This step is the same as step S12 in the embodiment shown in fig. 1, and is not described here again.
As can be seen from the above, according to the technical scheme provided by the embodiment of the disclosure, when the target task changes, the session address associated with the target task is pushed only when the change notification message matches the preset message type of the target task, the client of each user only receives the notification message of the preset message type of the target task, and the probability that the user receives the useless notification message is reduced by setting the preset message type, so that the density of the user receiving the effective message is increased.
Fig. 6 is a block diagram illustrating a message pushing apparatus according to an exemplary embodiment, the apparatus comprising:
a generating unit 301 configured to perform generating a change notification message of a target task in response to a change of the target task;
a pushing unit 302, configured to, when the change notification message matches with the preset message type of the target task, push the change notification message to the session address associated with the target task, so that the client corresponding to the session address associated with the target task displays the change notification message.
In one implementation, the apparatus further includes:
and the configuration unit is configured to execute a configuration instruction responding to the target task and determine a preset message type of the target task and a session address associated with the target task.
In one implementation, the configuration unit is specifically configured to perform:
displaying a first configuration page of the target task, wherein the first configuration page comprises a plurality of message types;
and in response to the selection operation of any one or more message types in the first configuration page, determining the selected message type as a preset message type of the target task.
In one implementation, the configuration unit is specifically configured to perform:
calling a preset communication interface, and displaying at least one candidate session on a second configuration page;
and in response to the selection operation of any candidate session in the second configuration page, determining the session address of the selected candidate session as the session address associated with the target task.
In one implementation, the configuration unit is specifically configured to perform:
and responding to the selection operation of any candidate session on the second configuration page, creating a session object in any candidate session, recording a callback address of the session object, and determining the callback address of the session object as the session address associated with the target task.
As can be seen from the above, according to the technical scheme provided by the embodiment of the disclosure, when the target task changes, the session address associated with the target task is pushed only when the change notification message matches the preset message type of the target task, the client of each user only receives the notification message of the preset message type of the target task, and the probability that the user receives the useless notification message is reduced by setting the preset message type, so that the density of the user receiving the effective message is increased.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Fig. 7 is a block diagram illustrating an electronic device for message push according to an example embodiment.
In an exemplary embodiment, a computer-readable storage medium comprising instructions, such as a memory comprising instructions, executable by a processor of an electronic device to perform the above-described method is also provided. Alternatively, the computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, a computer program product is also provided, which when run on a computer causes the computer to implement the above message pushing method.
As can be seen from the above, according to the technical scheme provided by the embodiment of the disclosure, when the target task changes, the session address associated with the target task is pushed only when the change notification message matches the preset message type of the target task, the client of each user only receives the notification message of the preset message type of the target task, and the probability that the user receives the useless notification message is reduced by setting the preset message type, so that the density of the user receiving the effective message is increased.
Fig. 8 is a block diagram illustrating an apparatus 800 for message push according to an example embodiment.
For example, the apparatus 800 may be a mobile phone, a computer, a digital broadcast electronic device, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 8, the apparatus 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.
The processing component 802 generally controls overall operation of the device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operation at the device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
Power supply components 807 provide power to the various components of device 800. The power components 807 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the apparatus 800.
The multimedia component 808 includes a screen that provides an output interface between the device 800 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front facing camera and/or a rear facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor assembly 814 includes one or more sensors for providing various aspects of state assessment for the device 800. For example, the sensor assembly 814 may detect the open/closed state of the device 800, the relative positioning of the components, such as a display and keypad of the apparatus 800, the sensor assembly 814 may also detect a change in position of the apparatus 800 or a component of the apparatus 800, the presence or absence of user contact with the apparatus 800, orientation or acceleration/deceleration of the apparatus 800, and a change in temperature of the apparatus 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communications between the apparatus 800 and other devices in a wired or wireless manner. The apparatus 800 may access a wireless network based on a communication standard, such as WiFi, an operator network (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the methods of the first and second aspects.
In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 804 comprising instructions, executable by the processor 820 of the device 800 to perform the above-described method is also provided. Alternatively, for example, the storage medium may be a non-transitory computer-readable storage medium, such as a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the message push method as described in any of the above embodiments.
As can be seen from the above, according to the technical scheme provided by the embodiment of the disclosure, when the target task changes, the session address associated with the target task is pushed only when the change notification message matches the preset message type of the target task, the client of each user only receives the notification message of the preset message type of the target task, and the probability that the user receives the useless notification message is reduced by setting the preset message type, so that the density of the user receiving the effective message is increased.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (10)

1. A message pushing method, comprising:
generating a change notification message of a target task in response to a change of the target task;
and under the condition that the change notification message is matched with the preset message type of the target task, pushing the change notification message to the session address associated with the target task, so that the client corresponding to the session address associated with the target task displays the change notification message.
2. The message pushing method according to claim 1, wherein the method further comprises:
and responding to the configuration instruction of the target task, and determining the preset message type of the target task and the session address associated with the target task.
3. The message pushing method according to claim 2, wherein the determining the preset message type of the target task in response to the configuration instruction of the target task comprises:
displaying a first configuration page of the target task, wherein the first configuration page comprises a plurality of message types;
and in response to the selection operation of any one or more message types in the first configuration page, determining the selected message type as a preset message type of the target task.
4. The message pushing method according to claim 2, wherein the determining a session address associated with the target task in response to the configuration instruction for the target task comprises:
calling a preset communication interface, and displaying at least one candidate session on a second configuration page;
and in response to the selection operation of any candidate session in the second configuration page, determining the session address of the selected candidate session as the session address associated with the target task.
5. The message pushing method according to claim 4, wherein the determining, in response to the selection operation of any one of the candidate sessions on the second configuration page, the session address of the selected candidate session as the session address associated with the target task includes: :
and in response to the selection operation of any candidate session on the second configuration page, creating a session object in any candidate session, recording a callback address of the session object, and determining the callback address of the session object as the session address associated with the target task.
6. A message push apparatus, comprising:
a generation unit configured to perform a change notification message in response to a change of a target task, the change notification message of the target task being generated;
the pushing unit is configured to push the change notification message to the session address associated with the target task under the condition that the change notification message is matched with the preset message type of the target task, so that the client corresponding to the session address associated with the target task displays the change notification message.
7. The message pushing device according to claim 6, wherein the device further comprises:
and the configuration unit is configured to execute a configuration instruction responding to the target task and determine a preset message type of the target task and a session address associated with the target task.
8. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the message pushing method of any one of claims 1 to 5.
9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of a message-pushing electronic device, enable the message-pushing electronic device to perform the message-pushing method of any one of claims 1-5.
10. A computer program product comprising a computer program, characterized in that the computer program realizes the message push method of any of claims 1-5 when executed by a processor.
CN202111674458.1A 2021-12-31 2021-12-31 Message pushing method and device, electronic equipment and storage medium Pending CN114443160A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111674458.1A CN114443160A (en) 2021-12-31 2021-12-31 Message pushing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111674458.1A CN114443160A (en) 2021-12-31 2021-12-31 Message pushing method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN114443160A true CN114443160A (en) 2022-05-06

Family

ID=81366383

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111674458.1A Pending CN114443160A (en) 2021-12-31 2021-12-31 Message pushing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114443160A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115248648A (en) * 2022-08-12 2022-10-28 北京字跳网络技术有限公司 Task processing method and device, electronic equipment and medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080209417A1 (en) * 2007-02-22 2008-08-28 Gabriel Jakobson Method and system of project management and task collaboration over instant messenger
CN104050540A (en) * 2014-06-27 2014-09-17 北京思特奇信息技术股份有限公司 Method and system for team cooperation task management
CN107809372A (en) * 2016-09-08 2018-03-16 阿里巴巴集团控股有限公司 The generation method of activity reminder message, movable based reminding method and device
CN109905315A (en) * 2017-12-08 2019-06-18 阿里巴巴集团控股有限公司 The information acquisition method and device of group task
CN111884823A (en) * 2020-07-20 2020-11-03 腾讯科技(深圳)有限公司 Task prompting method and device, storage medium and electronic device
CN112437004A (en) * 2020-11-27 2021-03-02 腾讯科技(深圳)有限公司 Information processing method, information processing device, electronic equipment and storage medium
WO2021169792A1 (en) * 2020-02-26 2021-09-02 北京达佳互联信息技术有限公司 Message viewing method and apparatus

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080209417A1 (en) * 2007-02-22 2008-08-28 Gabriel Jakobson Method and system of project management and task collaboration over instant messenger
CN104050540A (en) * 2014-06-27 2014-09-17 北京思特奇信息技术股份有限公司 Method and system for team cooperation task management
CN107809372A (en) * 2016-09-08 2018-03-16 阿里巴巴集团控股有限公司 The generation method of activity reminder message, movable based reminding method and device
CN109905315A (en) * 2017-12-08 2019-06-18 阿里巴巴集团控股有限公司 The information acquisition method and device of group task
WO2021169792A1 (en) * 2020-02-26 2021-09-02 北京达佳互联信息技术有限公司 Message viewing method and apparatus
CN111884823A (en) * 2020-07-20 2020-11-03 腾讯科技(深圳)有限公司 Task prompting method and device, storage medium and electronic device
CN112437004A (en) * 2020-11-27 2021-03-02 腾讯科技(深圳)有限公司 Information processing method, information processing device, electronic equipment and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115248648A (en) * 2022-08-12 2022-10-28 北京字跳网络技术有限公司 Task processing method and device, electronic equipment and medium
CN115248648B (en) * 2022-08-12 2024-01-30 北京字跳网络技术有限公司 Task processing method, device, electronic equipment and medium

Similar Documents

Publication Publication Date Title
CN112561631A (en) Information display method and device, electronic equipment and storage medium
CN109521918B (en) Information sharing method and device, electronic equipment and storage medium
CN109451341B (en) Video playing method, video playing device, electronic equipment and storage medium
US20220150598A1 (en) Method for message interaction, and electronic device
CN113259226B (en) Information synchronization method and device, electronic equipment and storage medium
CN112416219B (en) Target object processing method, device and system, electronic equipment and storage medium
CN112291631A (en) Information acquisition method, device, terminal and storage medium
CN107729098B (en) User interface display method and device
CN112699655A (en) Method and device for creating documents in communication group and electronic equipment
CN108984098B (en) Information display control method and device based on social software
CN113988021A (en) Content interaction method and device, electronic equipment and storage medium
CN110162366B (en) Information display method and device, electronic equipment and storage medium
CN105656639B (en) Group message display method and device
CN114443160A (en) Message pushing method and device, electronic equipment and storage medium
CN110690979B (en) Group message processing method, device, server, client and storage medium
CN113031837A (en) Content sharing method and device, storage medium, terminal and server
CN114339320B (en) Virtual resource processing method, device, equipment and storage medium
CN115904599A (en) Virtual resource information display method and device, electronic equipment and storage medium
CN111343510B (en) Information processing method, information processing device, electronic equipment and storage medium
CN114157520A (en) Project state acquisition method and device, electronic equipment and storage medium
CN114095794A (en) Information processing method, information processing device, electronic equipment and computer readable storage medium
CN113919311A (en) Data display method and device, electronic equipment and storage medium
CN113709572A (en) Content promotion method and device, electronic equipment and storage medium
CN112581102A (en) Task management method and device, electronic equipment and storage medium
CN109120499B (en) Information processing method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination