Authority management method, graphical interface and related device

Abstract

The invention discloses an authority management method, a graphical interface and a related device. In the method, the electronic equipment can store schedules created by a calendar application and schedules created by other applications in the calendar application, and marks the application to which each schedule belongs. Afterwards, when an application requests to obtain the permission for accessing the calendar application, the electronic equipment can grant the corresponding permission to the application by adopting the permission level (such as the permission level of only accessing the calendar created by the application) selected by the user from a plurality of permission levels. And thus, the application is prevented from accessing a schedule which is not created in the calendar by the application without permission.

Description

Technical Field

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

[0002] Nowadays, many private information of users is recorded in electronic devices. For example, the calendar application records the user's schedule. When users use electronic devices, some applications usually require the calendar application to grant some permissions to complete the corresponding tasks.

[0003] 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. Summary of the invention

[0004] The present 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 and 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 the calendar created by this application) from multiple permission levels to grant the application corresponding permissions, thereby preventing the application from accessing schedules not created by this application without permission.

[0005] In a first aspect, the present application provides a permission management method, the method comprising: 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 comprising: the name of a first application; a first option, when a second operation on the first option is received, 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 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, the second permission being access only to schedules created by the first application.

[0006] After implementing the method provided in the first aspect, the user can personalize the permission of the first application to access the calendar, including setting the permission of the first application to access the calendar to access all schedules of the calendar application, or setting it to access only the schedules created by the first application. In this way, both the user's privacy and security can be guaranteed and the normal use of the first application can be guaranteed.

[0007] 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.

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

[0009] 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.

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

[0011] 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.

[0012] 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 acquired schedules, while 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 those provided by the shopping application by default and have nothing to do with the schedule.

[0013] 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, after setting the first application's permission to access the calendar application to the first permission, the method also includes: receiving a second operation on the first option, and in response to the operation, setting the first application's permission to access the calendar application to the first permission; displaying a 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 first application's permission to access the calendar application to the second permission; displaying a fourth interface of the first application, the fourth interface only including schedules created by the first application.

[0014] 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.

[0015] In this way, when the schedule management application is set to allow access to all schedules of the calendar application, all schedules in the calendar can be displayed synchronously in the schedule management application. When the schedule management application is set to allow access to only the schedule of this application, only the schedule of the schedule management application itself is displayed in the schedule management application, that is, the schedule of other applications in the calendar application cannot be read, and the user's privacy cannot be analyzed or leaked.

[0016] 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, or after setting the permission of the first application 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.

[0017] 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.

[0018] 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.

[0019] 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 permission of the first application to access the calendar application to a third permission, and the third permission is to prohibit access to the schedule of the calendar application.

[0020] 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.

[0021] In combination with the method described in the first aspect, after setting the permission of the first application to access the calendar application as the first permission, the method also includes: displaying a prompt message, the prompt message being 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 as the second permission.

[0022] 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.

[0023] 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 setting application.

[0024] In this way, the user can output a window for managing the permission of the first application to access the calendar through different operations.

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

[0026] 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.

[0027] 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.

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

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

[0030] In combination with the method described in the first aspect, the method is applied to an electronic device including AppOpsService and Calendarprovider. 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 of 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.

[0031] In combination with the method described in the first aspect, the method is applied to an electronic device including AppOpsService and Calendarprovider. After receiving the third operation on 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 of 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.

[0032] In this way, the application to which the schedule stored in the Calendar provider belongs and the permissions of the application stored in the AppOpsService can be granted permission to access the corresponding schedule based on the permissions of the application.

[0033] In a second aspect, the present application provides an electronic device, comprising 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 comprises computer instructions, and the one or more processors call the computer instructions so that the electronic device executes a method as described in any one of the first aspects.

[0034] In a third aspect, the present application provides a chip, which is applied to an electronic device, and the chip includes one or more processors, and the processor is used to call computer instructions so that the electronic device executes any method described in the first aspect.

[0035] 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

[0036] Figure 1 A schematic diagram of a "multiple permission levels" management interface for accessing a calendar application provided in an embodiment of the present application;

[0037] Figure 2A-2B A schematic diagram of a first operation interface for managing the permission of an application to access a calendar application in settings provided in an embodiment of the present application;

[0038] Figure 2C-Figure 2D A schematic diagram of a second operation interface for managing the permission of an application to access a calendar application in settings provided in an embodiment of the present application;

[0039] Figure 2E A schematic diagram of a third operation interface for managing the permission of an application to access a calendar application in settings provided in an embodiment of the present application;

[0040] Figure 2F A schematic diagram of a fourth operation interface for managing the permission of an application to access a calendar application in settings provided in an embodiment of the present application;

[0041] Figure 3A A schematic diagram of an operation interface for managing the permission of application A to access a calendar application provided in an embodiment of the present application;

[0042] Figure 3BA schematic diagram of an operation interface for managing the permission of application B to access a calendar application provided in an embodiment of the present application;

[0043] Figure 3C A schematic diagram of an operation interface for managing the permission of application C to access a calendar application provided in an embodiment of the present application;

[0044] Figure 3D A schematic diagram of an operation interface for creating a schedule in a calendar application is shown as an example;

[0045] Figure 3E The following example illustrates a scenario in which application A recommends corresponding services based on schedules read from a calendar application.

[0046] Figure 3F A schematic diagram of an operation interface for creating a schedule in application C is shown as an example;

[0047] Figure 3G-3H The following example shows the schedule information provided by the calendar application and application C;

[0048] Fig. 3I A schematic diagram of an operation interface for exemplarily showing how to change the permission of application C to access the calendar application;

[0049] Figure 4 The permission management method process provided in the embodiment of this application;

[0050] Figure 5 A specific implementation of the rights management method provided in the embodiment of the present application;

[0051] Figure 6 A schematic diagram of the hardware architecture of an electronic device provided in an embodiment of the present application;

[0052] Figure 7 A schematic diagram of the software architecture of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] The technical solutions in the embodiments of the present application will be described clearly and in detail below in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in the text is only a description of the association relationship of the associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0054] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.

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

[0056] The term "user interface (UI)" in the following embodiments of the present 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 can be recognized by the user. The commonly used form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operation 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.

[0057] 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 snap-up reminders and sign-in reminders in a shopping application, the shopping application needs to be authorized by the calendar application, so that the purpose of reminding users to snap up 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 be authorized by 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 in a schedule management application, the schedule management application needs to be authorized by 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.

[0058] However, the default permissions granted by the current calendar application (referred to as native calendar access permissions) only include allowing access and prohibiting, where allowing access is equivalent to authorization by the calendar application. After obtaining authorization from the calendar application, some applications can access all schedules in the calendar application, including schedules newly created by users in the calendar application and schedules of other applications read by the calendar application. Accessing all schedules in the calendar application may include reading all schedules, creating new schedules, or modifying / deleting all schedules, etc. If these applications are third-party applications, they may illegally query or tamper with the schedules, thereby threatening the privacy security of users.

[0059] 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.

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

