WO2018166487A1 - 日程处理方法、装置、系统及存储介质 - Google Patents

日程处理方法、装置、系统及存储介质 Download PDF

Info

Publication number
WO2018166487A1
WO2018166487A1 PCT/CN2018/079076 CN2018079076W WO2018166487A1 WO 2018166487 A1 WO2018166487 A1 WO 2018166487A1 CN 2018079076 W CN2018079076 W CN 2018079076W WO 2018166487 A1 WO2018166487 A1 WO 2018166487A1
Authority
WO
WIPO (PCT)
Prior art keywords
schedule
information
event
participating
present application
Prior art date
Application number
PCT/CN2018/079076
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 WO2018166487A1 publication Critical patent/WO2018166487A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/33—Querying
    • G06F16/3331—Query processing
    • 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

Definitions

  • the present application relates to the field of Internet application technologies, and in particular, to a schedule processing method, apparatus, system, and storage medium.
  • Schedule management refers to the arrangement of work and things with a clear time, in a calendar or memo, and reminders in a timely manner, which may involve a single schedule or a multi-person schedule.
  • the participants of the schedule are the ones who created the user.
  • the participants of the schedule include the creator of the schedule, and other participants who complete the events in the schedule in conjunction with the creator of the schedule.
  • many users use the calendar management application in their work and life to initiate a multi-person participation schedule and notify all participants of the schedule. For example, a meeting or an exam.
  • the embodiment of the present application provides a schedule reminding method, including:
  • the embodiment of the present application further provides a schedule processing method, which is applied to a schedule server, and the method includes:
  • the embodiment of the present application further provides a schedule processing system, including: a first terminal device, a second terminal device, a schedule server, and an instant messaging server:
  • the schedule server adds the identifier of each participant to the participant object information of the first schedule corresponding to the identifier of the first schedule, obtains a second schedule reminder event, and generates an instant by using the second schedule reminder event Transmitting the instant messaging message and the identifier of each participating object to the instant messaging server;
  • the instant messaging server sends the instant messaging message to a second terminal device corresponding to each participating object.
  • the embodiment of the present application further provides a schedule processing apparatus, including: a processor, a memory connected to the processor; and the memory storing machine readable instructions, where the machine readable instructions are Configure to do the following by the owning processor:
  • the embodiment of the present application further provides a schedule processing apparatus, including: a processor, a memory connected to the processor; and the memory storing machine readable instructions, where the machine readable instructions are Configure to do the following by the owning processor:
  • the embodiment of the present application further provides a non-transitory computer readable storage medium, wherein the storage medium stores machine readable instructions, where the machine readable instructions are executable by a processor to complete the above Said method.
  • 1A is a system architecture diagram related to the present application
  • 1B is a schematic flowchart of a schedule processing method provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a set of participating objects provided by an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of determining a first schedule reminding event to be shared according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of an interface for displaying a schedule reminder event according to an embodiment of the present application.
  • FIG. 5 is another schematic diagram of an interface for displaying a schedule reminder event according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of obtaining a specified set of participating objects according to an embodiment of the present application.
  • FIG. 7(a) is a schematic diagram of an interface for displaying a candidate participation object set provided by an embodiment of the present application
  • FIG. 7(b) is a schematic diagram of an interface of a participant in a set of candidate participation objects provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of an interface of detailed information of a second schedule reminding event provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of an interface for sending a second schedule reminding event to a specified set of participating objects according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of an interface for displaying detailed information of a second schedule reminding event according to an embodiment of the present application
  • FIG. 11 is a schematic flowchart of a third generation manner of a schedule reminding event provided by an embodiment of the present application.
  • step 1101 is a schematic flow chart of an implementation of step 1101 provided by the present application.
  • FIG. 13 is another schematic flowchart of a third generation manner of a schedule reminding event provided by an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a guide creation entry provided by an embodiment of the present application.
  • 15 is a schematic diagram of a creation window of a schedule provided by an embodiment of the present application.
  • step 16 is a schematic flowchart of an implementation manner of step 1103 provided by the present application.
  • 17 is another schematic diagram of a creation window of a schedule provided by an embodiment of the present application.
  • FIG. 18 is another schematic flowchart of a third generation manner of a schedule reminding event provided by an embodiment of the present application.
  • FIG. 19 is another schematic diagram of an interface for displaying a schedule reminder event according to an embodiment of the present application.
  • FIG. 20 is a functional block diagram of a schedule processing apparatus according to an embodiment of the present application.
  • FIG. 21 is a functional block diagram of a schedule obtaining unit according to an embodiment of the present application.
  • FIG. 22 is a schematic flowchart of a schedule processing method according to an embodiment of the present application.
  • 23 is a message interaction diagram of a schedule processing method provided by an embodiment of the present application.
  • FIG. 24 is a system architecture diagram of an embodiment of the present application.
  • first, second, etc. may be used to describe the calendar reminder event in embodiments of the present application, these calendar reminder events should not be limited to these terms. These terms are only used to distinguish calendar reminder events from each other.
  • first calendar reminder event may also be referred to as a second calendar reminder event without departing from the scope of the embodiments of the present application.
  • second calendar reminder event may also be referred to as a first calendar reminder event.
  • the word “if” as used herein may be interpreted as “when” or “when” or “in response to determining” or “in response to detecting.”
  • the phrase “if determined” or “if detected (conditions or events stated)” may be interpreted as “when determined” or “in response to determination” or “when detected (stated condition or event) “Time” or “in response to a test (condition or event stated)”.
  • the system architecture diagram of the present application includes a plurality of terminal devices 1001a to 1001n, a network 1002, a schedule server 1003, and a social server 1004.
  • the terminal devices 1001a to 1001n are connected to the schedule server 1003 and the social server 1004 via the Internet.
  • the social server 1004 can provide social services to the terminal device.
  • the schedule server can provide storage and maintenance services for the user schedule to the terminal device.
  • the terminal devices 1001a to 1001n may provide social services for respective users, for example, receiving and receiving instant communication messages, conducting voice chats with contacts, video chats, and the like.
  • the terminal devices 1001a to 1001n can provide schedule reminder services for respective users, such as creating a schedule, modifying a schedule, deleting a schedule, scheduling reminders, and the like.
  • the functions of the terminal devices 1001a to 1001n may be implemented by dedicated hardware circuits or dedicated chips, or may be implemented by program instructions. The following describes the method of the embodiments in the terminal running in the terminal device as an example.
  • the client may edit the participants of the schedule by sharing the calendar into the social communication session.
  • the client can determine the schedule to be edited and the participants to be added according to the user's operation.
  • the client can display the schedule control on an interactive interface for inter-user communication (eg, a one-to-one chat window, a group chat window, etc.).
  • One or more schedules in the current schedule list are displayed in response to operations on the schedule control.
  • the schedule selected by the client user is used as the schedule to be edited, and one or more contacts corresponding to the current interaction interface are determined as participants who need to be added to the schedule.
  • the user's social contact list and/or the currently existing session list is displayed.
  • the client determines the current schedule as the schedule to be edited, and determines one or more contacts selected by the user or one or more contacts corresponding to the session selected by the user as needing to be added. Participants to the schedule.
  • the client After determining the schedule to be edited and the participants to be added according to the user's operation, the client can implement the editing of the schedule participants and the sharing of the schedule in various ways.
  • the client may join one or more contacts corresponding to the interaction interface to the participants of the schedule, thereby generating a modified schedule, and sending the modified schedule to the schedule server for saving.
  • the sharing of the schedule can be completed by the client or by the schedule server.
  • the client may send the information of the schedule, such as the identifier of the schedule, as the interaction information with the determined one or more contacts to the client corresponding to the one or more contacts through the social server.
  • the schedule server detects the modification to the schedule participant, the information of the schedule and the information of the added or all participants may be sent to the social server, and the information of the schedule is sent by the social server to the schedule server.
  • the client corresponding to the participant.
  • the client may send the information of the one or more contacts corresponding to the interaction interface and the information of the schedule to the schedule server, and modify the schedule by the schedule server, and join the one or more contacts to the schedule. Participants.
  • the calendar server may provide the modified schedule to the client corresponding to each participant of the schedule.
  • the schedule server may send the information of the modified schedule and the information of the added or all participants to the social server, and the information of the schedule is sent by the social server to the client corresponding to the participant specified by the schedule server.
  • the client may present information of one or more calendars selected by the user as interaction information in the current interaction interface, thereby prompting the user that the schedule has been edited and shared to the selected contact.
  • the schedule information may be used to acquire and display the data of the schedule from the schedule server, and (according to the user's instruction) join the schedule of the account corresponding to the client.
  • the schedule server may be used to acquire and display the data of the schedule from the schedule server, and (according to the user's instruction) join the schedule of the account corresponding to the client.
  • the first terminal device transmits the identifier of the schedule, the identifier of the participant of the schedule to the schedule server.
  • the schedule server is provided with a schedule database in which each schedule on each client is stored, and the schedule server finds a corresponding schedule in the schedule database based on the identifier of the received schedule, and searches according to the identifier of the participant.
  • the participant information of the schedule is revised.
  • the sharing of the schedule may be completed by the first terminal device, that is, the first terminal device modifies the participant information of the schedule according to the identifier of the participant, and the modification is performed.
  • the post schedule is sent to the schedule server.
  • the schedule server After receiving the identifier of the schedule to be shared and the identifier of the participant, or after receiving the modified schedule, the schedule server generates an interactive message of the schedule sharing according to the brief information of the schedule (for example, the theme + time of the schedule), and The interaction message and the identifier of each participant of the schedule are sent to the social server 1004, and the social server 1004 sends the interaction message to the second terminal device corresponding to the identifier of each participant.
  • the recipient client 1002 displays the interactive message in the dialog box, the user clicks the interactive message in the dialog box, and the second terminal device goes to the schedule server 1003 to acquire the data of the schedule and displays the detailed information of the schedule.
  • the schedule server may simultaneously send a link of the schedule to the second terminal device corresponding to the identifier of each participant, so that when the user views the schedule interface on the second terminal device, the link of the schedule is displayed on the schedule interface, and after the user clicks the link,
  • the second terminal device goes to the schedule server 1003 to acquire the data of the schedule, and displays the schedule detail information.
  • the schedule server 1003 modifies the schedule, or after receiving the modified schedule, the data of the schedule is sent to the second terminal device corresponding to the identifier of each participant, so that the second terminal device is View the details of the schedule locally.
  • each participating object needs to manually create the same schedule, and the schedule often needs to manually input information such as the theme, time, and the like, so the schedule acquisition efficiency is relatively low.
  • each participant needs to manually create a schedule separately, and the schedule creation operation is cumbersome, which reduces the efficiency of the schedule acquisition.
  • the embodiment of the present application provides a schedule processing method, which updates an agenda reminder event based on a specified set of participating objects, and then shares the updated schedule reminding event to each of the specified participating object sets. Participating in the object.
  • the embodiment of the present application provides a schedule processing method, which is applied to a terminal device, and the terminal device may be the foregoing first terminal device 1001.
  • FIG. 1B is a schematic flowchart of a schedule processing method provided by an embodiment of the present application. It can be performed by a social client on the first terminal device. As shown, the method includes the following steps:
  • the schedule reminder event can be automatically updated based on the specified set of participating objects, and then the updated schedule reminder event is automatically shared to each participating object in the specified set of participating objects, and only one participation is required.
  • the schedule reminding event can be automatically shared to other participating objects, the sharing of the schedule reminding event is realized, and the other participating objects are manually created to the same schedule, thereby solving the problem that the schedule obtaining efficiency is relatively low.
  • the following embodiments of the present application provide the following two possible implementation manners.
  • the first type first acquires a specified set of participating objects, and then determines a first schedule reminding event to be shared.
  • a schedule sharing portal is displayed in an interaction interface for performing instant communication between users; and in response to an operation instruction for the calendar sharing portal, the interaction object corresponding to the interaction object set is One or more participants as the specified set of participating objects.
  • the currently displayed set of participating objects is taken as the specified set of participating objects. For example, if an interactive interface of an interaction group or an interaction interface of a discussion group is currently displayed, all participating objects in the interaction group or all participating objects in the discussion group are used as participation in the specified participation object set.
  • the object that is, all the participating objects in the interaction group or all the participating objects in the discussion group constitute a specified participation object set, wherein some members of the interaction group may also be selected as the specified participation object collection.
  • the user can input @ ⁇ , @ ⁇ in the dialog box of the interaction group before clicking the schedule sharing entry, and then use Zhang San and Li Si as the specified participation object set.
  • FIG. 2 is a schematic diagram of a participant object set provided by an embodiment of the present application.
  • an interaction interface of an interaction group in an instant messaging tool is currently displayed, and the interaction group includes
  • the user names are three participating objects of “Leekid”, “Likid” and “ATS”, and the three participating objects constitute a currently displayed set of participating objects, that is, the three participating objects constitute the specified set of participating objects.
  • FIG. 3 is a schematic flowchart of determining a first schedule reminding event to be shared according to an embodiment of the present application.
  • determining a to-be-shared A schedule reminder event can include:
  • the schedule sharing portal is displayed in the interactive interface of the interaction group or the interaction interface of a discussion group in the instant messaging tool to which the currently participating participant object set belongs.
  • a button “schedule” 201 is displayed in the lower half of the interactive interface of the interactive group, and the button “schedule” 201 can be used as a schedule sharing entry.
  • an operation may be performed on the calendar sharing portal to trigger an operation instruction for generating a user sharing portal for the calendar. For example, as shown in FIG. 2, the user clicks on the button "schedule" displayed in the interactive interface of the interactive group, and then generates an operation instruction for the user to share the entry.
  • one or more schedule reminder events are displayed in response to an operation instruction of the user sharing the portal for the schedule.
  • FIG. 4 is a schematic diagram of an interface for displaying a schedule reminding event according to an embodiment of the present application.
  • the button “schedule” displayed in the interactive interface of the interactive group
  • Three calendar reminder events 401 are present for the user to make a selection.
  • the schedule reminding event may be stored after obtaining the schedule reminding event, so that when the display needs to be displayed, the schedule reminding event is read from the storage location.
  • a schedule reminder event in an active state such as a schedule reminder event that has not occurred and is not shared, or a schedule reminder event that has not occurred but has been shared, can be stored.
  • the user may select according to the one or more calendar reminding events, and click on the selected one or more calendar reminding events, thereby triggering the generating user to be reminded for the one or more schedules The operation instruction of the event.
  • one or more schedule reminding events selected by the user are determined, and then one or more schedule reminding events selected by the user are selected.
  • a schedule reminding event to be shared the embodiment of the present application is referred to as a first calendar reminding event, and indicates that one or more calendar reminding events selected by the user need to be shared with other users, and, in this embodiment, is in an interactive group.
  • the user selects the first and second calendar reminder events 402 among the three calendar reminder events, indicating that the two calendar reminder events need to be shared to the interactive group.
  • the currently displayed schedule reminder event is used as the first schedule reminder event. That is, the sharing of the calendar reminder event can be initiated when the calendar reminder event is displayed.
  • FIG. 5 is another schematic diagram of an interface for displaying a calendar reminder event according to an embodiment of the present application.
  • the schedule of the theme “Tonight at 7 o'clock in the Coast City” is currently displayed.
  • the schedule reminding event may be used as a reminder event to be shared, that is, a first schedule reminding event.
  • the modification operation of the schedule reminding event such as the modification of the theme information, the modification of the reminder setting, and the like, may also be received.
  • the schedule reminding event is displayed on the schedule editing interface; in response to the operation instruction for the schedule reminding event, The currently displayed schedule reminder event is used as the first schedule reminder event.
  • FIG. 6 is a schematic flowchart of obtaining a specified set of participating objects according to an embodiment of the present application.
  • an implementation manner of obtaining a specified set of participating objects may be performed. include:
  • each of the candidate participating object sets includes one or more participating objects.
  • the user may click a share button in the interface displaying the first schedule reminding event to trigger the generating user to notify the first schedule reminding event. Operation instructions.
  • one or more candidate participating object sets are displayed for the user to select.
  • each candidate participant set may include one participant object, or may also include multiple participant objects. That is to say, when there are multiple candidate participation object sets, the plurality of candidate participation object sets may include an interaction group (a plurality of participation objects in the group), or may include a single participant object. Alternatively, you can include only interactive groups, or you can include only a single participating object.
  • FIG. 7( a ) to 7 ( b ) are schematic diagrams of interfaces for displaying candidate participation object sets provided by the embodiments of the present application.
  • the names are respectively “MyGroup1”.
  • Four interaction groups 701 of "MyGroup2”, "OneOne” and "Import Test QQGroup” are available for the user to select.
  • FIG. 7(b) if the user selects a certain interaction group 702, each participating object in the interaction group may be further displayed, and the user may further select some of the participating objects or all participating objects.
  • the user may select among the one or more candidate participating object sets to trigger generating an operation instruction of the user for the candidate participating object set.
  • the one or more candidate participation object sets selected by the user are used as the specified participation object set, that is, the number of the specified participation object set may be one, or There may be many, and the embodiment of the present application does not specifically limit this.
  • the user selects the interaction of “Import Test QQ Group” in the four interaction groups 701 whose names are “MyGroup1”, “MyGroup2”, “OneOne” and “Import Test QQGroup” respectively.
  • Group 702. the interaction group further includes two participating objects 703, that is, two participating objects whose user names are “ATS” and “Likid”, and the user selects the two participating objects, and therefore, the name Specify a set of participating objects for all participating objects in the interactive group of "Import Test QQGroup".
  • step 102 For the implementation of step 102, the following embodiments of the present application provide the following possible implementation manners.
  • the first schedule reminder event is updated based on the specified set of participation objects
  • the implementation manner of obtaining the second schedule reminder event may include, but is not limited to, adding the participant object information included in the first schedule reminder event. Specifying each participating object in the set of participating objects to obtain the second schedule reminding event.
  • the first terminal device modifies the participant information of the schedule according to the specified participation object set, and generates a second schedule reminding event.
  • the second calendar reminder event can be sent to the calendar server.
  • the first terminal device may further send the identifier of the first schedule and the identifier of each participant to the schedule server, and the schedule server modifies the participant information of the schedule according to the identifier of each participant.
  • the detailed information of the first schedule reminding event may include subject information of the schedule, participation object information, time information, and location information, and the location information may be included in the topic information.
  • the participant object information of the first schedule reminding event only includes the user who initiates sharing the first schedule reminding event.
  • the schedule reminding event for the schedule reminding event to be shared, after obtaining the specified set of participating objects, indicating that the schedule reminding event is required to be shared to each participating object in the specified participating object set, and the participation of the first schedule reminding event
  • the object information only includes the user who initiated the sharing of the first schedule reminding event. Therefore, each participating object in the specified participating object set needs to be added to the participating object information of the first schedule reminding event, that is, the participation in the participating object set is specified.
  • the object needs to be the participation object information of the first schedule reminding event, thereby implementing the update of the first schedule reminding event, and the updated first schedule reminding event is referred to as the second schedule reminding event.
  • FIG. 8 is an interface diagram of detailed information of a second schedule reminding event provided by an embodiment of the present application.
  • FIG. 5 is a first schedule reminding event.
  • the interface diagram of the detailed information, the participant object information in the first schedule reminder event includes the participant object whose user name is "Leekid".
  • an interaction group named "Import Test QQGroup” is selected, which includes the participation objects "ATS” and "Likid” in addition to the current user, and then, based on FIG.
  • the two participating objects are updated to obtain a second schedule reminding event as shown in FIG. 8.
  • the participant object information in the second schedule reminding event includes a user name of “Leekid”. Participating objects 801 of "ATS" and "Likid”.
  • the method when performing the updating of the first schedule reminding event based on the specified set of participating objects to obtain the second schedule reminding event, the method includes the following steps:
  • the schedule server And sending, to the schedule server, the update data of the first schedule reminder event, where the update data includes an identifier of the first schedule reminder event and an identifier of each participant in the specified participant set to make the schedule server Adding the identifier of each participant to the participant object information of the first schedule reminder event corresponding to the identifier of the first schedule reminder event, obtaining the second schedule reminder event, and obtaining the obtained second schedule
  • the reminder event is sent to the terminal device corresponding to each participating object in the specified participating object set.
  • the schedule server modifies the schedule
  • the first terminal device sends update data to the schedule server
  • the schedule server modifies the participant information of the corresponding first schedule reminder event according to the update data to obtain a second schedule reminder event.
  • the first terminal device may modify its own schedule, or may go to the schedule server to pull the modified second schedule reminding event.
  • step 103 For the implementation of step 103, the following embodiments of the present application provide the following feasible embodiments.
  • sending the second schedule reminding event to each participating object in the specified participating object set may include, but is not limited to, the following three possible implementation manners:
  • the first type if each participating object in the specified participating object set belongs to the same specified interaction group, the second schedule reminding event may be sent to the specified interaction group, and the member of the specified interaction group includes each of the specified participating object sets. Participating in the object.
  • FIG. 9 is a schematic diagram of an interface for sending a second schedule reminding event to a specified set of participating objects according to an embodiment of the present application.
  • the reminder event 402 after updating the two schedule reminder events separately, as shown in FIG. 9, sending the updated schedule reminder event to the interaction group named "Import Test QQGroup", so that the user in the interaction group
  • the two shared calendar reminder events 901 can be obtained by the participants named "Leekid", “ATS” and "Likid”.
  • the second schedule reminding event may be separately sent to each participating object belonging to the same specified interactive group.
  • the second schedule reminding event may be sent to the specified interaction group, and the interaction is specified.
  • the members of the group include each participating object in the specified participating object set, and the second schedule reminding event is respectively sent to each participating object that does not belong to the same specified interactive group. That is, when the specified participation object set includes both an interaction group having a plurality of participation objects and a separate participation object, for the interaction group, the second schedule reminding event may be sent to the interaction group, and For a plurality of individual participants, the second calendar reminder event may be separately sent to each participating object.
  • the participating object may click the second schedule reminding event in the interactive interface to trigger the generating the second calendar reminding event. Operation instructions. As shown in FIG. 10, detailed information of the clicked second schedule reminder event is displayed in response to an operation instruction for the second schedule reminder event.
  • the schedule reminding event can be automatically updated based on the specified set of participating objects, and then the updated schedule reminding event is automatically shared to each participating object in the specified participating object set, and only one participating object acquisition schedule is required.
  • the event reminder event can be automatically shared to other participating objects, and the sharing of the calendar reminding event is realized, and the other participating objects are manually created to the same schedule, thereby solving the problem that the schedule obtaining efficiency is relatively low.
  • one or more schedule reminding events related to the display in the first embodiment of the implementation of step 101, or the second embodiment in the implementation manner of step 101 The currently displayed schedule reminder event, before displaying one or more schedule reminder events.
  • One or more schedule reminder events are available.
  • the first type generates a schedule reminder event based on the input schedule details.
  • the third as shown in Figure 11, includes:
  • each schedule reminding event may include a schedule reminding event obtained by using any one of the foregoing obtaining methods, or may include a schedule reminding event obtained by using any of the above two obtaining methods.
  • the schedule reminding event obtained by using the above three methods of obtaining may be included, which is not specifically limited in the embodiment of the present application.
  • the schedule reminder event generated by these methods is used for the user to select, and the schedule reminder event selected by the user is the schedule reminder event to be shared, and the embodiment of the present application is referred to as the first schedule reminder event. Therefore, the above three generation manners are also It can be the way the first schedule reminder event is generated.
  • the embodiment of the present application provides a feasible implementation manner.
  • step 1101 before the step 1101 is performed, whether the interaction information meets a trigger condition for generating a schedule reminder event is detected, and when the interaction information is detected to satisfy a trigger condition for generating a schedule reminder event, the response information is satisfied.
  • a trigger condition for generating a schedule reminder event is performed, and a step of collecting matching information of the schedule from the interaction information is performed (ie, step 1101).
  • the trigger condition may include at least one of the following two conditions:
  • the first, current interaction information contains the topic keywords of the schedule.
  • the interaction information in the instant messaging tool can be monitored. If the updated interaction information is detected, the updated interaction information can be used as the current interaction information, that is, the present application.
  • the second, interactive information within the specified range contains the topic keywords for the schedule.
  • the user may select the interaction information in the specified range in the interaction information record, and the interaction information in the specified range selected by the user is used as the embodiment of the present application in response to the operation instruction recorded by the user for the interaction information.
  • the specified range may also be pre-configured, and then the interaction information within the specified range may be obtained.
  • one piece of interaction information may be selected in the interaction information record, and then another piece of interaction information may be selected.
  • the two pieces of interaction information and the interaction information between the two pieces of interaction information may be used as the interaction information in the specified range.
  • a time may be selected in the interactive information record, and then a time may be selected, and each interaction information in the time period between the two times may be used as the interaction information within the specified range.
  • the interaction information of the day before the designated time is acquired, and the interaction information is used as the interaction information in the specified range. It should be understood that these are merely illustrative and are not intended to limit the implementation of the application.
  • the interaction information involved in the embodiment of the present application may include one or more of voice information, video information, and text information.
  • FIG. 12 is a schematic flowchart of an implementation of step 1101 provided by the present application. As shown in FIG. 12 , the method includes:
  • the topic keyword based on the schedule is searched in the current interaction information to obtain theme information of the schedule.
  • the search is performed in the interaction information that satisfies the trigger condition to acquire the topic information of the schedule.
  • the topic information of the schedule-based keyword is searched in the current interaction information, so that the topic information of the schedule can be obtained by, but not limited to, using the following methods:
  • the current interaction information determined by the above manner is subjected to word segmentation processing to obtain at least one candidate segmentation word.
  • the topic keywords are respectively matched with each candidate segmentation text to obtain a text matching result.
  • the target participle is obtained from each candidate participle as the subject information. Therefore, in the embodiment of the present application, the topic information of the schedule can be automatically recognized from the interaction information, thereby preventing the user from manually inputting the topic information.
  • the voice recognition technology may be used to convert the voice information into text information, and then the text information obtained after the conversion is performed. Cut word processing.
  • the voice information may be extracted from the video information, and then the voice information is converted into text information by using the voice recognition technology, and the text information obtained after the conversion is processed.
  • the interactive information is text information
  • the text information can be directly word-cutted.
  • a keyword related to the theme of the schedule may be set in advance, which is referred to as a topic keyword in the embodiment of the present application.
  • subject keywords may include, but are not limited to, one or more of a meeting, a regular meeting, a weekly meeting, a monthly meeting, a birthday, an exam, and a discussion. This is for illustrative purposes only and is not intended to limit the subject matter of the embodiments of the present application.
  • the word segmentation dictionary may be used to perform word segmentation processing on each piece of interaction information in the current interaction information, thereby obtaining at least one candidate segmentation word.
  • text similarity between the topic keyword and each candidate segmentation may be separately calculated, and each text similarity is used as a text matching result.
  • the candidate word segments may be sorted according to the order of the text similarity from large to small or from small to large, and the sorting result is obtained. According to the sorting result, the candidate participle with the largest text similarity is used as the target participle, that is, the subject information of the schedule, so that the subject information of the schedule can be obtained.
  • step 1202 if the topic information of the schedule can be obtained in the current interaction information determined above, step 1202 is performed.
  • the current interaction information for acquiring the topic information may be ignored, and the current process is ended, and the process proceeds to step 1201. For example, if there is currently an updated interaction information, and the topic keyword is not used to match the topic information of the schedule from the updated interaction information, the current process is ended, and the next update interaction occurs in the interaction window of the current instant messaging tool. At the time of the information, step 1201 is performed.
  • a dialog box may be displayed to request the user to confirm whether the schedule reminder event is automatically generated. If the user confirms yes, proceed to step 1202, if no , ends the current process and does not proceed with the next steps.
  • the current interaction information may be searched according to the attribute information of the parameter item to be collected, so as to automatically acquire other schedule-related information.
  • the parameter items to be collected ie, other schedule-related information
  • the parameter information to be collected includes the time information of the schedule, and the attribute information based on the parameter item to be collected is searched in the current interaction information, and the search result is obtained as an example: it can be based on the specified time. At least one of the format and the time keyword is searched in the current interaction information to obtain time information of the schedule. Therefore, in the embodiment of the present application, the time information of the schedule can be automatically recognized from the interaction information, thereby preventing the user from manually inputting the time information.
  • the current interaction information used in step 1201 is an updated interaction information
  • the current interaction information used in this step may be the updated interaction information, or the current interaction information used in this step may also include
  • the N pieces of interaction information before the updated interaction information and the N pieces of interaction information after the updated interaction information are not specifically limited in this embodiment of the present application.
  • the value of N may be set according to the requirement or the empirical value, and the embodiment of the present application does not specifically limit this.
  • the specified time format may include, but is not limited to, one or more of: xx/xx/xx, xx month xx, and xx:xx.
  • One or more of these time formats may be utilized for matching in the current interaction information determined above. If there is information conforming to these formats, information conforming to these formats may be extracted to obtain time information of the schedule.
  • the time keywords can include, but are not limited to, one or more of tomorrow, the next day, the morning, and the afternoon.
  • the implementation manner of finding the time information of the schedule from the current interaction information by using the time keyword is the same as the implementation manner of the topic information found in step 1101, and details are not described herein again.
  • the plurality of time information can be filtered, and a time information is obtained therefrom as the time information of the schedule. For example, one of the plurality of pieces of time information that is closest to the piece of interaction information that is queried for the subject information may be selected as the time information of the schedule.
  • step 1203 is performed.
  • the parameter information to be collected includes the participant information of the schedule, and the attribute information based on the parameter item to be collected is searched in the current interaction information, and the search result is obtained as an example: it can be based on the participation current
  • the identifiers or specified characters of each participant of the interaction are searched in the current interaction information to obtain participant information of the schedule.
  • the implementation manner of finding the participant information of the schedule from the current interaction information by using the identifier of each participant is the same as the implementation manner of the topic information found in step 1201, and details are not described herein again.
  • the identifier of the participant may be one or more of the participant's name, the user name, and the nickname, which is not specifically limited in this embodiment of the present application.
  • the schedule is only for some members of the group, so the schedule initiator may mention this part of the member in the interactive information, such as input "@ ⁇ , @ ⁇ , tomorrow morning at 10:00 am
  • the interactive information is such that the character "@” can be used to search in the current interactive information, and the information after "@" is extracted as the participant information.
  • the parameter information to be collected includes the location information of the schedule as an example, and the attribute information based on the parameter item to be collected is searched in the current interaction information, and the search result is obtained as an example: the location format information and the location may be used.
  • the keyword is searched in the current interaction information to obtain location information of the schedule.
  • the location format information and location keywords are: number + conference room and number + classroom, etc., so you can use the characters “number + conference room” and "digital + classroom” to find in the current interaction information, and extract the matching Information, as location information of the schedule.
  • the multiple information may be searched in parallel, or may be sequentially searched in the order of the present application.
  • the search method is not particularly limited, and the search order in the order of sequential search is not limited.
  • step 303 may be continued.
  • the current interaction information is determined based on the attribute information of the parameter item to be collected, and other information related to the schedule is not found in the current interaction information, the current current information for acquiring other information related to the schedule may be ignored. The information is exchanged, and the current process is ended. Then, when the next time the interaction information is acquired, step 1201 is performed to continue to acquire the topic information of the schedule.
  • step 1201 is performed.
  • step 1203 the following two feasible implementations are provided in the embodiment of the present application:
  • the first type, the subject information and the search result of the obtained schedule are directly used as the matching information of the schedule.
  • the subject information and the search result of the schedule are stored in a specified format to obtain the matching information.
  • the subject information and the search result of the schedule may be stored by using a data format.
  • the data format of the subject information and time information of the storage schedule is as follows:
  • the themeMessage field indicates the interaction information of the topic information matching the schedule
  • the themeRange field indicates the location interval of the matched topic information in the interaction information, where "10" indicates that the matched topic information is The position of the start character in the interactive information is the beginning of the 10th character, and "9” indicates that the character length of the matched topic information is 9 characters.
  • the content in the timeResult represents the time information of the matched schedule, wherein timeMessage represents the interaction information of the time information matching the schedule, and the timeRange field represents the location interval of the matched time information in the interaction information, wherein “5” indicates a match
  • timeMessage represents the interaction information of the time information matching the schedule
  • timeRange field represents the location interval of the matched time information in the interaction information
  • “5” indicates a match
  • the subject information to be obtained starts from the 5th character in the position of the start character in the interaction information
  • “6” indicates that the character length of the matched time information is 6 characters
  • the time field indicates the content of the matched time information. That is, March 6, 2017.
  • the corresponding field can be parsed from the data structure to obtain matching information, and then the matching information is quickly filled in to be filled in. Information is assigned to achieve the goal of quickly generating a schedule reminder event.
  • the instant messaging tool running in the background of the terminal, there is no running in the foreground, but the instant messaging tool still performs the above topic information and the search result when the background running, waiting for the instant communication tool to convert After the foreground is run, it is triggered to generate a schedule reminder event. Therefore, the topic information and the search result of the schedule need to be stored, and a schedule reminder event is generated when the condition is satisfied.
  • the instant messaging tool is combined with the schedule management, and the matching information of the schedule can be automatically collected in the interactive message, and the schedule reminding event is automatically generated, thereby realizing the function of automatically and quickly creating the schedule, and the prior art.
  • the cumbersome operation caused by the manual operation by the user is avoided, the operation cost is reduced, and the schedule generation efficiency is improved to some extent.
  • FIG. 13 is another schematic flowchart of a third generation manner of a schedule reminding event according to an embodiment of the present application. As shown in FIG. 13 , in a feasible implementation, before step 1102 , It can also include the following steps:
  • a corresponding flag bit may be set, and the flag bit is used to identify whether the information stored in the data structure has been used to generate a schedule reminding event. For information in the data structure that has been used to generate the calendar reminder event, there will be no need to regenerate the calendar reminder event, and for the information in the data structure that is not used to generate the calendar reminder event, it is subsequently required to generate a calendar reminder event.
  • the flag bits can be used to determine which of the data structures need to generate a calendar reminder event, and then step 1102' and subsequent steps in Figure 13 are performed.
  • the data structure may be deleted for information in a data structure that has been used to generate a calendar reminder event, for information in a data structure that is not used to generate a calendar reminder event, Save it.
  • step 1102' and subsequent steps in Fig. 13 can be performed.
  • a guide creation entry may be displayed for requesting the user. It is selected whether to generate a schedule reminder event, and then a step of acquiring a creation window template of the schedule is executed in response to the user's operation instruction for the guide creation entry.
  • FIG. 14 is a schematic diagram of a boot creation portal provided by an embodiment of the present application.
  • a boot creation portal 1401 may be displayed in a pop-up window in an interactive window of an instant messaging tool, and the boot creation portal 1401 may be Contains prompt information, such as "Do you want to create a schedule reminder event?", and can also include the user's action buttons, such as the button "Yes” and the button “No", the user can click on one of the two buttons. When the user clicks the button "Yes", an operation instruction for generating a user-created entry 1401 for the boot may be triggered.
  • prompt information such as "Do you want to create a schedule reminder event?"
  • buttons such as the button "Yes" and the button “No”
  • an operation instruction for generating a user-created entry 1401 for the boot may be triggered.
  • the example is merely illustrative and is not intended to limit the implementation of the guide creation entry in the embodiment of the present application.
  • step 1102 the embodiment of the present application provides a feasible implementation manner herein.
  • the creation window template of the schedule may be stored in advance in a specified storage location in the device in which the execution subject of step 1102 is located. After the user creates an operation instruction for the portal for the boot, the creation window template of the schedule is read from the specified storage location. Specifically, the creation window template read out from the specified storage location includes a plurality of information to be filled out.
  • the creation window template of the schedule may be implemented by using page code, and the page code of the creation window template of the implementation schedule is stored in the specified storage location. Further, the client or the browser may render the page code of the creation window template that implements the schedule based on the page template to display the creation window of the schedule.
  • FIG. 15 is a schematic diagram of a creation window of a schedule provided by an embodiment of the present application.
  • the information to be filled in the creation window includes: topic information, time information, location information, and participants. information.
  • step 1103 the embodiment of the present application provides a feasible implementation manner.
  • FIG. 16 is a schematic flowchart of the implementation of the step 1103 provided by the present application. As shown in FIG. 16 , the method includes:
  • each information to be filled in can have an attribute name and a corresponding attribute value, and can be searched in the matching information by using the attribute name of the information to be filled in to obtain the attribute value of the information to be filled out.
  • the attribute names of the information to be filled in the creation window shown in FIG. 15 such as the theme, time, location, and participant may be used to search in the matching information, respectively.
  • the corresponding information to be filled is assigned by using the found matching information.
  • the matching information corresponding to the attribute information (such as the attribute value of the information to be filled in) is found in the matching information
  • the information to be filled can be assigned by using the found matching information, that is, the found information is about to be found.
  • the matching information is used as the attribute value of the information to be filled out.
  • the attribute of the information to be filled out is named “topic”, and the matching information includes the topic information "weekly meeting” of the schedule previously collected from the interactive information, and therefore, according to the attribute name in the matching information You can find the matching information "Weekly Meeting", and then use the "Weekly Meeting” as the attribute value corresponding to the "Subject", indicating that the theme of this schedule is a weekly example.
  • the attribute of the information to be filled in is named “place”, and the matching information includes the location information “2004 conference room” of the schedule previously collected from the interaction information. Therefore, the corresponding information is found in the matching information according to the attribute name.
  • the matching information is "2004 conference room”, and then "2004 conference room” is used as the attribute value corresponding to "place”, indicating that the location of the schedule is in the 2004 conference room.
  • the default information is used to assign the corresponding information to be filled in or maintain the unfilled state of the corresponding information to be filled out.
  • the default information may be read and then utilized.
  • the default information assigns the corresponding pending information.
  • the unfilled state of the corresponding information to be filled may also be maintained, that is, the attribute value of the information to be filled out is temporarily empty.
  • the default information corresponding to each to-be-filled information may be pre-stored in advance in the device where the execution subject of step 1103 is located, so that if the information related to the schedule cannot be identified from the interaction information, such as
  • the pre-stored default information can be read by time information, location information, or participant information.
  • FIG. 17 is another schematic diagram of a creation window of a schedule provided by an embodiment of the present application.
  • the information to be filled in the information to be filled, only the attribute corresponding to the “topic” is obtained in the matching information.
  • the values of the "weekly meeting” and the "time” correspond to the attribute value "10:00-10:30 on December 18", and other information to be filled, such as "place” and "participant", have not obtained the corresponding matching information.
  • FIG. 17 is another schematic diagram of a creation window of a schedule provided by an embodiment of the present application.
  • the unfilled state can be maintained, and the attribute value in the creation window template is temporarily not empty; for the information “participant” to be filled in, the default information can be read, that is, The default information is all members in the current group, and all members in the current group are attribute values of "participants", which are filled in the creation window template of the schedule.
  • FIG. 18 is another schematic flowchart of a third generation manner of a schedule reminding event according to an embodiment of the present application. As shown in FIG. 18, in a feasible implementation, after step 1103, It can also include the following steps:
  • FIG. 19 is another schematic diagram of an interface for displaying a calendar reminding event according to an embodiment of the present application.
  • a calendar reminding event after generating a calendar reminding event, it may be in an interactive window of an instant messaging tool.
  • the schedule window 1901 is popped up, and the schedule reminder event is displayed in the schedule window 1901, and the user can operate on the displayed schedule reminder event.
  • the user performs the information in the schedule reminding event in the schedule window. Modify, or, if there is no problem with the information, the user can also not modify it. For example, as shown in FIG. 19, the user can modify the subject information, the time information, and the participant information in the displayed schedule reminder event.
  • the information to be filled in is empty, and the user can fill in the schedule window.
  • the filling may not be completed, and the unfilled state of the information to be filled is still maintained.
  • the content of the information to be filled out will not be included in the prompt information.
  • the "place" in the displayed schedule reminder event is in an unfilled state; as shown in Fig. 19, the user inputs the "place" information, that is, the 2004 conference room.
  • the user may trigger an operation instruction for generating the user for the schedule reminder event. For example, as shown in FIG. 19, the user may click a "Done" button in the schedule window 1901 to trigger an operation instruction for generating a user for the schedule reminder event, and in response to an operation instruction of the user for the schedule reminder event, the schedule is The reminder event is stored to the specified storage location, and when the schedule reminder event needs to be shared, it can be read and presented from the specified storage location.
  • the two or more schedule reminding events it is detected whether there is a schedule conflict; when it is detected that there is a schedule conflict, the prompt information is output.
  • the time information in each of the two calendar reminder events may be extracted, and then the extracted time information is compared to detect whether there is a time conflict, such as whether The time is crossed. If there is a time conflict, it is considered that there is a schedule conflict, and the prompt information needs to be output.
  • the time information in the schedule reminder event A is 9:00-11:00 on March 14, and the time information in the schedule reminder event B is 10:00-10:30 on March 14, and the time information is considered to exist. cross.
  • the prompt information is used to prompt the user to have a schedule conflict, so that the user can know the schedule conflict in time, and modify the schedule reminding event.
  • steps in this embodiment may be for each schedule reminding event shared by the sharer of the participating object schedule reminding event, or may be for obtaining a schedule reminding event from the sharer (referred to as the first in the present application)
  • the two schedule reminders of the participants of the second schedule reminder event may be for each schedule reminding event shared by the sharer of the participating object schedule reminding event, or may be for obtaining a schedule reminding event from the sharer (referred to as the first in the present application)
  • the two schedule reminders of the participants of the second schedule reminder event may be for each schedule reminding event shared by the sharer of the participating object schedule reminding event, or may be for obtaining a schedule reminding event from the sharer (referred to as the first in the present application)
  • the two schedule reminders of the participants of the second schedule reminder event may be for each schedule reminding event shared by the sharer of the participating object schedule reminding event, or may be for obtaining a schedule reminding event from the sharer (referred to as the first in the present application)
  • the modification information for the second schedule reminding event may also be acquired; and then, according to the modified information, the participating objects are obtained.
  • the second schedule reminding event is modified.
  • the modification information may include at least one of theme information, time information, location information, and participant object information of the second schedule reminding event.
  • the participant object of the second schedule reminding event wants to modify the second schedule reminding event, or when there is a schedule conflict, the second schedule reminding event may be modified, so that the The second schedule reminds the event to modify the information.
  • the sharer of the second schedule reminding event may initiate the modification, or may be the participant of the second schedule reminding event to initiate the modification.
  • each participating object in the second schedule reminding event is determined, and then the modification information is sent by the server to the client used by each participating object, so that each participating object The used client modifies the second schedule reminding event received by each according to the modification information.
  • the embodiment of the present application further provides an apparatus embodiment for implementing the steps and methods in the foregoing method embodiments.
  • FIG. 20 is a functional block diagram of a schedule processing apparatus according to an embodiment of the present application. As shown, the device includes:
  • a first obtaining unit 100 configured to determine a first schedule reminding event to be shared
  • a second obtaining unit 200 configured to acquire a specified set of participating objects
  • the schedule update unit 300 is configured to update the first schedule reminding event based on the specified set of participating objects to obtain a second schedule reminding event;
  • the schedule sharing unit 400 is configured to send the second schedule reminding event to each participating object in the specified participating object set.
  • the second obtaining unit 200 is specifically configured to: use the currently displayed participating object set as the specified participating object set;
  • the first obtaining unit 100 is specifically configured to:
  • a schedule reminder event to be shared is determined as the first schedule reminder event in response to an operation instruction for the one or more schedule reminder events.
  • the first obtaining unit 100 is specifically configured to: use the currently displayed schedule reminding event as the first schedule reminding event;
  • the second obtaining unit 200 is specifically configured to:
  • each of the candidate participating object sets includes one or more participating objects
  • a specified set of participating objects is determined in response to an operational instruction for the set of candidate participating objects.
  • the schedule updating unit 300 is specifically configured to: add, in the participation object information included in the first schedule reminding event, each participating object in the specified participating object set, to obtain the first Second schedule reminder event.
  • the schedule sharing unit 400 is specifically configured to: send the second schedule reminding event to a specified interaction group, where the member of the specified interaction group includes the specified participation object set Participating participants.
  • the schedule sharing unit 400 is specifically configured to: send the second schedule reminding event to each participating object in the specified participating object set.
  • the device further includes:
  • the schedule obtaining unit 500 is configured to obtain one or more schedule reminding events.
  • the schedule obtaining unit 500 is specifically configured to: generate the schedule reminding event according to the schedule detailed information input by the user.
  • the schedule obtaining unit 500 is specifically configured to: acquire a calendar reminding event shared by other users.
  • the schedule obtaining unit 500 further includes:
  • the information collection module 501 is configured to collect matching information of the schedule from the interaction information.
  • a template obtaining module 502 configured to acquire a creation window template of a schedule
  • the schedule generation module 503 is configured to configure the information to be filled in the created window template according to the matching information of the schedule to generate a schedule reminding event.
  • the schedule generating module 503 is specifically configured to:
  • the matching information to be filled is used to assign a value to be filled
  • the corresponding information to be filled in is assigned by the default information or the corresponding unfilled state of the information to be filled is maintained.
  • the schedule obtaining unit 500 further includes:
  • a first display module 504 configured to display a boot creation portal
  • the template obtaining module 502 is specifically configured to: execute a creation window template of acquiring a schedule in response to an operation instruction for creating an entry for the guidance.
  • the information collection module 501 is specifically configured to: perform, in response to the interaction information satisfying a trigger condition for generating a schedule reminder event, perform matching information of collecting a schedule from the interaction information.
  • the triggering condition includes:
  • the current interaction information includes the topic keywords of the schedule; and/or,
  • the interactive information within the specified range contains the topic keywords of the schedule.
  • the information collection module 501 is specifically configured to:
  • the matching information is determined according to the topic information of the schedule and the search result.
  • the information collection module 501 is configured to perform a search in the interaction information that satisfies the trigger condition based on the topic keyword of the schedule, to obtain the topic information of the schedule, specifically used for :
  • a target participle is obtained from each candidate participle as the subject information.
  • the information collecting module 501 is configured to perform text matching between the topic keywords and each candidate word segment to obtain a text matching result, and specifically used to: separately calculate topic keywords and each The text similarity of the candidate participle as the text matching result;
  • the information collecting module 501 is configured to: when obtaining the target word segmentation from each candidate participle based on the text matching result, specifically: acquiring the candidate word segment with the largest text similarity as the target word segment.
  • the parameter item to be collected includes time information of the schedule
  • the information collection module 501 is configured to perform interaction on the trigger condition based on attribute information of the parameter item to be collected. The information is searched and used to find the result:
  • the information collecting module 501 is configured to: when determining the matching information according to the theme information of the schedule and the search result, specifically, to: target the calendar in a specified format The information and the search result are stored to obtain the matching information.
  • the number of the schedule reminding events is two or more; the device further includes:
  • the conflict detecting unit 600 is configured to detect whether there is a schedule conflict according to the two or more schedule reminding events;
  • the conflict prompting unit 700 is configured to output prompt information when it is detected that there is a schedule conflict.
  • the device further includes:
  • the information obtaining unit 800 is configured to acquire modification information for the second schedule reminding event
  • the modifying synchronization unit 900 is configured to modify the second schedule reminding event obtained by each participating object according to the modification information
  • the modification information includes at least one of theme information, time information, location information, and participant object information of the second schedule reminding event.
  • each unit in this embodiment can perform the method shown in FIG. 1 to FIG. 19, and the parts not described in detail in this embodiment, reference may be made to the related description of FIG. 1 to FIG.
  • the application also provides a schedule processing method, which is applied to a schedule server, as shown in FIG. 22, the method includes the steps of:
  • S2201 Receive a modification instruction of the first terminal device to the participant of the first schedule, where the modification instruction includes an identifier of the first schedule and a specified participation object set, where the specified participation object set includes one or more participation The identity of the object;
  • S2202 Add the identifier of each participating object to the participant object information of the first schedule corresponding to the identifier of the first schedule, and obtain a second schedule reminding event;
  • S2203 Generate an instant communication message by using the second schedule reminding event
  • S2204 Send the instant messaging message and the identifier of each participating object to the instant messaging server, so that the instant messaging server sends the instant messaging message to the second terminal device corresponding to each participating object.
  • the schedule is modified and stored by the schedule server.
  • the schedule server simultaneously generates an instant communication message according to the second schedule reminding event.
  • the instant communication message is generated according to the summary information of the second schedule reminding time, for example, generating an instant communication message according to the subject and time information of the schedule.
  • the second terminal device goes to the calendar server to acquire the data of the schedule, thereby displaying the detailed information of the schedule.
  • the schedule server may also actively send the data of the second schedule reminding time to the second client of the participating object, so that when the user clicks on the instant messaging message, the data of the local second calendar reminding event is acquired, and the detailed information of the schedule is displayed. .
  • the participants of the schedule realize the sharing of the schedule through the social application, and the participants of the schedule are prevented from manually creating the same schedule, respectively, and the schedule acquisition efficiency is provided.
  • the schedule reminder event can be automatically updated based on the specified set of participating objects, and then the instant communication message corresponding to the schedule is transmitted to the terminal device of each participating object, and the schedule is made by the schedule server and the social server.
  • the participants realize the sharing of the schedule through the social application, and avoid the participants of the schedule to manually create the same schedule, and provide the schedule acquisition efficiency.
  • the schedule processing method provided by the present application further includes the steps of:
  • the second terminal device when the user corresponding to the second terminal device operates the instant messaging message, for example, the instant messaging message is displayed in the dialog box of the sender and the receiver, and when the recipient clicks the instant messaging message, the second terminal device (specifically, the social client on the second terminal device) acquires data of the schedule from the schedule server, and displays the detailed information of the schedule based on the acquired data.
  • the second terminal device specifically, the social client on the second terminal device
  • the schedule processing method provided by the present application further includes the following steps:
  • the schedule data of each second terminal device is maintained in the schedule server, and the schedule server adds the second schedule data to the schedule data of each second terminal device, and then transmits the second terminal device corresponding to each second terminal device.
  • a link of the two schedule data in which a link of each schedule is displayed in a schedule interface in the social application client on each terminal device.
  • the schedule server acquires the schedule data of the schedule, and then displays the detailed information of the schedule.
  • the second terminal device goes to the schedule server to pull the data of the schedule, and the schedule server can also actively send the data of the schedule to the second terminal device.
  • the modifying the command further includes: receiving the identifier of the shared user corresponding to the first terminal device;
  • the method includes the following steps:
  • the instant messaging message is transmitted as the interaction information of the group of all participating objects of the schedule. Therefore, after receiving the instant messaging message, the second terminal device corresponding to each participating object displays the instant messaging message in the dialog box of the group.
  • the instant messaging message sent to each second terminal device is used as an interaction message between the user corresponding to the first terminal device and the user corresponding to the second terminal device, so that the second terminal device after receiving the instant messaging message
  • the instant messaging message is displayed in a dialog box of a user (schedule sender) corresponding to the first terminal device.
  • the present application also provides a schedule processing system, including: a first terminal device, a second terminal device, a schedule server, and an instant messaging server, where
  • the schedule server adds the identifier of each participant to the participant object information of the first schedule corresponding to the identifier of the first schedule, obtains a second schedule reminder event, and generates an instant by using the second schedule reminder event Transmitting the instant messaging message and the identifier of each participating object to the instant messaging server;
  • the instant messaging server sends the instant messaging message to a second terminal device corresponding to each participating object.
  • the schedule server receives the acquisition request of the second schedule reminder event sent by the second terminal device corresponding to the identifier of the instant messaging message, and the second terminal device corresponding to the identifier of the instant messaging message The data of the second schedule reminding event is sent to the second terminal device.
  • the schedule server adds the second schedule reminder event to the schedule data of the participant object corresponding to the second terminal device.
  • the first terminal device further sends an identifier of the shared user corresponding to the first terminal device to the schedule server;
  • the schedule server sends the instant communication message, the identifier of each participating object, and the identifier of the shared user to the instant messaging server;
  • the instant messaging server sends the instant messaging message as an interaction message of the group that includes the shared user and the participant object to the second terminal device corresponding to each participant.
  • the message interaction diagram of the schedule processing method provided by an example of the present application is as shown in FIG. 23, and mainly includes the following steps:
  • the first client (the social client on the first terminal device) acquires a first schedule (to be shared), and specifies a set of participating objects.
  • the first client sends a modification instruction of the first schedule to the schedule server, where the modification instruction carries the identifier of the first schedule, the identifier of each participating object, and the identifier of the shared user.
  • the first client may modify the first schedule according to the specified set of participation objects to obtain the second schedule.
  • the schedule server modifies the first schedule according to the modification instruction to obtain a second schedule.
  • the corresponding schedule is found according to the identifier of the first schedule in the modification instruction, and the identifier of each participating object is added to the found one.
  • the second schedule is obtained.
  • S2304 Add the second schedule to the schedule data of each participating object.
  • the schedule server maintains one schedule data for each user corresponding to the terminal device, and adds the second schedule to the schedule data corresponding to the identifier of each participant object according to the identifier of each participant object of the first schedule.
  • the schedule server generates an instant communication message according to the information of the second schedule, where the instant communication message includes summary information of the second schedule, for example, a theme, a time, and the like.
  • S2306 Send the instant messaging message, the identifier of each participating object, and the identifier of the shared user to the social server.
  • the social server sends the instant messaging message as an interaction message of the user sharing the user with the second terminal device.
  • the second terminal device displays the instant messaging message in a dialog box of the user sharing the user corresponding to the second terminal device.
  • the social server sends the instant messaging message as an interactive message of the interaction group of each participating object.
  • the social client on the second terminal device displays the instant messaging message in a dialog box of the interactive group.
  • S2309 Acquire data of the second schedule to the schedule server in response to the operation of the interactive message.
  • the user corresponding to the second terminal device can click the instant messaging message in the dialog box, and the second terminal device requests the data of the second schedule from the schedule server. Further, the detailed information of the second schedule is displayed on the second terminal device.
  • the schedule server sends a link of the second schedule to the second terminal device corresponding to each participant.
  • S2311 The second terminal device displays a link of the second schedule on the schedule interface thereon.
  • the second terminal device requests data of the second schedule from the schedule server in response to the user's operation of the link of the second schedule.
  • the schedule server then transmits the data of the second schedule to the second terminal device, and the social client on the second terminal device displays the detailed information of the second schedule.
  • the application also provides a non-transitory computer readable storage medium, wherein the storage medium stores machine readable instructions that are executable by a processor to perform the methods described above.
  • Figure 24 is a diagram showing the composition of a computing device in which the schedule processing device is located.
  • the computing device includes one or more processors (CPUs) 2402, communication modules 2404, memories 2406, user interfaces 2410, and a communication bus 2408 for interconnecting these components.
  • processors CPUs
  • communication modules 2404 communication modules 2404
  • memories 2406 communication modules 2404
  • user interfaces 2410 user interfaces 2410
  • a communication bus 2408 for interconnecting these components.
  • the processor 2402 can receive and transmit data through the communication module 2404 to effect network communication and/or local communication.
  • User interface 2410 includes one or more output devices 2412 that include one or more speakers and/or one or more visual displays.
  • User interface 1510 also includes one or more input devices 2414 including, for example, a keyboard, a mouse, a voice command input unit or loudspeaker, a touch screen display, a touch sensitive tablet, a gesture capture camera or other input button or control, and the like.
  • the memory 2406 can be a high speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state storage device; or a non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, Or other non-volatile solid-state storage devices.
  • a high speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state storage device
  • non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, Or other non-volatile solid-state storage devices.
  • the memory 2406 stores a set of instructions executable by the processor 2402, the instruction code stored in the memory being configured to be executed by the processor to implement the steps in the schedule processing method of the present application described above, while also implementing the schedule processing apparatus of the present application.
  • the memory 2406 includes:
  • An operating system 2416 including a program for processing various basic system services and for performing hardware related tasks
  • the application 2418 includes various applications for calendar processing that enable the processing flow in each of the above examples to be implemented, such as may include some or all of the units in the schedule processing device. At least one of the units may store machine executable instructions.
  • the processor 2402 can implement the steps in the schedule processing method described above by executing the machine executable instructions in the memory 2406, and also implement the functions of the modules in the schedule processing apparatus of the present application.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the software functional unit is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the methods of the various embodiments of the present application. Part of the steps.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Data Mining & Analysis (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Computational Linguistics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Calculators And Similar Devices (AREA)

Abstract

本申请实施例提供了一种日程处理方法，包括：确定待分享的第一日程提醒事件，以及，获取指定参与对象集合；基于所述指定参与对象集合对所述第一日程提醒事件进行更新，获得第二日程提醒事件；将所述第二日程提醒事件发送给所述指定参与对象集合中各参与对象。本申请还提供了相应的装置、系统及存储介质。

Description

日程处理方法、装置、系统及存储介质
本申请要求于2017年3月15日提交中国专利局、申请号为201710153906.0、申请名称为“一种日程处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及互联网应用技术领域，尤其涉及日程处理方法、装置、系统及存储介质。
背景技术
日程管理，指的是将有明确时间的工作和事物等，安排在日历或者备忘录中，以及时进行提醒，可以涉及单人日程或者多人日程。对于单人日程来说，日程的参与者为创建用户的本人。对于多人日程来说，日程的参与者包括日程的创建者，还包括与所述日程的创建者共同完成日程中的事件的其他参与者。目前，很多用户都会在工作和生活中使用日程管理类应用来发起多人参与的日程，并通知该日程的所有参与者。例如，会议或者考试等。
技术内容
一方面，本申请实施例提供了一种日程提醒方法，包括：
确定待分享的第一日程提醒事件，以及，获取指定参与对象集合；
基于所述指定参与对象集合对所述第一日程提醒事件进行更新，获得第二日程提醒事件；
将所述第二日程提醒事件发送给所述指定参与对象集合中各参与对象对应的终端设备。
另一方面，本申请实施例还提供了一种日程处理方法，应用于日程服务器，所述方法包括：
接收第一终端设备对第一日程的参与者的修改指令，其中，所述修改指令包括所述第一日程的标识和指定参与对象集合，所述指定参与对象集合包括一个或多个参与对象的标识；
将所述各参与对象的标识添加到所述第一日程的标识对应的第一日程的参与对象信息中，获得第二日程提醒事件；
利用所述第二日程提醒事件生成即时通信消息；
将所述即时通信消息及所述各参与对象的标识发送给即时通信服务器，以使所述即时通信服务器将所述即时通信消息发送给各参与对象对应的第二终端设备。
本申请实施例还提供了一种日程处理系统，包括：第一终端设备、第二终端设备、日程服务器及即时通信服务器：
所述第一终端设备向日程服务器发送第一日程的参与者的修改指令，其中，所述修改指令包括所述第一日程的标识和指定参与对象集合，所述指定参与对象集合包括一个或多个参与对象的标识；
所述日程服务器，将所述各参与对象的标识添加到所述第一日程的标识对应的第一日程的参与对象信息中，获得第二日程提醒事件；利用所述第二日程提醒事件生成即时通信消息；将所述即时通信消息及所述各参与对象的标识发送给即时通信服务器；
所述即时通信服务器，将所述即时通信消息发送给各参与对象对应的第二终端设备。
另一方面，本申请实施例还提供了一种日程处理装置，包括：处理器，与所述处理器相连接的存储器；所述存储器中存储有机器可读指令，所述机器可读指令经配置以由所属处理器执行以下操作：
确定待分享的第一日程提醒事件，以及，获取指定参与对象集合；
基于所述指定参与对象集合对所述第一日程提醒事件进行更新，获得第二日程提醒事件；
将所述第二日程提醒事件发送给所述指定参与对象集合中各参与对象对应的终端设备。
另一方面，本申请实施例还提供了一种日程处理装置，包括：处理器，与所述处理器相连接的存储器；所述存储器中存储有机器可读指令，所述机器可读指令经配置以由所属处理器执行以下操作：
接收第一终端设备对第一日程的参与者的修改指令，其中，所述修改指令包括所述第一日程的标识和指定参与对象集合，所述指定参与对象集合包括一个或多个参与对象的标识；
将所述各参与对象的标识添加到所述第一日程的标识对应的第一日程的参与对象信息中，获得第二日程提醒事件；
利用所述第二日程提醒事件生成即时通信消息；
将所述即时通信消息及所述各参与对象的标识发送给即时通信服务器，以使所述即时通信服务器将所述即时通信消息发送给各参与对象对应的第二终端设备。
另一方面，本申请实施例还提供了一种非易失性计算机可读存储介质，其中所述存储介质中存储有机器可读指令，所述机器可读指令可以由处理器执行以完成上述所述的方法。
采用本申请提高的上述方案，能够提高日程的获取效率。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是 本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其它的附图。
图1A是本申请涉及的系统架构图；
图1B是本申请实施例所提供的日程处理方法的流程示意图；
图2是本申请实施例所提供的参与对象集合的示意图；
图3是本申请实施例所提供的确定待分享的第一日程提醒事件的一种流程示意图；
图4是本申请实施例所提供的显示日程提醒事件的一种界面示意图；
图5是本申请实施例所提供的显示日程提醒事件的另一种界面示意图；
图6是本申请实施例所提供的获取指定参与对象集合的一种流程示意图；
图7(a)是本申请实施例所提供的显示候选参与对象集合的界面示意图；
图7(b)是本申请实施例所提供的显示候选参与对象集合中的参与对象的界面示意图；
图8是本申请实施例所提供的第二日程提醒事件的详细信息的界面示意图；
图9是本申请实施例所提供的将第二日程提醒事件发送给指定参与对象集合的界面示意图；
图10是本申请实施例所提供的显示第二日程提醒事件的详细信息的界面示意图；
图11是本申请实施例所提供的日程提醒事件的第三种生成方式的一种流程示意图；
图12是本申请所提供的步骤1101的实施方式的一种流程示意图；
图13是本申请实施例所提供的日程提醒事件的第三种生成方式的另一种流程示意图；
图14是本申请实施例所提供的引导创建入口的示意图；
图15是本申请实施例所提供的日程的创建窗口的示意图；
图16是本申请所提供的步骤1103的实现方式的流程示意图；
图17是本申请实施例所提供的日程的创建窗口的另一示意图；
图18是本申请实施例所提供的日程提醒事件的第三种生成方式的另一种流程示意图；
图19是本申请实施例所提供的显示日程提醒事件的另一种界面示意图；
图20是本申请实施例所提供的日程处理装置的功能方块图；
图21是本申请实施例所提供的日程获取单元的功能方块图；
图22是本申请一实施例提供的日程处理方法的流程示意图；
图23是本申请实施例提供的日程处理方法的消息交互图；以及
图24是本申请实施例设计的系统架构图。
具体实施方式
为了更好的理解本申请的技术方案，下面结合附图对本申请实施例进行详细描述。
应当明确，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其它实施例，都属于本申请保护的范围。
在本申请实施例中使用的术语是仅仅出于描述特定实施例的目的， 而非旨在限制本申请。在本申请实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
应当理解，本文中使用的术语“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应当理解，尽管在本申请实施例中可能采用术语第一、第二等来描述日程提醒事件，但这些日程提醒事件不应限于这些术语。这些术语仅用来将日程提醒事件彼此区分开。例如，在不脱离本申请实施例范围的情况下，第一日程提醒事件也可以被称为第二日程提醒事件，类似地，第二日程提醒事件也可以被称为第一日程提醒事件。
取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”或“响应于检测”。类似地，取决于语境，短语“如果确定”或“如果检测(陈述的条件或事件)”可以被解释成为“当确定时”或“响应于确定”或“当检测(陈述的条件或事件)时”或“响应于检测(陈述的条件或事件)”。
本申请涉及的系统架构图，如图1A所示，包括多个终端设备1001a～1001n、网络1002、日程服务器1003、社交服务器1004。终端设备1001a～1001n与日程服务器1003及社交服务器1004通过互联网连接。社交服务器1004可以向终端设备提供社交服务。日程服务器可以向终端设备提供用户日程的存储、维护服务。
终端设备1001a～1001n可以为各自的用户提供社交服务，例如，收发即时通信消息、与联系人进行语音聊天、视频聊天等。终端设备1001a～1001n可以为各自的用户提供日程提醒服务，例如创建日程、修 改日程、删除日程、日程提醒，等。各实施例中，终端设备1001a～1001n的功能可以由专用的硬件电路或者专用芯片实现，也可以由程序指令实现。以下以终端设备中运行的客户端执行各实施例的方法为例进行说明。
根据各实施例，客户端可以通过将日程分享到社交通信会话中来编辑日程的参与者。客户端可以根据用户的操作分别确定待编辑的日程和需要添加的参与者。例如，客户端可以在用于用户间通信的交互界面(如一对一聊天窗口、群组聊天窗口，等)上展示日程控件。响应于对日程控件的操作，展示当前日程列表中的一个或多个日程。响应于用户的选取操作，客户端用户选择的日程作为待编辑的日程，将当前交互界面对应的一个或多个联系人确定为需要添加到该日程的参与者。
又例如，在日程界面中，响应于用户对日程的操作，展示用户的社交联系人列表和/或当前存在的会话列表。响应于用户对社交联系人或会话的选择，客户端将当前日程作为待编辑的日程，将用户选择的一个或多个联系人或用户选择的会话对应的一个或多个联系人确定为需要添加到该日程的参与者。
根据用户的操作确定了待编辑的日程和需要添加的参与者后，客户端可以通过多种方式实现日程参与者的编辑和日程的分享。
例如，客户端可以将该交互界面对应的一个或多个联系人加入日程的参与者，从而生成修改后的日程，并将修改后的日程发送到日程服务器保存。之后，日程的分享可以由客户端完成，也可以由日程服务器完成。例如，客户端可以将该日程的信息，例如日程的标识等，作为与确定的一个或多个联系人之间的交互信息通过社交服务器发送给一个或多个联系人对应的客户端。又例如，日程服务器检测到对日程参与者的修改后，可以将该日程的信息和新增的或者全部参与者的信息发送给社 交服务器，由社交服务器将该日程的信息发送给日程服务器指定的参与者对应的客户端。
又例如，客户端可以将该交互界面对应的一个或多个联系人的信息和该日程的信息发送到日程服务器，由日程服务器对该日程进行修改，将该一个或多个联系人加入该日程的参与者。一些例子中，日程服务器可以将修改后的日程提供给该日程的各参与者对应的客户端。一些例子中，日程服务器可以将修改后的日程的信息和新增的或者全部参与者的信息发送给社交服务器，由社交服务器将该日程的信息发送给日程服务器指定的参与者对应的客户端。
一些实施例中，客户端可以将用户选择的一个或多个日程的信息作为交互信息展示在当前的交互界面中，从而提示用户，该日程已编辑并分享给选择的联系人。
当客户端收到其它客户端发送的作为交互信息的日程信息时，可以利用日程信息从日程服务器获取并展示该日程的数据，并(根据用户的指令)加入到本客户端对应的账户的日程表中。
例如，第一终端设备将日程的标识，日程的参与人的标识发送给日程服务器。日程服务器设置有日程数据库，日程数据库中存储有各客户端上的各日程，日程服务器根据接收到的日程的标识，在日程数据库中查找到对应的日程，根据所述参与人的标识将查找到的日程的参与人信息进行修改。在另一种方式中，客户端完成分享后，可以由第一终端设备完成对日程的分享，即，由第一终端设备根据所述参与人的标识将日程的参与人信息进行修改，将修改后的日程发送给日程服务器。
日程服务器在接收到要分享的日程的标识和参与人的标识后，或接收到修改后的日程后，根据日程的简要信息(例如，日程的主题+时间)生成日程分享的交互消息，将该交互消息及所述日程的各参与人的标识 发送给社交服务器1004，由社交服务器1004将交互消息发送给各参与人的标识对应的第二终端设备。接受方客户端1002在对话框中展示该交互消息，用户点击对话框中的交互消息，第二终端设备去日程服务器1003获取日程的数据，展示日程的详细信息。日程服务器可以同时将日程的链接发送给各参与人的标识对应的第二终端设备，从而当用户在第二终端设备查看日程界面时，在日程界面上展示日程的链接，用户点击该链接后，第二终端设备去日程服务器1003获取日程的数据，显示日程详情信息。在另一中实现方式中，当日程服务器1003修改完日程后，或者接收到修改后的日程后，将日程的数据发送给各参与人的标识对应的第二终端设备，使得第二终端设备在本地查看日程的详情信息。
在一些实例中，如果一个日程涉及多个参与对象，每个参与对象需要各自手动创建该同一日程，日程往往还需要手动输入主题、时间等信息，因此日程获取效率比较低。在该实例中，每个参与者需要手动分别创建日程，日程创建的操作比较繁琐，降低了日程的获取效率。
为解决以上技术问题，本申请实施例提供了一种日程处理方法，该方法基于指定参与对象集合对日程提醒事件进行更新，然后将更新后的日程提醒事件分享给该指定参与对象集合中的各参与对象。
在该思路的引导下，本申请实施例提供了以下可行的实施方式。
本申请实施例给出一种日程处理方法，应用于终端设备，该终端设备可以为上述第一终端设备1001，请参考图1B，其为本申请实施例所提供的日程处理方法的流程示意图，可以由第一终端设备上的社交客户端来执行，如图所示，该方法包括以下步骤：
101、确定待分享的第一日程提醒事件，以及，获取指定参与对象集合。
102、基于所述指定参与对象集合对所述第一日程提醒事件进行更 新，获得第二日程提醒事件。
103、将所述第二日程提醒事件发送给所述指定参与对象集合中各参与对象对应的终端设备。
采用本申请提供的日程处理方法，能够基于指定参与对象集合，自动对日程提醒事件进行更新，然后自动将更新后的日程提醒事件分享给该指定参与对象集合中的各参与对象，只需要一个参与对象分享日程提醒事件后，就可以自动将该日程提醒事件分享给其他参与对象，实现了日程提醒事件的分享，避免了其他参与对象各自手动创建同一日程，从而解决了日程获取效率比较低的问题。针对步骤101的实现，本申请实施例在此提供了以下两种可行的实施方式。
第一种、先获取指定参与对象集合，然后确定待分享的第一日程提醒事件。
第二种、先确定待分享的第一日程提醒事件，然后获取指定参与对象集合。
在第一种可行的实施方式中，在用于用户间进行即时通信的交互界面中显示日程分享入口；响应于针对所述日程分享入口的操作指令，将所述交互界面对应的参与对象集合中的一个或多个参与者作为所述指定参与对象集合。将当前显示的参与对象集合作为指定参与对象集合。例如，若当前显示即时通讯工具中某交互群组的交互界面或者某讨论组的交互界面，将该交互群组中的所有参与对象或者讨论组中的所有参与对象作为指定参与对象集合中的参与对象，也即，交互群组中的所有参与对象或者讨论组中的所有参与对象组成指定参与对象集合，其中，也可以选取交互群组中的部分成员作为所述指定参与对象集合。例如，用户可以在点击日程分享入口之前，在交互群组的对对话框中输入@张三、@李四，则将张三、李四作为所述指定参与对象集合。
例如，请参考图2，其为本申请实施例所提供的参与对象集合的示意图，如图2所示，当前显示了某即时通讯工具中某交互群组的交互界面，该交互群组中包含用户名分别为“Leekid”、“Likid”和“ATS”的三个参与对象，将该三个参与对象组成当前显示的参与对象集合，也即，该三个参与对象组成上述指定参与对象集合。
请参考图3，其为本申请实施例所提供的确定待分享的第一日程提醒事件的一种流程示意图，如图3所示，在第一种可行的实施方式中，确定待分享的第一日程提醒事件可以包括：
301、基于当前显示的参与对象集合，显示日程分享入口。
在当前显示的参与对象集合所属的即时通讯工具中的交互群组的交互界面或者某讨论组的交互界面中，显示日程分享入口。例如，如图2所示，在该交互群组的交互界面中下半部分显示按钮“日程”201，该按钮“日程”201可以作为日程分享入口。
302、响应于针对所述日程分享入口的所述操作指令，显示一个或多个日程提醒事件。
显示日程分享入口后，若用户需要将第一日程提醒事件分享给其他用户，可以在该日程分享入口上进行操作，以触发生成用户针对所述日程分享入口的操作指令。例如，如图2所示，用户点击该交互群组的交互界面中显示的按钮“日程”，然后生成用户针对所述日程分享入口的操作指令。
进一步的，响应于用户针对所述日程分享入口的操作指令，显示一个或多个日程提醒事件。例如，请参考图4，其为本申请实施例所提供的显示日程提醒事件的一种界面示意图，如图4所示，用户点击该交互群组的交互界面中显示的按钮“日程”之后，显示存在的三个日程提醒事件401，以供用户进行选择。
在一种可行的实施方式中，对于显示的一个或多个日程提醒事件，可以在获得日程提醒事件后，将日程提醒事件进行存储，这样，需要显示时，从存储位置中读取日程提醒事件。可以理解的是，可以存储处于有效状态的日程提醒事件，如未发生且未分享的日程提醒事件或者未发生但已分享的日程提醒事件。
303、响应于针对所述一个或多个日程提醒事件的操作指令，确定待分享的日程提醒事件，作为所述第一日程提醒事件。
显示一个或多个日程提醒事件之后，用户可以根据该一个或者多个日程提醒事件进行选择，并点击所选择的一个或者多个日程提醒事件，从而触发生成用户针对所述一个或多个日程提醒事件的操作指令。
进一步的，响应于用户针对所述一个或多个日程提醒事件的操作指令，根据该操作指令，确定用户选择的一个或者多个日程提醒事件，然后，将用户选择的一个或者多个日程提醒事件作为待分享的日程提醒事件，本申请实施例称为第一日程提醒事件，表示用户选择的一个或者多个日程提醒事件需要分享给其他用户，而且，由于本实施例中，是在某交互群组的交互界面中发起的日程分享，因此，该第一日程提醒事件需要转发给该交互群组中的各参与对象。
例如，如图4所示，用户在三个日程提醒事件中选择了第一个和第二个日程提醒事件402，表示需要将这两个日程提醒事件分享给该交互群组中用户名分别为“Leekid”、“Likid”和“ATS”的三个参与对象。
在第二种可行的实施方式中，将当前显示的日程提醒事件作为所述第一日程提醒事件。也就是说，可以在显示日程提醒事件时发起日程提醒事件的分享。例如，请参考图5，其为本申请实施例所提供的显示日程提醒事件的另一种界面示意图，如图5所示，当前显示了主题为“今晚七点在海岸城聚餐”的日程提醒事件，本实施例中，可以将该日程提 醒事件作为待分享的日程提醒事件，即第一日程提醒事件。可以理解的是，对于待分享的日程提醒事件，还可以接收对该日程提醒事件的修改操作，如对主题信息的修改、提醒设置的修改等。
在获取第一日程提醒事件及指定参与对象集合的第二种方式中，在获取第一日程提醒事件时，在日程编辑界面显示日程提醒事件；响应于针对所述日程提醒事件的操作指令，将当前显示的所述日程提醒事件作为所述第一日程提醒事件。
请参考图6，其为本申请实施例所提供的获取指定参与对象集合的一种流程示意图，如图6所示，在第二种可行的实施方式中，获取指定参与对象集合的实施方式可以包括：
601、响应于针对所述日程提醒事件的操作指令，显示一个或多个候选参与对象集合；每个所述候选参与对象集合包含一个或多个参与对象。在一种可行的实施方式中，在确定需要分享的第一日程提醒事件之后，用户可以在显示第一日程提醒事件的界面中，点击分享按钮，以触发生成用户针对所述第一日程提醒事件的操作指令。
进一步的，响应于用户针对第一日程提醒事件的操作指令，显示一个或多个候选参与对象集合，以供用户选择。
本申请实施例中，每个候选参与对象集合可以包含一个参与对象，或者，也可以包含多个参与对象。也就是说，当存在多个候选参与对象集合时，多个候选参与对象集合中可以既包含交互群组(群组中包含多个参与对象)，也可以包含单个参与对象。或者，可以只包含交互群组，或者，也可以只包含单个参与对象。
例如，请参考图7(a)～7(b)，其为本申请实施例所提供的显示候选参与对象集合的界面示意图，如图7(a)所示，显示了名称分别为“MyGroup1”、“MyGroup2”、“OneOne”和“导入测试QQGroup”的 四个交互群组701供用户选择。如图7(b)所示，如果用户选择某一交互群组702，还可以进一步显示该交互群组中各参与对象，用户还可以进一步选择其中的部分参与对象或者全部参与对象。
602、响应于用户针对所述一个或多个候选参与对象集合的选取操作，确定所述指定参与对象集合。
在一种可行的实施方式中，显示一个或多个候选参与对象集合之后，用户可以在该一个或多个候选参与对象集合中进行选择，以触发生成用户针对所述候选参与对象集合的操作指令。
响应于用户针对所述候选参与对象集合的操作指令，将用户选择的一个或者多个候选参与对象集合，作为上述指定参与对象集合，也就是说，指定参与对象集合的数目可以是一个，或者也可以是多个，本申请实施例对此不进行特别限定。
如图7(a)所示，用户在显示的名称分别为“MyGroup1”、“MyGroup2”“OneOne”和“导入测试QQGroup”的四个交互群组701中，选择了“导入测试QQGroup”的交互群组702。如图7(b)所示，该交互群组中还包括两个参与对象703，即用户名为“ATS”和“Likid”的两个参与对象，用户选择该两个参与对象，因此，名称为“导入测试QQGroup”的交互群组中所有参与对象组成指定参与对象集合。
针对步骤102的实现，本申请实施例在此提供了以下可行的实施方式。
举例说明，基于所述指定参与对象集合对所述第一日程提醒事件进行更新，获得第二日程提醒事件的实施方式可以包括但不限于：在第一日程提醒事件包含的参与对象信息中添加所述指定参与对象集合中各参与对象，得到所述第二日程提醒事件。
将所述第二日程提醒事件提供给日程服务器，以使所述日程服务器 将所述第二日程提醒事件发送给所述指定参与对象集合中各参与对象对应的终端设备。
在该实例中，第一终端设备根据指定参与对象集合对日程的参与人信息进行修改，生成第二日程提醒事件。可以将第二日程提醒事件发送给日程服务器。此外，第一终端设备还可以将所述第一日程的标识及各参与对象的标识发送给日程服务器，由日程服务器根据各参与对象的标识修改日程的参与人员信息。
例如，如图5所示，第一日程提醒事件的详细信息中可以包含日程的主题信息、参与对象信息、时间信息和地点信息等，地点信息可以包含在主题信息中。其中，第一日程提醒事件的参与对象信息只包含发起分享该第一日程提醒事件的用户。
可以理解的是，对于待分享的日程提醒事件，在获取指定参与对象集合之后，表示该日程提醒事件是需要分享给指定参与对象集合中的各参与对象的，而且，第一日程提醒事件的参与对象信息只包含发起分享该第一日程提醒事件的用户，因此，需要将指定参与对象集合中的各参与对象添加到第一日程提醒事件的参与对象信息中，即指定参与对象集合中的各参与对象需要作为第一日程提醒事件的参与对象信息，从而实现对第一日程提醒事件的更新，更新后的第一日程提醒事件称为第二日程提醒事件。
请参考图8，其为本申请实施例所提供的第二日程提醒事件的详细信息的界面示意图，结合图5、图7(b)和图8，图5所示的是第一日程提醒事件的详细信息的界面示意图，第一日程提醒事件中参与对象信息包含用户名为“Leekid”的参与对象。如图7(b)所示，选择了名称为“导入测试QQGroup”的交互群组，该交互群组中除当前用户外，还包含参与对象“ATS”和“Likid”，然后，基于图7所示的两个参与对象， 对该第一日程提醒事件进行更新，得到如图8所示的第二日程提醒事件，该第二日程提醒事件中参与对象信息包含用户名分别为“Leekid”、“ATS”和“Likid”的参与对象801。
在一些实例中，在上述步骤102中，在执行所述基于所述指定参与对象集合对所述第一日程提醒事件进行更新，获得所述第二日程提醒事件时，包括步骤：
向日程服务器发送所述第一日程提醒事件的更新数据，所述更新数据中包括所述第一日程提醒事件的标识及所述指定参与对象集合中各参与对象的标识，以使所述日程服务器将所述各参与对象的标识添加到所述第一日程提醒事件的标识对应的第一日程提醒事件的参与对象信息中，得到所述第二日程提醒事件，并将得到的所述第二日程提醒事件发送给所述指定参与对象集合中各参与对象对应的终端设备。
在该实例中，由日程服务器对日程进行修改，第一终端设备向日程服务器发送更新数据，日程服务器根据更新数据对对应的第一日程提醒事件的参与人信息进行修改，得到第二日程提醒事件。第一终端设备可以修改自己的日程，也可以去日程服务器拉取修改后的第二日程提醒事件。
针对步骤103的实现，本申请实施例在此提供了以下可行的实施方式。
本申请实施例中，将所述第二日程提醒事件发送给所述指定参与对象集合中各参与对象可以包括但不限于以下三种可行的实施方式：
第一种、若指定参与对象集合中各参与对象都属于同一指定交互群组，则可以将第二日程提醒事件发送给该指定交互群组，指定交互群组的成员包含指定参与对象集合中各参与对象。
例如，请参考图9，其为本申请实施例所提供的将第二日程提醒事 件发送给指定参与对象集合的界面示意图，结合图4和图9，对于用户在图4中选择的两个日程提醒事件402，在对这两个日程提醒事件分别进行更新后，如图9所示，将更新后的日程提醒事件发送至名称为“导入测试QQGroup”的交互群组，这样交互群组中用户名分别为“Leekid”、“ATS”和“Likid”的参与对象均能获取到这两个分享的日程提醒事件901。
第二种、若指定参与对象集合中各参与对象都不属于同一指定交互群组，或者，若指定参与对象集合中各参与对象互相都不属于同一指定交互群组，或者，若指定参与对象集合中部分参与对象属于同一指定交互群组，其余参与对象互相都不属于同一指定交互群组，将所述第二日程提醒事件分别发送给所述指定参与对象集合中各参与对象。
也就是说，即使指定参与对象集合中存在若干参与对象属于同一指定交互群组时，也可以将第二日程提醒事件分别发送给属于同一指定交互群组中的各参与对象。
第三种、若指定参与对象集合中部分参与对象属于同一指定交互群组，其余参与对象互相都不属于同一指定交互群组，可以将第二日程提醒事件发送给该指定交互群组，指定交互群组的成员包含指定参与对象集合中各参与对象，且将第二日程提醒事件分别发送给互相都不属于同一指定交互群组的各参与对象。也就是说，当指定参与对象集合中既包含具有多个参与对象的交互群组，也包含单独参与对象时，对于交互群组，可以将第二日程提醒事件发送至该交互群组，而对于若干单独参与对象，可以将第二日程提醒事件分别发送给各参与对象。
进一步的，对于接收到其他参与对象分享的第二日程提醒事件的参与对象，如图9所示，该参与对象可以在交互界面中点击第二日程提醒事件，以触发生成针对第二日程提醒事件的操作指令。如图10所示， 响应于针对第二日程提醒事件的操作指令，显示所点击的第二日程提醒事件的详细信息。
本申请实施例中，能够基于指定参与对象集合，自动对日程提醒事件进行更新，然后自动将更新后的日程提醒事件分享给该指定参与对象集合中的各参与对象，只需要一个参与对象获取日程提醒事件后，就可以自动将该日程提醒事件分享给其他参与对象，实现了日程提醒事件的分享，避免了其他参与对象各自手动创建同一日程，从而解决了日程获取效率比较低的问题。
在一种可行的实施方式中，对于步骤101的实施方式中第一种实施方式所涉及的显示的一个或多个日程提醒事件，或者，对于步骤101的实施方式中第二种实施方式所涉及的当前显示的日程提醒事件，显示一个或多个日程提醒事件之前。可以获得一个或多个日程提醒事件。
获得日程提醒事件，本申请实施例提供了以下三种可行的实施方式：
第一种、根据输入的日程详细信息生成日程提醒事件。
第二种、获取其他用户分享的日程提醒事件。
第三种、如图11所示，包括：
1101、从交互信息中采集日程的匹配信息。
1102、获取日程的创建窗口模板。
1103、根据所述日程的匹配信息，对所述创建窗口模板中的待填写信息进行配置，以生成日程提醒事件。
需要说明的是，如果存在多个日程提醒事件，各日程提醒事件中可以包含使用上述任意一种获取方式得到的日程提醒事件，或者，也可以包含使用上述任意两种获取方式得到的日程提醒事件，或者，还可以包含使用上述三种获取方式得到的日程提醒事件，本申请实施例对此不进行特别限定。
另外，这些方式生成的日程提醒事件用于供用户选择，用户选择的日程提醒事件是待分享的日程提醒事件，且本申请实施例称为第一日程提醒事件，因此，上述三种生成方式也可以是第一日程提醒事件的生成方式。
针对第三种可行的实施方式，本申请实施例在此提供了一种可行的实施方式。
在一种可行的实现方式中，可以在执行步骤1101之前，先检测交互信息是否满足生成日程提醒事件的触发条件，当检测到交互信息满足生成日程提醒事件的触发条件时，响应于交互信息满足生成日程提醒事件的触发条件，执行从交互信息中采集日程的匹配信息的步骤(即步骤1101)。
具体的，本申请实施例中，触发条件可以包括以下两个条件中的至少一个：
第一个、当前交互信息包含日程的主题关键词。
在一种可行的实现方案中，可以对即时通讯工具中的交互窗口进行新交互信息的监控，若检测到存在更新的交互信息，可以将更新的交互信息作为上述当前交互信息，即作为本申请实施例中用于采集日程的匹配信息时所使用的交互信息。
第二个、指定范围内的交互信息包含日程的主题关键词。
在一种可行的实现方案中，用户可以在交互信息记录中选择指定范围内的交互信息，响应于用户针对交互信息记录的操作指令，将用户选择的指定范围内的交互信息作为本申请实施例中用于采集日程的匹配信息时所使用的交互信息。或者，在另一种可行的实现方案中，也可以预先配置好指定范围，然后获取指定范围内的交互信息。
例如，可以在交互信息记录中选的某一条交互信息，然后再选中另 一条交互信息，这两条交互信息以及这两条交互信息之间的各交互信息可以作为上述指定范围内的交互信息。或者，又例如，可以在交互信息记录中选择一个时间，然后再选择一个时间，这两个时间之间的时间段内的各交互信息可以作为上述指定范围内的交互信息。或者，又例如，根据预先配置的指定时刻，当到达该指定时刻后，获取当天在该指定时刻之前的交互信息，将这些交互信息作为上述指定范围内的交互信息。可以理解的是，这些仅为举例说明，并不用于限定本申请的实现方式。
本申请实施例中所涉及的交互信息可以包括语音信息、视频信息和文本信息中一种或者多种。
请参考图12，其为本申请所提供的步骤1101的实施方式的一种流程示意图，如图12所示，包括：
1201、基于日程的主题关键词在当前交互信息中进行查找，以获取所述日程的主题信息。
基于日程的主题关键词，在满足所述触发条件的交互信息中进行查找，以获取所述日程的主题信息。
举例说明，基于日程的主题关键词在当前交互信息中进行查找，以获取所述日程的主题信息可以但不限于利用以下方式实现：
首先，对利用上述方式确定的当前交互信息进行切词处理，得到至少一个候选分词。然后，将所述主题关键词分别与各候选分词进行文本匹配，得到文本匹配结果。最后，基于所述文本匹配结果，从各候选分词中获得目标分词，作为所述主题信息。因此，本申请实施例中可以从交互信息中自动识别日程的主题信息，避免了用户手动输入主题信息。
需要说明的是，对利用上述方式确定的当前交互信息进行切词处理时，如果交互信息是语音信息，可以利用语音识别技术，将语音信息转化成文本信息，然后对转化后得到的文本信息进行切词处理。或者，如 果交互信息是视频信息，可以先从视频信息中提取语音信息，然后利用语音识别技术，将语音信息转化成文本信息，对转化后得到的文本信息进行切词处理。或者，如果交互信息是文本信息，则可以直接对该文本信息进行切词处理。
可以理解的是，本申请实施例中所涉及的技术方案是针对日程的，因此可以预先设置与日程主题相关的关键词，本申请实施例中称为主题关键词。例如，主题关键词可以包括但不限于：会议、例会、周例会、月例会、生日、考试和讨论会中的一个或者多个。这里仅为举例说明，并不用于限定本申请实施例中主题关键词仅包含这些。
在一种具体的实现方案中，可以对当前交互信息中的各条交互信息，分别利用分词词典进行切词处理，从而得到至少一个候选分词。
在一种具体的实现方案中，可以分别计算主题关键词与每个候选分词的文本相似度，将各文本相似度作为文本匹配结果。
在一种具体的实现方案中，可以按照文本相似度由大到小或者由小到大的顺序，对各候选分词进行排序，得到排序结果。根据排序结果，将文本相似度最大的候选分词作为目标分词，即作为日程的主题信息，如此，可以得到日程的主题信息。
本申请实施例中，如果在上述确定的当前交互信息中能够获取到日程的主题信息，则执行步骤1202。反之，如果上述确定的当前交互信息中没有成功获取到日程的主题信息，可以忽略用于获取主题信息的当前交互信息，并结束当前流程，继续等待下一次获取到交互信息时再执行步骤1201。例如，如果当前存在一条更新的交互信息，利用主题关键词没有从该更新的交互信息中匹配出日程的主题信息，则结束当前流程，等待当前即时通讯工具的交互窗口中出现下一条更新的交互信息时，执行步骤1201。
另外，需要说明的是，如果从当前交互信息中查找到两个以上日程的主题信息，可以针对每个日程的主题信息，分别进行下述步骤的处理，其处理过程相似，本申请实施例只针对其中某一个日程进行陈述。
在一种可行的实现方案中，如果在当前交互信息中查找到主题信息后，还可以显示对话框，请求用户确认是否自动生成日程提醒事件，如果用户确认是，则继续执行步骤1202，如果否，结束当前流程，不继续执行后续步骤。
1202、基于待采集的参数项的属性信息，在满足所述触发条件的交互信息中进行查找，得到查找结果。
本申请实施例中，除了需要自动获取日程的主题信息外，还可以根据待采集的参数项的属性信息，在当前交互信息中进行查找，以自动获取其他与日程相关的信息。例如，待采集的参数项(即其他与日程相关的信息)可以包括但不限于：日程的时间信息、日程的地点信息和日程的参与者信息中的一个或者多个。
举例说明，以待采集的参数项包含日程的时间信息为例，对基于待采集的参数项的属性信息，在当前交互信息中进行查找，得到查找结果进行为例进行陈述：可以基于指定的时间格式和时间关键词中至少一种，在当前交互信息中进行查找，得到所述日程的时间信息。因此，本申请实施例中可以从交互信息中自动识别日程的时间信息，避免了用户手动输入时间信息。
例如，若步骤1201中所使用的当前交互信息是一条更新的交互信息，本步骤中所使用的当前交互信息可以是该更新的交互信息，或者，本步骤中所使用的当前交互信息也可以包含该更新的交互信息之前的N条交互信息和该更新的交互信息之后的N条交互信息，本申请实施例对此不进行特别限定。其中N的取值也可以根据需求或者经验值进行设 置，本申请实施例对此也不进行特别限定。
例如，指定的时间格式可以包括但不限于：xx/xx/xx、xx月xx日和xx:xx中的一个或者多个。可以利用这些时间格式中的一个或者多个在上述确定的当前交互信息中进行匹配，如果存在符合这些格式的信息，则可以将符合这些格式的信息进行提取，以获得日程的时间信息。
又例如，时间关键词可以包括但不限于：明天、后天、上午和下午中的一个或者多个。利用时间关键词从当前交互信息中查找到日程的时间信息的实现方式与步骤1101中查找到主题信息的实现方式原理相同，这里不再赘述。
可以理解的是，如果经过查找，查找结果中包含多个时间信息，则可以对多个时间信息进行筛选，从中获取一个时间信息作为日程的时间信息。例如，可以在多个时间信息中选择与查询到主题信息的那条交互信息之间距离最近的一个时间信息，将其作为日程的时间信息。
需要说明的是，由于日程提醒针对的一般是未来时间，因此获取到的时间信息需要满足是还未到达的时间这一条件，因此，如果需要获取日程的时间信息，则获取到日程的时间信息后，可以判断该日程的时间信息是否满足该条件，如果满足，可以继续获取其他与日程相关的信息，如果没有其他与日程相关的信息想要获取，则执行步骤1203。
举例说明，以待采集的参数项包含日程的参与者信息为例，对基于待采集的参数项的属性信息，在当前交互信息中进行查找，得到查找结果进行为例进行陈述：可以基于参与当前交互的各参与者的标识或者指定字符，在当前交互信息中进行查找，得到所述日程的参与者信息。
其中，利用各参与者的标识从当前交互信息中查找到日程的参与者信息的实现方式与步骤1201中查找到主题信息的实现方式原理相同，这里不再赘述。其中，参与者的标识可以是参与者的姓名、用户名和昵 称中的一个或者多个，本申请实施例对此不进行特别限定。
例如，交互信息中往往存在日程只针对群组中的部分成员，因此日程发起者可能会在交互信息中提及这部分成员，如输入“@张三、@李四，明天上午10点开例会”之类的交互信息，因此可以利用字符“@”在当前交互信息中进行查找，并提取“@”之后的信息，将其作为参与者信息。
举例说明，以待采集的参数项包含日程的地点信息为例，对基于待采集的参数项的属性信息，在当前交互信息中进行查找，得到查找结果进行为例：可以基于地点格式信息和地点关键词，在当前交互信息中进行查找，得到所述日程的地点信息。
例如，地点格式信息和地点关键词为：数字+会议室和数字+教室等，因此可以利用字符“数字+会议室”和“数字+教室”在当前交互信息中进行查找，并提取相匹配的信息，作为日程的地点信息。
可以理解的是，本申请实施例中，若需要获取的其他与日程相关的信息的数目是多个，可以对这多个信息进行并行查找，或者，也可以依次顺序查找，本申请实施例对该查找方式不进行特别限定，也不限定依次顺序查找时的查找顺序。
另外，如果在上述确定的当前交互信息中能够基于待采集的参数项的属性信息，在当前交互信息中查找到与日程相关的其他信息，可以继续执行步骤303。反之，如果在上述确定的当前交互信息中基于待采集的参数项的属性信息，在当前交互信息中没有查找到与日程相关的其他信息，可以忽略当前用于获取与日程相关的其他信息的当前交互信息，并结束当前流程，继续等待下一次获取到交互信息时再执行步骤1201，继续获取日程的主题信息。例如，如果当前存在一条更新的交互信息，利用待采集的参数项的属性信息没有从该更新的交互信息中匹配出与 日程相关的其他信息，则结束当前流程，等待当前即时通讯工具的交互窗口中出现下一条更新的交互信息时，执行步骤1201。
1203、根据所述日程的主题信息和所述查找结果，确定所述匹配信息。
针对步骤1203本申请实施例提供了以下两种可行的实现方案：
第一种、将获得的日程的主题信息和查找结果直接作为日程的匹配信息。
第二种、以指定格式对日程的主题信息和查找结果进行存储，得到所述匹配信息。
在一种可行的实现方案中，可以利用数据格式对日程的主题信息和查找结果进行存储。
例如，存储日程的主题信息和时间信息的数据格式如下：
Figure PCTCN2018079076-appb-000001
如上述数据格式所示，其中，themeMessage字段表示匹配到日程的主题信息的交互信息；themeRange字段表示匹配到的主题信息在该交互信息中的位置区间，其中“10”表示匹配到的主题信息在该交互信息中的起始字符的位置是第10个字符开始，“9”表示匹配到的主题信息的字符长度是9个字符。timeResult中的内容表示匹配到的日程的时间信 息，其中，timeMessage表示匹配到日程的时间信息的交互信息，timeRange字段表示匹配到的时间信息在该交互信息中的位置区间，其中“5”表示匹配到的主题信息在该交互信息中的起始字符的位置是第5个字符开始，“6”表示匹配到的时间信息的字符长度是6个字符，time字段表示匹配到的时间信息的内容，即2017年3月6日。
需要说明的是，将日程的主题信息和查找结果以数据格式进行存储，可以在生成日程提醒事件时，能够从数据结构中进行对应字段的解析，得到匹配信息，进而根据匹配信息快速为待填写信息进行赋值，实现了快速生成日程提醒事件的目的。
另外，由于可能存在一些特殊情况，如即时通讯工具在终端的后台运行，没有在前台运行，但即时通讯工具在后台运行时仍然进行上述日程的主题信息和查找结果的获取，待即时通讯工具转换到前台运行后再触发去生成日程提醒事件，因此，需要将日程的主题信息和查找结果进行存储，待满足条件时再生成日程提醒事件。
本申请实施例中，将即时通讯工具与日程管理相结合，能够自动在交互消息中采集到日程的匹配信息，进而自动生成日程提醒事件，实现了自动且快速创建日程的功能，与现有技术相比，避免了用户一一进行手动操作带来的操作繁琐的问题，减少了操作成本，在一定程度上提高了日程生成效率。
请参考图13，其为本申请实施例所提供的日程提醒事件的第三种生成方式的另一种流程示意图，如图13所示，在一种可行的实现方案中，在步骤1102之前，还可以包括以下步骤：
1102’、显示引导创建入口，响应于针对所述引导创建入口的操作指令，执行获取日程的创建窗口模板的步骤。
在一种可行的实现方案中，对于存储日程的主题信息和上述查询结 果的数据结构，可以设置对应的标志位，通过标志位来标识数据结构中存储的信息是否已经用于生成日程提醒事件，对于已经用于生成日程提醒事件的数据结构中的信息，后续将不需要再生成日程提醒事件，而对于没有用于生成日程提醒事件的数据结构中的信息，后续需要用于生成日程提醒事件。如此，可以通过标志位确定哪些数据结构中的信息需要生成日程提醒事件，然后执行图13中的步骤1102’及其之后的步骤。
或者，在另一种可行的实现方案中，对于已经用于生成日程提醒事件的数据结构中的信息，可以将该数据结构删除，对于没有用于生成日程提醒事件的数据结构中的信息，则进行保存。如此，对于存在的数据结构，都可以执行图13中的步骤1102’及其之后的步骤。
在一种可行的实现方案中，对于没有用于生成日程提醒事件的数据结构中的信息，也即需要用于生成日程提醒事件的数据结构中的信息，可以显示引导创建入口，用以请求用户选择是否生成日程提醒事件，然后响应于用户针对引导创建入口的操作指令，执行获取日程的创建窗口模板的步骤。
请参考图14，其为本申请实施例所提供的引导创建入口的示意图，如图14所示，可以在即时通讯工具的交互窗口中通过弹出窗口显示引导创建入口1401，该引导创建入口1401可以包含提示信息，如“是否创建日程提醒事件？”，还可以包含用户的操作按钮，如按钮“是”和按钮“否”，用户可以点击两个按钮中的一个。当用户点击按钮“是”时，可以触发生成用户针对引导创建入口1401的操作指令。本领域技术人员可以理解，该示例仅为举例说明，不用于限定本申请实施例中显示引导创建入口的实现方案。
针对步骤1102的实现，本申请实施例在此提供了一种可行的实施方式。
在一种可行的实现方案中，可以预先在步骤1102的执行主体所在的设备中的指定存储位置中存储日程的创建窗口模板。当用户针对引导创建入口的操作指令之后，从该指定存储位置中读取日程的创建窗口模板。具体的，从指定存储位置中读取出的创建窗口模板中包含若干待填写信息。
在一种具体的实现方案中，日程的创建窗口模板可以利用页面代码实现，实现日程的创建窗口模板的页面代码存储在上述指定存储位置中。进一步的，客户端或者浏览器可以基于页面模版对实现日程的创建窗口模板的页面代码进行渲染，以展现日程的创建窗口。
例如，请参考图15，其为本申请实施例所提供的日程的创建窗口的示意图，如图15所示，该创建窗口中的待填写信息包括：主题信息、时间信息、地点信息和参与者信息。
针对步骤1103的实现，本申请实施例在此提供了一种可行的实施方式。请参考图16，其为本申请所提供的步骤1103的实现方式的流程示意图，如图16所示，包括：
1601、根据所述创建窗口模板中的待填写信息的属性信息，在所述匹配信息中进行查找。
可以理解的是，每个待填写信息可以具有一个属性名和一个相应的属性值，可以利用待填写信息的属性名，在匹配信息中进行查找，以获得该待填写信息的属性值。例如，如图15所示，可以利用图15所示的创建窗口中的待填写信息的属性名，如主题、时间、地点和参与者，分别在匹配信息中进行查找。
1602、若查找到所述属性信息对应的匹配信息，利用找到的匹配信息对相应的待填写信息进行赋值。
根据待填写信息的属性信息，如果在匹配信息中找到了该属性信息 对应的匹配信息(如待填写信息的属性值)，则可以利用找到的匹配信息对该待填写信息进行赋值，即将找到的匹配信息作为该待填写信息的属性值。
例如，如图15所示，待填写信息的属性名为“主题”，匹配信息中包含之前从交互信息中采集到的日程的主题信息“周例会”，因此，根据该属性名在匹配信息中可以查找到对应的匹配信息“周例会”，然后将“周例会”作为“主题”对应的属性值，表示这次日程的主题是周例。又例如，待填写信息的属性名为“地点”，匹配信息中包含之前从交互信息中采集到的日程的地点信息“2004会议室”，因此，根据该属性名在匹配信息中查找到对应的匹配信息是“2004会议室”，然后将“2004会议室”作为“地点”对应的属性值，表示该日程的地点是在2004会议室。
1603、若没查找到所述属性信息对应的匹配信息，利用默认信息对相应的待填写信息进行赋值或者保持相应的待填写信息的未填写状态。
在一种可行的实现方案中，根据待填写信息的属性信息，如果在匹配信息中没有找到了该属性信息对应的匹配信息(如待填写信息的属性值)，可以读取默认信息，然后利用默认信息对相应的待填写信息进行赋值。或者，在另一种可行的实现方案中，也可以保持相应的待填写信息的未填写状态，也就是说，待填写信息的属性值暂时为空。
在一个具体的实现方案中，可以预先在步骤1103的执行主体所在的设备中预先存储每个待填写信息各自对应的默认信息，这样，如果无法从交互信息中识别出与日程相关的信息，如时间信息、地点信息或者参与者信息等，就可以读取预先存储的默认信息。
例如，请参考图17，其为本申请实施例所提供的日程的创建窗口的另一示意图，如图17所示，待填写信息中，在匹配信息中，只获取到 “主题”对应的属性值“周例会”以及“时间”对应的属性值“12月18日10:00-10:30”，其他的待填写信息，如“地点”和“参与者”都没有获取到对应的匹配信息，以图17为例，对于待填写信息“地点”，可以保持其未填写状态，在创建窗口模板中其属性值暂时未空；对于待填写信息“参与者”，可以读取默认信息，即默认信息为当前群组中的所有成员，将当前群组中的所有成员都作为“参与者”的属性值，被填入日程的创建窗口模板中。
请参考图18，其为本申请实施例所提供的日程提醒事件的第三种生成方式的另一种流程示意图，如图18所示，在一种可行的实现方案中，在步骤1103之后，还可以包括以下步骤：
1104、显示所述日程提醒事件，响应于用户针对所述日程提醒事件的操作指令，执行对所述日程提醒事件的存储。
举例说明，请参考图19，其为本申请实施例所提供的显示日程提醒事件的另一种界面示意图，如图19所示，在生成日程提醒事件后，可以在即时通讯工具的交互窗口中弹出日程窗口1901，在该日程窗口1901中显示该日程提醒事件，用户可以在显示的日程提醒事件上进行操作。
在一种可行的实现方案中，对于显示的日程提醒事件中已经填入的匹配信息(包括获取到的匹配信息和填入的默认信息)，用户在该日程窗口中进行日程提醒事件中信息的修改，或者，如果信息没有问题，用户也可以不进行修改。例如，如图19所示，对于显示的日程提醒事件中的主题信息、时间信息和参与者信息，用户均可以进行修改。
另外，对于显示的日程提醒事件中待填写信息为空，用户可以在该日程窗口中进行填写。或者，也可以不进行填写，仍然保持该待填写信息的未填写状态。这样，如果进行日程提醒时，提示信息中将不包含该待填写信息的内容。例如，如图17所示，显示的日程提醒事件中“地 点”之前处于未填写状态；如图19所示，用户输入了“地点”的信息，即2004会议室。
进一步的，如果显示的日程提醒事件无误，或者，用户对日程提醒事件进行修改后，用户可以触发生成用户针对所述日程提醒事件的操作指令。例如，如图19所示，用户可以点击日程窗口1901中的“完成”按钮，以触发生成用户针对所述日程提醒事件的操作指令，响应于用户针对所述日程提醒事件的操作指令，将日程提醒事件存储至指定存储位置，当需要将日程提醒事件进行分享时，可以从该指定存储位置进行读取并展现。
在一种可行的实施方式中，将第二日程提醒事件发送给各参与对象后，对于接收到该第二日程提醒事件的各参与对象侧，当获得的日程提醒事件的数目为两个以上时，或者，对于上述获取的日程提醒事件，当日程提醒事件的数目为两个以上时，在上述实施方式的基础上还包括以下步骤：
根据两个以上所述日程提醒事件，检测是否存在日程冲突；当检测到存在日程冲突时，输出提示信息。
在一种具体的实施方式中，可以对两个以上日程提醒事件中每个日程提醒事件中的时间信息进行提取，然后将提取的各时间信息进行比对，检测是否存在时间冲突，如是否存在时间交叉，如果存在时间冲突，则认为存在日程冲突，需要输出提示信息。
例如，日程提醒事件A中时间信息是3月14日9:00-11:00，日程提醒事件B中时间信息是3月14日10:00-10:30，认为这两个时间信息存在时间交叉。
在一种可行的实施方式中，该提示信息用于提示用户存在日程冲突，以便于用户能够及时获知日程冲突，并进行日程提醒事件的修改。
需要说明的是，本实施例中的步骤可以是针对分享给参与对象日程提醒事件的分享者的各日程提醒事件，或者，也可以是针对从分享者获得日程提醒事件(本申请中称为第二日程提醒事件)的参与对象的各日程提醒事件。
在一种可行的实施方式中，将第二日程提醒事件发送给各参与对象后，还可以获取针对所述第二日程提醒事件的修改信息；然后，根据所述修改信息对各参与对象获得的所述第二日程提醒事件进行修改。
本申请实施例中，所述修改信息可以包括：第二日程提醒事件的主题信息、时间信息、地点信息和参与对象信息中至少一个。
需要说明的是，当第二日程提醒事件的参与对象想要对第二日程提醒事件进行修改时，或者，当存在日程冲突时，都可以对第二日程提醒事件进行修改，因此可以获取针对第二日程提醒事件的修改信息。
本申请实施例中，可以是第二日程提醒事件的分享者发起修改，或者，也可以是第二日程提醒事件的参与对象发起修改。
在一种可行的实施方式中，获得该修改信息后，确定第二日程提醒事件中各参与对象，然后通过服务器将该修改信息发送给各参与对象所使用的客户端，以使得各参与对象所使用的客户端根据该修改信息对各自接收到的第二日程提醒事件进行修改。
本申请实施例进一步给出实现上述方法实施例中各步骤及方法的装置实施例。
请参考图20，其为本申请实施例所提供的日程处理装置的功能方块图。如图所示，该装置包括：
第一获取单元100，用于确定待分享的第一日程提醒事件，以及，第二获取单元200，用于获取指定参与对象集合；
日程更新单元300，用于基于所述指定参与对象集合对所述第一日 程提醒事件进行更新，获得第二日程提醒事件；
日程分享单元400，用于将所述第二日程提醒事件发送给所述指定参与对象集合中各参与对象。
在一种可行的实施方式中，所述第二获取单元200：具体用于：将当前显示的参与对象集合作为所述指定参与对象集合；
所述第一获取单元100，具体用于：
基于当前显示的参与对象集合，显示日程分享入口；
响应于针对所述日程分享入口的操作指令，显示一个或多个日程提醒事件；
响应于针对所述一个或多个日程提醒事件的操作指令，确定待分享的日程提醒事件，以作为所述第一日程提醒事件。
在一种可行的实施方式中，所述第一获取单元100，具体用于：将当前显示的日程提醒事件作为所述第一日程提醒事件；
所述第二获取单元200，具体用于：
响应于针对所述第一日程提醒事件的操作指令，显示一个或多个候选参与对象集合；每个所述候选参与对象集合包含一个或多个参与对象；
响应于针对所述候选参与对象集合的操作指令，确定指定参与对象集合。
在一种可行的实施方式中，所述日程更新单元300，具体用于：在所述第一日程提醒事件包含的参与对象信息中添加所述指定参与对象集合中各参与对象，得到所述第二日程提醒事件。
在一种可行的实施方式中，所述日程分享单元400，具体用于：将所述第二日程提醒事件发送给指定交互群组，所述指定交互群组的成员包含所述指定参与对象集合中各参与对象。
在一种可行的实施方式中，所述日程分享单元400，具体用于：将所述第二日程提醒事件分别发送给所述指定参与对象集合中各参与对象。
在一种可行的实施方式中，所述装置还包括：
日程获取单元500，用于获得一个或多个日程提醒事件。
在一种可行的实施方式中，所述日程获取单元500，具体用于：根据用户输入的日程详细信息生成所述日程提醒事件。
在一种可行的实施方式中，所述日程获取单元500，具体用于：获取其他用户分享的日程提醒事件。
如图21所示，在一种可行的实施方式中，所述日程获取单元500进一步包括：
信息采集模块501，用于从交互信息中采集日程的匹配信息；
模板获取模块502，用于获取日程的创建窗口模板；
日程生成模块503，用于根据所述日程的匹配信息，对所述创建窗口模板中的待填写信息进行配置，以生成日程提醒事件。
在一种可行的实施方式中，所述日程生成模块503具体用于：
根据所述创建窗口模板中的待填写信息的属性信息，在所述匹配信息中进行查找；
若查找到所述属性信息对应的匹配信息，利用找到的匹配信息对相应的待填写信息进行赋值；
若没查找到所述属性信息对应的匹配信息，利用默认信息对相应的待填写信息进行赋值或者保持相应的待填写信息的未填写状态。
在一种可行的实施方式中，所述日程获取单元500还包括：
第一显示模块504，用于显示引导创建入口；
所述模板获取模块502，具体用于：响应于针对所述引导创建入口 的操作指令，执行获取日程的创建窗口模板。
在一种可行的实施方式中，所述信息采集模块501具体用于：响应于交互信息满足生成日程提醒事件的触发条件，执行从交互信息中采集日程的匹配信息。
在一种可行的实施方式中，所述触发条件包括：
当前交互信息包含日程的主题关键词；和/或，
指定范围内的交互信息包含日程的主题关键词。
在一种可行的实施方式中，所述信息采集模块501，具体用于：
基于日程的主题关键词，在满足所述触发条件的交互信息中进行查找，以获取所述日程的主题信息；
基于待采集的参数项的属性信息，在满足所述触发条件的交互信息中进行查找，得到查找结果；
根据所述日程的主题信息和所述查找结果，确定所述匹配信息。
在一种可行的实施方式中，所述信息采集模块501用于基于日程的主题关键词，在满足所述触发条件的交互信息中进行查找，以获取所述日程的主题信息时，具体用于：
对所述当前交互信息进行切词处理，得到至少一个候选分词；
将所述主题关键词分别与各候选分词进行文本匹配，得到文本匹配结果；
基于所述文本匹配结果，从各候选分词中获得目标分词，作为所述主题信息。
在一种可行的实施方式中，所述信息采集模块501用于将所述主题关键词分别与各候选分词进行文本匹配，得到文本匹配结果时，具体用于：分别计算主题关键词与每个候选分词的文本相似度，以作为文本匹配结果；
所述信息采集模块501用于基于所述文本匹配结果，从各候选分词中获得目标分词时，具体用于：获取文本相似度最大的候选分词，以作为目标分词。
在一种可行的实施方式中，所述待采集的参数项包含所述日程的时间信息，所述信息采集模块501用于基于待采集的参数项的属性信息，在满足所述触发条件的交互信息中进行查找，得到查找结果时具体用于：
基于指定的时间格式和时间关键词中至少一种，在当前交互信息中进行查找，得到所述日程的时间信息。
在一种可行的实施方式中，所述信息采集模块501用于根据所述日程的主题信息和所述查找结果，确定所述匹配信息时，具体用于：以指定格式对所述日程的主题信息和所述查找结果进行存储，得到所述匹配信息。
在一种可行的实施方式中，所述日程提醒事件的数目为两个以上；所述装置还包括：
冲突检测单元600，用于根据两个以上所述日程提醒事件，检测是否存在日程冲突；
冲突提示单元700，用于当检测到存在日程冲突时，输出提示信息。
在一种可行的实施方式中，所述装置还包括：
信息获取单元800，用于获取针对所述第二日程提醒事件的修改信息；
修改同步单元900，用于根据所述修改信息对各参与对象获得的所述第二日程提醒事件进行修改；
其中，所述修改信息包括第二日程提醒事件的主题信息、时间信息、地点信息和参与对象信息中至少一个。
由于本实施例中的各单元能够执行图1至图19所示的方法，本实施例未详细描述的部分，可参考对图1至图19的相关说明。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
本申请还提供了一种日程处理方法，应用于日程服务器，如图22所示，所述方法包括步骤：
S2201：接收第一终端设备对第一日程的参与者的修改指令，其中，所述修改指令包括所述第一日程的标识和指定参与对象集合，所述指定参与对象集合包括一个或多个参与对象的标识；
S2202：将所述各参与对象的标识添加到所述第一日程的标识对应的第一日程的参与对象信息中，获得第二日程提醒事件；
S2203：利用所述第二日程提醒事件生成即时通信消息；
S2204：将所述即时通信消息及所述各参与对象的标识发送给即时通信服务器，以使所述即时通信服务器将所述即时通信消息发送给各参与对象对应的第二终端设备。
在该实例中，由日程服务器对日程进行修改、存储。日程服务器同时根据第二日程提醒事件生成即时通信消息，具体，根据第二日程提醒时间的概要信息生成即时通信消息，例如，根据日程的主体及时间信息生成即时通信消息。将即时通信消息经由社交服务器发送给各参与对象对应的第二终端设备，使得各第二终端设置在其上的社交应用客户端中展示该即时通信消息，当第二终端设备的用户操作该即时通信消息时(例如，点击即时通信消息)，第二终端设备去日程服务器获取日程的数据，进而展示日程的详细信息。还可以由日程服务器主动将第二日程提醒时间的数据发送给参与对象的第二客户端，从而当用户点击上述即 时通信消息时，获取本地的第二日程提醒事件的数据，展示日程的详情信息。通过日程服务器及社交服务器便使日程的参与人员通过社交应用实现日程的分享，避免了日程的参与对象各自手动创建同一日程，提供了日程获取效率。
采用本申请提供的日程处理方法，能够基于指定参与对象集合，自动对日程提醒事件进行更新，然后将日程对应的即时通信消息发送给各参与对象的终端设备，通过日程服务器及社交服务器便使日程的参与人员通过社交应用实现日程的分享，避免了日程的参与对象各自手动创建同一日程，提供了日程获取效率。
在一些实例中，本申请提供的日程处理方法进一步包括步骤：
接收参与对象的标识对应的第二终端设备响应于对所述即时通信消息的操作指令发送的所述第二日程提醒事件的获取请求，将所述第二日程提醒事件的数据发送给所述第二终端设备。
在该实例中，当第二终端设备对应的用户操作即时通信消息时，例如，在发送方与接收方的对话框中展示即时通信消息，当接收方点击该即时通信消息时，第二终端设备(具体地，为第二终端设备上的社交客户端)向日程服务器获取日程的数据，根据获取的数据展示日程的详情信息。
在一些实例中，本申请提供的日程处理方法，进一步包括以下步骤：
将所述第二日程提醒事件加入所述第二终端设备对应的参与对象的日程数据中。
在日程服务器中维护有各第二终端设备的日程数据，日程服务器将第二日程数据添加到各第二终端设备的日程数据中后，将各第二终端设备发送各第二终端设备对应的第二日程数据的链接，在各终端设备上的社交应用客户端中的日程界面中，展示各日程的链接。当各第二终端设 备对应的用户点击其中一个日程的链接时，去日程服务器获取该日程的日程数据，进而展示该日程的详情信息。在该实例中，由第二终端设备去日程服务器拉取日程的数据，还可以由日程服务器主动向第二终端设备发送日程的数据。
在一些实例中，其中，所述修改指令进一步包括：接收的第一终端设备对应的分享用户的标识；
其中，在执行所述将所述即时通信消息及所述各参与对象的标识发送给即时通信服务器时，包括步骤：
将所述即时通信消息、所述各参与对象的标识及所述分享用户的标识发送给即时通信服务器，以使所述即时通信服务器将所述即时通信消息作为包括所述分享用户和所述参与对象的群组交互消息发送给所述各参与对象对应的第二终端设备。
在该实例中，即时通信消息作为日程的所有参与对象的群组的交互信息进行发送。从而各参与对象对应的第二终端设备在接收到所述即时通信消息后，在所述群组的对话框中展示所述即时通信消息。在其他实例中，发送给各第二终端设备的即时通信消息作为第一终端设备对应的用户与第二终端设备对应的用户的交互消息，从而第二终端设备在接收到即时通信消息后，在与所述第一终端设备对应的用户(日程发送方)的对话框中展示所述即时通信消息。
本申请还提供了一种日程处理系统，包括：第一终端设备、第二终端设备、日程服务器及即时通信服务器，其中，
所述第一终端设备，向日程服务器发送第一日程的参与者的修改指令，其中，所述修改指令包括所述第一日程的标识和指定参与对象集合，所述指定参与对象集合包括一个或多个参与对象的标识；
所述日程服务器，将所述各参与对象的标识添加到所述第一日程的 标识对应的第一日程的参与对象信息中，获得第二日程提醒事件；利用所述第二日程提醒事件生成即时通信消息；将所述即时通信消息及所述各参与对象的标识发送给即时通信服务器；
所述即时通信服务器，将所述即时通信消息发送给各参与对象对应的第二终端设备。
在一些实例中，其中，所述日程服务器，接收参与对象的标识对应的第二终端设备响应于对所述即时通信消息的操作指令发送的所述第二日程提醒事件的获取请求，将所述第二日程提醒事件的数据发送给所述第二终端设备。
在一些实例中，其中，所述日程服务器，将所述第二日程提醒事件加入所述第二终端设备对应的参与对象的日程数据中。
在一些实例中，其中，所述第一终端设备还将第一终端设备对应的分享用户的标识发送给所述日程服务器；
所述日程服务器，将所述即时通信消息、所述各参与对象的标识及所述分享用户的标识发送给即时通信服务器；
所述即时通信服务器，将所述即时通信消息作为包括所述分享用户和所述参与对象的群组的交互消息发送给所述各参与对象对应的第二终端设备。
本申请一实例提供的日程处理方法的消息交互图如图23所示，主要包括以下步骤：
S2301：第一客户端(第一终端设备上的社交客户端)获取第一日程(待分享日程)、指定参与对象集合。
S2302：第一客户端向日程服务器发送第一日程的修改指令，该修改指令中携带第一日程的标识、各参与对象的标识及分享用户的标识。第一客户端在向日程服务器发送修改指令前，或发送修改指令后，第一 客户端可以根据指定参与对象集合对第一日程进行修改，得到第二日程。
S2303：日程服务器根据修改指令对第一日程进行修改，得到第二日程，在修改时，根据修改指令中的第一日程的标识查找到对应的日程，将各参与对象的标识添加到查找到的日程的参与人员信息中，得到第二日程。
S2304：将第二日程添加到各参与对象的日程数据中。在日程数据库中，日程服务器为每一个终端设备对应的用户维护一个日程数据，根据第一日程的各参与对象的标识，将第二日程添加到各参与对象的标识对应的日程数据中。
S2305，日程服务器根据第二日程的信息生成即时通信消息，该即时通信消息中包括第二日程的概要信息，例如，主题、时间等。
S2306：将即时通信消息、各参与对象的标识及分享用户的标识发送给社交服务器。
S2307：社交服务器将即时通信消息作为分享用户与第二终端设备对应的用户的交互消息发送。在该情况下，第二终端设备在分享用户与第二终端设备对应的用户的对话框中展示该所述即时通信消息。
S2308：社交服务器将即时通信消息作为各参与对象的交互群组的交互消息发送。在该情况下，第二终端设备上的社交客户端在所述交互群组的对话框中展示所述即时通信消息。
S2309：响应于对交互消息的操作，向日程服务器获取第二日程的数据。第二终端设备对应的用户可以点击对话框中即时通信消息，第二终端设备向日程服务器请求第二日程的数据。进而在第二终端设备上展示第二日程的详情信息。
S2310：日程服务器将第二日程的链接发送给各参与对象对应的第 二终端设备。
S2311：第二终端设备在其上的日程界面上展示第二日程的链接。
S2312：第二终端设备响应于用户对第二日程的链接的操作，向日程服务器请求第二日程的数据。之后日程服务器将第二日程的数据发送给第二终端设备，第二终端设备上的社交客户端展示第二日程的详情信息。
本申请还提供了一种非易失性计算机可读存储介质，其中所述存储介质中存储有机器可读指令，所述机器可读指令可以由处理器执行以完成上述所述的方法。
图24示出了日程处理装置所在的计算设备的组成结构图。如图24所示，该计算设备包括一个或者多个处理器(CPU)2402、通信模块2404、存储器2406、用户接口2410，以及用于互联这些组件的通信总线2408。
处理器2402可通过通信模块2404接收和发送数据以实现网络通信和/或本地通信。
用户接口2410包括一个或多个输出设备2412，其包括一个或多个扬声器和/或一个或多个可视化显示器。用户接口1510也包括一个或多个输入设备2414，其包括诸如，键盘，鼠标，声音命令输入单元或扩音器，触屏显示器，触敏输入板，姿势捕获摄像机或其他输入按钮或控件等。
存储器2406可以是高速随机存取存储器，诸如DRAM、SRAM、DDR RAM、或其他随机存取固态存储设备；或者非易失性存储器，诸如一个或多个磁盘存储设备、光盘存储设备、闪存设备，或其他非易失性固态存储设备。
存储器2406存储处理器2402可执行的指令集，存储器中存储的指 令代码经配置以由处理器执行，以实现上述本申请中的日程处理方法中的各步骤，同时还实现本申请的日程处理装置中各模块的功能。
存储器2406中包括：
操作系统2416，包括用于处理各种基本系统服务和用于执行硬件相关任务的程序；
应用2418，包括用于日程处理的各种应用程序，这种应用程序能够实现上述各实例中的处理流程，比如可以包括日程处理装置中的部分或全部单元。各单元中的至少一个单元可以存储有机器可执行指令。处理器2402通过执行存储器2406中的机器可执行指令，进而能够实现上述所述的日程处理方法中的各步骤，同时还实现本申请的日程处理装置中各模块的功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如，多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集 成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机装置(可以是个人计算机，服务器，或者网络装置等)或处理器(Processor)执行本申请各个实施例所述方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅为本申请的较佳实施例而已，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。

Claims (4)

  1. 一种日程处理方法，其特征在于，应用于终端设备，所述方法包括：
    确定待分享的第一日程提醒事件，以及，获取指定参与对象集合；
    基于所述指定参与对象集合对所述第一日程提醒事件进行更新，获得第二日程提醒事件；
    将所述第二日程提醒事件发送给所述指定参与对象集合中各参与对象对应的终端设备。
  2. 根据权利要求1所述的方法，其中，获取所述指定参与对象集合包括：
    在用于用户间进行即时通信的交互界面中显示日程分享入口；
    响应于针对所述日程分享入口的操作指令，将所述交互界面对应的参与对象集合中的一个或多个参与者作为所述指定参与对象集合。
  3. 根据权利要求2所述的方法，其中，确定待分享的所述第一日程提醒事件包括：
    响应于针对所述日程分享入口的所述操作指令，显示一个或多个日程提醒事件；
    响应于针对所述一个或多个日程提醒事件的操作指令，确定待分享的日程提醒事件，作为所述第一日程提醒事件。
  4. 根据权利要求1所述的方法，其中，确定待分享的所述第一日程提醒事件包括：
    在日程编辑界面显示日程提醒事件；
    响应于针对所述日程提醒事件的操作指令，将当前显示的所述日程提醒事件作为所述第一日程提醒事件。
PCT/CN2018/079076 2017-03-15 2018-03-15 日程处理方法、装置、系统及存储介质 WO2018166487A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710153906.0A CN108629548B (zh) 2017-03-15 2017-03-15 一种日程处理方法及装置
CN201710153906.0 2017-03-15

Publications (1)

Publication Number Publication Date
WO2018166487A1 true WO2018166487A1 (zh) 2018-09-20

Family

ID=63522812

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/079076 WO2018166487A1 (zh) 2017-03-15 2018-03-15 日程处理方法、装置、系统及存储介质

Country Status (2)

Country Link
CN (2) CN113469660B (zh)
WO (1) WO2018166487A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112966300A (zh) * 2021-03-04 2021-06-15 北京百度网讯科技有限公司 日程数据处理方法、装置、设备和介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110175183A (zh) * 2019-06-05 2019-08-27 合肥本源量子计算科技有限责任公司 一种对象处理方法及装置、存储介质及电子装置
CN110286980A (zh) * 2019-06-24 2019-09-27 维沃移动通信有限公司 一种日程创建方法及移动终端
CN110796426A (zh) * 2019-08-14 2020-02-14 腾讯科技（深圳）有限公司 一种日程提醒方法、装置、服务器及可读存储介质
CN110544072A (zh) * 2019-09-03 2019-12-06 Oppo（重庆）智能科技有限公司 信息分享方法、装置、电子装置及计算机可读存储介质
CN111461650B (zh) * 2020-03-27 2023-06-16 深圳价值在线信息科技股份有限公司 日程安排提醒方法、装置、存储介质和智能设备
WO2021212476A1 (zh) * 2020-04-24 2021-10-28 Sun Jian 一种通讯的方法、设备及系统
CN112866093B (zh) * 2021-01-26 2023-02-03 北京搜狗科技发展有限公司 一种数据处理方法、装置和电子设备
CN113888104B (zh) * 2021-06-21 2024-03-01 北京字跳网络技术有限公司 一种日程分享方法、装置及设备
CN113596246A (zh) * 2021-09-24 2021-11-02 北京风筝科技有限公司 一种事件提醒方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007130996A2 (en) * 2006-05-01 2007-11-15 Webex Communications, Inc. Methods and apparatuses for presenting information associated with a target to a user
CN102970334A (zh) * 2012-10-29 2013-03-13 东莞宇龙通信科技有限公司 多日程冲突的处理方法及其系统
CN105530168A (zh) * 2015-12-15 2016-04-27 北京乐动卓越科技有限公司 即时通信事件的同步方法及系统
CN106355382A (zh) * 2016-08-30 2017-01-25 深圳天珑无线科技有限公司 一种事件提醒的方法及装置
CN106375186A (zh) * 2016-08-26 2017-02-01 深圳市金立通信设备有限公司 一种日程分享方法及终端

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2323087A1 (en) * 2007-07-27 2011-05-18 Research In Motion Limited System and method for acknowledging calendar appointments using a mobile device
CN101222450B (zh) * 2008-01-31 2011-05-11 腾讯科技（深圳）有限公司 一种事件管理、事件通知的方法及系统
CN101800951A (zh) * 2009-12-29 2010-08-11 闻泰集团有限公司 使用移动终端发布日程的方法
US20110184768A1 (en) * 2010-01-27 2011-07-28 Norton Kenneth S Automatically determine suggested meeting locations based on previously booked calendar events
CN102325220B (zh) * 2011-09-06 2014-06-18 宇龙计算机通信科技(深圳)有限公司 终端和基于日程的通知方法
CN104348860B (zh) * 2013-07-31 2017-09-29 中国电信股份有限公司 一种日程分享方法和系统
JP5702029B1 (ja) * 2013-09-30 2015-04-15 楽天株式会社 スケジュール調整装置、スケジュール調整方法及びスケジュール調整プログラム
CN103702296A (zh) * 2013-12-26 2014-04-02 杭州电子科技大学 一种基于手机短信的日程管理装置及其实现方法
CN105429845B (zh) * 2014-09-05 2020-05-05 腾讯科技（深圳）有限公司 一种日程信息的处理方法、系统及相关设备
CN104484796B (zh) * 2014-12-18 2018-03-27 天津三星通信技术研究有限公司 便携式终端及其日程管理方法
CN104580767B (zh) * 2015-01-16 2017-12-12 四川联友电讯技术有限公司 碎片化异步会议系统及其添加会议成员的方法
CN104954580B (zh) * 2015-06-30 2018-02-23 小米科技有限责任公司 用户日程信息的处理方法及装置
WO2017130996A1 (ja) * 2016-01-29 2017-08-03 パナソニックＩｐマネジメント株式会社 距離測定装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007130996A2 (en) * 2006-05-01 2007-11-15 Webex Communications, Inc. Methods and apparatuses for presenting information associated with a target to a user
CN102970334A (zh) * 2012-10-29 2013-03-13 东莞宇龙通信科技有限公司 多日程冲突的处理方法及其系统
CN105530168A (zh) * 2015-12-15 2016-04-27 北京乐动卓越科技有限公司 即时通信事件的同步方法及系统
CN106375186A (zh) * 2016-08-26 2017-02-01 深圳市金立通信设备有限公司 一种日程分享方法及终端
CN106355382A (zh) * 2016-08-30 2017-01-25 深圳天珑无线科技有限公司 一种事件提醒的方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112966300A (zh) * 2021-03-04 2021-06-15 北京百度网讯科技有限公司 日程数据处理方法、装置、设备和介质

Also Published As

Publication number Publication date
CN108629548A (zh) 2018-10-09
CN113469660A (zh) 2021-10-01
CN113469660B (zh) 2022-09-30
CN108629548B (zh) 2021-08-10

Similar Documents

Publication Publication Date Title
WO2018166487A1 (zh) 日程处理方法、装置、系统及存储介质
US11223584B2 (en) Automatic action responses
CN109937427B (zh) 任务管理应用中的效率改善
US20210295272A1 (en) Automatically detecting and storing digital data items associated with digital calendar items
US11044286B2 (en) Information exchange method and terminal
CA2999572C (en) Systems and methods for converting emails to chat conversations
JP2018136952A (ja) 電子会議システム
US10491690B2 (en) Distributed natural language message interpretation engine
CN107465599A (zh) 一种即时通讯中的日程设置方法及装置
US11227264B2 (en) In-meeting graphical user interface display using meeting participant status
US9477371B2 (en) Meeting roster awareness
CN102984050A (zh) 即时通信中语音搜索的方法、客户端及系统
US20180365654A1 (en) Automatic association and sharing of photos with calendar events
CN108629549A (zh) 一种日程处理方法及装置
US20240020305A1 (en) Systems and methods for automatic archiving, sorting, and/or indexing of secondary message content
WO2018175270A1 (en) Smart reminder generation from input
CN113574555A (zh) 基于自动学习和用户输入的上下文分析的智能摘要
CN114556389A (zh) 保持对重要任务的跟踪
US11258744B2 (en) Digital conversation management
KR102149478B1 (ko) 캘린더 애플리케이션들의 입력 스트림들을 프로세싱하기 위한 시스템들 및 방법들
CN114626796A (zh) 任务处理方法、装置、电子设备及存储介质
JP6131812B2 (ja) 議事録作成システム、議事録作成装置及びプログラム
CN116048285A (zh) 基于输入法的多人协作输入方法、装置及系统
CN116360652A (zh) 消息交互方法、装置、设备、存储介质及程序产品
CN112036829A (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: 18766638

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

Country of ref document: EP

Kind code of ref document: A1