CN114095510B

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

Info

Publication number: CN114095510B
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: 2024-03-29
Anticipated expiration: 2040-07-31
Also published as: CN114095510A

Abstract

The application program multi-calendar account synchronization method and device, the processing method and device, the electronic equipment and the storage medium are applied to the technical field of communication, and the calendar server receives the calendar information returned by the calendar server according to the calendar protocol information to update and display the calendar information by acquiring all the calendars of all the calendar accounts, acquiring the calendar protocol information corresponding to each calendar book and sending the calendar synchronization request to the calendar server according to the calendar protocol information, so that the calendar books of the built-in calendar accounts and the added calendar books of other 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.

Description

Multi-calendar account synchronization, 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 program, 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 are layered endlessly. Many applications embed their own private calendar. Calendar books are widely used in a number of applications. At present, each application program only supports own private calendar protocol, so that only a private calendar book built in the application program can be used, and other calendars except the private calendar book can not 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 program can integrate a plurality of calendars of a plurality of calendar accounts, and is convenient for a user to synchronize or operate the calendars of the calendar accounts.

According to a first aspect of the present application, there is provided a method for synchronizing multiple calendar accounts of an application program, including:

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

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 method for processing multiple calendar accounts of an application program, including:

acquiring a selected calendar book;

acquiring protocol information of a calendar account of the selected calendar book;

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 device for an application program, comprising:

the calendar book acquisition module acquires all calendar books of all calendar accounts, wherein the calendar accounts are at least one of added calendar accounts or calendar accounts built in application programs;

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

the calendar protocol information is used for providing calendar protocol information to a calendar server;

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 device for an application program, comprising:

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

the protocol acquisition module is used for acquiring protocol information of a calendar account where the selected calendar 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 calendar server is used for receiving the calendar information returned by the calendar information receiving module;

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 program is 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 application, or to implement the method for multi-calendar account processing of an application program according to the second aspect of the application.

According to a sixth aspect of the present application, there is provided a computer readable storage medium having computer executable instructions for performing the method for multi-calendar account synchronization of an application program according to the first aspect of the present application, or for implementing the method for multi-calendar account processing of an application program according to the second aspect of the present application.

According to the technical scheme, all calendar books of all calendar accounts are obtained, the calendar protocol information corresponding to each calendar book is obtained, and the calendar server is sent to the calendar server according to the calendar protocol information, so that the calendar information returned by the calendar server according to the calendar protocol information is received, the calendar information is updated and displayed, the calendar books of the built-in calendar accounts and the added calendar books of other 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 technical aspects of the present application, and are incorporated in and constitute a part of this specification, illustrate the technical aspects of the present application and together with the examples of the present application, and not constitute a limitation of the technical aspects of the present application.

FIG. 1 is an application scenario diagram of a method for multi-calendar account synchronization of an application provided in one exemplary embodiment of the present application;

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

FIG. 3 is a flowchart of the steps of adding calendar accounts for the method of multi-calendar account synchronization for an 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 further interface schematic for adding a calendar account via a user terminal, provided in accordance with a 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 flow chart of the step of adding calendar accounts for the method of multi-calendar account synchronization for an application provided in a 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 diagram of yet another interface for adding calendar accounts via a user terminal provided in a third embodiment of the present application;

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

FIG. 11 is a schematic diagram of an abstract class approach for implementing the multiple calendar synchronization approach for each logical layer of FIG. 10;

FIG. 12 is a flowchart of the step of adding calendar accounts for the method of multi-calendar account synchronization for an application provided by the third embodiment of the present application;

FIG. 13 is a flowchart of a method for multi-calendar account processing for a first application program in accordance with 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 application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

It should be noted that although functional block division is performed in a device diagram and a logic sequence is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the block division in the device, or in the flowchart. The terms first, second and the like in the description and in the claims and in the above-described figures, 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 nouns referred to in this application are parsed:

calendar protocol: is a synchronization protocol of calendar information, comprising a built-in private calendar protocol and a public calendar protocol; wherein the common calendar protocol includes at least Exchange Activesync calendar protocol and Caldav calendar protocol.

Exchange Activesync calendar protocol: is a synchronization protocol that can be used to synchronize user terminals with Exchange servers to achieve synchronization of email, calendar information, contacts, tasks, etc.

Caldav calendar protocol: 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-mail, calendar information and the like.

Profile: is an abstract class, and can encapsulate corresponding operation methods to realize account processing.

