CN115221239A - Multi-data-source calendar data bidirectional synchronization method and system - Google Patents
Multi-data-source calendar data bidirectional synchronization method and system Download PDFInfo
- Publication number
- CN115221239A CN115221239A CN202110434231.3A CN202110434231A CN115221239A CN 115221239 A CN115221239 A CN 115221239A CN 202110434231 A CN202110434231 A CN 202110434231A CN 115221239 A CN115221239 A CN 115221239A
- Authority
- CN
- China
- Prior art keywords
- calendar
- data
- calendar data
- schedule
- unified
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Abstract
The invention discloses a method and a system for bidirectional synchronization of calendar data with multiple data sources, wherein the method comprises the following steps: the unified schedule center acquires the calendar data synchronized in real time by different types of calendar applications based on a standard schedule interface, and the synchronized calendar data is configured according to the calendar writing interfaces provided by other calendar applications and then is synchronously written into other calendar applications in real time.
Description
Technical Field
The invention relates to the field of calendars, in particular to a method and a system for bidirectional synchronization of calendar data with multiple data sources.
Background
Calendar applications are various in the market at present, and people who are used to manage travel by using a calendar are extremely painful as no good tool exists. Mainstream calendar applications in the existing market are independent of one another, so that users need to switch among multiple applications when viewing the calendar, and the user experience is poor. For example, a company can view offline meetings in the outlook calendar, video meetings in the nailed calendar, travel information in major business activity applications, and the like. If the calendar needs to be synchronized, customized development is needed, and bidirectional synchronization of the calendar is not supported, so that the cost of customized development of calendar synchronization is too high even if the calendar is synchronized.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a method and a system for bidirectional synchronization of calendar data with multiple data sources, which aims at the above-mentioned defects in the prior art, to improve the user experience.
The technical scheme adopted by the invention for solving the technical problems is as follows: constructing a method for bidirectional synchronization of calendar data of multiple data sources, wherein the method comprises the following steps:
the unified schedule center acquires calendar data synchronously sent by different types of calendar applications in real time based on a standard schedule interface;
and the unified schedule center configures the synchronized calendar data according to calendar writing interfaces provided by other calendar applications and then synchronously writes the synchronized calendar data into other calendar applications in real time.
Preferably, the unified schedule center obtains the calendar data synchronized in real time by the calendar applications of different types based on a standard schedule interface, and includes:
the client-side schedule synchronization application monitors the client-side calendar application, acquires changed calendar data when monitoring that the calendar changes, configures the changed calendar data according to a standard schedule interface of a unified schedule center and sends the changed calendar data to the unified schedule center;
the unified schedule center actively calls a standard calendar query interface of the third-party calendar application through the timing task to query and acquire calendar data; or the cloud integrated with various third-party calendar applications calls a standard calendar query interface of the third-party calendar applications to query and acquire calendar data through the timing task, and configures the acquired calendar data according to the standard schedule interface of the unified schedule center and sends the calendar data to the unified schedule center.
Preferably, the step of configuring the synchronized calendar data by the unified scheduling center according to a calendar writing interface provided by other calendar applications and then synchronously writing the synchronized calendar data into the other calendar applications in real time includes:
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, configures calendar writing interfaces of other third-party calendar applications needing to synchronize the log data by using the calendar data of the message queue, or/and sends the calendar data of the message queue to the client calendar application, and the client calendar application calls a standard calendar writing interface of the client to write the calendar data into the client calendar application.
Preferably, the method further comprises: when the unified schedule center acquires the calendar data synchronized by the calendar application in real time, comparing each newly acquired calendar data with the calendar data of the local database, judging whether the newly acquired calendar data belong to the calendar data with repeated travel, and if not, persisting the newly acquired calendar data to the local database.
Preferably, the comparison of calendar data comprises: extracting three information of a schedule title, a schedule starting time and a schedule ending time from the calendar data, generating a hash character string through a summary algorithm, and judging whether the calendar data belongs to the calendar data with repeated travel or not by comparing hash values.
The invention also constructs a bidirectional synchronization system of the calendar data with multiple data sources for realizing the method, which comprises a unified schedule center, wherein the unified schedule center is used for acquiring the calendar data synchronized in real time by different types of calendar applications based on a standard schedule interface, and the synchronized calendar data is configured according to the calendar writing interface provided by other calendar applications and then is synchronously written into other calendar applications in real time.
The system further comprises a client schedule synchronization application installed on the client, wherein the client schedule synchronization application is used for monitoring the client calendar application, and when the calendar changes, the changed calendar data is configured according to a standard schedule interface of the unified schedule center and is sent to the unified schedule center;
the unified schedule center is specifically used for actively calling a standard calendar query interface of a third-party calendar application through a timing task to query and acquire calendar data; or the cloud integrated with various third-party calendar applications calls a standard calendar query interface of the third-party calendar applications to query and acquire calendar data through the timing task, and configures the acquired calendar data according to the standard schedule interface of the unified schedule center and sends the calendar data to the unified schedule center.
Further, 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, the calendar data of the message queue is used for configuring calendar write-in interfaces of other third-party calendar applications needing synchronous log data, or/and the calendar data of the message queue is sent to the client calendar application, and the client calendar application calls a standard calendar write-in interface of the client to write the calendar data into the client calendar application.
Further, when acquiring the calendar data synchronized by the calendar application in real time, the unified schedule center compares each newly acquired calendar data with the calendar data of the local database to judge whether the newly acquired calendar data belong to the calendar data with repeated travel, and if not, the newly acquired calendar data are persisted to the local database;
further, the comparison of calendar data comprises: three information of schedule title, schedule starting time and schedule ending time are extracted from the calendar data, a hash character string is generated through a summary algorithm, and whether the calendar data belong to the schedule repetition or not is judged by comparing hash values.
The method and the system for bidirectionally synchronizing the calendar data with multiple data sources have the following beneficial effects: the invention provides a solution for unifying calendars, which can synchronize calendar data of calendar applications to a unified schedule center and then synchronize the calendar data of the calendar applications to other calendar applications from the unified schedule center, and a full-platform calendar sharing system is built, so that full-platform unified calendar data sharing is realized, bidirectional calendar synchronization is supported, and the cost is low.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts:
FIG. 1 is a flow chart of a method of bi-directional synchronization of multiple data source calendar data of the present invention;
FIG. 2 is a schematic diagram of synchronization of calendar data from a calendar application to a unified hub;
FIG. 3 is a schematic diagram of the synchronization of calendar data from a unified hub to a 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 Description
To facilitate an understanding of the invention, the invention will now be described more fully with reference to the accompanying drawings. Exemplary embodiments of the invention are shown in the drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.
Unless defined otherwise, 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 terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.
The general idea of the invention is as follows: the unified schedule center acquires the calendar data synchronized in real time by different types of calendar applications based on a standard schedule interface, and then configures the synchronized calendar data according to the calendar writing interface provided by other calendar applications and then synchronously writes the synchronized calendar data into other calendar applications in real time, so that the unified calendar data sharing of the whole platform is realized, the bidirectional synchronization of the calendars is supported, and the cost is low.
In order to better understand the technical solutions, the technical solutions will be described in detail below with reference to the drawings of the specification and the specific embodiments, and it should be understood that the specific features in the embodiments and examples of the present invention are detailed descriptions of the technical solutions of the present application, and are not limitations of the technical solutions of the present application, and the technical features in the embodiments and examples of the present invention may be combined with each other without conflict.
Example one
Referring to fig. 1, the method for bidirectional synchronization of calendar data with multiple data sources mainly includes:
s101: and the unified schedule center acquires the calendar data synchronized in real time by different types of calendar applications based on a standard schedule interface.
The calendar application comprises a client calendar application and a third-party calendar application, and the third-party calendar application specifically comprises but is not limited to a cloud nailing schedule, an Exchange calendar, a major official business and the like. Correspondingly, the synchronization of the calendar data also includes data synchronization between the client and the cloud, and referring to fig. 2, the step S101 mainly includes two situations:
a) The client-side schedule synchronization application monitors the client-side calendar application, and when the calendar changes, the changed calendar data is configured according to a standard schedule interface of the unified schedule center and is sent to the unified schedule center.
The client calendar application refers to a native calendar application carried by the client, such as a native calendar application of IOS and Android.
The client-side schedule synchronization application is software developed for realizing the method of the invention, and a user needs to download and install the software at the client side in advance and register an account.
The standard schedule interface of the unified schedule center can be customized, for example, the first parameter of the interface is defined as the schedule title, the second parameter is the schedule start time, and the third parameter is the schedule end time.
B) And the unified schedule center actively calls a standard calendar query interface of the third-party calendar application through the timing task to query and acquire the calendar data.
Cloud calendar synchronization requires a third-party calendar application to open a standard calendar interface (including a standard calendar query interface and a calendar write interface), for example, an Exchange calendar has an EWS service interface, and a nailed schedule has an open service.
It can be understood that, in the step B), the timing task is set at one side of the unified schedule center to actively call the standard calendar query interface of the third-party calendar application to obtain data, and actually, the task may also be actively set at the cloud, and the cloud calls the standard calendar query interface of the third-party calendar application through the timing task to query and obtain calendar data, and configures the obtained calendar data according to the standard schedule interface of the unified schedule center and sends the calendar data to the unified schedule center.
S102: and the unified schedule center configures the synchronized calendar data according to calendar writing interfaces provided by other calendar applications and then synchronously writes the synchronized calendar data into other calendar applications in real time.
The different calendar applications are associated through the account, the unified schedule center can associate the calendar data of the different calendar applications based on the account, once the calendar data of one calendar application changes, the unified schedule center can acquire the changed calendar data, and the changed calendar data can be synchronized to other associated calendar applications.
Specifically, referring to fig. 3, the present step includes:
firstly, when calendar data changes, the unified schedule center asynchronously sends the calendar data to the message queue MQ, and introduces the message queue MQ, mainly ensuring the reliability of data sending, for example, retransmitting the data if the data sending fails.
Secondly, the distribution service monitors the calendar data of the message queue, on one hand, the distribution service issues the calendar data of the message queue to the client calendar application, and the client calendar application calls a standard calendar writing interface of the client to write the calendar data into the client calendar application; on the other hand, the calendar data of the message queue is used for configuring the calendar writing interface of other third-party calendar applications needing log data synchronization, such as configuring various parameters of the interface.
It will be appreciated that different interfaces have different definitions of parameters, and therefore the invention needs to be implemented by combining the definitions of the parameters of the interfaces when querying or writing data through calling the interfaces, for example, for the calendar application 1, the parameters of the standard calendar querying interface or the calendar writing interface may be: schedule title, schedule start time, schedule end time, while the parameters of the standard calendar query interface or calendar write interface for calendar application 2 may in turn be: the calendar data is inquired by calling a standard calendar inquiry interface, the data transmitted by the interface is determined by combining the parameter definition of the interface, and similarly, the calendar data is written by calling a calendar writing interface, and the specific data of each parameter written into the interface is determined by combining the parameter definition of the interface.
Preferably, the method further comprises: and the unified schedule center persists the calendar data synchronously uploaded to a local database. And the unified schedule center compares each newly acquired calendar data with the calendar data of the local database to judge whether the calendar data belong to the calendar data with repeated travel, and if not, the newly acquired calendar data are written in. Specifically, the comparison of calendar data includes: extracting three information of a schedule title, a schedule starting time and a schedule ending time from the calendar data, generating a hash character string through a summary algorithm, and judging whether the calendar data belongs to the calendar data with repeated travel or not by comparing hash values.
Example two
Referring to fig. 4, in conjunction with fig. 2 and 3, the present embodiment discloses a system for implementing bidirectional synchronization of calendar data with multiple data sources according to the first method embodiment, including a unified schedule center, a client schedule synchronization application installed on a client, and the like. The unified calendar center may also be an open service running in the cloud.
The unified schedule center is used for acquiring the calendar data synchronized in real time by different types of calendar applications based on a standard schedule interface, and configuring the synchronized calendar data according to the calendar writing interfaces provided by other calendar applications and then synchronously writing the synchronized calendar data into other calendar applications in real time.
Referring to fig. 2, in particular, the client schedule synchronization application is configured to monitor the client calendar application, and when it is monitored that the calendar changes, the changed calendar data is configured according to a standard schedule interface of the unified schedule center and is sent to the unified schedule center;
referring to fig. 2, specifically, the unified schedule center actively calls a standard calendar query interface of the third-party calendar application through the timing task to query and acquire calendar data; or the cloud integrated with various third-party calendar applications calls a standard calendar query interface of the third-party calendar applications to query and acquire calendar data through timing tasks, configures the acquired calendar data according to the standard schedule interface of the unified schedule center and sends the calendar data to the unified schedule center.
Referring to fig. 3, in particular, the unified schedule center asynchronously sends calendar data to the message queue, and the distribution service listens to the calendar data of the message queue, in particular, when there is a change in the calendar data. The distribution service configures calendar writing interfaces of other third-party calendar applications needing log data synchronization by using the calendar data of the message queue, or/and issues the calendar data of the message queue to the client calendar application, and then the client calendar application calls a standard calendar writing interface of the client to write the calendar data into the client calendar application.
The unified schedule center is also used for comparing each newly acquired calendar data with the calendar data of the local database, judging whether the calendar data belong to the calendar data with repeated travel, and writing the newly acquired calendar data if the calendar data do not belong to the calendar data with repeated travel; wherein, the comparison of the calendar data comprises: three information of schedule title, schedule starting time and schedule ending time are extracted from the calendar data, a hash character string is generated through a summary algorithm, and whether the calendar data belong to the schedule repetition or not is judged by comparing hash values.
Further details can be found in the embodiments and are not repeated herein.
Furthermore, the system of this embodiment further includes internal services such as a meeting management service and a schedule management service, and the schedule management service may acquire calendar data from the database, analyze the calendar data, and automatically invoke the meeting management service to book a meeting room. Further, calendar related services can also be shared between internal applications of our platform and the calendar management service.
In summary, the method and the system for bidirectional synchronization of calendar data with multiple data sources of the present invention have the following advantages: the invention provides a solution for unifying calendars, which can synchronize calendar data of calendar applications to a unified schedule center and then synchronize the calendar data of the calendar applications to other calendar applications from the unified schedule center, and a full-platform calendar sharing system is built, so that full-platform unified calendar data sharing is realized, bidirectional calendar synchronization is supported, and the cost is low.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. A method for bidirectional synchronization of calendar data from multiple data sources, the method comprising:
the unified schedule center acquires calendar data synchronously sent by different types of calendar applications in real time based on a standard schedule interface;
and the unified schedule center configures the synchronized calendar data according to calendar writing interfaces provided by other calendar applications and then synchronously writes the synchronized calendar data into other calendar applications in real time.
2. The method of claim 1, wherein the unified scheduling center obtains the calendar data synchronized in real time by the different types of calendar applications based on a standard scheduling interface, and the method comprises:
the client-side schedule synchronization application monitors the client-side calendar application, acquires changed calendar data when the calendar changes, configures the changed calendar data according to a standard schedule interface of a unified schedule center and sends the changed calendar data to the unified schedule center;
the unified schedule center actively calls a standard calendar query interface of the third-party calendar application through the timing task to query and acquire calendar data; or the cloud integrated with various third-party calendar applications calls a standard calendar query interface of the third-party calendar applications to query and acquire calendar data through the timing task, and configures the acquired calendar data according to the standard schedule interface of the unified schedule center and sends the calendar data to the unified schedule center.
3. The method of claim 1, wherein the step of the unified scheduling center synchronously writing the synchronized calendar data into other calendar applications in real time after configuring the synchronized calendar data according to calendar writing interfaces provided by the other calendar applications comprises:
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, configures calendar writing interfaces of other third-party calendar applications needing log data synchronization by using the calendar data of the message queue, or/and issues the calendar data of the message queue to the client calendar application, and the client calendar application calls a standard calendar writing interface of the client to write the calendar data into the client calendar application.
4. The method of claim 1, further comprising: when the unified schedule center acquires the calendar data synchronized by the calendar application in real time, comparing each newly acquired calendar data with the calendar data of the local database, judging whether the newly acquired calendar data belong to the calendar data with repeated travel, and if not, persisting the newly acquired calendar data to the local database.
5. The method of claim 4, wherein the matching of calendar data comprises: three information of schedule title, schedule starting time and schedule ending time are extracted from the calendar data, a hash character string is generated through a summary algorithm, and whether the calendar data belong to the schedule repetition or not is judged by comparing hash values.
6. A bidirectional synchronization system for calendar data with multiple data sources for implementing the method as claimed in any one of claims 1 to 5, comprising a unified schedule center for acquiring the calendar data synchronized in real time by different types of calendar applications based on a standard schedule interface, and for configuring the synchronized calendar data according to the calendar writing interface provided by other calendar applications and then synchronously writing the configured data into other calendar applications in real time.
7. The system of claim 6, further comprising a client schedule synchronization application installed at the client for monitoring the client calendar application, and when monitoring that the calendar changes, configuring the changed calendar data according to the standard schedule interface of the unified schedule center and sending the changed calendar data to the unified schedule center;
the unified schedule center is specifically used for actively calling a standard calendar query interface of a third-party calendar application through a timing task to query and acquire calendar data; or the cloud integrated with various third-party calendar applications calls a standard calendar query interface of the third-party calendar applications to query and acquire calendar data through timing tasks, configures the acquired calendar data according to the standard schedule interface of the unified schedule center and sends the calendar data to the unified schedule center.
8. The system of claim 6, wherein the unified scheduling center asynchronously sends the calendar data to the message queue when the calendar data changes, the distribution service monitors the calendar data of the message queue, and configures calendar write interfaces of other third-party calendar applications that need to synchronize log data by using the calendar data of the message queue, or/and sends the calendar data of the message queue to the client calendar application, and the client calendar application calls a standard calendar write interface of the client to write the calendar data into the client calendar application.
9. The system of claim 6,
when the unified schedule center acquires the calendar data synchronized by the calendar application in real time, the unified schedule center compares each newly acquired calendar data with the calendar data of the local database to judge whether the newly acquired calendar data belong to the calendar data with repeated travel, and if not, the newly acquired calendar data are persisted to the local database.
10. The system of claim 9, wherein the comparison of calendar data comprises: extracting three information of a schedule title, a schedule starting time and a schedule ending time from the calendar data, generating a hash character string through a summary algorithm, and judging whether the calendar data belongs to the calendar data with repeated travel or not by comparing hash values.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110434231.3A CN115221239A (en) | 2021-04-21 | 2021-04-21 | Multi-data-source calendar data bidirectional synchronization method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110434231.3A CN115221239A (en) | 2021-04-21 | 2021-04-21 | Multi-data-source calendar data bidirectional synchronization method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115221239A true CN115221239A (en) | 2022-10-21 |
Family
ID=83606631
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110434231.3A Pending CN115221239A (en) | 2021-04-21 | 2021-04-21 | Multi-data-source calendar data bidirectional synchronization method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115221239A (en) |
-
2021
- 2021-04-21 CN CN202110434231.3A patent/CN115221239A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2010226162B2 (en) | Integration of pre-meeting and post-meeting experience into a meeting lifecycle | |
| US9213952B2 (en) | Automatic scheduling tool | |
| US9953465B2 (en) | Methods and systems for creating online unified contact and communication management (CM) platform | |
| CN112069265B (en) | Synchronization method of configuration data, business data system, computer system and medium | |
| CN101466077B (en) | System, device and method for implementing synchronization of presentation information and schedule information | |
| EP1829286A1 (en) | Systems and methods for continuous pim synchronization between a host computer and a client handheld device | |
| US20020116467A1 (en) | Method and apparatus for synchronizing an email client on a portable computer system with an email client on a desktop computer | |
| EP2275981A1 (en) | Distributed system and method for management of multiple users and workspaces | |
| US7783712B2 (en) | System and method for bi-directional synchronized conversion of electronic mail data | |
| US20060149828A1 (en) | Method and system for conducting client-to-server or peer-to-peer or mixed mode data synchronization | |
| TW201019246A (en) | Delegation of calendar functions | |
| US11288637B2 (en) | Systems and methods for analytics integration into electronic applications | |
| CN101895579A (en) | Address book synchronization method and system | |
| JP4575591B2 (en) | Meeting requests and group scheduling generation from mobile devices | |
| JP6185488B2 (en) | Retrieving availability information from public calendars | |
| CN110213156A (en) | A kind of span centre heart group's instant communicating method and system | |
| US20100318397A1 (en) | Synchronizing delegation models between disparate servers | |
| CN111460038A (en) | Quasi-real-time data synchronization method and device | |
| CN115221239A (en) | Multi-data-source calendar data bidirectional synchronization method and system | |
| CN115629909A (en) | Service data processing method and device, electronic equipment and storage medium | |
| WO2008122223A1 (en) | A method, a system and a device for managing calendar events | |
| CN114095510A (en) | Multi-calendar account synchronization and processing method and device, electronic equipment and storage medium | |
| CN103532827A (en) | System and method for realizing address book function by extending XMPP (Extensible Messaging and Presence Protocol) | |
| CN112767220A (en) | Emergency management communication method, system, storage medium and computer equipment | |
| CN114615025B (en) | Key synchronization processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |