Permission management method, graphical interface and related apparatus

Abstract

Disclosed in the present application are a permission management method, a graphical interface and a related apparatus. In the method, an electronic device can store a schedule created by a calendar application and other schedules created by other applications in the calendar application, and mark the application to which each schedule belongs. Then, when there is an application requesting the acquisition of the permission to access the calendar application, the electronic device can use, from among a plurality of permission levels, a permission level selected by a user (for example, only accessing the permission level of a calendar created by the application), so as to grant a corresponding permission to the application, thereby preventing the application from accessing schedules created by other applications, apart from the present application itself, in the calendar without consent.

Description

Rights management method, graphical interface and related devices

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on June 15, 2023, with application number 202310716159.2 and application name “Authority Management Method, Graphical Interface and Related Devices”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminals, and in particular to a rights management method, a graphical interface, and related devices. Background Art

[0003] Nowadays, electronic devices record a lot of users' private information. For example, calendar applications record users' schedules. When users use electronic devices, some applications usually require the calendar application to grant certain permissions before completing corresponding tasks.

[0004] Under the premise of protecting user privacy and ensuring the normal use of various applications, how to manage the permission to access the calendar is an urgent problem to be solved.

[0005] Summary of the Invention

[0006] This application discloses a permission management method, a graphical interface, and related devices. In this method, an electronic device can store schedules created by the calendar application itself, as well as schedules created by other applications in the calendar application, and mark the application to which each schedule belongs. Afterwards, when an application requests permission to access the calendar application, the electronic device can use the permission level selected by the user (for example, the permission level for accessing only calendars created by this application) from multiple permission levels to grant the application the corresponding permission, thereby preventing the application from accessing schedules not created by this application without permission.

[0007] In the first aspect, the present application provides a permission management method, which includes: when displaying a first interface, receiving a first operation; in response to the first operation, displaying a first window on the first interface, the first window including: the name of a first application; a first option, when receiving a second operation on the first option, setting the permission of the first application to access a calendar application to a first permission, the first permission being access to all schedules of the calendar application; and a second option, when receiving a third operation on the second option, setting the permission of the first application to access the calendar application to a second permission, the second permission being access only schedules created by the first application.

[0008] After implementing the method provided in the first aspect, the user can personalize the first application's calendar access permissions, including setting the first application's calendar access permissions to access all schedules in the calendar application, or setting it to access only schedules created by the first application. This ensures both user privacy and the normal use of the first application.

[0009] In combination with the method described in the first aspect, the first interface includes an interface for setting an application, or an interface of the first application.

[0010] In this way, the user can adjust the permission of the first application to access the calendar in various ways, such as by setting the application or adjusting it in the first application.

[0011] In combination with the method described in the first aspect, the first window further includes access type information, and the access type information includes: reading a schedule, and / or creating, deleting, or modifying a schedule.

[0012] In this way, permission settings can be performed for specific access types included in the first application's access to the calendar.

[0013] In combination with the method described in the first aspect, the first application is a shopping application, and the first interface is the interface of the first application; the method also includes: receiving the second operation on the first option; receiving the second operation on the first option, and in response to the second operation, setting the first application's access permission to the calendar application to the first permission; displaying the second interface of the first application, the products included in the second interface are different from the products included in the first interface.

[0014] In this way, after the user sets the access permission of the shopping application to access all schedules in the calendar application, the second interface displayed by the shopping application includes recommended products based on all the obtained schedules. Before the user sets the access permission of the shopping application to access all schedules in the calendar application, the products included in the first interface of the shopping application are the default products provided by the shopping application and are not related to the schedule.

[0015] In combination with the method described in the first aspect, the first application is a schedule management application; when a second operation on the first option is received, the permission of the first application to access the calendar application is set to the first permission, the method also includes: receiving a second operation on the first option, and in response to the operation, setting the permission of the first application to access the calendar application to the first permission; displaying the third interface of the first application, the third interface including all schedules in the calendar application; or, receiving a third operation on the second option, and in response to the operation, setting the permission of the first application to access the calendar application to the second permission; displaying the fourth interface of the first application, the fourth interface only including schedules created by the first application.

[0016] For example, all schedules in the calendar application include the schedule of the second application, and the second application may be a shopping application, etc. The fourth interface of the first application may not include the schedule of the second application.

[0017] In this way, if the schedule management app is set to allow access to all schedules in the calendar app, the schedule management app can synchronously display all schedules in the calendar. However, if the schedule management app is set to only allow access to schedules within this app, the schedule management app will only display its own schedules, i.e., it cannot read schedules of other apps in the calendar app, thus preventing the user's privacy from being analyzed or leaked.

[0018] In combination with the method described in the first aspect, after setting the first application's permission to access the calendar application to the first permission, or after setting the first application's permission to access the calendar application to the second permission, the method also includes: displaying the fifth interface of the calendar application, the fifth interface including the first schedule created by the first application.

[0019] In this way, no matter the first application is set to allow access to all schedules or is set to access only the schedules of the first application, the first application can create schedules in the calendar application.

[0020] In combination with the method described in the first aspect, when the interface of the calendar application is displayed, a fourth operation is received, and in response to the fourth operation, the second schedule is displayed in the interface of the calendar application.

[0021] In combination with the method described in the first aspect, the first window also includes a third option; the method also includes: when a fifth operation on the third option is received, setting the first application's access permission to the calendar application to a third permission, and the third permission is to prohibit access to the calendar application's schedule.

[0022] In this way, when the user can personalize the permission for the first application to access the calendar, the user can also set the permission to prohibit access to the schedule of the calendar application.

[0023] In combination with the method described in the first aspect, after setting the permission of the first application to access the calendar application to the first permission, the method also includes: displaying a prompt message, which is used to prompt the user to adjust the permission of the first application; receiving a sixth operation, and in response to the sixth operation, setting the permission of the first application to access the calendar application to the second permission.

[0024] In this way, when it is detected that the first application is set to the first permission and there is a privacy risk, the user can be prompted to change it to other permissions such as the second permission to protect user privacy.

[0025] In combination with the method described in the first aspect, the first operation includes an operation on a calendar reminder control in the first application, or an operation on a calendar permission management option in a settings application.

[0026] In this way, the user can output a window displaying management of the permission of the first application to access the calendar through different operations.

[0027] In combination with the method described in the first aspect, the first application is a third-party application.

[0028] In combination with the method described in the first aspect, the method is applied to an electronic device including an application operation permission management service (AppOpsService), and the method also includes: receiving a third operation on the second option; in response to the third operation, storing the permission of the first application to access the calendar application as the second permission in the AppOpsService.

[0029] In combination with the method described in the first aspect, after storing the permission of the first application to access the calendar application as the first permission in AppOpsService, the method also includes: receiving a second operation on the first option; in response to the second operation, changing the permission of the first application to access the calendar application stored in AppOpsService from the second permission to the first permission.

[0030] In this way, the permissions of the first application storing the latest settings can be refreshed in AppOpsService according to user operations.

[0031] In combination with the method described in the first aspect, the method is applied to an electronic device including a calendar provider, and the method includes: after receiving a third operation on the second option, storing the first schedule of the first application in the Calendar provider, and marking the first schedule as belonging to the first application.

[0032] In combination with the method described in the first aspect, the method is applied to an electronic device including an AppOpsService and a Calendar provider. After receiving the second operation on the first option, the method includes: the first application requests the Calendar provider to read the schedule; the Calendar provider queries from the AppOpsService that the permission for the first application to access the calendar application is the first permission; the Calendar provider returns all schedules in the calendar application to the first application.

[0033] In combination with the method described in the first aspect, the method is applied to an electronic device including an AppOpsService and a Calendar provider. After receiving the third operation of the second option, the method includes: the first application requests the Calendar provider to read the schedule; the Calendar provider queries from the AppOpsService that the permission for the first application to access the calendar application is the second permission; the Calendar provider only returns the first schedule belonging to the first application to the first application.

[0034] In this way, you can grant the application access to the corresponding schedule based on the application to which the schedule stored in the Calendar provider belongs and the permissions of the application stored in the AppOpsService.

[0035] In a second aspect, the present application provides an electronic device, which includes one or more memories and one or more processors; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the electronic device to execute the method described in any one of the first aspects.

[0036] In a third aspect, the present application provides a chip, which is applied to an electronic device. The chip includes one or more processors, which are used to call computer instructions to enable the electronic device to execute any method described in the first aspect.

[0037] In a fourth aspect, the present application provides a computer-readable storage medium, which includes instructions. When the instructions are executed on an electronic device, the electronic device executes the method described in any one of the first aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] FIG1 is a schematic diagram of a “multiple permission levels” management interface for accessing a calendar application according to an embodiment of the present application;

[0039] 2A-2B are schematic diagrams of a first operation interface for managing an application's permission to access a calendar application in settings, provided by an embodiment of the present application;

[0040] 2C-2D are schematic diagrams of a second operation interface for managing an application's permission to access a calendar application in settings, provided in an embodiment of the present application;

[0041] FIG2E is a schematic diagram of a third operation interface for managing the permission of an application to access a calendar application in settings provided by an embodiment of the present application;

[0042] FIG2F is a schematic diagram of a fourth operation interface for managing an application's permission to access a calendar application in settings, provided by an embodiment of the present application;

[0043] FIG3A is a schematic diagram of an operation interface for managing the permission of application A to access a calendar application in an embodiment of the present application;

[0044] FIG3B is a schematic diagram of an operation interface for managing the permission of application B to access the calendar application in an embodiment of the present application;

[0045] FIG3C is a schematic diagram of an operation interface for managing the permission of application C to access the calendar application, provided in an embodiment of the present application;

[0046] FIG3D exemplarily shows a schematic diagram of an operation interface for creating a schedule in a calendar application;

[0047] FIG3E exemplarily shows a scenario in which application A recommends corresponding services based on a schedule read from a calendar application;

[0048] FIG3F exemplarily shows a schematic diagram of an operation interface for creating a schedule in application C;

[0049] 3G-3H exemplarily illustrate schedule information provided in the calendar application and application C;

[0050] FIG3I exemplarily shows a schematic diagram of an operation interface for changing the permission of application C to access the calendar application;

[0051] FIG4 is a flowchart of a rights management method according to an embodiment of the present application;

[0052] FIG5 is a specific implementation of the rights management method provided in an embodiment of the present application;

[0053] FIG6 is a schematic diagram of the hardware architecture of an electronic device provided in an embodiment of the present application;

[0054] FIG7 is a schematic diagram of the software architecture of the electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] The following is a clear and detailed description of the technical solutions in the embodiments of the present application, with reference to the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " represents the meaning of "or." For example, A / B can represent A or B. "and / or" in the text is merely a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone.

[0056] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to imply or suggest relative importance or implicitly indicate the number of the technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more.

[0057] References to "embodiments" in this application mean that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described in this application may be combined with other embodiments.