The scheme provided by the embodiment of the application relates to a multi-calendar account synchronization method and device of an application program, an electronic device and a storage medium, and specifically, the multi-calendar account synchronization method of the application program in the embodiment of the application program is described first through the following description of the embodiment.

The embodiment of the application provides a multi-calendar account synchronization method of 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 smart phone, tablet, notebook, desktop, or smart watch, etc.; the server side can be configured as an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligent platforms and the like; the software may be, but is not limited to, a calendar application or the like that synchronizes multiple calendar accounts.

The multi-calendar account synchronization method of the application provided in the embodiment of fig. 1 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, etc., and the user terminal is used for communication connection with a background server of the application, and the background server of the application is used for managing the application running on the user terminal, for example, updating the application, etc.; the user terminal is also adapted to be communicatively connected to a calendar server for transmission of calendar data, e.g. to obtain calendar information from the calendar server, to synchronize calendar information created by the user terminal to the calendar server, etc. The calendar server is a server corresponding to a corresponding calendar protocol, and may be a server corresponding to Exchange Activesync calendar protocol or a server corresponding to Caldav calendar protocol, for example.

Fig. 2 is an optional 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 the user terminal, and a private calendar book is arranged in the application program.

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

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

Step 203, a schedule synchronization request is sent to a calendar server according to the calendar protocol information. Wherein the calendar server stores schedule information of account information.

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.

Step 205, updating the display schedule information. In some embodiments, the calendar information may include, but is not limited to including, a calendar list, a calendar name, a calendar description, a calendar duration, a time when the calendar starts, a calendar book to which the calendar belongs, a calendar reminder period, a participant, and the like; if a plurality of schedules exist, displaying the schedules in a schedule list mode; the schedule description may be used to describe summary content, topics, etc. of the schedule; the time length occupied by the schedule can be set by setting the time length 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; the schedule information can be shared to the corresponding participants by setting the participants; in some embodiments, the calendar account associated with the participant when manually adding calendar information is also a contact in the address book of the application, so that the user may select a corresponding participant contact from the address book of the application as needed or desired.

In some embodiments, the calendar account is at least one of an added calendar account or an application built-in calendar account. In an actual application scene, the calendar account built in the application program refers to a calendar account generated by a user through application program registration; the added calendar account refers to a calendar account of other account numbers added by the user 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 the application and a public calendar protocol configured by a background server of the application; wherein the protocol information may include, but is not limited to including, a protocol type; the protocol information may also include a protocol data field; further, the calendar agreement information corresponding to the added calendar account comprises an agreement type and an agreement data field corresponding to the added calendar account; further, the protocol type corresponding to the added calendar account 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 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 an actual application scenario, the private calendar protocol built in the application program may include, but is not limited to, a private calendar protocol stored in a configuration file of a terminal or server side running the application program, for example, a private calendar protocol of an operator of the application program or a calendar protocol corresponding to an enterprise mailbox.

In some embodiments, the common calendar protocol may include, but is not limited to including, at least one of Exchange Activesync calendar protocol and Caldav calendar protocol. In some other embodiments, the common calendar protocol may also include other calendar protocols in addition to the exchange actiginesync calendar protocol and the Caldav calendar protocol.

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

receiving a calendar operation instruction through an application program;

updating and displaying account information, the calendar which is not hidden and the corresponding calendar event of the calendar which is not hidden according to the calendar operation instruction, wherein the operation instruction is any instruction 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 mark, description of calendar. The calendar book adding instruction is used for adding a calendar book, so that a required calendar book can be added; the calendar deleting instruction is used for deleting the calendar, so that a user can delete unnecessary calendars according to needs or favorites; the calendar book hiding instruction is used for hiding corresponding calendar events of the calendar book and the hidden calendar book, so that a user can set the calendar book which is not required to be displayed as being hidden according to needs or favorites, and the calendar events corresponding to the hidden calendar book can be hidden; when the user needs to display the hidden calendar, the user can set the calendar to be canceled, so that the calendar to be canceled and the schedule information corresponding to the calendar can be redisplayed; the calendar attribute modifying instruction is used for modifying the calendar attribute, so that a user can modify the calendar attribute according to needs or favorites, for example, the name of the calendar can be modified to classify and distinguish the calendars; in the embodiment of the application, the display color is used as the calendar mark, so that the display color of the calendar can be modified to facilitate the distinction of a plurality of different calendars, and the personal preference is visually satisfied or personalized display is performed, or the urgency of the calendar can be conveniently and rapidly judged through vision.

