Schedule information synchronization method, device, 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 based on and claims priority from a Chinese patent application bearing application number 202210426223.9, filed on April 21, 2022, and entitled "Schedule information synchronization method, device, and electronic device," 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, some event management processes require personnel to summarize and maintain event information, and may also require personnel to enter a calendar application and create corresponding schedule reminders to remind them to complete tasks related to the event management process. In the current event management method, the process of summarizing and maintaining event information and the process of creating schedule reminders are quite cumbersome, making event management inefficient. Summary of the Invention

[0004] To solve or at least partially solve the above technical problems, the present disclosure provides a schedule information synchronization method that 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, the first record information being record information in an event management application, of a target event corresponding to the trigger; 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.

[0007] As an optional 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, wherein the target calendar is a calendar for populating the first schedule information in a calendar application.

[0008] As an optional embodiment of the present disclosure, creating or updating first schedule information corresponding to the first event parameter using a 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 one alternative 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 first schedule information corresponding to the first event parameters in the target calendar based on 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 one alternative 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 comprising: ,before It is a personal calendar related to the participant information. and 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 alternative 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] In one 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 one alternative 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 filling the at least one piece of information into the at least one second field of the first schedule information, wherein the at least one second field is a Rufu In one alternative embodiment of the present disclosure, filling the at least one information into at least one second field of the first schedule information comprises: Acquiring 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 recorded information, the target progress state belonging to one of at least one progress states 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 parameter by a target calendar based on the first event parameter includes: obtaining a target schedule generation rule corresponding to the target progress state; and 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.

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

[0018] In one 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 alternative embodiment of the present disclosure, determining, in response to a user's trigger operation, first record information of a target event corresponding to the trigger operation includes: determining, in response to the triggering operation, if the calendar application determines that a target calendar associated with the event management application exists, first record information of a target event corresponding to the triggering 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; The step of creating or updating first schedule information corresponding to the first event parameters on the target calendar based on the first event parameters includes: 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 the target calendar based on the first event parameters.

[0021] In one alternative embodiment of the present disclosure, 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 that the creation of schedule information has failed; and prompt information for prompting that updating of the schedule information has failed.

[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 parameter in the target calendar based on the first event parameter.

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

[0024] As an 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 determination 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, based on the first event parameter, event information corresponding to the first event parameter by a target application.

[0027] As an optional 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, wherein the target calendar is a calendar for populating the first schedule information in a calendar application.

[0028] As an optional embodiment of the present disclosure, creating or updating first schedule information corresponding to the first event parameter using a 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 first schedule information corresponding to the first event parameters in the target calendar based on 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 comprising: ,before It is a personal calendar related to the participant information. 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] In one 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 fill the at least one second field of the first schedule information, wherein the at least one second field is Rufu fields, each second field being filled in 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: Acquiring 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: The system is configured to determine a target progress state corresponding to the target event from the first recorded 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 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.

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

[0039] In one 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] In one alternative embodiment of the present disclosure, the determination module specifically: responsive to the triggering operation, if the calendar application determines that a target calendar associated with the event management application exists, obtaining first record information of a target event corresponding to the triggering 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 target calendar is created and first record information of the target event corresponding to the trigger operation is obtained.

[0041] In one alternative embodiment of the present disclosure, the determination module further comprises: arranged to determine the 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 an alternative embodiment of the present disclosure, the schedule information synchronization device 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 that the creation of schedule information has failed; and prompt information for prompting that the schedule information has failed to be updated.

[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 an 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 the schedule information synchronization method described in the second aspect or any one of its alternative embodiments when executed by the processor.

[0048] A fourth aspect provides a computer-readable storage medium having a computer program stored therein, the computer program realizing the schedule information synchronization method described in the second aspect or any one of its alternative 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 implement the schedule information synchronization method described in the second aspect or any one of its alternative embodiments. [Effects of the Invention]

[0050] A schedule information synchronization method according to an embodiment of the present disclosure includes, in response to a preset 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, wherein the target calendar is a calendar for loading the first schedule information in a calendar application. According to this solution, event management can be performed using an event management application, and first record information of a target event can be automatically extracted from the event management application according to a preset trigger, and first event parameters of the target event can be obtained from the first record information. Then, first schedule information corresponding to the first event parameters can 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. This event management method can automatically extract data from the event management application without the need for human intervention, and can automatically establish and synchronize a schedule with the calendar according to the extracted data, thereby simplifying the processes of event information summarization and maintenance and schedule creation, and improving the efficiency of event management. [Brief explanation of the drawings]

[0051] The drawings herein are incorporated in and constitute a part of this 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 explain the technical solutions in the embodiments of the present disclosure or the prior art, 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 any creative effort. [Figure 1] 1 is a flowchart illustrating a method for synchronizing schedule information according to an embodiment of the present disclosure. [Figure 2] FIG. 10 is a schematic diagram of a trigger operation for synchronization control related to first recorded information according to an embodiment of the present disclosure. [Figure 3] FIG. 1 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] 10 is a second flowchart of a method for synchronizing schedule information according to an embodiment of the present disclosure. [Figure 5] 10 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. 1 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. 1 is a structural block diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0053] In order to make the above-mentioned objects, features and advantages of the present disclosure more clearly understood, 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 different from 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] In the current event management method, the process of summarizing and maintaining event information and the process of creating and reminding schedules are quite complicated, making event management inefficient. To solve the above problems, the embodiments of the present disclosure provide a schedule information synchronization method, device, and electronic device, which can automatically extract data from an event management application, and automatically establish and synchronize a schedule with a calendar according to the extracted data, thereby simplifying the process of summarizing and maintaining event information and creating schedules, 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 implemented 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 PC, a laptop computer, a palmtop computer, an in-vehicle terminal, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), a personal computer (PC), etc., but 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, such as an object evaluation management application, a training management application, a performance management application, or a project management application, and the embodiments of the present disclosure are not specifically limited thereto.