[0058] The term "user interface (UI)" in the following embodiments of this application refers to a medium interface for interaction and information exchange between an application or operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. The user interface is a source code written in a specific computer language such as Java and extensible markup language (XML). The interface source code is parsed and rendered on an electronic device and finally presented as content that the user can recognize. The commonly used form of user interface is graphical user interface (GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It can be a visual interface element such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. displayed on the display screen of an electronic device.

[0059] At present, some applications (including third-party applications) in electronic devices require authorization from the calendar application to complete the corresponding tasks. For example, when a user wants to enable services such as rush purchase reminders and sign-in reminders in a shopping application, the shopping application needs to obtain authorization from the calendar application, so that the purpose of reminding users to rush purchases and sign in can be achieved through the calendar application. For another example, when a user wants to make an appointment for a movie / series / program in a video application, the video application also needs to obtain authorization from the calendar application so that the calendar application can remind the user to watch the movie / series / program when it starts. For another example, when a user wants to implement schedule management kinetic energy in a schedule management application, the schedule management application needs to obtain authorization from the calendar application to obtain all schedules in the calendar application to remind the user to process them. There are many other applications that require authorization from the calendar application, which are not listed here one by one.

[0060] However, the default permissions granted to calendar apps (referred to as native calendar access permissions) currently only include allowing access and denying access. Allowing access is equivalent to authorization by the calendar app. After obtaining authorization from the calendar app, some apps can access all schedules in the calendar app. All schedules include new schedules created by the user in the calendar app and schedules read by the calendar app from other apps. Accessing all schedules in the calendar app can include reading all schedules, creating new schedules, and modifying / deleting all schedules. If these apps are third-party apps, they may illegally query or tamper with schedules, thereby threatening user privacy.

[0061] In order to solve the above problems, the present application provides a permission management method, a graphical interface and related devices. In this method, the electronic device stores: schedules created by the calendar application itself, and schedules created by other applications in the calendar application, and marks the application to which each schedule belongs. Afterwards, when an application requests permission to access the calendar application, the electronic device can use the permission level selected by the user from a variety of permission levels (for example, the permission level for accessing only the calendar created by this application) to grant the application the corresponding permission, thereby preventing the application from accessing schedules created by other applications in the calendar system without permission.

[0062] The relevant concepts involved in this application are as follows:

[0063] The calendar app is a system app. A system app is one provided or developed by the manufacturer of an electronic device. The manufacturer of an electronic device can include the manufacturer, supplier, provider, or operator of the electronic device.

[0064] Third-party applications refer to applications provided or developed by manufacturers of non-electronic equipment.

[0065] Accessing the Calendar app involves reading or writing to the calendar. Specifically, "reading" refers to reading schedules in the Calendar app, while "writing" includes creating new schedules, or modifying / deleting schedules in the Calendar app.

[0066] The various permission levels include, but are not limited to, denying access to all calendars, allowing access only to calendars created by this app, and denying access to calendars created by this app. The "deny" permission is a native calendar access permission for electronic devices, while the "allow all calendars" and "allow access only to calendars created by this app" permissions are further refined versions of the "allow access" permission in native calendar access permissions.

[0067] Accessing only calendars created by this app means that the app can only access schedules created by this app in the Calendar app, and cannot access schedules created by the Calendar app or created by other apps in the Calendar app. Specifically, when accessing the calendar refers to reading the calendar, then accessing only calendars created by this app means only allowing the app to read schedules created by this app in the Calendar app; when accessing the calendar refers to creating a new calendar, then accessing only calendars created by this app means only allowing the app to write schedules created by this app in the Calendar app; when accessing the calendar refers to modifying / deleting the calendar, then accessing only calendars created by this app means only allowing the app to delete / modify schedules created by this app in the Calendar app.

[0068] Allowing access to all calendars means that the app can access all schedules in the Calendar app, including those created by the Calendar app and those created by this app or other apps in the Calendar app. Specifically, when accessing the Calendar refers to reading the calendar, allowing access to all calendars means allowing the app to read all schedules in the Calendar app; when accessing the Calendar refers to creating a new calendar, allowing access to all calendars means allowing the app to write schedules created by this app or other apps in the Calendar app; when accessing the Calendar refers to modifying / deleting the calendar, allowing access to all calendars means allowing the app to delete / modify all schedules in the Calendar app.

[0069] Prohibit means prohibiting the app from accessing schedules in the Calendar app. Specifically, if accessing the Calendar refers to reading the calendar, prohibiting means prohibiting the app from reading schedules in the Calendar app; if accessing the Calendar refers to creating a new calendar, prohibiting means prohibiting the app from writing schedules in the Calendar app; and if accessing the Calendar refers to modifying / deleting the calendar, prohibiting means prohibiting the app from deleting / modifying schedules in the Calendar app.

[0070] It can be seen that after implementing the method provided by this application, the following beneficial effects can be achieved:

[0071] (1) Personalize the access permissions of the calendar application. Specifically, based on user operations, the calendar application can grant different levels of permissions to different applications.

[0072] (2) It protects both user privacy and the normal use of various applications. Specifically, for applications that do not have access to all calendars, such applications cannot obtain schedules created by other applications in the calendar application, and thus cannot read schedules of other applications in the calendar application, and thus cannot analyze the user's privacy and leak the user's privacy. In addition, such applications cannot modify / delete schedules of other applications in the calendar application, and thus cannot illegally tamper with the user's schedule, etc. However, for applications that do not have access to all calendars but have access to calendars created by their own applications, they can create schedules in the calendar application and obtain schedules created by themselves in the calendar application, which is sufficient to provide users with corresponding functions.

[0073] Next, the permission management method and graphical interface provided by this application are introduced in conjunction with the UI implementation example.

[0074] Referring to FIG. 1 , FIG. 1 exemplarily shows a schematic diagram of a management interface for accessing “multiple permission levels” of a calendar application.

[0075] Figure 1, a-1, illustrates an exemplary management interface for the "multiple permission levels" associated with the calendar read permission. This interface includes window 111, which includes prompt information 111A requesting the user to allow "Application A" to access the calendar, prompt information 111B indicating that the calendar access is specifically for reading the calendar, and options corresponding to three levels of calendar access permissions: option 111C for accessing only calendars created by the application, option 111D for allowing access to all calendars, and option 111E for disabling access.

[0076] The user can select any one of the three options in a-1 in FIG. 1 to trigger the electronic device to take the calendar access permission corresponding to the option for application A.

[0077] a-1 in Figure 1 merely illustrates an example of a management interface for "multiple permission levels" corresponding to the permission to read the calendar. In another achievable manner, the permission levels provided by the management interface can also be as shown in a-2 in Figure 1. For example, the management interface only provides two permission levels, namely option 111F corresponding to allowing access to the calendar and option 111E corresponding to prohibiting. This is because, for applications that only read the calendar, such applications will not create schedules in the calendar application. Therefore, when such applications read the calendar application, there is no distinction between running and reading the schedules created by this application. Therefore, there is no need to provide an option corresponding to the permission level of only accessing the schedules created by this application. b in Figure 1 illustrates an example of a management interface for "multiple permission levels" corresponding to the permission to write the calendar. The management interface includes a window 112, which includes a prompt message 112A for requesting the user whether to allow "Application B" to access the calendar, and a prompt message 112B stating that the access to the calendar is specifically to write a calendar (including creating / modifying / deleting), and options corresponding to three levels of calendar access permissions, namely, option 112C corresponding to only accessing calendars created by this application, option 112D corresponding to allowing access to all calendars, and option 112E corresponding to prohibiting.

[0078] The user can select any one of the three options in b in FIG. 1 to trigger the electronic device to take the calendar access permission corresponding to the option for application B.

[0079] Figure 1, c, illustrates an exemplary management interface for "multiple permission levels" corresponding to the read and write calendar permissions. This management interface includes window 113, which includes prompt information 113A requesting the user to allow "Application C" to access the calendar, prompt information 113B specifying that the calendar access is specifically for reading and writing, and options corresponding to three levels of calendar access permissions: option 113C for accessing only calendars created by this application, option 113D for allowing access to all calendars, and option 113E for disabling access.

[0080] The user can select any one of the three options in c in FIG. 1 to trigger the electronic device to take the calendar access permission corresponding to the option to application C.

[0081] In an optional implementation, some applications (e.g., application A) only need to read the calendar when accessing the calendar application, some applications (e.g., application B) only need to write the calendar when accessing the calendar application, and some applications (e.g., application C) need to perform both read and write operations on the calendar. Therefore, when different applications request permission to access the calendar application, the operations they specify for accessing the calendar application may differ.

[0082] In an optional embodiment, window 111 / window 112 / window 113 shown in Figure 1 can be triggered and displayed when the calendar access rights specifically for managing various applications are provided in the settings application (see the description of Figures 2A-2F below for details), or can be triggered and displayed when the user turns on the calendar reminder function in application A / application B / application C (see the description of Figures 3A-3E below for details).

[0083] In an optional embodiment, in addition to providing users with a management service interaction interface with "multiple authority levels" in the form of a window as exemplified in Figure 1, a management service interaction interface with "multiple authority levels" can also be provided to users in other forms, and this embodiment of the present application does not limit this.

[0084] In the embodiment of the present application, the four interfaces shown in FIG. 1 may also be referred to as the first interface.

[0085] 2A-2F , which exemplarily illustrate a set of operation interface diagrams for managing the permission of an application to access a calendar application in settings.

[0086] 2A-2B illustrate a first method for managing an application's permission to access a calendar application in settings.

[0087] In FIG. 2A , “a” is an interface provided by a setting application, which may include multiple setting options, such as a privacy option.

[0088] The user can trigger the electronic device to display the privacy details page by clicking the privacy option in the setting options. In response to the operation on the privacy option in a of Figure 2A, the electronic device is triggered to open the privacy details page, as shown in b of Figure 2A.

[0089] b in Figure 2A is the privacy details page opened by setting the privacy option in the application. The privacy details page includes a card 211 for recommended optimization, a card 212 for viewing privacy access records, a card 213 for managing application permissions (or options, controls), and other cards, etc.

[0090] The user can trigger the electronic device to open the permission management page by clicking the card 213 for managing application permissions. In response to the operation on the card 213 for managing application permissions in Figure 2A b, the electronic device is triggered to open the permission management details page, as shown in Figure 2A c.

[0091] Item c in FIG2A is a permission management details page, which includes a permission column 213A and an application column 213B. By selecting either permission column 213A or application column 213B, the user can trigger the electronic device to display a series of options corresponding to the selected column on the permission management details page. For example, when application column 213B is selected in item c, the permission management details page displays a series of application options, including options corresponding to application A, application B, application C, application D, and so on.

[0092] The user can also trigger the electronic device to display the application permission details page corresponding to the selected application by selecting the option corresponding to any application. In response to the operation on the option corresponding to application A in Figure 2A c, the electronic device is triggered to open the permission details page of application A, as shown in Figure 2A d.

[0093] 2A , d, shows the permission details page for Application A. This page includes various permission settings, such as permission setting option 214 for Calendar, location information, camera, and microphone. Each permission setting also displays the current permission level. For example, permission setting option 214 for Calendar displays "Prohibited," indicating that Application A's current calendar permission is prohibited, meaning that Application A is prohibited from accessing the Calendar application.

[0094] The user can further manage the calendar permissions of Application A by clicking on the permission setting option 214 corresponding to the calendar. In response to the operation on the permission setting option 214 corresponding to the calendar in Figure 2A d, the electronic device is triggered to pop up a window for setting the permission level for Application A to access the calendar application, as shown in Figure 2B e. In this embodiment of the present application, the interface shown in Figure 2A d can also be referred to as the first interface, and the operation of the permission setting option 214 corresponding to the calendar shown in Figure 2A d can also be referred to as the first operation.

[0095] Figure 2B shows the permission details page for application A, which now displays window 215. This window 215 contains prompt information indicating the operations required for application A to access the calendar application. For example, the prompt allows "application A" to create / modify / delete calendars, and also includes options corresponding to multiple levels of calendar access permissions, including "Access only calendars created by this application," "Allow access to all calendars," and "Prohibit." The "Prohibit" option is selected, indicating that application A's current permission to access the calendar is "Prohibit." In an embodiment of the present application, window 215 can also be referred to as the first window, application A contained in window 215 can also be referred to as the name of the first application, the prompt information contained in window 215 for stating the operations involved in application A accessing the calendar application can also be referred to as access type information, and "Allow access to all calendars" contained in window 215 can also be referred to as the first permission, the option of "Allow access to all calendars" can also be referred to as the first option, "Only access calendars created by this application" can also be referred to as the second permission, the option of "Only access calendars created by this application" can also be referred to as the second option, "Prohibit" can also be referred to as the third permission, and the option of "Prohibit" can also be referred to as the third option. The operation acting on the first option can also be referred to as the second operation, the operation acting on the second option can also be referred to as the third operation, and the operation acting on the third option can also be referred to as the fifth operation.

[0096] The user can change App A's calendar access permission level from "Prohibited" to "Only Access Calendars Created by This App" by clicking the "Only Access Calendars Created by This App" option. In response to the action on "Only Access Calendars Created by This App" in Figure 2B (e), the electronic device is triggered to change App A's calendar access permission level to "Only Access Calendars Created by This App," as shown in Figure 2B (f).

[0097] f in Figure 2B is still the permission details page of application A. At this time, the permission setting option 214 corresponding to the calendar shows "Only access calendars created by this application", which means that the calendar permission currently owned by application A is only to access the schedules created by application A in the calendar application, and cannot access the schedules created by other applications or the calendar application itself in the calendar application.

[0098] 2C-2D illustrate a second method for managing an application's permission to access a calendar application in settings.

[0099] 2C is the permission management details page (same as shown in c in FIG2A above), which includes a permission column 213A and an application column 213B. For other introductions to the permission management details page, please refer to the description of c in FIG2A above, which will not be repeated here.

[0100] The user can select the permission column 213A to trigger the electronic device to display a series of permission options corresponding to the selected permission column in the permission management details page, as shown in b in Figure 2C.

[0101] b in Figure 2C is still the permission management details page, in which the permission column 213A is selected, and a series of permission options corresponding to the permission column 213A are displayed, such as the permission setting option 216 corresponding to the calendar, as well as the permission setting options corresponding to the location information, the permission setting options corresponding to the camera, the permission setting options corresponding to the microphone, the permission setting options corresponding to the phone, and the permission setting options corresponding to the information, etc.

[0102] The user can further manage calendar permissions by clicking on the permission setting option 216 corresponding to the calendar. In response to the operation on the permission setting option 216 corresponding to the calendar in Figure 2C b, the electronic device is triggered to display the calendar permission details page, as shown in Figure 2C c.

[0103] In FIG2C , c is the calendar permission details page. At this time, the calendar permission details page displays the “Read Calendar” option and the “Create / Modify / Delete Calendar” option, which respectively correspond to the calendar reading operation and the calendar writing operation.

[0104] The user can set the corresponding calendar reading permission or calendar writing permission by clicking any of the "Read Calendar" option and "Create / Modify / Delete Calendar" options. For example, in response to clicking the "Read Calendar" option, the electronic device will be triggered to display the calendar reading permission setting details page, as shown in Figure 2C (d).

[0105] 2C shows the permission setting details page for reading calendars. This page includes options for Application A, Application B, Application C, and Application D, among others. In addition, each application's corresponding option also displays the permission level for reading calendars. For example, option 217 for Application C displays the permission level as "Allow access to all calendars."

[0106] The user can reset the permission level of any application when reading the calendar by selecting the option corresponding to the application. Specifically, in response to the operation on option 217 corresponding to application C in Figure 2C d, the electronic device is triggered to pop up a window for setting the permission level of application C to read the calendar, as shown in Figure 2D e. In the embodiment of the present application, the interface shown in Figure 2C d can also be referred to as the first interface, and the operation on option 217 corresponding to application C shown in Figure 2C d can also be referred to as the first operation.

[0107] Figure 2D shows the permission setting details page for reading calendars. This page displays window 218. This window 218 contains a prompt allowing "Application C" to read calendars, as well as options corresponding to multiple permission levels for reading calendars, including, for example, "Access calendars created by this application only," "Allow access to all calendars," and "Prohibit." The "Allow access to all calendars" option is selected, indicating that Application C's permission to read calendars is "Allow access to all calendars." In this embodiment of the present application, window 218 may also be referred to as the first window, Application C contained in window 218 may also be referred to as the name of the first application, the prompt indicating Application C's permission to read calendars in window 218 may also be referred to as access type information, "Allow access to all calendars" contained in window 218 may also be referred to as the first permission, the "Allow access to all calendars" option may also be referred to as the first option, "Access calendars created by this application only" may also be referred to as the second permission, the "Access calendars created by this application only" option may also be referred to as the second option, "Prohibit" may also be referred to as the third permission, and the "Prohibit" option may also be referred to as the third option. The operation acting on the first option may also be referred to as a second operation, the operation acting on the second option may also be referred to as a third operation, and the operation acting on the third option may also be referred to as a fifth operation.

[0108] The user can change the calendar access permission level for App C from "Allow access to all calendars" to "Only access calendars created by this app" by clicking the "Only access calendars created by this app" option. In response to the action on "Only access calendars created by this app" in Figure 2D (e), the electronic device is triggered to change App C's calendar access permission level to "Only access calendars created by this app," as shown in Figure 2D (f).

[0109] f in Figure 2D is still the permission setting details page for reading the calendar. At this time, option 217 corresponding to application C displays "Only access calendars created by this application", which means that the calendar permission currently owned by application C is only to access the schedules created by application C in the calendar application, and cannot access the schedules created by other applications or the calendar application itself in the calendar application.

[0110] FIG. 2E illustrates a third method for managing an application's permission to access a calendar application in settings.

[0111] a in Figure 2E is the privacy details page opened by setting the privacy option in the application. The privacy details page may include, for example, a card 211 for suggesting optimizations, a card 212 for viewing privacy access records, a card 213 for managing application permissions, and other cards, etc.

[0112] The user can trigger the electronic device to display the privacy assistant details page by clicking the recommended optimization card 211, as shown in b in Figure 2E.

[0113] Figure 2E, part b, shows the Privacy Assistant details page, which includes the results of over-authorized application risk detection and, when an application presents a risk (for example, when an application frequently reads all calendars, it is considered that the application excessively obtains the user's private information), a prompt message 219A suggesting optimization will be displayed. This prompt message 219A may, for example, display a message such as "Allowing "Application B" to read all calendars poses a risk. Optimization is recommended to: only access calendars created by this application." It also displays a control 218A for immediate optimization and a control 218B for canceling the optimization.

[0114] The user can click control 218A to cause the electronic device to modify the permission for application B to access the calendar application to "only access calendars created by this application." Specifically, in response to the operation on control 218A in FIG. 2E b (also referred to as the sixth operation), the electronic device begins optimizing the permission level of application A, as shown in prompt message 219B in FIG. 2E c, and also outputs a prompt message indicating that the optimization was successful, as shown in FIG. 2E d.

[0115] 2E d shows a prompt message 219C for notifying the user that the optimization is successful. The prompt message 219C may display, for example, a prompt message “Optimization successful. Application B has been optimized to only access the calendar created by this application.”

[0116] FIG. 2F illustrates a fourth method for managing an application's permission to access a calendar application in settings.

[0117] A in Figure 2F is a privacy details page opened by setting the privacy option in the application. The privacy details page includes a card 211 for recommended optimization, a card 212 for viewing privacy access records, a card 213 for managing application permissions, and other cards, etc.

[0118] The user can view all privacy access records by clicking the control of all privacy access records in the card 212 for viewing privacy access records, as shown in b in FIG. 2F .

[0119] Figure 2F shows the details page for all privacy access records, which can be used to display records of each application accessing private information, such as records of "Application A reads all calendars", "Application A reads all calendars", etc.

[0120] Users can modify the privacy access permissions of any application by clicking on its privacy access record. For example, in response to an operation on the record "Application A reads calendar", the user will be redirected to the privacy access record details page of Application A, as shown in Figure 2F (c).

[0121] Figure c in Figure 2F is the privacy access record details page of application A, which records specific privacy record information such as the time and number of times application A accessed various privacy messages, for example, application A read the entire calendar 11 times before 15:10 today, etc.

[0122] The user can modify the privacy access rights of that type by clicking on any specific privacy record information. For example, in response to detecting that a click on the privacy record information corresponding to application A reading all calendars before 3:10 PM today is triggered, the electronic device is triggered to pop up a window for setting the permission level for application A to access the calendar application, as shown in b in Figure 2F. In this embodiment of the present application, the interface shown in c in Figure 2F can also be referred to as the first interface, and the operation acting on the privacy record information corresponding to application A reading all calendars before 3:10 PM today 11 times in c in Figure 2F can also be referred to as the first operation.

[0123] A window is displayed in d in Figure 2F. This window contains prompt information for indicating the operations involved in allowing Application A to access the calendar application. For example, the prompt information allows "Application A" to read the calendar, and also contains options corresponding to multiple permission levels for accessing the calendar application, such as "Access only calendars created by this application," "Allow access to all calendars," and "Prohibit." Among them, the "Prohibit" option is selected, indicating that the current permission for Application A to access the calendar application is "Prohibited."

[0124] The user can change the permission level of application A to access the calendar application from "Allow access to all calendars" to "Access only calendars created by this application" by clicking the "Only access calendars created by this application" option. In an embodiment of the present application, the window displayed in d in Figure 2F can also be called the first window, the application A contained in the window can also be called the name of the first application, the prompt information contained in the window allowing "application A" to read the calendar can also be called access type information, the "Allow access to all calendars" contained in the window can also be called the first permission, the "Allow access to all calendars" option can also be called the first option, "Access only calendars created by this application" can also be called the second permission, the "Access only calendars created by this application" option can also be called the second option, "Prohibit" can also be called the third permission, and the "Prohibit" option can also be called the third option. The operation acting on the first option can also be called the second operation, the operation acting on the second option can also be called the third operation, and the operation acting on the third option can also be called the fifth operation.

[0125] The above Figures 2A-2F only illustrate four exemplary operating methods for managing the application's access permissions to the calendar application in the settings, and should not constitute a limitation to this application. In addition, there are other ways to manage the application's access permissions to the calendar application.

[0126] 3A-3C , which exemplarily illustrate a set of operation interface diagrams for managing the permission of an application to access a calendar application.

[0127] FIG3A illustrates an operation method for managing the permission of application A to access the calendar application.

[0128] In FIG3A , a is a desktop of the electronic device, which may include icons of multiple application programs, for example, an icon of application A, an icon of application B, an icon of application C, an icon of application D, and an icon of settings.

[0129] The user can trigger the electronic device to activate any application by clicking on the icon of the application. For example, in response to the operation on the icon of application A in Figure 3A a, the electronic device opens application A and displays the interface provided by application A, as shown in Figure 3A b.

[0130] b in Figure 3A is the interface of application A. Application A can be a shopping application. The interface of application A can display a control 311 for signing in, and also display some goods available for users to purchase, etc. The embodiment of the present application does not impose any restrictions on the interface of application A.

[0131] The user can open the check-in interface through control 311. Usually, after the user opens the check-in interface, the electronic device can pop up a message to remind the user to turn on the calendar reminder, so that application A can create a check-in reminder task in the calendar to remind the user to check in in application A.

[0132] 3A includes a window 312, which displays a prompt message for reminding the user to subscribe to the calendar reminder service, such as "Turn on calendar reminders and sign in every day to receive cash", and also displays a control 312A for immediate subscription and a control 312B for unsubscribing.

[0133] The user can use control 312A to subscribe to the calendar reminder service. Specifically, in response to the operation on control 312A, the electronic device is triggered to pop up a window for application A to request permission to access the calendar application, as shown in Figure 3A (d). In this embodiment of the present application, the interface shown in Figure 3A (c) can also be referred to as the first interface, and the operation on control 312A shown in Figure 3A (c) can also be referred to as the first operation.

[0134] d in Figure 3A includes window 313, which includes prompt information 313A for requesting the user whether to allow "Application A" to access the calendar, and prompt information 313B stating that access to the calendar is specifically reading the calendar and creating / modifying / deleting the calendar, and options corresponding to three levels of calendar access rights: option 313C corresponding to only accessing calendars created by this application, option 313D corresponding to allowing access to all calendars, and option 313E corresponding to prohibiting.

[0135] By selecting any of the three options in d of FIG3A , the user can trigger the electronic device to grant the corresponding calendar access rights to application A. For example, in response to the operation on option 313C, application A's calendar access rights include the right to create schedules in the calendar application. Therefore, the calendar application can display the schedule information corresponding to "App A Check-in" created by the user through application A. For details, please refer to the description of b in FIG3D below.

[0136] In an embodiment of the present application, the window 313 displayed in d in Figure 3A can also be called the first window, the application A contained in the window can also be called the name of the first application, the prompt information 313B for reading calendars and creating / modifying / deleting calendars contained in window 313 can also be called access type information, and the "Allow access to all calendars" contained in window 313 can also be called the first permission, the option of "Allow access to all calendars" can also be called the first option, "Only access calendars created by this application" can also be called the second permission, the option of "Only access calendars created by this application" can also be called the second option, "Prohibit" can also be called the third permission, and the option of "Prohibit" can also be called the third option. The operation acting on the first option can also be called the second operation, the operation acting on the second option can also be called the third operation, and the operation acting on the third option can also be called the fifth operation.

[0137] FIG3B illustrates an operation method for managing the permission of application B to access the calendar application.

[0138] In FIG3B , a is a desktop of the electronic device, which may include icons of multiple application programs, for example, an icon of application A, an icon of application B, an icon of application C, an icon of application D, and an icon of settings.

[0139] The user can trigger the electronic device to activate any application by clicking on the icon of the application. For example, in response to an operation on the icon of application B in Figure 3B (a), the electronic device is triggered to open application B and display the interface provided by application B, as shown in Figure 3B (b).

[0140] b in Figure 3B is the interface of application B. Application B can be a video application. The interface of application B can display an icon 314A for booking live video, and also display some videos for users to watch, etc. The embodiment of the present application does not impose any restrictions on the interface of application B.

[0141] The user can schedule a live video using icon 314A. Typically, after the user confirms the live video schedule, a pop-up window will appear on the electronic device requesting permission for application B to access the calendar application. Once permission is granted, application B can create a calendar appointment to remind the user to watch the live video. In this embodiment of the present application, the interface shown in b of FIG. 3B may also be referred to as the first interface, and the operation performed on icon 314A shown in b of FIG. 3B may also be referred to as the first operation.

[0142] c in Figure 3B includes window 315, which includes prompt information 315A for requesting the user whether to allow "Application B" to access the calendar, and prompt information 315B stating that access to the calendar is specifically reading the calendar and creating / modifying / deleting the calendar, and options corresponding to three levels of calendar access permissions, namely, option 315C corresponding to accessing only calendars created by this application, option 315D corresponding to allowing access to all calendars, and option 315E corresponding to prohibiting.

[0143] The user can trigger the electronic device to take the calendar access permission corresponding to the option to application B by selecting any of the above three options in c in Figure 3B. For example, in response to the operation on the corresponding option 315C of only accessing calendars created by this application, the electronic device will control application B to only access (read and add / modify / delete) the schedules created by application B in the calendar application, and not access (read and add / modify / delete) the schedules created by other applications or the calendar application itself in the calendar application. In an embodiment of the present application, the window 315 displayed in c in Figure 3B can also be referred to as the first window, the application B contained in the window can also be referred to as the name of the first application, the prompt information 315B for reading calendars and creating / modifying / deleting calendars contained in window 315 can also be referred to as access type information, the "allow access to all calendars" contained in window 315 can also be referred to as the first permission, the "allow access to all calendars" option can also be referred to as the first option, the "access only calendars created by this application" can also be referred to as the second permission, the "access only calendars created by this application" option can also be referred to as the second option, the "disable" can also be referred to as the third permission, and the "disable" option can also be referred to as the third option. The operation acting on the first option may also be referred to as a second operation, the operation acting on the second option may also be referred to as a third operation, and the operation acting on the third option may also be referred to as a fifth operation.

[0144] 3B (d) shows the interface of Application B. After the user has granted Application B access to the Calendar app, the interface changes the video scheduling icon 314A to a scheduled icon 314B. Furthermore, in response to the action on option 315C, Application B's calendar access permissions include the ability to create schedules within the Calendar app. Therefore, the calendar app displays the schedule information corresponding to "Schedule a Live Video with Application B," which the user created through Application B. For details, see the description of 3D (b) below.

[0145] FIG3C illustrates an operation method for managing the permission of application C to access the calendar application.

[0146] In FIG. 3C , a is a desktop of the electronic device, which may include icons of multiple application programs, such as an icon of application C, and the like.

[0147] The user can trigger the electronic device to launch any application by clicking on the icon of the application. For example, in response to an operation on the icon of application C in Figure 3C (a), the electronic device is triggered to open application C and display the interface provided by application C, as shown in Figure 3C (b).

[0148] b in Figure 3C is the interface of application C, which can be a schedule management application. The interface of application C can display a calendar and window 318. Window 318 displays information for prompting the user to import the calendar application. The prompt information is, for example, "Try importing the calendar application, and you can view calendar events in application C." It also displays an icon 318A for importing, an icon 318B for canceling, and a control 318C for creating a schedule in application C.

[0149] The user can use icon 318A to import a schedule from the calendar application into application C. For example, in response to an operation performed on icon 318A, the electronic device displays the user interface shown in FIG3C (c). In this embodiment of the present application, the interface shown in FIG3C (b) may also be referred to as the first interface, and the operation performed on icon 318A shown in FIG3C (b) may also be referred to as the first operation.

[0150] The "c" in Figure 3C is still the interface of application C, and a window 319 is displayed. Window 319 includes a prompt message 319A requesting the user whether to allow "application C" to access the calendar, and a prompt message 319B stating the access to the calendar, such as reading the calendar and creating / modifying / deleting the calendar, and options corresponding to three levels of calendar access permissions, namely, option 319C for accessing only the calendar created by this application, option 319D for allowing access to all calendars, and option 319E for prohibiting.

[0151] By selecting any of the three options in c in FIG3D , the user can trigger the electronic device to take the calendar access permission corresponding to the option for application C. For example, in response to an operation on option 319C corresponding to "Allow access to all calendars," application B can access (read) all schedules created by applications in the calendar application, and application C can also display the schedule information obtained from the calendar application in application C, as shown in d in FIG3C . In an embodiment of the present application, the window 319 displayed in c in FIG3C can also be referred to as the first window, the application C contained in the window can also be referred to as the name of the first application, the prompt information 319B for reading calendars and creating / modifying / deleting calendars contained in window 319 can also be referred to as access type information, the "Allow access to all calendars" contained in window 319 can also be referred to as the first permission, the "Allow access to all calendars" option can also be referred to as the first option, the "Access only calendars created by this application" can also be referred to as the second permission, the "Access only calendars created by this application" option can also be referred to as the second option, the "Prohibit" option can also be referred to as the third permission, and the "Prohibit" option can also be referred to as the third option. The operation acting on the first option may also be referred to as a second operation, the operation acting on the second option may also be referred to as a third operation, and the operation acting on the third option may also be referred to as a fifth operation.

[0152] In c of Figure 3C, only the example of application C applying for both the permission to read and write the calendar is used to illustrate the management interface for managing the permission of application C to access the calendar. Since application C belongs to the schedule management application, it may already have relatively complete functions such as creating and managing calendars, and can then write the calendars it created directly to the local end without synchronizing them to the calendar application. Therefore, application C can also only apply for permission to read the calendar without applying for permission to write the calendar. In this case, when application C detects the operation on icon 318A as shown in b of Figure 3C above, the management window for managing the permission of application C to access the calendar that pops up on the electronic device can be the window shown in a-2 of Figure 1. For details, please refer to the above introduction to a-2 of Figure 1. Correspondingly, the above operation on option 319C corresponding to allowing access to all calendars in c of Figure 3C corresponds to the operation on option a-2 of Figure 1 allowing access to calendars.

[0153] d in Figure 3C is still the interface of Application C (also known as the third interface). This interface displays window 411, which displays all schedules in Application C's calendar application, such as schedule information 411A corresponding to "App A Check-in" and schedule information 411B corresponding to "App B Live Video Booking." Schedule information 411A represents the schedule created by Application A in the calendar application after being granted calendar access rights, as described in Figure 3A above. Schedule information 411B represents the schedule created by Application B in the calendar application after being granted calendar access rights, as described in Figure 3B above.

[0154] FIG. 3D exemplarily illustrates an operation method for creating a schedule in a calendar application.

[0155] In FIG3D , a is a desktop of the electronic device, which may include icons of multiple application programs, such as a calendar icon and the like.

[0156] The user can trigger the electronic device to activate any application by clicking on the icon of the application. For example, in response to the operation on the calendar icon in Figure 3E (a), the electronic device is triggered to open the calendar application and display the interface provided by the calendar application, as shown in Figure 3D (b).

[0157] 3D b is the calendar interface, which may display a calendar 316, a window 317, a new schedule icon 317A in window 317, and schedule reminder information. This schedule reminder information may include, for example, schedule information 317B corresponding to the schedule "Appointment for Live Video of Application B" created by Application A in the calendar application after Application A is granted calendar access rights, as described in FIG3A above, and schedule information 317C created by Application B in the calendar application after Application B is granted calendar access rights, as described in FIG3B above. In this embodiment of the present application, the calendar application interface shown in FIG3D b may also be referred to as the fifth interface, and Application A's schedule information 317B and Application B's schedule information 317C may also be referred to as the first schedule.

[0158] The user can create a schedule through the new schedule icon 317A. For example, in response to selecting a day in the calendar 316, such as May 5, and acting on the new schedule icon 317A, the electronic device displays the user interface shown in Figure 3D c.

[0159] Figure 3D shows the new schedule details page, i.e., the page to be edited for a new schedule. The new schedule details page may include an OK icon 318A and a Cancel icon 318B, and page titles such as "New Schedule," "Title," "Location," and "Time." The OK icon 318A can be used to confirm the edited to-do event, while the Cancel icon 318B can be used to close the page to be edited. The Title item can be used to receive user input for the title of the to-do event, the Location item can be used to receive user input for the location of the to-do event, and the Time item can be used to receive user input for the start and end times of the to-do event.

[0160] After editing the schedule information, the user can complete the creation of the schedule by clicking the confirmation icon 318A. For example, in response to an operation on the confirmation icon 318A in Figure 3D c, the electronic device is triggered to display the schedule information shown in Figure 3D d. In this embodiment of the present application, the operations of creating a schedule shown in Figures 3D b and c can also be referred to as the fourth operation.

[0161] The schedule reminder information displayed in d of FIG3D includes schedule information 317B and schedule information 317C, and also schedule information 317D (also referred to as a second schedule) corresponding to the mother's birthday that is created directly in the calendar application.

[0162] Optionally, after the user creates a birthday reminder schedule as shown in Figure 3D in the calendar application, if some shopping applications, such as the aforementioned application A, have permission to read all calendars, then application A can obtain the birthday reminder schedule and recommend the user to purchase birthday gifts on the interface of application A. Please refer to the scenario shown in Figure 3E for details.

[0163] FIG. 3E exemplarily illustrates a scenario in which application A recommends corresponding services based on a schedule read from a calendar application.

[0164] As shown in Figure 3E (a), a user creates a schedule for their mother's birthday in the calendar app at 8:08 AM. As shown in Figure 3E (b), when the user later opens App A at, for example, 9:30 AM, App A displays a product push notification, such as "Birthday Gift List," recommending birthday gifts for the user. The App A interface shown in Figure 3E (b) can also be referred to as the second interface.

[0165] FIG. 3F exemplarily shows an operation method for creating a schedule in application C. FIG.

[0166] A in Figure 3F is the interface of application C, which displays a window 411. Window 411 displays schedule information 411A corresponding to "App A check-in" previously read from the calendar application, schedule information 411B corresponding to "Appointment for live video of application B", and schedule information 411C corresponding to the mother's birthday created directly by the user in the calendar application.

[0167] The user can create a schedule in application C by operating on control 318C in a of Figure 3F. For example, in response to the operation on control 318C, application C displays a window 413 for creating a schedule, as shown in b of Figure 3F.

[0168] 3F b is still the interface of application C. At this time, a window 413 is displayed in the interface. The window 413 includes an input box 413A for displaying a schedule title and a control 413B for completing schedule creation.

[0169] The user can enter the title of a pending schedule by operating the keyboard. The corresponding electronic device can then display the corresponding schedule title based on the user's keyboard operation, such as the title "Project Meeting" shown in Figure 3F (c). After entering the schedule title, the user can also click control 413B to complete the creation of the schedule. For example, in response to the operation on control 413B, the user successfully creates the "Project Meeting" schedule in application C, and application C also displays the schedule information. For details, please refer to the content shown in Figure 3F (d).

[0170] d in Figure 3F is still the interface of application C. At this time, a window 411 is displayed in the interface. Window 411 not only displays the schedule information 411A corresponding to the "App A Check-in" previously read from the calendar application, the schedule information 411B corresponding to the "Appointment for Live Video of Application B", and the schedule information 411C corresponding to the mother's birthday created directly by the user in the calendar application, but also displays the schedule information 411D corresponding to the project meeting created directly by the user in application C this time.

[0171] Optionally, the schedule information corresponding to the project meeting created by the user in Application C as described in FIG3F above can be stored in the data of Application C. If Application C only has permission to read the calendar but not permission to write to the calendar (create / modify / delete calendars in the calendar application), the schedule information corresponding to the project meeting created by the user in Application C will not be synchronously stored in the database of the calendar application and will not be displayed in the interface of the calendar application. See FIG3G for details.

[0172] When application C has the permission to write calendars (create / modify / delete calendars in the calendar application), the schedule information corresponding to the project meeting created by the user in application C can also be synchronized and stored in the database of the calendar application, and then displayed in the interface of the calendar application. It depends on whether application C itself requires that the schedule created on this end be synchronized in the calendar application. This application does not impose any restrictions on this.

[0173] As shown in Figure 3G, taking the example of application C not having the permission to write to the calendar, or application C having the permission to write to the calendar but requiring that the schedule of application C not be synchronized with the calendar application, the schedule information of the project meeting created by the user is only provided by application C, and the schedule information of the project meeting is not provided in the calendar application.

[0174] As shown in FIG3H , taking the example of application C having the permission to write to the calendar and requiring the schedule of application C to be synchronized with the calendar application, the schedule information of the project meeting created by the user is not only provided by application C, but the calendar application also synchronously provides the schedule information 317E of the project meeting.

[0175] After the user grants Application C the right to access all calendars, if you want to change Application C's permission to access the calendar application, you can modify it in the settings. For the operation method of modifying Application C's permission to access the calendar application in the settings, you can refer to the four methods shown in Figures 2A-2F above. Figure 3I below only uses one method to introduce.

[0176] FIG3I exemplarily shows a schematic diagram of an operation interface for changing the permission of application C to access the calendar application.

[0177] FIG3I a is a rights management details page, which includes a rights section 213A and an application section 213B. A user can select either the rights section 213A or the application section 213B to trigger the electronic device to display a series of options corresponding to the selected section on the rights management details page. For example, as shown in FIG3I a, when the application section 213B is selected, the rights management details page displays a series of application options, including options corresponding to application A, application B, application C, and application D, and so on.

[0178] The user can also trigger the electronic device to display the application permission details page corresponding to any application by selecting the option corresponding to the selected application. For example, in response to an operation on the option corresponding to application C in Figure 3I a, the electronic device is triggered to open the permission details page of application C, as shown in Figure 3I b.

[0179] FIG3I b shows the permission details page for application C. This page includes various permission settings, such as permission setting option 214 for calendar, location information, camera, and microphone. Each permission setting also displays the current permission level. For example, permission setting option 214 for calendar displays "Allow access to all records," indicating that application C currently has calendar permissions that allow it to access all schedules created by other applications within the calendar application.

[0180] The user can further manage the calendar permissions of application A by clicking the permission setting option 214 corresponding to the calendar. In response to the operation on the permission setting option 214 corresponding to the calendar in Figure 3I (b), the electronic device is triggered to pop up a window for setting the permission level for application C to access the calendar application, as shown in Figure 3I (c). In this embodiment of the present application, the interface shown in Figure 3I (b) can also be referred to as the first interface, and the operation on the permission setting option 214 corresponding to the calendar shown in Figure 3I (b) can also be referred to as the first operation.

[0181] Figure 3I, c, is still the permission details page for application C, which now displays window 412. Window 412 contains prompt information for stating the operations involved in application C's access to the calendar. This prompt information, for example, allows application C to read calendars and create / modify / delete calendars, as well as options corresponding to multiple levels of calendar access permissions, including, for example, "Access calendars created by this application only," "Allow access to all calendars," and "Prohibit." The "Allow access to all calendars" option is selected, indicating that application C's current permission to access the calendar application is "Allow access to all calendars."

[0182] By clicking the "Access calendars created by this application only" option, the user can change the permission level of application C's access to the calendar application from "Allow access to all calendars" to "Access calendars created by this application only." For example, in response to an operation on "Access calendars created by this application only" in FIG3I c, the electronic device is triggered to change the permission level of application C's access to the calendar application to "Access calendars created by this application only," and the schedule information previously obtained by application C in the calendar application is cleared, as shown in FIG3I d. In this embodiment of the present application, the window 412 displayed in FIG3I c may also be referred to as the first window, the application C contained in the window may also be referred to as the name of the first application, the prompt information for reading calendars and creating / modifying / deleting calendars contained in window 412 may also be referred to as access type information, the "Allow access to all calendars" contained in window 412 may also be referred to as the first permission, the "Allow access to all calendars" option may also be referred to as the first option, the "Access calendars created by this application only" may also be referred to as the second permission, the "Access calendars created by this application only" option may also be referred to as the second option, the "Prohibit" option may also be referred to as the third permission, and the "Prohibit" option may also be referred to as the third option. The operation acting on the first option may also be referred to as a second operation, the operation acting on the second option may also be referred to as a third operation, and the operation acting on the third option may also be referred to as a fifth operation.

[0183] Similarly, in c of Figure 3I , only the case where application C applies for both the permission to read and write the calendar is used as an example to illustrate the management interface for managing the permission of application C to access the calendar. When application C only applies for the permission to read the calendar and does not need to apply for the permission to write the calendar, when application C detects the operation of the permission setting option 214 corresponding to the calendar as shown in b of Figure 3I above, the management window for managing the permission of application C to access the calendar that pops up on the electronic device can be the window shown in a-2 of Figure 1 . For details, please refer to the above introduction to a-2 of Figure 1 . Correspondingly, the above operation on the corresponding option of only accessing the calendar created by this application in c of Figure 3I corresponds to the operation on the corresponding option of prohibiting in a-2 of Figure 1 .

[0184] d in Figure 3I is the interface of application C (also known as the fourth interface). This interface is different from the interface shown in Figure 3E in that, since application C cannot read the schedule in the calendar application, the schedule information in the calendar application is no longer displayed in this interface. Instead, it only displays the schedule information 411D corresponding to the project meeting created by application C itself.

[0185] It is understandable that the operation method for managing the permissions of various applications to access the calendar application in the settings described in the aforementioned UI embodiment is only an example, and the operation method for managing the permissions of this application to access the calendar application in the application is also only an example and should not constitute a limitation on this application. For example, in the settings, the operation steps for managing the application's access to the calendar application may be more complex or simpler than those described in the aforementioned Figures 2A-2F, and this application does not impose any restrictions on this. For example, in different applications, the operations for triggering the management of the application's permission to access the calendar application are different. For example, the triggering operation in the shopping application (application A) described above is to subscribe to a calendar reminder to sign in and receive a red envelope, the triggering operation in the video application (application B) is to schedule a program to remind the user to watch the program through the calendar, and the triggering operation in the schedule management application (application C) is to authorize the import of the calendar application, etc. This application will no longer list all applications one by one.

[0186] Next, the rights management method provided by this application is introduced with reference to FIG4 . The method includes the following steps:

[0187] S41, an application in the electronic device requests access to a calendar application.

[0188] Specifically, a system application or a third-party application in an electronic device may request access to a calendar application. Operations that trigger an application in an electronic device to request access to a calendar application include but are not limited to the following:

[0189] In one possible implementation, the triggering operation may be the operation of starting the application for the first time. Specifically, for some applications, when the application is run for the first time, the application will request corresponding permissions, including the permission to access the calendar application.

[0190] In another possible implementation, the triggering operation can also be an operation that enables a calendar reminder function provided in the application while the application is running. For example, the operation of subscribing to a calendar reminder in application A as described in FIG3A , the operation of reserving a program as described in FIG3B , and the operation of enabling the imported calendar application as described in FIG3C . When the application is of other types, the triggering operation can also take many other forms, which are not detailed here.

[0191] In S41, accessing the calendar application may refer to performing a read operation on a schedule in the calendar application or performing a write operation on the calendar application. Specifically, "reading" refers to reading a schedule stored in the calendar application, and "writing" refers to creating a new schedule, modifying / deleting a schedule in the calendar application.

[0192] S42, the electronic device detects whether the application has native calendar access permission.

[0193] Native calendar access permissions specifically refer to native calendar read permissions and native calendar write permissions. Native calendar access permissions are coarse-grained and include only two permission levels: "Allow calendar access" and "Forbidden access." When an app's native calendar access permission is "Allow calendar access," it means the app has native access permissions and can access all calendars. When an app's native calendar access permission is "Forbidden access," it means the app does not have native access permissions and cannot access any calendars.

[0194] Specifically, the electronic device can pre-set the native calendar access rights of the installed applications. When an application requests access to the calendar application, the electronic device can detect whether the application has the native calendar access rights. When the application has the native calendar access rights, it continues to execute the subsequent S43, which is used to further refine the judgment of the permission level of the calendar access rights of the application.

[0195] The method for setting the native calendar access permission of the electronic device includes the following methods:

[0196] In one possible implementation, the electronic device may default to all applications having native calendar access permissions, or not having native calendar access permissions;

[0197] In another possible implementation method, the electronic device may pop up a prompt message for requesting calendar access permissions, so that the user can manage the native access permissions of the application through the prompt message; or the settings item in the application in the electronic device may provide an option to manage the native access permissions of the application, so that the user can manage the native access permissions of the application through the native access permission option, etc. The embodiments of the present application will not go into details about this.

[0198] S43, the electronic device further detects whether the permission level of the application is to allow access to all calendars.

[0199] Specifically, this application refines the permission levels for applications to access calendar applications, that is, further dividing the permission to access calendars into: allowing access to all calendars, and allowing access only to calendars created by this application. Therefore, when the electronic device detects in S42 that the application has native calendar access rights, it needs to further determine the permission level of the application. If the permission level is allowing access to all calendars, it proceeds to the subsequent S44-1. If the permission level is allowing access only to calendars created by this application, it proceeds to S44-2 of the procedure.

[0200] The electronic device may pre-set a specific level of calendar access permissions for installed applications. The setting method includes the following:

[0201] In one possible implementation, the electronic device may default the permission level of all applications to allow access to all calendars, or default the permission level of all applications to only allow access to calendars created by this application, or it may also default the permission level of all system apps to allow access to all calendars, and the permission level of third-party apps to only allow access to calendars created by this application.

[0202] In another possible implementation, the user may set the permission level of each application to access the calendar application in the settings of the electronic device, for example, refer to the four setting methods described in Figures 2A to 2F above.

[0203] In another possible implementation, the electronic device may pop up a prompt message for requesting calendar access rights, so that the user can use the prompt message to manage the specific permission level of the application accessing the calendar application. For example, refer to the three setting methods described in Figures 3A-3C above.

[0204] S44-1, the electronic device allows the application to access all schedules in the calendar application.

[0205] Specifically, when the electronic device detects in S43 that the permission level of the application is to allow access to all calendars, the electronic device allows the application to access all schedules in the calendar application.

[0206] For example, when the application request in S41 to access the calendar application specifically includes reading the calendar, then in S44-1, the electronic device can return all the schedules in the calendar to the application. For details, please refer to the result display of application C accessing all calendars introduced in Figures 3C and 3F above; when the application request in S41 to access the calendar application specifically includes creating / modifying / deleting a calendar, then in S44-1, the electronic device allows the application to create a new schedule in the calendar, or modify / delete all the schedules in the calendar.

[0207] S44-2, the electronic device only allows the application to access the schedule created by the application.

[0208] Specifically, when the electronic device detects in S43 that the permission level of the application is not allowed to access all calendars, the electronic device only allows the application to access schedules created by the application.

[0209] For example, when the application request in S41 to access the calendar application specifically includes reading the calendar, then in S44-2, the electronic device only returns the schedule created by the application in the calendar to the application. For details, please refer to the result display of application C accessing the schedule created by this application in the calendar as introduced in Figure 3I d above; when the application request in S41 to access the calendar application specifically includes creating / modifying / deleting a calendar, then in S44-2, the electronic device only allows the application to create a new schedule in the calendar, or modify / delete the schedule created by this application in the calendar.

[0210] It can be seen that by setting refined permission levels to implement the permission management method provided by this application, each application can access the calendar application according to the corresponding permission level based on user needs, avoiding access to all schedules in the calendar application without user authorization, including schedules created by other applications in the calendar, thereby avoiding the leakage of user privacy.

[0211] Next, the specific implementation of the permission management method provided by this application is described in detail with reference to FIG5 . The specific implementation involves a calendar application, a third-party application, a calendar provider (Calendar provider), and an application operation permission management service (Application Operations Service, AppOpsService).

[0212] Among them, for the introduction of calendar applications and third-party applications, please refer to the description in S41 above, which will not be repeated here.

[0213] The Calendar provider is a module within the content provider of the application framework layer of an electronic device. It acts as a database that stores calendar data (i.e., schedules) and provides data access methods, such as read and write methods. Write methods include creating, deleting, and modifying schedules. Applications can access schedules in the database through the Calendar Provider API.

[0214] In particular, in this application, the schedules stored by the Calendar provider are all marked with labels of the applications to which they belong.

[0215] Among them, AppOpsService is a service used to manage the operating permissions of applications. It is a function included in the native system of electronic devices. It can be used to manage the native calendar access permissions of applications installed in electronic devices, that is, it includes two permissions: prohibiting access and allowing access, and the allowing access means allowing access to all calendars.

[0216] In particular, in this application, AppOpsService can also be used to finely manage the permission level of each application to access the calendar application, including: allowing access to all calendars, and only allowing access to calendars and schedules created by this application.

[0217] The specific implementation of the rights management method shown in FIG5 includes the following steps:

[0218] Phase 1 (S51-S53): Setting the permission level for third-party apps to access the calendar app. In addition, you can also set the permission level for system apps to access the calendar app. Because the permission level for third-party apps to access the calendar app is closely related to user privacy and security, this application focuses on the management and control of calendar access permissions for third-party apps.

[0219] S51: The system UI of the electronic device receives an operation for setting permission for a third-party application (application C) to access a calendar application.

[0220] Specifically, the operation received by the system UI of the electronic device for setting the permission for the third-party application to access the calendar application may be any of the following:

[0221] (1) Set the calendar access rights of the third-party application in the settings. Specifically, for example, in the scenario described in Figures 2A and 2B above, the operation of the option "only access calendars created by this application" in Figure 2B e; for another example, in the scenario described in Figures 2C and 2D above, the operation of the option "only access calendars created by this application" in Figure 2D e; for another example, in the scenario described in Figure 2E above, the operation of the immediate optimization control 218A in Figure 2E b; for another example, in the scenario described in Figure 2F above, the operation of the option "only access calendars created by this application" in Figure 2F d.

[0222] (2) Setting the calendar access permission of the present application in the third-party application. Specifically, for example, when the third-party application is application A, the operation of setting the calendar access permission of the present application in application A can refer to the operation of the option of only accessing the calendar created by the present application acting on d in the scenario shown in FIG. 3A above; for another example, when the third-party application is application B, the operation of setting the calendar access permission of the present application in application B can refer to the operation of the option of only accessing the calendar created by the present application acting on c in the scenario shown in FIG. 3B above; for another example, when the third-party application is application C, the operation of setting the calendar access permission of the present application in application C can refer to the operation of the option of only accessing the calendar created by the present application acting on c in the scenario shown in FIG. 3C above. For different third-party applications, the specific operations of setting the calendar access permission level of the application are different, and this application will not list them one by one for all applications.

[0223] S52: The system UI of the electronic device sends the permission level setting result of the third-party application to the AppOpsService (for example, application C is only allowed to access the calendar created by this application).

[0224] Specifically, after the electronic device receives the operation for setting the permission for the third-party application to access the calendar application, it sends the setting result of the permission level of the corresponding third-party application to AppOpsService according to the operation. AppOpsService can refresh and store the permission level of each application to access the calendar, so that when the third-party application accesses the calendar application subsequently, AppOpsService can execute according to the latest permission level of the third-party application.

[0225] For example, taking the permission level of application C as an example, if in S51 the operation received by the system UI is the change of the permission level of application C to access the calendar from "Allow access to all calendars" to "Only access calendars created by this application" as shown in c of the aforementioned Figure 3I , then in S52 the permission level of application C to access the calendar sent by the system UI to the AppOpsService will be "Only access calendars created by this application", and accordingly the AppOpsService will refresh the previously stored permission level of application C to access the calendar from "Allow access to all calendars" to "Only access calendars created by this application".

[0226] S53: The AppOpsService of the electronic device stores information indicating the permission level of the third-party application (application C).

[0227] Specifically, after receiving the permission level setting result sent by the third-party application, the AppOpsService of the electronic device will store the latest information indicating the permission level of the third-party application in the AppOpsService.

[0228] The information indicating the permission level of the third-party application includes: information indicating the permission level of the third-party application to read calendars, and information indicating the permission level of the third-party application to create / modify / delete calendars. Specifically, the information indicating the permission level of the third-party application to read calendars, or to create / modify / delete calendars may be information indicating whether a refined switch is on, for example, 1 indicates on, and 0 indicates off. If the refined switch is on, it means that the permission level of the third-party application to read calendars is to allow access to all calendars. If the refined switch is off, it means that the permission level of the third-party application to read calendars is to allow access only to calendars created by the application.

[0229] Stage 2 (S54-S58): Create a schedule in the calendar application and store it with a tag. Generally, calendar applications, third-party applications, and other system applications can create schedules in the calendar application if they have the corresponding permissions. This example uses a third-party application to create a schedule in the calendar application for illustrative purposes only and should not constitute a limitation to this application.

[0230] S54 , the third-party application of the electronic device receives an operation of writing the schedule of the third-party application (eg, including application A, application B, and application C) into the calendar application.

[0231] Specifically, the operations received by the third-party application of the electronic device to write the schedule of the third-party application to the calendar application include: for example, the operation for subscribing to calendar reminders in application A introduced in c of the aforementioned Figure 3A can trigger application A to request to write the schedule information of the check-in reminder to the database of the calendar application, namely, the Calendar provider; for another example, the operation for making an appointment for live video in application B introduced in b of the aforementioned Figure 3B can trigger application B to request to write the schedule information of the reminder to watch the live video to the database of the calendar application, namely, the Calendar provider; for another example, the operation for creating a schedule in application C introduced in c of the aforementioned Figure 3F can trigger application C to request to write the schedule information of the reminder to watch the live video to the database of the calendar application, namely, the Calendar provider.

[0232] S55 , the third-party application of the electronic device requests to write the schedule of the third-party application (eg, including application A, application B, and application C) to the Calendar provider.

[0233] Specifically, after receiving the operation of writing the third-party application schedule into the calendar application, the third-party application of the electronic device requests the Calendar provider to write the third-party application schedule into the Calendar provider according to the operation.

[0234] S56: The Calendar provider of the electronic device requests AppOpsService to verify the permission level of the third-party application.

[0235] Specifically, after the Calendar provider of the electronic device receives the request from the third-party application to write the third-party application's schedule, it continues to request AppOpsService to verify the application's permission level to determine whether to allow the third-party application's schedule to be written into the Calendar provider.

[0236] S57, the AppOpsService of the electronic device returns the permission level of the third-party application to the Calendar provider, for example, allowing writing to the calendar.

[0237] Specifically, after the AppOpsService of the electronic device receives the request sent by the Calendar provider, it verifies the permissions of the third-party application and returns the verification result to the Calendar provider.

[0238] For example, if the permission level of application A stored in AppOpsService includes permission to create / delete / modify calendars, then it is confirmed that application A's schedule (sign in to receive red envelopes) is allowed to be written to the Calendar provider; for another example, if the permission level of application B stored in AppOpsService includes permission to create / delete / modify calendars, then it is confirmed that application B's schedule (live video reminder) is allowed to be written to the Calendar provider; for another example, if the permissions of the calendar application stored in AppOpsService include permission to create / delete / modify calendars, then it is confirmed that the calendar application's schedule (mom's birthday) is allowed to be written to the Calendar provider.

[0239] S58: The Calendar provider of the electronic device stores the schedules of the three-party applications (eg, including application A, application B, and application C), and tags the schedules with the labels of the applications to which they belong.

[0240] Specifically, after receiving the information returned by AppOpsService indicating that the calendar application is allowed to write the schedule, the Calendar provider of the electronic device stores the schedule corresponding to the operation of writing the schedule in S54 in the Calendar provider, and marks the schedule with the label of the application, that is, the application of the schedule is a calendar application.

[0241] It is understandable that Phase 2 only uses the example of creating a schedule using a calendar application. In addition, electronic devices can also create calendars in other ways, which will not be detailed here. Only a brief description is given:

[0242] For example, a schedule can be created in a calendar app through application A, application B, application C, or another application. Specifically, if application A creates a schedule in a calendar app, i.e., subscribing to the calendar app reminder service as described in Figure 3A above, application A will create a schedule in the calendar app to remind the user to check in. Specifically, if application B creates a schedule in a calendar app, i.e., booking a certain interface as described in Figure 3B above, application B will create a task in the calendar app to remind the user to watch the program. This article does not list all the ways that each application can create a schedule in a calendar app.

[0243] Refer to Table 1, which exemplarily shows the schedule-related information stored by the Calendar provider provided by this application.

[0244] Table 1

[0245] Table 1 merely illustrates the contents of the schedule stored in the Calendar provider. Optionally, the schedule stored in the Calendar provider may also include, but is not limited to, information such as the schedule location, time, and the package name (pkgName) corresponding to the schedule. This embodiment of the present application does not impose any restrictions on this.

[0246] In addition, the present application does not limit the execution order of stage 1 and stage 2. In a possible implementation, stage 1 may also occur after stage 2, or stage 2 may be executed synchronously during the execution of stage 1, and so on.

[0247] Phase 3 (S59-S64): Implement refined control based on the permission level of third-party applications accessing the calendar application. This section uses the example of a third-party application requesting to read the calendar as an example. The implementation of refined control for third-party applications requesting to write to the calendar is similar to that for reading the calendar, so we will not elaborate on each of these details here.

[0248] S59 , the application C of the electronic device receives an operation for reading a schedule.

[0249] Specifically, the operation for reading the calendar received by a third-party application of the electronic device, such as application C, includes but is not limited to the following:

[0250] (1) It is used to trigger the electronic device to start the third-party application for the first time. Specifically, for some applications, when the application is run for the first time, the application will request corresponding permissions, including the permission to read the schedule.

[0251] (2) Operations for enabling calendar reminder functions provided by the third-party application. For example, the operation of subscribing to calendar reminders in application A as described in FIG3A above, and the operation of reserving programs as described in FIG3B above, etc. When the application is another type of application, the operation for reading the schedule can also take many other forms, which will not be detailed here.

[0252] S60: Application C of the electronic device requests to read the schedule in the Calendar provider.

[0253] Specifically, after receiving the operation for reading the calendar, the application C of the electronic device requests the Calendar provider to read the schedule.

[0254] S61 , the Calendar provider of the electronic device requests AppOpsService to verify the permission level of application C.

[0255] Specifically, after the Calendar provider of the electronic device receives the request to read the schedule sent by application C, it continues to request AppOpsService to verify the permission level of application C to determine whether application C is allowed to read the schedule in the Calendar provider and further which schedules are allowed to be read.

[0256] S62 , the AppOpsService of the electronic device returns the permission level of application C to the Calendar provider, for example, only allowing reading of schedules created by this application.

[0257] Specifically, after receiving the request sent by the Calendar provider, the AppOpsService of the electronic device starts to verify the permissions of the third-party application and returns the verification result to the Calendar provider.

[0258] For example, in combination with the setting of the permission level for third-party applications to access the calendar application introduced in the aforementioned stage 1, the permission of the application C stored in the AppOpsService at this time is, for example, only allowing reading of schedules created by this application. Therefore, the permission level of the party application C returned by AppOpsService to the Calendar provider includes information indicating that only reading of schedules created by this application is allowed.

[0259] S63: The Calendar provider of the electronic device obtains the schedule created by the application C according to the schedule tag.

[0260] Specifically, after receiving the instruction returned by AppOpsService that only the information of the schedule created by this application is allowed to be read, the Calendar provider of the electronic device obtains the schedule created by the application C from the Calendar provider according to the tag of the schedule.

[0261] S64: The Calendar provider of the electronic device returns to the application C only the schedules belonging to the application C in the Calendar provider.

[0262] Specifically, when the Calendar provider stores schedules created by application C, the Calendar provider will only return the schedules created by application C in the calendar to application C. If the Calendar provider does not store schedules created by application C, no other schedules will be returned. Specifically, by comparing the interfaces of application C shown in d in the aforementioned Figure 3F and d in Figure 3I , it can be seen that when the permissions of application C include allowing reading of all calendars, application C can display the schedule information of application A, application B and calendar application included in d in Figure 3F . When the permissions of application C are modified to allow reading of calendars created by this application, application C displays the interface shown in d in Figure 3I , which does not include the schedule information of application A, application B and calendar application, but only includes the schedule and project meeting of application C.

[0263] It can be seen that by setting refined permission levels to implement the permission management method provided by this application, each application can access the calendar application according to the corresponding permission level based on user needs, avoiding access to all schedules in the calendar application without user authorization, including schedules created by other applications in the calendar, thereby avoiding the leakage of user privacy.

[0264] As well as the introduction to the aforementioned UI implementation and method flow, the following introduces the relevant devices used in the permission management method provided in this application, including the form of the electronic device, software and hardware architecture, etc.

[0265] Electronic equipment can be equipped or portable terminal devices with other operating systems, such as mobile phones, tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, ultra-mobile personal computers (UMPCs), netbooks, as well as cellular phones, personal digital assistants (PDAs), augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, wearable devices, in-vehicle devices, smart home devices and / or smart city devices, etc.

[0266] Referring to FIG6 , FIG6 shows a schematic diagram of the hardware architecture of an electronic device.

[0267] The electronic device may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a camera 193, a display screen 194, etc. The sensor module 180 may include a pressure sensor 180A, a touch sensor 180B, an acceleration sensor 180C, etc.

[0268] It is understood that the structures illustrated in the embodiments of the present application do not constitute specific limitations on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0269] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0270] The controller can be the nerve center and command center of the electronic device. The controller can generate operation control signals based on instruction operation codes and timing signals to complete the control of instruction fetching and execution.

