WO2018223869A1 - 任务提醒方法及装置、提醒消息的生成和展示方法及装置 - Google Patents

任务提醒方法及装置、提醒消息的生成和展示方法及装置 Download PDF

Info

Publication number
WO2018223869A1
WO2018223869A1 PCT/CN2018/088810 CN2018088810W WO2018223869A1 WO 2018223869 A1 WO2018223869 A1 WO 2018223869A1 CN 2018088810 W CN2018088810 W CN 2018088810W WO 2018223869 A1 WO2018223869 A1 WO 2018223869A1
Authority
WO
WIPO (PCT)
Prior art keywords
task
reminder
reminder message
message
conference
Prior art date
Application number
PCT/CN2018/088810
Other languages
English (en)
French (fr)
Inventor
杨博宇
张明
鲍丰
石佳锐
Original Assignee
阿里巴巴集团控股有限公司
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 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Priority to SG11201911449PA priority Critical patent/SG11201911449PA/en
Publication of WO2018223869A1 publication Critical patent/WO2018223869A1/zh
Priority to US16/705,054 priority patent/US20200111060A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/214—Monitoring or handling of messages using selective forwarding
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/1093—Calendar-based scheduling for persons or groups
    • G06Q10/1097—Task assignment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/1093—Calendar-based scheduling for persons or groups
    • G06Q10/1095—Meeting or appointment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72451—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to schedules, e.g. using calendar applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/725—Cordless telephones