[0061] The calendar application is a system application. A system application refers to an application provided or developed by a manufacturer of an electronic device. The manufacturer of an electronic device may include the manufacturer, supplier, provider or operator of the electronic device.

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

[0063] Accessing the calendar application refers to two types of operations: reading the calendar or writing the calendar. Specifically, "reading" refers to reading the schedule in the calendar application, and "writing" includes creating a new schedule in the calendar application, or modifying / deleting the schedule in the calendar application.

[0064] The various levels of permissions include but are not limited to: prohibit, allow access to all calendars, and only access to calendars created by this application. Among them, prohibit is one of the native calendar access permissions of the electronic device, while the two permission levels of allowing access to all calendars and only accessing calendars created by this application are equivalent to further refining the allowed access in the native calendar access permissions.

[0065] Accessing only the calendar created by this application means that the application can only access the schedules created by this application in the calendar application, and cannot access the schedules created by the calendar application or created by other applications in the calendar application. Specifically, when accessing the calendar refers to reading the calendar, accessing only the calendar created by this application means that the application is only allowed to read the schedules created by this application in the calendar application; when accessing the calendar refers to creating a new calendar, accessing only the calendar created by this application means that the application is only allowed to write the schedules created by this application in the calendar application; when accessing the calendar refers to modifying / deleting the calendar, accessing only the calendar created by this application means that the application is only allowed to delete / modify the schedules created by this application in the calendar application.

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

[0067] Prohibit means prohibiting the application from accessing the schedule in the calendar application. Specifically, when accessing the calendar means reading the calendar, prohibiting means prohibiting the application from reading the schedule in the calendar application; when accessing the calendar means creating a new calendar, prohibiting means prohibiting the application from writing schedules in the calendar application; when accessing the calendar means modifying / deleting the calendar, prohibiting means prohibiting the application from deleting / modifying the schedule in the calendar application.

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

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

[0070] (2) It ensures 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 that are not created by this application in the calendar application, and thus cannot read the 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 the 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 the calendar created by this application, they can create schedules in the calendar application and obtain the schedules they created in the calendar application, which is sufficient to provide users with corresponding functions.

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

[0072] refer to Figure 1 , Figure 1 A schematic diagram of a management interface for accessing “multiple permission levels” of a calendar application is shown as an example.

[0073] Figure 1 a-1 in the figure shows an example of a management interface of "multiple permission levels" corresponding to the permission to read the calendar. The management interface includes a window 111, which includes prompt information 111A for requesting the user whether to allow "application A" to access the calendar, and prompt information 111B stating that the access to the calendar is specifically to read the calendar, and options corresponding to three levels of calendar access permission, namely, option 111C corresponding to accessing only the calendar created by this application, option 111D corresponding to allowing access to all calendars, and option 111E corresponding to prohibiting.

[0074] Users can select Figure 1 Any of the above three options in a-1 is used to trigger the electronic device to take the calendar access permission corresponding to the option for application A.

[0075] Figure 1 a-1 in FIG. 1 is merely 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 may also be as follows: Figure 1 As shown in a-2 of FIG. 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 access. This is because, for applications that only read the calendar, such applications will not create schedules in the calendar application, so when such applications read the calendar application, there is no distinction between whether to run and read the schedules created by the application, so there is no need to provide an option corresponding to the permission level of only accessing the schedules created by the application. Figure 1 b in the figure shows an example of a management interface for "multiple permission levels" corresponding to the permission to write a 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 permission, namely, option 112C corresponding to accessing only calendars created by this application, option 112D corresponding to allowing access to all calendars, and option 112E corresponding to prohibiting.

[0076] Users can select Figure 1Any of the above three options in b is used to trigger the electronic device to take the calendar access permission corresponding to the option for application B.

[0077] Figure 1 Figure c in the figure shows an example of a management interface for "multiple permission levels" corresponding to the permissions for reading and writing calendars. The management interface includes a window 113, which includes prompt information 113A for requesting the user whether to allow "application C" to access the calendar, and prompt information 113B stating that the access to the calendar is specifically for reading and writing the calendar, and options corresponding to three levels of calendar access permissions, namely, option 113C corresponding to accessing only calendars created by this application, option 113D corresponding to allowing access to all calendars, and option 113E corresponding to prohibiting.

[0078] Users can select Figure 1 Any of the above three options in c can be used to trigger the electronic device to take the calendar access permission corresponding to the option for application C.

[0079] In an optional implementation, some applications (such as application A) need to access the calendar application only to perform read operations on the calendar, some applications (such as application B) need to access the calendar application only to perform write operations on the calendar, and some other applications (such as application C) need to access the calendar application both to perform read operations and to perform write operations on the calendar. Therefore, for different applications, when they request permission to access the calendar application, the operations included in the declared access to the calendar application may be different.

[0080] In an optional embodiment, Figure 1 The window 111 / window 112 / window 113 shown can be triggered to display by setting the calendar access permissions provided in the application for managing the calendar access permissions corresponding to various applications (see below for details). Figure 2A-2F ), or it can be triggered and displayed when the user opens the calendar reminder function in application A / application B / application C (see below for details) Figure 3A-3E description).

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

[0082] In the embodiments of the present application Figure 1 The four interfaces shown in can also be referred to as first interfaces.

[0083] refer to Figure 2A-2F , Figure 2A-2FA set of schematic diagrams of operation interfaces for managing the permission of an application to access a calendar application in settings are exemplified.

[0084] Figure 2A-2B Illustrate the first method of managing the permissions of an app to access the calendar app in settings.

[0085] Figure 2A The a in the figure is an interface provided by the settings application, which may include multiple setting options, such as privacy options.

[0086] The user can trigger the electronic device to display the privacy details page by clicking the privacy option in the setting option. Figure 2A The operation on the privacy option in a triggers the electronic device to open the privacy details page. For details, see Figure 2A As shown in b.

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

[0088] The user can click on the card 213 for managing application permissions to trigger the electronic device to open the permission management page. Figure 2A The operation on the card 213 for managing application permissions in b triggers the electronic device to open the permission management details page, see Figure 2A As shown in c.

[0089] Figure 2A c in the figure is a permission management details page, which includes a permission column 213A and an application column 213B. The user can trigger the electronic device to display a series of options corresponding to the selected column in the permission management details page by selecting the permission column 213A or the application column 213B. For example, when the application column 213B is selected as shown in c, a series of application options are displayed in the permission management details page, including options corresponding to application A, options corresponding to application B, options corresponding to application C, and options corresponding to application D, etc.

[0090] The user can also trigger the electronic device to display the application permission details page corresponding to the selected application by selecting an option corresponding to any application. Figure 2A The operation on the option corresponding to application A in c triggers the electronic device to open the permission details page of application A. For details, see Figure 2A As shown in d.

[0091] Figure 2Ad in FIG. 1 is the permission details page of application A, which includes multiple permission setting options, such as permission setting option 214 corresponding to the calendar, permission setting options corresponding to location information, permission setting options corresponding to the camera, permission setting options corresponding to the microphone, etc. Each permission option also displays the permission level currently used by the permission. For example, the permission setting option 214 corresponding to the calendar displays "prohibited", which means that the calendar permission currently owned by application A is prohibited, that is, application A is prohibited from accessing the calendar application.