[0271] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0272] In the embodiment of the present application, the processor 110 is used to control the corresponding software and hardware modules to execute the method introduced in Figures 4 and 5 above. The specific method can be combined with the relevant description of Figures 4 and 5 above, which will not be repeated here.

[0273] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0274] The USB interface 130 is an interface that complies with USB standard specifications, and specifically can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device.

[0275] In the present application, the USB interface 130 may also be used to transmit data between the electronic device and peripheral devices, for example, it may be used to connect headphones and play audio through the headphones.

[0276] It is understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is only for illustrative purposes and does not constitute a structural limitation on the electronic device. In other embodiments of the present application, the electronic device may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0277] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the electronic device's wireless charging coil. While charging the battery 142, the charging management module 140 can also power the electronic device through the power management module 141.

[0278] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0279] The wireless communication function of the electronic device can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.

[0280] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in an electronic device can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0281] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied in electronic devices. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0282] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0283] The wireless communication module 160 can provide wireless communication solutions for electronic devices, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, demodulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0284] In some embodiments, antenna 1 of the electronic device is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that the electronic device can communicate with a network and other devices via wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS) and / or satellite-based augmentation system (SBAS).

[0285] The electronic device implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0286] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD). The display screen panel can also be made of an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniLED, a microLED, a micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device can include one or N display screens 194, where N is a positive integer greater than one.