In other embodiments, the step of updating the display calendar account further comprises: the operation instruction response step specifically comprises the following steps:

receiving an operation instruction through an application program;

transmitting the received operation instruction to a corresponding calendar of the corresponding calendar account;

the calendar account carries out login and schedule synchronization of the calendar account according to the stored schedule protocol;

storing schedule information of schedule synchronization to the corresponding calendar of the corresponding calendar account;

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

In some embodiments, the operation instructions include at least an account operation instruction to operate an account, a calendar book operation instruction to operate a calendar book, and a calendar operation instruction to operate a calendar; 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 adding a schedule instruction, deleting a schedule instruction, updating a schedule instruction and storing a schedule instruction. In the above embodiment, if the operation instruction is a calendar account adding instruction, the login and schedule synchronization of the calendar account may be implemented 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 acquire all calendars corresponding to each account information. In practical application, account information of all calendar accounts can be obtained through the calendar account obtaining instruction, and after the account information of all calendar accounts is obtained, the synchronous interface program is called, so that all calendar books of the calendar accounts corresponding to each account information are obtained through the synchronous interface program, and all calendar books of all calendar accounts are obtained.

In some embodiments, step 203 comprises at least:

acquiring a protocol type according to calendar protocol information;

calling a corresponding calendar protocol according to the protocol type;

and sending a schedule synchronization request to the corresponding calendar server according to the calendar protocol. In practical applications, the calendar protocol includes at least one of Exchange Activesync calendar protocol and Caldav calendar protocol; after the protocol type is acquired according to the calendar protocol information, a corresponding calendar protocol may be called according to the protocol type, so that a schedule synchronization request is transmitted to a 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 step or a calendar account deleting step, wherein 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 number as a mailbox account number as an 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 by the user terminal; specifically, referring to fig. 4, fig. 4 is a schematic interface diagram of adding a calendar account, taking a user terminal as a mobile phone and taking a mailbox account of zhangsan03@company.com as an example for explanation, the account to be added with the calendar account is an enterprise mailbox account zhangsan03@company.com, and step 301 includes: receiving an account number of a calendar account to be added, which is input through a user terminal, receiving a confirmation instruction triggered by the user terminal, receiving a password of the calendar account to be added, which is input through the user terminal, in combination with fig. 4 and 5, the user can input the calendar account to be added zhangsan03@company.com through the user terminal, trigger a "next" confirmation instruction through the user terminal, input a password of a calendar book to be added through the user terminal, and trigger a "next" 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: receiving an account number and a password of a calendar account to be added, which are input through a user terminal, receiving a confirmation instruction triggered by 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 configuration information of the calendar server according to the account information.

In some embodiments, taking an account number as a mailbox account number as an example, the calendar server configuration information includes a mailbox type, an account number, 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 a mailbox address corresponding to a calendar account. With respect to calendar server configuration information, embodiments of the present application are not limited.

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

In some embodiments, step 302 comprises:

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

and if the calendar server configuration information is queried, acquiring the calendar server configuration information.

Step 304, an independent storage area is allocated 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 mutually independent, each calendar account is physically and logically isolated, each calendar book is respectively and independently stored, and even if one calendar book is abnormal (for example, synchronization fails), other calendar books are not influenced; 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 affect other schedule information.

In some embodiments, the calendar account deletion step includes:

sending a calendar account deletion request to a calendar server;

receiving an account deletion result returned by the calendar server;

and if the account deletion result is successful, deleting the calendar account in the storage area. In practical application, the calendar account deleting step can realize deleting the calendar account to be deleted; on the display interface of the user terminal, the corresponding calendar account in the storage area can be deleted only by deleting one key, and the operation is simple and convenient. 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 by the independent storage area together, and reassigning 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 calendar event display step comprising:

triggering schedule event display operation;

all calendar events of all calendar books of all calendar accounts of the day or of the selected day are displayed by default.

