Calendar management method and device, equipment, readable storage medium and program product

Abstract

The embodiment of the invention provides a calendar management method and device, equipment, a readable storage medium and a program product. The method comprises the steps that a management request of an operation initiation object for a first calendar object in a target application is obtained, the type of the first calendar object is a first type or a second type, and the calendar object of the first type is created by calling the target application by an external application; the calendar object of the second type is created by a use object of the target application; according to object authentication data in the management request, performing authentication processing on the operation initiating object to obtain an authentication result, the authentication result being used for indicating whether the authentication is passed or not and indicating the management authority of the operation initiating object for the first calendar object; and performing management operation on the object data of the first calendar object according to the authentication result and the management request. By adopting the calendar management method and device, compatible management of the application calendar and the common calendar can be realized, the calendar management efficiency is effectively improved, and the complexity of calendar management is reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a calendar management method, a calendar management device, a computer device, a computer-readable storage medium, and a computer program product. Background Art

[0002] In an application, a schedule typically refers to one or more reminder events, while a calendar is typically a collection of schedules. Calendars created by application objects are called normal calendars, while calendars created by applications associated with communication applications are called application calendars.

[0003] Generally, an application calendar can only be managed (e.g., modified, deleted, etc.) by the application that created it, while a regular calendar can be managed by a management object (e.g., a user object). This results in incompatible management between application calendars and regular calendars, making management more complex. Summary of the Invention

[0004] The embodiments of the present application provide a calendar management method, apparatus, device, readable storage medium, and program product, which can achieve compatible management of application calendars and ordinary calendars, effectively improve calendar management efficiency, and reduce the complexity of calendar management.

[0005] In one aspect, an embodiment of the present application provides a calendar management method, the calendar management method comprising:

[0006] Obtaining a management request from an operation initiating object for a first calendar object in a target application, where the first calendar object is of a first type or a second type, where the first type of calendar object is created by an external application by calling the target application, and the second type of calendar object is created by a user object of the target application; the management request includes object authentication data and operation content data;

[0007] authenticating the operation initiating object according to the object authentication data to obtain an authentication result, wherein the authentication result is used to indicate whether the authentication is passed and the management authority of the operation initiating object with respect to the first calendar object;

[0008] A management operation is performed on the object data of the first calendar object according to the authentication result and the operation content data.

[0009] Accordingly, an embodiment of the present application provides a calendar management device, which includes:

[0010] an acquiring unit, configured to acquire a management request from an operation initiating object for a first calendar object in a target application, wherein the first calendar object is of a first type or a second type, wherein the first type of calendar object is created by an external application by calling the target application, and the second type of calendar object is created by a user object of the target application; the management request includes object authentication data and operation content data;

[0011] a processing unit, configured to perform authentication processing on the operation initiating object according to the object authentication data to obtain an authentication result, wherein the authentication result is used to indicate whether the authentication is passed and the management authority of the operation initiating object with respect to the first calendar object;

[0012] A management unit is used to perform a management operation on the object data of the first calendar object according to the authentication result and the operation content data.

[0013] In one embodiment, the processing unit is further configured to perform the following steps:

[0014] Obtaining calendar object creation data, the calendar object creation data including one or more of calendar object basic data, schedule creation data, and participant object description data; the schedule creation data is used to indicate schedules included in the second calendar object, and the participant object description data is used to indicate object identifiers of participant objects of the second calendar object and management permissions of each participant object of the second calendar object with respect to the second calendar object;

[0015] The object data of the second calendar object is generated according to the calendar object creation data to create the second calendar object.

[0016] In one embodiment, the processing unit is configured to perform the following steps when obtaining calendar object creation data:

[0017] Acquire calendar object creation data submitted by a user of the target application through the target application, wherein the calendar object creation data also includes creation object data of the user; or

[0018] Calendar object creation data sent by the external application through the application interface of the target application is received, where the calendar object creation data further includes an application identifier of the external application and entity information corresponding to the external application.

[0019] In one embodiment, the object data of the first calendar object includes a list of participating object identifiers, wherein the list of participating object identifiers includes object identifiers of participating objects of the first calendar object and management rights of the participating objects of the first calendar object; the processing unit is further configured to perform the following steps:

[0020] Obtaining a calendar query request submitted by the operation initiating object through the client of the target application for the first calendar object, wherein the calendar query request includes the object authentication data; the object authentication data includes the object identifier of the operation initiating object;

[0021] querying the management authority of the operation initiating object on the first calendar object from the participating object identifier list according to the object identifier of the operation initiating object, where the management authority is any one of subscription authority, viewing authority, editing authority and adjustment authority;

[0022] determining first calendar object display data according to the management authority of the operation initiating object on the first calendar object and the object data of the first calendar object;

[0023] The first calendar object display data is sent to the client of the target application, where the first calendar object display data is used by the client of the target application to display the first calendar object.

[0024] In one embodiment, the type of the first calendar object is the second type, the object data of the first calendar object further includes the creation object data of the usage object, and the processing unit is further configured to perform the following steps:

[0025] Matching the object identifier of the operation initiating object with the creation object data of the use object to obtain a creation object matching result;

[0026] If the creation object matching result indicates that the object identifier of the operation initiating object matches the creation object data of the use object, determining that the management authority of the operation initiating object for the first calendar object is an adjustment authority, and performing the step of determining display data of the first calendar object based on the management authority of the operation initiating object for the first calendar object and the object data of the first calendar object;

[0027] If the creation object matching result indicates that the object identifier of the operation initiating object does not match the creation object data of the use object, a step is executed to query the management authority of the operation initiating object for the first calendar object from the participating object identifier list according to the object identifier of the operation initiating object.

[0028] In one embodiment, the processing unit is configured to perform authentication processing on the operation initiating object according to the object authentication data, and upon obtaining an authentication result, specifically to perform the following steps:

[0029] Determining a target object identifier that matches the object authentication data based on the object authentication data and the participating object identifier list;

[0030] An authentication result is determined according to the management authority corresponding to the target object identifier, the authentication result indicating that the authentication is passed, and the management authority of the operation initiating object for the first calendar object is the management authority corresponding to the target object identifier.

[0031] In one embodiment, the processing unit is further configured to perform the following steps:

[0032] receiving an entity query request for a target entity submitted by the operation initiating object through the web console of the target application, wherein the target entity is the entity to which the operation initiating object belongs, and the entity query request includes the object authentication data;

[0033] Perform entity authentication processing according to the object authentication data to obtain an entity authentication result;

[0034] If the entity authentication result indicates that the operation initiating object meets the entity query condition, obtaining object data of each target calendar object associated with the target entity, wherein the each target calendar object includes the first calendar object;

[0035] The object data of each target calendar object is sent to the web console of the target application, and the object data of the target calendar object is used by the web console of the target application to display each target calendar object.

[0036] In one embodiment, the processing unit is configured to perform authentication processing on the operation initiating object according to the object authentication data, and upon obtaining an authentication result, specifically to perform the following steps:

[0037] Determining a first entity identifier of an entity to which the first calendar object belongs;

[0038] Determining a second entity identifier of the entity to which the operation initiating object belongs according to the object authentication data;

[0039] Matching the first entity identifier and the second entity identifier to obtain an entity identifier matching result;

[0040] If the entity identifier matching result indicates that the first entity identifier and the second entity identifier match, then determining that the authentication result is authentication passed, and the management authority of the operation initiating object for the first calendar object is a super authority;

[0041] If the entity identifier matching result indicates that the first entity identifier and the second entity identifier do not match, the authentication result is determined to be authentication failure.

[0042] In one embodiment, the management unit is configured to perform the following steps when performing a management operation on the object data of the first calendar object based on the authentication result and the operation content data:

[0043] If the authentication result indicates that the authentication is passed, modifying the object data of the first calendar object according to the operation content data to obtain modified object data of the first calendar object;

[0044] The object data of the modified first calendar object is stored.

[0045] In one embodiment, the object data of the first calendar object includes a deletion flag, and the operation content data indicates deletion of the first calendar object; the management unit is configured to modify the object data of the first calendar object according to the operation content data, and to obtain the modified object data of the first calendar object by performing the following steps:

[0046] The deletion flag in the object data of the first calendar object is set to a deleted state.

[0047] Accordingly, an embodiment of the present application provides a computer device, comprising:

[0048] a processor suitable for implementing a computer program;

[0049] A computer-readable storage medium stores a computer program, and the computer program is suitable for being loaded by a processor and executing the above-mentioned calendar management method.

[0050] Accordingly, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is read and executed by a processor of a computer device, the computer device executes the above-mentioned calendar management method.

[0051] Accordingly, an embodiment of the present application further provides a computer program product, the computer program product including a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to perform the above-mentioned calendar management method.

[0052] In the present application, a management request from an operation initiating object for a first type of calendar object (i.e., an application calendar) or a second type of calendar object (i.e., an ordinary calendar) can be received; authentication processing can be performed on the operation initiating object, and management operations can be performed on the calendar object based on the management request and the authentication result. The calendar management method provided by the embodiment of the present application can achieve compatible management of application calendars and ordinary calendars, thereby effectively improving the management efficiency of calendar objects and reducing the complexity of the management method; at the same time, after receiving the management request, authentication processing can be performed on the operation initiating object, and corresponding management operations can be performed based on the authentication result, thereby effectively ensuring the rationality of the management operation, avoiding unauthorized operations, and ensuring the security of the data. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0054] Figure 1 This is a schematic diagram of the system architecture of a calendar management system provided by an embodiment of the present application;

[0055] Figure 2 This is a flowchart of a calendar management method provided by an embodiment of the present application;

[0056] Figure 3 This is a flowchart of a calendar generation method provided by an embodiment of the present application;

[0057] Figure 4 is a schematic diagram of a calendar data structure provided by an embodiment of the present application;

[0058] Figure 5 This is a flowchart of another calendar management method provided by an embodiment of the present application;

[0059] Figure 6 This is a schematic diagram of a calendar interface provided by an embodiment of the present application;

[0060] Figure 7 This is a schematic diagram of a calendar card provided in an embodiment of the present application;

[0061] Figure 8 is a schematic diagram of another calendar card provided in an embodiment of the present application;

[0062] Figure 9 This is a schematic diagram of an editing calendar interface provided by an embodiment of the present application;

[0063] Figure 10 This is a schematic diagram of a calendar interface provided by an embodiment of the present application;

[0064] Figure 11 This is a flowchart of another calendar management method provided by an embodiment of the present application;

[0065] Figure 12 This is a schematic diagram of a web console provided in an embodiment of the present application;