[0287] In an embodiment of the present application, the electronic device can display a user interface such as that shown in Figures 1, 2A-2F, and 3A-3H provided in the previous UI embodiment through the display screen 194, which will not be described in detail here.

[0288] The electronic device can realize the shooting function through the ISP, camera 193, video codec, GPU, display 194 and application processor.

[0289] The ISP processes data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and transformed into a visible image. The ISP can also perform algorithmic optimization on image noise and brightness. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be located within camera 193.

[0290] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0291] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when an electronic device selects a frequency, the DSP performs a Fourier transform on the frequency energy.

[0292] Video codecs are used to compress or decompress digital video. Electronic devices may support one or more video codecs. This allows them to play or record videos in a variety of encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0293] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU enables intelligent cognitive applications in electronic devices, such as image recognition, face recognition, speech recognition, and text comprehension.

[0294] The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).

[0295] Random access memory may include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM, for example, the fifth generation of DDR SDRAM is generally referred to as DDR5 SDRAM), etc.

[0296] Non-volatile memory may include disk storage devices and flash memory.

[0297] Flash memory can be divided into NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. according to the operating principle; single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), quad-level cell (QLC), etc. according to the storage cell potential level; universal flash storage (UFS) and embedded multi media card (eMMC) can be divided into UFS and eMMC according to the storage specification.