In practical application, a user can trigger a schedule event display operation through operation of a user terminal on a schedule display interface of an application program, and after the operation is triggered, all schedule events of the same day including all schedule events of all calendar books of all calendar accounts are displayed by default on the schedule display interface of the application program; the user can also select all calendar events of a certain day by operating the user terminal, so that all calendar events of all calendar books of all calendar accounts of the selected certain day can be displayed on the calendar display interface. Further, on the schedule display interface, it is possible to set to display all schedule events within a time unit of one day or three days or one week according to preference or need. Wherein the calendar event includes calendar information; the schedule information may include, but is not limited to, a schedule list, a schedule name, a schedule description, a schedule duration, a time when the schedule starts, a calendar to which the schedule belongs, a schedule reminding period, a participant, and the like; if a plurality of schedules exist, displaying the schedules in a schedule list mode; the schedule description may be used to describe summary content, topics, etc. of the schedule; the time length occupied by the schedule can be set by setting the time length 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; the schedule information can be shared to the corresponding participants by setting the participants; in some embodiments, the calendar account associated with the participant when manually adding calendar information is also a contact in the address book of the application, so that the user may select a corresponding participant from the address book of the application as needed or desired.

Referring to fig. 4 and 5, since the protocol type corresponding to the mailbox account zhangsan03@company.com of the enterprise is a private calendar protocol built in the application program, and the calendar server configuration information corresponding to the account zhangsan03@company.com is stored in the 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 configuration information of the calendar server is not queried from the user terminal, querying the configuration information of the calendar server from a background server of the application program;

and if the calendar server configuration information is queried, acquiring the calendar server configuration information. 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 because 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 can be queried from the background server of the application program, so that the calendar server configuration information can be obtained.

Further, step 302 further includes:

If the calendar server configuration information is not queried from the background server of the application program, the calendar server configuration information is acquired through the input of the user terminal. In an implementation, if the calendar server configuration information is not queried from the background server of the application program, the calendar server configuration information input by the user terminal may be received, referring to fig. 6, on an operation interface of the user terminal for adding the calendar account, the user may input an account number, a password, and select a protocol type to which the account number belongs through the user terminal, after receiving a confirmation instruction that the user triggers "determine" through user china, the calendar server configuration information input by the user terminal may be obtained, and in this embodiment, the account number zhangsan03@example.com is taken as an example, because the protocol type corresponding to the account number zhangsan03@example.com is not a private calendar protocol built in the application program, 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 the calendar server configuration information may be obtained by receiving the user terminal input: protocol type, account, password, wherein protocol type may select Exchange Activesync calendar protocol or Caldav calendar protocol; in addition, the user can also select the option of 'add the account at the computer end at the same time' through the user terminal, if the user selects the option of 'add the account at the computer end at the same time' through the user terminal, the account added at the user terminal is also 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 verification is passed, a verification success result is returned; if the verification is not passed, 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 an embodiment, the login error information may be displayed by the user terminal: "unable to connect to server, please check configuration".

If the received verification result is a verification success result, creating an 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 according to the account number and the password, and 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; if the verification account number and the password are incorrect, the calendar server returns a verification failure result, the account to be added cannot be created, and login error information is output so that a prompt of the login error information is displayed through the user terminal.

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

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

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

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

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

and sending the converted schedule information to the 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 the schedule information returned by the calendar server according to the calendar protocol information, and converts the received schedule information into a schedule structure template of a universal schedule field meeting the requirements of the user terminal, wherein the schedule structure template comprises the universal schedule field, the converted schedule information is sent to a corresponding calendar book of a corresponding calendar account, and the schedule information is stored in 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 comprises at least:

calendar information of the calendar book which is not hidden is displayed. Therefore, the user can set the calendar which does not need to be displayed as hidden according to the needs or the preference; when the user needs to display the hidden calendar, the user can set the calendar to be unhidden, so that the unhidden calendar and the calendar information corresponding to the calendar can be redisplayed. In some embodiments, after step 205, the multi-calendar account synchronization method of the application further comprises:

the calendar information is stored in a separate data space corresponding to the calendar account. In some embodiments, each calendar account is stored in an independent database, each calendar information is stored in an independent data space in the independent database, such that each calendar account is independent of each other, each calendar account is physically and logically isolated, and because each calendar information is stored in the independent data space, manipulation (e.g., synchronization, deletion, update, etc.) of one of the calendar information does not affect the other calendar information. Specifically, the independent data space may be different storage partitions divided in the same database, or may be storage 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 (such as MySQL).

Referring to fig. 7, the steps for adding a calendar account provided in the second embodiment of the present application include 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 account information of a calendar account to be added is matched with calendar server configuration information built in a user terminal; if so, go to step 703, otherwise go to 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 to successfully log in the calendar server; if the calendar server is successfully logged in, step 706 is performed; otherwise, ending;

step 706, storing login information; thus, the flow of adding the 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 account information of the calendar to be added;

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

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

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