[0066] Figure 13 This is a schematic diagram of an interface for editing a staff calendar provided in an embodiment of the present application;

[0067] Figure 14 This is a structural block diagram of a calendar management device provided by an embodiment of the present application;

[0068] Figure 15 This is a structural block diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0069] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of this application.

[0070] It should be noted that the terms "first" and "second" in the embodiments of this application are for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a technical feature designated as "first" or "second" may explicitly or implicitly include at least one such feature.

[0071] To facilitate understanding, we first provide a brief explanation of some nouns:

[0072] Schedule: refers to a reminder event or a group of reminder events, such as work arrangements, meetings, project plans, and other scenarios. A schedule can be associated with multiple members as participants.

[0073] Calendar: also known as calendar object, is a collection of schedules.

[0074] External applications: These are applications that are separate from the target application (including calendar creation functionality). External applications can implement corresponding functions by calling the target application's APIs. External applications can be categorized as internal entity applications, third-party applications, and built-in applications.

[0075] Participants: When an application or user creates a calendar, they can specify the associated participants and the calendar-specific management permissions that each participant has. Participants are also called calendar administrators.

[0076] Super Administrator: The highest-level administrator in an entity, who can manage all calendars within the entity.

[0077] Application interface: The open interface of the target application. External applications can use the application interface to call the internal capabilities of the target application (for example, creating a calendar).

[0078] Application calendar: A calendar created in a target application by an external application calling the target application's application interface.

[0079] An application calendar created by an external application by calling a target application can usually only be managed by the external application, while a regular calendar created by a user object of the target application can be managed by the user object. This results in incompatibility between the management of application calendars and regular calendars, making the management of application calendars more complicated.

[0080] Based on this, an embodiment of the present application provides a calendar management method, which can obtain a management request from an operation initiating object for a first calendar object in a target application. The type of the first calendar object is the first type or the second type. The first type of calendar object is created by an external application by calling the target application, and the second type of calendar object is created by a user object of the target application. The management request includes object authentication data and operation content data. The operation initiating object is authenticated according to the object authentication data to obtain an authentication result. The authentication result is used to indicate whether the authentication is passed and the management authority of the operation initiating object for the first calendar object. Management operations are performed on the object data of the first calendar object according to the authentication result and the operation content data. Through the method provided by the embodiment of the present application, compatible management of application calendars and ordinary calendars can be achieved, which effectively improves the efficiency of calendar management and reduces the complexity of calendar management.

[0081] The calendar management method provided in the embodiment of the present application can be applied to the field of artificial intelligence. Artificial Intelligence (AI) is a theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results. In the calendar management scenario of the application, artificial intelligence technology can be used to manage the calendar in the application. In this case, the method provided in the present application can be used to manage the calendar. Specifically, a management request for an application calendar or a common calendar can be received from an operation initiating object, the operation initiating object can be authenticated, an authentication result can be obtained, and management operations can be performed on the application calendar or the common calendar based on the authentication result and the management request. Through the method provided in the embodiment of the present application, compatible management of application calendars and common calendars can be achieved, effectively improving the efficiency of calendar management.

[0082] The calendar management method provided in the embodiment of the present application can also be applied to the field of cloud storage. Cloud storage is a new concept extended and developed from the concept of cloud computing. A distributed cloud storage system (hereinafter referred to as a storage system) refers to a storage system that uses cluster applications, grid technology, and distributed storage file systems to bring together a large number of different types of storage devices (storage devices are also called storage nodes) in the network to work together through application software or application interfaces to provide external data storage and business access functions. The method provided in the embodiment of the present application can be implemented based on cloud storage technology. Specifically, the background server of the target application can store the object data of the calendar object in the cloud storage system. When the background server of the target application obtains a management request from the operation initiating object for the first calendar object (which can be an application calendar or a normal calendar), the background server of the target application can authenticate the operation initiating object, obtain an authentication result, and perform management operations on the object data of the first calendar object stored in the cloud storage system based on the authentication result and the management request. Through the method provided in the embodiment of the present application, compatible management of application calendars and normal calendars can be achieved, and the storage resources of the background server can be effectively saved.

[0083] The following will introduce the architecture of the calendar management system provided by the embodiment of the present application with reference to the accompanying drawings.

[0084] See Figure 1 This figure is a schematic diagram of the system architecture of a calendar management system provided by an embodiment of the present application. The calendar management system includes a target backend server 101, a target terminal device 102, and an external backend server 103. The target backend server 101 can exchange data with the target terminal device 102 and the external backend server 103. Among them:

[0085] The target backend server 101 may be a backend server for a target program, which may have a calendar function. The target backend server 101 may create a calendar and return calendar-related data upon request. The calendar backend server 101 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It may also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0086] The calendar backend server 101 can store the generated calendar object data in a database. The database can be a local database in the calendar backend server 101 or a cloud database associated with the calendar backend server 101 (i.e., a database deployed in the cloud). Specifically, it can be based on any deployment of a private cloud, a public cloud, a hybrid cloud, an edge cloud, etc., so that the cloud database focuses on different functions. For example, a database deployed in a private cloud uses the user's personal equipment as the basic cloud hardware and focuses more on serving a small number of users. A database deployed in a public cloud is deployed based on a cloud platform provided by a third party, which allows the data stored in the database to be shared. Any user's data can be stored in the database, and any user can also use the data in the database.

[0087] The target terminal device 102 can run the client of the target application and can also display the web console of the target application. The target terminal device 102 can interact with the user object and send the request or data submitted by the user object to the target backend server 101. The target terminal device 102 can be a handheld device with display and communication functions (such as a smart phone, tablet computer), a computing device (such as a personal computer (PC), a car terminal, an intelligent voice interaction device, a wearable device or other smart device, etc., but is not limited to these.

[0088] The external backend server 103 may be a backend server for an external application that is different from the target application. The external backend server 103 may call the application interface of the target backend server 101 and perform data interaction with the target backend server 101. The external backend server 103 may receive data sent by the client of the external application, and the data sent by the client of the external application may be obtained by the client of the external application interacting with the business object. The external backend server 103 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0089] The following will explain in detail Figure 1 The calendar management system shown works as follows:

[0090] The target backend server 101 may store object data of a common calendar and object data of an application calendar.

[0091] When the operation initiating object is a user object that interacts with the target terminal device 102, the target terminal device 102 can send a management request for the first calendar object in the target application to the target backend server 101. The first calendar object can be an application calendar or a common calendar. The management request can include object authentication data and operation content data. After receiving the management request sent by the target terminal device 102, the target backend server 101 can authenticate the user object corresponding to the target terminal device 102 based on the object authentication data and obtain an authentication result. The authentication result can indicate whether the authentication is passed and the user object's management authority for the first calendar object. The target backend server 101 can perform management operations on the object data of the first calendar object based on the authentication result and the operation content data.

[0092] When the operation initiating object is an external application running in the external backend server 103, the external backend server 103 can call the application interface of the target backend server 101 and send the management request for the first calendar object to the target backend server 101 (i.e., call the application interface to send the management request). The target backend server 101 can perform authentication processing on the external backend server 103 based on the object authentication data in the management request, obtain the authentication result, and perform management operations on the object data of the first calendar object based on the authentication result and the operation content data in the management request. Through the calendar management method provided in the embodiment of the present application, compatible management of application calendars and ordinary calendars can be achieved. At the same time, management requests of different management objects (external applications or usage objects) can be responded to and management operations can be performed on the calendar, which effectively improves the efficiency of calendar management and is also conducive to expanding application scenarios.

[0093] It is understood that the architectural diagram of the calendar management system described in the embodiment of the present application is for the purpose of more clearly illustrating the calendar management method of the embodiment of the present application, and does not constitute a limitation on the calendar management method provided in the embodiment of the present application. Figure 1 The number of target backend servers 101, target terminal devices 102, and external backend servers 103 is merely illustrative. Any number of devices may be configured as needed for business implementation. Furthermore, as system architecture evolves and new business scenarios emerge, the calendar management method provided in the embodiments of the present application is equally applicable to similar technical issues.

[0094] It should be noted that the collection and processing of relevant data in this application (for example, object authentication data, object data of calendar objects) should be strictly in accordance with the requirements of relevant laws and regulations when applied in instances, and the informed consent or separate consent of the personal information subject should be obtained. Subsequent data use and processing should be carried out within the scope of authorization of laws and regulations and the personal information subject.

[0095] See Figure 2 , Figure 2 This is a flowchart of a calendar management method provided in an embodiment of the present application. The calendar management method can be implemented by the target backend server 101 described above, or by other devices capable of implementing the calendar management method. The following description uses the calendar management method implemented by the target backend server 101 as an example. The calendar management method provided in the embodiment of the present application includes, but is not limited to:

[0096] S201. Obtain a management request from an operation initiating object for a first calendar object in a target application, where the type of the first calendar object is a first type or a second type. The first type of calendar object is created by an external application by calling the target application, and the second type of calendar object is created by a user object of the target application; the management request includes object authentication data and operation content data.

[0097] In an embodiment of the present application, the target application may be an application program with calendar creation and display capabilities. The target application's backend server may receive a management request for an operation initiating object. The operation initiating object may be a user of the target application or an external application that calls the target application. The management request may be for a first calendar object in the target application. The first calendar object may be of a first type or a second type. A first-type calendar object is created by an external application by calling the target application, i.e., a first-type calendar object is an application calendar; a second-type calendar object is created by a user of the target application, i.e., a second-type calendar object is a regular calendar. The management request may include object authentication data and operation content data. The object authentication data may be used to authenticate the operation initiating object, and the operation content data may be used to indicate the specific operation content. The method provided in an embodiment of the present application can receive management requests for application calendars or regular calendars sent by different operation objects (external applications or user objects), thereby achieving joint management of different operation objects and facilitating subsequent management operations on the object data of calendar objects based on the management request, thereby eliminating the management barriers between application calendars and regular calendars and improving the efficiency of calendar management.

[0098] S202: Authenticate the operation initiating object according to the object authentication data to obtain an authentication result, where the authentication result indicates whether the authentication is passed and the management authority of the operation initiating object with respect to the first calendar object.

[0099] In an embodiment of the present application, the backend server of the target application can authenticate the operation-initiating object based on the object authentication data to obtain an authentication result. The authentication result can be used to indicate whether the authentication is successful and the management permissions of the operation-initiating object with respect to the first calendar object. For example, the authentication result can indicate that the authentication is successful and the management permissions of the operation-initiating object with respect to the first calendar object are edit permissions. For another example, the authentication result can indicate that the authentication is unsuccessful.

