Schedule Information Synchronization Method, Apparatus, and Electronic Device

Abstract

The present disclosure relates to a schedule information synchronization method, device and electronic device, particularly to the field of Internet technology. The method includes: determining, in response to a preset trigger, first record information of a target event corresponding to the trigger, which is record information in an event management application; obtaining first event parameters of the target event from the first record information; and creating or updating first schedule information corresponding to the first event parameters by a target calendar based on the first event parameters, where the target calendar is a calendar for carrying the first schedule information in a calendar application. The embodiments of the present disclosure are arranged to solve the problem that event management is inefficient.

Description

[Technical field]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application is proposed based on a Chinese patent application having application number 202210426223.9, filing date April 21, 2022, and titled "Schedule information synchronization method, device and electronic device", and claims priority to this Chinese patent application, the entire contents of which are hereby incorporated by reference into this application.

[0002] The present disclosure relates to the field of Internet technology, and in particular to a schedule information synchronization method, device, and electronic device. [Background technology]

[0003] For enterprise event management, in some event management processes, personnel need to summarize and maintain event information, and may also need to enter a calendar application and create corresponding schedule reminders to remind them to process tasks related to the event management process. In the current event management method, the event information summary and maintenance process and the schedule creation reminder process are quite complicated, making event management inefficient. Summary of the Invention

[0004] In order to solve or at least partially solve the above technical problems, the present disclosure provides a schedule information synchronization method, which can improve the efficiency of event management.

[0005] To achieve the above objectives, the technical solutions according to the embodiments of the present disclosure are as follows:

[0006] A first aspect provides a schedule information synchronization method, the method comprising: In response to a preset trigger, determining first record information of a target event corresponding to the trigger, the first record information being record information in an event management application; obtaining a first event parameter of the target event from the first recorded information; Creating or updating, by a target application, event information corresponding to the first event parameters based on the first event parameters.

[0007] As one optional embodiment of the embodiment of the present disclosure, creating or updating event information corresponding to the first event parameters by a target application based on the first event parameters includes creating or updating first schedule information corresponding to the first event parameters by a target calendar based on the first event parameters, where the target calendar is a calendar for populating the first schedule information in a calendar application.

[0008] As one optional embodiment of the present disclosure, creating or updating first schedule information corresponding to the first event parameter by the target calendar includes creating or updating meeting information corresponding to the first schedule information.

[0009] In one alternative embodiment of the present disclosure, the target calendar is a calendar associated with the event management application in the calendar application.

[0010] As an optional embodiment of the embodiment of the present disclosure, the step of creating or updating the first schedule information corresponding to the first event parameter by the target calendar based on the first event parameter includes: creating or updating, based on the first event parameters, first schedule information in the target calendar corresponding to the first event parameters; determining participant information corresponding to the first schedule information; and creating or updating the first schedule information in a personal calendar associated with the participant information.

[0011] As an optional embodiment of the embodiment of the present disclosure, the step of creating or updating the first schedule information corresponding to the first event parameter by the target calendar based on the first event parameter includes: determining participant information corresponding to the first event parameters, the target calendar being a personal calendar associated with the participant information in the calendar application; Creating or updating the first schedule information in the personal calendar based on the first event parameters.

[0012] In one alternative embodiment of the present disclosure, the first event parameter is: The event information includes at least one of event time information, event location information, event description information, and participant information.

[0013] As an optional embodiment of the embodiment of the present disclosure, the step of acquiring a first event parameter of the target event from the first recorded information includes: determining a target progress state of the target event from the first recorded information; and obtaining the first event parameter corresponding to the target progress state.

[0014] As an alternative embodiment of the present disclosure, the first record information is record information in a target table in the event management application, Obtaining the first event parameter corresponding to the target progress state includes: determining at least one first field in the target table associated with the target progress state; obtaining at least one piece of information from the at least one first field and determining the first event parameter based on the at least one piece of information.

[0015] As an optional embodiment of the embodiment of the present disclosure, the step of creating or updating the first schedule information corresponding to the first event parameter by the target calendar based on the first event parameter includes: and populating the at least one piece of information into the at least one second field of the first schedule information, where the at least one second field corresponds to the at least one first field in the first schedule information, and each second field is populated based on one or more of the at least one piece of information. As an alternative embodiment of the present disclosure, populating the at least one piece of information into the at least one second field of the first schedule information includes: Obtaining one piece of information from one first field, and dividing the one piece of information into a plurality of sub-information corresponding to a plurality of second fields; and filling the plurality of pieces of sub-information into a plurality of second fields corresponding to the plurality of pieces of sub-information, respectively.

[0016] In one alternative embodiment of the present disclosure, determining a target progress state of the target event from the first recorded information includes: determining a target progress state corresponding to the target event from the first record information, the target progress state belonging to one of at least one progress state corresponding to the target event, different progress states of the at least one progress state corresponding to different event parameters, and different progress states of the at least one progress state corresponding to different schedule generation rules; The step of creating or updating first schedule information corresponding to the first event parameters by a target calendar based on the first event parameters includes: Obtaining a target schedule generation rule corresponding to the target progress state; and generating or updating first schedule information corresponding to the first event parameter by the target calendar based on the target schedule generation rule and the first event parameter.

[0017] In one alternative embodiment of the present disclosure, the target progress state includes a current progress state or a future progress state.

[0018] As an alternative embodiment of the present disclosure, the first record information is record information in a target table in the event management application, The trigger includes a trigger operation for a synchronization control associated with the first recorded information.

[0019] As an optional embodiment of the present disclosure, the step of determining, in response to a trigger operation by a user, first record information of a target event corresponding to the trigger operation includes: determining, in response to the trigger operation, if the calendar application determines that a target calendar associated with the event management application exists in the calendar application, first record information of a target event corresponding to the trigger operation; Or, In response to the trigger operation, if it is determined that the target calendar associated with the event management application does not exist in the calendar application, creating the target calendar and determining first record information of a target event corresponding to the trigger operation.

[0020] As an alternative embodiment of the present disclosure, before creating or updating first schedule information corresponding to the first event parameter on the target calendar based on the first event parameter, the method includes: determining a base element of the schedule information; creating or updating first schedule information corresponding to the first event parameters on a target calendar based on the first event parameters, When it is determined that the first event parameters include information corresponding to the basic element, creating or updating first schedule information corresponding to the first event parameters on a target calendar based on the first event parameters.

[0021] In one alternative embodiment of the present disclosure, the method includes: if it is determined that the first event parameters do not include information corresponding to the basic element, prompt information for prompting the user to supplement information corresponding to the basic element; Prompt information for prompting the user that the schedule information has not been created; and prompt information for prompting a failure in updating the schedule information.

[0022] As an alternative embodiment of the present disclosure, the step of creating or updating first schedule information corresponding to the first event parameter on the target calendar based on the first event parameter includes: when it is determined that second schedule information corresponding to the first record information exists in the target calendar, updating the second schedule information to the first schedule information corresponding to the first event parameter based on the first event parameter; Or, and when it is determined that no schedule information corresponding to the first record information exists in the target calendar, creating the first schedule information corresponding to the first event parameters in the target calendar based on the first event parameters.