Fig. 8 is an interface schematic for adding a calendar account through a user terminal according to a third embodiment of the present application, where in this embodiment, a user terminal is taken as a mobile phone to be described, and the calendar account to be added is: zhangsan@company.com, the account number is: zhangsan@company.com to-be-added calendar account zhangsan@company.com input through the user terminal, because the calendar server configuration information of the user terminal or the background server of the application program includes the company mailbox with the suffix of company, the configuration is not needed through the user terminal input, at this time, a password (refer to fig. 5) is needed to be input through the user terminal according to fig. 8, if the input user name and password are correct, an account Profile library is created according to account information, the calendar server is logged in, and login information is stored after the calendar server is successfully logged in; and the user terminal can select the account which is added at the computer end at the same time according to the requirement, so that the corresponding calendar account is synchronously added to the computer end. Referring to fig. 9, two calendar accounts that have been added are displayed on the calendar setting interface of the application program: zhangsan@company.com and 222222222@example.com, all calendar accounts that have been added currently 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 of "friend birthdays" is set as the default calendar, and 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 added calendar account.

In an embodiment, the application program is an enterprise WeChat, the enterprise WeChat is internally provided with a private calendar account, 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 which is internally provided with the enterprise WeChat can be used as a default calendar book. If a plurality of calendars exist in the enterprise WeChat, the default calendars can be reset according to the needs or the favorites of the user. By the method for synchronizing the multiple calendar accounts, processing of other added calendar accounts can be realized besides processing of private calendar accounts built in enterprise WeChat, and multiple calendar accounts are integrated together for unified display and unified processing, so that inconvenience of processing of the multiple calendar accounts by a user is solved. In addition to supporting a private calendar protocol built in an enterprise WeChat, the embodiment of the application also supports at least Exchange Activesync calendar protocols and other public calendar protocols such as Caldav calendar protocols, and at least allows a user to add calendar accounts of Exchange Activesync and Caldav calendar protocols, thereby supporting the addition of calendar accounts of a plurality of different protocol types.

Fig. 10 is a logic layer structure diagram of a multi-calendar account synchronization method implementation of an application program according to an exemplary embodiment of the present application, where the logic layer structure implementing the multi-calendar account synchronization method of the embodiment of the present application includes an account layer, a logic abstraction layer, and a User Interface (UI) layer. The account layer comprises a protocol layer and a storage layer, wherein the storage layer is used for storing account information, schedule information and the like of a calendar account; the protocol layer is used for realizing the login of each calendar account and the synchronization of schedule information, and specifically comprises the following steps: calendar information and account information returned by the calendar server are acquired through calendar protocol information, so that all calendar books of all calendar accounts can be acquired. The logic abstract layer is used for managing all calendar accounts, providing a unified schedule management and synchronization interface for the UI layer, forwarding a request of the UI layer to a corresponding calendar account, sending schedule information and account information returned by the calendar server to the corresponding calendar account, and converting the received schedule information into a universal 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 logic abstraction layer and displaying the acquired data, and specifically comprises: calendar information and account information are acquired from the logic abstraction layer through the synchronous interface program, so that a calendar book of a calendar account corresponding to the account information is acquired.

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 profileManager, and the account module is implemented by an abstract class profile; the management module is used for managing all 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 profile configuration files; the management module comprises a calendar account adding module, a calendar account deleting module and a calendar account obtaining module, wherein the calendar account adding module is used for adding and deleting calendar accounts; the account module is realized through an abstract class profile, encapsulates a plurality of operation methods, can be used for realizing synchronous operation, adding operation, updating operation, deleting operation, storing operation and the like of a schedule, and realizes that each calendar account is physically and logically isolated through a subclass of the corresponding abstract class profile; the abstract class profile is used as a parent class and is also used for abstracting calendar protocols and storage operations into a common method abstract class, so that other operations (such as a synchronization operation, an adding operation and an updating operation) serving as subclasses of the parent class profile can call the common abstract class of the parent class profile: calendar agreements and storage operations; abstract class profile may be used to describe each calendar account; the abstract class profile comprises a Login sub-class, a synchronization sub-class, an addition sub-class, an update sub-class, a schedule deletion sub-class and a storage sub-class, wherein the Login sub-class realizes the Login of a calendar account through a Login () method, the synchronization sub-class realizes synchronization operation through a SyncEvents () method to realize synchronization of schedule information, the addition sub-class realizes addition operation through an AddEvent () method to realize addition of schedule information, the update sub-class realizes update operation through an update event () method to realize update of schedule information, the schedule deletion sub-class realizes deletion operation through a DeleteEvent () method to realize deletion of schedule information, and the storage sub-class realizes storage operation through a SaveEvents () method to realize storage of schedule information.

