WO2018223860A1 - 活动提醒方法、活动提醒消息生成方法及装置 - Google Patents

活动提醒方法、活动提醒消息生成方法及装置 Download PDF

Info

Publication number
WO2018223860A1
WO2018223860A1 PCT/CN2018/088652 CN2018088652W WO2018223860A1 WO 2018223860 A1 WO2018223860 A1 WO 2018223860A1 CN 2018088652 W CN2018088652 W CN 2018088652W WO 2018223860 A1 WO2018223860 A1 WO 2018223860A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
reminder
client
activity
user
Prior art date
Application number
PCT/CN2018/088652
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 阿里巴巴集团控股有限公司
Publication of WO2018223860A1 publication Critical patent/WO2018223860A1/zh
Priority to US16/705,115 priority Critical patent/US20200111059A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • 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
    • 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
    • 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
    • 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/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management

Definitions

  • the present application relates to the field of communications technologies, and in particular, to an activity reminding method, an activity reminding message generating method, and a device.
  • 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 message in the related art is applied to all scenarios, resulting in some important events that are more demanding for time limit and the like, and cannot be effectively highlighted; in particular, when the user receives more reminder messages or even is abused, It is easy to cause the above important events to be ignored, and the reminder effect of the reminder message is limited.
  • the present application provides an activity reminding method, an activity reminding message generating method, and a device, which can quickly implement an event reminder.
  • an activity reminding method including:
  • the client receives an alert message generation instruction for the activity type
  • the client sends an alert message to the reminder object, where the alert message includes the activity description information.
  • an activity reminding method including:
  • the client receives an alert message of the activity type
  • the client displays activity description information included in the reminder message
  • the client according to the received user triggering operation for the activity description information, returns a corresponding response message to the sender of the reminder message, where the response message includes the activity description of the user triggering operation indication.
  • Information on the acceptance status of the information is provided.
  • a method for generating an activity reminding message including:
  • the client receives the alert message generation instruction
  • the client displays an alternative message type of the reminder message
  • the client generates a corresponding message according to the selected message type.
  • an activity reminding device including:
  • Receiving unit so that the client receives an alert message generating instruction for the activity type
  • an activity reminding device comprising:
  • a first receiving unit configured to enable the client to receive an alert message of an activity type
  • Displaying unit causing the client to display activity description information included in the reminder message
  • the client causing the client to return a corresponding response message to the sender of the alert message according to the received user triggering operation for the activity description information, where the response message includes the target of the user triggering the operation indication
  • the activity describes information about the acceptance status of the information.
  • an activity reminding message generating apparatus including:
  • Receiving unit so that the client receives the reminder message generating instruction
  • the client is configured to display an alternate message type of the reminder message
  • the implementing unit is configured to enable the client to generate a corresponding message according to the selected message type.
  • an activity reminding method including:
  • the client generates a reminder message according to the activity description information and the reminder object;
  • the client sends an alert message to the reminder object, where the alert message includes the activity description information.
  • an activity reminding device including:
  • the present application can separately issue a reminder message for an event event having a higher requirement in terms of time limit and the like, and can effectively distinguish it from other types of reminder messages, thereby even When the user receives a larger number of reminder messages, the above-mentioned event events can still be quickly distinguished and identified based on the message type to avoid omissions.
  • FIG. 1 is a schematic structural diagram of an activity reminding system according to an exemplary embodiment of the present application
  • 2A is a flowchart of a method for reminding an activity based on a sender side according to an exemplary embodiment of the present application
  • FIG. 2B is a flowchart of another method for reminding an activity based on a sender side according to an exemplary embodiment of the present application
  • FIG. 3 is a flowchart of a method for reminding an activity based on a receiver side according to an exemplary embodiment of the present application
  • FIG. 4 is a flowchart of a method for generating an activity reminder message according to an exemplary embodiment of the present application
  • FIG. 5 is a schematic diagram of a sender side reminder message management page provided by an exemplary embodiment of the present application.
  • FIG. 6 is a schematic diagram of a message type selection page on the sender side according to an exemplary embodiment of the present application
  • FIG. 7 is a schematic diagram of a new conference page on the sender side according to an exemplary embodiment of the present application.
  • FIG. 8 is a schematic diagram of a sender side converting a communication message into a reminder message according to an exemplary embodiment of the present application
  • FIG. 9 is a schematic diagram of a reminder message management page on the receiving side according to an exemplary embodiment of the present application.
  • FIG. 10 is a schematic diagram of a reminder message detail page on the receiving side according to an exemplary embodiment of the present application.
  • FIG. 11 is a schematic diagram of another recipient side reminder message detail page provided by an exemplary embodiment of the present application.
  • FIG. 12 is a schematic diagram of another sender side reminder message management page provided by an exemplary embodiment of the present application.
  • FIG. 13A is a schematic diagram of a response side page of a sender side according to an exemplary embodiment of the present application.
  • FIG. 13B is a schematic diagram of another sender side response detail page provided by an exemplary embodiment of the present application.
  • FIG. 14 is a schematic diagram of a reason input window on a receiving side according to an exemplary embodiment of the present application.
  • FIG. 15 is a schematic diagram of still another response side page of the sender side according to an exemplary embodiment of the present application.
  • FIG. 16 is a schematic diagram of a receiving side requesting an adjustment request by a reminder message detail page according to an exemplary embodiment of the present application
  • FIG. 17 is another schematic diagram of receiving, by the receiver side, an adjustment request by using a reminder message detail page according to an exemplary embodiment of the present application
  • FIG. 18 is another schematic diagram of receiving, by the receiver side, an adjustment request by using a reminder message detail page according to an exemplary embodiment of the present application
  • FIG. 19 is a schematic diagram of a sender side processing adjustment request by a response detail page according to an exemplary embodiment of the present application.
  • FIG. 20 is a schematic diagram of prompting an adjusted conference description information by a sender side according to an exemplary embodiment of the present application
  • FIG. 21 is a schematic diagram of a method for prompting an adjusted conference description information in a new conference reminder message by a receiver side according to an exemplary embodiment of the present application
  • FIG. 22 is a schematic diagram of a page for managing a calendar according to an exemplary embodiment of the present application.
  • FIG. 23 is a schematic diagram of a classification and screening display of an alert message in an alert message management page according to an exemplary embodiment of the present application.
  • FIG. 24 is a schematic diagram of a method for creating a conference reminder message on a PC side according to an exemplary embodiment of the present application.
  • FIG. 25 is another schematic diagram of creating a conference reminder message on a PC side according to an exemplary embodiment of the present application.
  • FIG. 26 is still another schematic diagram of creating a conference reminder message on a PC side 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 disclosure.
  • FIG. 28 is a block diagram of an activity reminding device based on a sender side according to an exemplary embodiment of the present application.
  • FIG. 29 is a block diagram of an activity reminder device based on a receiver side according to an exemplary embodiment of the present application.
  • FIG. 30 is a block diagram of another activity-based reminder device based on a sender side according to an exemplary embodiment of the present application.
  • FIG. 31 is a schematic structural diagram of another electronic device according to an exemplary embodiment of the present disclosure.
  • FIG. 32 is a block diagram of an activity reminding message generating apparatus according to an exemplary embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of an activity 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 an activity reminding scheme.
  • the mobile enterprise 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 the processing of external events such as ordering, purchasing, etc.
  • the handling of internal events such as log events, such as the processing of external events such as ordering, purchasing, etc., is not limited in this application.
  • the mobile enterprise 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 enterprise office platform.
  • the enterprise 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.
  • 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 an activity type reminding message to the other one or more electronic devices through the network 12 to implement the activity 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.
  • FIG. 2A is a flowchart of a method for reminding an activity based on a sender side according to an exemplary embodiment of the present application. As shown in FIG. 2A, the method is applied to an electronic device used by a sender, and may include the following steps:
  • Step 202A The client of the mobile enterprise office platform obtains a reminder message generation instruction for the activity type.
  • the mobile enterprise office platform can provide multiple ways to generate the reminder message, and thus there are multiple ways to obtain the above-mentioned message generation instruction for the activity type reminder message, which is not limited in this application; Any of the manners for generating the alert message applicable in the related art may be applied to the present application to generate an alert message of the activity type.
  • the client may receive a user creation operation for the reminder message, and a user selection operation for the type information of the reminder message, and when the type information selected by the user selection operation is an activity type, The client determines to obtain the message generation instruction. For example, the client may first provide a user (in this embodiment, the sender) with a creation option for the reminder message. When the user triggers the creation option by the user creation operation, the client may further provide the user with a reminder message. Selecting a message type for the user to select the type information of the reminder message to be created by the user selection operation; or, the client may directly provide the user with a creation option corresponding to each type of reminder message, and the user triggers the activity type. When the creation option corresponding to the reminder message is completed, the above-mentioned user creation operation and user selection operation can be completed simultaneously to create an activity type reminder message.
  • the client may receive a user-triggered operation for a communication message within the mobile enterprise office platform, the user-triggered operation for instructing the client to convert the communication message into a reminder message;
  • the client includes the preset type of activity description information in the message content of the communication message, it is determined that the message generation instruction is acquired.
  • the foregoing communication message may include a received message or a sent message in any communication session page in the client, and may be called when the user performs a preset operation such as clicking, long pressing, and heavy pressing on the instant messaging message.
  • a plurality of processing options for the communication message such as copying, deleting, forwarding, converting, etc., wherein the user can complete the above-mentioned user triggering operation by selecting a "conversion" processing option, so that the client extracts the message content of the communication message and generates corresponding Reminder message.
  • the client may generate the message content of the communication message as an activity according to the recognition result of the message content of the communication message, if the message content includes a preset type of activity description information. Type of reminder message.
  • the client can obtain the foregoing recognition result in multiple ways.
  • the client can actively identify the message content of the communication message and generate a corresponding recognition result; in another case, the client can initiate an identification request to the server and receive the communication returned by the server.
  • the recognition result of the message content of the message in another case, the client may display the candidate message type providing the message to the user, and determine the corresponding recognition result according to the user's selection result, for example, when the user selects the activity type.
  • the client can determine that the recognition result is an activity description information including a preset type.
  • the client may add the activity description information to the alert message of the activity type to be generated, and may also be the communication message.
  • the associated communication party is added as a reminder object. For example, suppose the triggered communication message is “Tomorrow 2-4 pm in Room 201 of Building 2 to discuss the X project...”, the activity description information that the client can determine includes: the activity time information is “Tomorrow 2-4 pm "(It can be converted into a specific year, month and day form), the event location information is "Room 201, Building 2", and the activity topic information is "Discussion X Project", etc., and the associated communication party of the communication message may include corresponding Sender and receiver, etc.
  • the activity type reminder message is used to implement a reminder function for the activity; wherein the activity can be understood as participation by multiple people and completing certain actions in order to achieve the corresponding purpose, for example, the activities in the present application may include : Meetings, dinners, excursions, discussions, etc., this application does not limit this.
  • Step 204A The client determines the event description information corresponding to the reminder object and the activity type.
  • the activity description information may include at least one of the following: activity topic information, event location information, activity form information (such as offline meeting, online meeting, etc., such as video conference, conference call, etc.), activity time Information (such as the start time of the event, the end of the event; or, such as the start time of the event and the duration of the event; or, for example, only the start time of the event; or other circumstances).
  • the activity description information may include one or more activity topics at the same time, or may include one or more activity sites at the same time, and may separately indicate the activity location and activity time information corresponding to each activity theme to further clarify the activity situation.
  • Step 206A The client sends a reminder message to the reminder object, where the reminder message includes the activity description information.
  • the client may send the reminder message at a default sending time or a sending time set by the user, according to a default message type or a message type set by the user.
  • the user can implement the timing transmission of the activity type reminder message by setting the sending time.
  • the sending time can be any time that has not occurred yet.
  • the user can directly set the absolute time such as “15:25 today”. It can also be set to a relative time such as "30 minutes before the start of the event", or any other form of time.
  • the user can set different types of reminders by setting the message type.
  • the message type may include an "in-app" instant messaging message, a short message, a phone (such as a voice broadcast message content, etc.), and the user may select only one type.
  • the message type enables the client to send the reminder message only in a single form, or can also select multiple message types, so that the client sends the reminder message in multiple forms at the same time.
  • the reminder object as the recipient may respond to the alert message sent by the sender, and the client may receive a response message returned by the alert object, where the response message includes the alert object for the activity Determining the status information of the information; the client may then display the reminder object in association with the corresponding response message for the sender to view.
  • the acceptance status information indicates whether the recipient agrees with the activity description information included in the alert message of the activity type; for example, when the acceptance status information is “consent”, indicating that it can accept the “activity theme” defined by the activity description information, Activity location", “activity time”, etc., thus having a high probability of participating in related activities; and when the acceptance status information is "rejected”, indicating that it may not be able to accept at least a part of the activity description information, thereby having a high probability of being unable to participate in related activities .
  • the response message when the acceptance status information is a rejection, the response message further includes: a reason for the rejection, for example, the receiving party can clearly indicate that it is unable to participate due to reasons such as “too far from the activity place” and “too early time of the activity” Related activities help the sender to adjust the activity in time to facilitate the probability of the reminder participating in the activity.
  • a reason for the rejection for example, the receiving party can clearly indicate that it is unable to participate due to reasons such as “too far from the activity place” and “too early time of the activity” Related activities help the sender to adjust the activity in time to facilitate the probability of the reminder participating in the activity.
  • the above “rejection reason” may be optional; or it may be a required item when the recipient selects “reject” to ensure that the sender can adjust the activity accordingly, and then enhance the reminder object to participate in the activity. The probability.
  • the client may add a corresponding activity event to the management calendar in the mobile enterprise office platform according to the activity description information, so as to improve management efficiency and convenience of the event event.
  • the management calendar may contain multiple types of management events, and for the above-mentioned activity events and other management events, different display attributes may be adopted in the management calendar, so that the sender can quickly identify and distinguish in the viewing process.
  • the client may receive an adjustment request that is raised by the reminder object for at least one item of the activity description information, and the client may receive a user confirmation operation for the adjustment request, Sending a new reminder message to the reminder object based on the adjusted activity description information; or sending an adjustment instruction for the reminder message to the reminder object based on the adjusted activity description information, so that the client used by the reminder object is used
  • the activity description information in the previously received reminder message may be adjusted according to the adjustment instruction.
  • the client may automatically resend the reminder message to the reminder object to improve the reminder success rate.
  • the client can display a repeated reminding option for the reminding object, so that the user can determine whether the repeated reminding is needed according to the actual situation, and implement a user triggering operation on the repeated reminding option when determining that the repeated reminding is needed, so that the client is The reminder message is resent to the reminder object when a user triggering operation for the repeat reminder option is received.
  • the reminder message may include a default or user-set reminder time point, a default or a user-set reminder mode, so that the reminder object is based on the reminder mode at the reminder time point.
  • An activity reminder is made, and the reminder content is related to the activity description information.
  • the reminding time point may be any time before the event start time or the event start time, such as 5 minutes before the start of the event and half an hour before the start of the event.
  • the reminding method may include an “in-app” instant messaging message, a short message, a phone call, etc., and only one reminding method may be adopted, so that the reminding object only obtains a single form of event reminding, or a plurality of reminding manners may be adopted, so that the reminding object is simultaneously Get multiple forms of event reminders.
  • the client may further initiate a call request for the reminder object to establish an audio connection or a video connection according to an activity start time included in the activity description information, where
  • the call request can be used to establish an audio connection or a video connection between the client and the reminder object, or the call request can be used to establish an audio connection or a video connection or the like between the reminder objects.
  • clients or reminders who have not joined can also join in other ways.
  • the client may initiate a call reservation request to the server according to the activity start time included in the activity description information, and the client may initiate the call reservation request at any time before the event start time arrives; wherein the call is The reservation request is used to instruct the server to initiate a call to at least one of the client and the reminder object at the start time of the activity to establish an audio connection or a video connection.
  • the server can start the activity start time according to the activity description information.
  • the activity start time initiates a call to at least one of the client and the reminder object to establish an audio connection or a video connection without the client separately transmitting the above-mentioned call reservation request or the like.
  • the server may only initiate a call to the client, so that the client establishes a corresponding audio connection or video connection in response to the call, and the reminding object may join the audio connection through other means. Or the video connection; or, the server may only initiate a call to the reminder object, so that the reminder object establishes a corresponding audio connection or video connection in response to the call, wherein the server may initiate a call to all the reminder objects at the same time, or may only be part of the call.
  • the client may obtain the activity form information included in the activity description information, where the activity form information is used to indicate that the corresponding activity is an online activity such as a conference call or a video conference, or an offline event such as a meal or a trip. Then, the client may initiate the above call request or call reservation request when determining that the activity form information is an online activity such as a conference call or a video conference, so that the sender and the reminder object are implemented through a corresponding audio connection or video connection.
  • the online event may be obtained from the activity description information, where the activity form information is used to indicate that the corresponding activity is an online activity such as a conference call or a video conference, or an offline event such as a meal or a trip. The online event.
  • FIG. 2B is a flowchart of another method for reminding an activity based on a sender side according to an exemplary embodiment of the present application. As shown in FIG. 2B, the method is applied to an electronic device used by a sender, and may include the following steps:
  • Step 202B The client of the mobile enterprise office platform generates a reminder message according to the activity description information and the reminder object.
  • the mobile enterprise office platform can provide multiple ways to generate the reminder message, and thus there are multiple ways to obtain the above-mentioned message generation instruction for the activity type reminder message, which is not limited in this application; Any of the manners for generating the alert message applicable in the related art may be applied to the present application to generate an alert message of the activity type.
  • the client receives a user creation operation for the reminder message, and a user selection operation for the type information of the reminder message; when the type information selected by the user selection operation is an activity type
  • the client generates a reminder message according to the activity type.
  • the client may first provide a user (in this embodiment, the sender) with a creation option for the reminder message.
  • the client may further provide the user with a reminder message. Selecting a message type for the user to select the type information of the reminder message to be created by the user selection operation; or, the client may directly provide the user with a creation option corresponding to each type of reminder message, and the user triggers the activity type.
  • the creation option corresponding to the reminder message is completed, the above-mentioned user creation operation and user selection operation can be completed simultaneously to create an activity type reminder message.
  • the client receives a user-triggered operation for a communication message, the user-triggered operation is used to instruct the client to convert the communication message into a reminder message; the client is identifying The reminder message is generated when the message content of the communication message includes a preset type of activity description information.
  • the foregoing communication message may include a received message or a sent message in any communication session page in the client.
  • a preset operation such as clicking, long pressing, and heavy pressing on the communication message, the call may be invoked.
  • the processing information of the communication message such as copying, deleting, forwarding, converting, etc., wherein the user can complete the above-mentioned user triggering operation by selecting a "conversion" processing option, so that the client extracts the message content of the communication message and generates a corresponding Reminder message.
  • the client may generate the message content of the communication message as an activity according to the recognition result of the message content of the communication message, if the message content includes a preset type of activity description information.
  • Type of reminder message may include a text message, and may also include other message types such as a voice message, a picture message, and a video message, which are not limited in this application.
  • the client can obtain the foregoing recognition result in multiple ways.
  • the client can actively identify the message content of the communication message and generate a corresponding recognition result; in another case, the client can initiate an identification request to the server and receive the communication returned by the server.
  • the recognition result of the message content of the message in another case, the client may display the candidate message type providing the message to the user, and determine the corresponding recognition result according to the user's selection result, for example, when the user selects the activity type.
  • the client can determine that the recognition result is an activity description information including a preset type.
  • the client may add the activity description information to the alert message of the activity type to be generated, and may also be the communication message.
  • the associated communication party is added as a reminder object. For example, suppose the triggered communication message is “Tomorrow 2-4 pm in Room 201 of Building 2 to discuss the X project...”, the activity description information that the client can determine includes: the activity time information is “Tomorrow 2-4 pm "(It can be converted into a specific year, month and day form), the event location information is "Room 201, Building 2", and the activity topic information is "Discussion X Project", etc., and the associated communication party of the communication message may include corresponding Sender and receiver, etc.
  • the activity type reminder message is used to implement a reminder function for the activity; wherein the activity can be understood as participation by multiple people and completing certain actions in order to achieve the corresponding purpose, for example, the activities in the present application may include : Meetings, dinners, excursions, discussions, etc., this application does not limit this.
  • the activity description information may include at least one of the following: activity topic information, event location information, activity form information (such as offline meeting, online meeting, etc., such as video conference, conference call, etc.), activity time Information (such as the start time of the event, the end of the event; or, such as the start time of the event and the duration of the event; or, for example, only the start time of the event; or other circumstances).
  • the activity description information may include one or more activity topics at the same time, or may include one or more activity sites at the same time, and may separately indicate the activity location and activity time information corresponding to each activity theme to further clarify the activity situation.
  • Step 204B The client sends a reminder message to the reminder object, where the reminder message includes the activity description information.
  • the client may send the reminder message at a default sending time or a sending time set by the user, according to a default message type or a message type set by the user.
  • the user can implement the timing transmission of the activity type reminder message by setting the sending time.
  • the sending time can be any time that has not occurred yet.
  • the user can directly set the absolute time such as “15:25 today”. It can also be set to a relative time such as "30 minutes before the start of the event", or any other form of time.
  • the user can set different types of reminders by setting the message type.
  • the message type may include an "in-app" instant messaging message, a short message, a phone (such as a voice broadcast message content, etc.), and the user may select only one type.
  • the message type enables the client to send the reminder message only in a single form, or can also select multiple message types, so that the client sends the reminder message in multiple forms at the same time.
  • the reminder object as the recipient may respond to the alert message sent by the sender, and the client may receive a response message returned by the alert object, where the response message includes the alert object for the activity Determining the status information of the information; the client may then display the reminder object in association with the corresponding response message for the sender to view.
  • the acceptance status information indicates whether the recipient agrees with the activity description information included in the reminder message of the activity type; for example, when the acceptance status information is “consent”, indicating that it can accept the “activity theme” defined by the activity description information, Activity location", “activity time”, etc., thus having a high probability of participating in related activities; and when the acceptance status information is "rejected”, indicating that it may not be able to accept at least a part of the activity description information, thereby having a high probability of being unable to participate in related activities .
  • the response message when the acceptance status information is a rejection, the response message further includes: a reason for the rejection, for example, the receiving party can clearly indicate that it is unable to participate due to reasons such as “too far from the activity place” and “too early time of the activity” Related activities help the sender to adjust the activity in time to facilitate the probability of the reminder participating in the activity.
  • a reason for the rejection for example, the receiving party can clearly indicate that it is unable to participate due to reasons such as “too far from the activity place” and “too early time of the activity” Related activities help the sender to adjust the activity in time to facilitate the probability of the reminder participating in the activity.
  • the above “rejection reason” may be optional; or it may be a required item when the recipient selects “reject” to ensure that the sender can adjust the activity accordingly, and then enhance the reminder object to participate in the activity. The probability.
  • the client may add a corresponding activity event to the management calendar in the mobile enterprise office platform according to the activity description information, so as to improve management efficiency and convenience of the event event.
  • the management calendar may contain multiple types of management events, and for the above-mentioned activity events and other management events, different display attributes may be adopted in the management calendar, so that the sender can quickly identify and distinguish in the viewing process.
  • the client may receive an adjustment request that is raised by the reminder object for at least one item of the activity description information, and the client may receive a user confirmation operation for the adjustment request, Sending a new reminder message to the reminder object based on the adjusted activity description information; or sending an adjustment instruction for the reminder message to the reminder object based on the adjusted activity description information, so that the client used by the reminder object is used
  • the activity description information in the previously received reminder message may be adjusted according to the adjustment instruction.
  • the client may automatically resend the reminder message to the reminder object to improve the reminder success rate.
  • the client can display a repeated reminding option for the reminding object, so that the user can determine whether the repeated reminding is needed according to the actual situation, and implement a user triggering operation on the repeated reminding option when determining that the repeated reminding is needed, so that the client is The reminder message is resent to the reminder object when a user triggering operation for the repeat reminder option is received.
  • the reminder message may include a default or user-set reminder time point, a default or a user-set reminder mode, so that the reminder object is based on the reminder mode at the reminder time point.
  • An activity reminder is made, and the reminder content is related to the activity description information.
  • the reminding time point may be any time before the event start time or the event start time, such as 5 minutes before the start of the event and half an hour before the start of the event.
  • the reminding method may include an “in-app” instant messaging message, a short message, a phone call, etc., and only one reminding method may be adopted, so that the reminding object only obtains a single form of event reminding, or a plurality of reminding manners may be adopted, so that the reminding object is simultaneously Get multiple forms of event reminders.
  • the client may further initiate a call request for the reminder object to establish an audio connection or a video connection according to an activity start time included in the activity description information, where
  • the call request can be used to establish an audio connection or a video connection between the client and the reminder object, or the call request can be used to establish an audio connection or a video connection or the like between the reminder objects.
  • clients or reminders who have not joined can also join in other ways.
  • the client may initiate a call reservation request to the server according to the activity start time included in the activity description information, and the client may initiate the call reservation request at any time before the event start time arrives; wherein the call is The reservation request is used to instruct the server to initiate a call to at least one of the client and the reminder object at the start time of the activity to establish an audio connection or a video connection.
  • the server can start the activity start time according to the activity description information.
  • the activity start time initiates a call to at least one of the client and the reminder object to establish an audio connection or a video connection without the client separately transmitting the above-mentioned call reservation request or the like.
  • the server may only initiate a call to the client, so that the client establishes a corresponding audio connection or video connection in response to the call, and the reminding object may join the audio connection through other means. Or the video connection; or, the server may only initiate a call to the reminder object, so that the reminder object establishes a corresponding audio connection or video connection in response to the call, wherein the server may initiate a call to all the reminder objects at the same time, or may only be part of the call.
  • the client may obtain the activity form information included in the activity description information, where the activity form information is used to indicate that the corresponding activity is an online activity such as a conference call or a video conference, or an offline event such as a meal or a trip. Then, the client may initiate the above call request or call reservation request when determining that the activity form information is an online activity such as a conference call or a video conference, so that the sender and the reminder object are implemented through a corresponding audio connection or video connection.
  • the online event may be obtained from the activity description information, where the activity form information is used to indicate that the corresponding activity is an online activity such as a conference call or a video conference, or an offline event such as a meal or a trip. The online event.
  • FIG. 3 is a flowchart of a method for reminding an activity based on a receiver side according to an exemplary embodiment of the present application. As shown in FIG. 3, the method is applied to an electronic device used by a receiver, and may include the following steps:
  • Step 302 The client of the mobile enterprise office platform receives an alert message of an activity type.
  • Step 304 The client displays activity description information included in the reminder message.
  • Step 306 The client returns a corresponding response message to the sender of the reminder message according to the received user triggering operation for the activity description information, where the response message includes the target of the user triggering the operation indication.
  • the activity describes the acceptance status information of the information.
  • the client may directly return a corresponding response message to inform the sender of the corresponding acceptance status information.
  • the client may take different processing methods for the user to trigger the operation according to the recipient's acceptance status information. For example, when the acceptance status information of the user trigger operation indication is consent, the client may directly return the response message; and when the acceptance status information of the user trigger operation indication is rejection, the client may Further obtaining a corresponding reason for rejection, and adding the reason for the rejection to the response message to return to the sender.
  • the client may display the preset alternative rejection reason for the recipient to select, or the client may provide the receiver with a reason input box for the recipient to fill in the reason input box. The corresponding reason for rejection.
  • the filling of the reason for refusal may be non-mandatory, that is, the receiving party may decide whether to input the reason for refusal and does not affect the sending of the response message; or the filling of the reason for refusal may be mandatory, and the receiving party must input the reason for refusal Only afterwards can the response message be sent to ensure that the sender can understand the recipient's approval of the activity description information and make reasonable adjustments to the activity based on the reason for the rejection.
  • the client may add a corresponding activity to the management calendar in the mobile enterprise office platform according to the activity description information. event.
  • the process is similar to that of the sender. For details, refer to the description in the embodiment shown in FIG. 2A or FIG. 2B, and details are not described herein again.
  • the client may further acquire adjustment information for at least one item of the activity description information, and issue the inclusion to the sender.
  • the adjustment request of the adjustment information correspondingly, if the sender confirms accepting the adjustment request, the client on the sender side may adjust the activity description information, and further notify the reminder object of the adjusted activity description information, for example, The client on the sender side may send a new reminder message to the reminder object based on the adjusted activity description information, or may send an adjustment instruction for the reminder message to the reminder object based on the adjusted activity description information, and The activity description information in the reminder message is adjusted by the client on the receiving side according to the adjustment instruction.
  • the client may acquire the reminding time point and the reminding manner included in the reminder message, and initiate a corresponding to the reminding time point and the reminding mode to the server of the instant messaging application.
  • the activity reminder request then, the client may respond to the event reminding event initiated by the server at the reminding time point in the reminding manner to perform an event reminding to the receiving party, especially when receiving the event type reminding message
  • the recipient can be prevented from forgetting and missed the event or being late.
  • FIG. 4 is a flowchart of still another sender-side activity reminding method provided by an exemplary embodiment of the present application. As shown in FIG. 4, the method is applied to an electronic device used by a sender, and may include the following steps:
  • Step 402 The client of the mobile enterprise office platform obtains a reminder message generating instruction.
  • Step 404 The client displays an alternative message type of the reminder message.
  • the candidate message type may include at least one of the following: a standard type, a task type, an activity type, a reminder type, a voting type, and the like, which is not limited by the present application.
  • Step 406 The client generates a corresponding message according to the message type selected by the user.
  • the present application can separately issue a reminder message for an event event having a higher requirement in terms of time limit and the like, and can effectively distinguish it from other types of reminder messages, thereby even When the user receives a larger number of reminder messages, the above-mentioned event events can still be quickly distinguished and identified based on the message type to avoid omissions.
  • 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 enterprise WeChat client 2 and the enterprise WeChat client 3 corresponding to the two recipients are registered.
  • the user A can quickly create a conference reminder message on the mobile phone 13 and send it to the user B and the user C to implement the conference reminder for the user B and the user C.
  • FIG. 5 shows an alert message management page 50 included in the enterprise WeChat client 1 on the mobile phone 13 for centrally displaying all reminder messages received and sent by the user A, such as the task type from the user AA.
  • the reminder message the DING type reminder message (ie, the standard type of reminder message) sent by the user A itself, and the like.
  • the reminder message management page 50 can also be used to implement other functions related to the reminder message. For example, when the user A is triggered to trigger the new logo 51 in the upper right corner of the reminder message management page 50, the enterprise WeChat on the mobile phone 13 can be enabled.
  • the client 1 receives the user A creation operation for the reminder message by the user A, thereby switching to the message type selection page 60 shown in FIG. 6 to further select the message type of the reminder message to be created by the user A.
  • the message type selection page 60 may include a plurality of alternative message types, such as a type of DING suitable for notification, discussion, a task type suitable for task assignment, a type of task suitable for a meeting, an appointment type for an appointment, an appointment type for an appointment, and the like.
  • the enterprise WeChat client 1 can determine the message type of the reminder message to be created according to the received user A user selection operation for option 61, option 62 or option 63; for example, assume that the user selection operation for option 63 is received, The enterprise WeChat client 1 can determine that the user A wishes to create a reminder message of the conference type, thereby displaying the new conference page 70 shown in FIG. 7 for the user A to fill in the relevant information in the new conference page 70 for creating corresponding Meeting reminder message.
  • user A can input the "meeting theme” information in the conference description information in the input box 71, that is, the main content of the conference negotiation, such as "discussing the problem of the X project, and further development requirements". Wait.
  • the user A can input the "location" information in the conference description information in the input box 72, that is, the conference venue, such as "room 2, building 201".
  • User A can edit the meeting time information in the meeting description information in the time edit box 73, for example, the meeting start time is "14:00 on April 28, 2017", and the end time of the meeting is "16:00 on April 28, 2017.
  • the meeting time information can also take other forms, such as "meeting start time + meeting duration", etc., and this application does not limit this.
  • User A can set whether the currently created conference reminder message is automatically and repeatedly sent through option 74. For example, when user A is set to not need to repeat, the conference reminder message will only be received after user A triggers the "send" option 78. When the user A is set to need to repeat, the enterprise WeChat client 1 can repeatedly issue the meeting reminding message according to the repetition period further set by the user A until the meeting start time or the meeting end time is reached, thereby automatically implementing Multiple reminders to User B and User C.
  • User A can select a user who wants to be added as a reminder object (ie, a participant) by adding option 75, and the reminder object can be from an associated user of the user A, such as an in-app address book on the WeChat client 1 (such as a WeChat friend, etc.) ), the mobile phone address book in the mobile phone 13, the group member of the group (such as an enterprise) of the user A (such as a company) recorded on the enterprise WeChat client 1, and the user A recorded on the enterprise WeChat client 1
  • the corresponding external contact for example, a group member of an external group associated with the group to which the user A belongs), etc., is not limited by this application.
  • User A can also delete the corresponding reminder object through the delete option 76 corresponding to each added reminder object (such as user B and user C shown in FIG. 7).
  • the user A can select the sending manner of the reminder message for the conference by using the sending mode option 77, for example, the sending manner may include “in-app”, “sms” and “telephone” based on instant messaging technology, and user A may Also select one or more delivery methods.
  • the user A can set whether to activate the reminding function for the currently created meeting reminding message through the reminder option 78, and further set the reminding time point of the reminding function when the reminding function needs to be activated, for example, when the reminding time is When the point is "5 minutes ahead" as shown in Figure 7, the reminder can be reminded 5 minutes before the start time of the meeting to avoid omissions; at the same time, user A can further set the reminder mode, the selection of the reminder mode is similar to
  • the above “sending method” may include one or more reminding methods such as “in-app”, “sms”, “telephone”, and the like.
  • the user A can automatically initiate the option 79 by triggering the conference to determine whether the enterprise WeChat client 1 initiates a call operation to the reminder object.
  • the conference automatic initiation option 79 is enabled, the enterprise WeChat client 1 can automatically start at the conference start time. Initiating a call request for a conference call or a video conference to the reminder object, thereby implementing a conference call or video conference between the user A and the reminder object, or implementing a conference call or video conference between the reminder objects (ie, the user A may not participate in the conference) .
  • User A and the reminder can also join an established conference call or video conference midway.
  • the enterprise WeChat client 1 may initiate a call reservation request to the enterprise WeChat server 1 before the conference start time, so that the enterprise WeChat server 1 sends a reminder to the user A at the conference start time. At least one of the objects initiates a call to establish a conference call or video conference.
  • the enterprise WeChat client 1 sends the conference reminder message to the reminder object through the enterprise WeChat server, the enterprise WeChat server 1 can obtain the conference reminder message and obtain the conference start time therein, and the user is started at the conference start time.
  • At least one of A and the reminder object initiates a call to establish a conference call or video conference without separately transmitting the above-mentioned call reservation request or the like from the above-mentioned enterprise WeChat client 1.
  • the enterprise WeChat server may only initiate a call to the user A to establish a conference call or video conference in which only the user A joins, and the reminder object may join the conference call or video conference midway; or The enterprise WeChat server may only initiate a call to a part of the reminder object to establish a conference call or video conference in which only the part of the reminder object joins, and the user A and other reminder objects may join the conference call or video conference midway; or The enterprise WeChat server can initiate a call to all reminders to establish a conference call or video conference in which all reminders are joined, and user A can join the conference call or video conference midway; or, the enterprise WeChat server can send to user A and All reminders initiate a call to establish a conference call or video conference in which User A and all reminders join.
  • the enterprise WeChat client 1 can determine the conference form, and when the conference form is an online conference such as a conference call or a video conference, the call is automatically implemented between the user A and the reminder object through the above-mentioned call request or call reservation request. Conference or video conference; or, the enterprise WeChat client 1 can show the above-mentioned conference automatic initiation option 79 when the conference form is an online conference such as a conference call or a video conference, and hide the conference automatic initiation option in other conference forms. 79.
  • the user A can also create a conference reminder message by other means. Assume that user A participates in the group chat communication session shown in FIG. 8 in the enterprise WeChat client 1 (the same applies to the single-chat communication session between user A and a single contact), and user A can be in the corresponding communication session page.
  • triggering on any communication message 81 (such as clicking, long pressing, repressing, etc.) enables the enterprise WeChat client 1 to display a function menu 82 for the communication message 81, which includes "DING" Menu options such as "Copy", “Forward”, etc.
  • the enterprise WeChat client 1 can determine that the user A initiates a user creation operation for the reminder message, thereby switching to the message shown in FIG.
  • the type selection page 60 in order to further select the message type of the reminder message to be created by the user A, and create a corresponding meeting reminder message through the new meeting page 70 shown in FIG.
  • the enterprise WeChat client 1 can actively analyze the message content of the communication message 81, or the enterprise WeChat client 1 can initiate an analysis request for the communication message 81 to the enterprise WeChat server, to be used by the enterprise WeChat.
  • the server analyzes the message content of the communication message 81 to determine whether the communication message 81 contains a preset type of activity description information. For example, when the message content of the communication message 81 is "Tomorrow 2-4 pm in Room 201, Building 2, discussing the problem of the X item, and further development requirements", it is assumed that the analysis result includes the activity time information in the message content.
  • the enterprise WeChat client 1 can be in the user.
  • the menu option 820 the corresponding reminder message is automatically determined to be the conference reminder message and transferred to the new conference page 70 shown in FIG. 7, and the user A is not required to manually select the message type through the message type selection page 60 shown in FIG. 6; Further, the enterprise WeChat client 1 can automatically fill in the content of the new conference page 70 according to the analyzed activity description information, so as to simplify the operation of the user A and improve the creation efficiency of the conference reminder message.
  • the enterprise WeChat client 1 running on the mobile phone 14 and the mobile phone 15 can receive the conference reminding message and display it to the user B and the user C.
  • the enterprise WeChat client 3 running on the mobile phone 15 can display all the reminder messages sent and received by the user C through the reminder message management page 90, so that the user C can view the above-mentioned meeting reminder message from the user A.
  • Message content 91 At the same time, for the reminder message of the meeting reminder message or other activity type, in addition to the need for the sender to know whether the receiver has viewed the corresponding meeting reminder message, it is more important to know whether the receiver can participate in the relevant meeting.
  • a response option 92 for the message content 91 described above may also be displayed in the alert message management page 90, including "Accept” and "Reject” as shown in FIG. 9; wherein, when the user C selects the response option 92 When accepting, it indicates that it can participate in the meeting proposed by User A. When User C selects "Reject” in response option 92, it indicates that it cannot participate in the meeting proposed by User A.
  • the enterprise WeChat client 3 may minimize each article.
  • the display area occupied by the reminder message is such that the response option 92 described above may not necessarily be displayed in the reminder message management page 90, and even the message content 91 may not be fully displayed, and only the summary content may be shown. Then, the user C can trigger the message content 91 in the reminder message management page 90, so that the enterprise WeChat client 3 switches to the reminder message detail page 1000 shown in FIG. 10, and displays it in the content display area 1001 of the reminder message detail page 1000.
  • the above message content 91 is displayed, and the reminder message detail page 1000 may further include a function option area 1002.
  • the function option area 1002 may include the above-mentioned response options 92 such as “accept” and “reject”.
  • the corresponding option content may change accordingly. For example, when “reject” is selected, the corresponding response option 92 may be changed from “reject” in FIG. 10 to “already shown in FIG. Reject”; similarly, when “Accept” is selected, “Accept” can be changed to "Accepted”.
  • the alert message detail page 1000 may further include a message dynamic area 1003 corresponding to the conference reminder message, for displaying a dynamic message related to the conference reminder message, such as a sender of the conference reminder message or receiving a policy for the conference reminder message.
  • Reply information etc.
  • the user C can trigger the reply message for the conference reminder message by triggering the “reply” option in the function option area 1002.
  • the information content 1003A of the reply information is "Can start at 13:00?
  • the information content 1003A can be displayed in the dynamic area 1003 described above; similarly, when the mobile phone 15 When receiving the reply message sent by other users, the corresponding information content can also be displayed in the dynamic area 1003 for centralized display to the user C.
  • the reply message sent by a certain user may not be received and viewed by all associated parties (ie, the sender of the conference reminder message and all receivers) of the conference reminder message. For example, user C may select according to the actual situation.
  • One or more of the above-mentioned associated parties are the object of sending the reply information; for example, the enterprise WeChat client 3 can provide a "whisper" option to the user C, when the user C does not select the "whisper” When the option is selected, the above reply message can be sent to all associated parties. When the user C selects the "whisper” option, the above reply message can be sent only to the sender of the conference reminder message - user A, while other users will not Received the reply message.
  • the response status, reply information, and the like of the reminder object to the above-mentioned conference reminder message can be viewed on the mobile phone 13.
  • the reminder message management page 1200 of the enterprise WeChat client 1 running on the mobile phone 13 respectively displays the display area 1201 corresponding to the above-mentioned conference reminding message and the task reminding message for displaying the user AA.
  • the display area 1202 is used to display the display area 1203 of the DING reminder message sent by the user A.
  • the response status 1201A of the 8 reminding objects to the meeting reminding message may be displayed.
  • the response status 1201A may be “5 people have accepted, 1 person has rejected, 2 people have not responded”, wherein “1 person Rejected may correspond to the above-mentioned user C; at the same time, the display area 1201 may also display the reply information 1201B related to the meeting reminding message, for example, the reply information 1201B may include the above-mentioned user C input "can not 13:00 Start? There is an appointment at 16 o'clock.”
  • the mobile phone 15 can also display the dynamic area 1003 and its reply content shown in FIG. 11 in the reminder message management page 90 as shown in FIG. 9 in a manner similar to the embodiment shown in FIG. , will not repeat them here.
  • the response status 1201A may include only summary information similar to "5 people have accepted, 1 person has rejected, 2 people have not responded", and the user A can trigger the response status.
  • the enterprise WeChat client 3 displays the response detail page 1300 shown in FIG. 13A on the mobile phone 15 to view in detail the reminder object corresponding to each response status. For example, as shown in FIG.
  • the response details page 1300 may show all users who select "accept” for the above-mentioned conference reminder message, such as user AA, user BB, User DD, User EE, User FF, etc.; similarly, when User A selects the option 1302 corresponding to "Rejected", the response details page 1300 may show all users who select "Reject” for the above-mentioned meeting reminder message, for example User C above.
  • the response detail page 1300 may indicate a user who has not responded to the conference reminding message described above, such as the user LL, the user KK, and the like;
  • the response details page 1300 may also display a corresponding "re-alert" option 1304 for each "non-responsive" user.
  • the mobile phone 13 may again The conference reminder message described above is sent to the user LL to remind the user LL to respond.
  • the enterprise WeChat client 3 running on the mobile phone 15 can display the reason input window 1003 for the user C to input at least one reason for rejection;
  • the input operation for the reason for rejection may be mandatory, that is, the user C must input at least one reason for rejection, and the enterprise WeChat client 3 can allow the user C to select the "reject” option.
  • At least one predefined rejection reason 1003A may be displayed in the reason input window 1003 for the user C to select by triggering the selection box 1003B corresponding to the predefined rejection reason 1003A, and the user C may also manually input through the input box 1003C.
  • Reason for rejection of course, at least one of the predefined rejection reason 1003A and the input box 1003C may be shown in the reason input window 1003 as long as the reason for rejection can be provided by the user C.
  • the user A can view the reminder object selecting "reject” and the reason for rejection 1502, such as provided by the user C, by selecting the option 1501 corresponding to "rejected" in the response detail page 1500, for example.
  • the reason for refusal 1502 can be "I have a contract at 16:00 and cannot attend the meeting at all times.” Then, after viewing the rejection reason 1502, the user A can make arrangements or adjustments correspondingly, such as advancing or delaying the meeting time according to the needs of the user C.
  • an adjustment request may be made to the corresponding meeting description information to implement the corresponding adjustment.
  • the corresponding adjustment flag 1601 and the adjustment flag 1602 may be respectively displayed on the left side of the meeting time information and the meeting place information.
  • the enterprise WeChat client 3 running on the mobile phone 15 can display the time adjustment option 1603 shown in FIG.
  • the adjustment suggestion may be proposed for the meeting time information; more specifically, the user C may first set the adjusted meeting start time in the reminder message detail page 1600 shown in FIG. 17, and then further set the adjusted after triggering “next step”. At the end of the meeting, the adjusted meeting time information that the user C wishes to adopt is obtained.
  • the mobile phone 15 may initiate an adjustment request to the user A for the adjusted meeting time information; or, the mobile phone 15 may first display the confirmation window 1604 shown in FIG. 18 to the user C, and the user C confirms and initiates the above adjustment to the user A. request.
  • the adjustment flag 1601-1602 can be displayed for the user C to further issue an adjustment request; of course, even if the user C has not selected In the case of "Accept” or "Reject", or if User C has selected "Accept", the above-mentioned adjustment flags 1601-1602 can still be displayed for the user C to further issue an adjustment request.
  • the user A can view the request content 1901 of the adjustment request sent by the user C in the "rejected” sub-page in the response detail page 1900 shown in FIG. 19, such as the request content 1901. It may include “adjustment suggestions: adjust the meeting time to Friday, April 28, 13:00 ⁇ 15:00".
  • the user C selects "Accept”
  • the user A can view the request content of the adjustment request sent by the user C in the "Accepted” sub-page in the response details page 1900
  • User A can view the request content of the adjustment request sent by User C in the "Not Responding" sub-page in the response details page 1900.
  • processing options for the requested content 1901 may be shown, including “agree” and “reject” and the like.
  • the user A selects the "consent” option, it indicates that the user A agrees with the adjustment of the meeting time information suggested by the user C, and the enterprise WeChat client 1 running on the mobile phone 13 can issue the previously issued meeting information according to the adjusted meeting time information.
  • the meeting time information in the meeting reminding message is adjusted, and on the other hand, the corresponding adjusting instruction may be sent to the reminding object of the meeting reminding message, so that the enterprise WeChat client running on the electronic device used by each reminding object responds to the adjusting instruction: Adjusting the meeting time information in the previously received meeting reminding message according to the adjusted meeting time information indicated by the adjustment instruction.
  • the meeting time information can be adjusted from "16:00 to 18:00 on Friday, April 28" to "Friday, April 28, 13". : 00 to 15:00 ”, and “update”, “underline” or the like prompt information 2001 may be displayed in the vicinity of the adjusted conference time information, so that the user A can view it.
  • the mobile phone 14 used by the user B, the user C, and the like, the mobile phone 15, the running enterprise WeChat client 2, and the enterprise WeChat client 3 may also use the above-mentioned adjustment instruction to set the meeting time information from the above “4”. On Friday 28th, from 16:00 to 18:00, it is adjusted to "13:00 to 15:00 on Friday, April 28", and "update", "underline” or “inline” is displayed near the adjusted meeting time information. Similar tips.
  • the enterprise WeChat client 1 running on the mobile phone 13 can also send a new conference reminder message to each reminder object according to the adjusted conference time information, and new The meeting reminder message contains the adjusted meeting time information.
  • new reminder message 2101 received by the mobile phone 15 and the previously received reminder message 2102 may be shown; for the new reminder message 2101
  • the meeting time information may be such as "!!!", "underline” or the like prompt information 2103, so that the user C can more easily pay attention to the adjustment of the meeting time information.
  • a response option 2104 for the reminder message can be shown for user C to select.
  • a management calendar function can be provided.
  • FIG. 22 by showing the management calendar 2200 and showing the related enterprise items on the management calendar 2200, the user can quickly grasp the processing status of the enterprise matters and facilitate the reasonable arrangement of the subsequent work.
  • the management calendar 2200 shown in FIG. 22 by adding event prompt information for the date of the presence of the business item, the user can quickly understand that there is an associated business matter in the corresponding date, for example, on April 4, 2017. A black dot is added at the bottom of "April 5, 2017", “April 12, 2017”, and "April 18, 2017” to indicate the presence of a mission event.
  • the conference reminder message sent by the user A to the user C is equivalent to creating a new enterprise event, the conference event, and then the enterprise WeChat client 1 running on the mobile phone 13 used by the user A.
  • the enterprise WeChat client 3 running on the mobile phone 15 used by the user C a corresponding conference event can be created for the conference reminding message in the corresponding management calendar.
  • a calendar page entry 2105 may be provided in the upper left corner of the reminder message management page 2100 shown in FIG. 21, and when it is detected that the user C triggers the calendar page entry 2105, it may be transferred to the same as shown in FIG. Manage calendar 2200 for user C to view or edit existing business items, or to manually create new business items. As shown in FIG.
  • the business matter existing in the date may be displayed, for example, the display area 2201 in the lower part of the management calendar 2200 may be displayed.
  • the description information of the task event corresponding to the black dot at the bottom of "28"
  • the conference event corresponding to the white dot at the bottom of "28"
  • the description information It 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. 22; 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. 22, and the word “meeting” corresponding to the conference 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.
  • the enterprise WeChat client can support multiple types of reminder messages, such as the "meeting” type, the "task” type, the “DING” type, and the like described above.
  • the reminder message management page 2000 shown in FIG. 20 since the set message type is "all", all types of reminder messages such as “meeting”, “task”, “DING”, etc. can be displayed on the reminder message.
  • Manage page 2000 On the reminder message management page 2300 shown in FIG. 23, by triggering the type modification option 2301, the message type can be set to "meeting", thereby filtering out the "meeting” type reminder message and managing only the reminder message.
  • a reminder message of the "meeting” type is shown in page 2300 for quick viewing.
  • Terminal 3 can also implement a similar reminder message screening display, which will not be described here.
  • the user A sends a meeting reminding message to the user B, the mobile phone 14 used by the user C, and the mobile phone 15 through the enterprise WeChat client 1 running on the mobile phone 13, and the user B and the user C respectively pass the mobile phone 14,
  • the enterprise WeChat client 2 and the enterprise WeChat client 3 running on the mobile phone 15 view corresponding meeting reminding messages, etc., and implement effective reminders for meetings or other activities.
  • the enterprise WeChat client does not only have a mobile terminal, but also includes a PC end, that is, user A can send a meeting reminder message to user B and user C through the enterprise WeChat client running on the PC, and user B and user. C can also receive the meeting reminder message through the enterprise WeChat client running on the PC, and implement other functions in the above embodiments.
  • FIG. 24 shows the operation interface 2400 of the enterprise WeChat client of the PC side used by the user A.
  • the user A can display the "DING" option in the leftmost column of function options, and can be displayed on the operation interface 2400 from the left side.
  • the second column of function options user A further selects all the reminder messages received and sent by user A on the operation interface 2400 by selecting the "all" option in the second column of function options, and when user A further selects a certain
  • the rightmost reminder message detail interface 2402 may be displayed on the operation interface 2400, and the reminder message detail interface 2402 is used to display the message content of the reminder message 2401.
  • a new identification 2403 may be provided on the operation interface 2400.
  • a message type selection page 2500 as shown in FIG. 25 may be displayed; wherein, when the user A selects the "meeting" type, the user may further display The new conference page 2600 shown in FIG. 26 is created, thereby creating a reminder message of the conference type.
  • the above process is similar to the process in which the user A creates a conference reminder message through the mobile phone 13 as shown in FIG. 5-7, and details are not described herein again.
  • the user A can also create a conference reminder message by triggering the communication message on the operation interface 2400 of the PC, and details are not described herein again.
  • 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 an activity reminder 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 activity reminding device may include:
  • the receiving unit 2801 is configured to enable the client to receive an alert message generating instruction for the activity type
  • the determining unit 2802 is configured to enable the client to determine the event description information corresponding to the reminder object and the activity type;
  • the sending unit 2803 is configured to enable the client to send an alert message to the reminder object, where the alert message includes the activity description information.
  • the receiving unit 2801 is specifically configured to:
  • the client is determined to receive the reminder message generation instruction.
  • the receiving unit 2801 is specifically configured to:
  • the client When the client includes the preset type of activity description information in the message content of the communication message, it is determined that the reminder message generation instruction is received.
  • the determining unit 2802 is specifically configured to:
  • the activity description information includes at least one of the following:
  • Event topic information event location information, event form information, event time information.
  • the sending unit 2803 is specifically configured to:
  • the client is caused to send the reminder message according to a default message type or a message type set by the user at a default sending time or a sending time set by the user.
  • it also includes:
  • the response receiving unit 2804 is configured to enable the client to receive a response message returned by the reminder object, where the response message includes acceptance status information of the reminder object for the activity description information;
  • the displaying unit 2805 is configured to enable the client to display the reminder object in association with the corresponding response message.
  • the response message further includes: a reason for rejection.
  • it also includes:
  • the adding unit 2806 is configured to enable the client to add a corresponding event event in the management calendar in the communication application according to the activity description information.
  • it also includes:
  • the request receiving unit 2807 is configured to enable the client to receive an adjustment request that is raised by the reminding object for at least one item of the activity description information
  • the adjusting unit 2808 when the client receives the user confirmation operation for the adjustment request, sends an adjustment instruction for the reminder message to the reminder object based on the adjusted activity description information, or based on the adjusted The activity description information sends a new reminder message to the reminder object.
  • it also includes:
  • the client resending the reminder message to the reminder object when the response message returned by the reminder object is not received within a preset duration after the reminder message is sent, or displaying the reminder message Repetitive reminder options for the reminder object to resend the reminder message to the reminder object upon receiving a trigger action for the user of the repeat reminder option.
  • the reminder message includes a default or user-set reminding time point, a default or a user-set reminding manner, so that the reminding object is reminded to be active based on the reminding manner at the reminding time point.
  • the reminder content is related to the activity description information.
  • it also includes:
  • the call requesting unit 2810 causes the client to initiate a call request for the reminder object at the activity start time according to the activity start time included in the activity description information to establish an audio connection or a video connection.
  • it also includes:
  • the call reservation unit 2811 causes the client to initiate a call reservation request to the server according to the activity start time included in the activity description information, where the call reservation request is used to indicate that the server is at the start time of the activity. At least one of the client and the reminder object initiates a call to establish an audio connection or a video connection.
  • the sending unit 2803 is specifically configured to:
  • the reminder message is used to instruct the server to initiate a call to at least one of the client and the reminder object according to an activity start time included in the activity description information, to Establish an audio connection or video connection.
  • the activity description information includes activity form information, where the activity form information indicates that the corresponding activity is a conference call or a video conference.
  • the activity reminding device may include:
  • the first receiving unit 2901 is configured to enable the client to receive an alert message of an activity type
  • the displaying unit 2902 is configured to enable the client to display the activity description information included in the reminder message;
  • the client is configured to return a corresponding response message to the sender of the reminder message according to the received user triggering operation for the activity description information, where the response message includes the user triggering an operation indication Acceptance status information for the activity description information.
  • the returning unit 2903 is specifically configured to:
  • the client When the acceptance status information of the user triggering operation indication is consent, the client is directly returned to the response message;
  • the client When the acceptance status information of the user trigger operation indication is a rejection, the client is further acquired with a corresponding rejection reason, and the rejection reason is added to the response message to return to the sender.
  • it also includes:
  • the adding unit 2904 when the accepting status information of the user triggering operation indication is consent, causes the client to add a corresponding activity event in the management calendar in the communication application according to the activity description information.
  • it also includes:
  • the sending unit 2905 when the accepting status information of the user triggering operation indication is a rejection, causing the client to further acquire adjustment information for at least one item of the activity description information, and send the Adjust the adjustment request for information;
  • the second receiving unit 2906 the client is configured to receive a new reminder message returned by the sender, where the new reminder message includes activity description information adjusted based on the adjustment request; or Receiving, by the terminal, an adjustment instruction returned by the sender based on the adjusted activity description information, and adjusting activity description information in the reminder message according to the adjustment instruction.
  • it also includes:
  • the obtaining unit 2907 is configured to enable the client to obtain a reminder time point and a reminding manner included in the reminder message;
  • the requesting unit 2908 is configured to enable the client to initiate an activity reminding request corresponding to the reminding time point and the reminding mode to the server;
  • the response unit 2909 is configured to enable the client to respond to an activity reminding event initiated by the server in the reminding manner at the reminding time point.
  • the activity reminding device may include:
  • the generating unit 3001 is configured to enable the client to generate a reminder message according to the activity description information and the reminder object;
  • the sending unit 3002 causes the client to send an alert message to the reminder object, where the alert message includes the activity description information.
  • the generating unit 3001 is specifically configured to:
  • the client When the type information selected by the user selection operation is an activity type, the client is caused to generate a reminder message according to the activity type.
  • the generating unit 3001 is specifically configured to:
  • FIG. 31 shows a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application.
  • the electronic device includes a processor 3102, an internal bus 3104, a network interface 3106, a memory 3108, and a non-volatile memory 3110.
  • the processor 3102 reads the corresponding computer program from the non-volatile memory 3110 into the memory 3108 and then operates to form an activity reminder message generating 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 activity reminding message generating apparatus may include:
  • the receiving unit 3201 is configured to enable the client to receive an alert message generating instruction
  • the displaying unit 3202 is configured to enable the client to display an alternative message type of the reminder message
  • the implementing unit 3203 is configured to enable the client to generate a corresponding message according to the selected message type.
  • the candidate message type includes at least one of the following:
  • 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 to describe various information in this application, such 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

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (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)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)
  • Debugging And Monitoring (AREA)
  • Electrotherapy Devices (AREA)

