CN114095510A

CN114095510A - Multi-calendar account synchronization and processing method and device, electronic equipment and storage medium

Info

Publication number: CN114095510A
Application number: CN202010758049.9A
Authority: CN
Inventors: 黄铁鸣; 黄小刚; 杨培艺; 林莉; 李斌; 赵东
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-07-31
Filing date: 2020-07-31
Publication date: 2022-02-25
Anticipated expiration: 2040-07-31
Also published as: CN114095510B

Abstract

The application discloses a multi-calendar account synchronization method and device, a processing method and device, electronic equipment and a storage medium of an application program, which are applied to the technical field of communication.

Description

Multi-calendar account synchronization and processing method and device, electronic equipment and storage medium

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for synchronizing multiple calendar accounts of an application, a method and an apparatus for processing multiple calendar accounts, an electronic device, and a storage medium.

Background

With the continuous development of science and technology, various application programs emerge endlessly. Many applications have their own private calendars built in. Calendars are widely used in a variety of applications. At present, each application program only supports the own private calendar protocol, so that only the built-in private calendar book can be used, and other calendar books except the own private calendar book cannot be integrated at the same time.

Disclosure of Invention

The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

The application provides a multi-calendar account synchronization method and device of an application program, a multi-calendar account processing method and device, an electronic device and a storage medium, so that the application program can integrate a plurality of calendars of a plurality of calendar accounts, and a user can synchronize or operate the plurality of calendars of the plurality of calendar accounts conveniently.

According to a first aspect of the present application, there is provided a method for multi-calendar account synchronization of an application program, comprising:

acquiring all calendar books of all calendar accounts, wherein the calendar accounts are at least one of added calendar accounts or application built-in calendar accounts;

acquiring calendar protocol information corresponding to each calendar book;

sending a schedule synchronization request to a calendar server according to the calendar protocol information;

receiving schedule information returned by the calendar server;

and updating and displaying the schedule information.

According to a second aspect of the present application, there is provided a multi-calendar account processing method of an application program, including:

acquiring the selected calendar book;

acquiring protocol information of the calendar account where the selected calendar book is located;

receiving a schedule operation instruction, wherein the schedule operation instruction is any one of a schedule adding instruction, a schedule deleting instruction and a schedule updating instruction;

sending a schedule request to a calendar server according to the calendar protocol information and the schedule operation instruction;

receiving schedule information returned by the calendar server;

and updating and displaying the schedule information.

According to a third aspect of the present application, there is provided a multi-calendar account synchronization apparatus of an application program, including:

the calendar book acquisition module is used for acquiring all calendar books of all calendar accounts, wherein the calendar accounts are at least one of added calendar accounts or application built-in calendar accounts;

the protocol information acquisition module is used for acquiring calendar protocol information corresponding to each calendar book;

the schedule synchronization request module is used for sending a schedule synchronization request to the calendar server according to the calendar protocol information;

the schedule receiving module is used for receiving schedule information returned by the calendar server;

and the schedule information updating module is used for updating and displaying the schedule information.

According to a fourth aspect of the present application, there is provided a multi-calendar account processing apparatus of an application program, including:

the calendar book acquisition module is used for acquiring the selected calendar book;

the protocol acquisition module is used for acquiring protocol information of the calendar account where the selected calendar book is located;

the instruction receiving module is used for receiving a schedule operation instruction, wherein the schedule operation instruction is any one of a schedule adding instruction, a schedule deleting instruction and a schedule updating instruction;

the schedule request module is used for sending a schedule request to a calendar server according to the protocol information and the schedule operation instruction;

the schedule information receiving module is used for receiving the schedule information returned by the calendar server;

and the schedule updating module is used for updating and displaying the schedule information.

According to a fifth aspect of the present application, there is provided an electronic device comprising:

at least one memory;

at least one processor;

at least one program;

the programs are stored in the memory, and the processor executes the at least one program to implement the method for multi-calendar account synchronization of an application program according to the first aspect of the present application, or to implement the method for multi-calendar account processing of an application program according to the second aspect of the present application.

According to a sixth aspect of the present application, there is provided a computer-readable storage medium, wherein the computer-executable instructions are used for executing the method for synchronizing multiple calendar accounts of the application program according to the first aspect of the present application, or for implementing the method for processing multiple calendar accounts of the application program according to the second aspect of the present application.

According to the technical scheme, all calendar books of all calendar accounts are acquired, the calendar protocol information corresponding to each calendar book is acquired, and the schedule synchronization request is sent to the calendar server according to the calendar protocol information, so that the schedule information returned by the calendar server according to the schedule synchronization request is received, the schedule information is updated and displayed, the calendar books with the built-in calendar accounts and the calendar books with other added calendar accounts can be integrated in the application program, and a user can synchronize or operate the calendar books of a plurality of calendar accounts in the application program conveniently.

Drawings

The accompanying drawings are included to provide a further understanding of the claimed subject matter and are incorporated in and constitute a part of this specification, illustrate embodiments of the subject matter and together with the description serve to explain the principles of the subject matter and not to limit the subject matter.

FIG. 1 is a schematic diagram of an application scenario of a multi-calendar account synchronization method for an application program according to an exemplary embodiment of the application;

FIG. 2 is a flow chart of a method for multi-calendar account synchronization of an application provided by an exemplary embodiment of the present application;

FIG. 3 is a flowchart of the add calendar account step of the multiple calendar account synchronization method of the application provided in the first embodiment of the present application;

FIG. 4 is a schematic diagram of an interface for adding a calendar account via a user terminal according to a first embodiment of the present application;

FIG. 5 is a schematic diagram of another interface for adding a calendar account via a user terminal according to the first embodiment of the present application;

FIG. 6 is a schematic diagram of an interface for adding a calendar account via a user terminal according to a second embodiment of the present application;

FIG. 7 is a detailed flowchart of the add calendar account step of the multiple calendar account synchronization method of the application provided in the second embodiment of the present application;

FIG. 8 is a schematic diagram of an interface for adding a calendar account via a user terminal according to a third embodiment of the present application;

FIG. 9 is a schematic view of yet another interface for adding calendar accounts via a user terminal according to the third embodiment of the present application;

FIG. 10 is a logical level block diagram of an implementation of a method for multi-calendar account synchronization of an application provided by an exemplary embodiment of the present application;

FIG. 11 is a schematic diagram of an abstract class method for implementing the multi-calendar synchronization method at the logical layers of FIG. 10;