The management module (profileManager) includes a creation unit, a deletion unit, and an acquisition unit. The creation unit realizes the addition of the calendar account through a CreateProfiles () method; the deleting unit realizes the deletion of the calendar account through a DeleteProfiles () method; the obtaining unit is used for obtaining all calendar accounts through a GetAllProfiles () method.

The storage layer of the account layer stores a default profile DefaultProfile, EAS protocol class profile EASProfile, caldav protocol class profile caldav profile. Default configuration file DefaultProfile corresponds to relevant information of default calendar accounts; EAS protocol class configuration file easpiofile corresponds to Exchange Activesync calendar protocol account related information; the Caldav protocol class configuration file Caldav Profile corresponds to the relevant information of the calendar account of the Caldav protocol.

According to the embodiment of the application program, on the basis that the schedule data of the private calendar account built in the application program is used as the universal schedule data, a public schedule data model is abstracted, and the extension data fields are reserved for various different calendar protocols, so that the calendar accounts supporting different calendar protocols can be conveniently added. When creating a schedule, the schedule structure template displayed by default on the user interface layer is a template of universal schedule fields, and after selecting the calendar, the display interface is dynamically adjusted according to the calendar protocol type of the calendar, so that the schedule fields special for the protocol type are displayed. The user interface layer clicks and stores the corresponding schedule information after inputting the corresponding schedule information through the user terminal, 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 the corresponding schedule data, and schedule synchronization is achieved.

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 the corresponding operation page according to needs or favorites, the calendar book can be hidden, and different colors can be used for marking the calendar book according to the needs or favorites of the user so as to distinguish a plurality of different calendar books, thereby being convenient for the user to quickly judge whether the schedule is urgent or not, or visually meeting personal favorites or carrying out personalized display and the like. In addition, if the calendar is set to be hidden, the schedule information of the hidden calendar is hidden, so that the calendar is not displayed; when display is needed, the display can be further set to be unhidden, so that the display can be redisplayed. Further, a global default setting item is provided on an operation interface for creating the schedule, so that a user can conveniently and quickly complete the operation.

Based on fig. 10 and 11, fig. 12 is a flowchart of a step of adding a calendar account in the multi-calendar account synchronization method of an application program provided in the third embodiment of the present application, where in a practical application scenario, the step of adding a calendar account provided in the embodiment of the present application is implemented by a UI layer, a profilemnager 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 configuration information of a calendar server built in a user terminal; further, inquiring the configuration information of the calendar server arranged in the user terminal according to the account number and the password;

judging whether the received account number and password exist in the configuration information of the calendar server 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 number and password do not exist in the configuration information of the calendar server built in the user terminal, inquiring the configuration information of the calendar server from a background server of the application program;

judging whether the received account number and password exist in the calendar server configuration information of a 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 calendar server configuration information;

if the received account number 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 the user terminal;

After creating the account profile library according to the calendar server configuration information, the method further comprises:

logging in a calendar server;

judging whether the login is successful;

if the login is successful, storing login information; the login information may include, but is not limited to including account information, which is not limited to account numbers and passwords including calendar accounts; the login information may also include a login time;

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

After the login information is stored, the account configuration result is displayed.

According to the multi-calendar account synchronization method for the application program, all calendar books of all calendar accounts are obtained, the calendar protocol information corresponding to each calendar book is obtained, and the calendar synchronization request is sent to the calendar server according to the calendar protocol information, so that the calendar information returned by the calendar server according to the calendar synchronization request is received, the calendar information is updated and displayed, the calendar books of the built-in calendar accounts and the added calendar books of other calendar accounts can be integrated in the application program, and a user can synchronize or operate the calendar books of the plurality of 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 the terminal, the server and software running in the terminal or the server. In some embodiments, the terminal may be a smart phone, tablet, notebook, desktop, or smart watch, etc.; the server side can be configured as an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligent platforms and the like; the software may be, but is not limited to, a calendar application that handles multiple calendar accounts, etc.