Abstract

本申请提供一种活动提醒方法、活动提醒消息生成方法及装置，该方法可以包括：客户端接收针对活动类型的提醒消息生成指令；所述客户端确定提醒对象和所述活动类型对应的活动描述信息；所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。通过本申请的技术方案，可以快捷实现活动提醒。

Description

活动提醒方法、活动提醒消息生成方法及装置
本申请要求2017年06月06日递交的申请号为201710417733.9、发明名称为“活动提醒方法、活动提醒消息生成方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通讯技术领域，尤其涉及一种活动提醒方法、活动提醒消息生成方法及装置。
背景技术
在相关技术中，移动化企业办公平台被越来越广泛地应用于企业、教育机构、政府机关等各类团体的办公过程，不仅能够提升用户之间的沟通效率、降低沟通成本，而且能够有效提升用户的事件处理效率和办公效率。
举例而言，移动化企业办公平台可以用于发送提醒消息，该提醒消息可以基于移动化企业办公平台提供的即时通讯功能而发送，也可以基于短信、电话等传统的移动通讯方式而发送，以确保提醒效果。
但是，相关技术中的提醒消息被应用于所有场景，导致一些对于时限性等要求较高的重要事件，无法被有效突出；尤其是，当用户接收到的提醒消息较多、甚至被滥用时，很容易导致上述重要事件被忽视，造成提醒消息的提醒作用受限。
发明内容
有鉴于此，本申请提供一种活动提醒方法、活动提醒消息生成方法及装置，可以快捷实现活动提醒。
为实现上述目的，本申请提供技术方案如下：
根据本申请的第一方面，提出了一种活动提醒方法，包括：
客户端接收针对活动类型的提醒消息生成指令；
所述客户端确定提醒对象和所述活动类型对应的活动描述信息；
所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
根据本申请的第二方面，提出了一种活动提醒方法，包括：
客户端接收活动类型的提醒消息；
所述客户端展示所述提醒消息包含的活动描述信息；
所述客户端根据收到的针对所述活动描述信息的用户触发操作，向所述提醒消息的发送方返回相应的响应消息，所述响应消息包括所述用户触发操作指示的针对所述活动描述信息的接受状况信息。
根据本申请的第三方面，提出了一种活动提醒消息生成方法，包括：
客户端接收提醒消息生成指令；
所述客户端展示出所述提醒消息的备选消息类型；
所述客户端根据选中的消息类型，生成相应的消息。
根据本申请的第四方面，提出了一种活动提醒装置，包括：
接收单元，使客户端接收针对活动类型的提醒消息生成指令；
确定单元，使所述客户端确定提醒对象和所述活动类型对应的活动描述信息；
发送单元，使所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
根据本申请的第五方面，提出了一种活动提醒装置，包括：
第一接收单元，使客户端接收活动类型的提醒消息；
展示单元，使所述客户端展示所述提醒消息包含的活动描述信息；
返回单元，使所述客户端根据收到的针对所述活动描述信息的用户触发操作，向所述提醒消息的发送方返回相应的响应消息，所述响应消息包括所述用户触发操作指示的针对所述活动描述信息的接受状况信息。
根据本申请的第六方面，提出了一种活动提醒消息生成装置，包括：
接收单元，使客户端接收提醒消息生成指令；
展示单元，使所述客户端展示出所述提醒消息的备选消息类型；
实施单元，使所述客户端根据选中的消息类型，生成相应的消息。
根据本申请的第七方面，提出了一种活动提醒方法，包括：
客户端根据活动描述信息和提醒对象生成提醒消息；
所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
根据本申请的第八方面，提出了一种活动提醒装置，包括：
生成单元，使客户端根据活动描述信息和提醒对象生成提醒消息；
发送单元，使所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
由以上技术方案可见，本申请通过提供活动类型的提醒消息，可以针对在时限性等方面具有较高要求的活动事件而单独发出提醒消息，并且能够有效地区别于其他类型的提醒消息，从而即便在用户接收到较多数量的提醒消息时，仍然能够基于消息类型而快速区分、识别出上述的活动事件，避免发生遗漏。
附图说明
图1是本申请一示例性实施例提供的一种活动提醒系统的架构示意图；
图2A是本申请一示例性实施例提供的一种基于发送方侧的活动提醒方法的流程图；
图2B是本申请一示例性实施例提供的另一种基于发送方侧的活动提醒方法的流程图；
图3是本申请一示例性实施例提供的一种基于接收方侧的活动提醒方法的流程图；
图4提出了本申请一示例性实施例提供的一种活动提醒消息生成方法的流程图；
图5提出了本申请一示例性实施例提供的一种发送方侧的提醒消息管理页面的示意图；
图6提出了本申请一示例性实施例提供的一种发送方侧的消息类型选择页面的示意图；
图7提出了本申请一示例性实施例提供的一种发送方侧的新建会议页面的示意图；
图8提出了本申请一示例性实施例提供的一种发送方侧的将通讯消息转换为提醒消息的示意图；
图9提出了本申请一示例性实施例提供的一种接收方侧的提醒消息管理页面的示意图；
图10提出了本申请一示例性实施例提供的一种接收方侧的提醒消息详情页面的示意图；
图11提出了本申请一示例性实施例提供的另一种接收方侧的提醒消息详情页面的示意图；
图12提出了本申请一示例性实施例提供的另一种发送方侧的提醒消息管理页面的示意图；
图13A提出了本申请一示例性实施例提供的一种发送方侧的响应详情页面的示意图；
图13B提出了本申请一示例性实施例提供的另一种发送方侧的响应详情页面的示意 图；
图14提出了本申请一示例性实施例提供的一种接收方侧的理由输入窗口的示意图；
图15提出了本申请一示例性实施例提供的又一种发送方侧的响应详情页面的示意图；
图16提出了本申请一示例性实施例提供的一种接收方侧的通过提醒消息详情页面发起调整请求的一种示意图；
图17提出了本申请一示例性实施例提供的一种接收方侧的通过提醒消息详情页面发起调整请求的另一示意图；
图18提出了本申请一示例性实施例提供的一种接收方侧的通过提醒消息详情页面发起调整请求的另一示意图；
图19提出了本申请一示例性实施例提供的一种发送方侧的通过响应详情页面处理调整请求的示意图；
图20提出了本申请一示例性实施例提供的一种发送方侧的对调整后的会议描述信息进行提示的示意图；
图21提出了本申请一示例性实施例提供的一种接收方侧的对新的会议提醒消息中调整后的会议描述信息进行提示的示意图；
图22提出了本申请一示例性实施例提供的一种管理日历的页面示意图；
图23提出了本申请一示例性实施例提供的一种对提醒消息管理页面中的提醒消息进行分类筛选展示的示意图；
图24提出了本申请一示例性实施例提供的一种在PC端创建会议提醒消息的一种示意图；
图25提出了本申请一示例性实施例提供的一种在PC端创建会议提醒消息的另一示意图；
图26提出了本申请一示例性实施例提供的一种在PC端创建会议提醒消息的又一示意图；
图27是本申请一示例性实施例提供的一种电子设备的结构示意图；
图28是本申请一示例性实施例提供的一种基于发送方侧的活动提醒装置的框图；
图29是本申请一示例性实施例提供的一种基于接收方侧的活动提醒装置的框图；
图30是本申请一示例性实施例提供的另一种基于发送方侧的活动提醒装置的框图；
图31是本申请一示例性实施例提供的另一种电子设备的结构示意图；
图32是本申请一示例性实施例提供的一种活动提醒消息生成装置的框图。
具体实施方式
图1是本申请一示例性实施例提供的一种活动提醒系统的架构示意图。如图1所示，该系统可以包括服务器11、网络12、若干电子设备，比如手机13、手机14、手机15和手机16等。
服务器11可以为包含一独立主机的物理服务器，或者该服务器11可以为主机集群承载的虚拟服务器，或者该服务器11可以为云服务器。在运行过程中，服务器11可以运行某一应用的服务器侧的程序，以实现该应用的相关业务功能，比如当该服务器11运行移动化团体办公平台的程序时，可以实现为该移动化团体办公平台的服务端。而在本申请的技术方案中，可由服务器11通过与手机13-16上运行的客户端进行配合，以实现活动提醒方案。
其中，移动化企业办公平台不仅可以实现通讯功能，还可以作为诸多其他功能的集成化功能平台，比如对于审批事件(如请假、办公物品申领、财务等审批事件)、考勤事件、任务事件、日志事件等企业内部事件的处理，再比如订餐、采购等企业外部事件的处理，本申请并不对此进行限制。较为具体地，移动化企业办公平台可以承载于相关技术中的即时通讯应用，比如企业即时通讯(Enterprise Instant Messaging，EIM)应用，例如Skype For
Figure PCTCN2018088652-appb-000001
Microsoft
Figure PCTCN2018088652-appb-000002
Figure PCTCN2018088652-appb-000003
Figure PCTCN2018088652-appb-000004
等。当然，即时通讯功能仅为移动化企业办公平台支持的通讯功能之一，该企业办公平台还能够实现更多诸如上述的其他功能，以及本申请中所需实现的活动提醒功能等，此处不再赘述。
手机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的通讯过程，此处不再一一赘述。
可见，在本申请的技术方案的实施过程中，涉及到活动类型的提醒消息的发送方与接收方之间的交互过程；下面分别从双方的处理逻辑和交互过程，对本申请的技术方案进行描述。
图2A是本申请一示例性实施例提供的一种基于发送方侧的活动提醒方法的流程图。如图2A所示，该方法应用于发送方使用的电子设备上，可以包括以下步骤：
步骤202A，移动化企业办公平台的客户端获取针对活动类型的提醒消息生成指令。
在本实施例中，移动化企业办公平台可以提供多种生成提醒消息的途径，因而存在多种方式来获取上述的针对活动类型的提醒消息的消息生成指令，本申请并不对此进行限制；实际上，任何适用于相关技术中的提醒消息的生成方式，均可以适用于本申请中以生成活动类型的提醒消息。
在一实施方式中，客户端可以接收针对提醒消息的用户创建操作，以及针对所述提醒消息的类型信息的用户选择操作，并当所述用户选择操作选取的类型信息为活动类型时，所述客户端确定获取到所述消息生成指令。比如，客户端可以首先向用户(在本实施例中，即发送方)提供针对提醒消息的创建选项，当用户通过用户创建操作触发该创建选项时，客户端可以进一步向用户提供提醒消息的备选消息类型，以供用户通过用户选择操作选取所需创建的提醒消息的类型信息；或者，客户端可以直接向用户提供分别对应于每一类型的提醒消息的创建选项，而用户在触发活动类型的提醒消息对应的创建 选项时，即可同时完成上述的用户创建操作和用户选择操作，以创建活动类型的提醒消息。
在另一实施方式中，客户端可以接收针对移动化企业办公平台内的通讯消息的用户触发操作，所述用户触发操作用于指示所述客户端将所述通讯消息转换为提醒消息；然后，客户端在识别出所述通讯消息的消息内容中包含预设类型的活动描述信息时，确定获取到所述消息生成指令。其中，上述的通讯消息可以包括客户端内的任意通讯会话页面内的已接收消息或已发送消息，当用户针对该即时通讯消息实施点击、长按、重压等预设操作时，可以唤出针对该通讯消息的若干处理选项，比如复制、删除、转发、转换等，其中用户可以通过选取“转换”处理选项以完成上述的用户触发操作，使得客户端提取该通讯消息的消息内容并生成相应的提醒消息。在生成提醒消息的过程中，客户端可以根据对该通讯消息的消息内容的识别结果，在该消息内容中包含预设类型的活动描述信息的情况下，将上述通讯消息的消息内容生成为活动类型的提醒消息。
其中，客户端可以通过多种方式获取上述的识别结果。在一种情况下，客户端可以主动识别通讯消息的消息内容，并生成相应的识别结果；在另一种情况下，客户端可以向服务端发起识别请求，并接收服务端返回的针对该通讯消息的消息内容的识别结果；在又一种情况下，客户端可以向用户展示提供消息的备选消息类型，并根据用户的选择结果而确定相应的识别结果，比如当用户选择了活动类型时，客户端可以确定识别结果为包含预设类型的活动描述信息。
进一步地，当被触发的通讯消息的消息内容中包含预设类型的活动描述信息时，客户端可以将该活动描述信息添加至所需生成的活动类型的提醒消息中，还可以将该通讯消息的关联通讯方添加为提醒对象。例如，假定被触发的通讯消息为“明天下午2-4点在2号楼201室讨论X项目……”，客户端可以确定的活动描述信息包括：活动时间信息为“明天下午2-4点”(可以转换为具体的年月日形式)、活动地点信息为“2号楼201室”、活动主题信息为“讨论X项目……”等，同时该通讯消息的关联通讯方可以包括相应的发送方和接收方等。
在本实施例中，活动类型的提醒消息用于实现针对活动的提醒功能；其中，活动可以理解为由多人参与并完成一定的动作，以期达到相应的目的，比如本申请中的活动可以包括：会议、聚餐、出游、讨论等，本申请并不对此进行限制。
步骤204A，所述客户端确定提醒对象和所述活动类型对应的活动描述信息。
在本实施例中，活动描述信息可以包括以下至少之一：活动主题信息、活动地点信 息、活动形式信息(比如线下会议、线上会议等，再比如视频会议、电话会议等)、活动时间信息(比如活动开始时刻、活动结束时刻；或者，比如活动开始时刻和活动时长；或者，比如仅包含活动开始时刻；或者其他情况)。活动描述信息中可能同时包含一个或多个活动主题，也可能同时包含一个或多个活动地点，可以分别指出每一活动主题对应的活动地点和活动时间信息，以更加明确活动情况。
步骤206A，所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
在本实施例中，客户端可以在默认发送时刻或者用户设定的发送时刻、按照默认消息类型或者用户设定的消息类型发送所述提醒消息。其中，用户通过设定发送时刻，可以实现对活动类型的提醒消息的定时发送，该发送时刻可以为尚未发生的任意时刻，比如用户可以直接设定为诸如“今天15时25分”等绝对时刻，也可以设定为诸如“活动开始时刻之前30分钟”等相对时刻，或者其他任意形式的时刻。同时，用户可以通过设置消息类型，以实现不同程度的提醒作用，例如消息类型可以包括“应用内”的即时通讯消息、短信、电话(例如语音播报消息内容等)等，用户可以仅选取一种消息类型、使得客户端仅通过单一形式发送提醒消息，或者也可以选取多种消息类型、使得客户端同时通过多种形式发送提醒消息。
在本实施例中，作为接收方的提醒对象可以针对发送方发出的提醒消息进行响应，则客户端可以接收所述提醒对象返回的响应消息，所述响应消息包含所述提醒对象针对所述活动描述信息的接受状况信息；然后，所述客户端可以将所述提醒对象与对应的响应消息进行关联展示，以便于发送方进行查看。其中，接受状况信息表明接收方是否认同上述活动类型的提醒消息中包含的活动描述信息；例如，当接受状况信息为“同意”时，表明其可以接受活动描述信息定义的“活动主题”、“活动地点”、“活动时间”等，从而具有较大概率参与相关活动；而当接受状况信息为“拒绝”时，表明其可能无法接受至少一部分活动描述信息，从而具有较大概率无法参与相关活动。
其中，当所述接受状况信息为拒绝时，所述响应消息还包括：拒绝理由，比如接收方可以明确是由于“距离活动地点过远”、“活动时间过早”等原因，导致其无法参与相关活动，有助于发送方据此对活动进行及时调整，以便于提升提醒对象参与活动的概率。上述的“拒绝理由”可以为选填项；或者，也可以为接收方在选取“拒绝”时的必填项，以确保发送方能够据此实现对活动进行调整，并进而提升提醒对象参与活动的概率。
在本实施例中，客户端可以根据所述活动描述信息，在所述移动化企业办公平台中的管理日历中添加相应的活动事件，以便于提升对该活动事件的管理效率和便捷性。其中，管理日历中可能包含多种类型的管理事件，那么针对上述的活动事件以及其他管理事件，可以在管理日历中采用不同的展示属性，以便于发送方在查看过程中实现快速识别和区分。
在本实施例中，客户端可以接收所述提醒对象针对所述活动描述信息中的至少一个项目提出的调整请求，以及所述客户端在收到针对所述调整请求的用户确认操作时，可以基于调整后的活动描述信息向所述提醒对象发送新的提醒消息；或者，可以基于调整后的活动描述信息向所述提醒对象发送针对所述提醒消息的调整指令，使得提醒对象使用的客户端可以根据该调整指令对先前接收到的提醒消息中的活动描述信息进行调整。
在本实施例中，客户端在发出提醒消息后的预设时长内未接收到所述提醒对象返回的响应消息时，可以自动向所述提醒对象重新发送所述提醒消息，以提升提醒成功率；或者，客户端可以展示针对所述提醒对象的重复提醒选项，使得用户可以根据实际情况确定是否需要重复提醒，并在确定需要重复提醒时对重复提醒选项实施用户触发操作，以使得客户端在收到针对所述重复提醒选项的用户触发操作时向所述提醒对象重新发送所述提醒消息。
在本实施例中，所述提醒消息中可以包含默认或用户设定的提醒时间点、默认或用户设定的提醒方式，以使所述提醒对象在所述提醒时间点被基于所述提醒方式进行活动提醒，且提醒内容与所述活动描述信息相关。其中，提醒时间点可以为活动开始时刻或者活动开始时刻之前的任意时刻，比如活动开始前5分钟、活动开始前半小时等。提醒方式可以包括“应用内”的即时通讯消息、短信、电话等，可以仅采用一种提醒方式、使得提醒对象仅获得单一形式的活动提醒，或者也可以采用多种提醒方式、使得提醒对象同时获得多种形式的活动提醒。
在本实施例中，所述客户端还可以根据所述活动描述信息包含的活动开始时刻，在所述活动开始时刻发起针对所述提醒对象的呼叫请求，以建立音频连接或视频连接；其中，该呼叫请求可以用于使得客户端与提醒对象之间建立起音频连接或视频连接，或者该呼叫请求可以用于使得提醒对象之间建立起音频连接或视频连接等。此外，对于已经建立的音频连接或视频连接，尚未加入的客户端或提醒对象还可以通过其他途径进行中途加入。通过由客户端自动发起该呼叫请求，一方面无需发送方手动通过客户端执行呼叫操作，另一方面即便发送方忘记操作或由于其他事务而未注意到活动开始时刻已到达， 也可以确保活动准时开始、避免发生延误。实际上，当发送方忘记操作或由于其他事务而未注意到活动开始时刻已到达时，通过由客户端自动发起呼叫请求，还可以对发送方起到提醒作用，确保活动的顺利进行。
当然，除了由客户端发起呼叫请求之外，还可以存在其他实施方式。例如，所述客户端可以根据所述活动描述信息包含的活动开始时刻，向服务端发起呼叫预约请求，客户端可以在活动开始时刻到达之前的任意时刻发起该呼叫预约请求；其中，所述呼叫预约请求用于指示所述服务端在所述活动开始时刻向所述客户端和所述提醒对象中至少之一发起呼叫，以建立音频连接或视频连接。再例如，当客户端通过服务端将提醒消息发送至提醒对象时，由于服务端可以获得该提醒消息并获取其中的活动描述信息，那么服务端可以根据该活动描述信息包含的活动开始时刻，在所述活动开始时刻向所述客户端和所述提醒对象中至少之一发起呼叫，以建立音频连接或视频连接，而无需客户端单独发送上述的呼叫预约请求或类似消息。对于上述由服务端发起呼叫的方案，服务端可以仅向所述客户端发起呼叫，使得客户端响应于该呼叫而建立相应的音频连接或视频连接，而提醒对象可以通过其他途径加入该音频连接或视频连接；或者，服务端可以仅向提醒对象发起呼叫，使得提醒对象响应于该呼叫而建立相应的音频连接或视频连接，其中服务端可以同时向所有提醒对象发起呼叫，也可以仅向部分提醒对象发起呼叫、而其他提醒对象可以通过其他途径加入已建立的音频连接或视频连接，当然客户端也可以通过其他途径加入已建立的音频连接或视频连接；或者，服务端可以向客户端和提醒对象发起呼叫，使得在客户端与提醒对象之间建立起音频连接或视频连接。
在本实施例中，客户端可以获取活动描述信息包含的活动形式信息，该活动形式信息用于表明相应的活动为电话会议、视频会议等线上活动，或者聚餐、出游等线下活动。那么，客户端可以在确定活动形式信息为电话会议或视频会议等线上活动时，发起上述的呼叫请求或者呼叫预约请求，以使得发送方与提醒对象之间通过相应的音频连接或视频连接实现该线上活动。
图2B是本申请一示例性实施例提供的另一种基于发送方侧的活动提醒方法的流程图。如图2B所示，该方法应用于发送方使用的电子设备上，可以包括以下步骤：
步骤202B，移动化企业办公平台的客户端根据活动描述信息和提醒对象生成提醒消息。
在本实施例中，移动化企业办公平台可以提供多种生成提醒消息的途径，因而存在多种方式来获取上述的针对活动类型的提醒消息的消息生成指令，本申请并不对此进行 限制；实际上，任何适用于相关技术中的提醒消息的生成方式，均可以适用于本申请中以生成活动类型的提醒消息。
在一实施例中，所述客户端收到针对所述提醒消息的用户创建操作，以及针对所述提醒消息的类型信息的用户选择操作；当所述用户选择操作选取的类型信息为活动类型时，所述客户端根据所述活动类型生成提醒消息。比如，客户端可以首先向用户(在本实施例中，即发送方)提供针对提醒消息的创建选项，当用户通过用户创建操作触发该创建选项时，客户端可以进一步向用户提供提醒消息的备选消息类型，以供用户通过用户选择操作选取所需创建的提醒消息的类型信息；或者，客户端可以直接向用户提供分别对应于每一类型的提醒消息的创建选项，而用户在触发活动类型的提醒消息对应的创建选项时，即可同时完成上述的用户创建操作和用户选择操作，以创建活动类型的提醒消息。
在另一实施例中，所述客户端收到针对通讯消息的用户触发操作，所述用户触发操作用于指示所述客户端将所述通讯消息转换为提醒消息；所述客户端在识别出所述通讯消息的消息内容中包含预设类型的活动描述信息时，生成所述提醒消息。其中，上述的通讯消息可以包括客户端内的任意通讯会话页面内的已接收消息或已发送消息，当用户针对该通讯消息实施点击、长按、重压等预设操作时，可以唤出针对该通讯消息的若干处理选项，比如复制、删除、转发、转换等，其中用户可以通过选取“转换”处理选项以完成上述的用户触发操作，使得客户端提取该通讯消息的消息内容并生成相应的提醒消息。在生成提醒消息的过程中，客户端可以根据对该通讯消息的消息内容的识别结果，在该消息内容中包含预设类型的活动描述信息的情况下，将上述通讯消息的消息内容生成为活动类型的提醒消息。上述的通讯消息可以包括文字消息，也可以包括语音消息、图片消息、视频消息等其他消息类型，本申请并不对此进行限制。
其中，客户端可以通过多种方式获取上述的识别结果。在一种情况下，客户端可以主动识别通讯消息的消息内容，并生成相应的识别结果；在另一种情况下，客户端可以向服务端发起识别请求，并接收服务端返回的针对该通讯消息的消息内容的识别结果；在又一种情况下，客户端可以向用户展示提供消息的备选消息类型，并根据用户的选择结果而确定相应的识别结果，比如当用户选择了活动类型时，客户端可以确定识别结果为包含预设类型的活动描述信息。
进一步地，当被触发的通讯消息的消息内容中包含预设类型的活动描述信息时，客户端可以将该活动描述信息添加至所需生成的活动类型的提醒消息中，还可以将该通讯 消息的关联通讯方添加为提醒对象。例如，假定被触发的通讯消息为“明天下午2-4点在2号楼201室讨论X项目……”，客户端可以确定的活动描述信息包括：活动时间信息为“明天下午2-4点”(可以转换为具体的年月日形式)、活动地点信息为“2号楼201室”、活动主题信息为“讨论X项目……”等，同时该通讯消息的关联通讯方可以包括相应的发送方和接收方等。
在本实施例中，活动类型的提醒消息用于实现针对活动的提醒功能；其中，活动可以理解为由多人参与并完成一定的动作，以期达到相应的目的，比如本申请中的活动可以包括：会议、聚餐、出游、讨论等，本申请并不对此进行限制。
在本实施例中，活动描述信息可以包括以下至少之一：活动主题信息、活动地点信息、活动形式信息(比如线下会议、线上会议等，再比如视频会议、电话会议等)、活动时间信息(比如活动开始时刻、活动结束时刻；或者，比如活动开始时刻和活动时长；或者，比如仅包含活动开始时刻；或者其他情况)。活动描述信息中可能同时包含一个或多个活动主题，也可能同时包含一个或多个活动地点，可以分别指出每一活动主题对应的活动地点和活动时间信息，以更加明确活动情况。
步骤204B，所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
在本实施例中，客户端可以在默认发送时刻或者用户设定的发送时刻、按照默认消息类型或者用户设定的消息类型发送所述提醒消息。其中，用户通过设定发送时刻，可以实现对活动类型的提醒消息的定时发送，该发送时刻可以为尚未发生的任意时刻，比如用户可以直接设定为诸如“今天15时25分”等绝对时刻，也可以设定为诸如“活动开始时刻之前30分钟”等相对时刻，或者其他任意形式的时刻。同时，用户可以通过设置消息类型，以实现不同程度的提醒作用，例如消息类型可以包括“应用内”的即时通讯消息、短信、电话(例如语音播报消息内容等)等，用户可以仅选取一种消息类型、使得客户端仅通过单一形式发送提醒消息，或者也可以选取多种消息类型、使得客户端同时通过多种形式发送提醒消息。
在本实施例中，作为接收方的提醒对象可以针对发送方发出的提醒消息进行响应，则客户端可以接收所述提醒对象返回的响应消息，所述响应消息包含所述提醒对象针对所述活动描述信息的接受状况信息；然后，所述客户端可以将所述提醒对象与对应的响应消息进行关联展示，以便于发送方进行查看。其中，接受状况信息表明接收方是否认同上述活动类型的提醒消息中包含的活动描述信息；例如，当接受状况信息为“同意” 时，表明其可以接受活动描述信息定义的“活动主题”、“活动地点”、“活动时间”等，从而具有较大概率参与相关活动；而当接受状况信息为“拒绝”时，表明其可能无法接受至少一部分活动描述信息，从而具有较大概率无法参与相关活动。
其中，当所述接受状况信息为拒绝时，所述响应消息还包括：拒绝理由，比如接收方可以明确是由于“距离活动地点过远”、“活动时间过早”等原因，导致其无法参与相关活动，有助于发送方据此对活动进行及时调整，以便于提升提醒对象参与活动的概率。上述的“拒绝理由”可以为选填项；或者，也可以为接收方在选取“拒绝”时的必填项，以确保发送方能够据此实现对活动进行调整，并进而提升提醒对象参与活动的概率。
在本实施例中，客户端可以根据所述活动描述信息，在所述移动化企业办公平台中的管理日历中添加相应的活动事件，以便于提升对该活动事件的管理效率和便捷性。其中，管理日历中可能包含多种类型的管理事件，那么针对上述的活动事件以及其他管理事件，可以在管理日历中采用不同的展示属性，以便于发送方在查看过程中实现快速识别和区分。
在本实施例中，客户端可以接收所述提醒对象针对所述活动描述信息中的至少一个项目提出的调整请求，以及所述客户端在收到针对所述调整请求的用户确认操作时，可以基于调整后的活动描述信息向所述提醒对象发送新的提醒消息；或者，可以基于调整后的活动描述信息向所述提醒对象发送针对所述提醒消息的调整指令，使得提醒对象使用的客户端可以根据该调整指令对先前接收到的提醒消息中的活动描述信息进行调整。
在本实施例中，客户端在发出提醒消息后的预设时长内未接收到所述提醒对象返回的响应消息时，可以自动向所述提醒对象重新发送所述提醒消息，以提升提醒成功率；或者，客户端可以展示针对所述提醒对象的重复提醒选项，使得用户可以根据实际情况确定是否需要重复提醒，并在确定需要重复提醒时对重复提醒选项实施用户触发操作，以使得客户端在收到针对所述重复提醒选项的用户触发操作时向所述提醒对象重新发送所述提醒消息。
在本实施例中，所述提醒消息中可以包含默认或用户设定的提醒时间点、默认或用户设定的提醒方式，以使所述提醒对象在所述提醒时间点被基于所述提醒方式进行活动提醒，且提醒内容与所述活动描述信息相关。其中，提醒时间点可以为活动开始时刻或者活动开始时刻之前的任意时刻，比如活动开始前5分钟、活动开始前半小时等。提醒方式可以包括“应用内”的即时通讯消息、短信、电话等，可以仅采用一种提醒方式、 使得提醒对象仅获得单一形式的活动提醒，或者也可以采用多种提醒方式、使得提醒对象同时获得多种形式的活动提醒。
在本实施例中，所述客户端还可以根据所述活动描述信息包含的活动开始时刻，在所述活动开始时刻发起针对所述提醒对象的呼叫请求，以建立音频连接或视频连接；其中，该呼叫请求可以用于使得客户端与提醒对象之间建立起音频连接或视频连接，或者该呼叫请求可以用于使得提醒对象之间建立起音频连接或视频连接等。此外，对于已经建立的音频连接或视频连接，尚未加入的客户端或提醒对象还可以通过其他途径进行中途加入。通过由客户端自动发起该呼叫请求，一方面无需发送方手动通过客户端执行呼叫操作，另一方面即便发送方忘记操作或由于其他事务而未注意到活动开始时刻已到达，也可以确保活动准时开始、避免发生延误。实际上，当发送方忘记操作或由于其他事务而未注意到活动开始时刻已到达时，通过由客户端自动发起呼叫请求，还可以对发送方起到提醒作用，确保活动的顺利进行。
当然，除了由客户端发起呼叫请求之外，还可以存在其他实施方式。例如，所述客户端可以根据所述活动描述信息包含的活动开始时刻，向服务端发起呼叫预约请求，客户端可以在活动开始时刻到达之前的任意时刻发起该呼叫预约请求；其中，所述呼叫预约请求用于指示所述服务端在所述活动开始时刻向所述客户端和所述提醒对象中至少之一发起呼叫，以建立音频连接或视频连接。再例如，当客户端通过服务端将提醒消息发送至提醒对象时，由于服务端可以获得该提醒消息并获取其中的活动描述信息，那么服务端可以根据该活动描述信息包含的活动开始时刻，在所述活动开始时刻向所述客户端和所述提醒对象中至少之一发起呼叫，以建立音频连接或视频连接，而无需客户端单独发送上述的呼叫预约请求或类似消息。对于上述由服务端发起呼叫的方案，服务端可以仅向所述客户端发起呼叫，使得客户端响应于该呼叫而建立相应的音频连接或视频连接，而提醒对象可以通过其他途径加入该音频连接或视频连接；或者，服务端可以仅向提醒对象发起呼叫，使得提醒对象响应于该呼叫而建立相应的音频连接或视频连接，其中服务端可以同时向所有提醒对象发起呼叫，也可以仅向部分提醒对象发起呼叫、而其他提醒对象可以通过其他途径加入已建立的音频连接或视频连接，当然客户端也可以通过其他途径加入已建立的音频连接或视频连接；或者，服务端可以向客户端和提醒对象发起呼叫，使得在客户端与提醒对象之间建立起音频连接或视频连接。
在本实施例中，客户端可以获取活动描述信息包含的活动形式信息，该活动形式信息用于表明相应的活动为电话会议、视频会议等线上活动，或者聚餐、出游等线下活动。 那么，客户端可以在确定活动形式信息为电话会议或视频会议等线上活动时，发起上述的呼叫请求或者呼叫预约请求，以使得发送方与提醒对象之间通过相应的音频连接或视频连接实现该线上活动。
图3是本申请一示例性实施例提供的一种基于接收方侧的活动提醒方法的流程图。如图3所示，该方法应用于接收方使用的电子设备上，可以包括以下步骤：
步骤302，移动化企业办公平台的客户端接收活动类型的提醒消息。
步骤304，所述客户端展示所述提醒消息包含的活动描述信息。
步骤306，所述客户端根据收到的针对所述活动描述信息的用户触发操作，向所述提醒消息的发送方返回相应的响应消息，所述响应消息包括所述用户触发操作指示的针对所述活动描述信息的接受状况信息。
在一实施例中，基于接收方的用户触发操作，客户端可以直接返回相应的响应消息，以向发送方告知相应的接受状况信息。
在另一实施例中，客户端可以根据接收方的接受状况信息，对用户触发操作采取不同的处理方式。例如，当所述用户触发操作指示的接受状况信息为同意时，所述客户端可以直接返回所述响应消息；而当所述用户触发操作指示的接受状况信息为拒绝时，所述客户端可以进一步获取相应的拒绝理由，并将所述拒绝理由添加至所述响应消息中，以返回至所述发送方。其中，客户端可以向接收方展示预先设定的备选拒绝理由，以供接收方进行选择；或者，客户端可以向接收方提供理由输入框，以供接收方在该理由输入框内填入相应的拒绝理由。对于拒绝理由的填写可以为非强制性操作，即接收方可以自行决定是否输入拒绝理由，且不会影响响应消息的发送；或者，拒绝理由的填写可以为强制性操作，接收方必须输入拒绝理由后才能够发出响应消息，以确保发送方能够了解接收方对于活动描述信息的认同状况，并基于拒绝理由而对活动进行合理调整。
在本实施例中，当所述用户触发操作指示的接受状况信息为同意时，所述客户端可以根据所述活动描述信息，在所述移动化企业办公平台中的管理日历中添加相应的活动事件。其中，对于该管理日历与活动事件的处理过程，与发送方侧的处理过程类似，可以参考上述图2A或图2B所示实施例中的描述，此处不再赘述。
在本实施例中，当所述用户触发操作指示的接受状况信息为拒绝时，所述客户端可以进一步获取针对所述活动描述信息的至少一个项目的调整信息，并向所述发送方发出包含所述调整信息的调整请求；相应地，如果发送方确认接受该调整请求，发送方侧的客户端可以对活动描述信息进行调整，并进一步将调整后的活动描述信息告知各个提醒 对象，例如该发送方侧的客户端可以基于调整后的活动描述信息向所述提醒对象发送新的提醒消息，或者可以基于调整后的活动描述信息向所述提醒对象发送针对所述提醒消息的调整指令，并由接收方侧的客户端根据所述调整指令调整所述提醒消息中的活动描述信息。
在本实施例中，所述客户端可以获取所述提醒消息中包含的提醒时间点和提醒方式，并向所述即时通讯应用的服务端发起对应于所述提醒时间点和所述提醒方式的活动提醒请求；然后，客户端可以响应所述服务端在所述提醒时间点以所述提醒方式发起的活动提醒事件，以对接收方进行活动提醒，尤其是当接收到活动类型的提醒消息的时刻与活动开始时刻之间相隔较久的情况下，可以避免接收方发生遗忘而错过活动或迟到。
此外，针对本申请的移动化企业办公平台提供多种类型的提醒消息的特点，图4提出了本申请一示例性实施例提供的又一种基于发送方侧的活动提醒方法的流程图。如图4所示，该方法应用于发送方使用的电子设备上，可以包括以下步骤：
步骤402，移动化企业办公平台的客户端获取提醒消息生成指令。
步骤404，所述客户端展示出所述提醒消息的备选消息类型。
在本实施例中，备选消息类型可以包括以下至少之一：标准类型、任务类型、活动类型、催办类型、投票类型等，本申请并不对此进行限制。
步骤406，所述客户端根据用户选取的消息类型，生成相应的消息。
由以上技术方案可见，本申请通过提供活动类型的提醒消息，可以针对在时限性等方面具有较高要求的活动事件而单独发出提醒消息，并且能够有效地区别于其他类型的提醒消息，从而即便在用户接收到较多数量的提醒消息时，仍然能够基于消息类型而快速区分、识别出上述的活动事件，避免发生遗漏。
为了便于理解，下面以企业即时通讯应用“企业微信”为例，对本申请的技术方案进行说明。假定手机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的会议提醒， 下面基于该过程对本申请的技术方案进行详细描述。
图5示出了手机13上的企业微信客户端1包含的提醒消息管理页面50，该提醒消息管理页面50用于集中展示用户A接收和发送的所有提醒消息，比如来自用户AA的任务类型的提醒消息、由用户A自己发出的DING类型的提醒消息(即标准类型的提醒消息)等。同时，该提醒消息管理页面50还可以用于实施与提醒消息相关的其他功能，比如当检测到用户A触发该提醒消息管理页面50右上角的新建标识51时，可使手机13上的企业微信客户端1收到该用户A针对提醒消息的用户创建操作，从而切换至图6所示的消息类型选择页面60，以由用户A进一步选取所需创建的提醒消息的消息类型。
如图6所示，消息类型选择页面60中可以包括多种备选的消息类型，比如适合发通知、讨论的DING类型，适合任务分配、跟踪的任务类型、适合会议邀约、约会的会议类型等，当然本申请并不对此进行限制。企业微信客户端1可以根据收到的用户A针对选项61、选项62或选项63的用户选择操作，确定所需创建的提醒消息的消息类型；例如，假定收到针对选项63的用户选择操作，企业微信客户端1可以确定用户A希望创建会议类型的提醒消息，从而展示出图7所示的新建会议页面70，以供用户A在该新建会议页面70中填入相关信息，用于创建相应的会议提醒消息。
如图7所示，用户A可以在输入框71内输入会议描述信息中的“会议主题”信息，即会议所需协商的主要内容，比如“讨论X项目存在的问题，以及进一步的开发需求”等。用户A可以在输入框72内输入会议描述信息中的“地点”信息，即会议举办地，比如“2号楼201室”等。用户A可以在时间编辑框73内编辑会议描述信息中的会议时间信息，比如会议开始时刻为“2017年4月28日14:00”、会议结束时刻为“2017年4月28日16:00”；当然，会议时间信息还可以采用其他形式，比如“会议开始时刻+会议时长”等，本申请并不对此进行限制。用户A可以通过选项74设定当前创建的会议提醒消息的是否自动重复发送，比如当用户A设定为不需要重复时，该会议提醒消息只会在用户A触发“发送”选项78后被单次发出；而当用户A设定为需要重复时，企业微信客户端1可以根据用户A进一步设定的重复周期、反复发出该会议提醒消息，直至到达会议开始时刻或会议结束时刻，从而自动实现对用户B、用户C的多次提醒。用户A可以通过添加选项75选取希望添加为提醒对象(即参与人)的用户，该提醒对象可以来自该用户A的关联用户，比如企业微信客户端1上的应用内通讯录(如微信好友等)、手机13内的手机通讯录、企业微信客户端1上记录的该用户A的所属团体(如企业)的团体成员(如企业内的同事)、企业微信客户端1上记录的该用户A对应的外部联系 人(例如与用户A所属团体相关联的外部团体的团体成员)等，本申请并不对此进行限制。用户A还可以通过各个已添加的提醒对象(如图7所示的用户B和用户C)对应的删除选项76，删除相应的提醒对象。用户A可以通过发送方式选项77，选取希望采用的针对该会议提醒消息的发送方式，比如发送方式可以包括基于即时通讯技术的“应用内”、“短信”和“电话”等，且用户A可以同时选取一种或多种发送方式。用户A可以通过提醒选项78设定是否需要启动针对当前创建的会议提醒消息的提醒功能，以及在设定为需要启动该提醒功能时，进一步设定该提醒功能的提醒时间点，比如当提醒时间点为图7所示的“提前5分钟”时，提醒对象可以在会议开始时刻前5分钟得到提醒，避免发生遗漏；同时，用户A还可以进一步设定提醒方式，该提醒方式的选取类似于上述的“发送方式”，比如可以包括“应用内”、“短信”、“电话”等一种或多种提醒方式。
用户A可以通过触发会议自动发起选项79，确定是否由企业微信客户端1主动向提醒对象发起呼叫操作；其中，当会议自动发起选项79被开启时，企业微信客户端1可以在会议开始时刻自动向提醒对象发起电话会议或视频会议的呼叫请求，从而在用户A与提醒对象之间实现电话会议或视频会议，或者在提醒对象之间实现电话会议或视频会议(即用户A可以不参与会议)。当然，用户A和提醒对象也可以中途加入已建立的电话会议或视频会议。或者，当会议自动发起选项79被开启时，企业微信客户端1可以在会议开始时刻之前向企业微信服务端1发起呼叫预约请求，使得该企业微信服务端1在会议开始时刻向用户A和提醒对象中至少之一发起呼叫，从而建立起电话会议或视频会议。当然，如果企业微信客户端1通过企业微信服务端将会议提醒消息发送至提醒对象时，由于企业微信服务端1可以获得该会议提醒消息并获取其中的会议开始时刻，在该会议开始时刻向用户A和提醒对象中至少之一发起呼叫，以建立起电话会议或视频会议，而无需上述的企业微信客户端1单独发送上述的呼叫预约请求或类似消息。
当由企业微信服务端发起呼叫时，该企业微信服务端可以仅向用户A发起呼叫，以建立仅用户A加入的电话会议或视频会议，而提醒对象可以中途加入该电话会议或视频会议；或者，该企业微信服务端可以仅向部分提醒对象发起呼叫，以建立仅该部分提醒对象加入的电话会议或视频会议，而用户A和其他提醒对象可以中途加入该电话会议或视频会议；或者，该企业微信服务端可以向所有提醒对象发起呼叫，以建立所有提醒对象加入的电话会议或视频会议，而用户A可以中途加入该电话会议或视频会议；或者，该企业微信服务端可以向用户A和所有提醒对象发起呼叫，以建立用户A和所有提醒对 象加入的电话会议或视频会议。
进一步地，企业微信客户端1可以确定会议形式，并当会议形式为电话会议或视频会议等线上会议时，通过上述的呼叫请求或呼叫预约请求，自动在用户A与提醒对象之间实现电话会议或视频会议；或者，企业微信客户端1可以在会议形式为电话会议或视频会议等线上会议时，示出上述的会议自动发起选项79，而在其他会议形式时隐藏该会议自动发起选项79。
除了触发图5所示的新建标识51之外，用户A还可以通过其他方式创建会议提醒消息。假定用户A在企业微信客户端1中参与了如图8所示的群聊通讯会话(同样适用于用户A与单个联系人之间的单聊通讯会话)，用户A可以在相应的通讯会话页面80内，针对任一通讯消息81进行触发(如点击、长按、重压等)，可使企业微信客户端1展示出针对该通讯消息81的功能菜单82，该功能菜单82中包括“DING一下”、“复制”、“转发”等菜单选项。
在一种情况下，当检测到用户A选取“DING一下”对应的菜单选项820时，企业微信客户端1可以确定该用户A针对提醒消息发起用户创建操作，从而切换至图6所示的消息类型选择页面60，以由用户A进一步选取所需创建的提醒消息的消息类型，以及通过图7所示的新建会议页面70创建相应的会议提醒消息。
在另一种情况下，企业微信客户端1可以主动对通讯消息81的消息内容进行分析，或者企业微信客户端1可以向企业微信服务端发起针对该通讯消息81的分析请求、以由企业微信服务端对该通讯消息81的消息内容进行分析，以确定该通讯消息81是否包含预设类型的活动描述信息。例如，当通讯消息81的消息内容为“明天下午2-4点在2号楼201室讨论X项目存在的问题，以及进一步的开发需求”时，假定分析结果为该消息内容中包含活动时间信息为“明天下午2-4点”、活动地点信息为“2号楼201室”、活动主题信息为“讨论X项目存在的问题，以及进一步的开发需求”，那么企业微信客户端1可以在用户A选取菜单选项820时，自动确定相应的提醒消息为会议提醒消息并转入图7所示的新建会议页面70、无需用户A通过图6所示的消息类型选择页面60进行手动选取消息类型；进一步地，企业微信客户端1还可以根据分析出的上述活动描述信息，自动对新建会议页面70进行内容填写，以简化用户A的操作、提升会议提醒消息的创建效率。
用户A通过手机13发出会议提醒消息后，手机14、手机15上运行的企业微信客户端1可以接收到该会议提醒消息，并向用户B、用户C进行展示。例如图9所示，手机 15上运行的企业微信客户端3可以通过提醒消息管理页面90展示用户C发送和接收到的所有提醒消息，使得用户C可以查看到来自用户A的上述会议提醒消息的消息内容91。同时，对于会议提醒消息或其他活动类型的提醒消息而言，发送方除了需要了解接收方是否已经查看相应的会议提醒消息之外，更重要的是希望了解接收方是否能够参与相关会议。因此，在提醒消息管理页面90中还可以展示出针对上述消息内容91的响应选项92，包括图9所示的“接受”和“拒绝”等；其中，当用户C选取响应选项92中的“接受”时，表明其可以参与用户A提出的会议，当用户C选取响应选项92中的“拒绝”时，表明其无法参与用户A提出的会议。
由于提醒消息管理页面90需要对用户C发送和接收的所有提醒消息进行集中展示，为了使得用户C能够在手机15上同时查看到更多提醒消息，企业微信客户端3可能会尽量减小每条提醒消息占用的展示区域，使得上述的响应选项92可能并不一定展示于该提醒消息管理页面90中，甚至消息内容91也可能无法完全展示、仅能够示出概略内容。那么，用户C可以触发提醒消息管理页面90中的消息内容91，使得企业微信客户端3切换至图10所示的提醒消息详情页面1000，并在该提醒消息详情页面1000的内容展示区域1001示出上述的消息内容91，且该提醒消息详情页面1000还可以包括功能选项区域1002，该功能选项区域1002中可以包括上述的“接受”、“拒绝”等响应选项92。当某一响应选项92被选中时，相应的选项内容可以随之变化，比如当“拒绝”被选中时，相应的响应选项92可由图10中的“拒绝”变化为图11所示的“已拒绝”；类似地，当“接受”被选中时，可以将“接受”变化为“已接受”。
此外，提醒消息详情页面1000中还可以包括会议提醒消息对应的消息动态区域1003，用于展示与该会议提醒消息相关的动态消息，比如该会议提醒消息的发送方或接收方针对该会议提醒消息的回复信息等。以用户C为例，用户C可以通过对功能选项区域1002中的“回复”选项进行触发，从而输入针对该会议提醒消息的回复信息。例如图11所示，假定回复信息的信息内容1003A为“能不能13:00开始？16点有约了”，该信息内容1003A可以被展示于上述的动态区域1003中；类似地，当手机15接收到其他用户发出的回复信息时，相应的信息内容同样可以被展示于该动态区域1003中，以供向用户C进行集中展示。当然，某一用户发出的回复信息，并不一定会被该会议提醒消息的所有关联通讯方(即该会议提醒消息的发送方和所有接收方)接收和查看，比如用户C可以根据实际情况选择上述的所有关联通讯方中的一个或多个用户，作为该回复信息的发送对象；举例而言，企业微信客户端3可以向用户C提供一“悄悄话”选项，当用户 C未选中“悄悄话”选项时，上述的回复信息可以发送至所有关联通讯方，当用户C选中“悄悄话”选项时，上述的回复信息可以仅发送至该会议提醒消息的发送方——用户A、而其他用户不会接收到该回复信息。
对于用户A而言，可以在手机13上查看到提醒对象对上述的会议提醒消息的响应状况、回复信息等动态。例如图12所示，在手机13上运行的企业微信客户端1的提醒消息管理页面1200中，分别展示出了上述的会议提醒消息对应的展示区域1201以及用于展示来自用户AA的任务提醒消息的展示区域1202、用于展示用户A发出的DING提醒消息的展示区域1203。在展示区域1201中，可以展示出8个提醒对象对会议提醒消息的响应状况1201A，比如该响应状况1201A可以为“5人已接受，1人已拒绝，2人未响应”，其中“1人已拒绝”可以对应于上述的用户C；同时，展示区域1201中还可以展示出与会议提醒消息相关的回复信息1201B，比如该回复信息1201B可以包括上述的用户C输入的“能不能13:00开始？16点有约了”。同样地，为了方便查看，手机15也可以采用与图12所示实施例类似的方式，将图11所示的动态区域1003及其回复内容展示于如图9所示的提醒消息管理页面90中，此处不再赘述。
在图12所示的提醒消息管理页面1200中，响应状况1201A可以仅包括类似于“5人已接受，1人已拒绝，2人未响应”的概略信息，而用户A可以通过触发该响应状况1201A，使得企业微信客户端3在手机15上展示出图13A所示的响应详情页面1300，以详细查看每一响应状况具体对应的提醒对象。例如图13A所示，当用户A选取“已接受”对应的选项1301时，该响应详情页面1300中可以示出所有针对上述的会议提醒消息选择“接受”的用户，比如用户AA、用户BB、用户DD、用户EE、用户FF等；类似地，当用户A选取“已拒绝”对应的选项1302时，该响应详情页面1300可以示出所有针对上述的会议提醒消息选择“拒绝”的用户，例如上述的用户C。而当用户A选取“未响应”对应的选项1303时，如图13B所示，该响应详情页面1300可以示出尚未针对上述的会议提醒消息做出响应的用户，比如用户LL、用户KK等；其中，响应详情页面1300还可以针对每个“未响应”的用户，示出相应的“再次提醒”选项1304，当用户A选取诸如用户LL对应的“再次提醒”选项1304时，手机13可以再次向该用户LL发送上述的会议提醒消息，以提醒该用户LL做出响应。
当用户A发现用户C针对上述的会议提醒消息的响应状况为“拒绝”时，用户A并不能够由此了解用户C的拒绝原因。虽然用户C可能向用户A发送诸如图12所示的回复信息1201B，以向用户A进行说明，但是并不能够保证用户C每次都能够发送回复信 息进行解释，也不能够保证其他用户同样会发送回复信息进行解释，使得用户A需要通过额外的方式进行询问，比如向用户C发送回复信息或即时通讯消息、呼叫用户C等，造成操作繁琐、效率低下。因此，如图14所示，当用户C选取“拒绝”选项时，手机15上运行的企业微信客户端3可以展示出理由输入窗口1003，以供用户C输入至少一项拒绝理由；在一实施例中，对于拒绝理由的输入操作可以是强制的，即用户C必须输入至少一项拒绝理由，企业微信客户端3才能够允许用户C选中“拒绝”选项。理由输入窗口1003中可以示出至少一项预定义的拒绝理由1003A，以供用户C通过触发预定义的拒绝理由1003A对应的选择框1003B来进行选择，用户C也可以通过输入框1003C来手动输入拒绝理由；当然，理由输入窗口1003中可以示出预定义的拒绝理由1003A与输入框1003C中至少之一，只要能够由用户C提供拒绝理由即可。
相应地，如图15所示，用户A可以在诸如响应详情页面1500中，通过选择“已拒绝”对应的选项1501，查看选择“拒绝”的提醒对象及其拒绝理由1502，比如用户C提供的拒绝理由1502可以为“16:00有约，无法全程参加会议”。那么，用户A在查看到拒绝理由1502之后，就可以相应地做出安排或调整，比如根据用户C的需求而提前或延后会议时间等。
除了提供拒绝理由之外，当提醒对象对于会议提醒消息中的会议描述信息存在不同意见时，还可以对相应的会议描述信息提出调整请求，以实现相应调整。例如图16所示，在手机15示出的提醒消息详情页面1600中，在会议时间信息、会议地点信息的左侧可以分别示出相应的调整标识1601、调整标识1602。以针对会议时间信息的调整为例，当收到用户C针对调整标识1601的触发操作时，手机15上运行的企业微信客户端3可以示出图17所示的时间调整选项1603，使得用户C可以针对会议时间信息提出调整建议；较为具体地，用户C可以首先在图17所示的提醒消息详情页面1600中设置调整后的会议开始时刻，然后通过触发“下一步”来进一步设置调整后的会议结束时刻，从而得到用户C希望采用的、调整后的会议时间信息。手机15可以针对调整后的会议时间信息向用户A发起调整请求；或者，手机15可以首先向用户C展示出图18所示的确认窗口1604，并由用户C确认后向用户A发起上述的调整请求。
在图16所示的提醒消息详情页面1600中，可以在用户C确认选取“拒绝”后，才示出调整标识1601-1602，以供用户C进一步发出调整请求；当然，即便在用户C尚未选择“接受”或“拒绝”，或者用户C已经选择“接受”的情况下，仍然可以示出上述的调整标识1601-1602，以供用户C进一步发出调整请求。
假定用户C选择了“拒绝”，用户A可以在图19所示的响应详情页面1900中的“已拒绝”子页面中，查看到用户C发出的调整请求的请求内容1901，比如该请求内容1901可以包括“调整建议：将会议时间调整为4月28日周五13:00～15:00”。当然，正如上文所述，如果用户C选择了“接受”，用户A可以在响应详情页面1900中的“已接受”子页面中，查看到用户C发出的调整请求的请求内容，如果用户C尚未选择“接受”或“拒绝”，用户A可以在响应详情页面1900中的“未响应”子页面中，查看到用户C发出的调整请求的请求内容。
在图19所示的响应详情页面1900中，可以示出针对请求内容1901的处理选项，包括“同意”和“拒绝”等。当用户A选取“同意”选项时，表明用户A认同用户C建议的针对会议时间信息的调整，那么手机13上运行的企业微信客户端1一方面可以根据调整后会议时间信息，对先前发出的会议提醒消息中的会议时间信息进行调整，另一方面可以向会议提醒消息的提醒对象发送相应的调整指令，以由各个提醒对象使用的电子设备上运行的企业微信客户端响应于该调整指令：根据该调整指令指示的上述调整后会议时间信息，对先前接收到的会议提醒消息中的会议时间信息进行调整。例如图20所示，在手机13示出的提醒消息管理页面2000中，会议时间信息可由上述的“4月28日周五16:00～18:00”调整为“4月28日周五13:00～15:00”，且可以通过调整后的会议时间信息附近示出“更新”、“下划线”或类似的提示信息2001，以便于用户A进行查看。类似地，用户B、用户C等提醒对象使用的手机14、手机15上，运行的企业微信客户端2、企业微信客户端3也可以基于上述的调整指令，将会议时间信息由上述的“4月28日周五16:00～18:00”调整为“4月28日周五13:00～15:00”，以及在调整后的会议时间信息附近示出“更新”、“下划线”或类似的提示信息。
当然，除了通过调整指令对先前的会议提醒消息进行调整之外，手机13上运行的企业微信客户端1还可以根据调整后的会议时间信息，向各个提醒对象发送新的会议提醒消息，且新的会议提醒消息中包含调整后的会议时间信息。例如图21所示，在手机15示出的提醒消息管理页面2100中，可以示出手机15接收到的新的提醒消息2101，以及先前接收到的提醒消息2102；针对新的提醒消息2101中的会议时间信息，可以采用诸如“！！！”、“下划线”或类似的提示信息2103，使用户C更加容易关注到会议时间信息的调整情况。同时，针对新的提醒消息2101，可以示出针对该提醒消息的响应选项2104，以供用户C进行选取。
在本申请的企业微信客户端中，为了便于实施企业内部的企业事项管理，可以提供 管理日历功能。例如图22所示，通过示出管理日历2200，并在该管理日历2200上示出每天相关联的企业事项，可以帮助用户快速掌握企业事项的处理状况，便于后续工作的合理安排。以图22所示的管理日历2200为例，通过为存在企业事项的日期添加事件提示信息，即可使得用户快速了解相应的日期存在相关联的企业事项，比如在“2017年4月4日”、“2017年4月5日”、“2017年4月12日”、“2017年4月18日”的底部添加一黑色圆点，表明存在任务事件。而针对在上述实施例中，用户A向用户C发送的会议提醒消息，相当于创建了一项新的企业事项——会议事件，那么对于用户A使用的手机13上运行的企业微信客户端1、用户C使用的手机15上运行的企业微信客户端3而言，均可以在相应的管理日历中针对该会议提醒消息创建对应的会议事件。以用户C为例，在图21所示的提醒消息管理页面2100的左上角可以设有日历页面入口2105，当检测到用户C触发该日历页面入口2105时，可以转入如图22所示的管理日历2200，以供用户C查看或编辑已存在的企业事项，或者手动创建新的企业事项。如图22所示，由于手机15接收到的会议提醒消息中包含如图21所示的会议时间信息为“4月28日周五13:00～15:00”，因此可以创建与“2017年4月28日”相关的会议事件；其中，为了区别于上述的任务事件以及其他类型的企业事项，可以针对该会议事件在“28”的底部添加白色圆点，以便于用户C将该会议事件与其他企业事项进行快速区分。类似地，“2017年4月5日”的底部也存在一黑色圆点和一白色圆点，表明当天同时存在一任务事件和一会议事件。
其中，当检测到某一日期被选中时，比如图22中假定“2017年4月28日”被选中，可以示出该日期内存在的企业事项，例如可以在管理日历2200下部的展示区域2201内，示出“2017年4月28日”存在的任务事件(对应于“28”底部的黑色圆点)和会议事件(对应于“28”底部的白色圆点)的描述信息，该描述信息可以为图22所示的摘要信息(当某一摘要信息被选中时，可以进一步示出相应的详情信息)，或者该描述信息可以为详情信息。当“2017年4月28日”被选中时，可以对相应的数字“28”进行突出显示，以区别于其他日期，比如图22中采用了将数字28调整为白色并添加黑色背景的方式；同时，对于当前所处的日期，也可以采用区别于被选中的日期和其他日期的方式进行突出显示，比如“2017年4月26日”外围可以添加一圆环。
在展示被选中的日期内存在的企业事项时，可以示出针对该企业事项的类型提示信息，比如图22所示的任务事件对应的“任务”字样、会议事件对应的“会议”字样等。此外，还可以将该类型提示信息与管理日历中的上述黑色圆点、白色圆点等企业事项提 示信息相配合，比如将类型提示信息与企业事项提示信息采用相同或相近的展示属性，使得用户能够从视觉观感上获得两者之间的关联性，有助于提升用户体验；例如，该展示属性可以包括颜色、灰度、透明度等，本申请并不对此进行限制。
在本申请的技术方案中，企业微信客户端可以支持多种类型的提醒消息，比如上述的“会议”类型、“任务”类型、“DING”类型等。在图20所示的提醒消息管理页面2000中，由于设定的消息类型为“全部”，所以“会议”、“任务”、“DING”等所有类型的提醒消息都能够被展示于该提醒消息管理页面2000中。而在图23所示的提醒消息管理页面2300中，通过触发类型修改选项2301，可以将消息类型设定为“会议”，从而筛选出“会议”类型的提醒消息、并仅在该提醒消息管理页面2300中示出“会议”类型的提醒消息，以便于快速查看。当然，图23仅示意性地示出了手机13上运行的企业微信客户端1可能示出的提醒消息管理页面2300，而对于手机14、手机15等运行的企业微信客户端2、企业微信客户端3同样能够实现类似的提醒消息筛选展示，此处不再赘述。
在上述实施例中，假定用户A通过手机13上运行的企业微信客户端1，向用户B、用户C使用的手机14、手机15发送会议提醒消息，而用户B、用户C分别通过手机14、手机15上运行的企业微信客户端2、企业微信客户端3查看相应的会议提醒消息等，实现针对会议或其他活动的有效提醒。而实际上，企业微信客户端并不仅存在移动端，还可以包括PC端，即用户A可以通过PC上运行的企业微信客户端，向用户B、用户C发送会议提醒消息，以及用户B、用户C也可以通过PC上运行的企业微信客户端接收会议提醒消息，以及实现上述实施例中的其他功能。
假定图24示出了用户A使用的PC端的企业微信客户端的操作界面2400，用户A通过选取最左侧一列功能选项中的“DING”选项，可以在该操作界面2400上展示出从左侧起第二列功能选项，用户A进一步通过选取该第二列功能选项中的“全部”选项，可以在该操作界面2400上展示出用户A接收和发出的所有提醒消息，且当用户A进一步选取某一提醒消息2401时，该操作界面2400上可以示出最右侧的提醒消息详情界面2402，该提醒消息详情界面2402用于展示该提醒消息2401的消息内容。
在操作界面2400上可以设有新建标识2403。当检测到用户A触发(例如通过鼠标光标进行点击)该新建标识2403时，可以示出如图25所示的消息类型选择页面2500；其中，当用户A选取“会议”类型时，可以进一步示出图26所示的新建会议页面2600，从而创建会议类型的提醒消息。实际上，上述创建过程与图5-7所示的用户A通过手机 13创建会议提醒消息的过程相似，此处不再赘述。同样地，与图8所示实施例相类似的，用户A在PC端的操作界面2400上，也可以通过对通讯消息进行触发而创建会议提醒消息，此处不再赘述。
图27示出了根据本申请的一示例性实施例的电子设备的示意结构图。请参考图27，在硬件层面，该电子设备包括处理器2702、内部总线2704、网络接口2706、内存2708以及非易失性存储器2710，当然还可能包括其他业务所需要的硬件。处理器2702从非易失性存储器2710中读取对应的计算机程序到内存2708中然后运行，在逻辑层面上形成活动提醒装置。当然，除了软件实现方式之外，本申请并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图28，在软件实施方式中，该活动提醒装置可以包括：
接收单元2801，使客户端接收针对活动类型的提醒消息生成指令；
确定单元2802，使所述客户端确定提醒对象和所述活动类型对应的活动描述信息；
发送单元2803，使所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
可选的，所述接收单元2801具体用于：
使所述客户端收到针对提醒消息的用户创建操作，以及针对所述提醒消息的类型信息的用户选择操作；
当所述用户选择操作选取的类型信息为活动类型时，使所述客户端确定接收到所述提醒消息生成指令。
可选的，所述接收单元2801具体用于：
使所述客户端收到针对通讯消息的用户触发操作，所述用户触发操作用于指示所述客户端将所述通讯消息转换为提醒消息；
使所述客户端在识别出所述通讯消息的消息内容中包含预设类型的活动描述信息时，确定接收到所述提醒消息生成指令。
可选的，所述确定单元2802具体用于：
使所述客户端提取所述消息内容中包含的预设类型的活动描述信息，以及使所述客户端将所述通讯消息的关联通讯方确定为所述提醒对象。
可选的，所述活动描述信息包括以下至少之一：
活动主题信息、活动地点信息、活动形式信息、活动时间信息。
可选的，所述发送单元2803具体用于：
使所述客户端在默认发送时刻或者用户设定的发送时刻、按照默认消息类型或者用户设定的消息类型发送所述提醒消息。
可选的，还包括：
响应接收单元2804，使所述客户端接收所述提醒对象返回的响应消息，所述响应消息包含所述提醒对象针对所述活动描述信息的接受状况信息；
展示单元2805，使所述客户端将所述提醒对象与对应的响应消息进行关联展示。
可选的，当所述接受状况信息为拒绝时，所述响应消息还包括：拒绝理由。
可选的，还包括：
添加单元2806，使所述客户端根据所述活动描述信息，在所述通讯应用中的管理日历中添加相应的活动事件。
可选的，还包括：
请求接收单元2807，使所述客户端接收到所述提醒对象针对所述活动描述信息中的至少一个项目提出的调整请求；
调整单元2808，使所述客户端在收到针对所述调整请求的用户确认操作时，基于调整后的活动描述信息向所述提醒对象发送针对所述提醒消息的调整指令，或者基于调整后的活动描述信息向所述提醒对象发送新的提醒消息。
可选的，还包括：
重复提醒单元2809，所述客户端在发出所述提醒消息后的预设时长内未接收到所述提醒对象返回的响应消息时，向所述提醒对象重新发送所述提醒消息，或者展示针对所述提醒对象的重复提醒选项，以在收到针对所述重复提醒选项的用户触发操作时向所述提醒对象重新发送所述提醒消息。
可选的，所述提醒消息中包含默认或用户设定的提醒时间点、默认或用户设定的提醒方式，以使所述提醒对象在所述提醒时间点基于所述提醒方式被进行活动提醒，且提醒内容与所述活动描述信息相关。
可选的，还包括：
呼叫请求单元2810，使所述客户端根据所述活动描述信息包含的活动开始时刻，在所述活动开始时刻发起针对所述提醒对象的呼叫请求，以建立音频连接或视频连接。
可选的，还包括：
呼叫预约单元2811，使所述客户端根据所述活动描述信息包含的活动开始时刻，向 服务端发起呼叫预约请求，所述呼叫预约请求用于指示所述服务端在所述活动开始时刻向所述客户端和所述提醒对象中至少之一发起呼叫，以建立音频连接或视频连接。
可选的，所述发送单元2803具体用于：
所述客户端将所述提醒消息发送至服务端，以由所述服务端将所述提醒消息发送至所述提醒对象；
其中，所述提醒消息用于指示所述服务端：根据所述活动描述信息包含的活动开始时刻，在所述活动开始时刻向所述客户端和所述提醒对象中至少之一发起呼叫，以建立音频连接或视频连接。
可选的，所述活动描述信息包含活动形式信息，所述活动形式信息表明相应的活动为电话会议或视频会议。
请参考图29，在软件实施方式中，该活动提醒装置可以包括：
第一接收单元2901，使客户端接收活动类型的提醒消息；
展示单元2902，使客户端展示所述提醒消息包含的活动描述信息；
返回单元2903，使所述客户端根据收到的针对所述活动描述信息的用户触发操作，向所述提醒消息的发送方返回相应的响应消息，所述响应消息包括所述用户触发操作指示的针对所述活动描述信息的接受状况信息。
可选的，所述返回单元2903具体用于：
当所述用户触发操作指示的接受状况信息为同意时，使所述客户端直接返回所述响应消息；
当所述用户触发操作指示的接受状况信息为拒绝时，使所述客户端进一步获取相应的拒绝理由，并将所述拒绝理由添加至所述响应消息中，以返回至所述发送方。
可选的，还包括：
添加单元2904，当所述用户触发操作指示的接受状况信息为同意时，使所述客户端根据所述活动描述信息，在所述通讯应用中的管理日历中添加相应的活动事件。
可选的，还包括：
发送单元2905，当所述用户触发操作指示的接受状况信息为拒绝时，使所述客户端进一步获取针对所述活动描述信息的至少一个项目的调整信息，并向所述发送方发送包含所述调整信息的调整请求；
第二接收单元2906，使所述客户端接收所述发送方返回的新的提醒消息，所述新的提醒消息中包含基于所述调整请求而调整后的活动描述信息；或者，使所述客户端接收 所述发送方基于所述调整后的活动描述信息而返回的调整指令，并根据所述调整指令调整所述提醒消息中的活动描述信息。
可选的，还包括：
获取单元2907，使所述客户端获取所述提醒消息中包含的提醒时间点和提醒方式；
请求单元2908，使所述客户端向服务端发起对应于所述提醒时间点和所述提醒方式的活动提醒请求；
响应单元2909，使所述客户端响应所述服务端在所述提醒时间点以所述提醒方式发起的活动提醒事件。
请参考图30，在软件实施方式中，该活动提醒装置可以包括：
生成单元3001，使客户端根据活动描述信息和提醒对象生成提醒消息；
发送单元3002，使所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
可选的，所述生成单元3001具体用于：
使所述客户端收到针对所述提醒消息的用户创建操作，以及针对所述提醒消息的类型信息的用户选择操作；
当所述用户选择操作选取的类型信息为活动类型时，使所述客户端根据所述活动类型生成提醒消息。
可选的，所述生成单元3001具体用于：
使所述客户端收到针对通讯消息的用户触发操作，所述用户触发操作用于指示所述客户端将所述通讯消息转换为提醒消息；
使所述客户端在识别出所述通讯消息的消息内容中包含预设类型的活动描述信息时，生成所述提醒消息。
图31示出了根据本申请的一示例性实施例的电子设备的示意结构图。请参考图31，在硬件层面，该电子设备包括处理器3102、内部总线3104、网络接口3106、内存3108以及非易失性存储器3110，当然还可能包括其他业务所需要的硬件。处理器3102从非易失性存储器3110中读取对应的计算机程序到内存3108中然后运行，在逻辑层面上形成活动提醒消息生成装置。当然，除了软件实现方式之外，本申请并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图32，在软件实施方式中，该活动提醒消息生成装置可以包括：
接收单元3201，使客户端接收提醒消息生成指令；
展示单元3202，使所述客户端展示出所述提醒消息的备选消息类型；
实施单元3203，使所述客户端根据选中的消息类型，生成相应的消息。
可选的，所述备选消息类型包括以下至少之一：
标准类型、任务类型、活动类型、催办类型、投票类型。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
在一个典型的配置中，计算机包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附 图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
以上所述仅为本申请的较佳实施例而已，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。