[0023] In one alternative embodiment of the present disclosure, the pre-defined trigger is a trigger generated by the event management application.

[0024] As one alternative embodiment of the present disclosure, the first event parameters include mailbox information, the target application includes a mailbox application corresponding to the mailbox information, and creating or updating the event information corresponding to the first event parameters by the target application includes sending an email to a mailbox corresponding to the mailbox information, the email including the event information generated based on the first event parameters.

[0025] In one alternative embodiment of the present disclosure, the email includes conference information generated based on the first event parameters.

[0026] A second aspect provides a schedule information synchronization device, the device comprising: a determining module for determining, in response to a preset trigger, first record information of a target event corresponding to the trigger, the first record information being record information in an event management application; an acquiring module for acquiring a first event parameter of the target event from the first recorded information; and a synchronization module for creating or updating, by a target application, event information corresponding to the first event parameters based on the first event parameters.

[0027] As one optional embodiment of the embodiment of the present disclosure, creating or updating event information corresponding to the first event parameters by a target application based on the first event parameters includes creating or updating first schedule information corresponding to the first event parameters by a target calendar based on the first event parameters, where the target calendar is a calendar for populating the first schedule information in a calendar application.

[0028] As one optional embodiment of the present disclosure, creating or updating first schedule information corresponding to the first event parameter by the target calendar includes creating or updating meeting information corresponding to the first schedule information.

[0029] In one alternative embodiment of the present disclosure, the target calendar is a calendar associated with the event management application in the calendar application.

[0030] As an alternative embodiment of the present disclosure, the synchronization module specifically includes: creating or updating, based on the first event parameters, first schedule information in the target calendar corresponding to the first event parameters; determining participant information corresponding to the first schedule information; and creating or updating the first schedule information in a personal calendar associated with the participant information.

[0031] As an alternative embodiment of the present disclosure, the synchronization module specifically includes: determining participant information corresponding to the first event parameters, the target calendar being a personal calendar associated with the participant information in the calendar application; and creating or updating the first schedule information in the personal calendar based on the first event parameters.

[0032] In one alternative embodiment of the present disclosure, the first event parameter is: The event information includes at least one of event time information, event location information, event description information, and participant information.

[0033] As an alternative embodiment of the present disclosure, the acquisition module specifically includes: determining a target progress state of the target event from the first recorded information; and obtaining the first event parameter corresponding to the target progress state.

[0034] As an alternative embodiment of the present disclosure, the first record information is record information in a target table in the event management application, The acquisition module specifically includes: determining at least one first field in the target table associated with the target progress state; and obtaining at least one piece of information from the at least one first field and determining the first event parameter based on the at least one piece of information.

[0035] As an alternative embodiment of the present disclosure, the synchronization module specifically includes: The at least one piece of information is arranged to be filled into the at least one second field of the first schedule information, where the at least one second field is a field corresponding to the at least one first field in the first schedule information, and each second field is filled based on one or more of the at least one piece of information.

[0036] As an alternative embodiment of the present disclosure, the synchronization module specifically includes: Obtaining one piece of information from one first field, and dividing the one piece of information into a plurality of sub-information corresponding to a plurality of second fields; and filling the plurality of pieces of sub-information into a plurality of second fields corresponding to the plurality of pieces of sub-information, respectively.

[0037] As an alternative embodiment of the present disclosure, the acquisition module specifically includes: configured to determine a target progress state corresponding to the target event from the first record information, the target progress state belonging to one of at least one progress state corresponding to the target event, different progress states of the at least one progress state corresponding to different event parameters, and different progress states of the at least one progress state corresponding to different schedule generation rules; The synchronization module specifically includes: Obtaining a target schedule generation rule corresponding to the target progress state; and generating or updating first schedule information corresponding to the first event parameter by the target calendar based on the target schedule generating rule and the first event parameter.

[0038] In one alternative embodiment of the present disclosure, the target progress state includes a current progress state or a future progress state.

[0039] As an alternative embodiment of the present disclosure, the first record information is record information in a target table in the event management application, The trigger includes a trigger operation for a synchronization control associated with the first recorded information.

[0040] As an alternative embodiment of the present disclosure, the determination module specifically includes: retrieving, in response to the trigger operation, if the calendar application determines that a target calendar associated with the event management application exists in the calendar application, first record information of a target event corresponding to the trigger operation; Or, In response to the trigger operation, if the calendar application determines that the target calendar associated with the event management application does not exist, the calendar application is used to create the target calendar and obtain first record information of the target event corresponding to the trigger operation.

[0041] In one alternative embodiment of the present disclosure, the determination module further comprises: arranged to determine basic elements of schedule information; The synchronization module specifically includes: The system is configured to create or update first schedule information corresponding to the first event parameters on a target calendar based on the first event parameters when it is determined that the first event parameters include information corresponding to the basic element.

[0042] As one alternative embodiment of the present disclosure, the schedule information synchronization device includes: if it is determined that the first event parameters do not include information corresponding to the basic element, prompt information for prompting the user to supplement information corresponding to the basic element; Prompt information for prompting the user that the schedule information has not been created; and prompt information for prompting a failure in updating the schedule information.

[0043] As an alternative embodiment of the present disclosure, the synchronization module specifically includes: when it is determined that second schedule information corresponding to the first record information exists in the target calendar, updating the second schedule information to the first schedule information corresponding to the first event parameter based on the first event parameter; Or, When it is determined that no schedule information corresponding to the first record information exists in the target calendar, the first schedule information corresponding to the first event parameters is created in the target calendar based on the first event parameters.

[0044] In one alternative embodiment of the present disclosure, the pre-defined trigger is a trigger generated by the event management application.

[0045] As one alternative embodiment of the present disclosure, the first event parameters include mailbox information, the target application includes a mailbox application corresponding to the mailbox information, and creating or updating the event information corresponding to the first event parameters by the target application includes sending an email to a mailbox corresponding to the mailbox information, the email including the event information generated based on the first event parameters.

[0046] In one alternative embodiment of the present disclosure, the email includes conference information generated based on the first event parameters.

[0047] A third aspect provides an electronic device, the electronic device including a processor, a memory, and a computer program stored in the memory and operable to run on the processor, the computer program realizing, when executed by the processor, the schedule information synchronization method described in the second aspect or any one of its optional embodiments.

[0048] A fourth aspect provides a computer-readable storage medium having a computer program stored therein, the computer program being capable of implementing the schedule information synchronization method described in the second aspect or any one of its optional embodiments when executed by a processor.

[0049] A fifth aspect provides a computer program product, which, when running on a computer, causes the computer to realize the schedule information synchronization method described in the second aspect or any one of its optional embodiments. Effect of the Invention