In combination with fig. 1, in an application scenario of the multi-calendar account processing method of 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 an application program, where the user terminal may be, but is not limited to, a tablet computer, a smart phone, etc., and the user terminal is used for 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 running on the user terminal, for example, updating the application program, etc.; the user terminal is also used for communication connection with the calendar server to perform schedule data transmission, for example, obtain schedule information from the calendar server, that is, synchronize the schedule information generated by the operations of creating, deleting, updating, etc. of the schedule information by the user terminal to the calendar server, etc. The calendar server is a server corresponding to a corresponding calendar protocol, and may be a server corresponding to Exchange Activesync calendar protocol or a server corresponding to Caldav calendar protocol, for example.

Fig. 13 is an alternative flowchart of a method for processing multiple calendar accounts 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. In some embodiments, the user may select a calendar to be operated through the client terminal.

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

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

1304. And sending a schedule request to a 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 may include at least a schedule adding result, a schedule deleting result, a schedule updating result, and a schedule storing result, corresponding to the adding of a schedule instruction, the deleting of a schedule instruction, the updating of a schedule instruction, and the storing of a schedule instruction, respectively.

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

In some embodiments, following step 1035, the multi-calendar account processing method further includes:

converting the data format of 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 means that the schedule information is converted into a format of a schedule structure template of a universal schedule field on a display interface of the user terminal so as to be converted into the universal schedule structure template of the user terminal, so that when the schedule is created, the schedule structure template displayed by default on the user interface layer is the template of the universal schedule field, and the converted schedule information can be stored in a corresponding calendar account so as to be displayed by the user terminal.

In some embodiments, where the calendar operation instruction is an add calendar instruction, step 1304 includes:

converting the data format of the added schedule 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 a calendar server according to the calendar protocol information.

In step 1304, before sending the calendar request to the calendar server, the added calendar instruction is subjected to data format conversion according to the calendar protocol information, so that the generated calendar instruction can be matched with the protocol type, the corresponding calendar server can recognize the calendar instruction, and the corresponding calendar information is returned according to the recognized calendar instruction.

In some embodiments, following step 1033, the multi-calendar account processing method further includes:

defaulting to a schedule structure template for displaying the universal 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 belongs. In practical application, firstly, a schedule structure template of a 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 calendar structure template of the calendar 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 calendar field special for the protocol type can be displayed.

In some embodiments, where the calendar operation instruction is an add calendar instruction, step 1305 includes:

receiving a schedule adding result returned by the calendar server;

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

In some embodiments, adding the calendar instruction includes at least: schedule information and triggering request; further, the calendar information may include, but is not limited to, a calendar list, a calendar name, a calendar description, a calendar duration, a time when the calendar starts, a calendar book to which the calendar belongs, a calendar 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 calendar adding result returned by the calendar server is successful, storing newly added calendar information of the corresponding calendar account.

In some embodiments, where the calendar operation instruction is an add calendar instruction, step 1306 includes:

if the schedule information has no conflict with all the schedule information associated with the participants, updating and displaying the schedule information to the application program of the participants; the calendar account associated with the participation of the person in adding the schedule information is also a contact person in the address book of the application program. In the embodiment of the application, the user can select the corresponding participant from the address book of the application program as the calendar account associated with the addition of the schedule information according to the requirement or preference when the schedule information is added, 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 newly added schedule information conflicts with all current schedule information according to all current associated schedule information of a participant, and if no conflict exists, the calendar server sends the newly added schedule information to an application program of the participant, so that the application program displayed to the participant can be updated; whether newly added schedule information conflicts with all current schedule information is judged, namely, time conflicts are generated, for example, the same participant cannot participate in two schedule events at the same time in two same time periods, and then the conflicts are generated.

According to the multi-calendar account processing method of the application program, the calendar server sends the calendar request according to the calendar protocol information and the operation instruction by acquiring the protocol information of the calendar account where the selected calendar book is located, receives the calendar information returned by the calendar server according to the calendar request, and accordingly updates and displays the calendar information according to the calendar information, and 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 calendar information of the plurality of calendar accounts can be conveniently processed. Because the calendar accounts are mutually independent, each calendar account is physically and logically isolated, even if one calendar book is abnormal (such as synchronization failure), other calendar books are not influenced; 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 application also provides a multi-calendar account synchronization device of the application program, which can realize the embodiment of the multi-calendar account synchronization method of the application program, and the device comprises the following steps:

the calendar protocol information is used for providing calendar protocol information to the calendar server;

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

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

The embodiment of the application also provides a device for processing the multiple calendar accounts of the application program, which can realize the embodiment of the method for processing the multiple calendar accounts of the application program, and the device comprises the following steps:

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