[0100] S203: Perform a management operation on the object data of the first calendar object according to the authentication result and the operation content data.

[0101] In an embodiment of the present application, the background server of the target application can perform management operations on the object data of the first calendar object based on the authentication result and the operation content data. For example: if the authentication result indicates that the authentication is passed, the background server of the target application can modify the object data of the first calendar object based on the operation content data. For another example: if the authentication result indicates that the authentication is not passed, at this time, the background server of the target application may not manage the object data of the first calendar object, and may also generate an operation abnormality notification message, and send the operation abnormality notification message to the operation initiating object. Through the method provided in the embodiment of the present application, compatible management of application calendars and ordinary calendars can be achieved, effectively improving the management efficiency of calendars.

[0102] In one embodiment, the implementation method of performing a management operation on the object data of the first calendar object based on the authentication result and the operation content data can be as follows: if the authentication result indicates that the authentication is passed, the object data of the first calendar object is modified according to the operation content data to obtain the modified object data of the first calendar object; and the modified object data of the first calendar object is stored. If the authentication result indicates that the authentication is passed, the object data of the first calendar object can be modified according to the content data, and the modification result can be stored. For example: if the authentication result indicates that the authentication is passed, and the management authority of the operation initiating object for the first calendar object is editing authority, and the operation content data indicates that the object data of the first calendar object is modified, at this time, the management authority of the operation initiating object for the first calendar object matches the operation indicated by the operation content data, then the background server of the target application can modify the object data of the first calendar object according to the operation content data.

[0103] For another example: the authentication result indicates that the authentication is passed, and the management authority of the operation initiating object for the first calendar object is editing authority, and the operation content data indicates that the management authority of the participating objects of the first calendar object is modified. At this time, the management authority of the operation initiating object for the first calendar object does not match the operation indicated by the operation content data. Then, the background server of the target application may not modify the object data of the first calendar object according to the operation content data, but generate an operation unauthorized notification message and send the operation unauthorized communication message to the operation initiating object. The method provided in the embodiment of the present application can ensure the rationality of the management operation of the object data of the calendar object, avoid the situation of unauthorized operation, and effectively ensure the security of the object data.

[0104] It should be noted that if the authentication result indicates that authentication failed, the target application's backend server can directly generate an operation exception notification message and send it to the person who initiated the operation. For example, if the authentication result indicates that authentication failed, and the operation content data indicates that the object data of the first calendar object needs to be modified, the target application's backend server will not perform any management operations on the object data of the first calendar object, but will instead directly generate an operation exception notification message and send it to the person who initiated the operation.

[0105] In one embodiment, the object data of the first calendar object may include a deletion flag, and the operation content data may indicate deletion of the first calendar object; then, based on the operation content data, the object data of the first calendar object is modified to obtain the modified object data of the first calendar object. This may be achieved by setting the deletion flag in the object data of the first calendar object to a deleted state. The method provided in the embodiment of the present application can achieve soft deletion of the object data of a calendar object, that is, when the operation content data indicates deletion of the first calendar object, the deletion flag in the object data of the first calendar object is set to a deleted state, but the actually stored object data is not deleted. This can avoid data loss caused by accidental deletion operations.

[0106] Through the calendar management method provided in the embodiment of the present application, management requests sent by different operation objects (external applications or user objects) can be received, and the common management of calendars by different operation objects can be realized, thereby expanding the application scenarios; management requests for application calendars or ordinary calendars can be received, thereby realizing compatible management of application calendars and ordinary calendars, eliminating the management barriers between application calendars and ordinary calendars, improving the efficiency of calendar management, and reducing the complexity of calendar management; the operation initiating object can be authenticated to ensure the rationality of the management operation of the object data of the calendar object, avoid unauthorized operations, and ensure the security of the object data; soft deletion operations can be performed to effectively avoid data loss caused by accidental deletion operations.

[0107] See Figure 3 , Figure 3 A flow chart of a calendar generation method provided in an embodiment of the present application. The calendar generation method can be performed by the above Figure 1 The target backend server 101 in the embodiment is implemented, and the first calendar object involved in the above embodiment can be generated by using the calendar generation method. The process of the calendar generation method provided in the embodiment of the present application includes but is not limited to:

[0108] S301. Obtain calendar object creation data, where the calendar object creation data includes one or more of calendar object basic data, schedule creation data, and participant object description data; the schedule creation data is used to indicate the schedules included in the second calendar object, and the participant object description data is used to indicate the object identifiers of the participant objects of the second calendar object and the management permissions of each participant object of the second calendar object for the second calendar object.

[0109] In an embodiment of the present application, the background server of the target application can obtain calendar object creation data, which may include one or more of calendar object basic data, schedule creation data, and participant object description data. Among them, the calendar object basic data may include the calendar name, calendar description data, calendar number, flag bit and other data of the second calendar object; the schedule creation data may be used to indicate the schedule contained in the second calendar object, and the schedule creation data may include data such as the schedule name, schedule number, schedule creation object identifier; the participant object description data may be used to indicate the object identifier of the participant object of the second calendar object, and the management authority of each participant object of the second calendar object for the second calendar object. The participant object of the second calendar object is the object that can obtain relevant information of the second calendar object. The participant object description data may include information such as the object identifier of the participant object, the type of management authority, etc.

[0110] In one embodiment, obtaining calendar object creation data may be accomplished by: obtaining calendar object creation data submitted by a user of a target application through the target application, the calendar object creation data also including the user's creation data; or receiving calendar object creation data sent by an external application through an application interface of the target application, the calendar object creation data also including an application identifier of the external application and entity information corresponding to the external application. The backend server of the target application may receive the calendar object creation data submitted by the user or sent by the external application through the application interface.

[0111] When the obtained calendar object creation data is submitted by a user of the target application through the target application, the calendar object creation data may also include creation object data of the user, and the creation object data may include an object identifier of the user. The backend server of the target application may subsequently create a second calendar object of the second type (i.e., the second calendar object is a normal calendar) based on the calendar object creation data.

[0112] When the calendar object creation data is sent by an external application through the application interface of the target application, the calendar object creation data may also include the application identifier of the external application and the entity information corresponding to the external application. Among them, the entity information corresponding to the external application refers to the information of the entity to which the object that calls the external application belongs (for example: the identifier of the entity), and the entity may be an enterprise. For example: Object A calls an external application, so that the external application calls the target application through the application interface to create a calendar, then the information of the entity to which Object A belongs is the entity information corresponding to the external application. The background server of the target application can subsequently create data based on the calendar object and create a second calendar object of the first type (that is, the second calendar object is an application calendar). Through the method provided in the embodiment of the present application, the calendar object creation data submitted by different operation objects (using objects or external applications) can be obtained, which is conducive to the subsequent creation of different types of calendars and the subsequent compatible management of different types of calendars.

[0113] S302: Generate object data of the second calendar object according to the calendar object creation data to create the second calendar object.

[0114] In an embodiment of the present application, the background server of the target application can generate the object data of the second calendar object based on the calendar object creation data to create the second calendar object. Regardless of whether the calendar object creation data submitted by the object is used or the calendar object creation data sent by an external application, the background server of the target application can use the same method (for example: according to a preset data structure) to generate the object data of the second calendar object using the calendar object creation data, thereby realizing the creation of the second calendar object. The method provided in the embodiment of the present application can realize the compatible generation of application calendars and ordinary calendars, and is also conducive to the subsequent compatible management of application calendars and ordinary calendars, thereby improving management efficiency.

[0115] See Figure 4 , this figure is a schematic diagram of a calendar data structure provided in an embodiment of the present application. Figure 4 The calendar data structure shown may include five main parts: a calendar object data block, a participant object data block, a schedule data block, a first-type calendar data block, and a second-type calendar data block. The calendar object data block may include a calendar identification field, a calendar name field, a calendar description field, and a calendar flag field. One calendar object data block may correspond to n participant object data blocks (n is a non-negative integer). For any participant object data block, the participant object data block may include a management permission field (the value of the management permission field may be "subscription permission," "view permission," "edit permission," "adjustment permission," etc.) and an object identification field for the participant object.

[0116] A calendar object data block can correspond to m schedule data blocks (m is a non-negative integer). For any schedule data block, the schedule data block can include a schedule identification field, an object tag field of the schedule creation object, and other data (for example: a schedule description field, a schedule start time field, a schedule end time field, etc.).

[0117] The first type of calendar data block includes an entity identification field and an application identification field for creating an application; the second type of calendar data block includes an object identification field for creating an object.

[0118] If the calendar object creation data is submitted by the user object, the calendar object creation data includes the creation object data of the user object, then the calendar object creation data and the calendar object creation data are combined. Figure 4 When the data structure shown generates object data of a calendar object, the creation object data of the usage object included in the calendar object creation data can be determined as the value of the object identification field of the creation object included in the second type of calendar data block (at this time, the values ​​stored in each field in the first type of calendar data block in the data structure can be empty).

[0119] If the calendar object creation data is sent by an external application through an application interface, the calendar object creation data includes the application identifier of the external application and the entity information corresponding to the external application (including the entity identifier). Figure 4 When the data structure shown generates object data of a calendar object, the application identifier of the external application included in the calendar object creation data can be determined as the value of the application identifier field of the creation application in the first type of calendar data block; the entity identifier included in the calendar object creation data can be determined as the value of the entity identifier field included in the first type of calendar data block (at this time, the values ​​stored in each field in the second type of calendar data block in the data structure can be empty).

[0120] Depend on Figure 4 As can be seen from the data structure shown, a calendar object can contain multiple schedules, and the management authority of an operation initiating object over a schedule is the same as the management authority of the operation initiating object over the calendar object to which the schedule belongs, thereby achieving unified management of schedules in the calendar. The method provided by the embodiment of the present application can provide a calendar data structure so that the structure of the constructed application calendar and the structure of the ordinary calendar are the same, which is conducive to the subsequent compatible management of the application calendar and the ordinary calendar based on the same structure, thereby improving management efficiency.

[0121] In some cases, it is also possible to Figure 4 The data structure shown in the figure can be adjusted to further reduce the storage space occupied by the calendar object data. For example, Figure 4The first type calendar data block and the second type calendar data block in the creation data block are merged into a creation identification data block, which includes a creation object identification field (the creation object identification field is used to store the object identification of the creation object or the application identification of the creation application), and adds a calendar type field to the calendar object data block (the calendar type field is used to indicate whether the calendar object is an application calendar). The method provided in the embodiment of the present application can further reduce the storage space occupied by the object data of the calendar object, thereby saving storage resources.