[0092] The user can further manage the calendar permissions owned by application A by clicking the permission setting option 214 corresponding to the calendar. Figure 2A The operation on the permission setting option 214 corresponding to the calendar in d triggers the electronic device to pop up a window for setting the permission level of application A to access the calendar application, see Figure 2B In the embodiment of the present application, Figure 2A The interface shown in d in FIG. 1 can also be referred to as the first interface. Figure 2A The operation of the permission setting option 214 corresponding to the calendar shown in d can also be called the first operation.

[0093] Figure 2B e in the figure is still the permission details page of application A, and the permission details page of application A now displays window 215. Window 215 contains prompt information for stating the operations involved in application A accessing the calendar application, such as allowing "application A" to create / modify / delete calendars, and also contains options corresponding to multiple permission levels for accessing calendars, such as "only access calendars created by this application", "allow access to all calendars" and "forbid". Among them, the "forbid" option is selected, indicating that the current permission for application A to access the calendar is "forbid". In the embodiment of the present application, window 215 can also be referred to as the first window, application A included in window 215 can also be referred to as the name of the first application, the prompt information included in window 215 for stating the operation involved in application A accessing the calendar application can also be referred to as access type information, "Allow access to all calendars" included 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.

[0094] The user can change the permission level of application A to access the calendar from "prohibited" to "only access calendars created by this application" by clicking the "only access calendars created by this application" option. Figure 2B If the operation on "Only access calendars created by this application" in e is performed, the electronic device will be triggered to change the permission level of application A to access the calendar to "Only access calendars created by this application", see Figure 2B As shown in f.

[0095] Figure 2B f 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.

[0096] Figure 2C-Figure 2D Illustrate a second method for managing app access to the Calendar app in Settings.

