CN115221239A - Multi-data-source calendar data bidirectional synchronization method and system - Google Patents

Abstract

The invention discloses a method and system for bidirectional synchronization of calendar data from multiple data sources. The method includes: a unified schedule center obtains calendar data synchronized in real time from different types of calendar applications based on a standard schedule interface, and synchronizes the synchronized calendar data according to other calendar applications. The provided calendar writing interface is configured and written into other calendar applications in real time. The present invention provides a unified calendar solution, which can synchronize the calendar data of the calendar application to the unified schedule center, and then synchronize the unified schedule center to other calendar applications. , Build a calendar sharing system for the whole platform, realize the unified calendar data sharing of the whole platform, support two-way synchronization of calendars and have a low cost.

Description

Method and system for bidirectional synchronization of calendar data from multiple data sources

technical field

The invention relates to the field of calendars, in particular to a method and system for bidirectional synchronization of calendar data with multiple data sources.

Background technique

At present, there are many kinds of calendar applications on the market, and it is extremely painful for people who are accustomed to using calendars to manage their schedules without a good tool. The mainstream calendar applications in the existing market are independent of each other, which causes users to switch between multiple applications when viewing their own calendar, resulting in poor user experience. For example, a company executive will view offline meetings in the Outlook calendar, video conferences in the DingTalk calendar, and itinerary information in the major official event application. If you need to synchronize the calendar, customized development is required, and bidirectional synchronization of the calendar is not supported, so even if you want to synchronize the calendar, the customized development cost of calendar synchronization is too high.

SUMMARY OF THE INVENTION

The technical problem to be solved by the present invention is to provide a method and system for bidirectional synchronization of calendar data with multiple data sources, aiming at the above-mentioned defects of the prior art, improving user experience.

The technical solution adopted by the present invention to solve the technical problem is: constructing a bidirectional synchronization method for calendar data with multiple data sources, the method comprising:

Based on the standard schedule interface, the unified schedule center obtains the calendar data synchronized by different types of calendar applications in real time;

The unified calendar center configures the synchronized calendar data according to the calendar writing interface provided by other calendar applications, and then writes it to other calendar applications synchronously in real time.

Preferably, the unified schedule center obtains calendar data synchronized in real time by different types of calendar applications based on a standard schedule interface, including:

The client-side schedule synchronization application monitors the client-side calendar application, obtains the changed calendar data when monitoring changes in the calendar, configures the changed calendar data according to the standard schedule interface of the unified schedule center, and sends it to the unified schedule center;

The unified calendar center actively calls the standard calendar query interface of a third-party calendar application through scheduled tasks to query and obtain calendar data; or the cloud that integrates various third-party calendar applications can call the standard calendar query interface of third-party calendar applications through scheduled tasks to query and obtain calendar data. , and configure the obtained calendar data according to the standard schedule interface of the unified schedule center and send it to the unified schedule center.

Preferably, the unified schedule center configures the synchronized calendar data according to the calendar writing interface provided by other calendar applications, and then writes it into other calendar applications synchronously in real time, including:

When the calendar data changes, the unified schedule center asynchronously sends the calendar data to the message queue;

The distribution service monitors the calendar data of the message queue, uses the calendar data of the message queue to configure the calendar write interface of other third-party calendar applications that need to synchronize log data, or/and sends the calendar data of the message queue to the client calendar application , the client calendar application calls the client's standard calendar writing interface to write the calendar data into the client calendar application.

Preferably, the method further includes: when the unified calendar center acquires the calendar data synchronized by the calendar application in real time, for each newly acquired calendar data, compare it with the calendar data in the local database, and determine whether it belongs to the itinerary If there is no duplicate calendar data, the newly acquired calendar data will be persisted to the local database.

Preferably, the comparison of the calendar data includes: extracting three pieces of information: the schedule title, the schedule start time, and the schedule end time from the calendar data, generating a hash string by a digest algorithm, and judging whether the itinerary is repeated by comparing the hash values. Calendar data.