[0050] A schedule information synchronization method according to an embodiment of the present disclosure includes, in response to a predetermined trigger, determining first record information in an event management application of a target event corresponding to the trigger, obtaining first event parameters of the target event from the first record information, and creating or updating first schedule information corresponding to the first event parameters by a target calendar based on the first event parameters, where the target calendar is a calendar for loading the first schedule information in a calendar application. According to this solution, an event management application can be used to perform event management; first record information of a target event can be automatically extracted from the event management application according to a preset trigger; first event parameters of the target event can be obtained from the first record information; and first schedule information corresponding to the first event parameters can then be created or updated by a target calendar in a calendar application, thereby realizing automatic synchronization of the schedule information corresponding to the first event parameters with the target calendar. Such an event management method can automatically extract data from the event management application without the need for human participation, and can automatically establish and synchronize a schedule with the calendar according to the extracted data, simplifying the processes of event information summarization and maintenance and schedule creation, and improving the efficiency of event management. [Brief description of the drawings]

[0051] The drawings herein are incorporated in and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification serve to explain the principles of the present disclosure.

[0052] In order to more clearly describe the technical solutions in the embodiments or prior art of the present disclosure, the following briefly introduces drawings that need to be used in the embodiments or prior art description, and it is obvious that those skilled in the art can also derive other drawings based on these drawings without exerting creative efforts. [Figure 1] 1 is a flowchart of a method for synchronizing schedule information according to an embodiment of the present disclosure. [Diagram 2] FIG. 13 is a schematic diagram of a trigger operation for synchronization control related to first recorded information according to an embodiment of the present disclosure. [Diagram 3] FIG. 2 is a schematic diagram of creating or updating first schedule information in a target calendar according to an embodiment of the present disclosure; [Figure 4] 2 is a second flowchart of a method for synchronizing schedule information according to an embodiment of the present disclosure. [Diagram 5] 11 is a third flowchart of a method for synchronizing schedule information according to an embodiment of the present disclosure. [Figure 6] 4 is a fourth flowchart of a method for synchronizing schedule information according to an embodiment of the present disclosure. [Figure 7A] FIG. 2 is a structural block diagram of a schedule information synchronization device according to an embodiment of the present disclosure. [Figure 7B] FIG. 2 is a second structural block diagram of a schedule information synchronization device according to an embodiment of the present disclosure. [Figure 8] FIG. 2 is a structural block diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0053] In order to make the above objectives, features and advantages of the present disclosure more clearly understandable, the present disclosure will be further described below. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

[0054] In the following description, numerous specific details are set forth to facilitate a thorough understanding of the present disclosure, and the present disclosure may be embodied in other ways than those described herein, and it is apparent that the embodiments in the specification are merely some embodiments of the present disclosure, but not all embodiments.

[0055] The current event management method, the event information summary and maintenance process, and the schedule creation reminder process are quite complicated, and the event management is inefficient. To solve the above problem, the embodiment of the present disclosure provides a schedule information synchronization method, device and electronic device, which can automatically extract data from an event management application, and can automatically establish and synchronize a schedule with a calendar according to the extracted data, simplifying the process of event information summary and maintenance and schedule creation, and improving the efficiency of event management.

[0056] The schedule information synchronization method, device, and electronic device according to the embodiments of the present disclosure may be realized by a schedule information synchronization device or an electronic device, and the schedule information synchronization device may be an electronic device or a functional module or functional entity in the electronic device. The electronic device may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle terminal, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a personal digital assistant (PDA), a personal computer (PC), etc., and the embodiments of the present disclosure are not specifically limited thereto.

[0057] As shown in FIG. 1, which is a flowchart of a schedule information synchronization method according to an embodiment of the present disclosure, the method includes the following steps 101 to 103.

[0058] 101, in response to a preset trigger, determine first record information, which is record information in an event management application, of a target event corresponding to the trigger.

[0059] Here, the event management application may be an application for managing any event task. For example, the event management application may be an object evaluation management application, a training management application, a performance management application, a project management application, etc., and the embodiment of the present disclosure is not specifically limited.

[0060] In some embodiments, the pre-defined trigger is a trigger generated by the event management application.

[0061] The event management application may be arranged to manage a plurality of events in an event task. A target event may be an event for the event task.

[0062] Illustratively, the event management application is an object evaluation management application, for example, the event task is an object evaluation task, and the object evaluation task may include object demand management, object evaluation progress management, evaluation object management, etc. The target event may be a target evaluation event related to object evaluation progress management.

[0063] The first record information may be stored and presented in any manner in the event management application, in some embodiments the first record information is record information in a target table in the event management application, where the target table may be one or more tables in the event management application.

[0064] In some embodiments, when this first recorded information is information extracted from multiple tables, certain associative relationships exist among the multiple tables.

[0065] The preset trigger may be any type of trigger, such as a voice trigger, a trigger operation by a control related to the first recorded information in an event management application, a trigger time related to the first recorded information, a trigger condition related to the first recorded information, etc., and when the trigger time related to the first recorded information and the trigger condition are satisfied, the preset trigger is executed.

[0066] Here, the control associated with the first recorded information may be a control assembly, a physical button, or a trigger link, etc., which is not limited to the embodiments of the present disclosure.

[0067] In some embodiments, the trigger (i.e., the pre-set trigger) includes a trigger operation on a synchronization control associated with the first recording information, i.e., by the trigger operation on the synchronization control associated with the first recording information, the first recording information of the target event corresponding to this trigger operation can be determined, thereby realizing the creation of targeted schedule information, i.e., schedule information can be created for the target event.

[0068] For example, as shown in FIG. 2, which is a schematic diagram of a trigger operation on a synchronization control related to first record information according to an embodiment of the present disclosure, in which the event management application in FIG. 2 is a target evaluation management application as an example, a table 21 in the target evaluation management application records several record information of a target evaluation event, including first record information 211, where the first record information 211 includes multiple fields in table 21, as shown in the “Sync with Calendar” field 211a, the field value filled in this field is a trigger link, and the above step 101 can be executed by clicking on this trigger link.

[0069] 102, obtaining a first event parameter of the target event from the first record information.

[0070] Here, the first event parameters include, but are not limited to, the following information:

[0071] (1) Event time information, Here, the event time information may include an event start time, an event end time, and event end details.

[0072] For example, as shown in FIG. 2, in the first recorded information 211, the event is the target evaluation event time, specifically, the first round of target evaluation in the target evaluation event, the target evaluation time is "April 18th, 9:00 AM to 10:00 AM," and "April 18th, 9:00 AM to 10:00 AM" is the event time information of the target evaluation event.

[0073] (2) Event location information, In some embodiments, this event location information may include locations in real-life spaces, as well as virtual locations.

[0074] Illustratively, when the event location information is a location in a real-life space, the location may be a specific conference room, office, or other location.

[0075] Illustratively, when the event location information is a virtual location, the location may be a conference link for an online conference, or a communication tool name for communicating the target event, and so on.