FIG. 12 is a flowchart of the add calendar account step of the multiple calendar account synchronization method of the application provided by the third embodiment of the present application;

fig. 13 is a flowchart of a method for processing a multi-calendar account of a first application according to an exemplary embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

It should be noted that although functional blocks are partitioned in a schematic diagram of an apparatus and a logical order is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the partitioning of blocks in the apparatus or the order in the flowchart. The terms first, second and the like in the description and in the claims, and the drawings described above, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

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 herein is for the purpose of describing embodiments of the invention only and is not intended to be limiting of the invention.

First, several terms referred to in the present application are resolved:

and (3) calendar protocol: the protocol is a synchronization protocol of calendar information, and comprises a built-in private calendar protocol and a built-in public calendar protocol; wherein the public calendar protocol at least comprises Exchange Activesync calendar protocol and Caldav calendar protocol.

Exchange Activesync calendar protocol: the method is a synchronization protocol and can be used for synchronizing the user terminal with the Exchange server so as to realize synchronization of e-mails, calendar information, contacts, tasks and the like.

Caldav calendar protocol: the method is a synchronous protocol and an open protocol, and can be used for synchronizing the user terminal with a corresponding server so as to realize synchronization of e-mails, calendar information and the like.

Profile: the method is an abstract class, and can encapsulate a corresponding operation method to realize the processing of the account.

The scheme provided by the embodiment of the application relates to a method, a device, an electronic device and a storage medium for synchronizing multiple calendar accounts of an application program, and is specifically explained by the following embodiment, which first describes a method for synchronizing multiple calendar accounts of an application program in the embodiment of the application.

The embodiment of the application provides a multi-calendar account synchronization method for an application program, which can be applied to a terminal, a server side and software running in the terminal or the server side. In some embodiments, the terminal may be a smartphone, tablet, laptop, desktop computer, smart watch, or the like; the server side can be configured into an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and cloud servers for providing basic cloud computing services such as cloud service, a cloud database, cloud computing, cloud functions, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN (content delivery network) and big data and artificial intelligence platforms; the software may be a calendar application or the like that synchronizes to multiple calendar accounts, but is not limited to the above form.

Fig. 1 is a schematic application scenario of a multi-calendar account synchronization method for an application, which is applied to a user terminal installed with an application, where the user terminal may be, but is not limited to, a tablet computer, a smart phone, and the like, the user terminal is used for being in communication connection with a backend server of the application, and the backend server of the application is used for managing the application running on the user terminal, for example, updating the application; the user terminal is also used for communication connection with the calendar server for schedule data transmission, such as acquiring schedule information from the calendar server, synchronizing the schedule information created by the user terminal to the calendar server, and the like. The calendar server is a server corresponding to a corresponding calendar protocol, and may be, for example, a server corresponding to Exchange Activesync calendar protocol or a server corresponding to Caldav calendar protocol.

Fig. 2 is an alternative flowchart of a method for synchronizing multiple calendar accounts of an application program according to an embodiment of the present application, where the method in fig. 2 includes steps 201 to 205. The multi-calendar account synchronization method is applied to an application program of a user terminal, and a private calendar is built in the application program.

Step 201, obtaining all calendar books of all calendar accounts.

Step 202, obtaining calendar protocol information corresponding to each calendar book.

Step 203, sending a schedule synchronization request to the calendar server according to the calendar protocol information. The calendar server stores schedule information of account information.

And step 204, receiving schedule information returned by the calendar server. The calendar server is used for returning corresponding schedule information according to the received schedule synchronization request after receiving the schedule synchronization request.

And step 205, updating and displaying the schedule information. In some embodiments, the schedule information can include, but is not limited to including, a schedule list, a schedule name, a schedule description, a schedule duration, a time at which the schedule begins, a calendar to which the schedule belongs, a schedule reminder period, a participant, etc.; if a plurality of schedules exist, displaying the schedules in a schedule list mode; the schedule description can be used to describe summary content, topics, etc. of the schedule; the duration of the schedule can be set by setting the duration of the schedule; the time for starting the schedule is set, so that the preset time before the schedule is started can be set for reminding; by setting the participants, the schedule information can be shared to the corresponding participants; in some embodiments, the calendar account associated with the participant person adding the schedule information is also a contact in the address book of the application program, so that the user can select a corresponding participant contact from the address book of the application program according to needs or preferences.

In some embodiments, the calendar account is at least one of an added calendar account or an in-app calendar account. In an actual application scene, the calendar account built in the application program refers to a calendar account generated by the user through the registration of the application program; an added calendar account refers to a calendar account of other account numbers that the user adds through the application. In this embodiment, the added calendar account may be a mailbox account.

In some embodiments, the calendar protocol information corresponding to the added calendar account includes a private calendar protocol built in by the application program and a public calendar protocol configured by a backend server of the application program; the protocol information may include, but is not limited to including, protocol type; the protocol information may also include a protocol data field; further, the calendar protocol information corresponding to the added calendar account comprises a protocol type and a protocol data field corresponding to the added calendar account; furthermore, the protocol type corresponding to the added calendar account further comprises a private calendar protocol built in the application program and a public calendar protocol configured by the background server of the application program, and the protocol type corresponding to the added calendar account further comprises a private calendar protocol data field built in the application program and a public calendar protocol data field configured by the background server of the application program. In a practical application scenario, the private calendar protocol built in the application may include, but is not limited to, a private calendar protocol stored in a configuration file of a terminal or a server side running the application, for example, a private calendar protocol of an operator of the application or a calendar protocol corresponding to an enterprise mailbox.

In some embodiments, the public calendar protocol may include, but is not limited to including at least one of Exchange Activesync calendar protocol and callav calendar protocol. In some other embodiments, the public calendar protocol may also include other calendar protocols besides the ExchangeActivesync calendar protocol and the Caldav calendar protocol.

In some embodiments, the method for synchronizing multiple calendar accounts further comprises the step of updating the displayed calendar accounts, the step of updating the displayed calendar accounts comprising:

receiving a calendar operating instruction through an application program;

and updating the corresponding schedule events of the display account information, the unconcealed calendar and the unconcealed calendar according to the calendar operating instruction, wherein the operating instruction is any one of a calendar adding instruction, a calendar deleting instruction, a calendar hiding instruction and a calendar attribute modifying instruction.