[0122] It should be noted that the first calendar object and the second calendar object involved in the above embodiment can both be based on Figure 4 The calendar data structure shown is created.

[0123] In one embodiment, the above Figure 4 In the data structure shown, the calendar flag bit included in the calendar object data block can be a binary data string, which can include three binary digits, and each binary digit can represent a different meaning. The meanings represented by these three binary digits can be shown in Table 1 below.

[0124] Table 1:

[0125] Serial number Flag meaning 1 0x1 Has it been deleted? 2 0x2 Is it the default calendar? 3 0x4 Is it an application calendar?

[0126] In Table 1, the flag bit "0x1" (i.e. the first bit from the right) with serial number "1" means "whether it has been deleted". In the object data of a calendar object, if the value of the binary number of this bit is 1 (deleted state), it indicates that the calendar object has been deleted (i.e. soft deleted); if the value of the binary number of this bit is 0 (not deleted state), it indicates that the calendar object has not been deleted.

[0127] The flag bit "0x2" (the second bit from the right) with serial number "2" means "whether it is the default calendar". In the object data of a calendar object, if the value of this binary number is 1, it indicates that the calendar object is the default calendar object generated by the background server of the target application. If the value of this binary number is 0, it indicates that the calendar object is not the default calendar object generated by the background server of the target application.

[0128] The flag bit "0x4" (the third bit from the right) with serial number "3" means "whether it is an application calendar". In the object data of a calendar object, if the value of the binary number of this bit is 1, it indicates that the calendar object is an application calendar. If the value of the binary number of this bit is 0, it indicates that the calendar object is an ordinary calendar.

[0129] For example, if the calendar flag bit in the object data of a calendar object is 100, it means that the calendar object is an application calendar, not a default calendar, and has not been deleted. Through the method provided in the embodiment of the present application, a calendar flag bit containing three binary digits can be used to express richer content, which can effectively save storage space.

[0130] It should be noted that if the calendar object creation data is sent by an external application and the second calendar object is an application calendar, the external application's management permission for the second calendar object can be adjustment permission. If the calendar object creation data is submitted by a user and the second calendar object is a regular calendar, the user's management permission for the second calendar object can be adjustment permission.

[0131] The calendar generation method provided in the embodiment of the present application can generate application calendars and ordinary calendars with unified structures, which is conducive to the subsequent compatible management of application calendars and ordinary calendars with unified structures, thereby effectively improving the efficiency of calendar management; flag bits that occupy less storage space can be used to express richer content, thereby effectively saving storage resources.

[0132] See Figure 5 , Figure 5 This is a flowchart of another calendar management method provided in an embodiment of the present application. This calendar management method can be implemented by the target backend server 101 described above, or by other devices capable of implementing the calendar management method. The following uses the calendar management method implemented by the target backend server 101 as an example. The process of the calendar management method provided in the embodiment of the present application includes, but is not limited to:

[0133] S501: Obtain a management request submitted by an operation initiating object through a target application client for a first calendar object, where the type of the first calendar object is the first type or the second type, and the management request includes object authentication data and operation content data.

[0134] In an embodiment of the present application, the operation initiating object may be a user object of a target application client, which may be a mobile terminal or a desktop terminal. The backend server of the target application may obtain a management request submitted by the operation initiating object through the client for the first calendar object. The type of the first calendar object may be the first type or the second type, i.e., the first calendar object may be an application calendar or a normal calendar. The management request may include object authentication data and operation content data.

[0135] In one embodiment, the background server of the target application can receive a calendar query request submitted by the operation initiating object through the client for the first calendar object, and the background server returns the relevant calendar data to the client based on the calendar query request so that the client can display the first calendar object; the background server can then obtain the management request submitted by the operation initiating object based on the first calendar object displayed by the client (that is, the process described in step S501).

[0136] That is, when the object data of the first calendar object includes a list of participating object identifiers, and the list of participating object identifiers includes the object identifiers of the participating objects of the first calendar object and the management rights of the participating objects of each first calendar object, before executing step S501, the following steps can also be executed: obtain a calendar query request submitted by the operation initiating object for the first calendar object through the client of the target application, the calendar query request includes object authentication data; the object authentication data includes the object identifier of the operation initiating object; query the management rights of the operation initiating object for the first calendar object from the list of participating object identifiers according to the object identifier of the operation initiating object, the management rights being any one of subscription rights, viewing rights, editing rights and adjustment rights; determine the first calendar object display data according to the management rights of the operation initiating object for the first calendar object and the object data of the first calendar object; send the first calendar object display data to the client of the target application, and the first calendar object display data is used for the client of the target application to display the first calendar object.

[0137] The backend server of the target application can obtain a calendar query request for the first calendar object, which can include the object identifier of the operation initiating object. The object data of the first calendar object can include a list of participating object identifiers, which can correspond to the above Figure 4 n participating object data blocks in the . The management permission of the operation initiating object for the first calendar object can be determined based on the participating object identifier list. For example, if the object identifier of the operation initiating object is "001" and the participating object identifier list includes the object identifier "001" and the management permission "edit permission" corresponding to the object identifier, then it can be determined that the management permission of the operation initiating object for the first calendar object is "edit permission".

[0138] When the management permission is subscription permission, the operation initiating object can actively perform the subscription operation to subscribe to the first calendar object. After subscription, it can obtain the relevant data of the first calendar object in a read-only manner (for example: calendar identifier, calendar name, schedule name, schedule start time, schedule end time, etc. in the object data).

[0139] When the management permission is view permission, the initiator can directly obtain the relevant data of the first calendar object in read-only mode without actively performing the subscription operation. The data of the first calendar object obtained by view permission and subscription permission is the same.

[0140] When the management authority is editing authority, the operation initiating object can obtain and edit the schedule-related information (for example: schedule name, schedule start time, schedule end time, etc.) and calendar-related information (for example: calendar name, calendar description, etc.) of the first calendar object.

[0141] When the management authority is adjustment authority, the operation initiating object can obtain and edit schedule-related information and calendar-related information of the first calendar object, and can also adjust the management authority of other objects on the first calendar object.

[0142] It should be noted that the optional types of management permissions can be adaptively adjusted based on actual application requirements. For example, management permissions can be limited to either viewing permissions or adjustment permissions. In some cases, if the object identifier of the operation initiating object is not included in the list of participating object identifiers of the first calendar object, it indicates that the operation initiating object has unauthorized access to relevant information about the first calendar object. The target application's backend server can directly generate an operation exception notification message and send it to the target application's client.

[0143] The target application's backend server can determine the first calendar object's display data based on the operation initiating object's management permissions for the first calendar object and the object data of the first calendar object, and send the first calendar object's display data to the target application's client, so that the target application's client displays the first calendar object. The method provided in this embodiment of the application can return different calendar object display data based on different management permissions, thereby implementing hierarchical calendar management and ensuring the security and confidentiality of the calendar's object data.