[0097] Figure 2C a in the above is the permission management details page (same as the above Figure 2A The permission management details page includes a permission column 213A and an application column 213B. For other introductions to the permission management details page, please refer to the previous Figure 2A The description of c in is not repeated here.

[0098] 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. Figure 2C As shown in b.

[0099] Figure 2C b in the figure 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.

[0100] The user can further manage calendar permissions by clicking on the permission setting option 216 corresponding to the calendar. Figure 2C The operation on the permission setting option 216 corresponding to the calendar in b triggers the electronic device to display the calendar permission details page, see Figure 2C As shown in c.

[0101] Figure 2CThe c in the figure 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 correspond to the calendar read operation and calendar write operation respectively.

[0102] The user can set the corresponding permission to read the calendar or the permission to write the calendar by clicking any of the "Read Calendar" option and the "Create / Modify / Delete Calendar" option. For example, in response to clicking the "Read Calendar" option, the triggering electronic device will display the permission setting details page for reading the calendar. Figure 2C As shown in d.

[0103] Figure 2C d in the figure is a permission setting details page for reading calendars, which includes options corresponding to application A, options corresponding to application B, option 217 corresponding to application C, and options corresponding to application D, etc. In addition, the permission level of the application for reading calendars is also displayed in the options corresponding to each application, for example, the permission level displayed in option 217 corresponding to application C is "Allow access to all calendars".

[0104] The user can reset the permission level of any application when reading the calendar by selecting the option corresponding to the application. Figure 2C The operation on option 217 corresponding to application C in d triggers the electronic device to pop up a window for setting the permission level of application C to read the calendar, see Figure 2D In the embodiment of the present application, Figure 2C The interface shown in d can also be called the first interface, which acts on Figure 2C The operation on option 217 corresponding to application C shown in d may also be referred to as a first operation.

[0105] Figure 2De in the figure is still the permission setting details page for reading the calendar, and the permission setting details page for reading the calendar displays a window 218. The window 218 contains prompt information that allows "application C" to read the calendar, and also contains options corresponding to multiple permission levels for reading the calendar, such as "only access calendars created by this application", "allow access to all calendars" and "prohibit". Among them, the "allow access to all calendars" option is in a selected state, indicating that the permission for the current application C to read the calendar is "allow access to all calendars". In the embodiment of the present application, window 218 can also be referred to as the first window, the application C contained in window 218 can also be referred to as the name of the first application, the prompt information for stating that application C reads the calendar contained in window 218 can also be referred to as access type information, the "allow access to all calendars" contained in window 218 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 "only access calendars created by this application" can also be referred to as the second permission, the "only access calendars created by this application" option can also be referred to as the second option, "prohibit" 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.

[0106] The user can change the permission level of application C to read the calendar from "Allow access to all calendars" to "Only access calendars created by this application" by clicking the "Only access calendars created by this application" option. Figure 2D If the operation on "Only access calendars created by this application" in e is performed, the electronic device is triggered to change the permission level of application C to access the calendar application to "Only access calendars created by this application", see Figure 2D As shown in f.

[0107] Figure 2D f 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.

[0108] Figure 2E Illustrate a third method for managing app access to the Calendar app in Settings.

[0109] Figure 2EThe a in the figure 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 optimization, a card 212 for viewing privacy access records, a card 213 for managing application permissions, and other cards.

[0110] The user can click on the card 211 of the recommended optimization to trigger the electronic device to display the privacy assistant details page. Figure 2E As shown in b.

[0111] Figure 2E b in the figure is the privacy assistant details page, which includes the over-authorized application risk detection results, and when there is a risk in an application (for example, when an application frequently reads all calendars, it is considered that the application excessively obtains the user's private information), it will also display a prompt message 219A suggesting optimization. The prompt message 219A may, for example, display a prompt message such as "Allowing "Application B" to read all calendars is risky, and it is recommended to optimize to: only access calendars created by this application", and display a control 218A for immediate optimization and a control 218B for canceling optimization.

[0112] The user can click control 218A to make the electronic device modify the permission of application B to access the calendar application to the permission corresponding to "only access the calendar created by this application". Figure 2E The electronic device starts to optimize the permission level of application A. For details, see Figure 2E The prompt information 219B in c will also output the prompt information of successful optimization. Figure 2E As shown in d.

[0113] Figure 2E d in the figure displays a prompt message 219C for prompting the user that the optimization is successful. For example, the prompt message 219C may display a prompt message "The optimization is successful. Application B has been optimized to only access the calendar created by this application."

[0114] Figure 2F Illustrate a fourth method for managing an app's access to the Calendar app in Settings.

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

[0116] 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. Figure 2F As shown in b.

[0117] Figure 2F b in the figure is the details page of all privacy access records. The details page of all privacy access records can be used to display the records of each application accessing privacy information, for example, the records of "application A reads all calendars", the records of "application A reads all calendars", etc.

[0118] Users can modify the permissions of any application to access the corresponding privacy by clicking on the privacy access record of any application. For example, in response to the operation on the record of "Application A reads calendar", it jumps to the privacy access record details page of application A. For details, see Figure 2F As shown in c.

[0119] Figure 2F c in the figure 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 accesses various types of privacy information, for example, application A read all calendars 11 times before 15:10 today, etc.

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

[0121] Figure 2F A window is displayed in d in . The window contains prompt information for stating the operations involved in application A accessing the calendar application. The prompt information, for example, allows "application A" to read the calendar, and also contains options corresponding to multiple permission levels for accessing the calendar application. These options, for example, include three options: "Only access 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 "Prohibit".

[0122] The user can change the permission level of application A to access the calendar application from "Allow access to all calendars" to "Only access calendars created by this application" by clicking the "Only access calendars created by this application" option. Figure 2F The window displayed in d in the figure 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 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.

[0123] above Figure 2A-2F Only four operation methods for managing the permission of an application to access the calendar application in the settings are shown as examples, which should not constitute a limitation to the present application. In addition, the permission of an application to access the calendar application can be managed in more other ways.

[0124] refer to Figure 3A-3C , Figure 3A-3C A set of schematic diagrams of operation interfaces for managing the permission of an application to access a calendar application are shown as examples.

[0125] Figure 3A This section illustrates the operation method of managing the permission of application A to access the calendar application.

[0126] Figure 3A Here, a is the desktop of the electronic device, which may include icons of multiple applications, for example, an icon of application A, an icon of application B, an icon of application C, an icon of application D, and a setting icon.

[0127] The user can trigger the electronic device to activate any application by clicking on the icon of the application. Figure 3A The electronic device opens the application A and displays the interface provided by the application A. For details, see Figure 3A As shown in b.

[0128] Figure 3A b in the figure is the interface of application A. Application A may be a shopping application. The interface of application A may display a control 311 for signing in, and may also display some commodities available for purchase by the user, etc. The embodiment of the present application does not impose any limitation on the interface of application A.

[0129] The user can open the sign-in interface through control 311. Usually, after the user opens the sign-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 sign-in reminder task in the calendar to remind the user to sign in in application A.

[0130] Figure 3A The c in FIG. 3 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, sign in every day to receive cash", and also displays a control 312A for immediate subscription and a control 312B for unsubscribing.

[0131] The user can use control 312A to determine the subscription 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. Figure 3A In the embodiment of the present application, Figure 3A The interface shown in c can also be called the first interface, which acts on Figure 3A The operation on the control 312A shown in c may also be referred to as a first operation.

[0132] Figure 3A d in 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 the access to the calendar is specifically to read the calendar and create / modify / delete the calendar, and options corresponding to three levels of calendar access permission: option 313C corresponding to access only calendars created by this application, option 313D corresponding to allowing access to all calendars, and option 313E corresponding to prohibiting.

[0133] Users can select Figure 3A Any of the above three options in d is triggered to trigger the electronic device to take the calendar access permission corresponding to the option to application A. For example, in response to the operation on option 313C, the calendar access permission possessed by application A includes the permission to create schedules in the calendar application, so the calendar application can display the schedule information corresponding to the "application A check-in" created by the user through application A this time. For details, please refer to the following description of the calendar access permission. Figure 3D Description of b.

[0134] In the embodiments of the present application, Figure 3AThe window 313 displayed in d in 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 the window 313 can also be called access type information, the "allow access to all calendars" contained in the 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.

[0135] Figure 3B This section illustrates the operation method for managing the permission of application B to access the calendar application.

[0136] Figure 3B Here, a is the desktop of the electronic device, which may include icons of multiple applications, for example, an icon of application A, an icon of application B, an icon of application C, an icon of application D, and a setting icon.

[0137] The user can trigger the electronic device to activate any application by clicking on the icon of the application. Figure 3B The operation on the icon of application B in a triggers the electronic device to open application B and display the interface provided by application B. For details, see Figure 3B As shown in b.

[0138] Figure 3B Reference numeral b is the interface of application B, which may be a video application. The interface of application B may display an icon 314A for scheduling live video, and may 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.

[0139] The user can schedule a live video through icon 314A. Usually, after the user confirms the live video schedule, the electronic device can pop up a window for application B to request permission to access the calendar application. After obtaining the corresponding permission, application B can create a schedule in the calendar to remind the user to watch the live video. In this embodiment of the application, Figure 3B The interface shown in b can also be called the first interface, which acts on Figure 3B The operation on the icon 314A shown in b may also be referred to as a first operation.

[0140] Figure 3Bc in the figure 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 the access to the calendar is specifically to read the calendar and create / modify / delete the calendar, and options corresponding to three levels of calendar access permissions, namely, option 315C corresponding to access only the calendar created by this application, option 315D corresponding to allowing access to all calendars, and option 315E corresponding to prohibiting.

[0141] Users can select Figure 3B Any of the above three options in c triggers the electronic device to take the calendar access permission corresponding to the option to application B. For example, in response to the operation on option 315C corresponding to only accessing the calendar 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 cannot access (read and add / modify / delete) the schedules created by other applications or the calendar application itself in the calendar application. In the embodiment of the present application, Figure 3B The window 315 displayed in c in can also be called the first window, the application B contained in the window can also be called the name of the first application, the prompt information 315B for reading calendars and creating / modifying / deleting calendars contained in the window 315 can also be called access type information, the "allow access to all calendars" contained in the window 315 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.

[0142] Figure 3B d in the figure is the interface of application B. When the user has allowed application B to access the calendar application, the interface changes the icon 314A originally used for scheduling a video to the icon 314B for scheduling a video. In addition, in response to the operation on option 315C, the calendar access permission of application B includes the permission to create schedules in the calendar application. Therefore, the calendar application can display the schedule information corresponding to the "schedule a live video of application B" created by the user through application B. For details, please refer to the following description of Figure 3D Description of b.

[0143] Figure 3C The following illustrates the operation method of managing the permission of application C to access the calendar application.

[0144] Figure 3CHere, a is the desktop of the electronic device, which may include icons of multiple application programs, such as the icon of application C, etc.

[0145] The user can trigger the electronic device to activate any application by clicking on the icon of the application. Figure 3C The operation on the icon of application C in a triggers the electronic device to open application C and display the interface provided by application C. For details, see Figure 3C As shown in b.

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

[0147] The user can import the schedule in the calendar application into application C through icon 318A. For example, in response to the operation on icon 318A, the electronic device displays Figure 3C The user interface shown in c. In the embodiment of the present application, Figure 3C The interface shown in b can also be called the first interface, which acts on Figure 3C The operation on the icon 318A shown in b may also be referred to as a first operation.

[0148] Figure 3C The c in the figure is still the interface of application C, and a window 319 is displayed. Window 319 includes a prompt message 319A for 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 a calendar, and options corresponding to three levels of calendar access permissions, namely, option 319C corresponding to accessing only the calendar created by this application, option 319D corresponding to allowing access to all calendars, and option 319E corresponding to prohibiting.

[0149] Users can select Figure 3D Any of the above three options in c triggers the electronic device to take the calendar access permission corresponding to the option to application C. For example, in response to the operation on option 319C corresponding to allowing access to all calendars, application B can access (read) all schedules created by the application in the calendar application, and application C can also display the schedule information obtained from the calendar application in application C. For details, see Figure 3C In the embodiment of the present application, Figure 3CThe window 319 displayed in c in can also be called the first window, the application C contained in the window can also be called 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 called access type information, the "allow access to all calendars" contained in window 319 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.

[0150] Figure 3C In c, 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 application C's permission to access the calendar. Since application C is a schedule management application, it may already have relatively complete functions such as creating and managing calendars, and can directly write the calendars it created 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 above Figure 3C After the operation shown in b on icon 318A, the management window popped up by the electronic device for managing the permission of application C to access the calendar may be Figure 1 For details of the window shown in a-2, please refer to the above Figure 1 Correspondingly, the above action is Figure 3C c allows access to all calendars, corresponding to the operation on option 319C, corresponding to the operation on Figure 1 A-2 allows access to the operations on the corresponding options of the calendar.

[0151] Figure 3C d in the figure is still the interface of application C (also called the third interface). At this time, the interface displays a window 411, which displays all the schedules in the calendar application of application C, such as schedule information 411A corresponding to "check in to application A" and schedule information 411B corresponding to "book a live video of application B". Figure 3A After granting application A calendar access rights, application A creates a schedule in the calendar application. Schedule information 411B is as described above. Figure 3B This section describes how to create a schedule in the Calendar app after granting App B calendar access permissions.

[0152] Figure 3DThe following is an example of how to create a schedule in a calendar application.

[0153] Figure 3D Here, a is the desktop of the electronic device, which may include icons of multiple applications, such as a calendar icon, etc.

[0154] The user can trigger the electronic device to activate any application by clicking on the icon of the application. Figure 3E The operation on the calendar icon in a triggers the electronic device to open the calendar application and display the interface provided by the calendar application. Figure 3D As shown in b.

[0155] Figure 3D b in the figure is a calendar interface, and the calendar interface may display a calendar 316, a window 317, a new schedule icon 317A, and schedule reminder information, which may include the above Figure 3A After granting the calendar access permission to application A, the schedule information 317B corresponding to the schedule "booking the live video of application B" created by application A in the calendar application is the same as the schedule information 317B in the previous text. Figure 3B The schedule information 317C created by application B in the calendar application after granting application B calendar access rights is introduced. In the embodiment of the present application, Figure 3D The interface of the calendar application shown in b may also be referred to as a fifth interface, and the schedule information 317B of application A and the schedule information 317C of application B may also be referred to as a first schedule.

[0156] 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 Figure 3E The user interface shown in c.

[0157] Figure 3D c in the figure is a new schedule details page, i.e., a page to be edited for a new schedule. The new schedule details page may include a confirmation icon 318A and a cancel icon 318B, and page titles such as a new schedule, a title entry, a location entry, a time entry, etc. Among them, the confirmation icon 318A can be used to confirm the edited to-do event, and the cancel icon 318B can be used to close the to-do page. The title entry can be used to receive the title of the to-do event input by the user, the location entry can be used to receive the location of the to-do event input by the user, and the time entry can be used to receive the start and end time of the to-do event input by the user.

[0158] After editing the schedule information, the user can complete the creation of the schedule by confirming the icon 318A, for example, in response to the action on Figure 3DThe operation on the confirmation icon 318A of c in the figure triggers the electronic device to display the following Figure 3D In the embodiment of the present application, Figure 3D The operation of creating a schedule shown in b and c can also be referred to as a fourth operation.

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

[0160] Optionally, when the user creates a calendar application such as Figure 3D After the birthday reminder schedule is displayed, if some shopping applications, such as the aforementioned application A, have the permission to read all calendars, then application A can obtain the birthday reminder schedule and recommend birthday gifts for the user on the interface of application A. For details, refer to Figure 3E The scene shown.

[0161] Figure 3E The following example illustrates a scenario in which application A recommends a corresponding service based on a schedule read from a calendar application.

[0162] like Figure 3E As shown in a of FIG, when the user creates a schedule for his mother's birthday through the calendar application at 08:08. Figure 3E As shown in b, later, for example, at 09:30, the user opens application A, and the interface of application A will display product push information such as "Birthday Gift List" to recommend the user to buy birthday gifts. Figure 3E The interface of application A shown in b can also be called the second interface.

[0163] Figure 3F The operation method of creating a schedule in application C is exemplified.

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

[0165] Users can use Figure 3F The operation on the control 318C in a creates a schedule in the application C. For example, in response to the operation on the control 318C, the application C displays a window 413 for creating a schedule. Figure 3F b in.

[0166] Figure 3F b in FIG. 4 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.

[0167] The user can input the title of the to-do schedule by operating the keyboard, and the corresponding electronic device can display the corresponding schedule title according to the operation of the user on the keyboard, for example, display Figure 3F After entering the title of the schedule, the user can click control 413B to complete the creation of this schedule. For example, in response to the operation on control 413B, the user successfully creates a schedule of "project meeting" in application C, and the information of the schedule is also displayed in application C. For details, please refer to Figure 3F The contents shown in d.

[0168] Figure 3F d in the figure is still the interface of application C. At this time, window 411 is displayed in the interface. Window 411 displays not only schedule information 411A corresponding to "application 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 mother's birthday created directly in the calendar application by the user, but also schedule information 411D corresponding to the project meeting created directly in application C by the user this time.

[0169] Optional, the aforementioned Figure 3F The schedule information corresponding to the project meeting created by the user in application C can be stored in the data of application C. If application C only has the permission to read the calendar but not the permission to write the calendar (create / modify / delete the calendar 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. For details, see Figure 3G .

[0170] 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.

[0171] like Figure 3GAs shown, taking the example that application C does not have the permission to write to the calendar, or application C has the permission to write to the calendar but requires that the schedule of application C not be synchronized in the calendar application, the schedule information of the project meeting created by the user is only provided by application C, and the calendar application does not provide the schedule information of the project meeting.

[0172] like Figure 3H As shown, taking the example that application C has the permission to write to the calendar and requires the schedule of application C to be synchronized in the calendar application, the schedule information of the project meeting created by the user is not only provided by application C, but also synchronously provided in the calendar application 317E.

[0173] After the user grants App C the right to access all calendars, if you want to change App C's permission to access the calendar app, you can modify it in Settings. For how to modify App C's permission to access the calendar app in Settings, please refer to the previous article Figure 2A-2F Four exemplary methods are shown below. Fig. 3I Only one way to introduce it.

[0174] Fig. 3I The following is a schematic diagram of an operation interface for changing the permission of application C to access the calendar application.

[0175] Fig. 3I 213A and 213B. The user can select the permission column 213A or the application column 213B to trigger the electronic device to display a series of options corresponding to the selected column in the permission management details page. Fig. 3I As shown in a, when the application column 213B is selected, a series of application options are displayed in the permission management details page, including options corresponding to application A, options corresponding to application B, options corresponding to application C, options corresponding to application D, and so on.

[0176] The user can also trigger the electronic device to display the application permission details page corresponding to the selected application by selecting an option corresponding to any application. Fig. 3I The operation on the option corresponding to application C in a triggers the electronic device to open the permission details page of application C. For details, see Fig. 3I As shown in b.

[0177] Fig. 3Ib is the permission details page of application C, which includes multiple permission setting options, such as permission setting option 214 for calendar, permission setting options for location information, permission setting options for camera, permission setting options for microphone, etc. Each permission option also displays the permission level currently used by the permission. For example, permission setting option 214 for calendar displays "Allow access to all records", which means that the current calendar permission owned by application C is that application C can access all schedules created by applications in the calendar application.

[0178] The user can further manage the calendar permissions owned by application A by clicking the permission setting option 214 corresponding to the calendar. Fig. 3I The operation on the permission setting option 214 corresponding to the calendar in b triggers the electronic device to pop up a window for setting the permission level of application C to access the calendar application, see Fig. 3I In the embodiment of the present application, Fig. 3I The interface shown in b can also be called the first interface, which acts on Fig. 3I The operation on the permission setting option 214 corresponding to the calendar shown in b may also be referred to as a first operation.

[0179] Fig. 3I The c is still the permission details page of application C, and the permission details page of application C now displays window 412. The window 412 contains prompt information for stating the operations involved in application C's access to the calendar, such as allowing application C to read the calendar and create / modify / delete calendars, and also contains options corresponding to multiple permission levels for accessing the calendar, such as "only access calendars created by this application", "allow access to all calendars" and "forbid". Among them, the "allow access to all calendars" option is selected, indicating that the current permission for application C to access the calendar application is "allow access to all calendars".

[0180] The user can change the permission level of application C to access the calendar application from "Allow access to all calendars" to "Only access calendars created by this application" by clicking the "Only access calendars created by this application" option. Fig. 3I The operation on "Only access the calendar created by this application" in c triggers the electronic device to change the permission level of application C to access the calendar application to "Only access the calendar created by this application", and makes the schedule information in the calendar application previously obtained by application C cleared, see Fig. 3I In the embodiment of the present application, Fig. 3IThe window 412 displayed in c in can also be called the first window, the application C contained in the window can also be called the name of the first application, the prompt information for reading calendars and creating / modifying / deleting calendars contained in window 412 can also be called access type information, the "allow access to all calendars" contained in window 412 can also be called the first permission, the option of "allow access to all calendars" can also be called the first option, the "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.

[0181] akin, Fig. 3I In c, only the example of application C applying for both the permission to read the calendar and the permission to write the calendar is used 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 above Fig. 3I After the operation of the permission setting option 214 corresponding to the calendar shown in b, the management window for managing the permission of application C to access the calendar that pops up on the electronic device may be: Figure 1 For details of the window shown in a-2, please refer to the above Figure 1 Correspondingly, the above action is Fig. 3I In c, only the operations on the corresponding options of the calendar created by this application are accessed, corresponding to the operations on Figure 1 Operations on the corresponding options in a-2 are prohibited.

[0182] Fig. 3I D is the interface of application C (also called the fourth interface), which is Figure 3E The interface shown in FIG. 4 is different from that, since application C cannot read the schedule in the calendar application, the schedule information in the calendar application is no longer displayed in the interface at this time, and only the schedule information 411D corresponding to the project meeting created by application C itself is displayed.

[0183] It is understandable that the operation method for managing the permission of each application to access the calendar application in the settings described in the above UI embodiment is only an example, and the operation method for managing the permission of the application to access the calendar application in the application is also only an example and should not constitute a limitation to this application. Figure 2A-2FThe description is more complex or simple, and this application does not limit this. For example, in different applications, the operation of triggering the management application to access the calendar application is different. For example, the triggering operation in the shopping application (application A) described above is to subscribe to the 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 not list all applications one by one.

[0184] Next, combine Figure 4 The permission management method provided by this application is introduced, and the method comprises the following steps:

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

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

[0187] In a possible implementation, the triggering operation may be an 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.

[0188] In another possible implementation, the trigger operation may be an operation of enabling a calendar reminder function provided in the application during the running of the application. Figure 3A The operation of subscribing to calendar reminders in application A described above, as well as Figure 3B The operation of reserving programs described in Figure 3C In the example above, when the application is another type of application, the triggering operation may be in other forms, which will not be described in detail here.

[0189] In S41, accessing the calendar application may refer to performing a read operation on a schedule in the calendar application, or may refer to 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.

[0190] S42, the electronic device detects whether the application has native calendar access rights.

[0191] Native calendar access permissions specifically refer to native read calendar permissions and native write calendar permissions. Native calendar access permissions are coarse permissions, and only include two permission levels, namely "allow access to calendar" and "forbid access". When the native calendar access permission of an app is "allow access to calendar", it means that the app has native access permissions and can access all calendars. When the native calendar access permission of an app is "forbid access", it means that the app does not have native access permissions and cannot access any calendar.

[0192] Specifically, the electronic device can pre-set the native calendar access rights of the installed applications. When an application requests to access 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, the subsequent S43 is continued to be executed, which is used to further refine the determination of the permission level of the calendar access rights of the application.

[0193] The method for the electronic device to set the native calendar access permission of the application includes the following methods:

[0194] In a possible implementation, the electronic device may default that all applications have native calendar access permissions, or do not have native calendar access permissions;

[0195] 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 for managing 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 do not elaborate on this one by one.

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

[0197] Specifically, this application makes a fine-grained distinction in the permission levels for applications to access calendar applications, that is, further divides the permission to access calendars into: allowing access to all calendars, and only allowing access to calendars created by this application. Therefore, when the electronic device detects in S42 that the application has native calendar access rights, it is necessary to further determine the permission level of the application. When the permission level is to allow access to all calendars, the subsequent S44-1 is continued to be executed. When the permission level is to allow access to only calendars created by this application, the procedure S44-2 is continued to be executed.

[0198] The electronic device may pre-set a specific level corresponding to the calendar access permission of the installed application, and the setting method includes the following methods:

[0199] 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 the application itself, or 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 the application itself.

[0200] In another possible implementation, the user can set the permission level of each application to access the calendar application in the settings of the electronic device, for example, refer to the above Figure 2A-2F Four setting methods are introduced.

[0201] In another possible implementation, the electronic device may pop up a prompt message for requesting calendar access permission, so that the user can manage the specific permission level of the application to access the calendar application through the prompt message, for example, refer to the above Figure 3A-3C Three setting methods are introduced.

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

[0203] 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.

[0204] For example, when the application requests to access the calendar application in S41 specifically includes reading the calendar, then in S44-1, the electronic device may return all schedules in the calendar to the application. For details, please refer to the above text. Figure 3C , Figure 3F The result display of the introduced application C accessing all calendars; when the application requests access to the calendar application in S41 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 schedules in the calendar.

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

[0206] 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.

[0207] For example, when the application requests to access the calendar application in S41 specifically includes reading the calendar, then in S44-2, the electronic device returns only the schedule created by the application in the calendar to the application. For details, please refer to the above text. Fig. 3IThe result of application C accessing the schedule created by this application in the calendar introduced in d is displayed; when the application requests access to the calendar application in S41 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.

[0208] 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 leakage of user privacy.

[0209] Next, combine Figure 5 The specific implementation of the permission management method provided by this application is introduced in detail, which involves a calendar application, a third-party application, a calendar provider (Calendar provider) and an application operation permission management service (Application Operations Service, AppOpsService).

[0210] Among them, the introduction of calendar applications and third-party applications can be specifically referred to the description in S41 above, which will not be repeated here.

[0211] Calendarprovider is a module included in the content provider in the application framework layer of the electronic device, which is equivalent to a database responsible for storing calendar data (i.e., schedules) and provides data access methods, such as read and write methods, and write methods include create / delete / modify, etc. Applications can access schedules in the database through the Calendar Provider API.

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

[0213] Among them, AppOpsService 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: prohibiting access and allowing access. The allowing access means allowing access to all calendars.

[0214] 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.

[0215] Figure 5The specific implementation of the permission management method shown includes the following steps:

[0216] Phase 1 (S51-S53): Setting the permission level for third-party applications to access the calendar application. In addition, the permission level for system applications to access the calendar application can also be set. Since the permission level for third-party applications to access the calendar application is strongly related to the user's privacy and security, this application focuses on the management and control of the calendar access rights of third-party applications.

[0217] 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.

[0218] 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:

[0219] (1) Set the calendar access permissions for third-party apps in Settings. For example, Figure 2A-2B In the scenario introduced, it acts on Figure 2B In e, the option to access only the calendar created by this application is operated; for example, Figure 2C-Figure 2D In the scenario introduced, it acts on Figure 2D In e, only the operation of accessing the calendar created by this application is performed; for example, Figure 2E In the scenario introduced, it acts on Figure 2E b in the immediate optimization control 218A operation; for example, the previous Figure 2F In the scenario introduced, it acts on Figure 2F The option to access only calendars created by this app is available in D.

[0220] (2) Setting the calendar access permission of the application in the third-party application. For example, when the third-party application is application A, the operation of setting the calendar access permission of the application in application A can refer to the above. Figure 3A The scenario shown acts on Figure 3A For example, when the third-party application is application B, the operation of setting the calendar access permission of this application in application B can refer to the previous article. Figure 3B The scenario shown acts on Figure 3B For example, when the third-party application is application C, the operation of setting the calendar access permission of this application in application C can refer to the previous article. Figure 3C The scenario shown acts on Figure 3CFor the operation of the option of only accessing the calendar created by this application on c, for different third-party applications, the specific operations of setting the calendar access permission level of the application are different, and this application will no longer enumerate them one by one for all applications.

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

[0222] Specifically, after the electronic device receives an operation for setting the permission for a 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 based on the operation. AppOpsService can refresh and store the permission level of each application to access the calendar, so that when the third-party application subsequently accesses the calendar application, AppOpsService can execute according to the latest permission level of the third-party application.

[0223] For example, taking the permission level of application C as an example, when in S51, the operation received by the system UI is the above Fig. 3I In the case where the permission level of application C to access the calendar is changed from "allow access to all calendars" to "only access calendars created by this application" as shown in c. Then in S52, the permission level of application C to access the calendar sent by system UI to AppOpsService is "only access calendars created by this application", and the corresponding 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".

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

[0225] 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.

[0226] The information indicating the permission level of the third-party application includes: information indicating the permission level of the third-party application to read the calendar, 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 the calendar, or to create / modify / delete calendars can 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 the calendar is to allow access to all calendars, and if the refined switch is off, it means that the permission level of the third-party application to read the calendar is to allow access to only the calendar created by the application.

[0227] 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. Here, the third-party application is used to create a schedule in the calendar application for exemplary purposes and should not constitute a limitation on this application.

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

[0229] Specifically, the operation of receiving the third-party application of the electronic device to write the schedule of the third-party application into the calendar application includes: for example, the aforementioned Figure 3A The operation of subscribing to a calendar reminder in application A as described in c can trigger application A to request to write the schedule information of the sign-in reminder to the database of the calendar application, namely, the Calendar provider; for example, the aforementioned Figure 3B The operation of booking a live video in application B as described in b can trigger application B to request to write the schedule information of reminding to watch the live video to the database of the calendar application, that is, Calendar provider. For example, Figure 3F The operation of creating a schedule in application C introduced in c can trigger application C to request to write schedule information of reminding to watch the live video to the database of the calendar application, namely Calendarprovider.

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

[0231] 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.

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

[0233] Specifically, after the Calendar provider of the electronic device receives the request for writing the schedule of the third-party application sent by the third-party application, it continues to request AppOpsService to verify the permission level of the application to determine whether to allow writing the schedule of the third-party application into the Calendar provider.

[0234] 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.

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

[0236] 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.

[0237] 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.

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

[0239] It is understandable that stage 2 is only introduced by taking the calendar application to create a schedule as an example. In addition, the electronic device can also create a calendar in other ways, which will not be described in detail here, but only briefly described:

[0240] For example, create a schedule in the calendar application through application A, application B, application C or other applications. Specifically, create a schedule in the calendar application through application A, that is, Figure 3A After subscribing to the calendar application reminder service as described above, application A will create a schedule in the calendar application to remind the user to sign in. Specifically, application B creates a schedule in the calendar application, as described in the previous section. Figure 3B After a certain interface is reserved, application B will create a task in the calendar application to remind the user to watch the program. Here, we will not list the ways in which each application creates a schedule in the calendar application one by one.

[0241] Refer to Table 1, which exemplarily shows the relevant information of the schedule stored by the Calendar provider provided by the present application.

[0242] Table 1

[0243] Application (label) Schedule Record Calendar App Mom's birthday Application A Sign in to receive red envelope Application B Live video reminder Application C Project Meeting

[0244] 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: the location and time of the schedule, the package name (pkgName) corresponding to the schedule, and other information, which is not limited in this embodiment of the present application.

[0245] 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.

[0246] Phase 3 (S59-S64): Perform fine-grained control according to the permission level of the third-party application to access the calendar application. Here, we only take the third-party application request to read the calendar as an example to introduce in detail. The implementation of fine-grained control of the third-party application request to write the calendar is similar to the fine-grained management of reading the calendar, so we will not go into details here.

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

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

[0249] (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 to obtain corresponding permissions, including the permission to read the schedule.

[0250] (2) Operations used to enable calendar reminder functions provided by the third-party application. Figure 3A The operation of subscribing to calendar reminders in application A described above, as well as Figure 3B When the application is another type of application, the operation for reading the schedule can also be in other forms, which will not be described in detail here.

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

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

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

[0254] 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.

[0255] 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.

[0256] 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.

[0257] 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 third-party application C returned by AppOpsService to the Calendar provider includes information indicating that only reading of schedules created by this application is allowed.

[0258] S63, the Calendar provider of the electronic device obtains the schedule created by the application C according to the schedule tag.

[0259] Specifically, after receiving the instruction returned by AppOpsService that only the information of the schedule created by the 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 label of the schedule.

[0260] S64, the Calendar provider of the electronic device returns to the application C only the schedules in the Calendar provider that belong to the application C.

[0261] Specifically, if the calendar provider stores the schedule created by application C, the Calendar provider returns only the schedule created by application C in the calendar to application C. If the Calendar provider does not store the schedule created by application C, no other schedule will be returned. Figure 3F D and Fig. 3I As shown in the interface of application C in Figure d, when the permission of application C includes permission to read all calendars, application C can display the following Figure 3F The schedule information of application A, application B and calendar application included in d, when the permission of application C is modified to allow reading the calendar created by this application, application C displays the following Fig. 3I The d interface 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.

[0262] 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 leakage of user privacy.

[0263] As well as the introduction to the aforementioned UI implementation example 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.

[0264] 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 (UMPC), netbooks, as well as cellular phones, personal digital assistants (PDA), augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, wearable devices, vehicle-mounted devices, smart home devices and / or smart city devices, etc.

[0265] refer to Figure 6 , Figure 6 A schematic diagram of the hardware architecture of an electronic device is shown.

[0266] 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.

[0267] It is to be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0268] 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 processor (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), etc. Different processing units may be independent devices or integrated into one or more processors.

[0269] The controller can be the nerve center and command center of the electronic device. The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of fetching and executing instructions.

[0270] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0271] In the embodiment of the present application, the processor 110 is used to control the corresponding software and hardware modules to execute the above Figure 4-Figure 5 The methods introduced can be combined with the previous Figure 4-Figure 5 The relevant description is not repeated here.

[0272] In some embodiments, the processor 110 may include one or more interfaces. The interface 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, etc.

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

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

[0275] It is understandable that the interface connection relationship between the modules illustrated in the embodiments of the present application is only a schematic illustration 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 in the above embodiments, or a combination of multiple interface connection methods.

[0276] The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of an electronic device. While the charging management module 140 is charging the battery 142, it may also power the electronic device through the power management module 141.

[0277] 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 supplies power to the processor 110, the internal memory 121, the external memory, the display screen 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 number, battery health status (leakage, impedance), etc. 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.

[0278] 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.

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

[0280] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to 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.

[0281] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent 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 the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a 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.

[0282] The wireless communication module 160 can provide wireless communication solutions 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., which are applied to electronic devices. The wireless communication module 160 can be one or more devices integrating 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, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0283] In some embodiments, the antenna 1 of the electronic device is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device can communicate with the network and other devices through 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, etc. 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).

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