Claims (52)

  1. 一种活动提醒方法，其特征在于，包括：
    客户端接收针对活动类型的提醒消息生成指令；
    所述客户端确定提醒对象和所述活动类型对应的活动描述信息；
    所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
  2. 根据权利要求1所述的方法，其特征在于，所述客户端接收针对活动类型的提醒消息生成指令，包括：
    所述客户端收到针对提醒消息的用户创建操作，以及针对所述提醒消息的类型信息的用户选择操作；
    当所述用户选择操作选取的类型信息为活动类型时，所述客户端确定接收到所述提醒消息生成指令。
  3. 根据权利要求1所述的方法，其特征在于，所述客户端接收针对活动类型的提醒消息生成指令，包括：
    所述客户端收到针对通讯消息的用户触发操作，所述用户触发操作用于指示所述客户端将所述通讯消息转换为提醒消息；
    所述客户端在识别出所述通讯消息的消息内容中包含预设类型的活动描述信息时，确定接收到所述提醒消息生成指令。
  4. 根据权利要求3所述的方法，其特征在于，所述客户端确定提醒对象和所述活动类型对应的活动描述信息，包括：
    所述客户端提取所述消息内容中包含的预设类型的活动描述信息，以及所述客户端将所述通讯消息的关联通讯方确定为所述提醒对象。
  5. 根据权利要求1所述的方法，其特征在于，所述活动描述信息包括以下至少之一：
    活动主题信息、活动地点信息、活动形式信息、活动时间信息。
  6. 根据权利要求1所述的方法，其特征在于，所述客户端向所述提醒对象发送提醒消息，包括：
    所述客户端在默认发送时刻或者用户设定的发送时刻、按照默认消息类型或者用户设定的消息类型发送所述提醒消息。
  7. 根据权利要求1所述的方法，其特征在于，还包括：
    所述客户端接收所述提醒对象返回的响应消息，所述响应消息包含所述提醒对象针 对所述活动描述信息的接受状况信息；
    所述客户端将所述提醒对象与对应的响应消息进行关联展示。
  8. 根据权利要求7所述的方法，其特征在于，当所述接受状况信息为拒绝时，所述响应消息还包括：拒绝理由。
  9. 根据权利要求1所述的方法，其特征在于，还包括：
    所述客户端根据所述活动描述信息，在通讯应用中的管理日历中添加相应的活动事件。
  10. 根据权利要求1所述的方法，其特征在于，还包括：
    所述客户端接收到所述提醒对象针对所述活动描述信息中的至少一个项目提出的调整请求；
    所述客户端在收到针对所述调整请求的用户确认操作时，基于调整后的活动描述信息向所述提醒对象发送针对所述提醒消息的调整指令，或者基于调整后的活动描述信息向所述提醒对象发送新的提醒消息。
  11. 根据权利要求1所述的方法，其特征在于，还包括：
    所述客户端在发出所述提醒消息后的预设时长内未接收到所述提醒对象返回的响应消息时，向所述提醒对象重新发送所述提醒消息，或者展示针对所述提醒对象的重复提醒选项，以在收到针对所述重复提醒选项的用户触发操作时向所述提醒对象重新发送所述提醒消息。
  12. 根据权利要求1所述的方法，其特征在于，所述提醒消息中包含默认或用户设定的提醒时间点、默认或用户设定的提醒方式，以使所述提醒对象在所述提醒时间点基于所述提醒方式被进行活动提醒，且提醒内容与所述活动描述信息相关。
  13. 根据权利要求1所述的方法，其特征在于，还包括：
    所述客户端根据所述活动描述信息包含的活动开始时刻，在所述活动开始时刻发起针对所述提醒对象的呼叫请求，以建立音频连接或视频连接。
  14. 根据权利要求1所述的方法，其特征在于，还包括：
    所述客户端根据所述活动描述信息包含的活动开始时刻，向服务端发起呼叫预约请求，所述呼叫预约请求用于指示所述服务端在所述活动开始时刻向所述客户端和所述提醒对象中至少之一发起呼叫，以建立音频连接或视频连接。
  15. 根据权利要求1所述的方法，其特征在于，所述客户端向所述提醒对象发送提醒消息，包括：
    所述客户端将所述提醒消息发送至服务端，以由所述服务端将所述提醒消息发送至所述提醒对象；
    其中，所述提醒消息用于指示所述服务端：根据所述活动描述信息包含的活动开始时刻，在所述活动开始时刻向所述客户端和所述提醒对象中至少之一发起呼叫，以建立音频连接或视频连接。
  16. 根据权利要求13-15中任一项所述的方法，其特征在于，所述活动描述信息包含活动形式信息，所述活动形式信息表明相应的活动为电话会议或视频会议。
  17. 一种活动提醒方法，其特征在于，包括：
    客户端接收活动类型的提醒消息；
    所述客户端展示所述提醒消息包含的活动描述信息；
    所述客户端根据收到的针对所述活动描述信息的用户触发操作，向所述提醒消息的发送方返回相应的响应消息，所述响应消息包括所述用户触发操作指示的针对所述活动描述信息的接受状况信息。
  18. 根据权利要求17所述的方法，其特征在于，所述向所述提醒消息的发送方返回相应的响应消息，包括：
    当所述用户触发操作指示的接受状况信息为同意时，所述客户端直接返回所述响应消息；
    当所述用户触发操作指示的接受状况信息为拒绝时，所述客户端进一步获取相应的拒绝理由，并将所述拒绝理由添加至所述响应消息中，以返回至所述发送方。
  19. 根据权利要求17所述的方法，其特征在于，还包括：
    当所述用户触发操作指示的接受状况信息为同意时，所述客户端根据所述活动描述信息，在通讯应用中的管理日历中添加相应的活动事件。
  20. 根据权利要求17所述的方法，其特征在于，还包括：
    当所述用户触发操作指示的接受状况信息为拒绝时，所述客户端进一步获取针对所述活动描述信息的至少一个项目的调整信息，并向所述发送方发送包含所述调整信息的调整请求；
    所述客户端接收所述发送方返回的新的提醒消息，所述新的提醒消息中包含基于所述调整请求而调整后的活动描述信息；或者，所述客户端接收所述发送方基于所述调整后的活动描述信息而返回的调整指令，并根据所述调整指令调整所述提醒消息中的活动描述信息。
  21. 根据权利要求17所述的方法，其特征在于，还包括：
    所述客户端获取所述提醒消息中包含的提醒时间点和提醒方式；
    所述客户端向服务端发起对应于所述提醒时间点和所述提醒方式的活动提醒请求；
    所述客户端响应所述服务端在所述提醒时间点以所述提醒方式发起的活动提醒事件。
  22. 一种活动提醒消息生成方法，其特征在于，包括：
    客户端接收提醒消息生成指令；
    所述客户端展示出所述提醒消息的备选消息类型；
    所述客户端根据选中的消息类型，生成相应的消息。
  23. 根据权利要求22所述的方法，其特征在于，所述备选消息类型包括以下至少之一：
    标准类型、任务类型、活动类型、催办类型、投票类型。
  24. 一种活动提醒装置，其特征在于，包括：
    接收单元，使客户端接收针对活动类型的提醒消息生成指令；
    确定单元，使所述客户端确定提醒对象和所述活动类型对应的活动描述信息；
    发送单元，使所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
  25. 根据权利要求24所述的装置，其特征在于，所述接收单元具体用于：
    使所述客户端收到针对提醒消息的用户创建操作，以及针对所述提醒消息的类型信息的用户选择操作；
    当所述用户选择操作选取的类型信息为活动类型时，使所述客户端确定接收到所述提醒消息生成指令。
  26. 根据权利要求24所述的装置，其特征在于，所述接收单元具体用于：
    使所述客户端收到针对通讯消息的用户触发操作，所述用户触发操作用于指示所述客户端将所述通讯消息转换为提醒消息；
    使所述客户端在识别出所述通讯消息的消息内容中包含预设类型的活动描述信息时，确定接收到所述提醒消息生成指令。
  27. 根据权利要求26所述的装置，其特征在于，所述确定单元具体用于：
    使所述客户端提取所述消息内容中包含的预设类型的活动描述信息，以及使所述客户端将所述通讯消息的关联通讯方确定为所述提醒对象。
  28. 根据权利要求24所述的装置，其特征在于，所述活动描述信息包括以下至少之一：
    活动主题信息、活动地点信息、活动形式信息、活动时间信息。
  29. 根据权利要求24所述的装置，其特征在于，所述发送单元具体用于：
    使所述客户端在默认发送时刻或者用户设定的发送时刻、按照默认消息类型或者用户设定的消息类型发送所述提醒消息。
  30. 根据权利要求24所述的装置，其特征在于，还包括：
    响应接收单元，使所述客户端接收所述提醒对象返回的响应消息，所述响应消息包含所述提醒对象针对所述活动描述信息的接受状况信息；
    展示单元，使所述客户端将所述提醒对象与对应的响应消息进行关联展示。
  31. 根据权利要求30所述的装置，其特征在于，当所述接受状况信息为拒绝时，所述响应消息还包括：拒绝理由。
  32. 根据权利要求24所述的装置，其特征在于，还包括：
    添加单元，使所述客户端根据所述活动描述信息，在通讯应用中的管理日历中添加相应的活动事件。
  33. 根据权利要求24所述的装置，其特征在于，还包括：
    请求接收单元，使所述客户端接收到所述提醒对象针对所述活动描述信息中的至少一个项目提出的调整请求；
    调整单元，使所述客户端在收到针对所述调整请求的用户确认操作时，基于调整后的活动描述信息向所述提醒对象发送针对所述提醒消息的调整指令，或者基于调整后的活动描述信息向所述提醒对象发送新的提醒消息。
  34. 根据权利要求24所述的装置，其特征在于，还包括：
    重复提醒单元，所述客户端在发出所述提醒消息后的预设时长内未接收到所述提醒对象返回的响应消息时，向所述提醒对象重新发送所述提醒消息，或者展示针对所述提醒对象的重复提醒选项，以在收到针对所述重复提醒选项的用户触发操作时向所述提醒对象重新发送所述提醒消息。
  35. 根据权利要求24所述的装置，其特征在于，所述提醒消息中包含默认或用户设定的提醒时间点、默认或用户设定的提醒方式，以使所述提醒对象在所述提醒时间点基于所述提醒方式被进行活动提醒，且提醒内容与所述活动描述信息相关。
  36. 根据权利要求24所述的装置，其特征在于，还包括：
    呼叫请求单元，使所述客户端根据所述活动描述信息包含的活动开始时刻，在所述活动开始时刻发起针对所述提醒对象的呼叫请求，以建立音频连接或视频连接。
  37. 根据权利要求24所述的装置，其特征在于，还包括：
    呼叫预约单元，使所述客户端根据所述活动描述信息包含的活动开始时刻，向服务端发起呼叫预约请求，所述呼叫预约请求用于指示所述服务端在所述活动开始时刻向所述客户端和所述提醒对象中至少之一发起呼叫，以建立音频连接或视频连接。
  38. 根据权利要求24所述的装置，其特征在于，所述发送单元具体用于：
    所述客户端将所述提醒消息发送至服务端，以由所述服务端将所述提醒消息发送至所述提醒对象；
    其中，所述提醒消息用于指示所述服务端：根据所述活动描述信息包含的活动开始时刻，在所述活动开始时刻向所述客户端和所述提醒对象中至少之一发起呼叫，以建立音频连接或视频连接。
  39. 根据权利要求37或38所述的装置，其特征在于，所述活动描述信息包含活动形式信息，所述活动形式信息表明相应的活动为电话会议或视频会议。
  40. 一种活动提醒装置，其特征在于，包括：
    第一接收单元，使客户端接收活动类型的提醒消息；
    展示单元，使所述客户端展示所述提醒消息包含的活动描述信息；
    返回单元，使所述客户端根据收到的针对所述活动描述信息的用户触发操作，向所述提醒消息的发送方返回相应的响应消息，所述响应消息包括所述用户触发操作指示的针对所述活动描述信息的接受状况信息。
  41. 根据权利要求40所述的装置，其特征在于，所述返回单元具体用于：
    当所述用户触发操作指示的接受状况信息为同意时，使所述客户端直接返回所述响应消息；
    当所述用户触发操作指示的接受状况信息为拒绝时，使所述客户端进一步获取相应的拒绝理由，并将所述拒绝理由添加至所述响应消息中，以返回至所述发送方。
  42. 根据权利要求40所述的装置，其特征在于，还包括：
    添加单元，当所述用户触发操作指示的接受状况信息为同意时，使所述客户端根据所述活动描述信息，在通讯应用中的管理日历中添加相应的活动事件。
  43. 根据权利要求40所述的装置，其特征在于，还包括：
    发送单元，当所述用户触发操作指示的接受状况信息为拒绝时，使所述客户端进一 步获取针对所述活动描述信息的至少一个项目的调整信息，并向所述发送方发送包含所述调整信息的调整请求；
    第二接收单元，使所述客户端接收所述发送方返回的新的提醒消息，所述新的提醒消息中包含基于所述调整请求而调整后的活动描述信息；或者，使所述客户端接收所述发送方基于所述调整后的活动描述信息而返回的调整指令，并根据所述调整指令调整所述提醒消息中的活动描述信息。
  44. 根据权利要求40所述的装置，其特征在于，还包括：
    获取单元，使所述客户端获取所述提醒消息中包含的提醒时间点和提醒方式；
    请求单元，使所述客户端向服务端发起对应于所述提醒时间点和所述提醒方式的活动提醒请求；
    响应单元，使所述客户端响应所述服务端在所述提醒时间点以所述提醒方式发起的活动提醒事件。
  45. 一种活动提醒消息生成装置，其特征在于，包括：
    接收单元，使客户端接收提醒消息生成指令；
    展示单元，使所述客户端展示出所述提醒消息的备选消息类型；
    实施单元，使所述客户端根据选中的消息类型，生成相应的消息。
  46. 根据权利要求45所述的装置，其特征在于，所述备选消息类型包括以下至少之一：
    标准类型、任务类型、活动类型、催办类型、投票类型。
  47. 一种活动提醒方法，其特征在于，包括：
    客户端根据活动描述信息和提醒对象生成提醒消息；
    所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
  48. 根据权利要求47所述的方法，其特征在于，所述客户端根据活动描述信息和提醒对象生成提醒消息，包括：
    所述客户端收到针对所述提醒消息的用户创建操作，以及针对所述提醒消息的类型信息的用户选择操作；
    当所述用户选择操作选取的类型信息为活动类型时，所述客户端根据所述活动类型生成提醒消息。
  49. 根据权利要求47所述的方法，其特征在于，所述客户端根据活动描述信息和提醒对象生成提醒消息，包括：
    所述客户端收到针对通讯消息的用户触发操作，所述用户触发操作用于指示所述客户端将所述通讯消息转换为提醒消息；
    所述客户端在识别出所述通讯消息的消息内容中包含预设类型的活动描述信息时，生成所述提醒消息。
  50. 一种活动提醒装置，其特征在于，包括：
    生成单元，使客户端根据活动描述信息和提醒对象生成提醒消息；
    发送单元，使所述客户端向所述提醒对象发送提醒消息，所述提醒消息包含所述活动描述信息。
  51. 根据权利要求50所述的装置，其特征在于，所述生成单元具体用于：
    使所述客户端收到针对所述提醒消息的用户创建操作，以及针对所述提醒消息的类型信息的用户选择操作；
    当所述用户选择操作选取的类型信息为活动类型时，使所述客户端根据所述活动类型生成提醒消息。
  52. 根据权利要求50所述的装置，其特征在于，所述生成单元具体用于：
    使所述客户端收到针对通讯消息的用户触发操作，所述用户触发操作用于指示所述客户端将所述通讯消息转换为提醒消息；
    使所述客户端在识别出所述通讯消息的消息内容中包含预设类型的活动描述信息时，生成所述提醒消息。