In practical applications, the calendar attributes include at least one or more of the following: calendar name, calendar label, description of calendar. The calendar book adding instruction is used for adding a calendar book, so that the needed calendar book can be added; the calendar deleting instruction is used for deleting the calendar, so that a user can conveniently delete the calendar which is not needed according to needs or preferences; the calendar book hiding instruction is used for hiding the calendar book and the corresponding schedule event of the hidden calendar book, so that a user can set the calendar book which does not need to be displayed as hidden according to needs or preferences, and the schedule event corresponding to the hidden calendar book can be hidden; when a user needs to display the concealed calendar book, the concealment can be cancelled, so that the concealed calendar book and the schedule information corresponding to the calendar book can be displayed again; the calendar attribute modification instruction is used for modifying the calendar attributes, so that a user can modify the calendar attributes according to needs or preferences, for example, the name of the calendar can be modified so as to classify and distinguish the calendar; in the embodiment of the application, the display color is used as the calendar mark, the display color of the calendar can be modified so as to be convenient for distinguishing a plurality of different calendars, and the individual preference is visually met or the individual display is carried out, or the importance and urgency of the calendars can be conveniently and quickly judged through vision.

In other embodiments, the updating the displayed calendar account step further comprises: the operation instruction responding step specifically comprises the following steps:

receiving an operation instruction through an application program;

sending the received operation instruction to a corresponding calendar book of a corresponding calendar account;

the calendar account logs in and schedules are synchronized according to a schedule protocol stored by the calendar account;

storing the schedule information with synchronous schedule to the corresponding calendar book of the corresponding calendar account;

the application displays schedule information of a corresponding calendar book of the corresponding calendar account.

In some embodiments, the operation instructions at least include an account operation instruction for operating an account, a calendar operation instruction for operating a calendar, and a schedule operation instruction for operating a schedule; the calendar book operation instruction at least comprises a calendar book adding instruction, a calendar book deleting instruction, a calendar book hiding instruction and a calendar book attribute modifying instruction; the account operation instruction at least comprises a calendar account adding instruction, a calendar account deleting instruction and a calendar account obtaining instruction; the schedule operation instruction is any one of a schedule adding instruction, a schedule deleting instruction, a schedule updating instruction and a schedule storing instruction. In the above embodiment, if the operation instruction is a calendar account addition instruction, the login and schedule synchronization of the calendar account can be realized according to a schedule protocol stored in the calendar account.

In some embodiments, step 201 includes at least:

acquiring account information of all calendar accounts;

and calling a synchronous interface program to obtain all the calendar books corresponding to each account information. In practical application, the account information of all calendar accounts can be acquired through the calendar account acquisition instruction, and after the account information of all calendar accounts is acquired, the synchronous interface program is called, so that all calendar books of the calendar account corresponding to each account information are acquired through the synchronous interface program, and all calendar books of all calendar accounts are acquired.

In some embodiments, step 203 comprises at least:

acquiring a protocol type according to the calendar protocol information;

calling a corresponding calendar protocol according to the protocol type;

and sending a schedule synchronization request to a corresponding calendar server according to the calendar protocol. In practical application, the calendar protocol comprises at least one of Exchange Activesync calendar protocol and Caldav calendar protocol; after the protocol type is acquired according to the calendar protocol information, the corresponding calendar protocol can be called according to the protocol type, so that a schedule synchronization request is sent to the corresponding calendar server according to the called calendar protocol. The multi-calendar account synchronization method of the application program further comprises a calendar account adding or deleting step, the calendar account adding step can be realized through a calendar account adding instruction, and the calendar account deleting step can be realized through a calendar account deleting instruction. Referring to fig. 3, the calendar account adding step of the first embodiment of the present application includes steps 301 to 303.

Step 301, receiving account information of an account to be added. In some embodiments, the account information may include, but is not limited to including, an account number. The account information may also include a password.

In an actual application scenario, taking an account as a mailbox account for example, step 301 may include: receiving an account number of a calendar account to be added, which is input through a user terminal, and receiving a confirmation instruction triggered through the user terminal; specifically, referring to fig. 4, fig. 4 is an interface schematic diagram of adding a calendar account, which is described by taking a user terminal as a mobile phone and taking a mailbox account number of zhangsan03@ company.com as an example, where an account number to be added with a calendar account is an enterprise mailbox account number zhangsan03@ company.com, and step 301 includes: receiving an account number of a calendar account to be added input through a user terminal, receiving a confirmation instruction triggered by the user terminal, and receiving a password of the calendar account to be added input through the user terminal, and in combination with fig. 4 and 5, a user can input a calendar account zhangsan03@ company.com to be added through the user terminal, trigger a "next step" confirmation instruction through the user terminal, input a password of the calendar book to be added through the user terminal, and trigger a "next step" confirmation instruction through the user terminal. And acquiring account information of the account to be added through a series of operations of the user. In other application scenarios, step 301 includes: the method comprises the steps of receiving an account number and a password of a calendar account to be added, which are input through a user terminal, and receiving a confirmation instruction triggered through the user terminal, namely, the user can input the account number and the password of the calendar account to be added on the same operation interface through the user terminal and trigger a next confirmation instruction through the user terminal.

Step 302, obtaining calendar server configuration information according to the account information.

In some embodiments, taking an account as a mailbox account for example, the calendar server configuration information includes a mailbox type, an account, a server address, an SSL protocol port number, a non-SSL protocol port number, and the like, where the mailbox type may be, but is not limited to, POP3, SMTP, IMAP; the account number is the mailbox address of the corresponding calendar account. The embodiment of the present application is not limited to the calendar server configuration information.

And step 303, creating an account to be added according to the configuration information of the calendar server.

In some embodiments, step 302, comprises:

inquiring calendar server configuration information from a user terminal running an application program according to account information to be added;

and if the configuration information of the calendar server is inquired, acquiring the configuration information of the calendar server.

Step 304, allocating an independent storage area to store the newly added calendar account. In the embodiment of the application, because the calendar accounts are stored through the independent storage areas, the calendar accounts are independent from each other, each calendar account is physically and logically isolated, and each calendar book is respectively and independently stored, so that even if one calendar book is abnormal (such as synchronization failure), the other calendar books cannot be influenced; and the schedule information is stored in the independent data space corresponding to the calendar account, so that the operation (such as synchronous operation, adding operation, deleting operation, updating operation and the like) on one schedule information does not influence other schedule information.