[0285] The display screen 194 is used to display images, videos, etc. The 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), miniLED, microLed, micro-oled, quantum dot light emitting diodes (QLED), etc. In some embodiments, the electronic device may include 1 or N display screens 194, where N is a positive integer greater than 1.

[0286] In the embodiment of the present application, the electronic device can display, for example, the following information provided in the above UI embodiment through the display screen 194: Figure 1 , Figure 2A-2F and Figure 3A-3H The user interface shown and so on will not be described in detail here.

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

[0288] ISP is used to process the data fed back by camera 193. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to ISP for processing and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on the noise and brightness of the image. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, ISP can be set in camera 193.

[0289] 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 optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted 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.

[0290] Digital signal processors are used to process digital signals. In addition to processing digital image signals, they can also process other digital signals. For example, when an electronic device selects a frequency point, a digital signal processor is used to perform Fourier transform on the frequency point energy.

[0291] Video codecs are used to compress or decompress digital videos. Electronic devices can support one or more video codecs. In this way, electronic devices can play or record videos in multiple coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0292] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and continuously self-learn. NPU can realize applications such as intelligent cognition of electronic devices, such as image recognition, face recognition, voice recognition, text understanding, etc.

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

[0294] 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 DDR SDRAM is generally referred to as DDR5 SDRAM), etc.

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