[0298] The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (such as machine instructions) of the operating system or other running programs, and can also be used to store user and application data.

[0299] The non-volatile memory may also store executable programs and user and application data, etc., and may be loaded into the random access memory in advance for direct reading and writing by the processor 110 .

[0300] The external memory interface 120 can be used to connect to an external non-volatile memory device to expand the storage capacity of the electronic device. The external non-volatile memory device communicates with the processor 110 via the external memory interface 120 to implement data storage. For example, files such as music and videos can be stored in the external non-volatile memory device.

[0301] In the embodiment of the present application, the above-mentioned memory may be used to store the schedules stored in the Calendar Provider. For details, please refer to the introduction to Table 1 above, which will not be repeated here.

[0302] The electronic device can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0303] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0304] Speaker 170A, also known as a "speaker", is used to convert audio electrical signals into sound signals. The electronic device can listen to music or listen to hands-free calls through the speaker 170A. In an embodiment of the present application, the electronic device can choose to use the speaker 170A to output audio according to the operation of the audio output device selected by the user. In this scenario, if the electronic device sets the speaker volume to a large volume range, the processor 110 will control the corresponding software and hardware modules to execute the aforementioned method flow so that the speaker 170A outputs loud audio so that the user can hear the audio content clearly.

[0305] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the electronic device receives a call or voice message, the voice can be heard by placing the receiver 170B close to the human ear.