[0076] (3) event description information; The event description information includes main information describing the target event and comment information for the target event.

[0077] Here, the comment information for the target event may include information on the importance of the target event and / or information on precautions for the target event.

[0078] For example, for the first record information 211 shown in Fig. 2, the field "Type A file" in "Demand object details" and the object evaluation progress "First round object evaluation" may be determined as the event description information, and the event description information may be "First round object evaluation & Type A file". The value of other fields in Fig. 2 or other information other than Fig. 2 may be the event description information, and the embodiment of the present disclosure is not specifically limited.

[0079] (4) Participant information.

[0080] Participant information is: It may include a participant ID and / or some information related to this target event for the participant.

[0081] For example, for a subject evaluation event, participant information may include information about the subject being evaluated and / or information about the evaluator.

[0082] The information on the evaluation target may include the ID of the evaluation target, detailed introduction information of the evaluation target, etc. This information can facilitate the evaluator to understand the overview of the evaluation target and assist the evaluator in considering the evaluation target during the evaluation of the target.

[0083] If some participant information has a large content, the participant information may be linked through a hyperlink, that is, the participant information included in the first event parameters may be a hyperlink of the participant information, for example, the evaluation subject details (e.g., details of the documents to be evaluated and background introductions, resumes of candidates, documents related to the items to be evaluated, etc.) may be linked through a hyperlink.

[0084] 103, creating or updating event information corresponding to the first event parameters by the target application based on the first event parameters, where in some embodiments updating includes transmitting the information and may include modifying the corresponding information.

[0085] In some examples, creating or updating event information corresponding to the first event parameters by the target application based on the first event parameters includes creating or updating first schedule information corresponding to the first event parameters by the target calendar based on the first event parameters.

[0086] Here, the target calendar is a calendar for loading the first schedule information in the calendar application.

[0087] In an embodiment of the present disclosure, the calendar application and the object rating management application are different types of applications.

[0088] In some embodiments, if it is determined that second schedule information corresponding to the first record information exists in the target calendar, the second schedule information is updated to the first schedule information in the target calendar based on the first event parameters.

[0089] In some embodiments, if it is determined that no schedule information exists in the target calendar that corresponds to the first record information, the first schedule information is created in the target calendar based on the first event parameters.

[0090] In some embodiments, an implementation manner of creating or updating first schedule information corresponding to the first event parameters by a target calendar based on the first event parameters may include filling at least one of the event time information, event location information, event description information, and event participant information into at least one second field of the first schedule information.

[0091] Here, the at least one second field is a field corresponding to at least one first field in the first schedule information, and each second field is filled in based on one or more of the at least one piece of information.

[0092] That is, there is a certain correspondence between each first field in the first event parameters acquired in the first record information and each second field in the first schedule information, and the information in each first field needs to be filled into each second field according to the correspondence. In some embodiments, each first field may correspond to one second field, and thus the information in at least one first field can be filled into at least one second field in a one-to-one manner.

[0093] For example, if the first event parameters include fields for target evaluation time, target evaluation location, and evaluator, and the first schedule information includes fields for time, location, and participants, then information in the field for target evaluation time in the first event parameters can be filled into a field for time in the first schedule information, information in the field for target evaluation location can be filled into a field for location in the first schedule information, and information in the field for evaluator can be filled into a field for participants in the first schedule information.

[0094] In some embodiments, one or more first fields may correspond to a single second field, and thus in some cases it may be necessary to aggregate information in multiple first fields before filling in a single second field that corresponds to the multiple first fields.

[0095] For example, if the first event parameters include fields for demand target details, target evaluation progress, target evaluation time, target evaluation location, and evaluator, and the first schedule information includes fields for time, location, participants, and schedule title, then information in the field for target evaluation time in the first event parameters can be filled in the field for time in the first schedule information, information in the field for target evaluation location can be filled in the field for location in the first schedule information, information in the field for evaluator can be filled in the field for participants in the first schedule information, and information in the two fields for demand target details and target evaluation progress can be filled in the field for schedule title in the first schedule information.

[0096] In some embodiments, a first field may correspond to one or more second fields, and thus in some cases it may be necessary to split the information in a first field into multiple sub-information corresponding to multiple second fields, and then fill each of the multiple sub-information into the multiple second fields corresponding to the first field, respectively.

[0097] As an example, if the first event parameters include fields for target evaluation time, target evaluation location, and participants, and the first schedule information includes fields for date, time period, location, and evaluator, the information in the field for target evaluation time in the first event parameters can be divided into date information and time period information, and filled into the field for date and the field for time period in the first schedule information, respectively, the information in the field for target evaluation location can be filled into the field for location in the first schedule information, and the information in the field for evaluator can be filled into the field for participants in the first schedule information.

[0098] As shown in FIG. 3, it is a schematic diagram of creating or updating first schedule information in a target calendar according to an embodiment of the present disclosure, and in response to a click operation on a trigger link in the “Sync with Calendar” field 211a in FIG. 2, event parameters in the first record information 211 including a target evaluation time, a target evaluation location, and an evaluator can be obtained, and the first schedule information 31 in FIG. 3 created or updated in the calendar shown in FIG. 3 can be generated. The schedule information synchronization method according to the embodiment of the present disclosure determines first record information of a target event corresponding to the preset trigger in response to a preset trigger, the first record information is record information in an event management application, obtains first event parameters of the target event from the first record information, and creates or updates first schedule information corresponding to the first event parameters by the target calendar based on the first event parameters, where the target calendar is a calendar for loading the first schedule information in a calendar application. According to this solution, an event management application can be used to perform event management; first record information of a target event can be automatically extracted from the event management application according to a preset trigger; first event parameters of the target event can be obtained from the first record information; and first schedule information corresponding to the first event parameters can then be created or updated by a target calendar in a calendar application, thereby realizing automatic synchronization of the schedule information corresponding to the first event parameters with the target calendar. Such an event management method can automatically extract data from the event management application without the need for human participation, and can automatically establish and synchronize a schedule with the calendar according to the extracted data, simplifying the processes of event information summarization and maintenance and schedule creation, and improving the efficiency of event management.

[0099] In some embodiments, creating or updating first schedule information corresponding to the first event parameter by the target calendar includes creating or updating meeting information corresponding to the first schedule information, in this way, the corresponding meeting information can be created or updated smartly and easily.

[0100] For example, as shown in FIG. 1 and FIG. 4, this is the second flowchart of a schedule information synchronization method according to an embodiment of the present disclosure. In this method, 103 in FIG. 1 may be realized by, but is not limited to, the following three cases:

[0101] Case 1: The target calendar is a calendar associated with an event management application in a calendar application (hereinafter referred to as an event management calendar), and 103 may be replaced with 103a as follows: 103a, creating or updating, based on the first event parameters, first schedule information corresponding to the first event parameters in the event management calendar;