[0296] 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 unit potential level; universal flash storage (UFS), embedded multi media card (eMMC), etc. according to the storage specification.

[0297] 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.

[0298] 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 .

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

[0300] 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 described here.

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

[0302] 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 arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.

[0303] Speaker 170A, also called "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 speaker 170A. In an embodiment of the present application, the electronic device can choose to use 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.

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

[0305] Microphone 170C, also called "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 the collection of sound signals, noise reduction, identification of sound sources, and directional recording function, etc.

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

[0307] The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be set on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device determines the intensity of the pressure based on the change in capacitance. When a touch operation acts on the display screen 194, the electronic device detects the touch operation intensity according to the pressure sensor 180A. The electronic device can also calculate the touch position according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

[0308] The touch sensor 180B is also called a "touch panel". The touch sensor 180B can be arranged on the display screen 194, and the touch sensor 180B and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor 180B is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180B can also be arranged on the surface of the electronic device, which is different from the position of the display screen 194.

[0309] 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.

[0310] In the 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 three axes of X, Y, and Z on the acceleration sensor 180C.

[0311] The key 190 includes a power key, a volume key, etc. The key 190 can be a mechanical key or a touch key. The electronic device can receive key input and generate key signal input related to user settings and function control of the electronic device.

[0312] The software system of the electronic device may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to exemplify the software structure of the electronic device.