In some embodiments, the calendar account deletion step comprises:

sending a calendar account deletion request to a calendar server;

receiving an account deleting result returned by the calendar server;

and if the account deleting result is successful, deleting the calendar account in the storage area. In practical application, the calendar account deleting step can delete the calendar account needing to be deleted; on the display interface of the user terminal, the corresponding calendar account in the storage area can be deleted only by one-key deletion, and the operation is simple and convenient. And if the calendar account is stored in the independent storage area, deleting the calendar account corresponding to the independent storage area, or deleting the independent storage area and the calendar account stored in the independent storage area together, and reallocating the independent storage area to store the newly added calendar account when the calendar account needs to be added.

In some embodiments, the multi-calendar account synchronization method further comprises a schedule event display step, the schedule event display step comprising:

triggering schedule event display operation;

all calendar events of all calendars of all calendar accounts of the same day or of a selected day are displayed by default.

In practical application, on a schedule display interface of an application program, a user can trigger schedule event display operation through operation of a user terminal, and after the trigger, all schedule events of the current day including all schedule events of all calendar books of all calendar accounts are displayed on the schedule display interface of the application program in a default mode; the user can also select all schedule events of a certain day through the operation of the user terminal, so that all schedule events of all calendars of all calendar accounts of the selected certain day can be displayed on the schedule display interface. In addition, on the schedule display interface, it may be set to display all schedule events within a time unit of one or three days or one week according to preference or need. Wherein the schedule event comprises schedule information; the schedule information may include, but is not limited to including, a schedule list, a schedule name, a schedule description, a schedule duration, a time at which the schedule starts, a calendar book to which the schedule belongs, a schedule reminder period, participants, etc.; if a plurality of schedules exist, displaying the schedules in a schedule list mode; the schedule description can be used to describe summary content, topics, etc. of the schedule; the duration of the schedule can be set by setting the duration of the schedule; the time for starting the schedule is set, so that the preset time before the schedule is started can be set for reminding; by setting the participants, the schedule information can be shared to the corresponding participants; in some embodiments, the calendar account associated with the participant who added the schedule information is also a contact in the address book of the application program, so that the user can select the corresponding participant from the address book of the application program according to needs or preferences.

Referring to fig. 4 and 5, since the protocol type corresponding to the enterprise mailbox account zhangsan03@ company.com is a private calendar protocol built in an application program, and the calendar server configuration information corresponding to the account zhangsan03@ company.com is stored in a user terminal running the application program, the calendar server configuration information can be queried from the user terminal, so that the calendar server configuration information can be obtained.

Further, step 302 further includes:

if the calendar server configuration information is not inquired from the user terminal, inquiring the calendar server configuration information from a background server of the application program;

and if the configuration information of the calendar server is inquired, acquiring the configuration information of the calendar server. Referring to fig. 4 and 5, if the calendar server configuration information corresponding to the account zhangsan03@ company.com is not stored in the user terminal but is stored in the background server of the application program, and the protocol type corresponding to the account zhangsan03@ company.com is a private calendar protocol built in the application program, the calendar server configuration information may be queried from the background server of the application program, so that the calendar server configuration information may be acquired.

Further, step 302 further includes:

and if the calendar server configuration information is not inquired from the background server of the application program, acquiring the calendar server configuration information through the input of the user terminal. In one implementation, if the calendar server configuration information is not queried from the backend server of the application, the calendar server configuration information input by the user terminal may be received, see figure 6, on an operation interface of the user terminal for adding the calendar account, a user can input an account number, a password and select a protocol type of the account number through the user terminal, after receiving a confirmation instruction of the user for triggering "confirm" by the user china, the calendar server configuration information input by the user terminal may be obtained, which is described in this embodiment by taking account number zhangsan03@ example. Since the protocol type corresponding to the account zhangsan03@ example. com is not a private calendar protocol built into the application, and the calendar server configuration information corresponding to the account number zhangsan03@ example.com is not stored in the user terminal running the application program, nor in the background server of the application program, and can be acquired by receiving the input of the user terminal: the system comprises a protocol type, an account and a password, wherein the protocol type can select an Exchange Activesync calendar protocol or a Caldav calendar protocol; in addition, the user can also check whether the option of 'adding the account at the computer end at the same time' is available through the user terminal, and if the user checks the option of 'adding the account at the computer end at the same time' through the user terminal, the account added at the user terminal can be added to the computer end at the same time when the computer end logs in the application program.

In some embodiments, step 303 comprises:

sending an account adding request to a corresponding calendar server according to the acquired calendar server configuration information;

receiving a verification result returned by the calendar server according to the account adding request; the calendar server is used for verifying the configuration information of the calendar server, and if the configuration information passes the verification, a verification success result is returned; if the verification fails, returning a verification failure result;

if the received verification result is a verification failure result, outputting login error information so as to display a prompt of the login error information through the user terminal; in one embodiment, the login error information may be displayed by the user terminal: "cannot connect to the server, please check the configuration".

And if the received verification result is a verification success result, creating the account to be added.

In step 303, the account addition request may include, but is not limited to including, an account number, a password; the calendar server verifies whether the account number and the password are correct or not according to the account number and the password, if the account number and the password are correct, the calendar server returns a verification success result, and an account to be added can be created; and if the verification account number and the password are incorrect, returning a verification failure result by the calendar server, and outputting login error information if the account to be added cannot be created, so that a prompt of the login error information is displayed through the user terminal.

In some embodiments, further, step 204 comprises at least:

receiving schedule information returned by the calendar server according to the calendar protocol information;

and sending the received schedule information to a corresponding calendar book of the corresponding calendar account.

In some embodiments, sending the received schedule information to a corresponding calendar book of a respective calendar account includes:

converting the received schedule information into a schedule structure template of a general schedule field;

and sending the converted schedule information to a corresponding calendar book of the corresponding calendar account.

In practical application, the calendar server returns corresponding schedule information according to the received schedule synchronization request after receiving the schedule synchronization request; the application program receives schedule information returned by the calendar server according to the calendar protocol information, converts the received schedule information into a schedule structure template of a general schedule field meeting the requirements of the user terminal, wherein the schedule structure template comprises the general schedule field, sends the converted schedule information to a corresponding calendar book of a corresponding calendar account and stores the schedule information into a corresponding independent data space of the calendar book, so that the schedule information is ensured to be stored in the corresponding independent data space, and the influence of certain schedule information on other schedule information is avoided.