The embodiment of the application also provides electronic equipment, which comprises:

at least one memory;

at least one processor;

at least one program;

the program is stored in the memory, and the processor executes the at least one program 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 (Personal Digital Assistant, PDA for short), a Point of Sales (POS for short), a car-mounted computer, and the like.

The embodiment of the application also provides a computer readable storage medium, and the computer executable instructions are used for executing the multi-calendar account synchronization method of the application program or the multi-calendar account processing method of the application program.

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

Those 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 both 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 known to those skilled 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 be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, 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.

While the preferred embodiments of the present application have been described in detail, the present application is not limited to the above embodiments, and various equivalent modifications and substitutions can be made by those skilled in the art without departing from the spirit of the present application, and these equivalent modifications and substitutions are intended to be included in the scope of the present application as defined in the appended claims.

Claims

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

acquiring calendar protocol information corresponding to each calendar book;

sending a schedule synchronization request to a calendar server according to the calendar protocol information; the sending a schedule synchronization request to a calendar server according to the calendar protocol information comprises the following steps: 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; sending the schedule synchronization request to a corresponding calendar server according to the calendar protocol;

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 calendar books for all calendar accounts comprises:

acquiring account information of all calendar accounts;

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

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

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.

4. A method according to any one of claims 1-3, further comprising a calendar account adding or deleting step, said calendar account adding step comprising in particular:

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 newly added calendar accounts;

Or, the step of deleting the calendar account specifically includes:

sending a calendar account deletion request to the calendar server;

receiving an account deletion result returned by the calendar server;

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

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

inquiring the configuration information of the calendar server from a 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 acquiring the configuration information of the calendar server in a mode of input of the user terminal.

6. A method according to any of claims 1-3, further comprising the step of updating the display calendar account, said step of updating the display calendar account comprising:

receiving a calendar operation instruction through the application program;

updating and displaying account information, an unhidden calendar and corresponding calendar events of the unhidden calendar according to the calendar operation instruction, wherein the calendar operation instruction is any instruction of a calendar adding instruction, a calendar deleting instruction, a calendar hiding instruction and a calendar attribute modifying instruction.

7. A method according to any one of claims 1-3, further comprising a calendar event display step, in particular:

triggering schedule event display operation;

8. A method for processing multiple calendar accounts of an application program, comprising:

acquiring a selected calendar book;

acquiring calendar protocol information of a calendar account in which the selected calendar is located;

sending a schedule request to a calendar server according to the calendar protocol information and the schedule operation instruction; the sending a calendar request to a calendar server according to the calendar protocol information and the calendar operation instruction comprises the following steps: converting the data format of 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; sending the schedule request to the calendar server according to the calendar protocol information;

Receiving schedule information returned by the calendar server;

and updating and displaying the schedule information.

9. The method of claim 8, wherein the schedule operation instruction is an add schedule instruction, and wherein 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 belongs.

10. The method of claim 9, wherein the receiving calendar information returned by the calendar server comprises:

receiving a schedule adding result returned by the calendar server;

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

11. The method of claim 10, wherein the updating the display of the calendar information comprises:

if the schedule information has no conflict with all schedule information associated with the participant, updating and displaying the schedule information to an application program of the participant; the calendar account associated with the participant when manually adding calendar information.

12. The method according to any one of claims 8-11, wherein after receiving the calendar information returned by the calendar server, the method further comprises:

converting the schedule information into a data format;

13. A multi-calendar account synchronization device for an application program, comprising:

the calendar protocol information is used for providing calendar protocol information to a calendar server; the sending a schedule synchronization request to a calendar server according to the calendar protocol information comprises the following steps: 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; sending the schedule synchronization request to a corresponding calendar server according to the calendar protocol;

14. A multi-calendar account processing device for an application program, comprising:

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

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 sending a calendar request to a calendar server according to the calendar protocol information and the calendar operation instruction comprises the following steps: converting the data format of 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; sending the schedule request to the calendar server according to the calendar protocol information;

15. An electronic device, comprising:

at least one memory;

at least one processor;

at least one program;

the program is stored in the memory, the processor executing the at least one program to implement the method of multi-calendar account synchronization of an application program as claimed in any of claims 1-7, or to implement the method of multi-calendar account processing of an application program as claimed in any of claims 8-12.

16. A computer readable storage medium for executing the method of multi-calendar account synchronization of an application program according to any of claims 1-7 or for implementing the method of multi-calendar account processing of an application program according to any of claims 8-12.