Definitions

  • the present invention relates to the field of terminal technologies, and in particular, to a task reminding method and device, and a method and device for generating and displaying a reminder message.
  • the mobile enterprise office platform is more and more widely used in the business processes of various groups such as enterprises, educational institutions, government agencies, etc., which can not only improve communication efficiency between users, reduce communication costs, but also be effective. Improve user event processing efficiency and office efficiency.
  • the mobile enterprise office platform can be used to send a reminder message, which can be sent based on the instant messaging function provided by the mobile enterprise office platform, or can be sent based on traditional mobile communication methods such as short messages and telephones. Make sure the reminder is effective.
  • the reminder messages are independent of each other.
  • the user creates the reminder message 1 and the reminder message 2 related to the event 1 at time A and time B respectively.
  • the reminder message 1 and the reminder message 2 are objectively related to the event 1, the user is viewing the reminder message 1 It is not possible to know the content of the reminder message 2, or even the existence of the forgotten reminder message 2, which may result in the user not being able to successfully handle the event 1.
  • the number of reminder messages may be too large, so that the user cannot quickly find the reminder message 2.
  • the present application provides a task reminding method and apparatus, a method and a device for generating and displaying a reminder message, and can establish an association between a meeting reminding message and a task reminding message, so that the user can quickly view the process in the process of processing the task.
  • Relevant information about the conference can help improve the efficiency of task processing.
  • a task reminding method including:
  • the client receives a task reminder message generation instruction related to the conference reminder message
  • the client determines the reminder object and the task description information
  • the client sends a task reminder message related to the conference reminder message to the reminder object, where the task reminder message includes the task description information.
  • a task reminding method including:
  • the client receives a task reminder message related to the meeting reminder message
  • the client displays task description information included in the task reminder message, and displays meeting description information in the meeting reminder message.
  • a task reminding method including:
  • the client receives a task reminder message generation instruction related to the conference reminder message
  • the client determines the reminder object and the task description information
  • the task reminder message includes the task description information.
  • a task reminding method including:
  • the client receives a task reminder message related to the meeting reminder message
  • the client When the logged-in user participates in the conference, the client displays task description information included in the task reminder message, and displays conference description information of the conference; the client does not participate in the logged-in user. During the conference, the task description information included in the task reminder message is displayed.
  • a method for generating a reminder message including:
  • the client receives an alert message generation instruction related to the first reminder message
  • the client determines the reminder object and the reminder event description information
  • the client sends a second reminder message related to the first reminder message to the reminder object, where the second reminder message includes the reminder event description information.
  • a method for generating a reminder message including:
  • the client generates a second reminder message related to the first reminder message according to the reminder object, the reminder event description information, and the first reminder message;
  • the client sends the second reminder message to the reminder object, where the second reminder message includes the reminder event description information.
  • a method for displaying a reminder message including:
  • the client receives a second reminder message related to the first reminder message
  • the client displays the second reminder event description information included in the second reminder message, and displays the first reminder event description information corresponding to the first reminder message.
  • a task reminding method including:
  • the client receives a task reminder message generation instruction related to the conference
  • the client determines the reminder object and the task description information
  • the client sends a task reminder message related to the conference to the reminder object, where the task reminder message includes the task description information.
  • a task reminding method including:
  • the client generates a task reminder message related to the conference according to the reminder object, the task description information, and the conference;
  • the client sends the task reminder message to the reminder object, where the task reminder message includes the task description information.
  • a task reminding method including:
  • the client receives a task reminder message related to the conference
  • the client displays task description information included in the task reminder message, and shows meeting description information of the conference.
  • a task reminding device including:
  • a first instruction receiving unit configured to enable the client to receive a task reminder message generating instruction related to the meeting reminding message
  • a first determining unit configured to enable the client to determine a reminder object and task description information
  • the first sending unit is configured to enable the client to send a task reminding message related to the meeting reminding message to the reminding object, where the task reminding message includes the task description information.
  • a task reminding device including:
  • a first message receiving unit configured to enable the client to receive a task reminder message related to the meeting reminder message
  • the first display unit is configured to enable the client to display task description information included in the task reminder message, and display meeting description information in the meeting reminder message.
  • a task reminding device including:
  • a second instruction receiving unit configured to enable the client to receive a task reminder message generating instruction related to the meeting reminding message
  • a second determining unit configured, by the client, to determine a reminder object and task description information
  • a second sending unit configured to send, by the client, a task reminding message related to the meeting to a reminder object participating in the meeting corresponding to the meeting reminding message, and sending a reminder object not participating in the meeting to the reminding object not participating in the meeting
  • a task reminder message, the task reminder message includes the task description information.
  • a task reminding device including:
  • a second message receiving unit configured to enable the client to receive a task reminder message related to the meeting reminder message
  • a user type determining unit configured to enable the client to determine whether the logged-in user participates in a conference corresponding to the conference reminder message
  • a second display unit when the logged-in user participates in the conference, the task description information included in the task reminder message is displayed, and the conference description information of the conference is displayed; When the logged-in user does not participate in the conference, the task description information included in the task reminder message is displayed.
  • a device for generating a reminder message including:
  • a third instruction receiving unit configured to enable the client to receive an alert message generating instruction related to the first reminder message
  • a third determining unit configured to: determine, by the client, a reminder object and a reminder event description information
  • the third sending unit is configured to enable the client to send a second reminder message related to the first reminder message to the reminder object, where the second reminder message includes the reminder event description information.
  • a device for generating a reminder message including:
  • a first generating unit configured to generate, by the client, a second reminder message related to the first reminder message according to the reminder object, the reminder event description information, and the first reminder message;
  • the fourth sending unit is configured to enable the client to send the second reminder message to the reminder object, where the second reminder message includes the reminder event description information.
  • a display device for alerting messages including:
  • a third message receiving unit configured to enable the client to receive a second reminder message related to the first reminder message
  • the third display unit is configured to display the second reminder event description information included in the second reminder message, and display the first reminder event description information corresponding to the first reminder message.
  • a task reminding device including:
  • a fourth instruction receiving unit configured to enable the client to receive a task reminder message generation instruction related to the conference
  • a fourth determining unit configured to determine, by the client, a reminder object and task description information
  • a fifth sending unit configured to send, by the client, a task reminding message related to the meeting to the reminding object, where the task reminding message includes the task description information.
  • a task reminding device including:
  • a second generating unit configured to: generate, by the client, a task reminding message related to the meeting according to the reminding object, the task description information, and the meeting;
  • a sixth sending unit configured to send the task reminder message to the reminder object, where the task reminder message includes the task description information.
  • a task reminding device including:
  • a fourth message receiving unit configured to enable the client to receive a task reminder message related to the conference
  • the fourth display unit is configured to enable the client to display task description information included in the task reminder message, and display meeting description information of the conference.
  • a task reminding method including:
  • a task reminding method including:
  • a task reminding method including:
  • a task reminding method including:
  • the task description information included in the task reminder message is displayed, and the conference description information of the conference is displayed; the client is not involved in the conference when the logged-in user does not participate in the conference Demonstrating task description information included in the task reminder message.
  • a method for generating a reminder message including:
  • a method for generating a reminder message including:
  • a method for displaying a reminder message including:
  • the second reminder event description information included in the second reminder message is displayed, and the first reminder event description information corresponding to the first reminder message is displayed.
  • a task reminding method including:
  • a task reminding method including:
  • a task reminding method including:
  • the present invention associates the task reminding message with the meeting reminding message, so that the user can quickly view related information of the associated meeting in the process of processing the task, which helps improve the task processing efficiency.
  • the user can quickly view other related reminder messages when viewing any of the reminder messages, without the user manually searching for the reminder messages, which helps to improve The efficiency with which users can access relevant information and the efficiency of processing related events.
  • FIG. 1 is a schematic structural diagram of a task reminding system according to an exemplary embodiment of the present application.
  • FIG. 2 is a flowchart of a sender-based task reminding method provided by an exemplary embodiment of the present application.
  • FIG. 3 is a flowchart of a receiver-based task reminding method provided by an exemplary embodiment of the present application.
  • FIG. 4 is a flowchart of another method for reminding a task based on a sender according to an exemplary embodiment of the present application.
  • FIG. 5 is a flowchart of another method for reminding a task based on a receiver according to an exemplary embodiment of the present application.
  • FIG. 6 is a schematic diagram of a conference details interface according to an exemplary embodiment of the present application.
  • FIG. 7 is a schematic diagram of a conference task creation interface provided by an exemplary embodiment of the present application.
  • FIG. 8 is a schematic diagram of another conference detail interface provided by an exemplary embodiment of the present application.
  • FIG. 9 is a schematic diagram of a responsible person selection interface according to an exemplary embodiment of the present application.
  • FIG. 10 is a schematic diagram of an alert message management interface provided by an exemplary embodiment of the present application.
  • FIG. 11 is a schematic diagram of a task details interface according to an exemplary embodiment of the present application.
  • FIG. 12 is a schematic diagram of another alert message management interface provided by an exemplary embodiment of the present application.
  • FIG. 13 is a schematic diagram of still another reminder message management interface provided by an exemplary embodiment of the present application.
  • FIG. 14 is a schematic diagram of still another reminder message management interface according to an exemplary embodiment of the present application.
  • FIG. 15 is a schematic diagram of another task detail interface provided by an exemplary embodiment of the present application.
  • FIG. 16 is a schematic diagram of still another task detail interface according to an exemplary embodiment of the present application.
  • FIG. 17 is a schematic diagram of still another reminder message management interface according to an exemplary embodiment of the present application.
  • FIG. 18 is a schematic diagram of still another reminder message management interface according to an exemplary embodiment of the present application.
  • FIG. 19 is a schematic diagram of still another reminder message management interface according to an exemplary embodiment of the present application.
  • FIG. 20 is a flowchart of still another method for reminding a task based on a sender according to an exemplary embodiment of the present application.
  • FIG. 21 is a schematic diagram of an interface for managing a calendar according to an exemplary embodiment of the present application.
  • FIG. 22 is a flowchart of still another method for reminding a task based on a sender according to an exemplary embodiment of the present application.
  • FIG. 23 is a flowchart of still another method for reminding a task based on a receiver according to an exemplary embodiment of the present application.
  • FIG. 24 is a flowchart of a method for generating a reminder message according to an exemplary embodiment of the present application.
  • FIG. 25 is a flowchart of another method for generating an alert message according to an exemplary embodiment of the present application.
  • FIG. 26 is a flowchart of a method for displaying an alert message according to an exemplary embodiment of the present application.
  • FIG. 27 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application.
  • FIG. 28 is a block diagram of a sender-based task reminding apparatus according to an exemplary embodiment of the present application.
  • FIG. 29 is a block diagram of a receiver-based task reminding apparatus according to an exemplary embodiment of the present application.
  • FIG. 30 is a block diagram of another sender-based task reminding apparatus provided by an exemplary embodiment of the present application.
  • FIG. 31 is a block diagram of another recipient reminder device based on a receiver provided by an exemplary embodiment of the present application.
  • FIG. 32 is a block diagram of still another task reminder device based on a sender according to an exemplary embodiment of the present application.
  • FIG. 33 is a block diagram of still another task reminder device based on a sender according to an exemplary embodiment of the present application.
  • FIG. 34 is a block diagram of still another task reminding device based on a receiver according to an exemplary embodiment of the present application.
  • FIG. 35 is a schematic structural diagram of another electronic device according to an exemplary embodiment of the present application.
  • FIG. 36 is a block diagram of an apparatus for generating an alert message according to an exemplary embodiment of the present application.
  • FIG. 37 is a block diagram of another apparatus for generating an alert message according to an exemplary embodiment of the present application.
  • FIG. 38 is a schematic structural diagram of still another electronic device according to an exemplary embodiment of the present application.
  • FIG. 39 is a block diagram of an apparatus for displaying an alert message according to an exemplary embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of a task reminding system according to an exemplary embodiment of the present application.
  • the system may include a server 11, a network 12, and a number of electronic devices, such as a mobile phone 13, a mobile phone 14, a mobile phone 15, and a mobile phone 16.
  • the server 11 may be a physical server including a separate host, or the server 11 may be a virtual server hosted by the host cluster, or the server 11 may be a cloud server.
  • the server 11 can run a server-side program of an application to implement related business functions of the application. For example, when the server 11 runs the program of the mobile group office platform, the mobile group can be implemented. The server side of the platform.
  • the server 11 can cooperate with the client running on the mobile phone 13-16 to implement functions such as sending and receiving task reminding messages.
  • the mobile group office platform can not only realize the communication function, but also can be used as an integrated function platform for many other functions, such as approval events (such as leave, office item application, financial and other approval events), attendance events, task events,
  • approval events such as leave, office item application, financial and other approval events
  • attendance events such as task events
  • task events such as the processing of internal events such as log events, such as the processing of external events such as ordering, purchasing, etc.
  • the mobile group office platform can be carried in instant messaging applications in related technologies, such as enterprise instant messaging (EIM) applications, such as Skype For. Microsoft Wait.
  • EIM enterprise instant messaging
  • the instant messaging function is only one of the communication functions supported by the mobile group office platform.
  • the group office platform can also implement more functions such as the above, and the activity reminding function required in the present application, etc. Let me repeat.
  • Mobile phones 13-16 are just one type of electronic device that a user can use. In fact, users obviously can also use electronic devices such as tablet devices, notebook computers, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc. This is a limitation.
  • the electronic device can run a client-side program of an application to implement related business functions of the application, for example, when the electronic device runs a program of the mobile group office platform, the mobile device can be implemented as the mobile device.
  • the client of the group office platform is used to implement the functions of generating, sending, receiving, and displaying the task reminding message of the present application.
  • the application of the client of the mobile enterprise office platform can be pre-installed on the electronic device, so that the client can be started and run on the electronic device; of course, when adopting an online "client" such as HTML5 technology The client can be obtained and run without installing the corresponding application on the electronic device.
  • the network 12 may include multiple types of wired or wireless networks.
  • the network 12 may include a Public Switched Telephone Network (PSTN) and the Internet.
  • PSTN Public Switched Telephone Network
  • the electronic devices such as the mobile phone 13-16 can also communicate with each other through the network 12, for example, a single-chat communication session is established between any two electronic devices; or, a plurality of electronic devices can participate in the same group chat communication session.
  • the member can communicate with the group chat through the cross-group communication session; for example, each electronic device can send a task type reminder message to the other one or more electronic devices through the network 12 to implement the task reminding function of the present application. .
  • a long connection can be established between the server 11 and the mobile phone 13-16 through the network 12, so that the server 11 sends a push message or the like to the mobile phone 13-16 through the long connection, and the mobile phone 13-16 can also send a message to the server 11 based on the long connection.
  • the communication process based on the network 12 may be implemented between the server 11 and the mobile phone 13-16 in other manners, and details are not described herein again.
  • the electronic device such as the mobile phone 13-16 can be used by the sender and the receiver, so that the electronic device used by the sender can use the sender client of the task reminder message and the receiver.
  • the electronic device can run the recipient client of the task reminder message; wherein the sender client can generate a task reminder message related to one or more meeting reminder messages, and send the task reminder message to the receiving client, for example
  • the sender client can send the task reminder message to the receiver client through the server running by the server 11, and the receiver client can display the received task reminder message to the receiver, so that the receiver can remind the message through the task.
  • the technical solution of the present application is described below in conjunction with the processing logic of the sender client and the receiver client.
  • FIG. 2 is a flowchart of a sender-based task reminding method provided by an exemplary embodiment of the present application. As shown in FIG. 2, the method is applied to a sender's electronic device, and may include the following steps:
  • Step 202 The client receives a task reminder message generation instruction related to the conference reminder message.
  • the client may provide multiple types of reminder messages; for example, the conference reminder message is used to implement a reminder function for a conference event, and the task reminder message is used to implement a reminder function for a task event.
  • the conference reminder message is used to implement a reminder function for a conference event
  • the task reminder message is used to implement a reminder function for a task event.
  • the client may provide multiple ways to generate a task reminder message. Therefore, there are multiple ways to obtain the above-mentioned task reminder message generation instruction related to the conference reminder message, which is not limited in this application.
  • the client may provide multiple ways to generate a task reminder message. Therefore, there are multiple ways to obtain the above-mentioned task reminder message generation instruction related to the conference reminder message, which is not limited in this application.
  • the client may display a task creation option in a presentation interface of the conference reminder message; then, when the client receives a trigger operation for the task creation option, the client may determine Receiving the task reminder message generating instruction.
  • the display interface of the meeting reminding message includes any interface that can display the meeting reminding message, such as a detailed display interface dedicated to the meeting reminding message, or a reminder message management page for collectively displaying the meeting reminding message and other reminding messages.
  • the client may also provide other trigger forms for the conference reminder message, such as marking a preset touch gesture on the display interface. Controlling speech, etc., this application does not limit this.
  • the “Task Creation Option” is just a form of options that can be used, and other task-related function options can also be applied here to replace the “Task Creation Option”; for example, the function option can be “Task” Editing Options or Task Modifying Options, when the Task Editing Option or Task Modifying Option is triggered, may display a task reminder message template related to the meeting reminder message for the sender to edit the template Or modify it to get the task reminder message related to the meeting reminder message.
  • the client may receive a user creation operation for a task reminder message, and a conference binding operation for the task reminder message; then, when the conference binding operation selects the conference reminder message
  • the client may determine to receive a task reminder message generation instruction related to the conference reminder message.
  • the client may provide a user with a creation option for the task reminder message.
  • the client may further provide the user with an alternate meeting reminder message (eg, the client has received, has The sent conference reminder message, etc., for the user to select a conference reminder message that is desired to be bound to the task reminder message by the user selection operation.
  • Step 204 The client determines the reminder object and the task description information.
  • the reminder object may include at least one of the following: a participant of the conference corresponding to the conference reminder message, and an object selected by the object selection operation received by the client.
  • the client may display the participant of the conference and the associated user of the sender as alternate users, so that the sender selects the user who wishes to be the object of the reminder.
  • the client may use the participant of the conference as the reminder object by default, and display the associated user of the sender as an alternative user, so that the sender further adds the user who wishes to be the object of the reminder;
  • the participants of the meeting can be set to be reminders, and in another case, although the participants of the meeting are added as reminders by default, the sender can adjust according to the actual situation.
  • Step 206 The client sends a task reminder message related to the conference reminder message to the reminder object, where the task reminder message includes the task description information.
  • the task reminder message may further include meeting description information in the meeting reminding message, that is, the client may add at least one meeting description information in the meeting reminding message to the task reminding message, Show to the recipient.
  • the task reminder message may not include the conference description information; for example, in one case, the task alert message may include the identifier information of the conference reminder message, so that the receiver client receives the task reminder.
  • the server may obtain the corresponding at least one conference description information from the server according to the identifier information, or search for the corresponding conference reminder message and the conference description information thereof in the historical reminder message of the receiver client according to the identifier information;
  • the client may notify the server of the association information between the task reminder message and the conference reminder message, and the task reminder message may include a conference association identifier, where the conference association identifier may indicate to the receiver client.
  • the task reminder message has an associated conference reminder message, and the receiver client may initiate an inquiry to the server, so that the server returns at least one conference description of the corresponding conference reminder message to the receiver client based on the association information. information.
  • the reminder object when the reminder object does not participate in the conference corresponding to the conference reminder message, the reminder object is equivalent to a participant independent of the conference, and thus the reminder object may have a task for the task reminder message. Manage permissions to determine the task processing status of the reminder.
  • the reminder object when the reminder object participates in the conference, and the reminder object is configured as a task owner, the reminder object may have task management authority for the task reminder message.
  • the reminder object when the reminder object participates in the conference, and the reminder object is configured as a task participant, the reminder object may not have task management authority for the task reminder message;
  • the task participant is equivalent to a whole, and the task manager performs a unified task management operation on behalf of the whole.
  • the embodiment shown in FIG. 2 can be applied to a client running on an electronic device such as a mobile phone or a PC of a sender, so that a function of generating and sending a task reminder message is implemented through the client, in some cases.
  • the following can also be applied to the server, so that the server can implement the functions of generating and sending a task reminder message by running various steps included in the embodiment.
  • the embodiment shown in FIG. 2 may be applied to other possible execution entities. By executing the steps included in the embodiment, the execution entities implement functions such as generating and sending task reminding messages. The application does not limit this.
  • FIG. 3 is a flowchart of a receiver-based task reminding method provided by an exemplary embodiment of the present application. As shown in FIG. 3, the method is applied to an electronic device of a receiver, and may include the following steps:
  • Step 302 The client receives a task reminder message related to the conference reminder message.
  • Step 304 The client displays task description information included in the task reminder message, and displays meeting description information in the meeting reminder message.
  • the client may obtain the meeting description information included in the task reminding message, and display the meeting description information and the task description information included in the task reminding message.
  • the task reminder message may not include the conference description information.
  • the task reminder message may include the identifier information of the conference reminder message, and the client may obtain the corresponding conference description information according to the identifier information; for example, the client may perform the historical reminder message according to the identifier information. Searching to find a corresponding meeting reminding message, and obtaining meeting description information included in the meeting reminding message; for example, the client may initiate an inquiry to the server according to the identification information, so that the server returns a corresponding meeting to the client. Reminder message or meeting description information.
  • the task reminder message may include a conference association identifier, so that the client determines that the task alert message has an associated conference reminder message, and the client may initiate an inquiry related to the task alert message to the server; Then, if the sender client informs the server in advance of the association relationship between the task reminder message and the conference reminder message, the server can determine the conference reminder message based on the association relationship, and the client can receive the server return.
  • the meeting reminder message or meeting description information may be included in another conference reminder message.
  • the client may display at least a part of the content of the conference description information in a display area of the task reminding message, where the display area may include a detailed display interface dedicated to the task reminding message, or the foregoing The display area of the reminder message management page corresponding to the task reminder message.
  • the client may display at least a part of the content of the task description information in a display area of the meeting reminding message, where the display area may include a detailed display interface dedicated to the meeting reminding message, or the foregoing The display area of the reminder message management page corresponding to the meeting reminder message.
  • the client may display a first trigger option related to the conference reminder message in a display area of the task reminder message; wherein, when the first trigger option is triggered, the The client displays the conference description information in the conference reminder message.
  • the first triggering option may include summary information of the conference description information, and based on the triggering operation on the first triggering option, the client displays the detailed information of the conference description information, where The detailed information may be displayed in the display area of the task reminding message, or displayed on a separate interface (such as a detailed display interface or a temporary window interface dedicated to the meeting reminding message); when the client has not been informed of the meeting description information, the first triggering option
  • the indication options such as “click to learn the associated conference” may be included, and based on the triggering operation on the first trigger option, the client obtains the corresponding conference description information for display.
  • the client may display a second trigger option related to the task description information in a display area of the conference reminder message; wherein, when the second trigger option is triggered, the The client displays the task description information.
  • the first triggering option may include summary information of the task description information, and based on the triggering operation on the first triggering option, the client displays detailed information of the task description information, and the detailed information may be displayed in the meeting reminding message.
  • the display area or displayed in a separate interface (such as the specific display interface or temporary window interface dedicated to the task reminder message).
  • the client may perform task management on the task event according to a triggering operation for a task event corresponding to the task reminding message.
  • task management may include suspension, suspension, completion, etc. of a task event, which is not limited in this application.
  • the client can implement different types of task management; when the logged-in user has no privilege, the client may not be able to implement task management.
  • the embodiment shown in FIG. 3 can be applied to a client running on an electronic device such as a mobile phone or a PC of a receiving party, so that the receiving task reminding message and the task description information and the conference description are implemented by the client.
  • the information and the like can also be applied to the server in some cases, so that the server can receive the task reminding message, display the task description information and the meeting description information to the receiving party by running the various steps included in the embodiment (for example, the task)
  • the description information and the conference description information are sent to the client corresponding to the receiver, etc.).
  • the embodiment shown in FIG. 3 may also be applied to other possible execution entities, by which the execution subjects receive the task reminder message and display the task to the receiver by running the various steps included in the embodiment. Functions such as description information and meeting description information are not limited in this application.
  • FIG. 4 is a flowchart of another method for reminding a task based on a sender according to an exemplary embodiment of the present application. As shown in FIG. 4, the method is applied to an electronic device of a sender, and may include the following steps:
  • Step 402 The client receives a task reminder message generation instruction related to the conference reminder message.
  • the client may provide multiple types of reminder messages; for example, the conference reminder message is used to implement a reminder function for a conference event, and the task reminder message is used to implement a reminder function for a task event.
  • the conference reminder message is used to implement a reminder function for a conference event
  • the task reminder message is used to implement a reminder function for a task event.
  • the client may provide multiple ways to generate a task reminder message. Therefore, there are multiple ways to obtain the above-mentioned task reminder message generation instruction related to the conference reminder message, which is not limited in this application.
  • the client may provide multiple ways to generate a task reminder message. Therefore, there are multiple ways to obtain the above-mentioned task reminder message generation instruction related to the conference reminder message, which is not limited in this application.
  • the client may display a task creation option in a presentation interface of the conference reminder message; then, when the client receives a trigger operation for the task creation option, the client may determine Receiving the task reminder message generating instruction.
  • the display interface of the meeting reminding message includes any interface that can display the meeting reminding message, such as a detailed display interface dedicated to the meeting reminding message, or a reminder message management page for collectively displaying the meeting reminding message and other reminding messages.
  • the client may also provide other trigger forms for the conference reminder message, such as marking a preset touch gesture on the display interface. Controlling speech, etc., this application does not limit this.
  • the “Task Creation Option” is just a form of options that can be used, and other task-related function options can also be applied here to replace the “Task Creation Option”; for example, the function option can be “Task” Editing Options or Task Modifying Options, when the Task Editing Option or Task Modifying Option is triggered, may display a task reminder message template related to the meeting reminder message for the sender to edit the template Or modify it to get the task reminder message related to the meeting reminder message.
  • the client may receive a user creation operation for a task reminder message, and a conference binding operation for the task reminder message; then, when the conference binding operation selects the conference reminder message
  • the client may determine to receive a task reminder message generation instruction related to the conference reminder message.
  • the client may provide a user with a creation option for the task reminder message.
  • the client may further provide the user with an alternate meeting reminder message (eg, the client has received, has The sent conference reminder message, etc., for the user to select a conference reminder message that is desired to be bound to the task reminder message by the user selection operation.
  • Step 404 the client determines the reminder object and the task description information.
  • Step 406 The client sends a task reminding message related to the meeting to the reminder object participating in the meeting corresponding to the meeting reminding message, and sends a task reminding message unrelated to the meeting to the reminding object not participating in the meeting.
  • the task reminder message includes the task description information.
  • the reminder object may include at least one of the following: a participant of the conference corresponding to the conference reminder message, and an object selected by the object selection operation received by the client. Therefore, the reminder may include two situations: participants of the conference, participants of the conference; for the participants of the conference, by sending a task reminder message related to the conference, the participants of the conference are convenient for the conference and the task. Association view, association process; for non-meeting participants, by sending a task reminder message unrelated to the meeting, making it non-perceived to the meeting, avoiding confusion, and helping to avoid leakage of meeting content.
  • the receiving client may display the task description information to the receiving party and display the meeting to the receiving party.
  • the conference description information is used to facilitate the association view and association processing of the task and the conference.
  • the task reminder message may include the conference description information in the conference reminder message, that is, the client may add at least one conference description information in the conference reminder message to the task reminder message, to receive The party will show.
  • the task reminder message may not include the conference description information; for example, in one case, the task alert message may include the identifier information of the conference reminder message, so that the receiver client receives the task reminder.
  • the server may obtain the corresponding at least one conference description information from the server according to the identifier information, or search for the corresponding conference reminder message and the conference description information thereof in the historical reminder message of the receiver client according to the identifier information;
  • the client may notify the server of the association information between the task reminder message and the conference reminder message, and the task reminder message may include a conference association identifier, where the conference association identifier may indicate to the receiver client.
  • the task reminder message has an associated conference reminder message, and the receiver client may initiate an inquiry to the server, so that the server returns at least one conference description of the corresponding conference reminder message to the receiver client based on the association information. information.
  • the receiving client may display the task description information to the receiving party when receiving the task reminding message, and the task reminding message in the related technology is not available. different.
  • the reminder object when the reminder object does not participate in the conference corresponding to the conference reminder message, the reminder object is equivalent to a participant independent of the conference, and thus the reminder object may have a task for the task reminder message.
  • the authority is managed to determine the task processing status of the reminder object, and the operation experience is the same as the task reminder message in the related art.
  • the reminder object when the reminder object participates in the conference, and the reminder object is configured as a task owner, the reminder object may have task management authority for the task reminder message.
  • the reminder object when the reminder object participates in the conference, and the reminder object is configured as a task participant, the reminder object may not have task management authority for the task reminder message;
  • the task participant is equivalent to a whole, and the task manager performs a unified task management operation on behalf of the whole.
  • the embodiment shown in FIG. 4 can be applied to a client running on an electronic device such as a mobile phone or a PC of a sender, so that a function of generating and sending a task reminder message is implemented through the client, in some cases.
  • the following can also be applied to the server, so that the server can implement the functions of generating and sending a task reminder message by running various steps included in the embodiment.
  • the embodiment shown in FIG. 4 may be applied to other possible execution entities. By executing the steps included in the embodiment, the execution entities implement functions such as generating and sending task reminding messages. The application does not limit this.
  • FIG. 5 is a flowchart of another method for reminding a task based on a receiver provided by an exemplary embodiment of the present application. As shown in FIG. 5, the method is applied to an electronic device of a receiver, and may include the following steps:
  • Step 502 The client receives a task reminder message related to the meeting reminder message.
  • Step 504 The client determines whether the logged-in user participates in the conference corresponding to the conference reminder message.
  • Step 506 When the logged-in user participates in the conference, the client displays task description information included in the task reminder message, and displays conference description information of the conference; the client is logged in When the user does not participate in the conference, the task description information included in the task reminder message is displayed.
  • the sender client may send a task reminder message related to the conference reminder message to all the reminder objects, and the client at the receiver determines the conference participation status of the logged-in user (ie, the receiver).
  • the corresponding display content helps to simplify the processing process of the sender client and improve communication efficiency.
  • the client when the logged-in user participates in the conference, the client may display the task description information and the conference description information.
  • the client may obtain the meeting description information included in the task reminding message, and display the meeting description information and the task description information included in the task reminding message.
  • the task reminder message may not contain meeting description information.
  • the task reminder message may include the identifier information of the conference reminder message, and the client may obtain the corresponding conference description information according to the identifier information; for example, the client may perform the historical reminder message according to the identifier information.
  • the client may initiate an inquiry to the server according to the identification information, so that the server returns a corresponding meeting to the client.
  • Reminder message or meeting description information may include a conference association identifier, so that the client determines that the task alert message has an associated conference reminder message, and the client may initiate an inquiry related to the task alert message to the server; Then, if the sender client informs the server in advance of the association relationship between the task reminder message and the conference reminder message, the server can determine the conference reminder message based on the association relationship, and the client can receive the server return.
  • the meeting reminder message or meeting description information may include a conference association identifier, so that the client determines that the task alert message has an associated conference reminder message, and the client may initiate an inquiry related to the task alert message to the server; Then, if the sender client informs the server in advance of the association relationship between the task reminder message and the conference reminder message, the server can determine the conference reminder message based on the association relationship, and the client can receive the server return.
  • the client may display at least a part of the content of the conference description information in a display area of the task reminding message, where the display area may include a detailed display interface dedicated to the task reminding message, or the foregoing The display area of the reminder message management page corresponding to the task reminder message.
  • the client may display at least a part of the content of the task description information in a display area of the meeting reminding message, where the display area may include a detailed display interface dedicated to the meeting reminding message, or the foregoing The display area of the reminder message management page corresponding to the meeting reminder message.
  • the client may display a first trigger option related to the conference reminder message in a display area of the task reminder message; wherein, when the first trigger option is triggered, the The client displays the conference description information in the conference reminder message.
  • the first triggering option may include summary information of the conference description information, and based on the triggering operation on the first triggering option, the client displays the detailed information of the conference description information, where The detailed information may be displayed in the display area of the task reminding message, or displayed on a separate interface (such as a detailed display interface or a temporary window interface dedicated to the meeting reminding message); when the client has not been informed of the meeting description information, the first triggering option
  • the indication options such as “click to learn the associated conference” may be included, and based on the triggering operation on the first trigger option, the client obtains the corresponding conference description information for display.
  • the client may display a second trigger option related to the task description information in a display area of the conference reminder message; wherein, when the second trigger option is triggered, the The client displays the task description information.
  • the first triggering option may include summary information of the task description information, and based on the triggering operation on the first triggering option, the client displays detailed information of the task description information, and the detailed information may be displayed in the meeting reminding message.
  • the display area or displayed in a separate interface (such as the specific display interface or temporary window interface dedicated to the task reminder message).
  • the client may perform task management on the task event according to a triggering operation for a task event corresponding to the task reminding message.
  • task management may include suspension, suspension, completion, etc. of a task event, which is not limited in this application.
  • the client can implement different types of task management; when the logged-in user has no privilege, the client may not be able to implement task management.
  • the embodiment shown in FIG. 5 can be applied to a client running on an electronic device such as a mobile phone or a PC of a receiving party, so that the receiving task reminding message, the task description information, and the conference description are implemented by the client.
  • the information and the like can also be applied to the server in some cases, so that the server can receive the task reminding message, display the task description information and the meeting description information to the receiving party by running the various steps included in the embodiment (for example, the task)
  • the description information and the conference description information are sent to the client corresponding to the receiver, etc.).
  • the embodiment shown in FIG. 5 may be applied to other possible execution entities, by which the execution subjects receive the task reminder message and display the task to the receiver by running the various steps included in the embodiment. Functions such as description information and meeting description information are not limited in this application.
  • the present invention associates the task reminding message with the meeting reminding message, so that the user can quickly view related information of the associated meeting in the process of processing the task, which helps improve the task processing efficiency.
  • the technical solution of the present application is described below by taking the enterprise instant messaging application "Enterprise WeChat" as an example. It is assumed that the mobile phone 13, the mobile phone 14 and the mobile phone 15 are running the enterprise WeChat client, and the server 11 is running the enterprise WeChat server. The enterprise WeChat client on the mobile phone 13-15 is respectively registered with a registered account of a different user, such as a mobile phone.
  • the mobile phone 13 is registered with the sender's registered account A (ie, user A), so that the mobile phone 13 is configured as the sender device corresponding to the sender, the mobile phone 13 is registered with the enterprise WeChat client 1 corresponding to the initiator, and the mobile phone 14- 15 respectively registering the registered account B (ie, user B) and the registered account C (ie, user C) of the recipient, so that the mobile phone 14-15 is configured as the recipient device corresponding to the two recipients, and the mobile phone 14-15
  • the enterprise WeChat client 2 and the enterprise WeChat client 3 corresponding to the two recipients are registered.
  • the user A can create a task reminding message related to the meeting reminding message on the mobile phone 13 and send it to the user B and the user C to implement the task reminding to the user B and the user C.
  • the technical solution of the present application is performed based on the process. A detailed description.
  • the conference detail interface 600 is used to display the conference description information of the conference reminder message, such as the conference topic "Discussing the problem of the X project, and further "Development needs", meeting time "Friday, April 28, 14:00 ⁇ 16:00", meeting place "Building Room 201, Building 2", etc., and the sender A of the meeting reminder message (ie "I"), The transmission time "12:21 yesterday", etc., is the same as the presentation of the conference description information in the related art.
  • the meeting task creation option 601 is also included.
  • the enterprise WeChat client 1 can determine that the user A needs to create a task reminder message related to the conference reminder message shown in FIG. 6, that is, "meeting task".
  • the enterprise WeChat client 1 can display the conference task creation interface 700 shown in FIG. 7 for the user A to create the conference task described above.
  • other meeting participants can also create a task reminder message related to the meeting reminder message; for example, as shown in FIG.
  • the enterprise WeChat client 2 on the mobile phone 14 may include a conference task creation option 801, when the enterprise WeChat client 2 detects the trigger operation of the conference task creation option 801 by the user B.
  • the enterprise WeChat client 2 can display the conference task creation interface 700 shown in FIG. 7 for the user B to create a corresponding conference task.
  • the operation of the conference task creation interface 700 shown in FIG. 7 is performed by the user A.
  • the user A can input the task description information of the conference task through the conference task creation interface 700.
  • the task description information may include a task topic, and the user A may input the task topic through an input box in the conference task creation interface 700 in which "Please input task content" is displayed.
  • the task theme may also include other content such as voice, video, picture, document, and the like, and is not limited to the text content input by the user A in the input box.
  • the task description information may include a task owner, and the user A may select the person in charge of the meeting task by triggering the “responsible person” option in the meeting task creation interface 700.
  • the enterprise WeChat client 1 can display the responsible person selection interface 900 shown in FIG. 9, and determine the corresponding task owner according to the operation of the responsible person selection interface 900 by the user A.
  • the enterprise WeChat client 1 may show the participants of the conference corresponding to the conference reminding message (ie, "meeting staff"), and of course, the user A may also trigger the "add other responsible person” option to The other people involved in the meeting chose to be the task leader.
  • the task description information may include a sending mode, and the user A may select an option of “in-app”, “sms”, “telephone” and the like in the meeting task creation interface 700 to select a sending manner of the meeting task.
  • “in-app” indicates that the enterprise WeChat client 1 will send the conference task through instant messaging technology
  • “sms” indicates that the enterprise WeChat client 1 will send the conference task through SMS
  • “telephone” indicates that the enterprise WeChat client 1 will The call description is initiated and the task description information such as the task title is played after the call is turned on.
  • User A can select one or more of the options "in-app", “sms”, “telephone”, etc., so that the enterprise WeChat client 1 sends the conference task in one or more corresponding ways.
  • the task description information may include a task deadline.
  • User A may set a deadline for the conference task by triggering a "cutoff time” option in the conference task creation interface 700, such as "May 11, 2017, Thursday 18" as shown in FIG. :00" and so on.
  • the task description information may include an expiration reminding function, and the user A may trigger the “expiration reminder” option in the interface 700 to set whether the expiration reminder needs to be implemented for the meeting task; when the expiration reminder needs to be implemented, You can further set the way to expire reminders (such as “in-app”, “sms”, “telephone”, etc.), time (such as “3 days before expiration”, etc.).
  • the task description information may include a task participant, and the user A may select a task participant of the conference task by triggering a “participant” option in the conference task creation interface 700.
  • Both the task participant and the task leader can receive the meeting task, but as indicated in the “Participants do not need to complete” as shown in Figure 7, when the task participant and the task leader are both meeting personnel, the task leader has the right
  • the meeting task implements the "complete operation" permission, while the task participant does not have the permission, which will be described in detail below.
  • the enterprise WeChat client 1 can send the above-mentioned conference task to the user B, the user C, and the like when detecting the "complete" option in the upper right corner of the user A triggering conference task creation interface 700.
  • the creation time and the sending time of the conference task are not related to the progress of the conference itself; in other words, before the conference starts, during the conference, after the conference ends, or at other times, The creation or sending operation of the conference task can be implemented, and this application does not limit this.
  • the enterprise WeChat client 1 can display the conference task that has been sent in the alert message management interface 1000 shown in FIG. 10; meanwhile, the alert message management interface 1000 is also used for Focus on other reminders that User A has sent or has received.
  • the conference task is displayed in the corresponding display area 1001, and the display area 1001 further includes the display content 1002 related to the conference task, so as to be in the conference reminder message and the conference task. Establish an association.
  • the presentation content 1002 may include "1 conference task, 0 completions" to indicate that there is an associated conference task for the corresponding conference reminder message.
  • the enterprise WeChat client 1 may show the task details interface 1100 shown in FIG. 11 to show the task description information of the conference task in detail.
  • the reminder message management interface 1200 shown in FIG. 12 in the display area 1201 corresponding to the meeting reminding message, the display content corresponding to the meeting task is “1 meeting task, 0 completions.
  • the summary information 1203 of the task description information of the conference task may be further included, and the summary information 1202 may include “ ⁇ 3 solutions are proposed tomorrow...”, etc., and the display area 1201 may be reduced.
  • Remind the occupation of the message management interface 1200 in order to display more reminder messages on the mobile phone 13 at the same time), and may also prompt the user A to the task description information of the conference task to a certain extent, so that the user A may not need to be in some cases. Going to the task details interface 1100 shown in FIG. 11; of course, if the triggering operation for the prompt information 1202 or the summary information 1203 is detected, the enterprise WeChat client 1 can still display the task details interface 1100 shown in FIG. 11 to facilitate the user A. Check it out.
  • the display content corresponding to the meeting task may include the detailed information of the task description information.
  • User A is the person responsible for the meeting task, and thus User A has administrative rights to the meeting task.
  • a "complete task” option 1102 may be included in the task details interface 1100.
  • the enterprise WeChat client 1 may perform a "complete task" management for the meeting task. operating.
  • a "complete task” option 1204 may be included in the reminder message management interface 1200 shown in FIG. 12
  • a "complete task” option 1302 may be included in the reminder message management interface 1300 shown in FIG. 13, and the enterprise WeChat client 1 is included.
  • the management task of "complete task” can be implemented on the conference task according to the trigger operation of the user A for the option 1204 or the option 1302.
  • the enterprise WeChat client 1 can display related content of the task meeting in the display area 1401 of the meeting reminder message, and does not show the above-mentioned "complete task”.
  • the option prevents User A from performing the "Complete Task" management operation for the meeting task.
  • the "end task” option 1103 for the conference task may be included, so that when the user A triggers the option 1103, the enterprise WeChat Client 1 can terminate the conference task.
  • User A's "terminating task” permission for the meeting task is related to the identity of the user A as the creator, and thus, as shown in FIG. 15, even if the user A is not the person in charge of the meeting task, the task details interface shown in FIG. The "End Task” option 1501 can still be included in 1500 for User A to terminate the conference task.
  • the task details interface 1600 shown by the enterprise WeChat client 3 shown in FIG. 16 the user C serves as the conference personnel and the participants of the conference task, and the task details interface 1600 can show the discussion of the X project with the conference.
  • the related content of the problem" is 1601; however, since the user C is not the person in charge of the above-mentioned conference task, the task details interface 1600 does not exhibit the "complete task” option, that is, the user C does not have the task of the conference. Completing the task" permission; similarly, since the user C is not the creator of the meeting task, the task details interface 1600 does not exhibit the "end task” option, ie the user C does not have the "end task” permission for the meeting task .
  • the above-mentioned conference task can be used as a relatively independent task reminder message to be managed by the enterprise WeChat client.
  • the task description content of the conference task may be displayed in the display area 1701 in the alert message management interface 1700, and the display area is displayed.
  • the prompt content 1702 related to the conference reminding message (that is, the corresponding conference) may also be included in the 1701.
  • the prompt content 1702 may include “belonging to the conference: discussing the problem of the X project”, etc.; meanwhile, when the user B is the The person in charge of the meeting task may also include a "Complete Task” option 1703 in the display area 1701 so that the user B can perform the "Complete Task” operation on the meeting task by triggering the option 1703.
  • the task description content of the conference task can be displayed on the reminder message management interface 1800.
  • the presentation area 1801 may also include prompt content 1802 related to the conference reminder message (ie, corresponding to the conference), but does not include the "complete task" option.
  • the conference task can be used as an auxiliary message of the conference reminder message (can be expressed as the “task follow-up” shown in FIG. 18 . , different from the "task" shown in FIG. 17, but not a normal task reminder message, so that the affiliate message cannot be displayed in the reminder message management interface 1800 shown in FIG. 18, but can only be performed by the above-mentioned conference reminder message.
  • Indirect call For example, the user C can find the meeting reminding message in the reminder message management interface 1800, and the content of the meeting task can be included in the display area of the meeting reminding message (similar to the display content 1002 shown in FIG. 10). C can enter the task details interface 1600 as shown in FIG. 16 through the related content to view the corresponding task description information in detail.
  • the participant of the conference task may not be the conference attendant of the conference, and the task description information of the conference task may be normally displayed on the alert message management interface 1900 shown in FIG. 19 shown by the corresponding enterprise WeChat client.
  • the display area 1901 may also include a "Complete Task” option 1902, ie the participant has "Complete Task” permission for the meeting task; in other words, the meeting task for the participant, It is no different from other task reminder messages in the related art.
  • the task reminder message is associated with the conference reminder message, so that after receiving the task reminder message, the receiver client may display the conference description information of the conference reminder message related to the task reminder message. So that the recipient can view it conveniently.
  • the task reminder message may be associated with the conference event, and the receiver of the task reminder message may also display the conference description information of the conference.
  • FIG. 20 is a flowchart of still another method for reminding a task based on a sender according to an exemplary embodiment of the present application. As shown in FIG. 20, the method is applied to an electronic device of a sender, and may include the following steps:
  • step 2002 the client receives a task reminder message generation instruction related to the conference.
  • the client since the conference reminder message is used to implement the reminding function for the conference event, the client can also implement other functions related to the conference event, and thus the client can notify the message and the conference (ie, the conference event) by using the task.
  • the receiving client can obtain and display the corresponding meeting description information.
  • a management calendar function can be provided. For example, as shown in FIG. 21, by showing the management calendar 2100 and showing the related business matters on a daily basis on the management calendar 2100, the user can be helped to quickly grasp the processing status of the enterprise matters, and facilitate the reasonable arrangement of the subsequent work. Taking the management calendar 2100 shown in FIG. 21
  • the business matter existing within the date may be displayed, for example, in the display area 2101 below the management calendar 2100, Descriptive information showing a task event (corresponding to a black dot at the bottom of "28") and a meeting event (corresponding to a white dot at the bottom of "28") existing on "April 28, 2017", the description information may be The summary information shown in FIG. 22 (when a certain summary information is selected, the corresponding detailed information may be further shown), or the description information may be detailed information.
  • the corresponding number "28" can be highlighted to distinguish it from other dates, such as the manner in which the number 28 is adjusted to white and a black background is added in FIG. 21; At the same time, for the current date, it can also be highlighted by means of the selected date and other dates. For example, "April 26, 2017” can add a ring.
  • type prompt information for the enterprise item may be displayed, such as the word "task” corresponding to the task event shown in FIG. 21, and the word “meeting” corresponding to the meeting event.
  • the type prompt information may be matched with the enterprise item prompt information such as the black dot and the white dot in the management calendar, for example, the type prompt information and the enterprise item prompt information adopt the same or similar display attributes, so that the user The association between the two can be obtained from the visual perception, which helps to enhance the user experience; for example, the display attribute can include color, grayscale, transparency, etc., which is not limited in this application.
  • a "meeting task” option 2102 may be displayed in the associated area of the conference event.
  • the triggering operation for the option 2102 it may be determined to be received as shown in FIG.
  • the option 2102 can also take other forms, such as "task creation”, “task editing”, “task modification”, etc., and this application does not limit this.
  • a form such as “task editing” or “task modification”
  • a task reminding message template related to the meeting may be displayed for the sender. After editing or modifying the template, you can get the task reminder message related to the meeting.
  • the reminder object may include at least one of the following: a participant of the conference, and an object selected by the object selection operation received by the client.
  • the client may display the participant of the conference and the associated user of the sender as alternate users, so that the sender selects the user who wishes to be the object of the reminder.
  • the client may use the participant of the conference as the reminder object by default, and display the associated user of the sender as an alternative user, so that the sender further adds the user who wishes to be the object of the reminder;
  • the participants of the meeting can be set to be reminders, and in another case, although the participants of the meeting are added as reminders by default, the sender can adjust according to the actual situation.
  • Step 2006 The client sends a task reminder message related to the conference to the reminder object, where the task reminder message includes the task description information.
  • the task reminder message may further include conference description information of the conference, that is, the client may add at least one conference description information in the conference reminder message to the task reminder message, to the receiver. Show it.
  • the conference description information may exist in multiple sources; for example, in the embodiment shown in FIG. 21, the management calendar 2100 may record the conference description information of the conference event, so that the client can learn the conference description information from the management calendar 2100; Alternatively, the client may determine a conference reminder message corresponding to the conference event, and obtain corresponding conference description information from the conference alert message.
  • the task reminder message may not include the conference description information; for example, in one case, the task alert message may include the identifier information of the conference, so that the receiver client receives the task reminder message. Obtaining at least one conference description information from the server according to the identifier information, or searching for a corresponding conference reminder message or a conference event in the historical reminder message of the receiver client according to the identifier information, thereby obtaining corresponding conference description information.
  • the client may notify the server of the association information between the task reminder message and the conference, and the task reminder message may include a conference association identifier, and the conference association identifier may be sent to the receiver client. It is indicated that the task reminder message has an associated conference, and the receiver client may initiate an inquiry to the server, so that the server returns the corresponding at least one conference description information to the receiver client based on the association information.
  • the reminder object when the reminder object does not participate in the conference, the reminder object is equivalent to a participant independent of the conference, and thus the reminder object may have task management authority for the task reminder message, so as to facilitate Determine the task processing status of the reminder object.
  • the reminder object when the reminder object participates in the conference, and the reminder object is configured as a task owner, the reminder object may have task management authority for the task reminder message.
  • the reminder object when the reminder object participates in the conference, and the reminder object is configured as a task participant, the reminder object may not have task management authority for the task reminder message;
  • the task participant is equivalent to a whole, and the task manager performs a unified task management operation on behalf of the whole.
  • FIG. 22 is a flowchart of still another method for reminding a task based on a sender according to an exemplary embodiment of the present application. As shown in FIG. 22, the method is applied to an electronic device of a sender, and may include the following steps:
  • Step 2202 The client generates a task reminder message related to the conference according to the reminder object, the task description information, and the conference.
  • Step 2204 The client sends the task reminder message to the reminder object, where the task reminder message includes the task description information.
  • the embodiments shown in FIG. 20 and FIG. 22 can be applied to a client running on an electronic device such as a mobile phone or a PC of a sender, so that a function of generating and sending a task reminder message is implemented through the client.
  • it can also be applied to the server, so that the server can implement the functions of generating and sending a task reminder message by running various steps included in the embodiment.
  • the embodiments shown in FIG. 20 and FIG. 22 may be applied to other possible execution subjects, by which the execution main body is configured to generate and send task reminding messages, etc. by running the various steps included in the embodiment. Function, this application does not limit this.
  • FIG. 23 is a flowchart of still another task reminding method based on the receiver provided by an exemplary embodiment of the present application. As shown in FIG. 23, the method is applied to an electronic device of a receiver, and may include the following steps:
  • step 2302 the client receives a task reminder message related to the conference.
  • Step 2304 The client displays task description information included in the task reminder message, and displays conference description information of the conference.
  • the client may obtain the meeting description information included in the task reminding message, and display the meeting description information and the task description information included in the task reminding message.
  • the task reminder message may not include the conference description information.
  • the task reminder message may include the identifier information of the conference, and the client may obtain the corresponding conference description information according to the identifier information; for example, the client may perform the search in the history reminder message according to the identifier information.
  • the client may initiate an inquiry to the server according to the identifier information, so that the server sends the conference to the client. Returns the corresponding meeting description information.
  • the task reminder message may include a conference association identifier, so that the client determines that the task alert message has an associated conference, and the client may initiate an inquiry related to the task alert message to the server; If the sender client informs the server in advance of the association relationship between the task reminder message and the conference, the server can determine the conference based on the association relationship, and the client can receive the conference description of the conference returned by the server. information.
  • the client may display at least a part of the content of the conference description information in a display area of the task reminding message, where the display area may include a detailed display interface dedicated to the task reminding message, or the foregoing The display area of the reminder message management page corresponding to the task reminder message.
  • the client may display at least a part of the content of the task description information in a display area of the meeting reminding message corresponding to the meeting, and the display area may include a detailed display interface dedicated to the meeting reminding message. Or the display area corresponding to the meeting reminding message in the reminder message management page.
  • the client may display a first trigger option related to the conference in a display area of the task reminder message; wherein, when the first trigger option is triggered, the client The meeting description information is displayed.
  • the first triggering option may include summary information of the conference description information, and based on the triggering operation on the first triggering option, the client displays the detailed information of the conference description information, where The detailed information may be displayed in the display area of the task reminding message, or displayed on a separate interface (such as a detailed display interface or a temporary window interface dedicated to the meeting reminding message); when the client has not been informed of the meeting description information, the first triggering option
  • the indication options such as “click to learn the associated conference” may be included, and based on the triggering operation on the first trigger option, the client obtains the corresponding conference description information for display.
  • the client may display a second trigger option related to the task description information in a display area of the conference reminder message; wherein, when the second trigger option is triggered, the The client displays the task description information.
  • the first triggering option may include summary information of the task description information, and based on the triggering operation on the first triggering option, the client displays detailed information of the task description information, and the detailed information may be displayed in the meeting reminding message.
  • the display area or displayed in a separate interface (such as the specific display interface or temporary window interface dedicated to the task reminder message).
  • the client may perform task management on the task event according to a triggering operation for a task event corresponding to the task reminding message.
  • task management may include suspension, suspension, completion, etc. of a task event, which is not limited in this application.
  • the client can implement different types of task management; when the logged-in user has no privilege, the client may not be able to implement task management.
  • the technical solution of the present application is described by taking the association between the task reminding message and the meeting reminding message, the task reminding message, and the meeting as an example.
  • the “task” may have different understandings in different situations; for example, in some scenarios, the “task” may be understood as a pending item (for example, in a work scenario, Expressed as work content), the bearer of the “task” (such as the reminder object in the present application) needs to complete the pending item and provide feedback to the sender of the task reminder message (such as “notification of completing the task”); In other scenarios, a "task” can be understood as a notice or similar descriptive information.
  • the bearer of the "task” may need to handle the matter, or may only need to know the notice; in other scenarios, Other understandings are possible, and this application does not limit this.
  • some simple "tasks” can contain only one pending item or notice, while some more complex "tasks" may contain multiple pending items or notices.
  • the embodiment shown in FIG. 23 can be applied to a client running on an electronic device such as a mobile phone or a PC of a receiving party, so that the receiving task reminding message, the task description information, and the conference description are implemented by the client.
  • the information and the like can also be applied to the server in some cases, so that the server can receive the task reminding message, display the task description information and the meeting description information to the receiving party by running the various steps included in the embodiment (for example, the task)
  • the description information and the conference description information are sent to the client corresponding to the receiver, etc.).
  • the embodiment shown in FIG. 23 may be applied to other possible execution entities, by which the execution subjects receive the task reminder message and display the task to the receiver by running the various steps included in the embodiment. Functions such as description information and meeting description information are not limited in this application.
  • FIG. 24 is a flowchart of a method for generating a reminder message according to an exemplary embodiment of the present application. As shown in FIG. 24, the method may include the following steps:
  • step 2402 the client receives an alert message generation instruction related to the first alert message.
  • the client can provide multiple types of reminder messages; for example, the conference reminder message is used to implement a reminder function for the conference event, the task reminder message is used to implement the reminder function for the task event, and the reminder message is used for reminding Implement reminders for approval events, etc.
  • the conference reminder message is used to implement a reminder function for the conference event
  • the task reminder message is used to implement the reminder function for the task event
  • the reminder message is used for reminding Implement reminders for approval events, etc.
  • the first reminder message and the second reminder message may be any of the above types of reminder messages.
  • the first reminder message and the second reminder message may be of the same type.
  • the first reminder message and the second reminder message may be the task type, the conference type, or the reminder type.
  • the first reminder message and the second reminder message may be of different types.
  • the embodiment shown in FIG. 24 is equivalent to the embodiment shown in FIG. 2;
  • the first reminder message may be a task type
  • the second reminder message may be a conference type
  • the first reminder message may be a conference type
  • the second reminder message may be a reminder type
  • the second reminder message may be a reminder type.
  • the client may provide multiple ways to generate the second reminder message. Therefore, there are multiple ways to obtain the above-mentioned reminder message generating instruction related to the first reminder message, which is not limited in this application.
  • the client may provide multiple ways to generate the second reminder message. Therefore, there are multiple ways to obtain the above-mentioned reminder message generating instruction related to the first reminder message, which is not limited in this application.
  • the client may display a second reminder message creation option in the presentation interface of the first reminder message; then, the client receives an option for creating the second reminder message.
  • the display interface of the first reminder message includes any interface that can display the first reminder message, such as a detail display interface dedicated to the first reminder message, or a reminder message for collectively displaying the first reminder message and other reminder messages. Management page, etc.
  • the client may also provide other trigger forms for the first reminder message, such as drawing on the above display interface.
  • the preset touch gesture, the control voice, and the like are not limited in this application.
  • the "second reminder message creation option” is just a form of options that can be adopted, and other task-related function options can also be applied here to replace the "second reminder message creation option"; for example,
  • the function option may adopt a “second reminder message editing option” or a “second reminder message modification option”, and when the “second reminder message editing option” or the “second reminder message modification option” is triggered, the A second reminder message template related to the reminder message, for the sender to edit or modify the template, to obtain a second reminder message related to the first reminder message.
  • the client may receive a user creation operation for the second reminder message, and a first reminder message binding operation for the second reminder message; then, when the first reminder message is tied When the first alert message is selected, the client may determine to receive the alert message generating instruction related to the first alert message. For example, the client may provide a user with a creation option for the second reminder message. When the user triggers the creation option by the user creation operation, the client may further provide the user with an alternative first reminder message (eg, the client has received The first reminder message that has been sent, for the user to select the first reminder message that is desired to be bound to the second reminder message by the user selection operation.
  • an alternative first reminder message eg, the client has received The first reminder message that has been sent, for the user to select the first reminder message that is desired to be bound to the second reminder message by the user selection operation.
  • Step 2404 the client determines the reminder object and the reminder event description information.
  • the reminder object may include at least one of the following: an associated user of the first reminder message (for example, when the first reminder message is a conference reminder message, the associated user may be a conference participant), The object selected by the object selection operation received by the client.
  • the client may display the associated user of the first reminder message and the associated user of the sender as an alternate user, so that the sender selects the user who wishes to be the object of the reminder.
  • the client may use the associated user of the first reminder message as the reminder object by default, and display the associated user of the sender as an alternative user, so that the sender further adds the hope as the reminder object.
  • the associated user of the first reminder message may be set to be a reminder object, and in another case, although the associated user of the first reminder message is defaulted Added as a reminder, but the sender can adjust according to the actual situation.
  • Step 2406 The client sends a second reminder message related to the first reminder message to the reminder object, where the second reminder message includes the reminder event description information.
  • the second reminder message includes the second reminder event description information
  • the second reminder message may further include the first reminder event description information in the first reminder message
  • the client may At least one first reminder event description information in the reminder message is added to the second reminder message for presentation to the recipient.
  • the second reminder message may not include the first reminder event description information; for example, in one case, the second reminder message may include the identifier information of the first reminder message, so that the recipient client After receiving the second reminding message, the terminal may obtain corresponding at least one first reminding event description information from the server according to the identifier information, or search for a corresponding first in the historical reminder message of the receiving client according to the identifier information.
  • the conference association identifier may be included, and the conference association identifier may indicate to the receiver client that the second reminder message has an associated first reminder message, and the receiver client may initiate an inquiry to the server, so that the server is based on the association. And returning, to the receiving client, at least one first reminding event description information of the corresponding first reminding message.
  • the reminder object when the reminder object is not an associated user of the first reminder message, the reminder object may have a management right for a corresponding event of the second reminder message, so as to determine that the reminder object is Corresponding to the processing status of the event.
  • the reminder object when the reminder object belongs to an associated user of the first reminder message, and the reminder object is configured as an event person in charge of a corresponding event of the second reminder message, the reminder object may Has administrative rights to the corresponding event.
  • the reminder object when the reminder object belongs to an associated user of the first reminder message, and the reminder object is configured as an event participant of a corresponding event of the second reminder message, the reminder object may not have the same Corresponding to the management authority of the event; at this time, the event leader and the event participant are equivalent to a whole, and the event manager performs a unified event management operation on behalf of the whole.
  • FIG. 25 is a flowchart of another method for generating an alert message according to an exemplary embodiment of the present application. As shown in FIG. 25, the method may include the following steps:
  • Step 2502 The client generates a second reminder message related to the first reminder message according to the reminder object, the reminder event description information, and the first reminder message.
  • Step 2504 the client sends the second reminder message to the reminder object, where the second reminder message includes the reminder event description information.
  • the embodiments shown in FIG. 24 and FIG. 25 can be applied to a client running on an electronic device such as a mobile phone or a PC of a sender, so that a function of generating and transmitting a second reminder message is implemented through the client.
  • the server can also be applied to the server, so that the server can implement the functions of generating and sending the second reminder message by running various steps included in the embodiment.
  • the embodiments shown in FIG. 24 and FIG. 25 may also be applied to other possible execution entities, by which the execution body generates and sends a second reminder message by running the various steps included in the embodiment. Other functions, this application does not limit this.
  • FIG. 26 is a flowchart of a method for displaying an alert message according to an exemplary embodiment of the present application. As shown in FIG. 26, the method may include the following steps:
  • Step 2602 the client receives a second reminder message related to the first reminder message.
  • Step 2604 The client displays the second reminder event description information included in the second reminder message, and displays the first reminder event description information corresponding to the first reminder message.
  • the client may obtain the first reminder event description information included in the second reminder message, and describe the first reminder event information and the first reminder event.
  • the second reminder event description information included in the second reminder message is displayed.
  • the second reminder message may not include the first reminder event description information.
  • the second reminder message may include the identifier information of the first reminder message, and the client may obtain the corresponding first reminder event description information according to the identifier information; for example, the client may be based on the identifier information. Searching in the historical reminder message to find the corresponding first reminder message, and obtaining the first reminder event description information included in the first reminder message; for example, the client may initiate an inquiry to the server according to the identifier information, The server returns a corresponding first reminder message or first reminder event description information to the client.
  • the second reminder message may include a conference association identifier, so that the client determines that the second alert message has an associated first alert message, and the client may initiate the second alert message to the server.
  • the server may determine the first reminder message based on the association relationship, The client may receive the first reminder message or the first reminder event description information returned by the server.
  • the client may display at least a part of the content of the first reminder event description information in a display area of the second reminder message, where the display area may include a specific display dedicated to the second reminder message.
  • the client may display at least a part of the content of the second reminder event description information in a display area of the first reminder message, where the display area may include a specific display dedicated to the first reminder message.
  • the client may display a first trigger option related to the first reminder message in a display area of the second reminder message; wherein, when the first trigger option is triggered, The client displays the first reminder event description information in the first reminder message.
  • the first trigger option may include summary information of the first reminder event description information, and the first one is shown by the client based on the triggering operation on the first trigger option.
  • the detailed information may be displayed in the display area of the second reminder message, or displayed on a separate interface (such as a specific display interface or temporary window interface dedicated to the first reminder message);
  • the first trigger option may include an indication option such as “click to learn the associated event”, and based on the triggering operation on the first trigger option, the client obtains the corresponding first reminder event description. Information for display.
  • the client may display a second trigger option related to the second reminder event description information in a display area of the first reminder message; wherein, when the second trigger option is triggered
  • the client displays the second reminder event description information.
  • the first triggering option may include summary information of the second reminding event description information, and based on the triggering operation on the first triggering option, the client displays the detailed information of the second reminding event description information, the detailed information It can be displayed in the display area of the first reminder message, or displayed in a separate interface (such as a detail display interface or a temporary window interface dedicated to the second reminder message).
  • the client may perform event management on the corresponding event according to a triggering operation of the corresponding event for the second reminder message.
  • event management may include suspension, suspension, completion, etc. of the corresponding event, which is not limited in this application.
  • the client can implement different types of event management; when the logged-in user has no privilege, the client may not be able to implement event management.
  • the embodiment shown in FIG. 26 can be applied to a client running on an electronic device such as a mobile phone or a PC of a receiving party, so that receiving the second reminding message and displaying the second reminding event description through the client is implemented.
  • the information, the first reminder event description information, and the like may be applied to the server in some cases, so that the server can receive the second reminder message and display the second reminder to the receiver by running the steps included in the embodiment.
  • the event description information and the first reminder event description information (such as sending the second reminder event description information and the first reminder event description information to the client corresponding to the recipient, etc.) and the like.
  • the embodiment shown in FIG. 26 may be applied to other possible execution entities, by which the execution entities receive the second reminder message and display to the recipient by running the various steps included in the embodiment.
  • the second reminder event description information and the first reminder event description information and the like are not limited in this application.
  • FIG. 27 shows a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application.
  • the electronic device includes a processor 2702, an internal bus 2704, a network interface 2706, a memory 2708, and a non-volatile memory 2710, and of course may also include hardware required for other services.
  • the processor 2702 reads the corresponding computer program from the non-volatile memory 2710 into the memory 2708 and then operates to form a task reminder device on a logical level.
  • the present application does not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution body of the following processing flow is not limited to each logical unit, and may be Hardware or logic device.
  • the task reminding device may include:
  • the first instruction receiving unit 2801 is configured to enable the client to receive a task reminder message generating instruction related to the meeting reminding message;
  • the first determining unit 2802 is configured to enable the client to determine the reminder object and the task description information
  • the first sending unit 2803 causes the client to send a task reminding message related to the meeting reminding message to the reminding object, where the task reminding message includes the task description information.
  • the first instruction receiving unit 2801 is specifically configured to:
  • the first instruction receiving unit 2801 is specifically configured to:
  • Having the client receive a user creation operation for a task reminder message, and a conference binding operation for the task reminder message;
  • the client is determined to receive a task reminder message generation instruction related to the conference reminder message.
  • the task reminder message further includes conference description information in the conference reminder message.
  • the reminder object includes at least one of the following:
  • the participant of the conference corresponding to the conference reminder message, and the object selected by the object selection operation received by the client The participant of the conference corresponding to the conference reminder message, and the object selected by the object selection operation received by the client.
  • the reminder object When the reminder object does not participate in the conference corresponding to the conference reminder message, the reminder object has task management authority for the task reminder message;
  • the reminder object When the reminder object participates in the conference, and the reminder object is configured as a task owner, the reminder object has task management authority for the task reminder message.
  • the task reminding device may include:
  • the first message receiving unit 2901 is configured to enable the client to receive a task reminder message related to the meeting reminder message;
  • the first display unit 2902 is configured to enable the client to display the task description information included in the task reminder message, and display the conference description information in the conference reminder message.
  • the first display unit 2902 causes the client to display the task description information included in the task reminder message and display the conference description information in the conference reminder message by using at least one of the following manners:
  • the first display unit 2902 causes the client to display the task description information included in the task reminder message and display the conference description information in the conference reminder message by using at least one of the following manners:
  • it also includes:
  • the task management unit 2903 is configured to perform task management on the task event according to a trigger operation of the task event corresponding to the task reminder message.
  • the task reminding device may include:
  • the second instruction receiving unit 3001 causes the client to receive a task reminder message generating instruction related to the meeting reminding message;
  • the second determining unit 3002 is configured to enable the client to determine the reminder object and the task description information
  • the second sending unit 3003, the client sends a task reminder message related to the meeting to the reminder object participating in the meeting corresponding to the meeting reminding message, and sends the reminder object not participating in the meeting to the meeting object.
  • the task reminder message includes the task description information.
  • the task reminding device may include:
  • the second message receiving unit 3101 is configured to enable the client to receive a task reminder message related to the meeting reminder message;
  • the user type determining unit 3102 is configured to enable the client to determine whether the logged-in user participates in the conference corresponding to the conference reminder message;
  • the second display unit 3103 is configured to: when the logged-in user participates in the conference, display the task description information included in the task reminder message, and display conference description information of the conference; When the logged-in user does not participate in the conference, the task description information included in the task reminder message is displayed.
  • the task reminding device may include:
  • the fourth instruction receiving unit 3201 causes the client to receive a task reminder message generation instruction related to the conference
  • the fourth determining unit 3202 is configured to enable the client to determine the reminder object and the task description information
  • the fifth sending unit 3203 is configured to enable the client to send a task reminding message related to the meeting to the reminding object, where the task reminding message includes the task description information.
  • the task reminding device may include:
  • the second generating unit 3301 is configured to enable the client to generate a task reminding message related to the meeting according to the reminding object, the task description information, and the meeting;
  • the sixth sending unit 3302 is configured to enable the client to send the task reminder message to the reminder object, where the task reminder message includes the task description information.
  • the task reminding device may include:
  • the fourth message receiving unit 3401 is configured to enable the client to receive a task reminder message related to the conference;
  • the fourth display unit 3402 is configured to enable the client to display task description information included in the task reminder message, and display conference description information of the conference.
  • FIG. 35 shows a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application.
  • the electronic device includes a processor 3502, an internal bus 3504, a network interface 3506, a memory 3508, and a non-volatile memory 3510, and of course may also include hardware required for other services.
  • the processor 3502 reads the corresponding computer program from the non-volatile memory 3510 into the memory 3508 and then operates to generate a reminder message generating means on a logical level.
  • the present application does not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution body of the following processing flow is not limited to each logical unit, and may be Hardware or logic device.
  • the generating device of the reminder message may include:
  • the third instruction receiving unit 3601 causes the client to receive an alert message generating instruction related to the first reminder message
  • the third determining unit 3602 is configured to enable the client to determine the reminder object and the reminder event description information
  • the third sending unit 3603 is configured to enable the client to send a second reminder message related to the first reminder message to the reminder object, where the second reminder message includes the reminder event description information.
  • the generating device of the reminder message may include:
  • the first generating unit 3701 is configured to enable the client to generate a second reminder message related to the first reminder message according to the reminder object, the reminder event description information, and the first reminder message;
  • the fourth sending unit 3702 is configured to enable the client to send the second reminder message to the reminder object, where the second reminder message includes the reminder event description information.
  • FIG. 38 shows a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application.
  • the electronic device includes a processor 3802, an internal bus 3804, a network interface 3806, a memory 3808, and a non-volatile memory 3810.
  • the processor 3802 reads the corresponding computer program from the non-volatile memory 3810 into the memory 3808 and then runs to form a display device for the alert message on the logical level.
  • the present application does not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution body of the following processing flow is not limited to each logical unit, and may be Hardware or logic device.
  • the display device of the reminder message may include:
  • the third message receiving unit 3901 is configured to enable the client to receive a second reminder message related to the first reminder message
  • the third display unit 3902 is configured to display the second reminder event description information included in the second reminder message, and display the first reminder event description information corresponding to the first reminder message.
  • the third display unit 3902 is specifically configured to:
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, and a game control.
  • a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
  • first, second, third, etc. may be used in this application to describe various information, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present application.
  • second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请提供一种任务提醒方法及装置、提醒消息的生成和展示方法及装置，该任务提醒方法可以包括：客户端接收与会议提醒消息相关的任务提醒消息生成指令；所述客户端确定提醒对象和任务描述信息；所述客户端向所述提醒对象发送与所述会议提醒消息相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。通过本申请的技术方案，可以在会议提醒消息与任务提醒消息之间建立关联，便于用户在处理任务的过程中，快捷查看关联会议的相关信息，有助于提升任务处理效率。

Description

任务提醒方法及装置、提醒消息的生成和展示方法及装置
本申请要求2017年06月06日递交的申请号为201710417476.9、发明名称为“任务提醒方法及装置、提醒消息的生成和展示方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及终端技术领域，尤其涉及一种任务提醒方法及装置、提醒消息的生成和展示方法及装置。
背景技术
在相关技术中，移动化企业办公平台被越来越广泛地应用于企业、教育机构、政府机关等各类团体的办公过程，不仅能够提升用户之间的沟通效率、降低沟通成本，而且能够有效提升用户的事件处理效率和办公效率。
举例而言，移动化企业办公平台可以用于发送提醒消息，该提醒消息可以基于移动化企业办公平台提供的即时通讯功能而发送，也可以基于短信、电话等传统的移动通讯方式而发送，以确保提醒效果。
在相关技术中，提醒消息之间相互独立。例如，用户分别在时刻A、时刻B创建与事件1相关的提醒消息1、提醒消息2，虽然提醒消息1和提醒消息2在客观上均与事件1相关，但是用户在查看提醒消息1时，并不能够获知提醒消息2的内容、甚至已经遗忘提醒消息2的存在，可能导致用户无法顺利处理事件1。而在一些情况下，即便用户模糊地记得提醒消息2的存在，也可能由于提醒消息的数量较多，导致用户无法快捷地查找到该提醒消息2。
发明内容
有鉴于此，本申请提供一种任务提醒方法及装置、提醒消息的生成和展示方法及装置，可以在会议提醒消息与任务提醒消息之间建立关联，便于用户在处理任务的过程中，快捷查看关联会议的相关信息，有助于提升任务处理效率。
为实现上述目的，本申请提供技术方案如下：
根据本申请的第一方面，提出了一种任务提醒方法，包括：
客户端接收与会议提醒消息相关的任务提醒消息生成指令；
所述客户端确定提醒对象和任务描述信息；
所述客户端向所述提醒对象发送与所述会议提醒消息相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第二方面，提出了一种任务提醒方法，包括：
客户端接收与会议提醒消息相关的任务提醒消息；
所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息。
根据本申请的第三方面，提出了一种任务提醒方法，包括：
客户端接收与会议提醒消息相关的任务提醒消息生成指令；
所述客户端确定提醒对象和任务描述信息；
所述客户端向参与所述会议提醒消息对应的会议的提醒对象发送与所述会议相关的任务提醒消息、向未参与所述会议的提醒对象发送与所述会议无关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第四方面，提出了一种任务提醒方法，包括：
客户端接收与会议提醒消息相关的任务提醒消息；
所述客户端确定已登录用户是否参与所述会议提醒消息对应的会议；
所述客户端在所述已登录用户参与所述会议时，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息；所述客户端在所述已登录用户未参与所述会议时，展示所述任务提醒消息包含的任务描述信息。
根据本申请的第五方面，提出了一种提醒消息的生成方法，包括：
客户端接收与第一提醒消息相关的提醒消息生成指令；
所述客户端确定提醒对象和提醒事件描述信息；
所述客户端向所述提醒对象发送与所述第一提醒消息相关的第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
根据本申请的第六方面，提出了一种提醒消息的生成方法，包括：
客户端根据提醒对象、提醒事件描述信息和第一提醒消息，生成与所述第一提醒消息相关的第二提醒消息；
所述客户端向所述提醒对象发送所述第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
根据本申请的第七方面，提出了一种提醒消息的展示方法，包括：
客户端接收与第一提醒消息相关的第二提醒消息；
所述客户端展示所述第二提醒消息包含的第二提醒事件描述信息，以及展示所述第一提醒消息对应的第一提醒事件描述信息。
根据本申请的第八方面，提出了一种任务提醒方法，包括：
客户端接收与会议相关的任务提醒消息生成指令；
所述客户端确定提醒对象和任务描述信息；
所述客户端向所述提醒对象发送与所述会议相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第九方面，提出了一种任务提醒方法，包括：
客户端根据提醒对象、任务描述信息和会议，生成与所述会议相关的任务提醒消息；
所述客户端向所述提醒对象发送所述任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第十方面，提出了一种任务提醒方法，包括：
客户端接收与会议相关的任务提醒消息；
所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息。
根据本申请的第十一方面，提出了一种任务提醒装置，包括：
第一指令接收单元，使客户端接收与会议提醒消息相关的任务提醒消息生成指令；
第一确定单元，使所述客户端确定提醒对象和任务描述信息；
第一发送单元，使所述客户端向所述提醒对象发送与所述会议提醒消息相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第十二方面，提出了一种任务提醒装置，包括：
第一消息接收单元，使客户端接收与会议提醒消息相关的任务提醒消息；
第一展示单元，使所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息。
根据本申请的第十三方面，提出了一种任务提醒装置，包括：
第二指令接收单元，使客户端接收与会议提醒消息相关的任务提醒消息生成指令；
第二确定单元，使所述客户端确定提醒对象和任务描述信息；
第二发送单元，使所述客户端向参与所述会议提醒消息对应的会议的提醒对象发送与所述会议相关的任务提醒消息、向未参与所述会议的提醒对象发送与所述会议无关的 任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第十四方面，提出了一种任务提醒装置，包括：
第二消息接收单元，使客户端接收与会议提醒消息相关的任务提醒消息；
用户类型确定单元，使所述客户端确定已登录用户是否参与所述会议提醒消息对应的会议；
第二展示单元，使所述客户端在所述已登录用户参与所述会议时，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息；所述客户端在所述已登录用户未参与所述会议时，展示所述任务提醒消息包含的任务描述信息。
根据本申请的第十五方面，提出了一种提醒消息的生成装置，包括：
第三指令接收单元，使客户端接收与第一提醒消息相关的提醒消息生成指令；
第三确定单元，使所述客户端确定提醒对象和提醒事件描述信息；
第三发送单元，使所述客户端向所述提醒对象发送与所述第一提醒消息相关的第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
根据本申请的第十六方面，提出了一种提醒消息的生成装置，包括：
第一生成单元，使客户端根据提醒对象、提醒事件描述信息和第一提醒消息，生成与所述第一提醒消息相关的第二提醒消息；
第四发送单元，使所述客户端向所述提醒对象发送所述第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
根据本申请的第十七方面，提出了一种提醒消息的展示装置，包括：
第三消息接收单元，使客户端接收与第一提醒消息相关的第二提醒消息；
第三展示单元，使所述客户端展示所述第二提醒消息包含的第二提醒事件描述信息，以及展示所述第一提醒消息对应的第一提醒事件描述信息。
根据本申请的第十八方面，提出了一种任务提醒装置，包括：
第四指令接收单元，使客户端接收与会议相关的任务提醒消息生成指令；
第四确定单元，使所述客户端确定提醒对象和任务描述信息；
第五发送单元，使所述客户端向所述提醒对象发送与所述会议相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第十九方面，提出了一种任务提醒装置，包括：
第二生成单元，使客户端根据提醒对象、任务描述信息和会议，生成与所述会议相关的任务提醒消息；
第六发送单元，使所述客户端向所述提醒对象发送所述任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第二十方面，提出了一种任务提醒装置，包括：
第四消息接收单元，使客户端接收与会议相关的任务提醒消息；
第四展示单元，使所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息。
根据本申请的第二十一方面，提出了一种任务提醒方法，包括：
接收与会议提醒消息相关的任务提醒消息生成指令；
确定提醒对象和任务描述信息；
向所述提醒对象发送与所述会议提醒消息相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第二十二方面，提出了一种任务提醒方法，包括：
接收与会议提醒消息相关的任务提醒消息；
展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息。
根据本申请的第二十三方面，提出了一种任务提醒方法，包括：
接收与会议提醒消息相关的任务提醒消息生成指令；
确定提醒对象和任务描述信息；
向参与所述会议提醒消息对应的会议的提醒对象发送与所述会议相关的任务提醒消息、向未参与所述会议的提醒对象发送与所述会议无关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第二十四方面，提出了一种任务提醒方法，包括：
接收与会议提醒消息相关的任务提醒消息；
确定已登录用户是否参与所述会议提醒消息对应的会议；
在所述已登录用户参与所述会议时，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息；所述客户端在所述已登录用户未参与所述会议时，展示所述任务提醒消息包含的任务描述信息。
根据本申请的第二十五方面，提出了一种提醒消息的生成方法，包括：
接收与第一提醒消息相关的提醒消息生成指令；
确定提醒对象和提醒事件描述信息；
向所述提醒对象发送与所述第一提醒消息相关的第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
根据本申请的第二十六方面，提出了一种提醒消息的生成方法，包括：
根据提醒对象、提醒事件描述信息和第一提醒消息，生成与所述第一提醒消息相关的第二提醒消息；
向所述提醒对象发送所述第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
根据本申请的第二十七方面，提出了一种提醒消息的展示方法，包括：
接收与第一提醒消息相关的第二提醒消息；
展示所述第二提醒消息包含的第二提醒事件描述信息，以及展示所述第一提醒消息对应的第一提醒事件描述信息。
根据本申请的第二十八方面，提出了一种任务提醒方法，包括：
接收与会议相关的任务提醒消息生成指令；
确定提醒对象和任务描述信息；
向所述提醒对象发送与所述会议相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第二十九方面，提出了一种任务提醒方法，包括：
根据提醒对象、任务描述信息和会议，生成与所述会议相关的任务提醒消息；
向所述提醒对象发送所述任务提醒消息，所述任务提醒消息包含所述任务描述信息。
根据本申请的第三十方面，提出了一种任务提醒方法，包括：
接收与会议相关的任务提醒消息；
展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息。
由以上技术方案可见，本申请通过将任务提醒消息与会议提醒消息进行关联，使得用户在处理任务的过程中，能够快捷查看到关联会议的相关信息，有助于提升任务处理效率。同时，通过在任意类型的提醒消息之间建立关联，使得用户在查看其中任一提醒消息时，均可以快捷地查看到关联的其他提醒消息，而无需用户手动查找这些提醒消息，有助于提升用户对相关信息的获取效率，以及对相关事件的处理效率。
附图说明
图1是本申请一示例性实施例提供的一种任务提醒系统的架构示意图。
图2是本申请一示例性实施例提供的基于发送方的一种任务提醒方法的流程图。
图3是本申请一示例性实施例提供的基于接收方的一种任务提醒方法的流程图。
图4是本申请一示例性实施例提供的基于发送方的另一种任务提醒方法的流程图。
图5是本申请一示例性实施例提供的基于接收方的另一种任务提醒方法的流程图。
图6是本申请一示例性实施例提供的一种会议详情界面的示意图。
图7是本申请一示例性实施例提供的一种会议任务创建界面的示意图。
图8是本申请一示例性实施例提供的另一种会议详情界面的示意图。
图9是本申请一示例性实施例提供的一种负责人选择界面的示意图。
图10是本申请一示例性实施例提供的一种提醒消息管理界面的示意图。
图11是本申请一示例性实施例提供的一种任务详情界面的示意图。
图12是本申请一示例性实施例提供的另一种提醒消息管理界面的示意图。
图13是本申请一示例性实施例提供的又一种提醒消息管理界面的示意图。
图14是本申请一示例性实施例提供的又一种提醒消息管理界面的示意图。
图15是本申请一示例性实施例提供的另一种任务详情界面的示意图。
图16是本申请一示例性实施例提供的又一种任务详情界面的示意图。
图17是本申请一示例性实施例提供的又一种提醒消息管理界面的示意图。
图18是本申请一示例性实施例提供的又一种提醒消息管理界面的示意图。
图19是本申请一示例性实施例提供的又一种提醒消息管理界面的示意图。
图20是本申请一示例性实施例提供的基于发送方的又一种任务提醒方法的流程图。
图21是本申请一示例性实施例提供的一种管理日历的界面示意图。
图22是本申请一示例性实施例提供的基于发送方的又一种任务提醒方法的流程图。
图23是本申请一示例性实施例提供的基于接收方的又一种任务提醒方法的流程图。
图24是本申请一示例性实施例提供的一种提醒消息的生成方法的流程图。
图25是本申请一示例性实施例提供的另一种提醒消息的生成方法的流程图。
图26是本申请一示例性实施例提供的一种提醒消息的展示方法的流程图。
图27是本申请一示例性实施例提供的一种电子设备的结构示意图。
图28是本申请一示例性实施例提供的基于发送方的一种任务提醒装置的框图。
图29是本申请一示例性实施例提供的基于接收方的一种任务提醒装置的框图。
图30是本申请一示例性实施例提供的基于发送方的另一种任务提醒装置的框图。
图31是本申请一示例性实施例提供的基于接收方的另一种任务提醒装置的框图。
图32是本申请一示例性实施例提供的基于发送方的又一种任务提醒装置的框图。
图33是本申请一示例性实施例提供的基于发送方的又一种任务提醒装置的框图。
图34是本申请一示例性实施例提供的基于接收方的又一种任务提醒装置的框图。
图35是本申请一示例性实施例提供的另一种电子设备的结构示意图。
图36是本申请一示例性实施例提供的一种提醒消息的生成装置的框图。
图37是本申请一示例性实施例提供的另一种提醒消息的生成装置的框图。
图38是本申请一示例性实施例提供的又一种电子设备的结构示意图。
图39是本申请一示例性实施例提供的一种提醒消息的展示装置的框图。
具体实施方式
图1是本申请一示例性实施例提供的一种任务提醒系统的架构示意图。如图1所示，该系统可以包括服务器11、网络12、若干电子设备，比如手机13、手机14、手机15和手机16等。
服务器11可以为包含一独立主机的物理服务器，或者该服务器11可以为主机集群承载的虚拟服务器，或者该服务器11可以为云服务器。在运行过程中，服务器11可以运行某一应用的服务器侧的程序，以实现该应用的相关业务功能，比如当该服务器11运行移动化团体办公平台的程序时，可以实现为该移动化团体办公平台的服务端。而在本申请的技术方案中，可由服务器11通过与手机13-16上运行的客户端进行配合，以实现任务提醒消息的发送、接收等功能。
其中，移动化团体办公平台不仅可以实现通讯功能，还可以作为诸多其他功能的集成化功能平台，比如对于审批事件(如请假、办公物品申领、财务等审批事件)、考勤事件、任务事件、日志事件等团体内部事件的处理，再比如订餐、采购等团体外部事件的处理，本申请并不对此进行限制。较为具体地，移动化团体办公平台可以承载于相关技术中的即时通讯应用，比如企业即时通讯(Enterprise Instant Messaging，EIM)应用，例如Skype For
Figure PCTCN2018088810-appb-000001
Microsoft
Figure PCTCN2018088810-appb-000002
Figure PCTCN2018088810-appb-000003
Figure PCTCN2018088810-appb-000004
Figure PCTCN2018088810-appb-000005
Figure PCTCN2018088810-appb-000006
Figure PCTCN2018088810-appb-000007
Figure PCTCN2018088810-appb-000008
Figure PCTCN2018088810-appb-000009
等。当然，即时通讯功能仅为移动化团体办公平台支持的通讯功能之一，该团体办公平台还能够实现更多诸如上述的其他功能，以及本申请中所需实现的活动提醒功能等，此处不再赘述。
手机13-16只是用户可以使用的一种类型的电子设备。实际上，用户显然还可以使用诸如下述类型的电子设备：平板设备、笔记本电脑、掌上电脑(PDAs，Personal Digital  Assistants)、可穿戴设备(如智能眼镜、智能手表等)等，本申请并不对此进行限制。在运行过程中，该电子设备可以运行某一应用的客户端侧的程序，以实现该应用的相关业务功能，比如当该电子设备运行移动化团体办公平台的程序时，可以实现为该移动化团体办公平台的客户端，用于实现本申请的任务提醒消息的生成、发送、接收、展示等功能。其中，移动化企业办公平台的客户端的应用程序可以被预先安装在电子设备上，使得该客户端可以在该电子设备上被启动并运行；当然，当采用诸如HTML5技术的在线“客户端”时，无需在电子设备上安装相应的应用程序，即可获得并运行该客户端。
而对于手机13-16与服务器11之间进行交互的网络12，可以包括多种类型的有线或无线网络。在一实施例中，该网络12可以包括公共交换电话网络(Public Switched Telephone Network，PSTN)和因特网。同时，手机13-16等电子设备之间也可以通过该网络12进行通讯交互，比如在任意两台电子设备之间建立单聊通讯会话；或者，若干电子设备可以参与至同一群聊通讯会话，使得任一用户可以通过自身的电子设备向该群聊通讯会话中的其他所有用户发送通讯消息，比如当该群聊通讯会话为多个团体之间的跨团体通讯会话时，这些团体中的团体成员可以通过该跨团体通讯会话进行群聊通讯；再比如，每台电子设备均可以通过网络12向其他的一台或多台电子设备发送任务类型的提醒消息，以实现本申请的任务提醒功能。
服务器11与手机13-16之间可以通过网络12建立长连接，使得服务器11通过该长连接向手机13-16发送推送消息等，手机13-16也可以基于该长连接向服务器11发送消息等。或者，服务器11与手机13-16之间也可以通过其他方式实现基于该网络12的通讯过程，此处不再一一赘述。
基于诸如图1所示的任务提醒系统，手机13-16等电子设备可以被发送方和接收方使用，使得被发送方使用的电子设备可以运行任务提醒消息的发送方客户端、被接收方使用的电子设备可以运行任务提醒消息的接收方客户端；其中，发送方客户端可以生成与一条或多条会议提醒消息相关的任务提醒消息，并将该任务提醒消息发送至接收方客户端，比如发送方客户端可以通过服务器11运行的服务端将该任务提醒消息发送至接收方客户端，以及接收方客户端可以向接收方展示收到的任务提醒消息，使得接收方可以通过该任务提醒消息了解相应的任务描述信息，还可以通过该任务提醒消息了解相关联的会议提醒消息的会议描述信息。下面结合发送方客户端、接收方客户端的处理逻辑，对本申请的技术方案进行描述。
图2是本申请一示例性实施例提供的基于发送方的一种任务提醒方法的流程图。如 图2所示，该方法应用于发送方的电子设备，可以包括以下步骤：
步骤202，客户端接收与会议提醒消息相关的任务提醒消息生成指令。
在本实施例中，客户端可以提供多种类型的提醒消息；比如，会议提醒消息用于实现针对会议事件的提醒功能，任务提醒消息用于实现针对任务事件的提醒功能。通过为提醒消息设定相应的类型，便于用户对不同提醒消息进行分类展示和管理，有助于提升提醒消息的提醒效果，以提升用户的事件处理效率。
在本实施例中，客户端可以提供多种生成任务提醒消息的途径，因而存在多种方式来获取上述的与会议提醒消息相关的任务提醒消息生成指令，本申请并不对此进行限制。例如：
在一实施方式中，所述客户端可以在所述会议提醒消息的展示界面中，示出任务创建选项；然后，所述客户端在收到针对所述任务创建选项的触发操作时，可以确定接收到所述任务提醒消息生成指令。会议提醒消息的展示界面包括任意可以展示该会议提醒消息的界面，比如该会议提醒消息专用的详情展示界面，或者用于对该会议提醒消息以及其他提醒消息进行集中展示的提醒消息管理页面等。当然，除了示出任务创建选项并由用户对该任务创建选项实施触发操作之外，客户端还可以提供针对会议提醒消息的其他触发形式，比如在上述展示界面上划出预设触摸手势、发出控制语音等，本申请并不对此进行限制。此外，“任务创建选项”只是一种可以采用的选项形式，而其他与任务相关的功能选项，也可以应用于此处、以替换该“任务创建选项”；例如，该功能选项可以采用“任务编辑选项”或“任务修改选项”，当该“任务编辑选项”或“任务修改选项”被触发时，可以示出与会议提醒消息相关的任务提醒消息模板，以供发送方对该模板进行编辑或修改后，即可得到与会议提醒消息相关的任务提醒消息。
在另一实施方式中，所述客户端可以接收针对任务提醒消息的用户创建操作，以及针对所述任务提醒消息的会议绑定操作；然后，当所述会议绑定操作选取所述会议提醒消息时，所述客户端可以确定接收到与所述会议提醒消息相关的任务提醒消息生成指令。比如，客户端可以向用户提供针对任务提醒消息的创建选项，当用户通过用户创建操作触发该创建选项时，客户端可以进一步向用户提供备选的会议提醒消息(比如该客户端已接收、已发送的会议提醒消息等)，以供用户通过用户选择操作选取希望绑定至任务提醒消息的会议提醒消息。
步骤204，所述客户端确定提醒对象和任务描述信息。
在本实施例中，所述提醒对象可以包括以下至少之一：所述会议提醒消息对应的会 议的参与者、所述客户端收到的对象选择操作选择的对象。在一实施方式中，客户端可以将会议的参与者和发送方的关联用户均作为备选用户进行展示，以供发送方选取希望作为提醒对象的用户。在另一实施方式中，客户端可以默认将会议的参与者均作为提醒对象，并将发送方的关联用户作为备选用户进行展示，以供发送方进一步添加希望作为提醒对象的用户；其中，在一种情况下，会议的参与者可以被设定为必须作为提醒对象，而在另一种情况下，虽然会议的参与者被默认添加为提醒对象，但是发送方可以根据实际情况进行调整。
步骤206，所述客户端向所述提醒对象发送与所述会议提醒消息相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
在一实施例中，所述任务提醒消息还可以包含所述会议提醒消息中的会议描述信息，即客户端可以将该会议提醒消息中的至少一项会议描述信息添加至任务提醒消息中，以向接收方进行展示。
在另一实施例中，任务提醒消息可以不包含会议描述信息；例如，在一种情况下，该任务提醒消息中可以包含该会议提醒消息的标识信息，使得接收方客户端收到该任务提醒消息后，可以根据该标识信息向服务端获取相应的至少一项会议描述信息，或者根据该标识信息在接收方客户端的历史提醒消息中查找相应的会议提醒消息及其会议描述信息等；在另一种情况下，客户端可以向服务端告知该任务提醒消息与该会议提醒消息之间的关联信息，而该任务提醒消息中可以包含会议关联标识，该会议关联标识可以向接收方客户端表明：该任务提醒消息存在相关联的会议提醒消息，该接收方客户端可以向服务端发起询问，使得服务端基于上述关联信息而向接收方客户端返回相应的会议提醒消息的至少一项会议描述信息。
在本实施例中，当所述提醒对象未参与所述会议提醒消息对应的会议时，该提醒对象相当于独立于该会议的参与者，因而该提醒对象可以具有对所述任务提醒消息的任务管理权限，以便于确定该提醒对象的任务处理状况。
在本实施例中，当所述提醒对象参与所述会议，且所述提醒对象被配置为任务负责人时，所述提醒对象可以具有对所述任务提醒消息的任务管理权限。其中，当所述提醒对象参与所述会议，且所述提醒对象被配置为任务参与者时，所述提醒对象可以不具有对所述任务提醒消息的任务管理权限；此时，任务负责人与任务参与者相当于一个整体，而由任务负责人代表该整体实施统一的任务管理操作。
需要说明的是：图2所示的实施例除了可以应用于发送方的手机、PC等电子设备上 运行的客户端，使得通过该客户端来实现生成、发送任务提醒消息等功能，在一些情况下也可以应用于服务端，使得服务端通过运行该实施例中包含的各个步骤来实现生成、发送任务提醒消息等功能。甚至，在一些情况下，图2所示的实施例还可能应用于其他可能的执行主体，由这些执行主体通过运行该实施例中包含的各个步骤来实现生成、发送任务提醒消息等功能，本申请并不对此进行限制。
相应地，图3是本申请一示例性实施例提供的基于接收方的一种任务提醒方法的流程图。如图3所示，该方法应用于接收方的电子设备，可以包括以下步骤：
步骤302，客户端接收与会议提醒消息相关的任务提醒消息。
步骤304，所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息。
在本实施例中，当任务提醒消息中包含会议描述信息时，客户端可以获取该任务提醒消息包含的会议描述信息，并对该会议描述信息与任务提醒消息包含的任务描述信息进行展示。
在本实施例中，任务提醒消息可能未包含会议描述信息。在一实施方式中，任务提醒消息中可以包含该会议提醒消息的标识信息，则客户端可以根据该标识信息获取相应的会议描述信息；例如，客户端可以根据该标识信息在历史提醒消息中进行搜索，以查找相应的会议提醒消息，并获取该会议提醒消息包含的会议描述信息；再例如，客户端可以根据该标识信息向服务端发起询问，以由服务端向该客户端返回相应的会议提醒消息或会议描述信息。在另一实施方式中，任务提醒消息中可以包含会议关联标识，使得客户端确定该任务提醒消息存在相关联的会议提醒消息，则客户端可以向服务端发起与该任务提醒消息相关的询问；那么，如果发送方客户端预先向服务端告知该任务提醒消息与该会议提醒消息之间的关联关系，服务端就可以基于该关联关系确定出该会议提醒消息，则客户端可以接收服务端返回的该会议提醒消息或会议描述信息。
在本实施例中，所述客户端可以将所述会议描述信息的至少一部分内容展示于所述任务提醒消息的展示区域，该展示区域可以包括该任务提醒消息专用的详情展示界面，或者上述的提醒消息管理页面中对应于该任务提醒消息的展示区域。
在本实施例中，所述客户端可以将所述任务描述信息的至少一部分内容展示于所述会议提醒消息的展示区域，该展示区域可以包括该会议提醒消息专用的详情展示界面，或者上述的提醒消息管理页面中对应于该会议提醒消息的展示区域。
在本实施例中，所述客户端可以在所述任务提醒消息的展示区域内显示与所述会议 提醒消息相关的第一触发选项；其中，当所述第一触发选项被触发时，所述客户端展示所述会议提醒消息中的会议描述信息。当客户端已经获知会议描述信息时，第一触发选项可以包括该会议描述信息的概要信息，并基于对该第一触发选项的触发操作，由客户端示出该会议描述信息的详情信息，该详情信息可以展示于任务提醒消息的展示区域内，或者展示于独立界面(比如该会议提醒消息专用的详情展示界面或者临时窗口界面等)；当客户端尚未获知会议描述信息时，第一触发选项可以包括“点击了解关联会议”等指示性选项，并基于对该第一触发选项的触发操作，由客户端获取相应的会议描述信息以供展示。
在本实施例中，所述客户端可以在所述会议提醒消息的展示区域内显示与所述任务描述信息相关的第二触发选项；其中，当所述第二触发选项被触发时，所述客户端展示所述任务描述信息。例如，第一触发选项可以包括该任务描述信息的概要信息，并基于对该第一触发选项的触发操作，由客户端示出该任务描述信息的详情信息，该详情信息可以展示于会议提醒消息的展示区域内，或者展示于独立界面(比如该任务提醒消息专用的详情展示界面或者临时窗口界面等)。
在本实施例中，所述客户端可以根据针对所述任务提醒消息对应的任务事件的触发操作，对所述任务事件进行任务管理。例如，任务管理可以包括对任务事件的暂停、中止、完成等，本申请并不对此进行限制。根据客户端的已登录用户的权限不同，该客户端可以实现不同类型的任务管理；而当已登录用户无权限时，该客户端可能无法实现任务管理。
需要说明的是：图3所示的实施例除了可以应用于接收方的手机、PC等电子设备上运行的客户端，使得通过该客户端来实现接收任务提醒消息以及展示任务描述信息、会议描述信息等功能，在一些情况下也可以应用于服务端，使得服务端通过运行该实施例中包含的各个步骤来实现接收任务提醒消息、向接收方展示任务描述信息和会议描述信息(比如将任务描述信息和会议描述信息发送至接收方对应的客户端等)等功能。甚至，在一些情况下，图3所示的实施例还可能应用于其他可能的执行主体，由这些执行主体通过运行该实施例中包含的各个步骤来实现接收任务提醒消息、向接收方展示任务描述信息和会议描述信息等功能，本申请并不对此进行限制。
图4是本申请一示例性实施例提供的基于发送方的另一种任务提醒方法的流程图。如图4所示，该方法应用于发送方的电子设备，可以包括以下步骤：
步骤402，客户端接收与会议提醒消息相关的任务提醒消息生成指令。
在本实施例中，客户端可以提供多种类型的提醒消息；比如，会议提醒消息用于实现针对会议事件的提醒功能，任务提醒消息用于实现针对任务事件的提醒功能。通过为提醒消息设定相应的类型，便于用户对不同提醒消息进行分类展示和管理，有助于提升提醒消息的提醒效果，以提升用户的事件处理效率。
在本实施例中，客户端可以提供多种生成任务提醒消息的途径，因而存在多种方式来获取上述的与会议提醒消息相关的任务提醒消息生成指令，本申请并不对此进行限制。例如：
在一实施方式中，所述客户端可以在所述会议提醒消息的展示界面中，示出任务创建选项；然后，所述客户端在收到针对所述任务创建选项的触发操作时，可以确定接收到所述任务提醒消息生成指令。会议提醒消息的展示界面包括任意可以展示该会议提醒消息的界面，比如该会议提醒消息专用的详情展示界面，或者用于对该会议提醒消息以及其他提醒消息进行集中展示的提醒消息管理页面等。当然，除了示出任务创建选项并由用户对该任务创建选项实施触发操作之外，客户端还可以提供针对会议提醒消息的其他触发形式，比如在上述展示界面上划出预设触摸手势、发出控制语音等，本申请并不对此进行限制。此外，“任务创建选项”只是一种可以采用的选项形式，而其他与任务相关的功能选项，也可以应用于此处、以替换该“任务创建选项”；例如，该功能选项可以采用“任务编辑选项”或“任务修改选项”，当该“任务编辑选项”或“任务修改选项”被触发时，可以示出与会议提醒消息相关的任务提醒消息模板，以供发送方对该模板进行编辑或修改后，即可得到与会议提醒消息相关的任务提醒消息。
在另一实施方式中，所述客户端可以接收针对任务提醒消息的用户创建操作，以及针对所述任务提醒消息的会议绑定操作；然后，当所述会议绑定操作选取所述会议提醒消息时，所述客户端可以确定接收到与所述会议提醒消息相关的任务提醒消息生成指令。比如，客户端可以向用户提供针对任务提醒消息的创建选项，当用户通过用户创建操作触发该创建选项时，客户端可以进一步向用户提供备选的会议提醒消息(比如该客户端已接收、已发送的会议提醒消息等)，以供用户通过用户选择操作选取希望绑定至任务提醒消息的会议提醒消息。
步骤404，所述客户端确定提醒对象和任务描述信息。
步骤406，所述客户端向参与所述会议提醒消息对应的会议的提醒对象发送与所述会议相关的任务提醒消息、向未参与所述会议的提醒对象发送与所述会议无关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
在本实施例中，所述提醒对象可以包括以下至少之一：所述会议提醒消息对应的会议的参与者、所述客户端收到的对象选择操作选择的对象。因此，提醒对象可能包括两种情况：会议的参与者，非会议的参与者；对于会议的参与者而言，通过发送与会议相关的任务提醒消息，便于该会议的参与者对会议和任务进行关联查看、关联处理；而对于非会议的参与者，通过发送与会议无关的任务提醒消息，使其对于该会议无感知，避免造成困扰，并且有助于避免会议内容发生泄密。
在本实施例中，对于“与会议相关的任务提醒消息”，使得接收方客户端在收到该任务提醒消息后，可以在向接收方展示任务描述信息的同时，向接收方展示该会议的会议描述信息，以便于接收方对任务和会议进行关联查看、关联处理。在一实施方式中，该任务提醒消息可以包含所述会议提醒消息中的会议描述信息，即客户端可以将该会议提醒消息中的至少一项会议描述信息添加至任务提醒消息中，以向接收方进行展示。在另一实施方式中，任务提醒消息可以不包含会议描述信息；例如，在一种情况下，该任务提醒消息中可以包含该会议提醒消息的标识信息，使得接收方客户端收到该任务提醒消息后，可以根据该标识信息向服务端获取相应的至少一项会议描述信息，或者根据该标识信息在接收方客户端的历史提醒消息中查找相应的会议提醒消息及其会议描述信息等；在另一种情况下，客户端可以向服务端告知该任务提醒消息与该会议提醒消息之间的关联信息，而该任务提醒消息中可以包含会议关联标识，该会议关联标识可以向接收方客户端表明：该任务提醒消息存在相关联的会议提醒消息，该接收方客户端可以向服务端发起询问，使得服务端基于上述关联信息而向接收方客户端返回相应的会议提醒消息的至少一项会议描述信息。
在本实施例中，对于“与会议无关的任务提醒消息”，使得接收方客户端在收到该任务提醒消息时，可以在向接收方展示任务描述信息，与相关技术中的任务提醒消息无异。
在本实施例中，当所述提醒对象未参与所述会议提醒消息对应的会议时，该提醒对象相当于独立于该会议的参与者，因而该提醒对象可以具有对所述任务提醒消息的任务管理权限，以便于确定该提醒对象的任务处理状况，并使得操作体验与相关技术中的任务提醒消息无异。
在本实施例中，当所述提醒对象参与所述会议，且所述提醒对象被配置为任务负责人时，所述提醒对象可以具有对所述任务提醒消息的任务管理权限。其中，当所述提醒对象参与所述会议，且所述提醒对象被配置为任务参与者时，所述提醒对象可以不具有 对所述任务提醒消息的任务管理权限；此时，任务负责人与任务参与者相当于一个整体，而由任务负责人代表该整体实施统一的任务管理操作。
需要说明的是：图4所示的实施例除了可以应用于发送方的手机、PC等电子设备上运行的客户端，使得通过该客户端来实现生成、发送任务提醒消息等功能，在一些情况下也可以应用于服务端，使得服务端通过运行该实施例中包含的各个步骤来实现生成、发送任务提醒消息等功能。甚至，在一些情况下，图4所示的实施例还可能应用于其他可能的执行主体，由这些执行主体通过运行该实施例中包含的各个步骤来实现生成、发送任务提醒消息等功能，本申请并不对此进行限制。
相应地，图5是本申请一示例性实施例提供的基于接收方的另一种任务提醒方法的流程图。如图5所示，该方法应用于接收方的电子设备，可以包括以下步骤：
步骤502，客户端接收与会议提醒消息相关的任务提醒消息。
步骤504，所述客户端确定已登录用户是否参与所述会议提醒消息对应的会议。
步骤506，所述客户端在所述已登录用户参与所述会议时，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息；所述客户端在所述已登录用户未参与所述会议时，展示所述任务提醒消息包含的任务描述信息。
在本实施例中，发送方客户端可以向所有提醒对象均发送与会议提醒消息相关的任务提醒消息，而由接收方处的客户端根据已登录用户(即接收方)的会议参与情况，确定相应的展示内容，从而有助于简化发送方客户端的处理流程、提升通讯效率。
在本实施例中，当已登录用户参与会议时，客户端可以展示任务描述信息和会议描述信息。在一实施例中，当任务提醒消息中包含会议描述信息时，客户端可以获取该任务提醒消息包含的会议描述信息，并对该会议描述信息与任务提醒消息包含的任务描述信息进行展示。在另一实施例中，任务提醒消息可能未包含会议描述信息。在一种情况下，任务提醒消息中可以包含该会议提醒消息的标识信息，则客户端可以根据该标识信息获取相应的会议描述信息；例如，客户端可以根据该标识信息在历史提醒消息中进行搜索，以查找相应的会议提醒消息，并获取该会议提醒消息包含的会议描述信息；再例如，客户端可以根据该标识信息向服务端发起询问，以由服务端向该客户端返回相应的会议提醒消息或会议描述信息。在另一种情况下，任务提醒消息中可以包含会议关联标识，使得客户端确定该任务提醒消息存在相关联的会议提醒消息，则客户端可以向服务端发起与该任务提醒消息相关的询问；那么，如果发送方客户端预先向服务端告知该任务提醒消息与该会议提醒消息之间的关联关系，服务端就可以基于该关联关系确定出该 会议提醒消息，则客户端可以接收服务端返回的该会议提醒消息或会议描述信息。
在本实施例中，所述客户端可以将所述会议描述信息的至少一部分内容展示于所述任务提醒消息的展示区域，该展示区域可以包括该任务提醒消息专用的详情展示界面，或者上述的提醒消息管理页面中对应于该任务提醒消息的展示区域。
在本实施例中，所述客户端可以将所述任务描述信息的至少一部分内容展示于所述会议提醒消息的展示区域，该展示区域可以包括该会议提醒消息专用的详情展示界面，或者上述的提醒消息管理页面中对应于该会议提醒消息的展示区域。
在本实施例中，所述客户端可以在所述任务提醒消息的展示区域内显示与所述会议提醒消息相关的第一触发选项；其中，当所述第一触发选项被触发时，所述客户端展示所述会议提醒消息中的会议描述信息。当客户端已经获知会议描述信息时，第一触发选项可以包括该会议描述信息的概要信息，并基于对该第一触发选项的触发操作，由客户端示出该会议描述信息的详情信息，该详情信息可以展示于任务提醒消息的展示区域内，或者展示于独立界面(比如该会议提醒消息专用的详情展示界面或者临时窗口界面等)；当客户端尚未获知会议描述信息时，第一触发选项可以包括“点击了解关联会议”等指示性选项，并基于对该第一触发选项的触发操作，由客户端获取相应的会议描述信息以供展示。
在本实施例中，所述客户端可以在所述会议提醒消息的展示区域内显示与所述任务描述信息相关的第二触发选项；其中，当所述第二触发选项被触发时，所述客户端展示所述任务描述信息。例如，第一触发选项可以包括该任务描述信息的概要信息，并基于对该第一触发选项的触发操作，由客户端示出该任务描述信息的详情信息，该详情信息可以展示于会议提醒消息的展示区域内，或者展示于独立界面(比如该任务提醒消息专用的详情展示界面或者临时窗口界面等)。
在本实施例中，所述客户端可以根据针对所述任务提醒消息对应的任务事件的触发操作，对所述任务事件进行任务管理。例如，任务管理可以包括对任务事件的暂停、中止、完成等，本申请并不对此进行限制。根据客户端的已登录用户的权限不同，该客户端可以实现不同类型的任务管理；而当已登录用户无权限时，该客户端可能无法实现任务管理。
需要说明的是：图5所示的实施例除了可以应用于接收方的手机、PC等电子设备上运行的客户端，使得通过该客户端来实现接收任务提醒消息以及展示任务描述信息、会议描述信息等功能，在一些情况下也可以应用于服务端，使得服务端通过运行该实施例 中包含的各个步骤来实现接收任务提醒消息、向接收方展示任务描述信息和会议描述信息(比如将任务描述信息和会议描述信息发送至接收方对应的客户端等)等功能。甚至，在一些情况下，图5所示的实施例还可能应用于其他可能的执行主体，由这些执行主体通过运行该实施例中包含的各个步骤来实现接收任务提醒消息、向接收方展示任务描述信息和会议描述信息等功能，本申请并不对此进行限制。
由以上技术方案可见，本申请通过将任务提醒消息与会议提醒消息进行关联，使得用户在处理任务的过程中，能够快捷查看到关联会议的相关信息，有助于提升任务处理效率。
为了便于理解，下面以企业即时通讯应用“企业微信”为例，对本申请的技术方案进行说明。假定手机13、手机14和手机15上运行有企业微信客户端、服务器11上运行有企业微信服务端，其中手机13-15上的企业微信客户端分别登录有不同使用者的注册账号，例如手机13上登录有发送方的注册账号A(即用户A)，使得手机13被配置为发送方对应的发送方设备、手机13上登录有该发起方对应的企业微信客户端1，以及手机14-15分别上登录有接收方的注册账号B(即用户B)和注册账号C(即用户C)，使得手机14-15被配置为这两个接收方对应的接收方设备、手机14-15上登录有这两个接收方对应的企业微信客户端2和企业微信客户端3。其中，用户A可以在手机13上创建与会议提醒消息相关的任务提醒消息并发送至用户B、用户C，以实现对用户B和用户C的任务提醒，下面基于该过程对本申请的技术方案进行详细描述。
图6为手机13上的企业微信客户端1的会议详情界面600，该会议详情界面600用于对会议提醒消息的会议描述信息进行详情展示，比如会议主题“讨论X项目存在的问题，以及进一步的开发需求”、会议时间“4月28日周五14:00～16:00”、会议地点“2号楼201室”等，以及该会议提醒消息的发送方A(即“我”)、发送时间“昨天12:21”等，这些与相关技术中对于会议描述信息的展示相同。
而在本申请的会议详情界面600中，还包括会议任务创建选项601。当用户A通过点击或其他方式触发该会议任务创建选项601时，企业微信客户端1可以判定为用户A需要创建与图6所示的会议提醒消息相关的任务提醒消息，即“会议任务”。例如，企业微信客户端1可以展示出图7所示的会议任务创建界面700，以供用户A创建上述的会议任务。当然，除了会议提醒消息的创建者A之外，其他的会议参与者也可以创建与该会议提醒消息相关的任务提醒消息；比如图8所示，在手机14上的企业微信客户端2(或手机15上的企业微信客户端3等)示出的会议详情界面800中，可以包含会议任务 创建选项801，当该企业微信客户端2检测到用户B对该会议任务创建选项801的触发操作时，企业微信客户端2可以展示出图7所示的会议任务创建界面700，以供用户B创建相应的会议任务。
以用户A对图7所示的会议任务创建界面700进行操作为例，该用户A可以通过该会议任务创建界面700输入会议任务的任务描述信息。例如：
任务描述信息可以包括任务主题，用户A可以通过会议任务创建界面700中展示有“请输入任务内容”的输入框来输入该任务主题。当然，任务主题还可以包括语音、视频、图片、文档等其他内容，而不仅限于用户A在输入框内输入的文字内容。
任务描述信息可以包括任务负责人，用户A可以通过触发会议任务创建界面700中的“负责人”选项，选取该会议任务的负责人。例如企业微信客户端1可以展示图9所示的负责人选择界面900，并根据用户A对该负责人选择界面900的操作，确定相应的任务负责人。如图9所示，企业微信客户端1可以示出上述会议提醒消息对应的会议的参与者(即“会议人员”)，当然用户A也可以通过触发“添加其他负责人”选项，以将未参与该会议的其他人员选择为任务负责人。
任务描述信息可以包括发送方式，用户A可以通过触发会议任务创建界面700中的“应用内”、“短信”、“电话”等选项，选取对该会议任务的发送方式。其中，“应用内”表明企业微信客户端1将通过即时通讯技术发送该会议任务、“短信”表明企业微信客户端1将通过短信发送该会议任务、“电话”表明该企业微信客户端1将发起通话并在接通后语音播放任务主题等任务描述信息。用户A可以选择“应用内”、“短信”、“电话”等选项中的一个或多个，使得企业微信客户端1通过相应的一种或多种方式发送会议任务。
任务描述信息可以包括任务截止时间，用户A可以通过触发会议任务创建界面700中的“截止时间”选项，设定该会议任务的截止时间，比如图7所示的“5月11日周四18:00”等。
任务描述信息可以包括到期提醒功能，用户A可以通过触发会议任务创建界面700中的“到期提醒”选项，设定是否需要对该会议任务实施到期提醒；当需要实施到期提醒时，还可以进一步设定到期提醒的方式(如“应用内”、“短信”、“电话”等)、时间(如“到期前3天”等)等。
任务描述信息可以包括任务参与人，用户A可以通过触发会议任务创建界面700中的“参与人”选项，选取该会议任务的任务参与人。任务参与人与任务负责人均可以接 收到该会议任务，但正如图7所示的“参与人不需要完成”所指出的，当任务参与人和任务负责人均为会议人员时，任务负责人具有对该会议任务实施“完成操作”的权限，而任务参与人则不具有该权限，这在下文将会详细描述。
企业微信客户端1在检测到用户A触发会议任务创建界面700右上角的“完成”选项时，可以向用户B、用户C等发出上述的会议任务。需要指出的是：在本申请的技术方案中，会议任务的创建时刻和发送时刻，与会议本身的进行情况无关；换言之，无论是在会议开始前、会议过程中、会议结束后或其他时刻，均可以实施对会议任务的创建操作或发送操作，本申请并不对此进行限制。
对于用户A而言，企业微信客户端1在发出会议任务后，可以在图10所示的提醒消息管理界面1000中示出已发送的该会议任务；同时，该提醒消息管理界面1000还用于集中展示用户A已发出或已收到的其他提醒消息。在该提醒消息管理界面1000中，上述会议任务展示于自身对应的展示区域1001内，且该展示区域1001中还包含与上述会议任务相关的展示内容1002，以在该会议提醒消息与会议任务之间建立关联。
如图10所示，展示内容1002可以包括“1个会议任务，0个完成”，以表明相应的会议提醒消息存在一个相关联的会议任务。当检测到针对该展示内容1002的触发操作时，企业微信客户端1可以示出图11所示的任务详情界面1100，以详细展示该会议任务的任务描述信息。当然，在其他实施例中，比如在图12所示的提醒消息管理界面1200中，在会议提醒消息对应的展示区域1201内，该会议任务对应的展示内容除了“1个会议任务，0个完成”或类似的提示信息1202之外，还可以包括该会议任务的任务描述信息的概要信息1203，如该概要信息1202可以包括“·明天提出3个解决…”等，既可以减少展示区域1201对提醒消息管理界面1200的占用(以便于在手机13上同时展示更多的提醒消息)，又可以在一定程度上向用户A提示该会议任务的任务描述信息，使得用户A在一些情况下可以无需进入图11所示的任务详情界面1100；当然，如果检测到针对提示信息1202或概要信息1203的触发操作，企业微信客户端1仍然可以展示图11所示的任务详情界面1100，以便于用户A进行查看。而在其他实施例中，比如在图13所示的提醒消息管理界面1300中，在会议提醒消息对应的展示区域1301内，该会议任务对应的展示内容可以包括任务描述信息的详情信息。
在图11-13所示的实施例中，用户A为会议任务的负责人，因此该用户A具有对该会议任务的管理权限。例如图11所示，在任务详情界面1100中可以包括“完成任务”选项1102，当检测到针对该选项1102的触发操作时，企业微信客户端1可以针对该会 议任务实施“完成任务”的管理操作。类似地，在图12所示的提醒消息管理界面1200中可以包含“完成任务”选项1204，在图13所示的提醒消息管理界面1300中可以包含“完成任务”选项1302，企业微信客户端1可以根据用户A针对选项1204或选项1302的触发操作，对该会议任务实施“完成任务”的管理操作。而在图14所示的实施例中，当会议任务的负责人为用户B、而非用户A时，用户A并不具有对该会议任务的管理权限。因此，在图14所示的提醒消息管理界面1400中，企业微信客户端1可以在会议提醒消息的展示区域1401中示出该任务会议的相关内容，而并不示出上述的“完成任务”选项，使得用户A无法针对该会议任务实施“完成任务”的管理操作。
当用户A为上述会议任务的创建者时，在诸如图11所示的任务详情界面1100中，可以包括针对该会议任务的“结束任务”选项1103，使得用户A触发该选项1103时，企业微信客户端1可以终止该会议任务。用户A对会议任务的“终止任务”权限，与该用户A作为创建者的身份相关，因而如图15所示，即便用户A并非该会议任务的负责人，在图15所示的任务详情界面1500中仍然可以包括“结束任务”选项1501，可供用户A对该会议任务实施终止操作。
而对于如图16所示的企业微信客户端3示出的任务详情界面1600而言，用户C作为会议人员以及该会议任务的参与人，该任务详情界面1600可以示出与会议“讨论X项目存在的问题…”的相关内容1601；但是，由于用户C并非上述会议任务的负责人，因而该任务详情界面1600并未展示出“完成任务”选项，即用户C不具有对该会议任务的“完成任务”权限；类似地，由于用户C并非该会议任务的创建者，因而该任务详情界面1600并未展示出“结束任务”选项，即用户C不具有对该会议任务的“结束任务”权限。
上述的会议任务可以作为相对独立的任务提醒消息，以由企业微信客户端进行管理。例如图17所示，在企业微信客户端2示出的提醒消息管理界面1700中，上述会议任务的任务描述内容可以被展示于该提醒消息管理界面1700中的展示区域1701内，且该展示区域1701中还可以包括与上述会议提醒消息(即与相应的会议)相关的提示内容1702，比如该提示内容1702可以包括“属于会议：讨论X项目存在的问题”等；同时，当用户B为该会议任务的负责人时，该展示区域1701中还可以包括“完成任务”选项1703，以便用户B可以通过触发该选项1703，以对该会议任务实施“完成任务”操作。
而对于并非负责人的用户C，在图18所示的企业微信客户端3示出的提醒消息管理界面1800中，上述会议任务的任务描述内容可以被展示于该提醒消息管理界面1800中 的展示区域1801内，且该展示区域1801中还可以包括与上述会议提醒消息(即与相应的会议)相关的提示内容1802，但并不包含“完成任务”选项。
其中，对于会议任务的参与人而言，由于并不需要对该会议任务进行管理，因而该会议任务可以被作为上述会议提醒消息的附属消息(可以表现为图18所示的“任务跟进”，区别于图17所示的“任务”)，而并非正常的任务提醒消息，使得该附属消息无法被展示于图18所示的提醒消息管理界面1800中，而仅能够通过上述会议提醒消息进行间接调用。比如，用户C可以在提醒消息管理界面1800中查找到该会议提醒消息，该会议提醒消息的展示区域内可以包含该会议任务的相关内容(类似于图10所示的展示内容1002等)，用户C可以通过该相关内容进入如图16所示的任务详情界面1600，以详细查看相应的任务描述信息。
此外，会议任务的参与人可能并非上述会议的会议人员，则在相应的企业微信客户端示出的图19所示的提醒消息管理界面1900中，该会议任务的任务描述信息可以被正常展示于相应的展示区域1901内，并且该展示区域1901还可以包括“完成任务”选项1902，即该参与人具有对该会议任务的“完成任务”权限；换言之，该会议任务对于该参与人而言，与相关技术中的其他任务提醒消息无异。
在上述的各个实施例中，通过将任务提醒消息与会议提醒消息进行关联，使得接收方客户端在收到任务提醒消息后，可以展示与该任务提醒消息相关的会议提醒消息的会议描述信息，以便于接收方进行便捷查看。而在下述实施例中，还可以将任务提醒消息与会议事件相关联，同样可以使得任务提醒消息的接收方对该会议的会议描述信息进行展示。
图20是本申请一示例性实施例提供的基于发送方的又一种任务提醒方法的流程图。如图20所示，该方法应用于发送方的电子设备，可以包括以下步骤：
步骤2002，客户端接收与会议相关的任务提醒消息生成指令。
在本实施例中，由于会议提醒消息用于实现针对会议事件的提醒功能，而客户端还可以实现与会议事件相关的其他功能，因而客户端可以通过将任务提醒消息与会议(即会议事件)相关联，即可使得接收方客户端对相应的会议描述信息进行获取和展示。
举例而言，在本申请的企业微信客户端中，为了便于实施企业内部的企业事项管理，可以提供管理日历功能。例如图21所示，通过示出管理日历2100，并在该管理日历2100上示出每天相关联的企业事项，可以帮助用户快速掌握企业事项的处理状况，便于后续工作的合理安排。以图21所示的管理日历2100为例，通过为存在企业事项的日期添加 事件提示信息，即可使得用户快速了解相应的日期存在相关联的企业事项，比如在“2017年4月4日”、“2017年4月5日”、“2017年4月12日”、“2017年4月18日”的底部添加一黑色圆点，表明存在任务事件。而“2017年4月5日”、“2017年4月28日”的底部存在一白色圆点，表明当天存在一会议事件。当然，还可以通过其他方式表示出其他类型的事件。
当检测到某一日期被选中时，比如图21中假定“2017年4月28日”被选中，可以示出该日期内存在的企业事项，例如可以在管理日历2100下部的展示区域2101内，示出“2017年4月28日”存在的任务事件(对应于“28”底部的黑色圆点)和会议事件(对应于“28”底部的白色圆点)的描述信息，该描述信息可以为图22所示的摘要信息(当某一摘要信息被选中时，可以进一步示出相应的详情信息)，或者该描述信息可以为详情信息。当“2017年4月28日”被选中时，可以对相应的数字“28”进行突出显示，以区别于其他日期，比如图21中采用了将数字28调整为白色并添加黑色背景的方式；同时，对于当前所处的日期，也可以采用区别于被选中的日期和其他日期的方式进行突出显示，比如“2017年4月26日”外围可以添加一圆环。
在展示被选中的日期内存在的企业事项时，可以示出针对该企业事项的类型提示信息，比如图21所示的任务事件对应的“任务”字样、会议事件对应的“会议”字样等。此外，还可以将该类型提示信息与管理日历中的上述黑色圆点、白色圆点等企业事项提示信息相配合，比如将类型提示信息与企业事项提示信息采用相同或相近的展示属性，使得用户能够从视觉观感上获得两者之间的关联性，有助于提升用户体验；例如，该展示属性可以包括颜色、灰度、透明度等，本申请并不对此进行限制。
以图21所示的会议事件为例，在该会议事件的关联区域可以示出一“会议任务”选项2102，当检测到针对该选项2102的触发操作时，可以确定为接收与图21所示的“讨论X项目存在的问题，以…”会议事件相关的任务提醒消息生成指令，以创建于该会议相关的任务提醒消息(即会议任务)。
当然，该选项2102还可以采用其他形式，比如“任务创建”、“任务编辑”、“任务修改”等，本申请并不对此进行限制。例如，当采用“任务编辑”或“任务修改”等形式时，当该“任务编辑”或“任务修改”的选项被触发时，可以示出与会议相关的任务提醒消息模板，以供发送方对该模板进行编辑或修改后，即可得到与会议相关的任务提醒消息。
步骤2004，所述客户端确定提醒对象和任务描述信息。
在本实施例中，所述提醒对象可以包括以下至少之一：会议的参与者、所述客户端收到的对象选择操作选择的对象。在一实施方式中，客户端可以将会议的参与者和发送方的关联用户均作为备选用户进行展示，以供发送方选取希望作为提醒对象的用户。在另一实施方式中，客户端可以默认将会议的参与者均作为提醒对象，并将发送方的关联用户作为备选用户进行展示，以供发送方进一步添加希望作为提醒对象的用户；其中，在一种情况下，会议的参与者可以被设定为必须作为提醒对象，而在另一种情况下，虽然会议的参与者被默认添加为提醒对象，但是发送方可以根据实际情况进行调整。
步骤2006，所述客户端向所述提醒对象发送与所述会议相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
在一实施例中，所述任务提醒消息还可以包含所述会议的会议描述信息，即客户端可以将该会议提醒消息中的至少一项会议描述信息添加至任务提醒消息中，以向接收方进行展示。会议描述信息可以存在多种来源；例如：在图21所示的实施例中，管理日历2100可以记录有会议事件的会议描述信息，使得客户端可以从管理日历2100处获知上述的会议描述信息；或者，客户端可以确定该会议事件对应的会议提醒消息，并从该会议提醒消息中获取相应的会议描述信息。
在另一实施例中，任务提醒消息可以不包含会议描述信息；例如，在一种情况下，该任务提醒消息中可以包含该会议的标识信息，使得接收方客户端收到该任务提醒消息后，可以根据该标识信息向服务端获取相应的至少一项会议描述信息，或者根据该标识信息在接收方客户端的历史提醒消息中查找相应的会议提醒消息或会议事件，从而获取相应的会议描述信息；在另一种情况下，客户端可以向服务端告知该任务提醒消息与该会议之间的关联信息，而该任务提醒消息中可以包含会议关联标识，该会议关联标识可以向接收方客户端表明：该任务提醒消息存在相关联的会议，该接收方客户端可以向服务端发起询问，使得服务端基于上述关联信息而向接收方客户端返回相应的至少一项会议描述信息。
在本实施例中，当所述提醒对象未参与所述会议时，该提醒对象相当于独立于该会议的参与者，因而该提醒对象可以具有对所述任务提醒消息的任务管理权限，以便于确定该提醒对象的任务处理状况。
在本实施例中，当所述提醒对象参与所述会议，且所述提醒对象被配置为任务负责人时，所述提醒对象可以具有对所述任务提醒消息的任务管理权限。其中，当所述提醒对象参与所述会议，且所述提醒对象被配置为任务参与者时，所述提醒对象可以不具有 对所述任务提醒消息的任务管理权限；此时，任务负责人与任务参与者相当于一个整体，而由任务负责人代表该整体实施统一的任务管理操作。
与图20所示实施例相类似地，图22是本申请一示例性实施例提供的基于发送方的又一种任务提醒方法的流程图。如图22所示，该方法应用于发送方的电子设备，可以包括以下步骤：
步骤2202，客户端根据提醒对象、任务描述信息和会议，生成与所述会议相关的任务提醒消息。
步骤2204，所述客户端向所述提醒对象发送所述任务提醒消息，所述任务提醒消息包含所述任务描述信息。
本实施例的功能逻辑可以参考图20所示的实施例，此处不再赘述。
需要说明的是：图20和图22所示的实施例除了可以应用于发送方的手机、PC等电子设备上运行的客户端，使得通过该客户端来实现生成、发送任务提醒消息等功能，在一些情况下也可以应用于服务端，使得服务端通过运行该实施例中包含的各个步骤来实现生成、发送任务提醒消息等功能。甚至，在一些情况下，图20和图22所示的实施例还可能应用于其他可能的执行主体，由这些执行主体通过运行该实施例中包含的各个步骤来实现生成、发送任务提醒消息等功能，本申请并不对此进行限制。
对应于图20或图22所示的实施例，图23是本申请一示例性实施例提供的基于接收方的又一种任务提醒方法的流程图。如图23所示，该方法应用于接收方的电子设备，可以包括以下步骤：
步骤2302，客户端接收与会议相关的任务提醒消息。
步骤2304，所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息。
在本实施例中，当任务提醒消息中包含会议描述信息时，客户端可以获取该任务提醒消息包含的会议描述信息，并对该会议描述信息与任务提醒消息包含的任务描述信息进行展示。
在本实施例中，任务提醒消息可能未包含会议描述信息。在一实施方式中，任务提醒消息中可以包含该会议的标识信息，则客户端可以根据该标识信息获取相应的会议描述信息；例如，客户端可以根据该标识信息在历史提醒消息中进行搜索，以查找相应的会议事件或会议提醒消息，并获取该会议事件或会议提醒消息包含的会议描述信息；再例如，客户端可以根据该标识信息向服务端发起询问，以由服务端向该客户端返回相应 的会议描述信息。在另一实施方式中，任务提醒消息中可以包含会议关联标识，使得客户端确定该任务提醒消息存在相关联的会议，则客户端可以向服务端发起与该任务提醒消息相关的询问；那么，如果发送方客户端预先向服务端告知该任务提醒消息与该会议之间的关联关系，服务端就可以基于该关联关系确定出该会议，则客户端可以接收服务端返回的该会议的会议描述信息。
在本实施例中，所述客户端可以将所述会议描述信息的至少一部分内容展示于所述任务提醒消息的展示区域，该展示区域可以包括该任务提醒消息专用的详情展示界面，或者上述的提醒消息管理页面中对应于该任务提醒消息的展示区域。
在本实施例中，所述客户端可以将所述任务描述信息的至少一部分内容展示于所述会议对应的会议提醒消息的展示区域，该展示区域可以包括该会议提醒消息专用的详情展示界面，或者上述的提醒消息管理页面中对应于该会议提醒消息的展示区域。
在本实施例中，所述客户端可以在所述任务提醒消息的展示区域内显示与所述会议相关的第一触发选项；其中，当所述第一触发选项被触发时，所述客户端展示所述会议描述信息。当客户端已经获知会议描述信息时，第一触发选项可以包括该会议描述信息的概要信息，并基于对该第一触发选项的触发操作，由客户端示出该会议描述信息的详情信息，该详情信息可以展示于任务提醒消息的展示区域内，或者展示于独立界面(比如该会议提醒消息专用的详情展示界面或者临时窗口界面等)；当客户端尚未获知会议描述信息时，第一触发选项可以包括“点击了解关联会议”等指示性选项，并基于对该第一触发选项的触发操作，由客户端获取相应的会议描述信息以供展示。
在本实施例中，所述客户端可以在所述会议提醒消息的展示区域内显示与所述任务描述信息相关的第二触发选项；其中，当所述第二触发选项被触发时，所述客户端展示所述任务描述信息。例如，第一触发选项可以包括该任务描述信息的概要信息，并基于对该第一触发选项的触发操作，由客户端示出该任务描述信息的详情信息，该详情信息可以展示于会议提醒消息的展示区域内，或者展示于独立界面(比如该任务提醒消息专用的详情展示界面或者临时窗口界面等)。
在本实施例中，所述客户端可以根据针对所述任务提醒消息对应的任务事件的触发操作，对所述任务事件进行任务管理。例如，任务管理可以包括对任务事件的暂停、中止、完成等，本申请并不对此进行限制。根据客户端的已登录用户的权限不同，该客户端可以实现不同类型的任务管理；而当已登录用户无权限时，该客户端可能无法实现任务管理。
在上述实施例中，以任务提醒消息与会议提醒消息、任务提醒消息与会议之间的关联为例，对本申请的技术方案进行了说明。需要指出的是：在本申请的技术方案中，“任务”在不同情况下可以存在不同的理解；比如，在一些场景下，“任务”可以理解为待处理事项(例如在工作场景下，可以表现为工作内容)，该“任务”的承担者(比如本申请中的提醒对象)需要完成该待处理事项，并向该任务提醒消息的发送方予以反馈(如“完成任务”的通知)；在另一些场景下，“任务”可以理解为通知事项或类似的描述性信息，该“任务”的承担者可能需要处理该事项，也可能仅需获知该通知事项即可；在其他场景下，还可能存在其他理解，本申请并不对此进行限制。另外，一些较为简单的“任务”，可以仅包含一项待处理事项或通知事项，而一些较为复杂的“任务”则可能包含多项待处理事项或通知事项。
当然，除了任务提醒消息与会议提醒消息或会议之间的相互关联之外，实际上本申请的技术方案还可以进一步扩展至任意类型的提醒消息之间的相互关联，下面结合实施例进行说明。
需要说明的是：图23所示的实施例除了可以应用于接收方的手机、PC等电子设备上运行的客户端，使得通过该客户端来实现接收任务提醒消息以及展示任务描述信息、会议描述信息等功能，在一些情况下也可以应用于服务端，使得服务端通过运行该实施例中包含的各个步骤来实现接收任务提醒消息、向接收方展示任务描述信息和会议描述信息(比如将任务描述信息和会议描述信息发送至接收方对应的客户端等)等功能。甚至，在一些情况下，图23所示的实施例还可能应用于其他可能的执行主体，由这些执行主体通过运行该实施例中包含的各个步骤来实现接收任务提醒消息、向接收方展示任务描述信息和会议描述信息等功能，本申请并不对此进行限制。
图24是本申请一示例性实施例提供的一种提醒消息的生成方法的流程图。如图24所示，该方法可以包括以下步骤：
步骤2402，客户端接收与第一提醒消息相关的提醒消息生成指令。
在本实施例中，客户端可以提供多种类型的提醒消息；比如，会议提醒消息用于实现针对会议事件的提醒功能，任务提醒消息用于实现针对任务事件的提醒功能，催办提醒消息用于实现针对审批事件的提醒功能等。通过为提醒消息设定相应的类型，便于用户对不同提醒消息进行分类展示和管理，有助于提升提醒消息的提醒效果，以提升用户的事件处理效率。
在本实施例中，第一提醒消息、第二提醒消息可以分别为上述任意类型的提醒消息。 第一提醒消息与第二提醒消息可以为相同类型，比如第一提醒消息与第二提醒消息可以同时为任务类型、会议类型或催办类型等。第一提醒消息与第二提醒消息可以为不同类型，比如当第一提醒消息为会议类型、第二提醒消息为任务类型时，图24所示的实施例相当于图2所示的实施例；再比如，第一提醒消息可以为任务类型、第二提醒消息可以为会议类型，或者第一提醒消息可以为会议类型、第二提醒消息可以为催办类型等。
在本实施例中，客户端可以提供多种生成第二提醒消息的途径，因而存在多种方式来获取上述的与第一提醒消息相关的提醒消息生成指令，本申请并不对此进行限制。例如：
在一实施方式中，所述客户端可以在所述第一提醒消息的展示界面中，示出第二提醒消息创建选项；然后，所述客户端在收到针对所述第二提醒消息创建选项的触发操作时，可以确定接收到所述提醒消息生成指令。第一提醒消息的展示界面包括任意可以展示该第一提醒消息的界面，比如该第一提醒消息专用的详情展示界面，或者用于对该第一提醒消息以及其他提醒消息进行集中展示的提醒消息管理页面等。当然，除了示出第二提醒消息创建选项并由用户对该第二提醒消息创建选项实施触发操作之外，客户端还可以提供针对第一提醒消息的其他触发形式，比如在上述展示界面上划出预设触摸手势、发出控制语音等，本申请并不对此进行限制。此外，“第二提醒消息创建选项”只是一种可以采用的选项形式，而其他与任务相关的功能选项，也可以应用于此处、以替换该“第二提醒消息创建选项”；例如，该功能选项可以采用“第二提醒消息编辑选项”或“第二提醒消息修改选项”，当该“第二提醒消息编辑选项”或“第二提醒消息修改选项”被触发时，可以示出与第一提醒消息相关的第二提醒消息模板，以供发送方对该模板进行编辑或修改后，即可得到与第一提醒消息相关的第二提醒消息。
在另一实施方式中，所述客户端可以接收针对第二提醒消息的用户创建操作，以及针对所述第二提醒消息的第一提醒消息绑定操作；然后，当所述第一提醒消息绑定操作选取所述第一提醒消息时，所述客户端可以确定接收到与所述第一提醒消息相关的提醒消息生成指令。比如，客户端可以向用户提供针对第二提醒消息的创建选项，当用户通过用户创建操作触发该创建选项时，客户端可以进一步向用户提供备选的第一提醒消息(比如该客户端已接收、已发送的第一提醒消息等)，以供用户通过用户选择操作选取希望绑定至第二提醒消息的第一提醒消息。
步骤2404，所述客户端确定提醒对象和提醒事件描述信息。
在本实施例中，所述提醒对象可以包括以下至少之一：所述第一提醒消息的关联用 户(例如当该第一提醒消息为会议提醒消息时，关联用户可以为会议参与者)、所述客户端收到的对象选择操作选择的对象。在一实施方式中，客户端可以将所述第一提醒消息的关联用户和发送方的关联用户均作为备选用户进行展示，以供发送方选取希望作为提醒对象的用户。在另一实施方式中，客户端可以默认将所述第一提醒消息的关联用户均作为提醒对象，并将发送方的关联用户作为备选用户进行展示，以供发送方进一步添加希望作为提醒对象的用户；其中，在一种情况下，所述第一提醒消息的关联用户可以被设定为必须作为提醒对象，而在另一种情况下，虽然所述第一提醒消息的关联用户被默认添加为提醒对象，但是发送方可以根据实际情况进行调整。
步骤2406，所述客户端向所述提醒对象发送与所述第一提醒消息相关的第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
在一实施例中，假定第二提醒消息包含第二提醒事件描述信息，该第二提醒消息还可以包含所述第一提醒消息中的第一提醒事件描述信息，即客户端可以将该第一提醒消息中的至少一项第一提醒事件描述信息添加至第二提醒消息中，以向接收方进行展示。
在另一实施例中，第二提醒消息可以不包含第一提醒事件描述信息；例如，在一种情况下，该第二提醒消息中可以包含该第一提醒消息的标识信息，使得接收方客户端收到该第二提醒消息后，可以根据该标识信息向服务端获取相应的至少一项第一提醒事件描述信息，或者根据该标识信息在接收方客户端的历史提醒消息中查找相应的第一提醒消息及其第一提醒事件描述信息等；在另一种情况下，客户端可以向服务端告知该第二提醒消息与该第一提醒消息之间的关联信息，而该第二提醒消息中可以包含会议关联标识，该会议关联标识可以向接收方客户端表明：该第二提醒消息存在相关联的第一提醒消息，该接收方客户端可以向服务端发起询问，使得服务端基于上述关联信息而向接收方客户端返回相应的第一提醒消息的至少一项第一提醒事件描述信息。
在本实施例中，当所述提醒对象并非所述第一提醒消息的关联用户时，该提醒对象可以具有对所述第二提醒消息的对应事件的管理权限，以便于确定该提醒对象对该对应事件的处理状况。
在本实施例中，当所述提醒对象属于所述第一提醒消息的关联用户，且所述提醒对象被配置为所述第二提醒消息的对应事件的事件负责人时，所述提醒对象可以具有对该对应事件的管理权限。其中，当所述提醒对象属于所述第一提醒消息的关联用户，且所述提醒对象被配置为所述第二提醒消息的对应事件的事件参与者时，所述提醒对象可以不具有对该对应事件的管理权限；此时，事件负责人与事件参与者相当于一个整体，而 由事件负责人代表该整体实施统一的事件管理操作。
图25是本申请一示例性实施例提供的另一种提醒消息的生成方法的流程图。如图25所示，该方法可以包括以下步骤：
步骤2502，客户端根据提醒对象、提醒事件描述信息和第一提醒消息，生成与所述第一提醒消息相关的第二提醒消息。
步骤2504，所述客户端向所述提醒对象发送所述第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
本实施例的功能逻辑可以参考图24所示的实施例，此处不再赘述。
需要说明的是：图24和图25所示的实施例除了可以应用于发送方的手机、PC等电子设备上运行的客户端，使得通过该客户端来实现生成、发送第二提醒消息等功能，在一些情况下也可以应用于服务端，使得服务端通过运行该实施例中包含的各个步骤来实现生成、发送第二提醒消息等功能。甚至，在一些情况下，图24和图25所示的实施例还可能应用于其他可能的执行主体，由这些执行主体通过运行该实施例中包含的各个步骤来实现生成、发送第二提醒消息等功能，本申请并不对此进行限制。
对应于图24或图25所示的实施例，图26是本申请一示例性实施例提供的一种提醒消息的展示方法的流程图。如图26所示，该方法可以包括以下步骤：
步骤2602，客户端接收与第一提醒消息相关的第二提醒消息。
步骤2604，所述客户端展示所述第二提醒消息包含的第二提醒事件描述信息，以及展示所述第一提醒消息对应的第一提醒事件描述信息。
在本实施例中，当第二提醒消息中包含第一提醒事件描述信息时，客户端可以获取该第二提醒消息包含的第一提醒事件描述信息，并对该第一提醒事件描述信息与第二提醒消息包含的第二提醒事件描述信息进行展示。
在本实施例中，第二提醒消息可能未包含第一提醒事件描述信息。在一实施方式中，第二提醒消息中可以包含该第一提醒消息的标识信息，则客户端可以根据该标识信息获取相应的第一提醒事件描述信息；例如，客户端可以根据该标识信息在历史提醒消息中进行搜索，以查找相应的第一提醒消息，并获取该第一提醒消息包含的第一提醒事件描述信息；再例如，客户端可以根据该标识信息向服务端发起询问，以由服务端向该客户端返回相应的第一提醒消息或第一提醒事件描述信息。在另一实施方式中，第二提醒消息中可以包含会议关联标识，使得客户端确定该第二提醒消息存在相关联的第一提醒消息，则客户端可以向服务端发起与该第二提醒消息相关的询问；那么，如果发送方客户 端预先向服务端告知该第二提醒消息与该第一提醒消息之间的关联关系，服务端就可以基于该关联关系确定出该第一提醒消息，则客户端可以接收服务端返回的该第一提醒消息或第一提醒事件描述信息。
在本实施例中，所述客户端可以将所述第一提醒事件描述信息的至少一部分内容展示于所述第二提醒消息的展示区域，该展示区域可以包括该第二提醒消息专用的详情展示界面，或者上述的提醒消息管理页面中对应于该第二提醒消息的展示区域。
在本实施例中，所述客户端可以将所述第二提醒事件描述信息的至少一部分内容展示于所述第一提醒消息的展示区域，该展示区域可以包括该第一提醒消息专用的详情展示界面，或者上述的提醒消息管理页面中对应于该第一提醒消息的展示区域。
在本实施例中，所述客户端可以在所述第二提醒消息的展示区域内显示与所述第一提醒消息相关的第一触发选项；其中，当所述第一触发选项被触发时，所述客户端展示所述第一提醒消息中的第一提醒事件描述信息。当客户端已经获知第一提醒事件描述信息时，第一触发选项可以包括该第一提醒事件描述信息的概要信息，并基于对该第一触发选项的触发操作，由客户端示出该第一提醒事件描述信息的详情信息，该详情信息可以展示于第二提醒消息的展示区域内，或者展示于独立界面(比如该第一提醒消息专用的详情展示界面或者临时窗口界面等)；当客户端尚未获知第一提醒事件描述信息时，第一触发选项可以包括“点击了解关联事件”等指示性选项，并基于对该第一触发选项的触发操作，由客户端获取相应的第一提醒事件描述信息以供展示。
在本实施例中，所述客户端可以在所述第一提醒消息的展示区域内显示与所述第二提醒事件描述信息相关的第二触发选项；其中，当所述第二触发选项被触发时，所述客户端展示所述第二提醒事件描述信息。例如，第一触发选项可以包括该第二提醒事件描述信息的概要信息，并基于对该第一触发选项的触发操作，由客户端示出该第二提醒事件描述信息的详情信息，该详情信息可以展示于第一提醒消息的展示区域内，或者展示于独立界面(比如该第二提醒消息专用的详情展示界面或者临时窗口界面等)。
在本实施例中，所述客户端可以根据针对所述第二提醒消息的对应事件的触发操作，对该对应事件进行事件管理。例如，事件管理可以包括对该对应事件的暂停、中止、完成等，本申请并不对此进行限制。根据客户端的已登录用户的权限不同，该客户端可以实现不同类型的事件管理；而当已登录用户无权限时，该客户端可能无法实现事件管理。
需要说明的是：图26所示的实施例除了可以应用于接收方的手机、PC等电子设备上运行的客户端，使得通过该客户端来实现接收第二提醒消息以及展示第二提醒事件描 述信息、第一提醒事件描述信息等功能，在一些情况下也可以应用于服务端，使得服务端通过运行该实施例中包含的各个步骤来实现接收第二提醒消息、向接收方展示第二提醒事件描述信息和第一提醒事件描述信息(比如将第二提醒事件描述信息和第一提醒事件描述信息发送至接收方对应的客户端等)等功能。甚至，在一些情况下，图26所示的实施例还可能应用于其他可能的执行主体，由这些执行主体通过运行该实施例中包含的各个步骤来实现接收第二提醒消息、向接收方展示第二提醒事件描述信息和第一提醒事件描述信息等功能，本申请并不对此进行限制。
图27示出了根据本申请的一示例性实施例的电子设备的示意结构图。请参考图27，在硬件层面，该电子设备包括处理器2702、内部总线2704、网络接口2706、内存2708以及非易失性存储器2710，当然还可能包括其他业务所需要的硬件。处理器2702从非易失性存储器2710中读取对应的计算机程序到内存2708中然后运行，在逻辑层面上形成任务提醒装置。当然，除了软件实现方式之外，本申请并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图28，在软件实施方式中，该任务提醒装置可以包括：
第一指令接收单元2801，使客户端接收与会议提醒消息相关的任务提醒消息生成指令；
第一确定单元2802，使所述客户端确定提醒对象和任务描述信息；
第一发送单元2803，使所述客户端向所述提醒对象发送与所述会议提醒消息相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
可选的，所述第一指令接收单元2801具体用于：
使所述客户端在所述会议提醒消息的展示界面中，示出任务创建选项；
使所述客户端在收到针对所述任务创建选项的触发操作时，确定接收到所述任务提醒消息生成指令。
可选的，所述第一指令接收单元2801具体用于：
使所述客户端接收针对任务提醒消息的用户创建操作，以及针对所述任务提醒消息的会议绑定操作；
当所述会议绑定操作选取所述会议提醒消息时，使所述客户端确定接收到与所述会议提醒消息相关的任务提醒消息生成指令。
可选的，所述任务提醒消息还包含所述会议提醒消息中的会议描述信息。
可选的，所述提醒对象包括以下至少之一：
所述会议提醒消息对应的会议的参与者、所述客户端收到的对象选择操作选择的对象。
可选的，
当所述提醒对象未参与所述会议提醒消息对应的会议时，所述提醒对象具有对所述任务提醒消息的任务管理权限；
当所述提醒对象参与所述会议，且所述提醒对象被配置为任务负责人时，所述提醒对象具有对所述任务提醒消息的任务管理权限。
请参考图29，在软件实施方式中，该任务提醒装置可以包括：
第一消息接收单元2901，使客户端接收与会议提醒消息相关的任务提醒消息；
第一展示单元2902，使所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息。
可选的，所述第一展示单元2902使客户端通过下述方式中至少之一，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息：
使所述客户端将所述会议描述信息的至少一部分内容展示于所述任务提醒消息的展示区域；
使所述客户端将所述任务描述信息的至少一部分内容展示于所述会议提醒消息的展示区域。
可选的，所述第一展示单元2902使客户端通过下述方式中至少之一，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息：
使所述客户端在所述任务提醒消息的展示区域内显示与所述会议提醒消息相关的第一触发选项；其中，当所述第一触发选项被触发时，所述客户端展示所述会议提醒消息中的会议描述信息；
使所述客户端在所述会议提醒消息的展示区域内显示与所述任务描述信息相关的第二触发选项；其中，当所述第二触发选项被触发时，所述客户端展示所述任务描述信息。
可选的，还包括：
任务管理单元2903，使所述客户端根据针对所述任务提醒消息对应的任务事件的触发操作，对所述任务事件进行任务管理。
请参考图30，在软件实施方式中，该任务提醒装置可以包括：
第二指令接收单元3001，使客户端接收与会议提醒消息相关的任务提醒消息生成指 令；
第二确定单元3002，使所述客户端确定提醒对象和任务描述信息；
第二发送单元3003，使所述客户端向参与所述会议提醒消息对应的会议的提醒对象发送与所述会议相关的任务提醒消息、向未参与所述会议的提醒对象发送与所述会议无关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
请参考图31，在软件实施方式中，该任务提醒装置可以包括：
第二消息接收单元3101，使客户端接收与会议提醒消息相关的任务提醒消息；
用户类型确定单元3102，使所述客户端确定已登录用户是否参与所述会议提醒消息对应的会议；
第二展示单元3103，使所述客户端在所述已登录用户参与所述会议时，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息；所述客户端在所述已登录用户未参与所述会议时，展示所述任务提醒消息包含的任务描述信息。
请参考图32，在软件实施方式中，该任务提醒装置可以包括：
第四指令接收单元3201，使客户端接收与会议相关的任务提醒消息生成指令；
第四确定单元3202，使所述客户端确定提醒对象和任务描述信息；
第五发送单元3203，使所述客户端向所述提醒对象发送与所述会议相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
请参考图33，在软件实施方式中，该任务提醒装置可以包括：
第二生成单元3301，使客户端根据提醒对象、任务描述信息和会议，生成与所述会议相关的任务提醒消息；
第六发送单元3302，使所述客户端向所述提醒对象发送所述任务提醒消息，所述任务提醒消息包含所述任务描述信息。
请参考图34，在软件实施方式中，该任务提醒装置可以包括：
第四消息接收单元3401，使客户端接收与会议相关的任务提醒消息；
第四展示单元3402，使所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息。
图35示出了根据本申请的一示例性实施例的电子设备的示意结构图。请参考图35，在硬件层面，该电子设备包括处理器3502、内部总线3504、网络接口3506、内存3508以及非易失性存储器3510，当然还可能包括其他业务所需要的硬件。处理器3502从非易失性存储器3510中读取对应的计算机程序到内存3508中然后运行，在逻辑层面上形 成提醒消息的生成装置。当然，除了软件实现方式之外，本申请并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图36，在软件实施方式中，该提醒消息的生成装置可以包括：
第三指令接收单元3601，使客户端接收与第一提醒消息相关的提醒消息生成指令；
第三确定单元3602，使所述客户端确定提醒对象和提醒事件描述信息；
第三发送单元3603，使所述客户端向所述提醒对象发送与所述第一提醒消息相关的第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
请参考图37，在软件实施方式中，该提醒消息的生成装置可以包括：
第一生成单元3701，使客户端根据提醒对象、提醒事件描述信息和第一提醒消息，生成与所述第一提醒消息相关的第二提醒消息；
第四发送单元3702，使所述客户端向所述提醒对象发送所述第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
图38示出了根据本申请的一示例性实施例的电子设备的示意结构图。请参考图38，在硬件层面，该电子设备包括处理器3802、内部总线3804、网络接口3806、内存3808以及非易失性存储器3810，当然还可能包括其他业务所需要的硬件。处理器3802从非易失性存储器3810中读取对应的计算机程序到内存3808中然后运行，在逻辑层面上形成提醒消息的展示装置。当然，除了软件实现方式之外，本申请并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图39，在软件实施方式中，该提醒消息的展示装置可以包括：
第三消息接收单元3901，使客户端接收与第一提醒消息相关的第二提醒消息；
第三展示单元3902，使所述客户端展示所述第二提醒消息包含的第二提醒事件描述信息，以及展示所述第一提醒消息对应的第一提醒事件描述信息。
可选的，所述第三展示单元3902具体用于：
使所述客户端在所述第一提醒消息或所述第二提醒消息的展示区域中，对所述第一提醒事件描述信息和所述第二提醒事件描述信息进行关联展示。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、 媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
在一个典型的配置中，计算机包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这 些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
以上所述仅为本申请的较佳实施例而已，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。

Claims (48)

  1. 一种任务提醒方法，其特征在于，包括：
    客户端接收与会议提醒消息相关的任务提醒消息生成指令；
    所述客户端确定提醒对象和任务描述信息；
    所述客户端向所述提醒对象发送与所述会议提醒消息相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  2. 根据权利要求1所述的方法，其特征在于，所述客户端接收与会议提醒消息相关的任务提醒消息生成指令，包括：
    所述客户端在所述会议提醒消息的展示界面中，示出任务创建选项；
    所述客户端在收到针对所述任务创建选项的触发操作时，确定接收到所述任务提醒消息生成指令。
  3. 根据权利要求1所述的方法，其特征在于，所述客户端接收与会议提醒消息相关的任务提醒消息生成指令，包括：
    所述客户端接收针对任务提醒消息的用户创建操作，以及针对所述任务提醒消息的会议绑定操作；
    当所述会议绑定操作选取所述会议提醒消息时，所述客户端确定接收到与所述会议提醒消息相关的任务提醒消息生成指令。
  4. 根据权利要求1所述的方法，其特征在于，所述任务提醒消息还包含所述会议提醒消息中的会议描述信息。
  5. 根据权利要求1所述的方法，其特征在于，所述提醒对象包括以下至少之一：
    所述会议提醒消息对应的会议的参与者、所述客户端收到的对象选择操作选择的对象。
  6. 根据权利要求1所述的方法，其特征在于，
    当所述提醒对象未参与所述会议提醒消息对应的会议时，所述提醒对象具有对所述任务提醒消息的任务管理权限；
    当所述提醒对象参与所述会议，且所述提醒对象被配置为任务负责人时，所述提醒对象具有对所述任务提醒消息的任务管理权限。
  7. 一种任务提醒方法，其特征在于，包括：
    客户端接收与会议提醒消息相关的任务提醒消息；
    所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消 息中的会议描述信息。
  8. 根据权利要求7所述的方法，其特征在于，所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息，包括以下至少之一：
    所述客户端将所述会议描述信息的至少一部分内容展示于所述任务提醒消息的展示区域；
    所述客户端将所述任务描述信息的至少一部分内容展示于所述会议提醒消息的展示区域。
  9. 根据权利要求7所述的方法，其特征在于，所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息，包括以下至少之一：
    所述客户端在所述任务提醒消息的展示区域内显示与所述会议提醒消息相关的第一触发选项；其中，当所述第一触发选项被触发时，所述客户端展示所述会议提醒消息中的会议描述信息；
    所述客户端在所述会议提醒消息的展示区域内显示与所述任务描述信息相关的第二触发选项；其中，当所述第二触发选项被触发时，所述客户端展示所述任务描述信息。
  10. 根据权利要求7所述的方法，其特征在于，还包括：
    所述客户端根据针对所述任务提醒消息对应的任务事件的触发操作，对所述任务事件进行任务管理。
  11. 一种任务提醒方法，其特征在于，包括：
    客户端接收与会议提醒消息相关的任务提醒消息生成指令；
    所述客户端确定提醒对象和任务描述信息；
    所述客户端向参与所述会议提醒消息对应的会议的提醒对象发送与所述会议相关的任务提醒消息、向未参与所述会议的提醒对象发送与所述会议无关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  12. 一种任务提醒方法，其特征在于，包括：
    客户端接收与会议提醒消息相关的任务提醒消息；
    所述客户端确定已登录用户是否参与所述会议提醒消息对应的会议；
    所述客户端在所述已登录用户参与所述会议时，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息；所述客户端在所述已登录用户未参与所 述会议时，展示所述任务提醒消息包含的任务描述信息。
  13. 一种提醒消息的生成方法，其特征在于，包括：
    客户端接收与第一提醒消息相关的提醒消息生成指令；
    所述客户端确定提醒对象和提醒事件描述信息；
    所述客户端向所述提醒对象发送与所述第一提醒消息相关的第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
  14. 一种提醒消息的生成方法，其特征在于，包括：
    客户端根据提醒对象、提醒事件描述信息和第一提醒消息，生成与所述第一提醒消息相关的第二提醒消息；
    所述客户端向所述提醒对象发送所述第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
  15. 一种提醒消息的展示方法，其特征在于，包括：
    客户端接收与第一提醒消息相关的第二提醒消息；
    所述客户端展示所述第二提醒消息包含的第二提醒事件描述信息，以及展示所述第一提醒消息对应的第一提醒事件描述信息。
  16. 根据权利要求15所述的方法，其特征在于，所述客户端展示所述第二提醒消息包含的第二提醒事件描述信息，以及展示所述第一提醒消息包含的第一提醒事件描述信息，包括：
    所述客户端在所述第一提醒消息或所述第二提醒消息的展示区域中，对所述第一提醒事件描述信息和所述第二提醒事件描述信息进行关联展示。
  17. 一种任务提醒方法，其特征在于，包括：
    客户端接收与会议相关的任务提醒消息生成指令；
    所述客户端确定提醒对象和任务描述信息；
    所述客户端向所述提醒对象发送与所述会议相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  18. 一种任务提醒方法，其特征在于，包括：
    客户端根据提醒对象、任务描述信息和会议，生成与所述会议相关的任务提醒消息；
    所述客户端向所述提醒对象发送所述任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  19. 一种任务提醒方法，其特征在于，包括：
    客户端接收与会议相关的任务提醒消息；
    所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息。
  20. 一种任务提醒装置，其特征在于，包括：
    第一指令接收单元，使客户端接收与会议提醒消息相关的任务提醒消息生成指令；
    第一确定单元，使所述客户端确定提醒对象和任务描述信息；
    第一发送单元，使所述客户端向所述提醒对象发送与所述会议提醒消息相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  21. 根据权利要求20所述的装置，其特征在于，所述第一指令接收单元具体用于：
    使所述客户端在所述会议提醒消息的展示界面中，示出任务创建选项；
    使所述客户端在收到针对所述任务创建选项的触发操作时，确定接收到所述任务提醒消息生成指令。
  22. 根据权利要求20所述的装置，其特征在于，所述第一指令接收单元具体用于：
    使所述客户端接收针对任务提醒消息的用户创建操作，以及针对所述任务提醒消息的会议绑定操作；
    当所述会议绑定操作选取所述会议提醒消息时，使所述客户端确定接收到与所述会议提醒消息相关的任务提醒消息生成指令。
  23. 根据权利要求20所述的装置，其特征在于，所述任务提醒消息还包含所述会议提醒消息中的会议描述信息。
  24. 根据权利要求20所述的装置，其特征在于，所述提醒对象包括以下至少之一：
    所述会议提醒消息对应的会议的参与者、所述客户端收到的对象选择操作选择的对象。
  25. 根据权利要求20所述的装置，其特征在于，
    当所述提醒对象未参与所述会议提醒消息对应的会议时，所述提醒对象具有对所述任务提醒消息的任务管理权限；
    当所述提醒对象参与所述会议，且所述提醒对象被配置为任务负责人时，所述提醒对象具有对所述任务提醒消息的任务管理权限。
  26. 一种任务提醒装置，其特征在于，包括：
    第一消息接收单元，使客户端接收与会议提醒消息相关的任务提醒消息；
    第一展示单元，使所述客户端展示所述任务提醒消息包含的任务描述信息，以及展 示所述会议提醒消息中的会议描述信息。
  27. 根据权利要求26所述的装置，其特征在于，所述第一展示单元使客户端通过下述方式中至少之一，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息：
    使所述客户端将所述会议描述信息的至少一部分内容展示于所述任务提醒消息的展示区域；
    使所述客户端将所述任务描述信息的至少一部分内容展示于所述会议提醒消息的展示区域。
  28. 根据权利要求26所述的装置，其特征在于，所述第一展示单元使客户端通过下述方式中至少之一，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息：
    使所述客户端在所述任务提醒消息的展示区域内显示与所述会议提醒消息相关的第一触发选项；其中，当所述第一触发选项被触发时，所述客户端展示所述会议提醒消息中的会议描述信息；
    使所述客户端在所述会议提醒消息的展示区域内显示与所述任务描述信息相关的第二触发选项；其中，当所述第二触发选项被触发时，所述客户端展示所述任务描述信息。
  29. 根据权利要求26所述的装置，其特征在于，还包括：
    任务管理单元，使所述客户端根据针对所述任务提醒消息对应的任务事件的触发操作，对所述任务事件进行任务管理。
  30. 一种任务提醒装置，其特征在于，包括：
    第二指令接收单元，使客户端接收与会议提醒消息相关的任务提醒消息生成指令；
    第二确定单元，使所述客户端确定提醒对象和任务描述信息；
    第二发送单元，使所述客户端向参与所述会议提醒消息对应的会议的提醒对象发送与所述会议相关的任务提醒消息、向未参与所述会议的提醒对象发送与所述会议无关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  31. 一种任务提醒装置，其特征在于，包括：
    第二消息接收单元，使客户端接收与会议提醒消息相关的任务提醒消息；
    用户类型确定单元，使所述客户端确定已登录用户是否参与所述会议提醒消息对应的会议；
    第二展示单元，使所述客户端在所述已登录用户参与所述会议时，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息；所述客户端在所述已登录用户未参与所述会议时，展示所述任务提醒消息包含的任务描述信息。
  32. 一种提醒消息的生成装置，其特征在于，包括：
    第三指令接收单元，使客户端接收与第一提醒消息相关的提醒消息生成指令；
    第三确定单元，使所述客户端确定提醒对象和提醒事件描述信息；
    第三发送单元，使所述客户端向所述提醒对象发送与所述第一提醒消息相关的第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
  33. 一种提醒消息的生成装置，其特征在于，包括：
    第一生成单元，使客户端根据提醒对象、提醒事件描述信息和第一提醒消息，生成与所述第一提醒消息相关的第二提醒消息；
    第四发送单元，使所述客户端向所述提醒对象发送所述第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
  34. 一种提醒消息的展示装置，其特征在于，包括：
    第三消息接收单元，使客户端接收与第一提醒消息相关的第二提醒消息；
    第三展示单元，使所述客户端展示所述第二提醒消息包含的第二提醒事件描述信息，以及展示所述第一提醒消息对应的第一提醒事件描述信息。
  35. 根据权利要求34所述的装置，其特征在于，所述第三展示单元具体用于：
    使所述客户端在所述第一提醒消息或所述第二提醒消息的展示区域中，对所述第一提醒事件描述信息和所述第二提醒事件描述信息进行关联展示。
  36. 一种任务提醒装置，其特征在于，包括：
    第四指令接收单元，使客户端接收与会议相关的任务提醒消息生成指令；
    第四确定单元，使所述客户端确定提醒对象和任务描述信息；
    第五发送单元，使所述客户端向所述提醒对象发送与所述会议相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  37. 一种任务提醒装置，其特征在于，包括：
    第二生成单元，使客户端根据提醒对象、任务描述信息和会议，生成与所述会议相关的任务提醒消息；
    第六发送单元，使所述客户端向所述提醒对象发送所述任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  38. 一种任务提醒装置，其特征在于，包括：
    第四消息接收单元，使客户端接收与会议相关的任务提醒消息；
    第四展示单元，使所述客户端展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息。
  39. 一种任务提醒方法，其特征在于，包括：
    接收与会议提醒消息相关的任务提醒消息生成指令；
    确定提醒对象和任务描述信息；
    向所述提醒对象发送与所述会议提醒消息相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  40. 一种任务提醒方法，其特征在于，包括：
    接收与会议提醒消息相关的任务提醒消息；
    展示所述任务提醒消息包含的任务描述信息，以及展示所述会议提醒消息中的会议描述信息。
  41. 一种任务提醒方法，其特征在于，包括：
    接收与会议提醒消息相关的任务提醒消息生成指令；
    确定提醒对象和任务描述信息；
    向参与所述会议提醒消息对应的会议的提醒对象发送与所述会议相关的任务提醒消息、向未参与所述会议的提醒对象发送与所述会议无关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  42. 一种任务提醒方法，其特征在于，包括：
    接收与会议提醒消息相关的任务提醒消息；
    确定已登录用户是否参与所述会议提醒消息对应的会议；
    在所述已登录用户参与所述会议时，展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息；客户端在所述已登录用户未参与所述会议时，展示所述任务提醒消息包含的任务描述信息。
  43. 一种提醒消息的生成方法，其特征在于，包括：
    接收与第一提醒消息相关的提醒消息生成指令；
    确定提醒对象和提醒事件描述信息；
    向所述提醒对象发送与所述第一提醒消息相关的第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
  44. 一种提醒消息的生成方法，其特征在于，包括：
    根据提醒对象、提醒事件描述信息和第一提醒消息，生成与所述第一提醒消息相关的第二提醒消息；
    向所述提醒对象发送所述第二提醒消息，所述第二提醒消息包含所述提醒事件描述信息。
  45. 一种提醒消息的展示方法，其特征在于，包括：
    接收与第一提醒消息相关的第二提醒消息；
    展示所述第二提醒消息包含的第二提醒事件描述信息，以及展示所述第一提醒消息对应的第一提醒事件描述信息。
  46. 一种任务提醒方法，其特征在于，包括：
    接收与会议相关的任务提醒消息生成指令；
    确定提醒对象和任务描述信息；
    向所述提醒对象发送与所述会议相关的任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  47. 一种任务提醒方法，其特征在于，包括：
    根据提醒对象、任务描述信息和会议，生成与所述会议相关的任务提醒消息；
    向所述提醒对象发送所述任务提醒消息，所述任务提醒消息包含所述任务描述信息。
  48. 一种任务提醒方法，其特征在于，包括：
    接收与会议相关的任务提醒消息；
    展示所述任务提醒消息包含的任务描述信息，以及展示所述会议的会议描述信息。
PCT/CN2018/088810 2017-06-06 2018-05-29 任务提醒方法及装置、提醒消息的生成和展示方法及装置 WO2018223869A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
SG11201911449PA SG11201911449PA (en) 2017-06-06 2018-05-29 Task reminder method and apparatus, and method and apparatus for generating and presenting reminder message
US16/705,054 US20200111060A1 (en) 2017-06-06 2019-12-05 Task reminder method and apparatus, and method and apparatus for generating and presenting reminder message

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710417476.9A CN109005098B (zh) 2017-06-06 2017-06-06 任务提醒方法及装置、提醒消息的生成和展示方法及装置
CN201710417476.9 2017-06-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/705,054 Continuation US20200111060A1 (en) 2017-06-06 2019-12-05 Task reminder method and apparatus, and method and apparatus for generating and presenting reminder message

Publications (1)

Publication Number Publication Date
WO2018223869A1 true WO2018223869A1 (zh) 2018-12-13

Family

ID=64566489

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088810 WO2018223869A1 (zh) 2017-06-06 2018-05-29 任务提醒方法及装置、提醒消息的生成和展示方法及装置

Country Status (5)

Country Link
US (1) US20200111060A1 (zh)
CN (1) CN109005098B (zh)
SG (1) SG11201911449PA (zh)
TW (1) TW201903663A (zh)
WO (1) WO2018223869A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822092A (zh) * 2019-11-18 2021-05-18 腾讯科技（深圳）有限公司 消息提醒方法、装置及计算机可读存储介质

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107809517B (zh) * 2016-09-08 2020-07-10 阿里巴巴集团控股有限公司 事件展示方法及装置
CN109981303B (zh) * 2019-01-28 2023-06-20 平安科技（深圳）有限公司 会议信息推送方法、装置、存储介质及终端设备
KR20200123560A (ko) * 2019-04-22 2020-10-30 라인플러스 주식회사 리마인더 메시지를 제공하는 방법, 시스템, 및 비-일시적인 컴퓨터 판독가능한 기록 매체
CN112083978B (zh) * 2019-06-12 2024-01-16 钉钉控股（开曼）有限公司 事件分享方法及装置
CN111934984B (zh) * 2020-07-30 2023-05-12 北京达佳互联信息技术有限公司 一种消息反馈方法、装置、电子设备及存储介质
CN113992611A (zh) * 2021-08-30 2022-01-28 北京百度网讯科技有限公司 一种任务信息管理方法、装置、设备及存储介质
CN113839855B (zh) * 2021-09-22 2023-03-24 武汉夜莺科技有限公司 会话提醒方法、装置及存储介质
US11620041B1 (en) * 2022-01-31 2023-04-04 Zoom Video Communications, Inc. Reminder notifications for messages
EP4266224A1 (en) * 2022-04-21 2023-10-25 Nokia Technologies Oy A system and method for using non-focus meeting periods to increase productivity
CN114819923B (zh) * 2022-06-28 2022-12-13 荣耀终端有限公司 工作任务提醒方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1648908A (zh) * 2004-01-28 2005-08-03 微软公司 向工程和会议分配时间的时间管理表示和自动化
US20080103867A1 (en) * 2006-10-27 2008-05-01 Darryl Moore Systems, methods and computer program products for user-selected calendar and task alerts
CN104468137A (zh) * 2013-09-12 2015-03-25 华为技术有限公司 网络会议控制方法和装置
CN105631607A (zh) * 2016-01-26 2016-06-01 福建捷联电子有限公司 智慧党建系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104734942B (zh) * 2015-03-13 2018-02-02 日立楼宇技术（广州）有限公司 一种会议管理方法、装置及系统
CN104954151A (zh) * 2015-04-24 2015-09-30 成都腾悦科技有限公司 一种基于网络会议的会议纪要提取与推送方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1648908A (zh) * 2004-01-28 2005-08-03 微软公司 向工程和会议分配时间的时间管理表示和自动化
US20080103867A1 (en) * 2006-10-27 2008-05-01 Darryl Moore Systems, methods and computer program products for user-selected calendar and task alerts
CN104468137A (zh) * 2013-09-12 2015-03-25 华为技术有限公司 网络会议控制方法和装置
CN105631607A (zh) * 2016-01-26 2016-06-01 福建捷联电子有限公司 智慧党建系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822092A (zh) * 2019-11-18 2021-05-18 腾讯科技（深圳）有限公司 消息提醒方法、装置及计算机可读存储介质
CN112822092B (zh) * 2019-11-18 2022-07-26 腾讯科技（深圳）有限公司 消息提醒方法、装置及计算机可读存储介质

Also Published As

Publication number Publication date
CN109005098B (zh) 2021-09-28
US20200111060A1 (en) 2020-04-09
TW201903663A (zh) 2019-01-16
CN109005098A (zh) 2018-12-14
SG11201911449PA (en) 2020-01-30

Similar Documents

Publication Publication Date Title
WO2018223869A1 (zh) 任务提醒方法及装置、提醒消息的生成和展示方法及装置
US11317240B2 (en) Geo-location based event gallery
WO2020135142A1 (zh) 项目群组的创建方法、项目管理方法及装置
WO2017008629A1 (zh) 工作状态的提示方法及装置
WO2018166361A1 (zh) 会话筛选方法及装置
WO2019062569A1 (zh) 消息展示方法及装置
TW201927014A (zh) 通訊方法及裝置
WO2019062586A1 (zh) 会议信息的显示方法及装置
TW202010295A (zh) 群組通信方法、裝置和設備
TW201813418A (zh) 通訊方法及裝置
US11714517B2 (en) Method, apparatus and computer program product for providing a member calendar in a group-based communication system
WO2019109880A1 (zh) 群组任务的信息获取方法及装置
US11477315B2 (en) Contact information exchanging and content system and method for networking and marketing
WO2019062587A1 (zh) 任务生成方法及装置
TWI795389B (zh) 活動提醒方法、活動提醒消息產生方法及裝置
US20150026595A1 (en) Detection of shared content viewed by attendees in online meetings
US11699133B2 (en) Method, apparatus and computer program product for providing a channel calendar in a group-based communication system
TW201911158A (zh) 考勤設置方法及裝置
US11294557B2 (en) Team configuration method, and method and apparatus for sharing team configuration solution
TW201830305A (zh) 事件處理方法及裝置
US20210019705A1 (en) Method and apparatus for sharing data across groups
WO2019091323A1 (zh) 批量呼叫方法及装置
WO2019015507A1 (zh) 通讯方法及装置
WO2019019929A1 (zh) 签名档的生成方法、签名档模板的分享方法及装置
US20180139165A1 (en) Dynamic authorization using internet-based social networks

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18814152

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18814152

Country of ref document: EP

Kind code of ref document: A1