In some embodiments, step 205 includes at least:

and displaying the schedule information of the calendar which is not hidden. Therefore, the user can set the calendar which does not need to be displayed as hidden according to the needs or the preferences; when the user needs to display the concealed calendar, the concealment can be cancelled, so that the concealed calendar and the schedule information corresponding to the calendar can be displayed again. In some embodiments, after step 205, the method for synchronizing multiple calendar accounts of an application further comprises:

and storing the schedule information in an independent data space corresponding to the calendar account. In some embodiments, each calendar account is stored in a separate database, and each schedule information is stored in a separate data space in the separate database, so that each calendar account is independent from another calendar account, each calendar account is physically and logically isolated, and since each schedule information is stored in a separate data space, an operation (e.g., a synchronization operation, a deletion operation, an update operation, etc.) performed on one of the schedule information does not affect other schedule information. Specifically, the independent data space may be different memory partitions divided in the same database, or may be memory spaces of different databases. For example, the independent data space may be a storage space of a database such as Oracle, DB2, PostgreSQL, Microsoft SQL Server, Microsoft Access, MySQL, or may be a plurality of storage partitions under a certain database (e.g., MySQL).

Referring to fig. 7, the step of adding a calendar account provided in the second embodiment of the present application includes steps 701 to 710:

step 701, receiving account information of a calendar to be added, which is input through a user terminal; the account information may include, but is not limited to including, an account number; the account information may also include a password;

step 702, judging whether the account information of the calendar account to be added is matched with the calendar server configuration information built in the user terminal; if so, executing step 703, otherwise, executing step 707;

step 703, creating an account profile library according to the account information;

step 704, logging in a calendar server according to the received account information; further, acquiring protocol information corresponding to the calendar account to be added according to the received account information, and logging in a corresponding calendar server according to the protocol information;

step 705, judging whether the calendar server is successfully logged in; if the calendar server is successfully logged in, executing step 706; otherwise, ending;

step 706, storing the login information; thus, the process of adding a calendar account ends; the login information at least comprises received account information, login time and the like;

step 707, inquiring matched calendar server configuration information from a background server of the application program according to the account information of the calendar book to be added;

step 708, judging whether the matched calendar server configuration information is inquired, and if the matched calendar server configuration information is inquired, executing step 703; otherwise, go to step 709;

step 709, receiving calendar server configuration information input through the user terminal;

step 710, displaying an account configuration result through a user terminal; specifically, the account setting result is displayed on the user terminal according to the calendar server configuration information input by the user terminal.

Fig. 8 is an interface schematic diagram of adding a calendar account through a user terminal according to a third embodiment of the present application, in this embodiment, a user terminal is taken as a mobile phone for example, and a calendar account to be added is: com, the account number is: zhangsan @ company.com, a calendar account zhangsan @ company.com to be added, which is input by a user terminal, is included in calendar server configuration information of a background server of the user terminal or an application program, and the suffix is a company mailbox of the company.com, so that the configuration is not required to be input by the user terminal, at the moment, a password (refer to fig. 5) needs to be input by the user terminal according to the method shown in fig. 8, if the input user name and the password are correct, an account Profile library is created according to account information, a calendar server is logged in, and login information is stored after the calendar server is successfully logged in; and through the user terminal, the user terminal can also check 'the account is added at the computer terminal at the same time' according to the requirement, so that the corresponding calendar account is synchronously added to the computer terminal. Referring to fig. 9, two calendar accounts that have been added are displayed on the schedule setting interface of the application: zhangsan @ company.com and 222222222@ example.com, all calendar accounts currently added are displayed by the user terminal. In addition, through the user terminal, a default calendar can be set according to needs or preferences, for example, a calendar book "friend birthday" is set as the default calendar, a "synchronization system calendar" is set, and if the "synchronization system calendar" is set, the system calendar of the user terminal can be synchronized and displayed together with the calendar book of the calendar account that has been added.

In one embodiment, the application program is enterprise WeChat, a private calendar account is built in the enterprise WeChat, the private calendar account comprises a private calendar book, and if other calendar accounts are not added, the calendar book of the private calendar account built in the enterprise WeChat can be used as a default calendar book. If the enterprise WeChat has a plurality of calendar books, the default calendar book can be reset according to the needs or preferences of the user. Through the multi-calendar account synchronization method, the private calendar accounts built in the enterprise WeChat can be processed, other added calendar accounts can be processed, the calendar accounts are integrated together to be uniformly displayed and uniformly processed, and inconvenience of a user in processing the calendar accounts is solved. In the embodiment of the application, besides supporting the private calendar protocol built in the enterprise WeChat, the method at least supports other public calendar protocols such as Exchange Activesync calendar protocol and Caldav calendar protocol, and at least allows a user to add calendar accounts of the Exchange Activesync and Caldav calendar protocol, thereby supporting the addition of a plurality of calendar accounts with different protocol types.

Fig. 10 is a logical layer structure diagram implemented by a multi-calendar account synchronization method of an application according to an exemplary embodiment of the present application, where the logical layer structure implementing the multi-calendar account synchronization method according to the embodiment of the present application includes an account layer, a logical abstraction layer, and a User Interface (UI) layer. The account layer comprises a protocol layer and a storage layer, and the storage layer is used for storing account information, schedule information and the like of the calendar account; the protocol layer is used for realizing the login and schedule information synchronization of each calendar account, and specifically comprises the following steps: and acquiring schedule information and account information returned by the calendar server through the calendar protocol information, so that all calendar books of all calendar accounts can be acquired. The logic abstraction layer is used for managing all calendar accounts, providing a uniform schedule management and synchronization interface for the UI layer, forwarding the request of the UI layer to the corresponding calendar account, sending the schedule information and the account information returned by the calendar server to the corresponding calendar account, and converting the received schedule information into a general schedule structure template meeting the requirements of the user terminal before sending the schedule information. The UI layer is used for acquiring data from the logical abstraction layer and displaying the acquired data, and specifically includes: and acquiring the schedule information and the account information from the logic abstract layer through a synchronous interface program, thereby acquiring a calendar book of the calendar account corresponding to the account information.