[0102] In this case 1, since the event management calendar is associated with the event management application, a calendar identifier (Identity Document, ID) of this event management calendar associated with the event management application is stored, and based on this calendar ID, first schedule information corresponding to the first event parameter can be created or updated in the event management calendar.

[0103] Case 2: The target calendar is a calendar associated with an event management application in a calendar application (hereinafter referred to as an event management calendar), and 103 may be replaced by 103b to 103d below, 103b, creating or updating, based on the first event parameters, first schedule information corresponding to the first event parameters in the event management calendar.

[0104] In this case 1, since the event management calendar is associated with the event management application, a calendar identifier of the event management calendar associated with the event management application is stored, and based on this calendar ID, first schedule information corresponding to the first event parameter can be created or updated in the event management calendar.

[0105] 103c, determining participant information corresponding to the first schedule information.

[0106] 103d, creating or updating first schedule information in the personal calendar associated with the participant information.

[0107] Furthermore, when determining participant information corresponding to the first schedule information, a calendar ID associated with the participant information is determined, thereby determining personal calendars associated with the participant information, and the first schedule information can be created or updated in these personal calendars.

[0108] In some embodiments, obtaining a personal calendar associated with the participant information may involve pre-storing a correspondence between some participant information and calendar IDs of the personal calendars, and determining the calendar ID of the personal calendar associated with the participant information corresponding to the first schedule information by querying the pre-stored correspondence.

[0109] In some other embodiments, after creating or updating first schedule information corresponding to a first event parameter in an event management calendar, the calendar ID of a personal calendar associated with the participant information corresponding to the first schedule information may be determined by sending the participant information to a calendar application and requesting a calendar ID corresponding to the participant information from the calendar application.

[0110] Case 3: The target calendar is a personal calendar associated with attendee information in a calendar application, and 103 may be replaced by 103e and 103f below, 103e, determining participant information corresponding to the first event parameters.

[0111] 103f, creating or updating first schedule information in a personal calendar associated with the participant information based on the first event parameters.

[0112] In some embodiments, obtaining a personal calendar associated with participant information corresponding to the first event parameters may involve pre-storing a correspondence between some participant information and calendar IDs of personal calendars, and determining the calendar ID of the personal calendar associated with the participant information corresponding to the first event parameters by querying the pre-stored correspondence.

[0113] In some other embodiments, the calendar ID of a personal calendar associated with the participant information corresponding to the first event parameter may be determined by sending the participant information to a calendar application and requesting or instructing the calendar application to determine a calendar ID corresponding to the participant information.

[0114] The above three cases are merely exemplary descriptions, and creating or updating the first schedule information by the target calendar may be realized in other manners, and are not limited to the embodiments of the present disclosure.

[0115] The present disclosure realizes various implementation methods of creating or updating the first schedule information based on the target calendar, and diversifies the implementation methods of the schedule information synchronization method according to the embodiments of the present disclosure, which can be freely selected according to different application scenarios.

[0116] It should be noted that, in actual implementation, the above three cases generally do not occur at the same time; that is, in FIG. 4, if 103a is executed after 101 and 102 are executed, then 103b to 103d are generally not executed, and 103e to 103f are also not executed; if 103b to 103d are executed after 101 and 102 are executed, then 103a is generally not executed, and 103e to 103f are also not executed; and if 103e to 103f is executed after 101 and 102, then 103a is generally not executed, and 103b to 103d are also not executed.

[0117] As shown in FIG. 5, which is a third flowchart of a schedule information synchronization method according to an embodiment of the present disclosure, the method includes the following steps 501 to 504.

[0118] 501, in response to a preset trigger, determine first record information, which is record information in an event management application, of a target event corresponding to the trigger.

[0119] 502, determining a target progress state of the target event from the first recorded information.

[0120] Here, the target event may correspond to at least one progress state. For example, for a target evaluation event, the corresponding progress state may include a target evaluation node indicating which round the target evaluation event is in, such as a first round target evaluation, a second round target evaluation, a third round target evaluation, etc.

[0121] In some embodiments, different progress states of the at least one progress state may correspond to different event parameters and / or different progress states of the at least one progress state may correspond to different schedule generation rules, including but not limited to conditions for generating the schedule, types of parameters included in the schedule, a final presentation style of the schedule, etc.

[0122] In some embodiments, determining a target progress state of the target event from the first recorded information may include determining a target progress state corresponding to the target event from the first recorded information, where the target progress state belongs to one of the at least one progress state corresponding to the target event.

[0123] For example, with respect to the progress state corresponding to a target evaluation event including a first round of target evaluation, a second round of target evaluation, a third round of target evaluation, etc., if the first round of target evaluation has already been passed, the current progress state determined at this time may be the second round of target evaluation, and the future progress state may be the third round of target evaluation.

[0124] In some embodiments, the target progress state includes a current progress state or a future progress state. Since the event parameters corresponding to the progress state before the current progress state are already historical event parameters, it is not necessary to determine the progress state before the current progress state, but only to look at the current progress state or the future progress state and obtain the corresponding first event parameters, thereby avoiding scheduling an event that has already been executed and reducing interference.

[0125] 503, obtaining a first event parameter corresponding to the target progress state.

[0126] In some embodiments, the first record information is record information in a target table in the event management application, where the target table may be one table or multiple associated tables of the event management application.

[0127] The above-mentioned obtaining the first event parameter corresponding to the target progress state may include first determining at least one first field related to the target progress state in the target table, obtaining at least one piece of information from the at least one first field, and determining the first event parameter based on the at least one piece of information.

[0128] Here, determining the first event parameters based on the at least one information may mean making the at least one information the entire first event parameters, or making the at least one information a part of the first event parameters, or forming a part or all of the first event parameters after appropriately processing the at least one information.

[0129] 504, creating or updating first schedule information corresponding to the first event parameter by the target calendar based on the first event parameter.

[0130] In the process of creating or updating the first schedule information corresponding to the first event parameter by the target calendar based on the first event parameter, a target schedule generation rule corresponding to the target progress state may be obtained first, and the schedule information of the first event parameter may be created or updated by the target calendar based on the target schedule generation rule and the first event parameter. That is, information such as the condition for generating a schedule corresponding to the current target progress state, the parameter types included in the schedule, and the final presentation style of the schedule may be clarified first, and then the first schedule information corresponding to the first event parameter may be determined based on this information and the first event parameter.

[0131] In the above embodiment, in the process of determining the first event parameters from the first record information, a target progress state corresponding to the target event in the first record is first determined, and then the first event parameters corresponding to this target progress state are selected from the first record information based on the target progress state, thus extracting valid information and avoiding obtaining event parameters that do not match the progress state of the schedule to be created that is required in the information extraction process, thereby improving the accuracy of the information extraction process and avoiding the extraction of invalid information.

[0132] As shown in FIG. 6, which is a fourth flowchart of a schedule information synchronization method according to an embodiment of the present disclosure, the method includes:

[0133] 601, receiving a trigger operation from a user.