The present invention also constructs a multi-data source calendar data bidirectional synchronization system for implementing the method described in the preceding item, including a unified schedule center, which is used to obtain real-time synchronization data from different types of calendar applications based on a standard schedule interface. Calendar data, configure the synchronized calendar data according to the calendar writing interface provided by other calendar applications, and then synchronously write it to other calendar applications in real time.

Further, it also includes a client schedule synchronization application installed on the client, which is used to monitor the client calendar application, and when monitoring changes in the calendar, configure and send the changed calendar data according to the standard schedule interface of the unified schedule center. to the Unified Agenda Center;

The unified calendar center is specifically used to actively call the standard calendar query interface of a third-party calendar application through scheduled tasks to query and obtain calendar data; or the cloud that integrates various third-party calendar applications can call the standard calendar query interface of a third-party calendar application through scheduled tasks to query Acquire the calendar data, configure the acquired calendar data according to the standard schedule interface of the unified schedule center, and send it to the unified schedule center.

Further, when the calendar data changes, the unified calendar center sends the calendar data to the message queue asynchronously, and the distribution service monitors the calendar data of the message queue, and uses the calendar data of the message queue to synchronize other third-party calendar applications that need to synchronize log data. The calendar writing interface is configured, or/and the calendar data of the message queue is delivered to the client calendar application, and the client calendar application calls the client's standard calendar writing interface to write the calendar data into the client calendar application.

Further, when the unified schedule center obtains the calendar data synchronized by the calendar application in real time, for each newly acquired calendar data, it is compared with the calendar data of the local database to determine whether it belongs to the calendar data of repeated itineraries. , if not, persist the newly acquired calendar data to the local database;

Further, the comparison of the calendar data includes: extracting three pieces of information, the schedule title, the schedule start time, and the schedule end time from the calendar data, generating a hash string through a digest algorithm, and judging whether it belongs to the itinerary repetition by comparing the hash value. Calendar data.

The method and system for bidirectional synchronization of calendar data with multiple data sources of the present invention have the following beneficial effects: the present invention provides a solution for a unified calendar, which can synchronize the calendar data of the calendar application to the unified calendar center, and then synchronize the unified calendar center to other calendars Application, build a calendar sharing system for the whole platform, realize the unified calendar data sharing of the whole platform, support two-way synchronization of calendars and low cost.

Description of drawings

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention. For those of ordinary skill in the art, other drawings can also be obtained according to the provided drawings without creative work:

Fig. 1 is the flow chart of the multi-data source calendar data bidirectional synchronization method of the present invention;

Fig. 2 is a schematic diagram of the synchronization of calendar data from a calendar application to a unified schedule center;

Fig. 3 is the schematic diagram that calendar data is synchronized from unified schedule center to calendar application;

FIG. 4 is a schematic diagram of the structure of the multi-data source calendar data bidirectional synchronization system of the present invention.

Detailed ways

In order to facilitate understanding of the present invention, the present invention will be described more fully hereinafter with reference to the related drawings. Typical embodiments of the invention are shown in the drawings. However, the present invention may be embodied in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terms used herein in the description of the present invention are for the purpose of describing specific embodiments only, and are not intended to limit the present invention.

The general idea of the present invention is as follows: the unified schedule center obtains the calendar data synchronized in real time by different types of calendar applications based on the standard schedule interface, and then configures the synchronized calendar data according to the calendar writing interface provided by other calendar applications and synchronizes it in real time. Write to other calendar applications, in this way, to achieve unified calendar data sharing across the platform, support bidirectional synchronization of calendars, and low cost.

In order to better understand the above technical solutions, the above technical solutions will be described in detail below with reference to the accompanying drawings and specific embodiments of the description. The description is not intended to limit the technical solutions of the present application, and the embodiments of the present invention and the technical features in the embodiments may be combined with each other under the condition of no conflict.

Example 1