The logical abstraction layer includes a management module and an account module. Referring to fig. 11, in an embodiment, the management module is implemented by a profile manager, and the account module is implemented by an abstract profile; the management module is used for managing all the calendar accounts, each calendar account corresponds to a unique account profile library, each account profile library is configured with a corresponding profile configuration file, and the profile manager is used for managing all the profile configuration files; the management module comprises calendar account adding, calendar account deleting and calendar account acquiring so as to realize calendar account adding and deleting; the account module is realized by an abstract profile, encapsulates a plurality of operation methods, can be used for realizing schedule synchronization operation, adding operation, updating operation, deleting operation, storing operation and the like, and each operation method is realized by a corresponding abstract profile subclass, so that each calendar account is physically and logically isolated; the abstract class profile serves as a parent class and is also used to abstract calendar protocols and storage operations into a common method abstract class, so that other operations (e.g. synchronization operations, addition operations, update operations) as subclasses of the parent class profile can call the common abstract class of the parent class profile: calendar protocol and storage operations; an abstract class profile may be used to describe each calendar account; the abstract class Prolfile comprises a Login subclass, a synchronization subclass, an addition subclass, an update subclass, a schedule deletion subclass and a storage subclass, wherein the Login subclass realizes the Login of a calendar account through a Login () method, the synchronization subclass realizes the synchronization operation through a SyncEvents () method so as to realize the synchronization of schedule information, the addition subclass realizes the addition operation through an AddEvent () method so as to realize the addition of the schedule information, the update subclass realizes the update operation through an UpdateEvent () method so as to realize the update of the schedule information, the schedule deletion subclass realizes the deletion operation through a DeleteEvent () method so as to realize the deletion of the schedule information, and the storage subclass realizes the storage operation through a SaveEvents () method so as to realize the storage of the schedule information.

The management module (ProfileManager) includes a creating unit, a deleting unit, and an acquiring unit. The creating unit realizes the addition of the calendar account through a CreateProfiles () method; the deletion unit realizes the deletion of the calendar account through a DeleteProfiles () method; the acquisition unit is used for realizing acquisition of all calendar accounts through a GetAllProfile () method.

The storage layer of the account layer stores default configuration files DefaultProfile, EAS protocol class configuration files EASPprofile and Caldav protocol class configuration files CaldavProfile. The default configuration file DefaultProfile corresponds to the relevant information of the default calendar account; the EAS protocol type configuration file EASProfile corresponds to the relevant information of the Exchange Activesync calendar protocol account; the Caldav protocol class configuration file Caldav profile corresponds to the information related to the calendar account of the Caldav protocol.

According to the embodiment of the application, on the basis that the schedule data of the private calendar account built in the application program is used as the general schedule data, a public schedule data model is abstracted, and the extended data fields are reserved for various different calendar protocols, so that the calendar accounts supporting different calendar protocols can be conveniently added. When the schedule is created, the schedule structure template displayed on the user interface layer by default is a template of a general schedule field, and after the calendar book is selected, the display interface is dynamically adjusted according to the calendar protocol type of the calendar book, so that the specific schedule field of the protocol type is displayed. The user interface layer inputs corresponding schedule information through the user terminal and then clicks and stores the schedule information, transmits the public schedule data model to the corresponding protocol layer, converts the public schedule data model into a data format required by the corresponding calendar protocol, and then transmits the data format to the calendar server so that the calendar server can return corresponding schedule data, thereby realizing schedule synchronization.

In an actual application scene, a schedule setting page, a calendar account adding page, a calendar book setting page and the like are provided on an operation interface of an application program, a user can add a calendar account, delete a calendar account, set a default calendar book, create a schedule and the like through corresponding operation pages according to needs or preferences, can hide the calendar book, and mark the calendar book with different colors according to the needs or preferences of the user so as to distinguish a plurality of different calendar books, so that the user can quickly judge the urgency of the schedule through vision, or visually meet personal preferences or perform personalized display and the like. In addition, if the calendar is set to be hidden, the schedule information of the hidden calendar is hidden and is not displayed; when the display is needed, the hiding can be set to be cancelled, so that the display can be performed again. Further, a global default setting item is provided in an operation interface for creating the schedule, so that the user can complete the operation quickly.

Based on fig. 10 and 11, fig. 12 is a flowchart of a calendar account adding step of the multi-calendar account synchronization method for an application program according to the third embodiment of the present application, where in an actual application scenario, the calendar account adding step provided in the embodiment of the present application is implemented by a UI layer, a profile manager and a profile of a logical abstraction layer, and includes the following steps:

receiving an account number and a password of a calendar account input through a user terminal;

inquiring calendar server configuration information built in a user terminal; further, inquiring calendar server configuration information built in the user terminal according to the account number and the password;

judging whether the received account and password exist in calendar server configuration information built in the user terminal;

if the received account number and password exist in the calendar server configuration information built in the user terminal, an account profile library is created according to the calendar server configuration;

if the received account and password do not exist in the calendar server configuration information built in the user terminal, inquiring the calendar server configuration information from a background server of the application program;

judging whether the received account and password exist in the calendar server configuration information of the background server of the application program;

if the received account number and password exist in the calendar server configuration of the background server of the application program, an account profile library is created according to the schedule server configuration information;

if the received account and password do not exist in the server configuration information of the background server of the application program, receiving calendar server configuration information input through a user terminal;

after the account profile library is created according to the calendar server configuration information, the method further comprises the following steps:

logging in a calendar server;

judging whether the login is successful;

if the login is successful, storing login information; wherein, the login information may include, but is not limited to including account information, the account information is not limited to including account number and password of the calendar account; the login information may also include login time;

if the login is unsuccessful, displaying login error information; in some embodiments, the login error information may be: "cannot connect to the server, please check the configuration".

And after the login information is stored, displaying an account configuration result.

According to the multi-calendar account synchronization method of the application program, all calendar books of all calendar accounts are obtained, the calendar protocol information corresponding to each calendar book is obtained, the schedule synchronization request is sent to the calendar server according to the calendar protocol information, and therefore the schedule information returned by the calendar server according to the schedule synchronization request is received, the schedule information is updated and displayed, the calendar books with the built-in calendar accounts and the calendar books with other added calendar accounts can be integrated in the application program, and a user can synchronize or operate the calendar books of the calendar accounts in the application program conveniently.

The embodiment of the application also provides a multi-calendar account processing method of the application program, which can be applied to a terminal, a server and software running in the terminal or the server. In some embodiments, the terminal may be a smartphone, tablet, laptop, desktop computer, smart watch, or the like; the server side can be configured into an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and cloud servers for providing basic cloud computing services such as cloud service, a cloud database, cloud computing, cloud functions, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN (content delivery network) and big data and artificial intelligence platforms; the software may be a calendar application or the like that handles multiple calendar accounts, but is not limited to the above form.