[0134] Here, the triggering operation may be a triggering operation on a control associated with the first record information in the event management application, the triggering operation being configured to trigger generation of a schedule based on a target event in the first record information and synchronization with a calendar.

[0135] 602, determining whether a target calendar exists in the calendar application that is associated with the event management application.

[0136] In response to a user's trigger operation, first record information of a target event corresponding to the trigger operation is determined; in response to the trigger operation, if it is determined that a target calendar associated with the event management application exists in the calendar application, first record information of the target event corresponding to the trigger operation is determined; in response to the trigger operation, if it is determined that a target calendar associated with the event management application does not exist in the calendar application, a target calendar is created and first record information of the target event corresponding to the trigger operation is determined.

[0137] Before generating a schedule based on the target event in the first record information and synchronizing it with the calendar, it is necessary to first detect whether a target calendar related to the event management application has already been preset in the calendar application. If a target calendar related to the event management application has already been preset, proceed to subsequent steps 604 to 612, and then generate a schedule based on the target event in the first record information and synchronize it with the target calendar; if a calendar related to the event management application has not been preset, first create a target calendar and associate it with the event management application, and then generate a schedule based on the target event in the first record information and synchronize it with the target calendar, that is, first perform step 603, and then proceed to subsequent steps 604 to 612.

[0138] 603, creating a target calendar.

[0139] 604, determining first record information of a target event corresponding to a trigger operation.

[0140] 605, determining a target progress state of the target event from the first recorded information.

[0141] 606, obtain a first event parameter corresponding to the target progress state.

[0142] Regarding the description of 604 to 605 above, reference can be made to the related description of 501 to 503, and the description will be omitted here.

[0143] In some embodiments, after determining the target progress state, it may be determined whether the first record information includes event parameters that match the target progress state. If there are no event parameters that match the target progress state, prompt information may be output to prompt that there are no event parameters that match the target progress state, so as to facilitate the user using the event management application to supplement the event parameters that match the target progress state; or, if there are no event parameters that match the target progress state, an error occurs, prompting that there is an error in the target progress state and the event parameters cannot be matched, and prompting the user using the event management application to check whether the target progress state is set incorrectly.

[0144] 607, determining basic elements of schedule information.

[0145] Here, basic elements of schedule information must include information such as participants, time, and location.

[0146] 608, determining whether the first event parameters include basic elements of schedule information.

[0147] In some embodiments, before creating or updating first schedule information corresponding to the first event parameter on the target calendar based on the first event parameter, a basic element of the schedule information may first be determined, and then, if it is determined that the first event parameter includes information corresponding to the basic element, the first schedule information corresponding to the first event parameter on the target calendar may be created or updated based on the first event parameter.

[0148] By determining whether the first event parameters include the basic elements of schedule information, it is possible to know whether the first event parameters are sufficient to generate schedule information, for example, if the first event parameters do not have time information in the basic elements of schedule information, the schedule information cannot be generated.

[0149] If it is determined that the first event parameters include information corresponding to the basic elements, it indicates that the first event parameters are sufficient to generate schedule information, and in this case steps 610 to 612 below may be performed; if it is determined that the first event parameters do not include information corresponding to the basic elements, it indicates that the first event parameters are not sufficient to generate schedule information, and in this case steps 609 below are performed.

[0150] 609, outputting prompt information.

[0151] Outputting the prompt information may include outputting prompt information including, but not limited to, at least one of the following: 1), prompt information for prompting the user to supplement information corresponding to basic elements; Here, this prompt information may be displayed in an event management application, and a user of the prompt event management application supplements, in the event management application, information corresponding to basic elements for generating schedule information in the first recording information.

[0152] 2) ,Prompt information to prompt the failure to create schedule information; 3), prompt information for prompting the failure of updating schedule information. In the embodiment of the present disclosure, by determining whether the first event parameters include basic elements of schedule information, before creating or updating the first schedule information corresponding to the first event parameters, it may be determined first whether the first event parameters are complete enough to generate the first schedule information, thus avoiding the situation that incomplete schedule information or no schedule information is obtained after performing subsequent operations when the first event parameters are incomplete, avoiding subsequent invalid operations, reducing power consumption, and ensuring the generation of complete schedule information; meanwhile, it may output user-friendly prompt information to prompt the user to supplement basic elements for generating schedule information in the first record information, thereby improving human-machine interaction performance.

[0153] 610, determining whether second schedule information corresponding to the first record information exists in the target calendar.

[0154] When it is determined that the second schedule information corresponding to the first record information exists in the target calendar, the following step 611 is executed. Specifically, when it is determined that the second schedule information corresponding to the target progress state exists in the first record information, the following step 611 may be executed: If it is determined that no schedule information corresponding to the first recorded information exists in the target calendar, the following step 612 may be executed. Specifically, if it is determined that no second schedule information corresponding to the target progress state exists in the first recorded information, the following step 612 may be executed.

[0155] 611, updating the second schedule information to the first schedule information corresponding to the first event parameters based on the first event parameters.

[0156] In some embodiments, updating the second schedule information to the first schedule information corresponding to the first event parameter may include modifying the second schedule information to the first schedule information, or deleting the second schedule information and recreating the first schedule information.

[0157] 612, creating the first schedule information corresponding to the first event parameters in the target calendar based on the first event parameters.

[0158] In the above embodiment, by determining whether second schedule information corresponding to the first record information exists in the target calendar, it is possible to know whether schedule information has already been created based on the first record information. If schedule information has been created, the original schedule information may be updated to the first schedule information; if schedule information has not been created, the first schedule information may be created based on the first event parameters in the first record information, thereby avoiding repeatedly creating the same schedule information.

[0159] In some embodiments, the first event parameters include mailbox information, and the target application includes a mailbox application corresponding to the mailbox information. In some embodiments, creating or updating the event information corresponding to the first event parameters by the target application includes sending an email to a mailbox corresponding to the mailbox information, the email including the event information generated based on the first event parameters. For example, the table has a column of mailbox information of a user, and information such as a conference link corresponding to a schedule can be sent to the mailbox, and the user can join the conference corresponding to the schedule from the conference link in the email. In this way, sending the conference link and joining the conference is made convenient.

[0160] In some embodiments, the email includes meeting information that is generated based on the first event parameters, thus making it convenient to generate and synchronize the meeting information.

[0161] As shown in FIG. 7A, an embodiment of the present disclosure provides a structural block diagram of a schedule information synchronization device, A determination module 701 for determining, in response to a preset trigger, first record information of a target event corresponding to the trigger, the first record information being record information in an event management application; an acquiring module 702 for acquiring a first event parameter of the target event from the first recorded information; and a synchronization module 703 for creating or updating, based on the first event parameter, event information corresponding to the first event parameter by a target application.

[0162] As an alternative embodiment of the present disclosure, creating or updating, by a target application, event information corresponding to the first event parameters based on the first event parameters, includes creating or updating, by a target calendar, first schedule information corresponding to the first event parameters based on the first event parameters; Here, the target calendar is a calendar for loading the first schedule information in a calendar application.