PCT/CN2018/088652 2017-06-06 2018-05-28 活动提醒方法、活动提醒消息生成方法及装置 WO2018223860A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/705,115 US20200111059A1 (en) 2017-06-06 2019-12-05 Method for event reminding, and method and apparatus for generating event reminding message

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710417733.9A CN109005517B (zh) 2017-06-06 2017-06-06 活动提醒方法、活动提醒消息生成方法及装置
CN201710417733.9 2017-06-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/705,115 Continuation US20200111059A1 (en) 2017-06-06 2019-12-05 Method for event reminding, and method and apparatus for generating event reminding message

Publications (1)

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

Family

ID=64565719

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088652 WO2018223860A1 (zh) 2017-06-06 2018-05-28 活动提醒方法、活动提醒消息生成方法及装置

Country Status (4)

Country Link
US (1) US20200111059A1 (zh)
CN (1) CN109005517B (zh)
TW (1) TWI795389B (zh)
WO (1) WO2018223860A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111275394A (zh) * 2020-01-17 2020-06-12 杭州涂鸦信息技术有限公司 消息提醒方法及装置、电子设备

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109600305B (zh) * 2019-01-17 2022-07-12 腾讯科技（深圳）有限公司 提醒处理方法、设置方法及服务器、智能终端及介质
CN112083978B (zh) * 2019-06-12 2024-01-16 钉钉控股（开曼）有限公司 事件分享方法及装置
CN114079651A (zh) * 2020-08-19 2022-02-22 阿里巴巴集团控股有限公司 会议处理方法及装置
CN114726661A (zh) * 2022-03-31 2022-07-08 京东方科技集团股份有限公司 一种智能便签的提醒方法及智能交互显示设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104506715A (zh) * 2014-12-05 2015-04-08 小米科技有限责任公司 通知消息显示方法及装置
CN104507165A (zh) * 2014-09-18 2015-04-08 上海触乐信息科技有限公司 智能提醒方法、系统和装置
CN105099887A (zh) * 2015-07-20 2015-11-25 阿里巴巴集团控股有限公司 活动提醒方法及装置
CN105578431A (zh) * 2016-01-20 2016-05-11 北京智驾互联信息服务有限公司 提醒消息发送装置及方法

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110231216A1 (en) * 2010-03-17 2011-09-22 Research In Motion Limited System and method for controlling event reminders
CN101835108B (zh) * 2010-03-24 2013-06-19 杭州东信北邮信息技术有限公司 一种定制来电助手业务提醒信息的系统和方法
US9402167B2 (en) * 2013-03-14 2016-07-26 Google Technology Holdings LLC Notification handling system and method
CN104376451A (zh) * 2013-08-13 2015-02-25 中兴通讯股份有限公司 一种待提醒事件的提醒方法及终端
CN105243799B (zh) * 2015-09-30 2018-07-27 小米科技有限责任公司 安全提醒处理方法和装置
CN106488413A (zh) * 2016-10-20 2017-03-08 广东欧珀移动通信有限公司 通知消息提醒方法及移动终端
CN106657603A (zh) * 2016-10-28 2017-05-10 努比亚技术有限公司 一种重要通知的发送/接收方法及终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104507165A (zh) * 2014-09-18 2015-04-08 上海触乐信息科技有限公司 智能提醒方法、系统和装置
CN104506715A (zh) * 2014-12-05 2015-04-08 小米科技有限责任公司 通知消息显示方法及装置
CN105099887A (zh) * 2015-07-20 2015-11-25 阿里巴巴集团控股有限公司 活动提醒方法及装置
CN105578431A (zh) * 2016-01-20 2016-05-11 北京智驾互联信息服务有限公司 提醒消息发送装置及方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111275394A (zh) * 2020-01-17 2020-06-12 杭州涂鸦信息技术有限公司 消息提醒方法及装置、电子设备
CN111275394B (zh) * 2020-01-17 2023-10-20 杭州涂鸦信息技术有限公司 消息提醒方法及装置、电子设备