With reference to fig. 1, in an application scenario of the multi-calendar account processing method for an application program provided in the embodiment of the present application, the multi-calendar account processing method is applied to a user terminal installed with the application program, where the user terminal may be, but is not limited to, a tablet computer, a smart phone, and the like, the user terminal is used for being in communication connection with a background server of the application program, and the background server of the application program is used for managing the application program run by the user terminal, for example, updating the application program; the user terminal is also used for being in communication connection with the calendar server to perform schedule data transmission, for example, acquiring schedule information from the calendar server, i.e. synchronizing the schedule information generated by the user terminal through operations of creating, deleting, updating and the like of the schedule information to the calendar server and the like. The calendar server is a server corresponding to a corresponding calendar protocol, and may be, for example, a server corresponding to Exchange Activesync calendar protocol or a server corresponding to Caldav calendar protocol.

Fig. 13 is an alternative flowchart of a method for processing a multi-calendar account of an application program according to an embodiment of the present application, where the method in fig. 13 includes steps 1301 to 1306.

1301. And acquiring the selected calendar book. In some embodiments, the user may select the calendar book to be operated through the client terminal.

1302. And acquiring the calendar protocol information of the calendar account of the selected calendar book. Specifically, after the calendar book selected by the user is obtained, the calendar account where the calendar book selected by the user is located can be obtained, so that the calendar protocol information corresponding to the calendar account can be obtained; wherein the calendar protocol information may include, but is not limited to including, protocol type; further, the calendar protocol information may also include a protocol data field.

1303. And receiving a schedule operation instruction. In some embodiments, the user may trigger the schedule operation instruction through the client terminal; the schedule operation instruction is any one of a schedule adding instruction, a schedule deleting instruction, a schedule updating instruction and a schedule storing instruction. Further, the schedule adding instruction refers to an instruction for adding a schedule, the schedule deleting instruction refers to an instruction for deleting a schedule, the schedule updating instruction refers to an instruction for updating a schedule, and the schedule storing instruction refers to an instruction for storing a schedule.

1304. And sending a schedule request to the calendar server according to the calendar protocol information and the schedule operation instruction.

1305. And receiving schedule information returned by the calendar server. The calendar server is used for returning corresponding schedule information according to the received schedule request after receiving the schedule request. In some embodiments, the schedule information at least includes a schedule adding result, a schedule deleting result, a schedule updating result and a schedule storing result, corresponding to the schedule adding instruction, the schedule deleting instruction, the schedule updating instruction and the schedule storing instruction respectively.

1306. And updating and displaying the schedule information. And updating and displaying the current schedule information according to the received schedule information returned by the calendar server.

In some embodiments, after step 1035, the multi-calendar account processing method further comprises:

carrying out data format conversion on the schedule information;

and storing the converted schedule information into a corresponding calendar book of the corresponding calendar account.

The data format conversion of the schedule information refers to converting the schedule information into a format of a schedule structure template of a general schedule field on a display interface of the user terminal so as to convert the format into the schedule structure template general for the user terminal, so that when the schedule is created, the schedule structure template displayed on the user interface layer by default is the template of the general schedule field, and the converted schedule information can be stored into a corresponding calendar account so as to be conveniently displayed through the user terminal.

In some embodiments, the schedule operation instruction is an add schedule instruction, then step 1304 includes:

carrying out data format conversion on the schedule adding instruction according to the calendar protocol information;

generating a schedule request according to the schedule adding instruction after the data format conversion;

and sending a schedule request to the calendar server according to the calendar protocol information.

In step 1304, before sending a schedule request to the calendar server, data format conversion is performed on the schedule adding instruction according to the calendar protocol information, so that the generated schedule instruction can be matched with the protocol type, so that the corresponding calendar server can recognize the schedule instruction, and return corresponding schedule information according to the recognized schedule instruction.

In some embodiments, after step 1033, the multi-calendar account processing method further comprises:

defaulting a schedule structure template for displaying the general schedule field;

or displaying a schedule structure template of a schedule field corresponding to the protocol type according to the protocol type of the calendar account to which the selected calendar book belongs. In practical application, firstly, a schedule structure template of the universal schedule field is created, so that the schedule structure template of the universal schedule field is displayed by default, and uniform and universal display of schedule information is facilitated; in addition, after the calendar book is selected, the schedule structure template of the schedule field corresponding to the protocol type can be displayed according to the protocol type of the calendar account to which the selected calendar book belongs, so that the display interface can be dynamically adjusted, and the schedule field specific to the protocol type can be displayed.

In some embodiments, the schedule operation instruction is an add schedule instruction, and step 1305 includes:

receiving a schedule adding result returned by the calendar server;

and if the schedule adding result is successful, storing the newly added schedule information of the corresponding calendar book of the corresponding calendar account.

In some embodiments, adding the calendar instruction includes at least: schedule information and a trigger request; further, the schedule information may include, but is not limited to including, a schedule list, a schedule name, a schedule description, a schedule duration, a time at which the schedule begins, a calendar to which the schedule belongs, a schedule reminder period, a participant, and the like; the trigger request is generated by the user by triggering the user terminal, thereby sending a request to the calendar server. And if the schedule adding result returned by the calendar server is successful, storing the newly added schedule information of the corresponding calendar book of the corresponding calendar account.

In some embodiments, the schedule operation instruction is an add schedule instruction, then step 1306 includes:

if the schedule information does not conflict with all schedule information associated with the participants, updating and displaying the schedule information to an application program of the participants; the calendar account related to the schedule information added by the participant is also a contact in the address list of the application program. In the embodiment of the application, the user can select a corresponding participant from the address list of the application program as the calendar account associated with adding the schedule information when adding the schedule information according to needs or preferences, so as to share the newly added schedule information to the participant. In practical application, after receiving a schedule request, the calendar server judges whether the newly added schedule information conflicts with all current schedule information according to all schedule information currently associated with the participants, and if no conflict exists, the calendar server sends the newly added schedule information to the application programs of the participants, so that the application programs displayed to the participants can be updated; the determination of whether the newly added schedule information conflicts with all current schedule information means a time conflict, for example, in two identical time periods, one participant cannot participate in two schedule events at the same time, and a conflict occurs at this time.