[0306] Microphone 170C, also known as "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 170C to input the sound signal into the microphone 170C. The electronic device can be provided with at least one microphone 170C. In other embodiments, the electronic device can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device can also be provided with three, four or more microphones 170C to realize sound signal collection, noise reduction, and identification of sound sources, and realize directional recording function, etc.

[0307] The headphone jack 170D is used to connect a wired headphone and can be the USB interface 130 or a 3.5mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0308] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be located on display screen 194. There are many types of pressure sensors 180A, such as resistive, inductive, and capacitive. A capacitive pressure sensor can include at least two parallel plates made of conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. The electronic device determines the intensity of the pressure based on this change in capacitance. When a touch operation is applied to display screen 194, the electronic device detects the intensity of the touch operation based on pressure sensor 180A. The electronic device can also calculate the location of the touch based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch location but with different touch intensities can correspond to different operation instructions. For example, when a touch operation with an intensity less than a first pressure threshold is applied to a short message application icon, an instruction to view short messages is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to a short message application icon, an instruction to create a new short message is executed.

[0309] Touch sensor 180B, also known as a "touch panel," can be disposed on display screen 194. The touch sensor 180B and display screen 194 form a touch screen, also known as a "touch screen." Touch sensor 180B is configured to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to an application processor to determine the type of touch event. Visual output related to the touch operations can be provided via display screen 194. In other embodiments, touch sensor 180B can also be disposed on the surface of the electronic device, at a location different from that of display screen 194.