Also Published As

Publication number Publication date
TWI795389B (zh) 2023-03-11
CN109005517B (zh) 2022-05-27
US20200111059A1 (en) 2020-04-09
CN109005517A (zh) 2018-12-14
TW201904238A (zh) 2019-01-16

Similar Documents

Publication Publication Date Title
JP6689422B2 (ja) 新規の通信およびメッセージシステム
WO2018223860A1 (zh) 活动提醒方法、活动提醒消息生成方法及装置
CN109005098B (zh) 任务提醒方法及装置、提醒消息的生成和展示方法及装置
CN111669311A (zh) 通讯方法及装置、系统、电子设备、可读存储介质
US10812431B2 (en) Social platform for event creation and communication and method therefor
US10579969B2 (en) Techniques for managing calendar invites received from different messaging services
US20170302780A1 (en) Calling for Instant Messaging and Recording Instant Messaging Call Specific Conversation
CN108494571B (zh) 发起预约会议的方法、装置及系统
US20120284638A1 (en) System and method for social interaction, sharing and collaboration
US11146510B2 (en) Communication methods and apparatuses
US10491690B2 (en) Distributed natural language message interpretation engine
US20150188862A1 (en) Apparatus and Method for Multi-Format Communication Composition
US20060242234A1 (en) Dynamic group formation for social interaction
WO2020238873A1 (zh) 一种通信方法、服务器和通信系统
US20130094642A1 (en) Call scheduling system
US20160112358A1 (en) Apparatus and method for intelligent suppression of incoming multi-format multi-protocol communications
US20150119080A1 (en) Opt-in and time limited bi-directional real-time location sharing
CN112534837B (zh) 用于提供灵活且集成的通信、调度和商业平台的系统和方法
EP3942497A1 (en) Live meeting object in a calendar view
KR20160138076A (ko) 크로스 클라이언트 그룹 가입 기법
GB2556332A (en) A computerized method and a system for dynamic communication
JP5956079B2 (ja) 社会的、時間的および空間的パラメータに基づくデータオブジェクトの統合的表示および管理
TW201629861A (zh) 約會邀請方法和系統
WO2019015507A1 (zh) 通讯方法及装置
CN106170805B (zh) 组的跨客户端集成

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: 18812958

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: 18812958

Country of ref document: EP

Kind code of ref document: A1