[0163] As one optional embodiment of the present disclosure, creating or updating first schedule information corresponding to the first event parameter by the target calendar includes creating or updating meeting information corresponding to the first schedule information.

[0164] In one alternative embodiment of the present disclosure, the target calendar is a calendar associated with the event management application in the calendar application.

[0165] In one alternative embodiment of the present disclosure, the synchronization module 703 specifically includes: creating or updating, based on the first event parameters, first schedule information in the target calendar corresponding to the first event parameters; determining participant information corresponding to the first schedule information; and creating or updating the first schedule information in a personal calendar associated with the participant information.

[0166] In one alternative embodiment of the present disclosure, the synchronization module 703 specifically includes: determining participant information corresponding to the first event parameters, the target calendar being a personal calendar associated with the participant information in the calendar application; and creating or updating the first schedule information in the personal calendar based on the first event parameters.

[0167] In one alternative embodiment of the present disclosure, the first event parameter is: The event information includes at least one of event time information, event location information, event description information, and participant information.

[0168] In one alternative embodiment of the present disclosure, the acquisition module 702 specifically includes: determining a target progress state of the target event from the first recorded information; and obtaining the first event parameter corresponding to the target progress state.

[0169] As an alternative embodiment of the present disclosure, the first record information is record information in a target table in the event management application, Specifically, the acquisition module 702 includes: determining at least one first field in the target table associated with the target progress state; and obtaining at least one piece of information from the at least one first field and determining the first event parameter based on the at least one piece of information.

[0170] In one alternative embodiment of the present disclosure, the synchronization module 703 specifically includes: The at least one piece of information is arranged to be filled into the at least one second field of the first schedule information, where the at least one second field is a field corresponding to the at least one first field in the first schedule information, and each second field is filled based on one or more of the at least one piece of information.

[0171] As an alternative embodiment of the present disclosure, the synchronization module specifically includes: Obtaining one piece of information from one first field, and dividing the one piece of information into a plurality of sub-information corresponding to a plurality of second fields; and filling the plurality of pieces of sub-information into a plurality of second fields corresponding to the plurality of pieces of sub-information, respectively.

[0172] In one alternative embodiment of the present disclosure, the acquisition module 702 specifically includes: configured to determine a target progress state corresponding to the target event from the first record information, the target progress state belonging to one of at least one progress state corresponding to the target event, different progress states of the at least one progress state corresponding to different event parameters, and different progress states of the at least one progress state corresponding to different schedule generation rules; The synchronization module 703 specifically includes: Obtaining a target schedule generation rule corresponding to the target progress state; and generating or updating first schedule information corresponding to the first event parameter by the target calendar based on the target schedule generating rule and the first event parameter.

[0173] In one alternative embodiment of the present disclosure, the target progress state includes a current progress state or a future progress state.

[0174] As an alternative embodiment of the present disclosure, the first record information is record information in a target table in the event management application, The trigger includes a trigger operation for a synchronization control associated with the first recorded information.

[0175] In one alternative embodiment of the present disclosure, the determining module 701 specifically: retrieving, in response to the trigger operation, if the calendar application determines that a target calendar associated with the event management application exists in the calendar application, first record information of a target event corresponding to the trigger operation; Or, In response to the trigger operation, if the calendar application determines that the target calendar associated with the event management application does not exist, the calendar application is used to create the target calendar and obtain first record information of the target event corresponding to the trigger operation.

[0176] In one alternative embodiment of the present disclosure, the determining module 701 further comprises: arranged to determine basic elements of schedule information; The synchronization module 703 specifically includes: The system is configured to create or update first schedule information corresponding to the first event parameters on a target calendar based on the first event parameters when it is determined that the first event parameters include information corresponding to the basic element.

[0177] As shown in FIG. 7A and FIG. 7B, the second structural block diagram of a schedule information synchronization device according to an embodiment of the present disclosure, the schedule information synchronization device includes: If the synchronization module 703 determines that the first event parameters do not include information corresponding to the basic element, prompt information for prompting the user to supplement information corresponding to the basic element; Prompt information for prompting the user that the schedule information has not been created; and prompt information for prompting a failure to update the schedule information.

[0178] In one alternative embodiment of the present disclosure, the synchronization module 703 specifically includes: when it is determined that second schedule information corresponding to the first record information exists in the target calendar, updating the second schedule information to the first schedule information corresponding to the first event parameter based on the first event parameter; Or, When it is determined that no schedule information corresponding to the first record information exists in the target calendar, the first schedule information corresponding to the first event parameters is created in the target calendar based on the first event parameters.

[0179] As one alternative embodiment of the present disclosure, the first event parameters include mailbox information, the target application includes a mailbox application corresponding to the mailbox information, and creating or updating the event information corresponding to the first event parameters by the target application includes sending an email to a mailbox corresponding to the mailbox information, the email including the event information generated based on the first event parameters.

[0180] In one alternative embodiment of the present disclosure, the email includes conference information generated based on the first event parameters.

[0181] As shown in Fig. 8, an embodiment of the present disclosure provides an electronic device, which includes a processor 801, a memory 802, and a computer program stored in the memory 802 and operable on the processor 801, and when the computer program is executed by the processor 801, it realizes each process of the schedule information synchronization method in the above method embodiment, and can achieve the same technical effect, and will not be further described here to avoid repetition.

[0182] An embodiment of the present invention provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, it realizes each process of the schedule information synchronization method in the above method embodiment, and can achieve the same technical effect. In order to avoid repetition of description, no further description will be given here.

[0183] Here, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or the like.

[0184] An embodiment of the present invention provides a computer program product, in which a computer program is stored, and when the computer program is executed by a processor, each process of the schedule information synchronization method in the above method embodiment can be realized and the same technical effect can be achieved, and in order to avoid repetition of description, no further description will be given here.

[0185] It should be understood by those skilled in the art that the embodiments of the present disclosure may be provided as a method, a system, or a computer program product. Thus, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. And, the present disclosure may take the form of a computer program product embodied by one or more computer usable storage mediums that contain computer usable program code.

[0186] In this disclosure, a processor may be a Central Processing Unit (CPU) or other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware assembly, etc. A general purpose processor may be a microprocessor, or the processor may be any common processor, etc.

[0187] In this disclosure, memory may include non-persistent memory, random access memory (RAM) and / or non-volatile memory in the form of a computer readable medium, such as read only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer readable medium.

[0188] In this disclosure, computer readable media includes permanent and non-permanent, removable and non-removable storage media. Storage media may achieve information storage by any method or technology, and information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, read only optical disk read only memory (CD-ROM), digital versatile optical disk (DVD) or other optical storage, magnetic cartridge, magnetic disk storage or other magnetic storage device, or any other non-transmission medium that may be arranged to store information accessible by a computing device. As defined herein, computer readable media does not include transitory computer readable media, such as modulated data signals and carriers.