[0144] See Figure 6 , which is a schematic diagram of a calendar interface provided by an embodiment of the present application. The client of the target application can display Figure 6 In the calendar interface shown, the user object of the target calendar client can be the object initiating the above operation. The calendar interface includes the "Add Calendar" function, as well as three categories: "My Calendar", "Shared Calendars with Me", and "Subscribed Calendars". The calendars in the "My Calendar" category are calendars created by the object initiating the operation (i.e. Figure 6 Calendars in the "Shared with me" category are calendars that the operation initiator has management permissions for (i.e. Figure 6"Calendar created by object 2", "Public calendar 1"), and the calendars in the "Subscribed calendars" category are calendars that the operation initiator actively subscribes to (i.e. Figure 6 "Public Calendar 2" in the .

[0145] The calendar interface can also display the object that created the calendar. For example, "Public Calendar 2" is created by "Application B", so it can be determined that "Calendar of Object 1", "Calendar created by Object 2", "Public Calendar 1" is a common calendar, and "Public Calendar 2" is an application calendar. The calendar interface can also display the schedules in the calendar. Figure 6 For example, if the start time of a schedule in "Public Calendar 1" is 12:00 on the 9th, then "Public Calendar 1" can be displayed in the corresponding position on the calendar interface; if the start time of a schedule in "Public Calendar 2" is 20:00 on the 24th, then "Public Calendar 2" can be displayed in the corresponding position on the calendar interface. The method provided in the embodiments of the present application can intuitively display application calendars and ordinary calendars, which is conducive to improving management efficiency.

[0146] In some cases, if the operation is initiated by the object Figure 6 When a trigger operation is performed on "Public Calendar 1" in the "Shared Calendars with Me" category on the left side of the screen, the background server of the target application can obtain the calendar query request submitted by the operation initiator for "Public Calendar 1". The background server of the target application can use the method provided in the above embodiment to determine the display data of "Public Calendar 1" and send the display data of "Public Calendar 1" to the client of the target application. If the management authority of the operation initiator for "Public Calendar 1" is "view authority", the client of the target application can display the "Public Calendar 1" according to the display data of "Public Calendar 1". Figure 7 shown.

[0147] See Figure 7 , which is a schematic diagram of a calendar card provided in an embodiment of the present application. Figure 7 As shown, the calendar name is "Public Calendar 1", and its calendar description is "Interview Plan". The relevant information of the calendar includes "Object 3 Created" and "Department B Subscribed". Figure 7 The calendar card shown also includes the schedule included in the calendar, the schedule name is "First round of interviews for front-end engineers", the schedule time is "April 2024", and the schedule duration is "April 9, 12:00-14:00".

[0148] If the operation initiator has the management permission "Adjustment Permission" for "Public Calendar 1", the client of the target application can display the data of "Public Calendar 1" as follows: Figure 8 shown.

[0149] See Figure 8 , which is a schematic diagram of another calendar card provided in an embodiment of the present application. Figure 8 As shown, the calendar name is "Public Calendar 1", and the relevant information of the calendar includes "Object 3 Creation", "Department B Subscribed", and "My Permissions - Adjustment (Manage Calendar and Notification Scope)". Figure 8 The calendar card shown also includes the schedule included in the calendar, the schedule name is "First round of interviews for front-end engineers", the schedule time is "April 2024", and the schedule duration is "April 9, 12:00-14:00".

[0150] The client of the target application is displayed as follows Figure 8 After the calendar card is shown, if the operation initiator triggers the triangle in the calendar card, the client of the target application can edit the calendar interface, such as Figure 9 shown.

[0151] See Figure 9 , which is a schematic diagram of an editing calendar interface provided by an embodiment of the present application. Figure 9 As shown, the calendar name "Public Calendar 1" and the calendar description "Interview Plan" are displayed in the calendar editing interface, and both of these contents can be modified. "Subscription scope" refers to the scope of users who can subscribe to the calendar, and "people within the scope are allowed to subscribe to this calendar and view schedule details." "Objects belonging to entity A" are users belonging to entity A. The object initiating the operation has adjustment permissions for the calendar. Therefore, the calendar editing interface can include a notification scope adjustment module, and the object initiating the operation can "add a new notification scope", and "objects within the notification scope can view the calendar." The management permission of "Object 1" for "Public Calendar 1" is viewing permission (i.e. "viewable"); the management permission of "Object 3" for "Public Calendar 1" is adjustment permission (i.e. "adjustable"); the management permission of "Object 2" for "Public Calendar 1" is viewing permission (i.e. "viewable"). The calendar editing interface also includes delete, save, and cancel controls. The initiator can modify the management permissions of "Object 1" and "Object 2" (Object 3 is the creation object of "Public Calendar 1" and its management permissions cannot be modified). After the modification operation is completed, the save control can be triggered, causing the target application client to generate a management request based on the content of the calendar editing interface. The target application's backend server can receive the management request and implement the process described in steps S501-S504.

[0152] In one embodiment, the type of the first calendar object is the second type, and the object data of the first calendar object also includes the creation object data of the usage object. The calendar management method provided by the present application may further include the following steps: matching the object identifier of the operation initiating object with the creation object data of the usage object to obtain a creation object matching result; if the creation object matching result indicates that the object identifier of the operation initiating object matches the creation object data of the usage object, determining that the management authority of the operation initiating object for the first calendar object is an adjustment authority, and executing the step of determining the display data of the first calendar object based on the management authority of the operation initiating object for the first calendar object and the object data of the first calendar object; if the creation object matching result indicates that the object identifier of the operation initiating object does not match the creation object data of the usage object, executing the step of querying the management authority of the operation initiating object for the first calendar object from the participating object identifier list based on the object identifier of the operation initiating object.

[0153] When the type of the first calendar object is the second type (ie, ordinary calendar), the object data of the first calendar object may include the creation object data of the usage object (corresponding to the above Figure 4 The creation object data may include a creation object identifier. The object identifier of the operation initiating object may be matched with the creation object identifier. If the object identifier of the operation initiating object matches the creation object identifier, it indicates that the operation initiating object is the creation object of the first calendar object. The management authority of the operation initiating object for the first calendar object can then be directly determined to be the adjustment authority, and the step of determining the display data of the first calendar object based on the management authority and subsequent steps can be directly executed.

[0154] If the object identifier of the operation initiating object does not match the creation object identifier, it indicates that the operation initiating object is not the creation object of the first calendar object. In this case, the reference object identifier list of the first calendar object can be used to determine the management authority of the operation initiating object for the first calendar object. The method provided in the embodiment of the present application can enable the user object that creates the calendar object to obtain management authority, ensuring the completeness of the method.

[0155] S502: Determine a target object identifier that matches the object authentication data according to the object authentication data and a list of participating object identifiers included in the object data of the first calendar object.

[0156] In an embodiment of the present application, the backend server of the target application can determine a target object identifier that matches the object authentication data based on the object authentication data and the list of participating object identifiers included in the object data of the first calendar object. The list of participating object identifiers can include the object identifiers of each participating object of the first calendar object, as well as the management permissions of each participating object with respect to the first calendar object. The method provided in an embodiment of the present application can determine the target object identifier, which in turn facilitates the subsequent determination of the management permissions of the object initiating the operation with respect to the first calendar object.

[0157] It should be noted that if the target object identifier that matches the object authentication data is not determined, it means that the operation initiating object is not a participating object of the first calendar object. At this time, if the type of the first calendar object is the second type (i.e., ordinary calendar), the object identifier of the operation initiating object can be matched with the creation object data in the object data of the first calendar object. If the matching result indicates that the object identifier of the operation initiating object matches the creation object data, it means that the operation initiating object is the creation object of the first calendar object. The background server of the target application can directly determine that the management authority of the operation initiating object for the first calendar object is the adjustment authority, and can skip step S503 and directly execute step S504; if the matching result indicates that the object identifier of the operation initiating object does not match the creation object data, it means that the operation initiating object has unauthorizedly obtained relevant data of the first calendar object. The background server of the target application can skip steps S503 and S504, directly generate operation exception notification information, and send the operation exception notification information to the client of the target application, or generate an authentication result indicating that the authentication failed.

[0158] S503: Determine an authentication result according to the management authority corresponding to the target object identifier, where the authentication result indicates that the authentication is successful, and the management authority of the operation initiating object for the first calendar object is the management authority corresponding to the target object identifier.

[0159] In an embodiment of the present application, the backend server of the target application may determine an authentication result based on the management permission corresponding to the target object identifier. The authentication result may indicate that the authentication is successful and that the management permission of the operation-initiating object with respect to the first calendar object is the management permission corresponding to the target object identifier. For example, if the management permission corresponding to the target object identifier is "edit permission," the authentication result may indicate that the authentication is successful and that the management permission of the operation-initiating object with respect to the first calendar object is edit permission.

[0160] S504: Perform a management operation on the object data of the first calendar object according to the authentication result and the operation content data.

[0161] In the embodiment of the present application, the backend server of the target application can perform a management operation on the object data of the first calendar object according to the authentication result and the operation content data. The specific implementation method of performing the management operation can be as described in the above step S203.

[0162] In one embodiment, if the background server of the target application performs management operations on the object data of the first calendar object, which involves adjusting the management permissions of the participating objects of the first calendar object, then after the management operation is completed, the background server of the target application can send permission change notification information to the client corresponding to the participating object whose management permissions have been adjusted. For example: Object 1 is a participating object of the first calendar object, and the background server of the target application changes the management permissions of Object 4 for the first calendar object from "view permissions" to "edit permissions", then after the management operation on the object data of the first calendar object is completed, the background server of the target application can generate permission change notification information and send the permission change notification information to the client of the target application corresponding to Object 4. Through the method provided in the embodiment of the present application, the participating objects can be informed of the changes in management permissions in a timely manner, which is conducive to improving the effectiveness of calendar management operations.

[0163] See Figure 10 , this figure is a schematic diagram of a notification interface provided in an embodiment of the present application. Figure 10 The notification interface shown can be the interface displayed by the target client, and the target client can be the client of the target application corresponding to the operation initiating object. The notification interface includes two message objects, "Notification List" and "Object 1", among which the message displayed in the notification list is the permission change notification information sent by the background server of the target application. Figure 10 As shown in the figure, the notification list includes the permission change notification information sent at "17:56" (that is, object 3 changed your permission for "Public Calendar 1" to "Edit Permission"); the permission change notification information sent at "18:00" (that is, object 1 removed you from "Calendar created by Interview Assistant"). The notification list can also include notification message cards (such as Figure 10 As shown, the notification message card includes "Object 3 shares the calendar with you", the calendar name is "Public Calendar 1", and the related information is "My Permissions: Edit Permissions" and a "View Calendar" button).

[0164] Through the calendar management method provided in this application, compatible management of application calendars and ordinary calendars can be achieved, the management permissions between the two can be opened up, and the complexity of calendar management can be reduced; the operation initiating object can customize the modification or deletion of calendars and schedules, and the management permissions of the calendar's participating objects can be customized, which greatly improves the flexibility of calendar management and expands the application scenarios of calendars.

[0165] See Figure 11 , Figure 11 This is a flowchart of another calendar management method provided in an embodiment of the present application. The calendar management method can be implemented by the target backend server 101 described above, or by other devices capable of implementing the calendar management method. The following description uses the calendar management method implemented by the target backend server 101 as an example. The process of the calendar management method provided in the embodiment of the present application includes, but is not limited to:

[0166] S1101: Obtain a management request submitted by an operation initiating object through a web console of a target application for a first calendar object.

[0167] In an embodiment of the present application, the operation initiating object may be a user of a target application's web console (e.g., a world wide web page, i.e., a web page). In this case, the operation initiating object may be referred to as a super administrator. The target application's backend server may obtain a management request submitted by the operation initiating object via the web console for a first calendar object. The first calendar object may be of the first type or the second type, and the management request may include object authentication data and operation content data.

[0168] In one embodiment, the backend server of the target application can receive an entity query request submitted by the operation initiating object for the target entity through the web console, and the backend server returns the object data of all calendar objects (which may include the first calendar object) corresponding to the target entity to the web console based on the entity query request, so that the web console can display all calendar objects of the target entity; the backend server can then obtain the management request submitted by the operation initiating object based on the first calendar object displayed by the web console (i.e., the content described in step S1101).

[0169] That is, before executing step S501, the following steps can also be performed: receiving an entity query request for the target entity submitted by the operation initiating object through the web console of the target application, the target entity is the entity to which the operation initiating object belongs, and the entity query request includes object authentication data; performing entity authentication processing based on the object authentication data to obtain an entity authentication result; if the entity authentication result indicates that the operation initiating object meets the entity query condition, then obtaining the object data of each target calendar object associated with the target entity, each target calendar object including the first calendar object; sending the object data of each target calendar object to the web console of the target application, and the object data of the target calendar object is used to display each target calendar object on the web console of the target application.

[0170] The person who can access the web console of the target application is usually a super administrator, who has the right to modify all calendars in the entity to which he belongs. Figure 4 As can be seen from the data structure shown, the object data of the calendar object may not contain relevant information of the super administrator (for example, the object data of a calendar created by an external application or a user object of a non-super administrator may not contain the object identifier of the super administrator); based on this, the target calendar object can be determined according to the relevant information of the entity to which the super administrator belongs.

[0171] Specifically, the backend server of the target application may receive an entity query request for a target entity submitted by the operation initiating object through the web console of the target application. The target entity is the entity to which the operation initiating object belongs. The entity query request may include object authentication data. Entity authentication processing may be performed based on the object authentication data to obtain an entity authentication result. For example, entity authentication processing may be performed based on the object authentication data to determine whether the entity to which the operation initiating object belongs is the same as the target entity, and whether the operation initiating object is a super administrator of the target entity. If both conditions are met (i.e., the entity query condition is met), the entity authentication result is determined to be that the operation initiating object meets the entity query condition. If one or both of the two conditions are not met (i.e., the entity query condition is not met), the entity authentication result is determined to be that the operation initiating object does not meet the entity query condition.

[0172] If the entity authentication result indicates that the operation initiating object meets the entity query condition, the background server of the target application can obtain the object data of each target calendar object associated with the target entity, and each target calendar object includes the first calendar object. The target calendar object associated with the target entity can be a calendar object whose entity to which the creation object belongs is the target entity, that is, the object identifier of the creation object in the second type calendar data block of the calendar object is associated with the target entity; the target calendar object associated with the target entity can also be a calendar object whose object data contains the entity identifier of the target entity, that is, the entity identifier in the first type calendar data block of the calendar object is the same as the entity identifier of the target entity. The background server of the target application can send the object data of all the determined target calendar objects to the web console of the target application, so that the web console can display each target calendar object.

[0173] If the entity authentication result indicates that the operation initiating object does not meet the entity query conditions, the target application's backend server can directly generate a permission-missing notification message and send the permission-missing notification message to the target application's web console. The method provided in this embodiment of the application allows a super administrator to obtain object data for all calendars associated with the target entity, which helps improve the super administrator's calendar management efficiency.

[0174] See Figure 12 , which is a schematic diagram of a web console provided by an embodiment of the present application. After the backend server of the target application receives the entity query request sent by the operation initiating object, it can determine the object data of multiple target calendar objects and send the object data of these target calendar objects to the web console. The target calendar objects displayed by the web console can be as follows Figure 12 shown. Figure 12 In the web console, the interface is named "All-Staff Calendar", and the object initiating the operation can "create a calendar for all staff and arrange schedules in a unified manner. Objects can use the schedule to arrange personal work, and can also initiate schedules for multiple objects for collaboration". The "All-Staff Calendar" interface includes a function button for "Add All-Staff Calendar" and also displays the object data of the target calendar object. Among them, the calendar name is "First Calendar Object", its calendar description is "Interview Plan", its administrator is "Object 1", and the subscription scope is "Object 1"; the calendar name is "Target Calendar 2", its calendar description is empty, its administrator is "Object 2", and the subscription scope is "Entity 1" (that is, objects belonging to Entity 1 can subscribe to the calendar); the calendar name is "Target Calendar 3", its calendar description is "Modify Description", its administrator is "Object 1", and the subscription scope is "Object 5"; the calendar name is "Target Calendar 4", its calendar description is "Work Plan", its administrator is "Object 3", and the subscription scope is "Object 1". For each target calendar object displayed in the interface, the object initiating the operation can perform "Edit" or "Delete" operations.

[0175] Assume that the operation is initiated by the object Figure 12 If an "Edit" operation is performed on the "First Calendar Object" in the target application, the target application's page console may display an "Edit All Calendar" card. The person initiating the operation may enter operation content data based on the "Edit All Calendar" card. The target application's page console may determine a management request for the first calendar object based on the operation content data, and the target application's backend server may receive the management request for the first calendar object, i.e., the process described in step S1101.

[0176] See Figure 13 , which is a schematic diagram of an interface for editing the calendar of all employees provided in an embodiment of the present application. Figure 13As shown, the "calendar name" displayed in the edit all-staff calendar interface is "first calendar object", the "calendar description" is "interview plan", and the "participating members" include "object 11" (whose management authority for the first calendar object is adjustment authority) and "object 13" (whose management authority for the first calendar object is adjustment authority). "Automatic subscription scope" is "objects belonging to the target entity" (that is, all objects belonging to the target entity have subscription authority to the first calendar object). The operation initiating object can modify the calendar name, calendar description, participating members, and subscription scope, and can also add or reduce participating members, and can also modify the management authority of participating members for the first calendar object. The edit all-staff calendar interface also includes an "OK" control and a "Cancel" control. The web console of the target application can determine the management request based on the content entered by the operation initiating object through the edit all-staff calendar interface, and can send the management request to the background server of the target application. The background server of the target application can receive the management request, that is, the process described in step S1101.

[0177] S1102: Determine a first entity identifier of an entity to which the first calendar object belongs, and determine a second entity identifier of an entity to which the operation initiating object belongs based on the object authentication data.

[0178] In the embodiment of the present application, the backend server of the target application can determine the first entity identifier of the entity to which the first calendar object belongs. When the first calendar object is an application calendar, Figure 4 As can be seen from the data structure shown, the object data of the first calendar object includes an entity identifier, which can be determined as the first entity identifier. When the first calendar object is a common calendar, Figure 4 As can be seen from the data structure shown, the object data of the first calendar object includes the object identifier of the created object. Based on this object identifier, the entity to which the created object belongs can be determined, and the entity identifier of this entity can be determined as the first entity identifier. The object authentication data includes the object identifier of the object to which the operation was initiated. Based on this object identifier, the second entity identifier of the entity to which the operation was initiated can be determined.

[0179] S1103: Determine an authentication result according to the first entity identifier and the second entity identifier.

[0180] In an embodiment of the present application, the background server of the target application can match the first entity identifier and the second entity identifier to obtain an entity identifier matching result. If the entity identifier matching result indicates that the first entity identifier and the second entity identifier match, it means that the management request initiated by the operation initiating object has not exceeded its authority, and the authentication result can be determined to be authentication passed, and the management authority of the operation initiating object for the first calendar object is a super authority. If the entity identifier matching result indicates that the first entity identifier and the second entity identifier do not match, it means that the management request initiated by the operation initiating object has exceeded its authority (it may be that the operation initiating object manages the calendar object across entities), and the authentication result can be determined to be authentication failure. Through the method provided in the embodiment of the present application, the operation initiating object can be authenticated before executing the management operation, thereby effectively avoiding the situation of unauthorized operation and ensuring the security and confidentiality of the calendar object data.

[0181] In one embodiment, the management request includes object authentication data, which may include the object identifier of the object initiating the operation; the background server of the target application may also perform object determination processing based on the object identifier of the operation initiating object to determine whether the operation initiating object is a super administrator. If the object determination result indicates that the operation initiating object is a super administrator, steps S1102-S1104 may be executed; if the object determination result indicates that the operation initiating object is not a super administrator, steps S1102-S1104 may not be executed, and the background server of the target application may directly generate object exception notification information and send the object exception notification information to the web console of the target application. The method provided by the embodiment of the present application can avoid unauthorized operations on objects (i.e., objects that are not super administrators).

[0182] S1104: Perform a management operation on the object data of the first calendar object according to the authentication result and the operation content data.

[0183] In the embodiment of the present application, the backend server of the target application can perform a management operation on the object data of the first calendar object according to the authentication result and the operation content data. The specific implementation method of performing the management operation can be as described in the above step S203.

[0184] It should be noted that when an external application needs to access and manage the first calendar object, the target backend server can receive an application management request (for requesting management operations on the first calendar object) or an application query request (for requesting to obtain and display the first calendar object) sent by the external application through the application interface. The process of the target application's backend server responding to application management requests and application query requests is similar. The following uses the target application's backend server responding to an application management request as an example for explanation:

[0185] The application management request may include the entity identifier of the entity corresponding to the external application and the application identifier of the external application; the background server of the target application can perform authentication processing based on the application management request to obtain an application authentication result (the method for implementing the authentication processing can be as shown in the above steps S1102-S1103, and the entity identifier of the entity corresponding to the external application can be determined as the second entity identifier. If the first entity identifier matches the second entity identifier, and the application identifier of the external application in the application management request matches the application identifier of the creation application in the object data of the first calendar object, then the authentication result is determined to be authentication passed, and the management authority of the external application for the first calendar object is adjustment authority; otherwise, the authentication result is determined to be authentication failed). The background server of the target calendar can perform management operations on the object data of the first calendar object based on the application authentication result and the application management request. Through the method provided in the embodiment of the present application, the management operations of the external application on the calendar can be implemented, which effectively expands the application scenarios.

[0186] The calendar management method provided in the embodiment of the present application can achieve compatible management of application calendars and ordinary calendars, open up the management permissions between the two, and enable super administrators or external applications to customize the modification or deletion of calendars and schedules. It can also customize the management permissions of the calendar's participating objects, allowing super administrators to manage all calendar objects belonging to the same entity, which can meet more application scenarios, has good universality, and also reduces the complexity of calendar management.

[0187] The above describes in detail the method of the embodiment of the present application. In order to facilitate better implementation of the above scheme of the embodiment of the present application, the device of the embodiment of the present application is provided below accordingly.

[0188] See Figure 14 , Figure 14 This is a structural block diagram of a calendar management device provided in an embodiment of the present application. The calendar management device can be set in the computer device provided in an embodiment of the present application. The computer device can be the above-mentioned Figure 1 The target backend server 101 in the calendar management system is shown. Figure 14 The calendar management device shown can be a computer program running on a computer device, and the calendar management device can be used to perform Figure 2 or Figure 3 or Figure 5 or Figure 11 Some or all of the steps in the method embodiment shown. Figure 14 , the blockchain-based data processing device may include the following units:

[0189] An acquiring unit 1401 is configured to acquire a management request from an operation initiating object for a first calendar object in a target application, where the first calendar object is of a first type or a second type, where the first type of calendar object is created by an external application by calling the target application, and the second type of calendar object is created by a user object of the target application; the management request includes object authentication data and operation content data;

[0190] Processing unit 1402 is configured to perform authentication processing on the operation initiating object according to the object authentication data to obtain an authentication result, wherein the authentication result is used to indicate whether the authentication is passed and the management authority of the operation initiating object with respect to the first calendar object;

[0191] The management unit 1403 is configured to perform a management operation on the object data of the first calendar object according to the authentication result and the operation content data.

[0192] In one embodiment, the processing unit 1402 is further configured to perform the following steps:

[0193] Obtaining calendar object creation data, the calendar object creation data including one or more of calendar object basic data, schedule creation data, and participant object description data; the schedule creation data is used to indicate schedules included in the second calendar object, and the participant object description data is used to indicate object identifiers of participant objects of the second calendar object and management permissions of each participant object of the second calendar object with respect to the second calendar object;

[0194] The object data of the second calendar object is generated according to the calendar object creation data to create the second calendar object.

[0195] In one embodiment, the processing unit 1402 is configured to perform the following steps when obtaining calendar object creation data:

[0196] Acquire calendar object creation data submitted by a user of the target application through the target application, wherein the calendar object creation data also includes creation object data of the user; or

[0197] Calendar object creation data sent by the external application through the application interface of the target application is received, where the calendar object creation data further includes an application identifier of the external application and entity information corresponding to the external application.

[0198] In one embodiment, the object data of the first calendar object includes a list of participating object identifiers, wherein the list of participating object identifiers includes object identifiers of participating objects of the first calendar object and management permissions of the participating objects of the first calendar object. The processing unit 1402 is further configured to perform the following steps:

[0199] Obtaining a calendar query request submitted by the operation initiating object through the client of the target application for the first calendar object, wherein the calendar query request includes the object authentication data; the object authentication data includes the object identifier of the operation initiating object;

[0200] querying the management authority of the operation initiating object on the first calendar object from the participating object identifier list according to the object identifier of the operation initiating object, where the management authority is any one of subscription authority, viewing authority, editing authority and adjustment authority;

[0201] determining first calendar object display data according to the management authority of the operation initiating object on the first calendar object and the object data of the first calendar object;

[0202] The first calendar object display data is sent to the client of the target application, where the first calendar object display data is used by the client of the target application to display the first calendar object.

[0203] In one embodiment, the type of the first calendar object is the second type, and the object data of the first calendar object further includes the creation object data of the usage object. The processing unit 1402 is further configured to perform the following steps:

[0204] Matching the object identifier of the operation initiating object with the creation object data of the use object to obtain a creation object matching result;

[0205] If the creation object matching result indicates that the object identifier of the operation initiating object matches the creation object data of the use object, determining that the management authority of the operation initiating object for the first calendar object is an adjustment authority, and performing the step of determining display data of the first calendar object based on the management authority of the operation initiating object for the first calendar object and the object data of the first calendar object;

[0206] If the creation object matching result indicates that the object identifier of the operation initiating object does not match the creation object data of the use object, a step is executed to query the management authority of the operation initiating object for the first calendar object from the participating object identifier list according to the object identifier of the operation initiating object.

[0207] In one embodiment, the processing unit 1402 is configured to authenticate the operation initiating object according to the object authentication data, and upon obtaining an authentication result, specifically to execute the following steps:

[0208] Determining a target object identifier that matches the object authentication data based on the object authentication data and the participating object identifier list;

[0209] An authentication result is determined according to the management authority corresponding to the target object identifier, the authentication result indicating that the authentication is passed, and the management authority of the operation initiating object for the first calendar object is the management authority corresponding to the target object identifier.

[0210] In one embodiment, the processing unit 1402 is further configured to perform the following steps:

[0211] receiving an entity query request for a target entity submitted by the operation initiating object through the web console of the target application, wherein the target entity is the entity to which the operation initiating object belongs, and the entity query request includes the object authentication data;

[0212] Perform entity authentication processing according to the object authentication data to obtain an entity authentication result;

[0213] If the entity authentication result indicates that the operation initiating object meets the entity query condition, obtaining object data of each target calendar object associated with the target entity, wherein the each target calendar object includes the first calendar object;

[0214] The object data of each target calendar object is sent to the web console of the target application, and the object data of the target calendar object is used by the web console of the target application to display each target calendar object.

[0215] In one embodiment, the processing unit 1402 is configured to authenticate the operation initiating object according to the object authentication data, and upon obtaining an authentication result, specifically to execute the following steps:

[0216] Determining a first entity identifier of an entity to which the first calendar object belongs;

[0217] Determining a second entity identifier of the entity to which the operation initiating object belongs according to the object authentication data;

[0218] Matching the first entity identifier and the second entity identifier to obtain an entity identifier matching result;

[0219] If the entity identifier matching result indicates that the first entity identifier and the second entity identifier match, then determining that the authentication result is authentication passed, and the management authority of the operation initiating object for the first calendar object is a super authority;

[0220] If the entity identifier matching result indicates that the first entity identifier and the second entity identifier do not match, the authentication result is determined to be authentication failure.

[0221] In one embodiment, the management unit 1403 is configured to perform the following steps when performing a management operation on the object data of the first calendar object according to the authentication result and the operation content data:

[0222] If the authentication result indicates that the authentication is passed, modifying the object data of the first calendar object according to the operation content data to obtain modified object data of the first calendar object;

[0223] The object data of the modified first calendar object is stored.

[0224] In one embodiment, the object data of the first calendar object includes a deletion flag, and the operation content data indicates deletion of the first calendar object; the management unit 1403 is configured to modify the object data of the first calendar object according to the operation content data, and to obtain the modified object data of the first calendar object by specifically performing the following steps:

[0225] The deletion flag in the object data of the first calendar object is set to a deleted state.

[0226] Figure 14 The various units in the calendar management device shown can be individually or completely combined into one or several other units to form a whole, or one (or more) of the units can be further divided into multiple functionally smaller units to form a whole, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In actual applications, the functions of one unit can also be implemented by multiple units, or the functions of multiple units can be implemented by one unit. In other embodiments of the present application, the blockchain-based data processing device can also include other units. In actual applications, these functions can also be implemented with the assistance of other units and can be implemented by collaboration of multiple units.

[0227] In one embodiment, the program can be executed by running on a general-purpose computing device such as a computer including a central processing unit (CPU), a random access memory (RAM), a read-only memory (ROM), and other processing elements and storage elements. Figure 2 or Figure 5 or Figure 11 A computer program for each step involved in part or all of the method shown is constructed as follows Figure 14 The calendar management device shown in and the calendar management method of the embodiment of the present application are implemented. The computer program can be recorded on a computer-readable storage medium, for example, and loaded into the above-mentioned computing device through the computer-readable storage medium and run therein.

[0228] The calendar management device provided by the embodiment of the present application can receive management requests sent by different operation objects (external applications or user objects), realize the joint management of calendars by different operation objects, and expand the application scenarios; it can receive management requests for application calendars or ordinary calendars, thereby realizing compatible management of application calendars and ordinary calendars, eliminating the management barriers between application calendars and ordinary calendars, improving the efficiency of calendar management, and reducing the complexity of calendar management; it can authenticate the operation initiating object, thereby ensuring the rationality of the management operation of the object data of the calendar object, avoiding unauthorized operations, and ensuring the security of the object data; it can perform soft deletion operations to effectively avoid data loss caused by accidental deletion operations.

[0229] Based on the above method and device embodiments, the present application provides a computer device. Figure 15 , Figure 15 A structural block diagram of a computer device provided in an embodiment of the present application. Figure 15 The computer device shown can be the above Figure 1 The target background server 101 in. Figure 15 The computer device shown includes at least a processor 1501, an input interface 1502, an output interface 1503, and a computer-readable storage medium 1504. The processor 1501, the input interface 1502, the output interface 1503, and the computer-readable storage medium 1504 may be connected via a bus or other means.

[0230] Computer-readable storage medium 1504 may be stored in a memory of a computer device. Computer-readable storage medium 1504 is used to store a computer program, which includes computer instructions. Processor 1501 is used to execute the computer program stored in computer-readable storage medium 1504. Processor 1501 (or CPU (Central Processing Unit)) is the computing and control core of the computer device and is suitable for implementing computer programs, specifically loading and executing computer programs to implement corresponding method processes or corresponding functions.

[0231] The embodiment of the present application also provides a computer-readable storage medium (Memory), which is a memory device in a computer device for storing programs and data. It is understandable that the computer-readable storage medium here can include both built-in storage media in the computer device and, of course, extended storage media supported by the computer device. The computer-readable storage medium provides a storage space that stores the operating system of the computer device. In addition, a computer program suitable for being loaded and executed by the processor is also stored in the storage space. It should be noted that the computer-readable storage medium here can be a high-speed RAM memory or a non-volatile memory (Non-Volatile Memory), such as at least one disk memory; optionally, it can also be at least one computer-readable storage medium located away from the aforementioned processor.

[0232] In a specific implementation, the processor 1501 can load and execute the computer program stored in the computer-readable storage medium 1504 to implement the above-mentioned Figure 2 In a specific implementation, the computer program in the computer-readable storage medium 1504 is loaded by the processor 1501 and executes the following steps:

[0233] Obtaining a management request from an operation initiating object for a first calendar object in a target application, where the first calendar object is of a first type or a second type, where the first type of calendar object is created by an external application by calling the target application, and the second type of calendar object is created by a user object of the target application; the management request includes object authentication data and operation content data;

[0234] authenticating the operation initiating object according to the object authentication data to obtain an authentication result, wherein the authentication result is used to indicate whether the authentication is passed and the management authority of the operation initiating object with respect to the first calendar object;

[0235] A management operation is performed on the object data of the first calendar object according to the authentication result and the operation content data.

[0236] In one embodiment, when the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501, it is further configured to perform the following steps:

[0237] Obtaining calendar object creation data, the calendar object creation data including one or more of calendar object basic data, schedule creation data, and participant object description data; the schedule creation data is used to indicate schedules included in the second calendar object, and the participant object description data is used to indicate object identifiers of participant objects of the second calendar object and management permissions of each participant object of the second calendar object with respect to the second calendar object;

[0238] The object data of the second calendar object is generated according to the calendar object creation data to create the second calendar object.

[0239] In one embodiment, when the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 to obtain calendar object creation data, the computer program is specifically configured to perform the following steps:

[0240] Acquire calendar object creation data submitted by a user of the target application through the target application, wherein the calendar object creation data also includes creation object data of the user; or

[0241] Calendar object creation data sent by the external application through the application interface of the target application is received, where the calendar object creation data further includes an application identifier of the external application and entity information corresponding to the external application.

[0242] In one embodiment, the object data of the first calendar object includes a list of participating object identifiers, wherein the list of participating object identifiers includes object identifiers of participating objects of the first calendar object and management permissions of the participating objects of the first calendar object. When the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501, it is further configured to perform the following steps:

[0243] Obtaining a calendar query request submitted by the operation initiating object through the client of the target application for the first calendar object, wherein the calendar query request includes the object authentication data; the object authentication data includes the object identifier of the operation initiating object;

[0244] querying the management authority of the operation initiating object on the first calendar object from the participating object identifier list according to the object identifier of the operation initiating object, where the management authority is any one of subscription authority, viewing authority, editing authority and adjustment authority;

[0245] determining first calendar object display data according to the management authority of the operation initiating object on the first calendar object and the object data of the first calendar object;

[0246] The first calendar object display data is sent to the client of the target application, where the first calendar object display data is used by the client of the target application to display the first calendar object.

[0247] In one embodiment, the type of the first calendar object is the second type, and the object data of the first calendar object further includes the creation object data of the usage object. When the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501, it is further configured to perform the following steps:

[0248] Matching the object identifier of the operation initiating object with the creation object data of the use object to obtain a creation object matching result;

[0249] If the creation object matching result indicates that the object identifier of the operation initiating object matches the creation object data of the use object, determining that the management authority of the operation initiating object for the first calendar object is an adjustment authority, and performing the step of determining display data of the first calendar object based on the management authority of the operation initiating object for the first calendar object and the object data of the first calendar object;

[0250] If the creation object matching result indicates that the object identifier of the operation initiating object does not match the creation object data of the use object, a step is executed to query the management authority of the operation initiating object for the first calendar object from the participating object identifier list according to the object identifier of the operation initiating object.

[0251] In one embodiment, the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 to authenticate the operation initiating object according to the object authentication data. When an authentication result is obtained, the computer program is specifically configured to perform the following steps:

[0252] Determining a target object identifier that matches the object authentication data based on the object authentication data and the participating object identifier list;

[0253] An authentication result is determined according to the management authority corresponding to the target object identifier, the authentication result indicating that the authentication is passed, and the management authority of the operation initiating object for the first calendar object is the management authority corresponding to the target object identifier.

[0254] In one embodiment, when the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501, it is further configured to perform the following steps:

[0255] receiving an entity query request for a target entity submitted by the operation initiating object through the web console of the target application, wherein the target entity is the entity to which the operation initiating object belongs, and the entity query request includes the object authentication data;

[0256] Perform entity authentication processing according to the object authentication data to obtain an entity authentication result;

[0257] If the entity authentication result indicates that the operation initiating object meets the entity query condition, obtaining object data of each target calendar object associated with the target entity, wherein the each target calendar object includes the first calendar object;

[0258] The object data of each target calendar object is sent to the web console of the target application, and the object data of the target calendar object is used by the web console of the target application to display each target calendar object.

[0259] In one embodiment, the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 to authenticate the operation initiating object according to the object authentication data. When an authentication result is obtained, the computer program is specifically configured to perform the following steps:

[0260] Determining a first entity identifier of an entity to which the first calendar object belongs;

[0261] Determining a second entity identifier of the entity to which the operation initiating object belongs according to the object authentication data;

[0262] Matching the first entity identifier and the second entity identifier to obtain an entity identifier matching result;

[0263] If the entity identifier matching result indicates that the first entity identifier and the second entity identifier match, then determining that the authentication result is authentication passed, and the management authority of the operation initiating object for the first calendar object is a super authority;

[0264] If the entity identifier matching result indicates that the first entity identifier and the second entity identifier do not match, the authentication result is determined to be authentication failure.

[0265] In one embodiment, when the computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 and performs a management operation on the object data of the first calendar object based on the authentication result and the operation content data, the computer program is specifically configured to perform the following steps:

[0266] If the authentication result indicates that the authentication is passed, modifying the object data of the first calendar object according to the operation content data to obtain modified object data of the first calendar object;

[0267] The object data of the modified first calendar object is stored.

[0268] In one embodiment, the object data of the first calendar object includes a deletion flag, and the operation content data indicates deletion of the first calendar object. The computer program in the computer-readable storage medium 1504 is loaded and executed by the processor 1501 to modify the object data of the first calendar object according to the operation content data. When the modified object data of the first calendar object is obtained, the computer program is specifically configured to execute the following steps:

[0269] The deletion flag in the object data of the first calendar object is set to a deleted state.

[0270] The computer device provided by the embodiment of the present application can receive management requests sent by different operation objects (external applications or user objects), realize the joint management of calendars by different operation objects, and expand the application scenarios; it can receive management requests for application calendars or ordinary calendars, thereby realizing compatible management of application calendars and ordinary calendars, eliminating the management barriers between application calendars and ordinary calendars, improving the efficiency of calendar management, and reducing the complexity of calendar management; it can authenticate the operation initiating object, thereby ensuring the rationality of the management operation of the object data of the calendar object, avoiding unauthorized operations, and ensuring the security of the object data; it can perform soft deletion operations to effectively avoid data loss caused by accidental deletion operations.

[0271] The present application also provides a computer-readable storage medium storing computer instructions that, when executed on a computer device, cause the computer device to execute the steps of each method embodiment of the present application to implement the calendar management method provided by the present application. The specific implementation method can be found in the previous description and will not be repeated here.

[0272] The present application also provides a computer program product, comprising a computer program or computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the computer device to perform the steps of each method embodiment of the present application to implement the calendar management method provided in the present application. The specific implementation method can be found in the previous description and will not be repeated here.

[0273] Those skilled in the art will appreciate that the units and algorithmic steps of each example described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application. In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuitry or memory) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that contains the function of the module or unit.

[0274] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted via a computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0275] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any technical object of a person skilled in the art that is within the technical scope disclosed in the present application and that can be easily conceived of by a person skilled in the art is within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection of the claims.

Claims

1. A calendar management method, characterized in that: The method comprises: Obtaining a management request from an operation initiating object for a first calendar object in a target application, where the first calendar object is of a first type or a second type, where the first type of calendar object is created by an external application by calling the target application, and the second type of calendar object is created by a user object of the target application; the management request includes object authentication data and operation content data; authenticating the operation initiating object according to the object authentication data to obtain an authentication result, wherein the authentication result is used to indicate whether the authentication is passed and the management authority of the operation initiating object with respect to the first calendar object; A management operation is performed on the object data of the first calendar object according to the authentication result and the operation content data.

2. The method according to claim 1, wherein The method further comprises: Obtaining calendar object creation data, the calendar object creation data including one or more of calendar object basic data, schedule creation data, and participant object description data; the schedule creation data is used to indicate schedules included in the second calendar object, and the participant object description data is used to indicate object identifiers of participant objects of the second calendar object and management permissions of each participant object of the second calendar object with respect to the second calendar object; The object data of the second calendar object is generated according to the calendar object creation data to create the second calendar object.

3. The method according to claim 2, characterized in that The step of obtaining calendar object creation data includes: Acquire calendar object creation data submitted by a user of the target application through the target application, wherein the calendar object creation data also includes creation object data of the user; or Calendar object creation data sent by the external application through the application interface of the target application is received, where the calendar object creation data further includes an application identifier of the external application and entity information corresponding to the external application.

4. The method according to claim 1 or 2, wherein: The object data of the first calendar object includes a list of participating object identifiers, wherein the list of participating object identifiers includes object identifiers of participating objects of the first calendar object and management rights of the participating objects of the first calendar object; the method further includes: Obtaining a calendar query request submitted by the operation initiating object through the client of the target application for the first calendar object, wherein the calendar query request includes the object authentication data; the object authentication data includes the object identifier of the operation initiating object; querying the management authority of the operation initiating object on the first calendar object from the participating object identifier list according to the object identifier of the operation initiating object, where the management authority is any one of subscription authority, viewing authority, editing authority and adjustment authority; determining first calendar object display data according to the management authority of the operation initiating object on the first calendar object and the object data of the first calendar object; The first calendar object display data is sent to the client of the target application, where the first calendar object display data is used by the client of the target application to display the first calendar object.

5. The method according to claim 4, wherein The type of the first calendar object is the second type, the object data of the first calendar object further includes the creation object data of the usage object, and the method further includes: Matching the object identifier of the operation initiating object with the creation object data of the use object to obtain a creation object matching result; If the creation object matching result indicates that the object identifier of the operation initiating object matches the creation object data of the use object, determining that the management authority of the operation initiating object for the first calendar object is an adjustment authority, and performing the step of determining display data of the first calendar object based on the management authority of the operation initiating object for the first calendar object and the object data of the first calendar object; If the creation object matching result indicates that the object identifier of the operation initiating object does not match the creation object data of the use object, a step is executed to query the management authority of the operation initiating object for the first calendar object from the participating object identifier list according to the object identifier of the operation initiating object.

6. The method according to claim 4, wherein The performing authentication processing on the operation initiating object according to the object authentication data to obtain an authentication result includes: Determining a target object identifier that matches the object authentication data based on the object authentication data and the participating object identifier list; An authentication result is determined according to the management authority corresponding to the target object identifier, the authentication result indicating that the authentication is passed, and the management authority of the operation initiating object for the first calendar object is the management authority corresponding to the target object identifier.

7. The method according to any one of claims 1 to 3, wherein: The method further comprises: receiving an entity query request for a target entity submitted by the operation initiating object through the web console of the target application, wherein the target entity is the entity to which the operation initiating object belongs, and the entity query request includes the object authentication data; Perform entity authentication processing according to the object authentication data to obtain an entity authentication result; If the entity authentication result indicates that the operation initiating object meets the entity query condition, obtaining object data of each target calendar object associated with the target entity, wherein the each target calendar object includes the first calendar object; The object data of each target calendar object is sent to the web console of the target application, and the object data of the target calendar object is used by the web console of the target application to display each target calendar object.

8. The method according to claim 7, wherein The performing authentication processing on the operation initiating object according to the object authentication data to obtain an authentication result includes: Determining a first entity identifier of an entity to which the first calendar object belongs; Determine a second entity identifier of the entity to which the operation initiating object belongs according to the object authentication data; Matching the first entity identifier and the second entity identifier to obtain an entity identifier matching result; If the entity identifier matching result indicates that the first entity identifier and the second entity identifier match, then determining that the authentication result is authentication passed, and the management authority of the operation initiating object for the first calendar object is a super authority; If the entity identifier matching result indicates that the first entity identifier and the second entity identifier do not match, the authentication result is determined to be authentication failure.

9. The method according to any one of claims 1 to 3, wherein: The performing a management operation on the object data of the first calendar object according to the authentication result and the operation content data includes: If the authentication result indicates that the authentication is passed, modifying the object data of the first calendar object according to the operation content data to obtain modified object data of the first calendar object; The object data of the modified first calendar object is stored.

10. The method according to claim 9, wherein The object data of the first calendar object includes a deletion flag, and the operation content data indicates deletion of the first calendar object; and modifying the object data of the first calendar object according to the operation content data to obtain the modified object data of the first calendar object includes: The deletion flag in the object data of the first calendar object is set to a deleted state.

11. A calendar management device, characterized in that: include: an acquiring unit, configured to acquire a management request from an operation initiating object for a first calendar object in a target application, wherein the first calendar object is of a first type or a second type, wherein the first type of calendar object is created by an external application by calling the target application, and the second type of calendar object is created by a user object of the target application; the management request includes object authentication data and operation content data; a processing unit, configured to perform authentication processing on the operation initiating object according to the object authentication data to obtain an authentication result, wherein the authentication result is used to indicate whether the authentication is passed and the management authority of the operation initiating object with respect to the first calendar object; A management unit is used to perform a management operation on the object data of the first calendar object according to the authentication result and the operation content data.

12. A computer device, characterized in that: The computer device comprises: a processor suitable for implementing a computer program; A computer-readable storage medium storing a computer program, wherein the computer program is suitable for being loaded by the processor and implementing the calendar management method according to any one of claims 1 to 10.

13. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which is suitable for being loaded by a processor and implementing the calendar management method according to any one of claims 1 to 10.

14. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the calendar management method according to any one of claims 1 to 10 is implemented.

Images