1, the multi-data source calendar data bidirectional synchronization method of the present invention mainly includes:

S101: The unified schedule center acquires calendar data synchronized in real time by different types of calendar applications based on a standard schedule interface.

Among them, the calendar application includes a client calendar application and a third-party calendar application, and the third-party calendar application may specifically include, but is not limited to, Dingding Calendar in the cloud, Exchange calendar, major official business, and the like. Correspondingly, the synchronization of calendar data also includes data synchronization between the client and the cloud. Referring to FIG. 2 , step S101 mainly includes two situations:

A) The client-side schedule synchronization application monitors the client-side calendar application, and when monitoring changes in the calendar, configures the changed calendar data according to the standard schedule interface of the unified schedule center and sends it to the unified schedule center.

The client-side calendar application refers to the native calendar application that comes with the client, such as the native calendar application of IOS and Android.

The client-side schedule synchronization application is a piece of software developed to implement the method of the present invention, and the user needs to download and install the software on the client-side and register an account in advance.

The standard schedule interface of the unified schedule center can be customized. For example, the first parameter of the definition interface is the schedule title, the second parameter is the schedule start time, and the third parameter is the schedule end time.

B) The unified schedule center actively invokes the standard calendar query interface of a third-party calendar application to query and obtain calendar data through a scheduled task.

Cloud schedule synchronization requires open standard calendar interfaces (including standard calendar query interfaces and calendar write interfaces) of third-party calendar applications. For example, the Exchange calendar has an EWS service interface, and DingTalk has an open service.

It can be understood that, in the above step B), a scheduled task is set on the side of the unified schedule center to actively call the standard calendar query interface of a third-party calendar application to obtain data. In fact, the task can also be actively set in the cloud, and the cloud can call through the scheduled task. The standard calendar query interface of the third-party calendar application queries and obtains calendar data, configures the obtained calendar data according to the standard calendar interface of the unified calendar center, and sends it to the unified calendar center.

S102: The unified schedule center configures the synchronized calendar data according to the calendar writing interface provided by other calendar applications, and then writes the synchronized calendar data in other calendar applications in real time.

Among them, different calendar applications are associated through accounts, and the unified schedule center can associate the calendar data of different calendar applications based on the account. Once the calendar data of a calendar application changes, the unified schedule center will get its changes. Calendar data, the changed calendar data will be synced to other associated calendar applications.

Specifically, referring to Figure 3, this step includes:

First of all, when the calendar data changes, the unified calendar center sends the calendar data to the message queue MQ asynchronously, and introduces the message queue MQ, mainly to ensure the reliability of data transmission. For example, if the data transmission fails, it can be resent.

Secondly, the distribution service monitors the calendar data of the message queue. On the one hand, the distribution service sends the calendar data of the message queue to the client calendar application, and the client calendar application calls the client's standard calendar writing interface to write the calendar data to the client Calendar application; on the other hand, use the calendar data of the message queue to configure the calendar writing interface of other third-party calendar applications that need to synchronize log data, such as configuring various parameters of the interface.

It can be understood that different interfaces have different definitions of parameters. Therefore, in the present invention, when querying or writing data by calling the interface, it needs to be implemented in combination with the parameter definition of the interface. For example, for calendar application 1, its standard calendar query The parameters of the interface or calendar writing interface may be: schedule title, schedule start time, and schedule end time, and for Calendar Application 2, the parameters of the standard calendar query interface or calendar writing interface may be: schedule start time, schedule end time. Time and schedule title, so when querying calendar data by calling the standard calendar query interface, it is necessary to combine the parameter definitions of the interface to determine the data sent by the interface. Similarly, when calling the calendar writing interface to write calendar data, it is necessary to combine The parameter definition of the interface determines the specific data of each parameter written to the interface.