[0310] In the present application, the electronic device can detect operations acting on the permission level of the management application to access the calendar application, as well as operations for receiving triggers for the application to read or write to the calendar, etc. through the pressure sensor 180A and the touch sensor 180B.

[0311] In an embodiment of the present application, the electronic device can also determine the motion posture of the electronic device, such as whether the user lifts or picks up the electronic device, by detecting the acceleration on the X, Y, and Z axes on the acceleration sensor 180C.

[0312] Keys 190 include a power button, a volume button, and the like. Keys 190 may be mechanical keys or touch-sensitive keys. The electronic device may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device.

[0313] The software system of the electronic device can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to illustrate the software structure of the electronic device.

[0314] FIG7 is a block diagram of the software structure of the electronic device according to an embodiment of the present application.

[0315] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0316] The application layer can include a series of application packages.

[0317] As shown in FIG. 7 , the application package may include a calendar application, application A, application B, application C, and settings applications.

[0318] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0319] The Calendar app can be used to create schedules. Apps A, B, and C can create schedules through the Calendar app. Settings can be used to provide options for setting the permission level for each app to access the Calendar app.

[0320] As shown in FIG7 , the application framework layer may include a content provider, an activity management system (AMS), and some window managers, view systems, phone managers, resource managers, notification managers, etc. that are not shown.