[0313] Figure 7 A software structure block diagram of the electronic device according to an embodiment of the present application.

[0314] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.

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

[0316] like Figure 7 As shown, the application package may include a calendar application, application A, application B, application C, and settings applications.

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

[0318] Among them, the calendar application can be used to create schedules. Application A, application B, and application C can create schedules through the calendar application. Settings can be used to provide options for setting the permission level of each application to access the calendar application.

[0319] like Figure 7 As shown, the application framework layer may include a content provider, an activity management system (Activity manager service, AMS), and some window managers, view systems, phone managers, resource managers, notification managers, etc. that are not shown.

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

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

[0322] AMS is one of the important services in the system services of electronic devices. It is mainly responsible for the startup, switching, scheduling of various components in the system and the management and scheduling of application processes. Its responsibilities are similar to the process management and scheduling modules in the operating system.

[0323] In particular, AMS includes AppOpsService, which is a service for managing the operating permissions of applications. AppOpsService 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. The allowing access means allowing access to all calendars.

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

[0325] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

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

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

[0328] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0329] Android runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

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

[0331] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0332] The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

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

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

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

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

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

[0338] It should be understood that each step in the above method embodiment provided by the present application can be completed by an integrated logic circuit of hardware in a processor or by instructions in the form of software. The method steps disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware processor, or by a combination of hardware and software modules in a processor.

[0339] The present application also provides an electronic device, which may include: a memory and a processor, wherein the memory may be used to store a computer program; and 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.

[0340] 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.

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

[0342] The chip system may be composed of the chip, or may include the chip and other discrete devices.

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

[0344] Optionally, the memory in the chip system may also be one or more. The memory may be integrated with the processor or may be separately arranged with the processor, which is not limited in the embodiments of the present application. Exemplarily, 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 may be arranged on different chips respectively. The embodiments of the present application do not specifically limit the type of memory and the arrangement of the memory and the processor.

[0345] Exemplarily, the chip system can 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.

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

[0347] The present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores 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.

[0348] The various implementation modes of the present application can be combined arbitrarily to achieve different technical effects.

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

[0350] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

[0351] In short, the above description is only an embodiment of the technical solution of the present invention, and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present invention shall be included in the protection scope 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