Preferably, the method further includes: the unified calendar center persists the synchronously uploaded calendar data to a local database. For each newly acquired calendar data, the unified schedule center compares it with the calendar data in the local database to determine whether it belongs to the calendar data of repeated itineraries, and if not, writes the newly acquired calendar data. Specifically, the comparison of the calendar data includes: extracting the schedule title, schedule start time, and schedule end time from the calendar data, generating a hash string through the digest algorithm, and comparing the hash value to determine whether it belongs to the itinerary repetition. calendar data.

Embodiment 2

Referring to FIG. 4 , in conjunction with FIGS. 2 and 3 , this embodiment discloses a bidirectional synchronization system for calendar data with multiple data sources as in the method embodiment 1, including a unified schedule center and a client schedule synchronization application installed on the client Wait. The unified schedule center can also be an open service running on the cloud.

Among them, the unified calendar center is used to obtain the calendar data synchronized by different types of calendar applications in real time based on the standard calendar interface, configure the synchronized calendar data according to the calendar write interface provided by other calendar applications, and then write it to other calendars in real time. application.

Referring to Figure 2, specifically, the client-side schedule synchronization application is used to monitor the client-side calendar application. When monitoring changes in the calendar, the changed calendar data is configured according to the standard schedule interface of the unified schedule center and sent to the unified schedule. center;

Referring to Figure 2, specifically, the unified schedule center actively calls the standard calendar query interface of a third-party calendar application through scheduled tasks to query and obtain calendar data; or the cloud that integrates various third-party calendar applications calls the standard of third-party calendar applications through scheduled tasks. The calendar query interface queries and obtains calendar data, configures the obtained calendar data according to the standard calendar interface of the unified calendar center, and sends it to the unified calendar center.

Referring to FIG. 3 , specifically, the unified schedule center sends the calendar data to the message queue asynchronously when the calendar data changes, and the distribution service monitors the calendar data of the message queue. The distribution service uses the calendar data of the message queue to configure the calendar write interface of other third-party calendar applications that need to synchronize log data, or/and sends the calendar data of the message queue to the client calendar application, and then the client calendar application Call the client's standard calendar writing interface to write calendar data into the client calendar application.

The unified schedule center is also used to compare the calendar data of the local database for each newly acquired calendar data, and judge whether it belongs to the calendar data of the itinerary repetition, if not, just write the newly acquired calendar data; Among them, the comparison of the calendar data includes: extracting three pieces of information: the schedule title, the schedule start time, and the schedule end time from the calendar data, generating a hash string through a digest algorithm, and judging whether it belongs to a calendar with repeated itineraries by comparing the hash values. data.

For more content, reference may be made to the embodiments, which will not be repeated here.

Further, the system of this embodiment also includes internal services such as conference management service and schedule management service. The schedule management service can obtain calendar data from the database, analyze the calendar data, and automatically call the conference management service to reserve a conference room. Furthermore, schedule-related services can also be shared between internal applications of our platform and schedule management services.

To sum up, the method and system for bidirectional synchronization of calendar data from multiple data sources of the present invention have the following beneficial effects: the present invention provides a solution for a unified calendar, which can synchronize the calendar data of the calendar application to the unified schedule center, and then use the unified schedule The center synchronizes to other calendar applications, builds a full-platform calendar sharing system, realizes unified calendar data sharing across the entire platform, supports bi-directional calendar synchronization and has a low cost.

The embodiments of the present invention have been described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific embodiments, which are merely illustrative rather than restrictive. Under the inspiration of the present invention, without departing from the scope of protection of the present invention and the claims, many forms can be made, which all belong to the protection of the present invention.

Claims (10)