[0060] In some embodiments, the pre-configured trigger is a trigger that occurs in the event management application.

[0061] The event management application may be arranged to manage multiple events in an event task, and the target event may be an event for the event task.

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

[0063] The first recorded information may be stored and presented in any manner in the event management application, and in some embodiments, the first recorded information is recorded 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, there is a certain association relationship between these 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, or a trigger method in which a trigger time or a trigger condition related to the first recorded information is preset, and the preset trigger is executed when the trigger time or the trigger condition related to the first recorded information is met.

[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 preset trigger) includes a trigger operation on a synchronization control associated with the first recording information, i.e., by triggering 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 Figure 2, this 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 Figure 2, the event management application is an example of a target evaluation management application, and table 21 in the target evaluation management application records some record information of a target evaluation event, where it includes first record information 211, and 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 recorded 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 name of a communication tool 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 target details" and the target evaluation progress "First round target evaluation" may be determined as the event description information, and the event description information may be "First round target evaluation & Type A file". The value of other fields in Fig. 2 or other information other than that in Fig. 2 may also be used as the event description information, and the embodiments of the present disclosure are 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 help the evaluator to easily understand the overview of the evaluation target and support the evaluator's consideration of the evaluation target during the evaluation of the target.

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

[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 also include modifying the corresponding information.

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

[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 corresponding to the first record information exists in the target calendar, 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 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 information in at least one first field can be filled into at least one second field in a one-to-one correspondence.

[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 the 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, the information in the field for target evaluation location can be filled into a field for location in the first schedule information, and the 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 corresponding to those 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, one first field may correspond to one or more second fields, and thus in some cases it may be necessary to split the information in one first field into multiple sub-information corresponding to multiple second fields, and then fill these multiple sub-information into multiple second fields corresponding to the one first field, respectively.

[0097] For 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 target evaluation time field in the first event parameters can be divided into date information and time period information, and filled into the date field and the time period field in the first schedule information, respectively, the information in the target evaluation location field can be filled into the location field in the first schedule information, and the information in the evaluator field can be filled into the participant field in the first schedule information.

[0098] FIG. 3 is a schematic diagram illustrating a method for creating or updating first schedule information in a target calendar according to an embodiment of the present disclosure. 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 assessment time, a target assessment location, and an assessor, can be obtained, and 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, in response to a preset trigger, first record information of a target event corresponding to the preset trigger, the first record information being 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 in the target calendar based on the first event parameters, where the target calendar is a calendar for loading the first schedule information in the calendar application. According to this solution, event management can be performed using an event management application, and first record information of a target event can be automatically extracted from the event management application according to a preset trigger, and first event parameters of the target event can be obtained from the first record information. Then, first schedule information corresponding to the first event parameters can 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. This event management method can automatically extract data from the event management application without the need for human intervention, and can automatically establish and synchronize a schedule with the calendar according to the extracted data, thereby 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 using the target calendar includes creating or updating meeting information corresponding to the first schedule information, thereby enabling smart and easy creation or updating of the corresponding meeting information.

[0100] For example, as shown in Figures 1 and 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 Figure 1 above 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 below: 103a, creating or updating first schedule information corresponding to the first event parameters in an event management calendar based on the first event parameters;

[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 the following 103b to 103d: 103b, creating or updating first schedule information corresponding to the first event parameters in the event management calendar based on the first event parameters;

[0104] In this case 1, since the event management calendar is associated with the event management application, a calendar identifier 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.

[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, the calendar ID associated with this participant information can be 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 first event parameters in the event management calendar, the calendar ID of the 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 the 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 parameter.

[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 parameter 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 parameter by querying the pre-stored correspondence.

[0113] In some other embodiments, the calendar ID of the 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 the calendar ID corresponding to the participant information.

[0114] The above three cases are merely illustrative, and other methods may be used to create or update the first schedule information by the target calendar, and are not limiting to the embodiments of the present disclosure.

[0115] The present disclosure realizes various implementation methods for creating or updating the first schedule information according to 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 simultaneously. That is, in FIG. 4, if 103a is executed after 101 and 102 are executed, 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, 103a is generally not executed, and 103e to 103f are also not executed; if 101 and 102 are executed after 103e to 103f are executed, 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 the round number of the target evaluation event, 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 a schedule, types of parameters to be 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, the progress status corresponding to a target evaluation event may include a first round target evaluation, a second round target evaluation, a third round target evaluation, etc., and if the first round target evaluation has already been passed, the current progress status determined at this time may be the second round target evaluation, and the future progress status may be the third round target evaluation.

[0124] In some embodiments, the target progress state includes a current progress state or a future progress state. Because 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 focus on the current progress state or a 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 is a record in a target table in the event management application, where the target table may be one table or multiple related tables in 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 be 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 first obtained, and then 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 conditions for creating a schedule corresponding to the current target progress state, the types of parameters included in the schedule, and the final presentation style of the schedule may be first clarified, 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, thereby extracting valid information and avoiding obtaining event parameters that do not match the progress state of the schedule required for creation 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 user's trigger operation;

[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, determine whether a target calendar associated with the event management application exists in the calendar application.

[0136] In response to a trigger operation by a user, 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 associated with the event management application has already been preset in the calendar application. If a target calendar associated with the event management application has already been preset, proceed to the 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 associated with 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, after first performing step 603, proceed to the 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] For the description of 604 to 605 above, please refer 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, a prompt is output to indicate that there is an error in the target progress state and it cannot match the event parameters, and the user using the event management application is prompted to check whether the target progress state is set incorrectly.

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

[0145] Here, the basic elements of the 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, basic elements 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 elements, 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 the schedule information, it is possible to know whether the first event parameters are sufficient to generate the schedule information. For example, if the first event parameters do not include time information in the basic elements of the 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, step 609 below is 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 to prompt supplementary 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 the event management application with information corresponding to the basic elements for generating schedule information in the first recording information.

[0152] 2) ,Prompt information to prompt the failure of creating schedule information; 3) Prompt information for prompting when schedule information update fails. In an 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 whether the first event parameters are complete enough to generate the first schedule information. In this way, if the first event parameters are incomplete, a situation in which incomplete schedule information or no schedule information is obtained after performing a subsequent operation can be avoided. This avoids subsequent invalid operations, reduces power consumption, and ensures the generation of complete schedule information. Meanwhile, user-friendly prompt information can be output to prompt for supplementing the 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 may be 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 the target calendar does not have schedule information corresponding to the first record information, the following step 612 may be executed. Specifically, if it is determined that the first record information does not have second schedule information corresponding to the target progress state, the following step 612 may be executed.

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

[0156] In some embodiments, updating the second schedule information to the first schedule information corresponding to the first event parameter may involve 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 parameter in the target calendar based on the first event parameter;

[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 may have a column for user mailbox information, and information such as a conference link corresponding to a schedule may be sent to the mailbox, allowing the user to 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 conference information that is generated based on the first event parameters, thus making it convenient to generate and synchronize conference information.

[0161] As shown in FIG. 7A, an embodiment of the present disclosure provides one structural block diagram of a schedule information synchronization device, a determining 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 event information corresponding to the first event parameter by a target application based on the first event parameter.

[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 an optional embodiment of the present disclosure, creating or updating first schedule information corresponding to the first event parameter using a 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] As an alternative embodiment of the present disclosure, the synchronization module 703 specifically includes: creating or updating first schedule information corresponding to the first event parameters in the target calendar based on 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] As an 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] In one 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 702 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.

[0170] As an 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, wherein 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: Acquiring 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: The system is configured to determine a target progress state corresponding to the target event from the first recorded 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 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.

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

[0174] In one 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] As an alternative embodiment of the present disclosure, the determining module 701 specifically: responsive to the triggering operation, if the calendar application determines that a target calendar associated with the event management application exists, obtaining first record information of a target event corresponding to the triggering 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 target calendar is created and first record information of the target event corresponding to the trigger operation is obtained.

[0176] In one alternative embodiment of the present disclosure, the determining module 701 further comprises: arranged to determine the 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 the schedule information synchronization device according to the embodiment of the present disclosure, in which the schedule information synchronization device: If the synchronization module 703 determines that the first event parameter does not include information corresponding to the primitive, prompt information for prompting the user to supplement information corresponding to the basic element; Prompt information for prompting that the creation of schedule information has failed; and prompt information for prompting that the schedule information has not been updated.

[0178] As an 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 an 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] 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-described method embodiment, and can achieve the same technical effect, which will not be further described here to avoid repetition.

[0182] An embodiment of the present invention provides a computer-readable storage medium having a computer program stored therein, which, when executed by a processor, realizes each process of the schedule information synchronization method in the above-described method embodiment, and can achieve the same technical effect. To avoid repetition, 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, which stores a computer program, 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 effects, and in order to avoid repetition, no further description will be given here.

[0185] Those skilled in the art should understand that embodiments of the present disclosure may be provided as a method, a system, or a computer program product. As such, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied by one or more computer-usable storage mediums containing computer-usable program code.

[0186] In this disclosure, a processor may be a Central Processing Unit (CPU), or may be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), off-the-shelf Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware assemblies, 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 implement information storage by any method or technology, and information may be computer-readable instructions, data structures, program modules, 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 (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 and do not necessarily require or imply the existence of any such actual relationship or ordering between those entities or operations. Furthermore, the terms "comprise," "include," or any other variation 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 other elements not expressly listed, or further elements inherent in such process, method, article, or device. Absent further limitations, an element qualified 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 foregoing are merely specific embodiments of the present disclosure that will 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 intended to be limited to these embodiments herein, but is to 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, the first record information being record information in an event management application, of a target event corresponding to the trigger; obtaining a first event parameter of the target event from the first recorded information; creating or updating, by a target application based on the first event parameters, event information corresponding to the first event parameters; Including, creating or updating, by a target application based on the first event parameter, event information corresponding to the first event parameter; creating or updating first schedule information corresponding to the first event parameters by a target calendar based on the first event parameters; wherein the target calendar is a calendar for loading the first schedule information in a calendar application; creating or updating first schedule information corresponding to the first event parameter by a target calendar based on the first event parameter; 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; further comprising The method, wherein the first record information is record information in a target table in the event management application, and the trigger includes a trigger operation on a synchronization control associated with the first record information.

2. Creating or updating first schedule information corresponding to the first event parameter using a target calendar includes: The method of claim 1 , further comprising creating or updating meeting information corresponding to the first schedule information.

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

4. 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 first schedule information corresponding to the first event parameters in the target calendar based on 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.

5. 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.

6. 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.

7. 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; 7. The method of claim 6, 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.

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

8. The method of claim 7, further comprising filling the at least one piece of information into at least one second field of the first schedule information, wherein the at least one second field is a 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.

9. Populating the at least one piece of information into at least one second field of the first schedule information includes: Acquiring 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; 9. The method of claim 8, further comprising: filling the plurality of pieces of sub-information into a plurality of second fields corresponding to the plurality of pieces of sub-information, respectively.

10. Determining a target progress state of the target event from the first recorded information comprises: determining a target progress state corresponding to the target event from the first recorded information, wherein the target progress state belongs to one of at least one progress states corresponding to the target event, and different progress states of the at least one progress state correspond to different event parameters and / or different progress states of the at least one progress state correspond 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; and 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.

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

12. determining, in response to the predetermined trigger, first record information of a target event corresponding to the trigger; determining, in response to the predetermined trigger, 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 predetermined trigger; Or, 2. The method of claim 1, further comprising, in response to the preset trigger, 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 preset trigger.

13. Before creating or updating first schedule information corresponding to the first event parameter on a target calendar based on the first event parameter, the method further comprises: determining a base element of the schedule information; The step of creating or updating first schedule information corresponding to the first event parameters on the target calendar based on the first event parameters includes:

2. The method of claim 1, further comprising: 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.

14. 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 that the creation of schedule information has failed; and prompt information for prompting a failure to update the schedule information.

14. The method of claim 13, further comprising: outputting at least one of prompt information for prompting a failure to update the schedule information.

15. Creating or updating first schedule information corresponding to the first event parameters on a target calendar based on the first event parameters 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, 2. The method of claim 1, 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.

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

17. the first event parameter includes 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 parameter to a mailbox corresponding to the mailbox information.

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

19. An information synchronization device, a determination 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; 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; The synchronization module further creates or updates, based on the first event parameters, first schedule information corresponding to the first event parameters by a target calendar, the target calendar being a calendar for loading the first schedule information in a calendar application; creating or updating first schedule information corresponding to the first event parameter by a target calendar based on the first event parameter; determining participant information corresponding to the first event parameters, wherein the target calendar is 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; An information synchronization device characterized in that the first record information is record information in a target table in the event management application, and the trigger includes a trigger operation for a synchronization control associated with the first record information.

20. 19. An electronic device comprising: a processor; a memory; and a computer program stored in the memory and operable on the processor, the computer program implementing the information synchronization method according to any one of claims 1 to 18 when executed by the processor.

21. 19. A computer-readable storage medium having a computer program stored therein, the computer program implementing the information synchronization method of any one of claims 1 to 18 when executed by a processor.

Images