[0321] Content providers are used to store and retrieve data and make it accessible to applications. This data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0322] In particular, the content provider includes a Calendar Provider, which stores calendars or schedules created by other applications in the calendar.

[0323] AMS is one of the most important system services in electronic devices. It is responsible for starting, switching, and scheduling various components in the system, as well as managing and scheduling application processes. Its responsibilities are similar to those of the process management and scheduling module in an operating system.

[0324] In particular, AMS includes AppOpsService, which is a service for managing the operating permissions of applications. It is a function included in the native system of electronic devices. It can be used to manage the native calendar access permissions of applications installed in electronic devices, that is, it includes two permissions: prohibit access and allow access, and the allowed access means allowing access to all calendars.

[0325] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0326] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0327] The phone manager is used to provide communication functions for electronic devices, such as call status management (including answering, hanging up, etc.).

[0328] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0329] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0330] The Android runtime includes the core library and the virtual machine. The Android runtime is responsible for scheduling and management of the Android system.

[0331] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0332] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0333] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (e.g., OpenGL ES), and a 2D graphics engine (e.g., SGL).

[0334] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0335] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0336] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0337] A 2D graphics engine is a drawing engine for 2D drawings.

[0338] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0339] It should be understood that each step in the above method embodiments provided herein can be implemented by hardware integrated logic circuits in a processor or by software instructions. The method steps disclosed in the embodiments of this application can be directly implemented as being executed by a hardware processor, or by a combination of hardware and software modules in a processor.

[0340] The present application also provides an electronic device, which may include: a memory and a processor. The memory may be used to store a computer program; the processor may be used to call the computer program in the memory so that the electronic device executes the method in any one of the above embodiments.

[0341] The present application also provides a chip system, which includes at least one processor for implementing the functions involved in the method executed by the electronic device in any of the above embodiments.

[0342] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0343] The chip system can be composed of chips, or can include chips and other discrete devices.

[0344] Optionally, there may be one or more processors in the chip system. The processor may be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, etc. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.

[0345] Optionally, the memory in the chip system may be one or more. The memory may be integrated with the processor or may be provided separately from the processor, which is not limited in the embodiments of the present application. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or provided on different chips. The embodiments of the present application do not specifically limit the type of memory or the configuration of the memory and the processor.

[0346] Exemplarily, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.

[0347] The present application also provides a computer program product, which includes: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute the method executed by the electronic device in any of the above embodiments.

[0348] The present application also provides a computer-readable storage medium storing a computer program (also referred to as code or instruction). When the computer program is executed, the computer executes the method executed by the electronic device in any of the above embodiments.

[0349] The various implementation modes of this application can be combined arbitrarily to achieve different technical effects.

[0350] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented 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, all or part of the processes or functions described herein are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may 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) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may 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 integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive).

[0351] Those skilled in the art will appreciate that all or part of the process steps in the above-described method embodiments can be implemented by a computer program instructing the relevant hardware. The program can be stored in a computer-readable storage medium, and when executed, the program can include the process steps in the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0352] In short, the above description is only an embodiment of the technical solution of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made based on the disclosure of the present invention should be included in the scope of protection of the present invention.

Claims

1. A rights management method, characterized in that: The method comprises: When the first interface is displayed, a first operation is received; In response to the first operation, a first window is displayed on the first interface, where the first window includes: The name of the first application; A first option, when a second operation on the first option is received, setting the permission of the first application to access the calendar application to a first permission, wherein the first permission is to access all schedules of the calendar application; and a second option, when a third operation on the second option is received, setting the permission of the first application to access the calendar application to a second permission, wherein the second permission is to access only the schedule created by the first application.

2. The method according to claim 1, characterized in that: The first interface includes an interface for setting an application, or an interface of the first application.

3. The method according to claim 1 or 2, characterized in that: The first window also includes access type information, and the access type information includes: reading a schedule, and / or creating, deleting, or modifying a schedule.

4. The method according to any one of claims 1 to 3, characterized in that: The first application is a shopping application, the first interface is an interface of the first application, The method further comprises: receiving the second operation on the first option; In response to the second operation, setting the permission of the first application to access the calendar application as the first permission; A second interface of the first application is displayed, wherein the commodities included in the second interface are related to the schedules in the calendar application.

5. The method according to any one of claims 1 to 4, characterized in that The first application is a schedule management application; the method further includes: receiving the second operation on the first option, and in response to the second operation, setting the permission for the first application to access the calendar application to the first permission; The third interface of the first application is displayed, and the third interface includes all schedules in the calendar application.

6. The method according to any one of claims 1 to 4, characterized in that The method further comprises: receiving the third operation on the second option, and in response to the third operation, setting the permission for the first application to access the calendar application to the second permission; A fourth interface of the first application is displayed, wherein the fourth interface only includes a schedule created by the first application.

7. The method according to claim 6, characterized in that The method further comprises: A fifth interface of the calendar application is displayed, wherein the fifth interface includes a first schedule created by the first application.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: When the interface of the calendar application is displayed, a fourth operation is received, In response to the fourth operation, a second schedule is displayed in the interface of the calendar application.

9. The method according to any one of claims 1 to 8, characterized in that The first window also includes a third option. When a fifth operation on the third option is received, the permission for the first application to access the calendar application is set to a third permission, and the third permission is to prohibit access to the schedule of the calendar application.

10. The method according to claim 5, characterized in that The method further comprises: Display prompt information, where the prompt information is used to prompt the user to adjust the permissions of the first application.

11. The method according to claim 5, characterized in that All schedules in the calendar application include schedules of the second application, and the method further includes: receiving a sixth operation, and in response to the sixth operation, setting the permission for the first application to access the calendar application to the second permission; The interface of the first application is displayed, wherein the interface of the first application does not include the schedule of the second application.

12. The method according to any one of claims 1 to 11, characterized in that The first operation includes an operation on a calendar reminder control / option.

13. The method according to any one of claims 1 to 12, characterized in that The first application is a third-party application.

14. The method according to any one of claims 1 to 13, characterized in that The method is applied to an electronic device including an application operation authority management service (AppOpsService), and the method further includes: receiving the third operation on the second option; In response to the third operation, the permission of the first application to access the calendar application is stored in the AppOpsService as the second permission.

15. The method according to any one of claims 1 to 14, characterized in that The method is applied to an electronic device including a calendar provider, and the method comprises: After receiving the third operation on the second option, storing the first schedule of the first application in the Calendar provider, and marking the first schedule as belonging to the first application.

16. An electronic device, characterized in that: The electronic device includes one or more memories and one or more processors; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the electronic device to execute the method described in any one of claims 1-15.

17. A computer-readable storage medium comprising instructions, characterized in that: When the instructions are executed on an electronic device, the electronic device is caused to execute the method as claimed in any one of claims 1 to 15.

Images