1. a multi-data source calendar data bidirectional synchronization method, is characterized in that, described method comprises: Based on the standard schedule interface, the unified schedule center obtains the calendar data synchronized by different types of calendar applications in real time; The unified calendar center configures the synchronized calendar data according to the calendar writing interface provided by other calendar applications, and then writes it to other calendar applications synchronously in real time. 2. The method according to claim 1, wherein the unified schedule center obtains the calendar data synchronized in real time by different types of calendar applications based on a standard schedule interface, comprising: The client-side schedule synchronization application monitors the client-side calendar application, obtains the changed calendar data when monitoring changes in the calendar, configures the changed calendar data according to the standard schedule interface of the unified schedule center, and sends it to the unified schedule center; The unified calendar center actively calls the standard calendar query interface of a third-party calendar application through scheduled tasks to query and obtain calendar data; or the cloud that integrates various third-party calendar applications can call the standard calendar query interface of third-party calendar applications through scheduled tasks to query and obtain calendar data. , and configure the obtained calendar data according to the standard schedule interface of the unified schedule center and send it to the unified schedule center. 3. method according to claim 1, is characterized in that, described unified schedule center will synchronise and write other calendar applications in real time after configuring according to the calendar writing interface that other calendar applications provide the calendar data that comes over, including : When the calendar data changes, the unified schedule center asynchronously sends the calendar data to the message queue; The distribution service monitors the calendar data of the message queue, uses the calendar data of the message queue to configure the calendar write interface of other third-party calendar applications that need to synchronize log data, or/and sends the calendar data of the message queue to the client calendar application , the client calendar application calls the client's standard calendar writing interface to write the calendar data into the client calendar application. 4. The method according to claim 1, wherein the method further comprises: when the unified schedule center acquires the calendar data synchronized by the calendar application in real time, for each newly acquired calendar data, compare it with the local The calendar data in the database is compared to determine whether it belongs to the calendar data of repeated itineraries. If not, the newly acquired calendar data is persisted to the local database. 5. method according to claim 4, is characterized in that, the comparison of calendar data comprises: from calendar data, extract three pieces of information of schedule title, schedule start time, schedule end time, generate hash string by digest algorithm, By comparing the hash value, it is judged whether it belongs to the calendar data of the itinerary repetition. 6. A multi-data source calendar data bidirectional synchronization system for realizing the method according to any one of claims 1-5, characterized in that, comprising a unified schedule center, and the unified schedule center is used to obtain different schedules based on a standard schedule interface. Type the calendar data synchronized by the calendar application in real time. After configuring the synchronized calendar data according to the calendar writing interface provided by other calendar applications, it will be synchronized and written to other calendar applications in real time. 7. The system according to claim 6, further comprising a client schedule synchronization application installed on the client, for monitoring the client calendar application, and when monitoring that the calendar has changed, the changed calendar data, according to Configure the standard schedule interface of the unified schedule center and send it to the unified schedule center; The unified calendar center is specifically used to actively call the standard calendar query interface of a third-party calendar application through scheduled tasks to query and obtain calendar data; or the cloud that integrates various third-party calendar applications can call the standard calendar query interface of a third-party calendar application through scheduled tasks to query Acquire the calendar data, configure the acquired calendar data according to the standard schedule interface of the unified schedule center, and send it to the unified schedule center. 8. The system according to claim 6, wherein the unified schedule center specifically sends the calendar data to the message queue asynchronously when the calendar data changes, the distribution service monitors the calendar data of the message queue, and utilizes the calendar data of the message queue. Configure the calendar writing interface of other third-party calendar applications that need to synchronize log data, or/and deliver the calendar data of the message queue to the client calendar application, and the client calendar application will call the client's standard calendar writing interface to write Calendar data is written to the client calendar application. 9. The system of claim 6, wherein When the unified schedule center acquires the calendar data synchronized by the calendar application in real time, for each newly acquired calendar data, it is compared with the calendar data of the local database to determine whether it belongs to the calendar data of the itinerary repetition, if not. , to persist the newly acquired calendar data to the local database. 10. The system according to claim 9, wherein the comparison of calendar data comprises: extracting three information of schedule title, schedule start time, and schedule end time from the calendar data, and generating a hash string by a digest algorithm, By comparing the hash value, it is judged whether it belongs to the calendar data of the itinerary repetition.

Images