[0189] It should be explained that in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that any such actual relationship or order exists between those entities or operations. And the terms "comprise", "include", "includes" or any other variants thereof are intended to cover a non-exclusive "comprise", whereby a process, method, article or device that includes a set of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent in such process, method, article or device. In the absence of further limitations, an element limited by the phrase "comprises a" does not exclude the presence of other identical elements in the process, method, article or device that includes the element.

[0190] The above are merely specific embodiments of the present disclosure that enable those skilled in the art to understand or realize the present disclosure. Various modifications of these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not limited to these embodiments herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. 1. An information synchronization method, comprising: In response to a preset trigger, determining first record information of a target event corresponding to the trigger, the first record information being record information in an event management application; obtaining a first event parameter of the target event from the first recorded information; and creating or updating, by a target application based on the first event parameters, event information corresponding to the first event parameters.

2. creating or updating, by a target application based on the first event parameters, event information corresponding to the first event parameters; creating or updating, based on the first event parameters, first schedule information corresponding to the first event parameters by a target calendar; 2. The method of claim 1, wherein the target calendar is a calendar for populating the first schedule information in a calendar application.

3. Creating or updating first schedule information corresponding to the first event parameter by a target calendar includes:

3. The method of claim 2, further comprising creating or updating meeting information corresponding to the first schedule information.

4. 3. The method of claim 2, wherein the target calendar is a calendar associated with the event management application in the calendar application.

5. The step of creating or updating first schedule information corresponding to the first event parameter by a target calendar based on the first event parameter includes: creating or updating, based on the first event parameters, first schedule information in the target calendar corresponding to the first event parameters; determining participant information corresponding to the first schedule information; and creating or updating the first schedule information in a personal calendar associated with the participant information.

6. The step of creating or updating first schedule information corresponding to the first event parameter by a target calendar based on the first event parameter includes: determining participant information corresponding to the first event parameters, the target calendar being a personal calendar associated with the participant information in the calendar application; 3. The method of claim 2, further comprising creating or updating the first schedule information in the personal calendar based on the first event parameters.

7. The first event parameter is 10. The method of claim 1, further comprising at least one of the following information: event time information, event location information, event description information, and participant information.

8. The step of obtaining a first event parameter of the target event from the first recorded information includes: determining a target progress state of the target event from the first recorded information; and obtaining the first event parameter corresponding to the target progress state.

9. the first record information is record information in a target table in the event management application; Obtaining the first event parameter corresponding to the target progress state includes: determining at least one first field in the target table associated with the target progress state; 9. The method of claim 8, further comprising obtaining at least one piece of information from the at least one first field and determining the first event parameter based on the at least one piece of information.

10. The step of creating or updating first schedule information corresponding to the first event parameter by a target calendar based on the first event parameter includes:

10. The method of claim 9, further comprising filling at least one second field of the first schedule information with the at least one piece of information, wherein the at least one second field corresponds to the at least one first field in the first schedule information, and each second field is filled based on one or more of the at least one piece of information.

11. Populating at least one second field of the first schedule information with the at least one piece of information includes: Obtaining one piece of information from one first field, and dividing the one piece of information into a plurality of sub-information corresponding to a plurality of second fields; and filling the plurality of sub-information into a plurality of second fields corresponding to the plurality of sub-information, respectively.

12. determining a target progress state of the target event from the first recorded information includes: determining a target progress state corresponding to the target event from the first record information, the target progress state belonging to one of at least one progress state corresponding to the target event, different progress states of the at least one progress state corresponding to different event parameters, and / or different progress states of the at least one progress state corresponding to different schedule generation rules; The step of creating or updating first schedule information corresponding to the first event parameter by a target calendar based on the first event parameter includes: Obtaining a target schedule generation rule corresponding to the target progress state; 9. The method of claim 8, further comprising: creating or updating first schedule information corresponding to the first event parameter by the target calendar based on the target schedule generation rule and the first event parameter.

13. The method of claim 12 , wherein the target progress state comprises a current progress state or a future progress state.

14. the first record information is record information in a target table in the event management application; 2. The method of claim 1, wherein the trigger comprises a trigger operation on a synchronization control associated with the first recorded information.

15. Determining, in response to the user's trigger operation, first record information of a target event corresponding to the trigger operation, determining, in response to the trigger operation, if the calendar application determines that a target calendar associated with the event management application exists in the calendar application, first record information of a target event corresponding to the trigger operation; Or, 2. The method of claim 1, further comprising, in response to the triggering operation, if the calendar application determines that the target calendar associated with the event management application does not exist, creating the target calendar and determining first record information for a target event corresponding to the triggering operation.

16. Before creating or updating first schedule information corresponding to the first event parameters on a target calendar based on the first event parameters, the method further comprises: determining a base element of the schedule information; creating or updating first schedule information corresponding to the first event parameters on a target calendar based on the first event parameters, 3. The method of claim 2, further comprising: creating or updating, on a target calendar, first schedule information corresponding to the first event parameters based on the first event parameters when it is determined that the first event parameters include information corresponding to the basic element.

17. The method comprises: if it is determined that the first event parameters do not include information corresponding to the basic element, prompt information for prompting the user to supplement information corresponding to the basic element; Prompt information for prompting the user that the schedule information has not been created; and prompting information for prompting a failure to update the schedule information.

18. creating or updating first schedule information corresponding to the first event parameters on a target calendar based on the first event parameters, when it is determined that second schedule information corresponding to the first record information exists in the target calendar, updating the second schedule information to the first schedule information corresponding to the first event parameter based on the first event parameter; Or, 3. The method of claim 2, further comprising: if it is determined that no schedule information corresponding to the first record information exists in the target calendar, creating the first schedule information corresponding to the first event parameters in the target calendar based on the first event parameters.

19. The method of claim 1 , wherein the pre-defined trigger is a trigger that occurs in the event management application.

20. the first event parameters include mailbox information, and the target application includes a mailbox application corresponding to the mailbox information; Creating or updating event information corresponding to the first event parameter by the target application includes: The method of claim 1 , further comprising: sending an email containing event information generated based on the first event parameters to a mailbox corresponding to the mailbox information.

21. The method of claim 20 , wherein the email includes meeting information generated based on the first event parameters.

22. An information synchronization device, a determining module for determining, in response to a preset trigger, first record information of a target event corresponding to the trigger, the first record information being record information in an event management application; an acquiring module for acquiring a first event parameter of the target event from the first recorded information; and a synchronization module for creating or updating event information corresponding to the first event parameters by a target application based on the first event parameters.

23. 22. An electronic device comprising: a processor; a memory; and a computer program stored in the memory and operable on the processor, the electronic device realizing the schedule information synchronization method according to any one of claims 1 to 21 when the computer program is executed by the processor.

24. 22. A computer-readable storage medium having a computer program stored therein, the computer program realizing the schedule information synchronization method according to any one of claims 1 to 21 when executed by a processor.

Images