According to the method for processing the multiple calendar accounts of the application program, the protocol information of the calendar account where the selected calendar book is located is obtained, the operation instruction is received, the schedule request is sent to the calendar server according to the calendar protocol information and the operation instruction, the schedule information returned by the calendar server according to the schedule request is received, and therefore the schedule information is updated and displayed according to the schedule information, therefore, synchronous operation, deleting operation, updating operation and the like of the calendar account built in the application program and other added calendar accounts can be achieved, and the schedule information of the multiple calendar accounts can be conveniently processed. Because the calendar accounts are mutually independent and are physically and logically isolated, even if one calendar book is abnormal (such as synchronization failure), other calendar books cannot be influenced; and the schedule information is stored in the independent data space corresponding to the calendar account, so that the operation (such as synchronous operation, deleting operation, updating operation and the like) on one schedule information does not influence other schedule information.

The embodiment of the present application further provides a device for synchronizing multiple calendar accounts of an application program, which can implement the embodiment of the method for synchronizing multiple calendar accounts of an application program, and the device includes:

The embodiment of the present application further provides a device for processing multiple calendar accounts of an application program, which can implement the embodiment of the method for processing multiple calendar accounts of the application program, and the device includes:

An embodiment of the present application further provides an electronic device, including:

at least one memory;

at least one processor;

at least one program;

the programs are stored in the memory, and the processor executes at least one of the programs to implement the multi-calendar account synchronization method of the application program or the multi-calendar account processing method of the application program. The electronic device may be any intelligent terminal including a mobile phone, a tablet computer, a Personal Digital Assistant (PDA for short), a Point of Sales (POS for short), a vehicle-mounted computer, and the like.

An embodiment of the present application further provides a computer-readable storage medium, where the computer-executable instruction is used to execute the method for synchronizing multiple calendar accounts of the application program or the method for processing multiple calendar accounts of the application program.

According to the technical scheme, all calendar books of all calendar accounts are acquired, the calendar protocol information corresponding to each calendar book is acquired, and the schedule synchronization request is sent to the calendar server according to the calendar protocol information, so that the schedule information returned by the calendar server according to the schedule synchronization request is received, and the schedule information is updated and displayed.

One of ordinary skill in the art will appreciate that all or some of the steps, systems, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.

While the preferred embodiments of the present invention have been described, the present invention is not limited to the above embodiments, and those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention, and such equivalent modifications or substitutions are included in the scope of the present invention defined by the claims.

Claims

1. A method for synchronizing multiple calendar accounts of an application program, comprising:

acquiring calendar protocol information corresponding to each calendar book;

receiving schedule information returned by the calendar server;

and updating and displaying the schedule information.

2. The method of claim 1, wherein the obtaining all calendars of all calendar accounts comprises:

acquiring account information of all calendar accounts;

and calling a synchronous interface program to obtain all the calendar books corresponding to each piece of account information.

3. The method of claim 1, wherein sending a calendar synchronization request to a calendar server according to the calendar protocol information comprises:

acquiring a protocol type according to the calendar protocol information;

calling a corresponding calendar protocol according to the protocol type, wherein the calendar protocol comprises a private calendar protocol built in the application program and a public calendar protocol configured by a background server of the application program;

and sending the schedule synchronization request to a corresponding calendar server according to the calendar protocol.

4. The method of claim 1, wherein the receiving the schedule information returned by the calendar server comprises:

5. The method according to any one of claims 1 to 4, further comprising a calendar account adding or deleting step, wherein the calendar account adding step specifically comprises:

receiving account information of a calendar account to be added;

acquiring calendar server configuration information according to the account information;

creating the calendar account to be added according to the calendar server configuration information;

allocating an independent storage area to store the newly added calendar account;

or, the calendar account deleting step specifically includes:

sending a calendar account deletion request to the calendar server;

receiving an account deleting result returned by the calendar server;

and if the account deleting result is successful, deleting the calendar account in a storage area.

6. The method of claim 5, wherein obtaining calendar server configuration information based on the account information comprises at least one of:

inquiring the calendar server configuration information from the user terminal of the application program according to the account information;

or inquiring the configuration information of the calendar server from a background server of the application program according to the account information;

or obtaining the configuration information of the calendar server by a mode input by a user terminal.

7. The method according to any one of claims 1-4, further comprising the step of updating the displayed calendar account, the step of updating the displayed calendar account comprising:

receiving a calendar operating instruction through the application program;

and updating display account information, a non-hidden calendar and a corresponding schedule event of the non-hidden calendar according to the calendar operating instruction, wherein the calendar operating instruction is any one of a calendar adding instruction, a calendar deleting instruction, a calendar hiding instruction and a calendar attribute modifying instruction.

8. The method according to any one of claims 1 to 4, further comprising a calendar event display step, in particular:

triggering schedule event display operation;

displaying all schedule events of all calendars of all calendar accounts of the same day or a selected day by default.

9. A method for processing multiple calendar accounts of an application program is characterized by comprising the following steps:

acquiring the selected calendar book;

receiving schedule information returned by the calendar server;

and updating and displaying the schedule information.

10. The method of claim 9, wherein the schedule operation instruction is an add schedule instruction, and the sending a schedule request to a calendar server according to the calendar protocol information and the schedule operation instruction comprises:

performing data format conversion on the schedule adding instruction according to the calendar protocol information;

generating the schedule request according to the schedule adding instruction after the data format conversion;

and sending the schedule request to the calendar server according to the calendar protocol information.

11. The method of claim 9, wherein the schedule operation instruction is an add schedule instruction, and after receiving the schedule operation instruction, the method further comprises:

or displaying a schedule structure template of a schedule field corresponding to the protocol type according to the protocol type of the calendar account to which the selected calendar book belongs.

12. The method of claim 11, wherein receiving the schedule information returned by the calendar server comprises:

receiving a schedule adding result returned by the calendar server;

13. The method of claim 12, wherein the updating displays the schedule information, comprising:

if the schedule information does not conflict with all schedule information associated with the participants, updating and displaying the schedule information to an application program of the participants; the participant is a calendar account associated with adding schedule information.

14. The method according to any of claims 10-13, wherein after receiving the schedule information returned by the calendar server, the method further comprises:

carrying out data format conversion on the schedule information;

and storing the converted schedule information into a corresponding calendar book of a corresponding calendar account.

15. An apparatus for synchronizing multiple calendar accounts of an application program, comprising: