Application management method and wearable device

Abstract

The embodiment of the application discloses an application management method and a wearable device, and relates to the technical field of intelligent devices. The method comprises the following steps: displaying a first interface in a first application; in response to a first operation of triggering a first function in the first application on the first interface, determining a first permission associated with the first function; searching for a management state of the first permission in a permission management state of the first application; in the case that the management state of the first permission is a closed state, displaying a second interface, and the second interface comprises an opening option corresponding to the first permission; and in response to a second operation on the opening option, displaying a third interface, and the third interface comprises an operation interface of the first function. By adopting the scheme, the personal information of a user in the wearable device can be collected without the user performing permission authorization on the first application, so that the personal information of the user in the wearable device is effectively protected.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of intelligent devices, and in particular to an application management method and a wearable device. BACKGROUND

[0002] Nowadays, wearable devices such as smart watches and smart bands have become indispensable tools in people's daily life. By installing applications (APPs) in wearable devices, the functions of the devices can be improved. However, some APPs in wearable devices may collect and use personal information of users without the users' knowledge, for example, some APPs automatically use the microphone of the wearable device to collect voice information or automatically read the setting location information in the wearable device during work. In summary, after some APPs are installed in wearable devices, the APPs can randomly collect personal information of users in the wearable devices, and there is a lack of effective protection measures for personal information of users in wearable devices. SUMMARY

[0003] Embodiments of the present application provide an application management method and a wearable device, which can avoid applications in the wearable device from collecting personal information of users in the wearable device without the users' permission, thereby effectively protecting personal information of users in the wearable device.

[0004] To achieve the above object, embodiments of the present application adopt the following technical solutions:

[0005] In a first aspect, an application management method is provided, which is applied to a wearable device. The method comprises: displaying a first interface in a first application; in response to a first operation that triggers a first function in the first application on the first interface, determining a first permission associated with the first function; then, searching for a management state of the first permission in a permission management state of the first application, the permission management state of the first application being a default closed state when saved for the first time; in the case where the management state of the first permission is a closed state, displaying a second interface, the second interface comprising an opening option corresponding to the first permission; in response to a second operation on the opening option, displaying a third interface, the third interface comprising an operation interface of the first function.

[0006] It can be understood that when the wearable device first saves the permission management state of the first application, the user does not authorize any permission of the first application, and the permission management state of the first application saved by the wearable device for the first time is in a closed state by default. Further, when the user triggers the first function in the first application, if the management state of the first permission associated with the first function in the permission management state of the first application is in a closed state, the second interface is displayed to request the user to authorize the first permission of the first application. The wearable device responds to the second operation of the user on the opening option in the second interface, indicating that the user authorizes the first permission of the first application, and then normally displays the operation interface of the first function. When the operation interface of the first function is normally displayed, the first application can collect the personal information of the user in the wearable device through the first permission associated with the first function. Since the user has authorized the first permission of the first application, the first application collects the personal information of the user in the wearable device through the first permission with the consent of the user.

[0007] In summary, the present solution avoids the situation that an application collects the personal information of the user in the wearable device through a permission without the authorization of the user. Thus, the personal information of the user in the wearable device is effectively protected.

[0008] In combination with the first aspect, in a possible implementation, the second interface further includes a closing option corresponding to the first permission. After displaying the second interface, the method further includes: in response to a third operation on the closing option, displaying the first interface.

[0009] It can be understood that when the wearable device displays the second interface to request the user to authorize the first permission of the first application, the user can also select not to authorize the first permission of the first application by operating the closing option in the second interface, so as to avoid the first application from collecting the personal information of the user in the wearable device through the first permission.

[0010] In combination with the first aspect, in another possible implementation, the method further includes: while displaying the third interface, performing a first behavior allowed by the first permission; generating and saving first behavior information, the first behavior information being used to record the use information of the first application on the first permission.

[0011] It can be understood that after the wearable device determines that the user authorizes the first permission of the first application, the wearable device normally displays the third interface and performs the first behavior allowed by the first permission. The third interface can include the operation interface of the first function. The wearable device can collect some personal information of the user during the execution of the first behavior, and then update the operation interface of the first function based on the personal information of the user collected during the execution of the first behavior.

[0012] In addition, the wearable device can save the first behavior information, so that the user can view the use information of the first application for the first permission.

[0013] With reference to the first aspect, in a possible implementation, the method further includes: in response to the second operation, updating the management state of the first permission in the permission management state of the first application to an open state.

[0014] It can be understood that after the wearable device determines that the user authorizes the first application for the first permission, the wearable device updates the management state of the first permission in the permission management state of the first application to an open state. In this way, the first application can not need to request authorization of the user when the first application needs to use the first permission next time, and the user is avoided from repeatedly authorizing the same application for the same permission.

[0015] With reference to the first aspect, in a possible implementation, before displaying the first interface in the first application, the method further includes: displaying a fourth interface; the fourth interface includes a desktop interface of the wearable device. Receiving a fourth operation of triggering the first application on the fourth interface; in response to the fourth operation, in a case where the management state of the first application declaration is a cancel state, displaying a fifth interface, wherein the management state of the first application declaration is a cancel state by default when the first application declaration is saved for the first time, and the fifth interface includes the first application declaration and a confirmation option corresponding to the first application declaration. In response to a fifth operation of the confirmation option, updating the management state of the first application declaration to a confirmation state, and displaying a sixth interface, and the sixth interface includes a home interface of the first application.

[0016] It can be understood that when the wearable device saves the first application declaration of the first application for the first time, the user does not confirm the first application declaration of the first application, and thus the management state of the first application declaration saved for the first time is a cancel state by default. Further, when the user triggers the first application, if the management state of the first application declaration is a cancel state, the fifth interface is displayed to request the user to confirm the first application declaration. In response to a fifth operation of a confirmation option in the fifth interface by the user, it indicates that the user confirms the first application declaration, and thus the home interface of the first application is normally displayed. By using this solution, the first application can be started without the user confirming the first application declaration of the first application.

[0017] With reference to the first aspect, in a possible implementation, the fifth interface further includes a cancel option corresponding to the first application declaration. After the fifth interface is displayed, the method further includes: in response to a sixth operation of the cancel option, displaying the fourth interface.

[0018] It can be understood that when the wearable device displays the fifth interface to request the user to confirm the first application declaration, the user can also select not to determine the first application declaration by operating the cancel option in the fifth interface.

[0019] With reference to the first aspect, in a possible implementation, the method further includes: in response to the seventh operation, obtaining an installation package of the first application when the first application is not installed, and installing the first application by using the installation package of the first application; parsing the permission application file and the application declaration file from the installation package of the first application, the permission application file including at least one permission required by the first application, and the application declaration file including the first application declaration; after successfully installing the first application, setting the management state of the first application declaration to the cancel state based on the application declaration file, and saving the management state of the first application declaration; setting the permission management state of the first application to the close state based on the permission application file, and saving the permission management state of the first application, the permission management state of the first application including the management state of each of the at least one permission.

[0020] It can be understood that the wearable device can obtain the permission application file and the application declaration file during the process of installing the first application; then, create the management state of the first application declaration based on the application declaration file, and create the permission management state of the first application based on the permission application file. The management state of the first application declaration is used to determine whether the user confirms the first application declaration, so as to ensure that the first application is started when the user confirms the first application declaration. The permission management state of the first application is used to determine whether the user authorizes the first application to use the permission, so as to ensure that the behavior allowed by the permission is executed when the user authorizes the first application to use the permission. In summary, the present solution realizes moving the first application when the user confirms and executing the behavior allowed by the permission when the user authorizes, by creating the management state of the first application declaration and the permission management state of the first application, thereby protecting the personal information of the user in the wearable device. In addition, the process of creating the management state of the first application declaration and the permission management state of the first application is simple, and the computing resources consumed are less, so that the present solution has less impact on the normal work of the wearable device.

[0021] With reference to the first aspect, in a possible implementation, the method further includes: in response to the seventh operation, obtaining an installation package of the first application when the first application is not installed, and installing the first application by using the installation package of the first application; parsing the permission application file and the application declaration file from the installation package of the first application, the permission application file including at least one permission required by the first application, and the application declaration file including the first application declaration; after successfully installing the first application, setting the management state of the first application declaration to the cancel state based on the application declaration file, and saving the management state of the first application declaration; setting the permission management state of the first application to the close state based on the permission application file, and saving the permission management state of the first application, the permission management state of the first application including the management state of each of the at least one permission.

[0022] The embodiment describes that the wearable device can first create a permission white list corresponding to the first application, and then create a permission management state of the first application. The permission white list and the permission management state of the first application are used to jointly manage the use of the permission by the first application.

[0023] With reference to the first aspect, in a possible implementation, the method further includes: in response to the first operation, displaying a first prompt information and a first interface in a case that the wearable device does not save the permission management state of the first application. The first prompt information is used to prompt that the first application does not apply for the first permission.

[0024] It can be understood that if the wearable device cannot normally start the first function triggered by the first operation in a case that the wearable device does not save the permission management state of the first application, the first prompt information can be displayed to inform the user of the reason why the first function cannot be normally started. Thus, the use experience of the user that the wearable device does not respond to the first operation can be avoided due to that the wearable device does not display the operation interface of the first function after the user inputs the first operation, but displays the first interface.

[0025] With reference to the first aspect, in a possible implementation, the operating system of the wearable device is a real-time operating system (RTOS), and the first application belongs to a JS application.

[0026] The embodiment describes an example of the operating system of the wearable device, and an example of the first application in the wearable device.

[0027] With reference to the first aspect, in a possible implementation, the method further includes: displaying a seventh interface, the seventh interface including a first setting option; in response to an eighth operation on the first setting option, displaying an eighth interface, the eighth interface including a behavior record option; and in response to a ninth operation on the behavior record option, displaying a ninth interface, the ninth interface including at least one behavior information.

[0028] It can be understood that after each application in the wearable device performs a behavior allowed by a permission, corresponding behavior information (for example, the first behavior information described above) can be saved locally to record the use information of the application on the permission. The wearable device provides a query entrance through the first setting option in the seventh interface, so that the user can browse all the saved behavior information.

[0029] With reference to the first aspect, in a possible implementation form of the first aspect, the seventh interface comprises a second setting option. After displaying the seventh interface, the method further comprises: in response to a tenth operation on the second setting option, displaying a tenth interface, the tenth interface comprising a declaration switch corresponding to each of the at least one application in the wearable device, the declaration switch corresponding to each of the at least one application being used to modify a management state of the application declaration of each of the at least one application, the at least one application comprising the first application.

[0030] It can be understood that, in addition to displaying the confirmation option and the cancel option corresponding to the first application declaration before the user triggers the first application to enable the user to update the management state of the first application declaration of the first application, the wearable device can also provide other setting entrances of the application declaration to enable the user to update the management state of the first application declaration of the first application through the other setting entrances of the application declaration. The other setting entrances of the application declaration can comprise the second setting option in the seventh interface to enable the user to enter the tenth interface through the second setting option and update the management state of the first application declaration of the first application through the declaration switch corresponding to the first application in the tenth interface.

[0031] With reference to the first aspect, in a possible implementation form of the first aspect, the seventh interface comprises a third setting option. After displaying the seventh interface, the method further comprises: in response to a tenth operation on the third setting option, displaying an eleventh interface, the eleventh interface comprising a fourth setting option corresponding to each of the at least one application in the wearable device, the at least one application comprising the first application; and in response to an eleventh operation on the fourth setting option corresponding to the first application, displaying a twelfth interface. The twelfth interface comprises a permission switch corresponding to each of the at least one permission required by the first application, the permission switch corresponding to each of the at least one permission being used to modify a management state of each of the at least one permission.

[0032] It can be understood that, in addition to displaying the start option and the stop option corresponding to the first permission when the first application needs to use the first permission to enable the user to update the management state of the first permission required by the first application, the wearable device can also provide other setting entrances of the permission to enable the user to update the management state of the first permission required by the first application through the other setting entrances of the permission. The other setting entrances of the permission can comprise the third setting option in the seventh interface to enable the user to enter the eleventh interface through the third setting option and enter the twelfth interface through the fourth setting option corresponding to the first application in the eleventh interface; and then update the management state of the first permission required by the first application through the permission switch corresponding to the at least one permission in the twelfth interface (including the permission switch corresponding to the first permission).

[0033] In a second aspect, a wearable device is provided, which includes a processor, a memory and a communication interface. The memory and the communication interface are coupled to the processor, and the memory is configured to store computer program code including computer instructions. When the processor executes the computer instructions, the wearable device is caused to perform the method according to any one of the first aspect.

[0034] In a third aspect, a computer readable storage medium is provided, which stores computer instructions. When the computer instructions are run on the wearable device, the wearable device is caused to perform the method according to any one of the first aspect.

[0035] In a fourth aspect, a computer program product is provided, which includes computer instructions. When the computer instructions are run on the wearable device, the wearable device is caused to perform the method according to any one of the first aspect.

[0036] In a fifth aspect, an apparatus (e.g., the apparatus can be a chip system) is provided, which includes a processor configured to support the wearable device to implement the method according to the first aspect. In a possible design, the apparatus further includes a memory configured to store necessary program instructions and data for the wearable device. When the apparatus is a chip system, the apparatus can be composed of a chip or include a chip and other discrete devices.

[0037] The technical effects brought by any one of the designs of the second aspect to the fifth aspect can be referred to the technical effects brought by the different designs of the first aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0038] Figure 1 FIG. 1 is a structural schematic diagram of a wearable device according to an embodiment of the present application;

[0039] Figure 2 FIG. 2 is a system structure diagram of a wearable device according to an embodiment of the present application;

[0040] Figure 3 FIG. 3 is a flowchart of an application management method according to an embodiment of the present application; Figure 1

[0041] Figure 4 FIG. 4 is an interface schematic diagram of a wearable device requesting a user to confirm an application declaration according to an embodiment of the present application;

[0042] Figure 5 FIG. 5 is an interface schematic diagram of modifying a management state of a first application declaration according to an embodiment of the present application;

[0043] Figure 6 ​(a)-(b) in FIG. 1 are interface schematic diagrams of a wearable device displaying a first application declaration according to an embodiment of the present application;

[0044] Figure 7 FIG. 2 is a flowchart of an application management method according to an embodiment of the present application; Figure 1 ;

[0045] Figure 8 (a)-(d) in FIG. 3 are interface schematic diagrams of a wearable device requesting a user to authorize a permission according to an embodiment of the present application;

[0046] Figure 9 (a)-(f) in FIG. 4 are interface schematic diagrams of a wearable device modifying a permission management state of a first application according to an embodiment of the present application;

[0047] Figure 10 (a)-(b) in FIG. 5 are interface schematic diagrams of a wearable device viewing behavior information according to an embodiment of the present application;

[0048] Figure 11 (a)-(e) in FIG. 6 are interface schematic diagrams of a wearable device uninstalling an application according to an embodiment of the present application;

[0049] Figure 12 (a)-(e) in FIG. 7 are interface schematic diagrams of a wearable device installing a system application according to an embodiment of the present application;

[0050] Figure 13 FIG. 8 is a flowchart of an application management method according to an embodiment of the present application; Figure 1 . DETAILED DESCRIPTION

[0051] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application.

[0052] The terms "first", "second" are only for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined with "first", "second" can explicitly or implicitly include one or more of the features. In the description of the present application, unless otherwise specified, the meaning of "a plurality of" is two or more.

[0053] At present, due to the fact that the RTOS system (or RTOS) provides functions relative to the Android system (or Android) and the iOS system (or iOS), the RTOS system is widely used in wearable devices. TMThere are limitations in general operating systems such as Android (a general operating system) and the like. Therefore, the RTOS system does not have some functions provided by the general operating system. For example, in order to protect the personal data of the user in the electronic device, Android TM The general operating system such as the Android system sets up a plurality of different permissions, such as the permission to read the location information, the permission to use the microphone, the permission to use the wireless network, and the like. After an APP is installed on the electronic device, the APP needs to apply to the general operating system to open some permissions. The electronic device can display a notification box to obtain the permission authorization of the APP from the user, so as to realize the reasonable control of the use permission of the APP. However, the RTOS system lacks the management of the application declaration of the APP and the management of the permission of the APP.

[0054] Due to the lack of the management of the application declaration of the APP and the management of the permission of the APP in the RTOS system, after an APP is installed on the wearable device using the RTOS system, the application declaration of the APP is accepted by default, and the APP is allowed to randomly collect the personal information of the user in the wearable device by default. For example, the APP can use the microphone of the wearable device to collect voice information, and can also read the setting location information in the wearable device, and the like. Thus, the personal information of the user in the wearable device is collected by the APP without the permission of the user.

[0055] Further, the wearable device also lacks the record of some sensitive behaviors of the APP. The sensitive behavior can refer to the behavior related to the collection of the personal information of the user, such as the behavior of the APP reading the location information of the wearable device, the behavior of the APP using the microphone of the wearable device to collect voice information, and the like.

[0056] In view of the above problems, the application embodiment provides an application management method. After each APP is installed on the wearable device, the management state of the application declaration of the APP can be initialized to a cancel state and saved, and at least one permission required by the APP can be initialized to a closed state and saved. Then, the wearable device determines the permission associated with the function in response to the operation of triggering any one of the functions in the APP. If the wearable device determines that the management state of the application declaration of the APP is the cancel state, and the management state of the permission associated with the function is the closed state, a declaration pop-up window can be displayed to obtain the confirmation of the application declaration of the APP from the user, and a permission pop-up window can be displayed to obtain the authorization of the permission associated with the function from the user. Further, the wearable device determines that the management state of the application declaration of the APP is the confirmation state, and the management state of the permission associated with the function is the open state, and then the function in the APP can be executed.

[0057] By adopting this solution, wearable devices prevent apps from collecting users' personal information on the wearable device without their permission by initializing the management status of an app's application declaration to a canceled state and the management status of at least one permission required by the app to a disabled state. This effectively protects the personal information of users on the wearable device.

[0058] In addition, while performing this function in the app, the wearable device can also save behavioral information (or sensitive behavioral information), which is used to record the app's usage information of permissions associated with this function.

[0059] This application provides an application management method that can be applied to wearable devices with displays, such as smart bracelets and smartwatches. This application does not limit the specific type of wearable device.

[0060] The following embodiments use a smartwatch as an example of a wearable device for illustrative purposes. Figure 1 A schematic diagram of the structure of a wearable device provided in an embodiment of this application is shown.

[0061] like Figure 1 As shown, the smartwatch 10 may include a processor 1, a memory 2, a microcontroller unit 3, a power management system 4, a power supply 5, a display screen 6, a touch panel 7, a housing, Bluetooth 8, a microphone 9, a temperature sensor, a photoplethysmography (PPG) sensor, and an acceleration transducer (ACC) sensor.

[0062] Although not shown, watch 10 may also include an ambient temperature sensor, an antenna, a wireless fidelity (Wi-Fi) module, a near-field communication (NFC) module, a global positioning system (GPS) module, a speaker, a gyroscope sensor, etc.

[0063] Processor 1 is used for system scheduling and to control the operation of modules such as display screen 6, touch screen 7, Bluetooth 8, and microphone 9.

[0064] The memory 2 is used to store software programs and data. The processor 1 executes various functions and data processing of the smartwatch 10 by running the software programs and data stored in the memory 2. For example, the memory 2 can store data collected by the PPG sensor, ACC sensor, and temperature sensor mentioned above.

[0065] The microcontroller unit 3 is used to control the sensors, perform calculations on the sensor data, and communicate with the processor 1. The sensors may include an ACC sensor C, a PPG sensor B, and a temperature sensor A, and may also include other sensors.

[0066] The power supply 5 is logically connected to the processor 1 through the power management system 4, thereby enabling the power management system 4 to manage functions such as charging, discharging, and power consumption.

[0067] The display screen 6 can be used to display information output by the smartwatch 10, such as the desktop interface of the smartwatch 10 or the interface of any app on the smartwatch 10.

[0068] The touchscreen 7, also known as the touch panel, collects touch operations performed by the user of the smartwatch 10. The touch panel 7 can cover the display screen 6. When the touch panel 7 detects a touch operation, it transmits the information to the processor 1 to determine the type of touch event. The processor 1 then provides corresponding visual output on the display screen 6 based on the type of touch event.

[0069] In some embodiments, the touch panel 7 may be disposed in the display screen 6. The display screen 6 including the touch panel 7 may be referred to as a touch screen. The following embodiments illustrate the use of a display screen including a touch panel as an example.

[0070] A temperature sensor is used to collect the user's skin temperature data. A PPG sensor is used to collect ambient light intensity data. An ACC sensor is used to collect the user's ACC data.

[0071] Microphone 9, also known as a microphone, converts the sound signal from the smartwatch 10 into an electrical signal, which is then received by the audio circuit and converted into audio data. The audio circuit can also convert the audio data into an electrical signal, which is then transmitted to the speaker and converted into a sound signal for output.

[0072] With Bluetooth 8, the smartwatch 10 can connect to other terminal devices via Bluetooth.

[0073] Understandably, the above Figure 1 The illustration shown is merely an example when the wearable device is in the form of a smartwatch. If the wearable device is in the form of a smart bracelet or other devices, the structure of the wearable device may include more... Figure 1 The fewer structures shown can also include more than Figure 2 The structures shown are not limited here.

[0074] Understandably, the implementation of wearable device functions requires not only hardware support but also a compatible software architecture. In some examples, refer to... Figure 2As shown, the software architecture of the wearable device provided in this application can include an application layer, a JavaScript (JS) application framework layer, a system framework layer (such as an operating system framework (OS framework)), and a system kernel layer (OS kernel), taking the system used by the wearable device as an RTOS system as an example.

[0075] In some embodiments, the application layer can include a series of APPs. The series of APPs can be divided into system APPs that are self-provided by the wearable device and third-party APPs that are downloaded into the wearable device by the user. For example, as shown, Figure 2 As shown, the system APPs can include a settings APP, a music APP, a short message APP, an exercise APP, and the like; and the third-party APPs can include a multimedia player APP and the like, without any limitation in the embodiments of this application.

[0076] In some embodiments, the JS application framework layer can include a JS data binding (JSData binding) module, a JS runtime (JS runtime) module, and a JS framework (JS framework) module. The JS data binding module can be used to provide a set of basic data binding capabilities using JS code, including a view model instance, a subject, and an observer. The JS runtime module can be used to support the parsing and execution of JS code. The JS framework module can be used to provide a JS application programming interface (API) and a component framework mechanism using C++ language. The JS framework module can include a user interface component adapter layer (UI component adapter layer) and an API adapter layer (API adapter layer); the UI component adapter layer can include basic components, animations, a rendering module (Render module), a router, a style manager, and a context object. The API adapter layer can include basic components, a rendering module (render module), and a style manager.

[0077] In some embodiments, the system framework layer can be used for communication between the JS application framework layer and the system kernel layer. The system framework layer can include a UI kit of an ability manager service (AMS) for application startup, a bundle manager service (BMS) for application update, and the like.

[0078] In some embodiments, the system kernel layer can be used for creation and communication of processes and threads. The system kernel layer can be an RTOS system.

[0079] In the embodiments of the present application, the JS framework module can further include a declaration management module, a permission management module, a behavior reporting module, and at least one behavior calling interface. For example, as shown in Figure 3 The at least one behavior calling interface can include an interface for making a phone call, a microphone interface, an interface for sending a short message, a Bluetooth interface, an interface for reading location information, and an interface for reading media and audio data, and the like.

[0080] The declaration management module can be used to save and manage the management state of the application declaration of each APP in the wearable device.

[0081] The permission management module can be used to save and manage the management state of all permissions required by each APP in the wearable device. Alternatively, the permission management module can be referred to as a sensitive behavior management module.

[0082] The behavior reporting module can be used to save the behavior information (or sensitive behavior information) of each APP in the wearable device. Alternatively, the behavior reporting capability can be referred to as a sensitive behavior log reporting module.

[0083] Each behavior calling interface in the at least one behavior calling interface can be used to control the display of a permission pop-up window of the permission corresponding to the behavior calling interface based on the management state of the permission. Alternatively, each behavior calling interface can also be used to report an event of an APP using the permission corresponding to the behavior calling interface to the behavior reporting module. Alternatively, each behavior calling interface can be an interface defined by a C++ programming language.

[0084] The following embodiments take a smart watch as an example of a wearable device to introduce the application management method provided in the embodiments of the present application.

[0085] Referring to Figure 3 As shown in the flowchart of the application management method provided in the embodiments of the present application. As shown in Figure 1 The method can include S301-S310.

[0086] S301, in response to a trigger of an installation operation of the first APP, the smart watch acquires an installation package of the first APP and installs the first APP by using the installation package of the first APP.

[0087] The smart watch can display an application installation interface in the case that the first APP is not installed. The application installation interface can include an installation option corresponding to the first APP. Then, the smart watch can receive a trigger of an installation operation of the first APP on the application installation interface. For example, the installation operation can be a click operation on the installation option. The smart watch acquires an installation package of the first APP in response to the installation operation. The smart watch can install the first APP by using the installation package of the first APP after acquiring the installation package of the first APP.

[0088] The first APP can be any APP that can be installed in the smart watch, such as a system APP or a third-party APP. For example, as shown in FIG. 1, the first APP can be an exercise APP. Figure 1

[0089] In some embodiments, the smart watch can include an application market APP, and the application installation interface can be an interface in the application market APP. Alternatively, the application installation interface can also be an interface in another APP, which is different from the application market APP in the smart watch.

[0090] In some embodiments, the operating system of the smart watch is an RTOS, and all APPs (including the first APP) in the smart watch can belong to JS (JavaScript) applications. JS applications generally refer to application programs written in JavaScript language and running on the smart watch.

[0091] S302, the smart watch parses a permission application file and an application declaration file from the installation package of the first APP, the permission application file including at least one permission required by the first APP, and the application declaration file including a first application declaration of the first APP.

[0092] The smart watch can parse the installation package of the first APP to obtain the permission application file and the application declaration file during installation of the first APP by using the installation package of the first APP. Optionally, the application declaration of the first APP can be referred to as the first application declaration.

[0093] In some embodiments, the application declaration (e.g., the first application declaration) of an APP is used to introduce details of the APP. For example, the application declaration of the APP can be used to introduce functions of the APP, data and information required to be collected by the APP, and permissions required by the APP, and the like. ​

[0094] In some embodiments, the permission application file can be a JSON (JavaScript object notation) file. The application declaration file can also be a JSON file.

[0095] In some embodiments, if the smart watch can parse the application declaration file from the installation package of the first APP, the smart watch can request the user to confirm the application declaration of the first APP when starting the first APP. If the smart watch cannot obtain the application declaration file from the installation package of the first APP, the smart watch cannot request the user to confirm the application declaration of the first APP. Further, in the case that the user does not confirm the application declaration of the first APP, the smart watch cannot normally start the first APP, and cannot run the first APP.

[0096] In some embodiments, if the smart watch can parse the permission application file from the installation package of the first APP, the smart watch can request the user to authorize the use of the one or more permissions in the permission application file by the first APP when the first APP needs to use the one or more permissions. If the smart watch cannot obtain the permission application file from the installation package of the first APP, the smart watch cannot request the user to authorize the use of the permission by the first APP when the first APP needs to use the permission in the smart watch. Further, in the case that the user does not authorize the use of the permission by the first APP, the first APP cannot use the permission.

[0097] For example, taking the first APP as a workout APP in the smart watch as an example, as shown in FIG. 1, the workout APP can include a permission application file and an application declaration file. Figure 1

[0098] It should be noted that, in addition to the workout APP in the smart watch including the permission application file and the application declaration file as shown in FIG. 1, the workout APP in the smart watch can also not include the permission application file and the application declaration file. Alternatively, the smart watch parses the permission application file and the application declaration file from the installation package of the workout APP, and can delete the permission application file and the application declaration file after using the permission application file and the application declaration file. Figure 4 S303, the declaration management module in the smart watch sets the management state of the first application declaration to a cancel state based on the application declaration file after successfully installing the first APP, and saves the management state of the first application declaration.

[0099]

[0100] ​​The declaration management module in the smart watch can generate and save the management state of the first application declaration based on the application declaration file after successfully installing the first APP. When the smart watch generates the management state of the first application declaration based on the application declaration file, the smart watch can set the management state of the first application declaration to the cancel state.

[0101] It can be understood that the user has not confirmed the application declaration of the first APP after the smart watch successfully installs the first APP, and therefore, the declaration management module can first set the management state of the first application declaration to the cancel state.

[0102] In some embodiments, the smart watch can delete the application declaration file after saving the management state of the first application declaration.

[0103] S304, the permission management module in the smart watch generates and saves the permission white list corresponding to the first APP based on the permission application file, and the permission white list includes at least one permission required by the first APP.

[0104] The smart watch can generate and save the permission white list corresponding to the first APP based on the permission application file after successfully installing the first APP. The permission white list can be used as a basis for the smart watch to determine whether to request the user to authorize the use of any one of the permissions by the first APP.

[0105] In some embodiments, the smart watch can delete the permission application file after saving the permission white list corresponding to the first APP.

[0106] S305, the permission management module sets the permission management state of the first APP to the closed state based on the permission white list, and saves the permission management state of the first APP.

[0107] The smart watch generates and saves the management state of all permissions in the permission white list based on the permission white list. When the smart watch generates the permission management state of the first APP based on the permission white list, the smart watch can set the permission management state of the first APP to the cancel state.

[0108] The permission management state of the first APP includes the management state of all permissions in the permission white list, or the permission management state of the first APP includes the management state of all permissions required by the first APP. Therefore, the smart watch can set the permission management state of the first APP to the cancel state, which can include setting the management state of all permissions required by the first APP to the cancel state.

[0109] It can be understood that the user has not authorized the use of the permissions in the smart watch by the first APP after the smart watch successfully installs the first APP, and therefore, the smart watch can first set the management state of all permissions required by the first APP to the closed state.

[0110] Alternatively, unlike those described in S304-S305, the smartwatch can directly generate the permission management status of the first APP based on the permission request file.

[0111] S306, the smartwatch displays the desktop interface and receives the first launch operation triggered by the first APP on the desktop interface.

[0112] After successfully installing the first app on the smartwatch, the displayed desktop interface can include the app's icon. The smartwatch can then receive user clicks on the app's icon. Clicking the app's icon triggers the first launch action of the app.

[0113] For example, taking the first app as a workout app on a smartwatch as an example, such as Figure 4 As shown in (a), the smartwatch 10 displays a desktop interface 410, which includes an icon 411 for a workout app. The smartwatch 10 can receive user clicks on the workout app icon 411.

[0114] S307, the smartwatch responds to the first startup operation and reads the management status of the first application declaration of the first APP from the declaration management module.

[0115] After the smartwatch reads the management status of the first application declaration of the first APP from the declaration management module, it can determine whether the management status of the first application declaration is canceled. If the management status of the first application declaration is canceled, then S308 is executed. If the management status of the first application declaration is not canceled, or in other words, the management status of the first application declaration is confirmed, then the home page of the first APP is displayed.

[0116] S308. When the management status of the first application declaration is canceled, the smartwatch displays a declaration confirmation interface, which includes the first application declaration and the corresponding confirmation and cancellation options.

[0117] In some embodiments, in response to a first launch operation, if the management status of the first application declaration of the first app is canceled, the smartwatch displays a declaration pop-up window corresponding to the first app to obtain confirmation from the user regarding the first application declaration. This declaration pop-up window may include: the first application declaration, a confirmation option, and a cancellation option. Optionally, the interface including the declaration pop-up window may be referred to as a declaration confirmation interface.

[0118] For example, such as Figure 4As shown in (b) of FIG. 4, the smart watch 10 displays the declaration pop-up window 420 corresponding to the exercise APP in response to the click operation on the icon 411 of the exercise APP. Figure 4 As shown in (c) of FIG. 4, all the contents in the declaration pop-up window 420 can include the application declaration 421 of the exercise APP, the confirmation option 422 and the cancel option 423.

[0119] However, due to the limited display area of the smart watch 10, only a part of the contents in the declaration pop-up window 420 can be displayed, for example, as shown in (b) of FIG. 5. Figure 4 As shown in (b) of FIG. 5, the smart watch 10 displays a part of the application declaration 421 of the exercise APP in the declaration pop-up window 420. The user can slide up and down in the area of the smart watch 10 where the declaration pop-up window 420 is located to view other contents in the declaration pop-up window 420, for example, the confirmation option 422 and the cancel option 423. As shown in (c) of FIG. 5, the smart watch 10 displays the confirmation option 422 and the cancel option 423 in the declaration pop-up window 420 in response to the up sliding operation input by the user in the area where the declaration pop-up window 420 is located. Figure 4 As shown in (c) of FIG. 5, the smart watch 10 displays the confirmation option 422 and the cancel option 423 in the declaration pop-up window 420 in response to the up sliding operation input by the user in the area where the declaration pop-up window 420 is located.

[0120] In some embodiments, the management state of the first application declaration is defaulted to the cancel state when saved for the first time. Alternatively, the smart watch saves the management state of the first application declaration based on the application declaration file can be referred to as saving the management state of the first application declaration for the first time.

[0121] S309, the smart watch updates the management state of the first application declaration in the declaration management module to the confirmation state in response to the click operation on the confirmation option, and displays the home interface of the first APP.

[0122] When the smart watch displays the declaration confirmation interface including the confirmation option, the smart watch can receive and respond to the click operation on the confirmation option to update the management state of the first application declaration in the declaration management module to the confirmation state, and normally start the first APP. The normal starting of the first APP by the smart watch includes displaying the home interface of the first APP.

[0123] For example, as shown in (e) of FIG. 4, the smart watch 10 displays the home interface 430 of the exercise APP in response to the click operation of the user on the confirmation option 422. Figure 4 As shown in (e) of FIG. 4, the smart watch 10 displays the home interface 430 of the exercise APP in response to the click operation of the user on the confirmation option 422.

[0124] S310, the smart watch displays the desktop interface in response to the click operation on the cancel option.

[0125] When the smart watch displays the declaration confirmation interface including the cancel option, the smart watch can receive and respond to a click operation on the cancel option to continue maintaining the management state of the first application declaration as the cancel state. When the smart watch continues to maintain the management state of the first application declaration as the cancel state, the smart watch cannot start the first APP, and can continue to display the desktop interface.

[0126] For example, as shown in (f) of FIG. 4, the smart watch 10 continues to display the desktop interface 410 in response to a click operation of the user on the cancel option 423. Figure 5

[0127] In some embodiments, in addition to displaying the declaration pop-up window before the first time the first APP is started after the first APP is installed to enable the user to update the management state of the first application declaration of the first APP through the declaration pop-up window, the smart watch can also provide other setting entrances of application declaration to enable the user to update the management state of the first application declaration of the first APP through the other setting entrances of application declaration.

[0128] For example, the other setting entrances of application declaration can include a first setting entrance in the setting APP. The process in which the user updates the management state of the first application declaration of the first APP through the first setting entrance can include: the smart watch displays a first setting interface in the setting APP, the first setting interface can include an application and privacy option; the smart watch displays a second setting interface in response to a click operation on the application and privacy option, the second setting interface can include a declaration management option; and the smart watch displays a third setting interface in response to a click operation on the declaration management option, the third setting interface can include a declaration switch corresponding to the first APP, and the user can modify the management state of the first application declaration of the first APP by operating the declaration switch corresponding to the first APP.

[0129] For example, the other setting entrances of application declaration can include a first setting entrance in the setting APP. The process in which the user updates the management state of the first application declaration of the first APP through the first setting entrance can include: the smart watch displays a first setting interface in the setting APP, the first setting interface can include an application and privacy option; the smart watch displays a second setting interface in response to a click operation on the application and privacy option, the second setting interface can include a declaration management option; and the smart watch displays a third setting interface in response to a click operation on the declaration management option, the third setting interface can include a declaration switch corresponding to the first APP, and the user can modify the management state of the first application declaration of the first APP by operating the declaration switch corresponding to the first APP.

[0130] Optionally, the third setting interface can include a declaration switch corresponding to each application of all applications included in the smart watch, and each declaration switch corresponding to each application is used to modify the management state of the application declaration of each application.​

[0131] In some embodiments, if a user changes the management status of the first application declaration of the first APP to the canceled status by operating the declaration switch corresponding to the first APP, the smartwatch can send a first broadcast message to the declaration management module to control the declaration management module to update the management status of the first application declaration to the canceled status; it can also send a first broadcast message to the permission management module to control the permission management module to update the permission management status of the first APP to the closed status, or keep the permission management status of the first APP closed.

[0132] Secondly, when a user changes the management status of the first application declaration of the first APP to the canceled status by operating the declaration switch corresponding to the first APP, if the smartwatch is running the first APP in the background, the smartwatch must also close the first APP running in the background.

[0133] For example, taking a workout app on a smartwatch as the first app, and the workout app's first application declaration management status as confirmed, this example illustrates the process of updating the first app's first application declaration management status through the first settings entry in the settings app. Figure 5 As shown in (a), the smartwatch 10 displays a first settings interface 510 in the settings app, which may include application and privacy options 511; the smartwatch 10 receives user clicks on the application and privacy options 511. Figure 5 As shown in (b), in response to a click on the application and privacy option 511, the smartwatch 10 displays a second settings interface 520, which may include a claims management option 521; then, the smartwatch 10 receives a click on the claims management option 521. The smartwatch 10 may, in response to a click on the claims management option 521, display a fourth settings interface 530 or a fifth settings interface 540. Both the fourth settings interface 530 and the fifth settings interface 540 are part of the third settings interface.

[0134] like Figure 5 As shown in (c), when the management status of the first application declaration of the exercise app is in the canceled state, the smartwatch 10 can display the fourth settings interface 530 in response to a click on the declaration management option 521. In the fourth settings interface 530, the declaration switch 531 corresponding to the exercise app is in the off state. Then, in response to a click on the declaration switch 531 corresponding to the exercise app, the smartwatch 10 can update the saved management status of the first application declaration to the confirmed state and update the declaration switch 531 corresponding to the exercise app to the on state. Figure 5 As shown in (d), the declaration switch 531 corresponding to the exercise APP is in the on state.

[0135] like Figure 5 As shown in (e), when the management status of the first application declaration of the exercise app is confirmed, the smartwatch 10 can display the fifth settings interface 540 in response to a click on the declaration management option 521. In the fifth settings interface 540, the declaration switch 541 corresponding to the exercise app is turned on. Then, as... Figure 5 As shown in (f), the smartwatch 10 can respond to a click on the declaration switch 541 corresponding to the exercise app by displaying a closing prompt message 550. The closing prompt message 550 is used to indicate that the app cannot be used normally after disagreeing with the app's application declaration. Figure 6 As shown in (g), in response to the user triggering a confirmation to cancel the first application declaration, the smartwatch 10 displays an updated settings interface 560. The updated settings interface 560 does not include the declaration switch 541 corresponding to the workout app.

[0136] Optionally, the updated settings interface 560 may also include a declaration switch for the exercise app, and the declaration switch for the exercise app in the updated settings interface 560 is in a closed state. For example, the declaration switch for the exercise app in the updated settings interface 560 is the same as the declaration switch 531 for the exercise app in the fourth settings interface 530.

[0137] Optionally, if the smartwatch does not include application claims with a confirmed management status, the second settings interface displayed on the smartwatch may not include the claim management option.

[0138] In some embodiments, the declaration pop-up in the declaration confirmation interface may also include information collection options for the first app. The smartwatch receives and responds to a click on the information collection option in the declaration confirmation interface, displaying a declaration of the information collection usage rules for the first app. For example, assuming the first app is a workout app on the smartwatch, such as... Figure 6 As shown in (a), when the smartwatch 10 displays the declaration pop-up 420, it receives a click operation from the user on the information collection option 424 in the declaration pop-up 420. Figure 7 As shown in (b), in response to a click on the information collection option 424, the smartwatch 10 displays a statement 610 of the rules for information collection and usage of the workout app.

[0139] In some embodiments, the smart watch can run the first APP in a case where the management state of the first application declared by the first APP is a confirmed state. In the process of running the first APP, the smart watch can determine whether to request the user for authorization for the first APP to use the permission when the first APP needs to use one or more permissions in the smart watch, based on the permission whitelist corresponding to the first APP and the permission management state of the first APP. For example, Figure 8 As shown in FIG. 8(a), the application management method provided by the embodiments of the present application can further include S701-S709.

[0140] S701, the smart watch displays a first application interface in the first APP in a case where the management state of the first application declared by the first APP is a confirmed state.

[0141] The smart watch can display the first application interface when normally running the first APP. For example, the first application interface can be a home interface of the first APP.

[0142] For example, taking the first APP as a workout APP in the smart watch as an example, as shown in FIG. 8(a), the smart watch 10 displays a first application interface 810 in the workout APP. Figure 8

[0143] S702, the smart watch determines a first permission associated with a first function in response to a second start operation triggering the first function in the first APP on the first application interface.

[0144] The smart watch can determine one or more permissions associated with the first function in response to the second start operation. The first permission associated with the first function can include all permissions associated with the first function.

[0145] For example, the first application interface 810 can include a start recording option 811, and the first function triggered by the start recording option 811 can be recording movement information. As shown in FIG. 8(a), the smart watch 10 receives a click operation of the user on the start recording option 811. The smart watch 10 determines a first permission associated with recording movement information in response to the click operation on the start recording option 811. The first permission associated with recording movement information can include a permission to read location information. Figure 8

[0146] S703, the smart watch finds the management state of the first permission from the permission management state of the first APP saved by the permission management module, and the permission management state of the first APP is a closed state by default when saved for the first time.

[0147] ​​The smart watch can first find the management state of the first permission in the permission management state of the first APP, and then determine whether to request the user to authorize the first APP to use the first permission based on the management state of the first permission.

[0148] Optionally, the smart watch can be referred to as first saving the permission management state of the first APP after generating the permission management state of the first APP based on the permission application file.

[0149] In some embodiments, the smart watch can save the permission white list corresponding to the first APP and the permission management state of the first APP. The smart watch can first read the permission white list corresponding to the first APP from the permission management module, and then determine whether the permission white list includes the first permission. If the permission white list includes the first permission, the smart watch can read the permission management state of the first APP from the permission management module, and find the management state of the first permission from the permission management state of the first APP. If the permission white list does not include the first permission, the smart watch can not start the first function, and display the first prompt information. The first prompt information can be used to prompt that the first APP does not apply for the first permission.

[0150] In some embodiments, if the smart watch does not save the permission white list or does not save the permission management state of the first APP, the smart watch can not start the first function, and display the first prompt information.

[0151] S704, the smart watch displays a permission request interface in the case that the management state of the first permission is the closed state, and the permission request interface includes an open option corresponding to the first permission and a closed option corresponding to the first permission.

[0152] The smart watch can determine whether the management state of the first permission is the closed state. If the management state of the first permission is the closed state, S704 is executed. If the management state of the first permission is not the closed state, or the management state of the first permission is the open state, the first function is started, and the operation interface of the first function is displayed.

[0153] In some embodiments, the smart watch displays a permission pop-up window corresponding to the first APP to obtain authorization of the user to the first APP using the first permission in the case that the management state of the first permission is the closed state in response to the second start operation. The permission pop-up window can include an open option corresponding to the first permission and a closed option. Optionally, the interface including the permission pop-up window can be referred to as a permission request interface.

[0154] For example, taking the first permission including only the permission of reading location information as an example, as shown in FIG. 7A, the smart watch can display a permission request interface 7001 including an open option 7002 and a closed option 7003. Figure 8As shown in (b), when the permission management status for reading location information is off, the smartwatch 10 displays a permission pop-up window 820 for the exercise app. The permission pop-up window 820 may include: a prompt message 821 indicating whether to enable the permission to read location information, an enable option 822, and a disable option 823.

[0155] S705: In response to a click on the enable option, the smartwatch executes the first action allowed by the first permission by calling the behavior call interface corresponding to the first permission through the first APP, and displays the operation interface of the first function.

[0156] In response to a tap on the activation option, the smartwatch launches the first function and displays the interface of that first function within the first app. Simultaneously, the smartwatch can invoke the corresponding API call to execute the first action permitted by that first permission. For example, it can invoke the location information interface to read the smartwatch's location data, invoke the call interface to launch the phone app, invoke the SMS interface to launch the SMS app, invoke the Bluetooth interface to launch the Bluetooth app, invoke the media data interface to read media data, or invoke the microphone interface to activate the microphone, and so on.

[0157] For example, such as Figure 8 As shown in (c), when the smartwatch 10 displays the permission pop-up 820, in response to the click operation of the enable option 822, the operation interface 830 for recording running information is displayed, and the exercise APP begins to read the location information of the smartwatch 10 through the interface for reading location information.

[0158] In some embodiments, when the management status of a permission required by an app on the smartwatch is off, the app cannot call the behavior call interface corresponding to that permission. Only when the management status of a permission required by an app on the smartwatch is on can the app call the behavior call interface corresponding to that permission and execute the behavior allowed by that permission.

[0159] S706, the behavior call interface corresponding to the first permission in the smartwatch reports the first event to the behavior reporting module. The first event refers to the event in which the first APP executes the first behavior.

[0160] The behavior call interface corresponding to each permission in a smartwatch can not only control whether an app can execute the behavior allowed by that permission, but also report the first event of the app executing the behavior allowed by that permission to the behavior reporting module after the app executes the behavior allowed by that permission.

[0161] The behavior reporting module in the S707 smartwatch generates and saves first behavior information based on the first event. The first behavior information is used to record the usage information of the first APP on the first permission.

[0162] The first line of information is used to record the usage information of the first app on the first permission, and the usage information may include the duration of the first app's use of the first permission. For example, the first line of information may include: the exercise app reads the location information of the smartwatch 10 at a certain moment.

[0163] S708: In response to a click on the enable option, the smartwatch updates the management status of the first permission in the permission management status of the first APP to the enabled state in the permission management module.

[0164] After displaying the permission request interface, the S709 smartwatch displays the first application interface in response to a click on the close option.

[0165] When a smartwatch displays a permission request interface that includes a "close" option, it can receive and respond to a click on the "close" option, maintaining the primary permission management status as "closed." While the smartwatch maintains the primary permission management status as "closed," it can choose not to activate the primary function and continue displaying the primary application interface.

[0166] In some embodiments, in response to a click on the close option, the smartwatch may first display a second prompt message and then display the first application interface. The second prompt message may indicate that the first function in the first app cannot be started because the first permission has not been granted to the first app.

[0167] For example, such as Figure 9 As shown in (d), when the smartwatch 10 displays the permission pop-up 820, in response to clicking the close option 823 in the permission pop-up 820, a second prompt message 840 is displayed. The second prompt message 840 may include: The exercise app has not been authorized to read location information, and cannot start recording running information.

[0168] It should be noted that when the first permission includes multiple permissions, the smartwatch can perform the processing procedure for the first permission described in S701-S709 above for each of the first permissions.

[0169] Optionally, different from the process described in S701-S709, the smart watch can start the first function when the first APP is not authorized the first permission. However, the process of starting the first function when the first APP is not authorized the first permission is different from the process of starting the first function when the first APP is authorized the first permission. For example, the first function can include multiple sub-functions, the smart watch can start part of the sub-functions in the first function when the first APP is not authorized the first permission, and the smart watch can start all the sub-functions in the first function when the first APP is authorized the first permission.

[0170] For example, the case that the first APP is not authorized the first permission can include that the smart watch does not save the permission whitelist, the smart watch does not save the permission management state of the first APP, the permission whitelist does not include the first permission, and the management state of the first permission is the off state. The case that the first APP is authorized the first permission can include that the management state of the first permission is the on state.

[0171] In some embodiments, in addition to displaying the permission pop-up window when the first APP needs to use the first permission, so that the user updates the management state of the first permission required by the first APP through the permission pop-up window, the smart watch can also provide other setting entrances of the permission, so that the user updates the management state of the first permission required by the first APP through the other setting entrances of the permission.

[0172] For example, the other setting entrances of the permission can include a second setting entrance in the setting APP. The process that the user updates the management state of the first permission required by the first APP through the second setting entrance can include that the second setting interface displayed by the smart watch in the setting APP can also include a permission management option; the smart watch can display a sixth setting interface in response to the click operation on the permission management option, and the sixth setting interface can include a sub-permission management option corresponding to the first APP; the smart watch displays a seventh setting interface in response to the click operation on the sub-permission management option corresponding to the first APP. The seventh setting interface includes a permission switch corresponding to each permission in at least one permission required by the first APP, and the user can modify the management state of the permission in the permission management state of the first APP by operating the permission switch corresponding to each permission.

[0173] When a permission required by the first app is in a disabled state, the corresponding permission switch will be displayed as disabled. In this case, the smartwatch can respond to a tap on the permission switch by updating the permission management status of that permission in the first app to enabled and the corresponding permission switch to enabled. Conversely, when a permission required by the first app is in a disabled state, the corresponding permission switch will be displayed as enabled. In this case, the smartwatch can respond to a tap on the corresponding permission switch by updating the permission management status of that permission in the first app to disabled and the corresponding permission switch to disabled.

[0174] Optionally, the sixth settings interface may include sub-permission management options for each application among all the applications included in the smartwatch. These sub-permission management options for each application are used to trigger the display of the permission switch for each of the at least one required permission for each application.

[0175] For example, taking a workout app on a smartwatch as the first app, and the workout app's first application declaration management status as "on," this example illustrates the process of updating the first app's first application declaration management status through a second settings entry within the app. Figure 9 As shown in (a), the second settings interface 520 displayed by the smartwatch 10 may also include a permission management option 522; the smartwatch 10 receives user clicks on the permission management option 522. Figure 9 As shown in (b), in response to a click on permission management option 522, smartwatch 10 displays a sixth settings interface 910. The sixth settings interface 910 may include sub-permission management options corresponding to each of the apps included with smartwatch 10, such as sub-permission management option 911 for the workout app. In response to a click on sub-permission management option 911 for the workout app, smartwatch 10 displays an eighth settings interface 920 or a ninth settings interface 930. Both the eighth and ninth settings interfaces 920 and 930 are part of the seventh settings interface. Both the eighth and ninth settings interfaces 920 may include permission switches for each of at least one permission required by the workout app, such as the permission switch for reading location information. The display states of the permission switches in the eighth and ninth settings interfaces 920 and 930 are different.

[0176] like Figure 9As shown in (c), when the permission management status for the exercise app to read location information is off, the smartwatch 10 displays the eighth settings interface 920 in response to a click on the sub-permission management option 911 corresponding to the exercise app. In the eighth settings interface 920, the permission switch 921 corresponding to the permission to read location information is off.

[0177] like Figure 9 As shown in (d), when the permission management status for reading location information required by the exercise app is enabled, the smartwatch 10 responds to a click on the sub-permission management option 911 corresponding to the exercise app, displaying the ninth settings interface 930. In the ninth settings interface 930, the permission switch 931 corresponding to the permission to read location information is enabled. Then, as... Figure 9 As shown in (e), the smartwatch 10 can respond to a click operation on the permission switch 931 corresponding to the permission to read location information, displaying a third prompt message 941, a confirm closing option 942, and a cancel closing option 943. The third prompt message 941 is used to inform the user that the exercise app cannot be used normally after the permission to read location information is closed. Figure 10 As shown in (f), in response to the click operation of the confirmation close option 942, the smartwatch updates the management status of the permission to read location information required by the exercise APP to the closed state, and updates the permission switch 931 corresponding to the permission to read location information to the closed state.

[0178] In addition, the smartwatch 10 can respond to the click operation of the cancel / close option 943, keep the management status of the permission to read location information required by the exercise app in the enabled state, and display the ninth settings interface 930.

[0179] In some embodiments, after each app on the smartwatch performs the permitted actions, it can save the corresponding behavior information locally (e.g., the first behavior information mentioned above) to record the app's usage information of that permission. The smartwatch provides a query entry point for users to browse all saved behavior information.

[0180] For example, the entry point for querying behavior information can be located in the settings app. The process of a user viewing behavior information through the query entry point in the settings app may include: a second settings interface in the settings app displayed on the smartwatch may also include a behavior recording option; the smartwatch may respond to a click on the behavior recording option by displaying a tenth settings interface, which may include at least one piece of behavior information within a preset duration. Due to the limited display area of ​​the smartwatch, only a portion of the at least one piece of behavior information may be displayed. The user can swipe up and down within the area of ​​the tenth settings interface to view other content within the at least one piece of behavior information.

[0181] For example, taking the first APP as a workout APP in a smart watch as an example, the process of updating the management state of the first application declaration of the first APP through the second setting entry in the APP is introduced. As shown in (a) of FIG. 5, the second setting interface 520 displayed by the smart watch 10 can further include a behavior record option 523; the smart watch 10 receives a click operation of the user on the behavior record option 523. As shown in (b) of FIG. 5, the smart watch 10 displays a tenth setting interface 1010 in response to the click operation on the behavior record option 523. The tenth setting interface 1010 can include at least one behavior information in a week, and the at least one behavior information can include the position information of the smart watch 10 read by the workout APP at one time. Figure 10 Figure 11 As shown in (b) of FIG. 5, the smart watch 10 displays a tenth setting interface 1010 in response to the click operation on the behavior record option 523. The tenth setting interface 1010 can include at least one behavior information in a week, and the at least one behavior information can include the position information of the smart watch 10 read by the workout APP at one time.

[0182] In some embodiments, the smart watch supports uninstalling any one APP in the smart watch. When the smart watch displays a desktop interface, an editing interface can be displayed in response to an editing trigger operation triggering an editing mode. The editing interface can include an icon of each application in the smart watch and an editing identifier corresponding to the icon of each application. Then, the smart watch can display an uninstall prompt interface in response to a click operation on the icon of one APP in the editing interface. The uninstall prompt interface can include fourth prompt information, a confirmation uninstall option, and a cancel uninstall option. The smart watch can uninstall the APP in response to a click operation on the confirmation uninstall option, or not execute uninstalling the APP in response to a click operation on the cancel uninstall option.

[0183] The fourth prompt information can be used to prompt the user to confirm whether to uninstall the APP, and can also prompt the installation path of the APP. Exemplarily, since the installation paths of system APPs and third-party APPs can be different, the installation path in the fourth prompt information displayed when uninstalling a system APP is different from the installation path in the fourth prompt information displayed when uninstalling a third-party APP.

[0184] In some embodiments, after the smart watch uninstalls an APP (for example, a first APP), a second broadcast message can be sent to the declaration management module to control the declaration management module to delete the management state of the application declaration of the APP (for example, the management state of the first application declaration); and a second broadcast message can also be sent to the permission management module to control the permission management module to delete the permission management state of the APP.

[0185] For example, as shown in (a) of FIG. 5, Figure 11 ​As shown in (a) of FIG. 11, the smart watch 10 displays a desktop interface 410, which includes an icon 411 of an exercise APP and an icon 412 of a multimedia playing APP. The exercise APP belongs to a system APP, and the multimedia playing APP belongs to a third-party APP. Then, the smart watch 10 can receive a long-press operation input by a user on the desktop interface 410, which belongs to an edit trigger operation. As shown in (b) of FIG. 11, the smart watch 10 displays a fifth prompt information 1110 in response to the long-press operation. The fifth prompt information 1110 is used to prompt entering an edit operation and an operation of exiting the edit mode. As shown in (c) of FIG. 11, the smart watch 10 displays an edit interface 1120 after a certain time length, after displaying the fifth prompt information 1110. The edit interface 1120 includes an edit mark corresponding to an icon of each APP, for example, an edit mark 1122 corresponding to an icon 1121 of the exercise APP and an edit mark 1124 corresponding to an icon 1123 of the multimedia playing APP. Figure 11 Figure 11

[0186] Then, as shown in (d) of FIG. 11, the smart watch 10 can display a fourth prompt information 1131 corresponding to the exercise APP, a confirmation uninstall option 1132 and a cancel uninstall option 1133 in response to a click operation of the user on the icon 1121 corresponding to the exercise APP. The installation path prompted by the fourth prompt information 1131 corresponding to the exercise APP can be located in a setting APP. Figure 11

[0187] Alternatively, as shown in (e) of FIG. 11, the smart watch 10 can display a fourth prompt information 1141 corresponding to the multimedia playing APP, a confirmation uninstall option 1142 and a cancel uninstall option 1143 in response to a click operation of the user on the icon 1123 corresponding to the multimedia playing APP. The installation path prompted by the fourth prompt information 1141 corresponding to the multimedia playing APP can be located in an application market APP. Figure 12

[0188] It should be noted that the display style of the icon of the APP in the edit interface and the display style of the icon of the APP in the desktop interface can be different, for example, the size of the icon of the APP in the edit interface is larger, the color of the icon of the APP in the edit interface is brighter, and the line of the icon of the APP in the edit interface is thicker, and the like.

[0189] In some embodiments, the smart watch can provide an installation entrance of the uninstalled system APP in addition to supporting uninstalling the system APP in the smart watch. Exemplarily, the installation entrance of the uninstalled system APP can be located in the setting APP.

[0190] For example, taking the uninstalled system APP as the exercise APP, the process of reinstalling the uninstalled system APP by the smart watch is introduced. As shown in (f) of FIG. 11, the smart watch 10 displays a sixth prompt information 1151 in response to a click operation of the user on the confirmation uninstall option 1132. The sixth prompt information 1151 is used to prompt the user to enter the setting APP. Figure 12 ​​​​As shown in (a), the second settings interface 520 displayed by the smartwatch 10 may also include a system application retrieval option 524; the smartwatch 10 receives a user's click on the behavior system application retrieval option 524. Figure 12 As shown in (b), in response to a click on the system app retrieval option 524, the smartwatch 10 displays an eleventh settings interface 1210. The eleventh settings interface 1210 may include installation options for each uninstalled system app, for example, installation option 1211 for the uninstalled workout app. Figure 12 As shown in (c), in response to a click on the installation option 1211 corresponding to the workout app, the smartwatch 10 displays a sixth prompt message 1220, which indicates that installation is in progress. Then, as... Figure 12 As shown in (d), when the smartwatch 10 successfully installs the workout app, it displays the seventh notification message 1230. This seventh notification message 1230 indicates successful installation of the workout app. Figure 13 As shown in (e), after the seventh prompt message 1230, the smartwatch 10 can display the twelfth settings interface 1240. The twelfth settings interface 1240 may include an option 1241 for opening the exercise app, which can be used to launch the exercise app.

[0191] Optionally, if the smartwatch does not include the uninstalled system apps, the second settings interface displayed on the smartwatch may not include the option to retrieve system apps.

[0192] Reference Figure 13 The diagram shown is a flowchart illustrating an application management method provided in an embodiment of this application. Figure 8 As shown, the method may further include the following steps S1301-S1305.

[0193] S1301, the smartwatch displays the first interface of the first application.

[0194] For example, the first interface can be the first application interface described above, such as... Figure 8 The first application interface 810 of the exercise APP is shown in (a).

[0195] For example, S1301 may include the above-described S701.

[0196] S1302, The smartwatch responds to a first operation that triggers a first function in a first application on the first interface and determines the first permission associated with the first function.

[0197] For example, the first operation can be the second startup operation described above.

[0198] Exemplarily, S1302 can include S702 described above.

[0199] S1303, the smart watch finds the management state of the first permission in the permission management state of the first application, and the permission management state of the first application is in a default off state when saved for the first time.

[0200] Exemplarily, S1303 can include S703 described above.

[0201] S1304, the smart watch displays a second interface in a case where the management state of the first permission is in an off state, and the second interface includes an opening option corresponding to the first permission.

[0202] Exemplarily, the second interface can be the permission request interface described above, for example, the interface including the permission pop-up window 820 shown in (b) of FIG. 8. Figure 8

[0203] Exemplarily, S1304 can include S704 described above.

[0204] S1305, the smart watch displays a third interface in response to a second operation on the opening option, and the third interface includes an operation interface of the first function.

[0205] Exemplarily, the second operation can be the click operation on the opening option described above. The third interface can be the operation interface of the first function described above, for example, the operation interface 830 for recording running information shown in (c) of FIG. 8. Figure 4

[0206] Exemplarily, S1305 can include S705 described above.

[0207] Optionally, the second interface further includes a closing option corresponding to the first permission; and after displaying the second interface, the method further includes: in response to a third operation on the closing option, displaying the first interface. Exemplarily, the third operation can be the click operation on the closing option described above.

[0208] Optionally, before displaying the first interface in the first application, the method further includes: displaying a fourth interface; the fourth interface includes a desktop interface of the wearable device; receiving a fourth operation triggering the first application on the fourth interface; in response to the fourth operation, in a case where the management state of the first application declaration is in a cancel state when saved for the first time, displaying a fifth interface, wherein the management state of the first application declaration is in a default cancel state when saved for the first time, and the fifth interface includes the first application declaration and a confirmation option corresponding to the first application declaration; in response to a fifth operation on the confirmation option, updating the management state of the first application declaration to a confirmation state, and displaying a sixth interface, and the sixth interface includes a home interface of the first application.

[0209] ​​Exemplarily, the fourth interface can be the desktop interface, for example, the display desktop interface 410 shown in (a) of FIG. 4. Figure 4 The fourth operation can be the first starting operation. The fifth interface can be the declaration confirmation interface, for example, the interface including the declaration pop-up window 420 shown in (b) of FIG. 4. Figure 4 The sixth operation can be the operation of the user selecting the declaration pop-up window 420 shown in (c) of FIG. 4. Figure 13 The sixth operation can be the operation of the user selecting the declaration pop-up window 420 shown in (c) of FIG. 4.

[0210] Optionally, the method further includes: in the case that the first application is not installed, in response to a seventh operation, obtaining an installation package of the first application, and installing the first application by using the installation package of the first application; parsing the permission application file and the application declaration file from the installation package of the first application, the permission application file including at least one permission required by the first application, and the application declaration file including the first application declaration; after successfully installing the first application, setting the management state of the first application declaration to a cancel state based on the application declaration file, and saving the management state of the first application declaration; setting the permission management state of the first application to a close state based on the permission application file, and saving the permission management state of the first application, the permission management state of the first application including the management state of each of the at least one permission.

[0211] Exemplarily, the seventh operation can be the installation operation.

[0212] Optionally, the method further includes: displaying a seventh interface, the seventh interface including a first setting option; in response to an eighth operation on the first setting option, displaying an eighth interface, the eighth interface including a behavior record option; and in response to a ninth operation on the behavior record option, displaying a ninth interface, the ninth interface including at least one behavior information.

[0213] Exemplarily, the seventh interface can be the first setting interface, for example, the first setting interface 510. The first setting option can be the application-privacy option. The eighth interface can be the second setting interface, for example, the second setting interface 520. The ninth interface can be the tenth setting interface, for example, the tenth setting interface 1010.

[0214] Optionally, the seventh interface includes a second setting option. After displaying the seventh interface, the method further includes: in response to a tenth operation on the second setting option, displaying a tenth interface, the tenth interface including a declaration switch corresponding to each of at least one application in the wearable device, each of the declaration switches being used for modifying the management state of the application declaration of each of the at least one application, the at least one application including the first application.

[0215] Exemplarily, the second setting option can be the declaration management option described above. The tenth interface can be the third setting interface described above, for example, the fourth setting interface 530 or the fifth setting interface 540.

[0216] Optionally, the seventh interface includes a third setting option. After displaying the seventh interface, the method further includes: in response to a tenth operation on the third setting option, displaying an eleventh interface, the eleventh interface including a fourth setting option corresponding to each of at least one application in the wearable device, the at least one application including the first application; and in response to an eleventh operation on the fourth setting option corresponding to the first application, displaying a twelfth interface, the twelfth interface including a permission switch corresponding to each of at least one permission required by the first application.

[0217] Exemplarily, the third setting option can be the permission management option described above. The eleventh interface can be the sixth setting interface described above, for example, the sixth setting interface 910. The fourth setting option can be the sub-permission management option described above. The twelfth interface can be the seventh setting interface described above, for example, the eighth setting interface 920 or the ninth setting interface 930.

[0218] It can be understood that, in order to implement the above functions, the wearable device includes hardware structures and / or software modules corresponding to the functions. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed in the present application, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is implemented in hardware or computer software driven hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of the present application.

[0219] The embodiments of the present application can divide the wearable device into functional modules according to the above method examples, for example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The integrated module can be implemented in the form of hardware or software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical functional division. When actually implemented, there can be another division method.

[0220] The embodiments of the present application also provide a wearable device, which includes: a memory and one or more processors; the memory is coupled to the processor; and the memory stores computer program code, the computer program code includes computer instructions, when the computer instructions are executed by the processor, the wearable device executes the application management method provided by the foregoing embodiments.

[0221] The embodiment of the present application further provides a computer readable storage medium, which comprises computer instructions, and when the computer instructions are executed on the wearable device, the wearable device executes the application management method provided in the foregoing embodiment.

[0222] The embodiment of the present application further provides a computer program product, which comprises executable instructions, and when the computer program product is executed on the wearable device, the wearable device executes the application management method provided in the foregoing embodiment.

[0223] The embodiment of the present application further provides a chip system, as shown in the figure, the chip system 1300 comprises at least one processor 1301 and at least one interface circuit 1302. The processor 1301 and the interface circuit 1302 can be interconnected through a line. For example, the interface circuit 1302 can be used to receive signals from other devices (such as the memory of the wearable device). For another example, the interface circuit 1302 can be used to send signals to other devices (such as the processor 1301). ​

[0224] Illustratively, the interface circuit 1302 can read the instructions stored in the memory and send the instructions to the processor 1301. When the instructions are executed by the processor 1301, the chip system can execute each step in the above embodiment. Of course, the chip system can also comprise other discrete devices, and the embodiment of the present application does not specifically limit this.

[0225] Through the description of the above embodiments, those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional modules is exemplified, and in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0226] In several embodiments provided in the present application, it should be understood that the disclosed devices / equipment and methods can be implemented in other ways. For example, the device / equipment embodiments described above are only illustrative, for example, the division of the modules or units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another device, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed each other can be through some interface, indirect coupling or communication connection between devices or units, which can be electrical, mechanical or other forms.

[0227] ​The units described as separate components may or may not be physically separate, and the components displayed as units may be a physical unit or multiple physical units, that is, may be located in one place, or also can be distributed to multiple different places. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0228] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0229] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a readable storage medium. Based on such understanding, the technical scheme of the embodiments of the present application essentially or the part that contributes to the prior art or the whole or part of the technical scheme can be embodied in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for causing an apparatus (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0230] The above is only a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, any change or replacement within the technical scope disclosed in the present application should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. An application management method characterized by comprising: The method is applied to a wearable device, an operating system of the wearable device is a real-time operating system (RTOS), and the method comprises the following steps: displaying a first interface in a first application, the first application belonging to a JS application; in response to a first operation of triggering a first function in the first application on the first interface, determining a first permission associated with the first function; finding a management state of the first permission in a permission management state of the first application, the permission management state of the first application being a closed state by default when saved for the first time; in the case that the management state of the first permission is a closed state, displaying a second interface, the second interface comprising an opening option corresponding to the first permission; in response to a second operation on the opening option, displaying a third interface, the third interface comprising an operation interface of the first function.

2. The method of claim 1, wherein, The second interface further comprises a closing option corresponding to the first permission; after the second interface is displayed, the method further comprises: in response to a third operation on the closing option, displaying the first interface.

3. The method according to claim 1 or 2, characterized in that, The method further comprises: displaying the third interface, and performing a first behavior allowed by the first permission; generating first behavior information and saving the first behavior information, the first behavior information being used for recording usage information of the first application on the first permission.

4. The method according to claim 1 or 2, characterized in that, The method further comprises: in response to the second operation, updating the management state of the first permission in the permission management state of the first application to an opening state.

5. The method according to claim 1 or 2, characterized in that, Before the first interface in the first application is displayed, the method further comprises: displaying a fourth interface; the fourth interface comprising a desktop interface of the wearable device; receiving a fourth operation of triggering the first application on the fourth interface; in response to the fourth operation, in the case that a management state of a first application declaration of the first application is a cancellation state, displaying a fifth interface, wherein the management state of the first application declaration is a cancellation state by default when saved for the first time, the fifth interface comprising the first application declaration and a confirmation option corresponding to the first application declaration; in response to a fifth operation on the confirmation option, updating the management state of the first application declaration to a confirmation state, and displaying a sixth interface, the sixth interface comprising a home interface of the first application.

6. The method of claim 5, wherein, The fifth interface further comprises a cancellation option corresponding to the first application declaration; wherein, after the fifth interface is displayed, the method further comprises: in response to a sixth operation on the cancellation option, displaying the fourth interface.

7. The method according to claim 1 or 2, characterized in that, The method further comprises: in the case that the first application is not installed, in response to a seventh operation, obtaining an installation package of the first application, and installing the first application by using the installation package of the first application; parsing a permission application file and an application declaration file from the installation package of the first application, the permission application file comprising at least one permission required by the first application, and the application declaration file comprising the first application declaration; after the first application is successfully installed, setting the management state of the first application declaration to a cancellation state based on the application declaration file, and saving the management state of the first application declaration; setting, based on the permission application file, a permission management state of the first application to a closed state, and saving the permission management state of the first application, the permission management state of the first application including a management state of each of the at least one permission.

8. The method of claim 7, wherein, The saving, based on the permission application file, the permission management state of the first application and setting the permission management state of the first application to a closed state includes: generating, based on the permission application file, a permission white list corresponding to the first application and saving the permission white list, the permission white list including the at least one permission; saving, based on the permission white list, the permission management state of the first application and setting the permission management state of the first application to a closed state.

9. The method of claim 1 or 2, wherein, The method further includes: in response to the first operation, displaying a first prompt information in a case that the wearable device does not save the permission management state of the first application, and then displaying the first interface, the first prompt information being used to prompt that the first application does not apply for the first permission.

10. The method of claim 1 or 2, wherein, The method further includes: displaying a seventh interface, the seventh interface including a first setting option; in response to an eighth operation on the first setting option, displaying an eighth interface, the eighth interface including a behavior record option; in response to a ninth operation on the behavior record option, displaying a ninth interface, the ninth interface including at least one behavior information.

11. The method of claim 10, wherein, The seventh interface includes a second setting option; after the seventh interface is displayed, the method further includes: in response to a tenth operation on the second setting option, displaying a tenth interface, the tenth interface including a declaration switch corresponding to each of at least one application in the wearable device, the declaration switch corresponding to each of the at least one application being used to modify a management state of an application declaration of the each of the at least one application, the at least one application including the first application.

12. The method of claim 10, wherein, The seventh interface includes a third setting option; after the seventh interface is displayed, the method further includes: in response to a tenth operation on the third setting option, displaying an eleventh interface, the eleventh interface including a fourth setting option corresponding to each of at least one application in the wearable device, the at least one application including the first application; in response to an eleventh operation on the fourth setting option corresponding to the first application, displaying a twelfth interface, the twelfth interface including a permission switch corresponding to each of at least one permission required by the first application, the permission switch corresponding to each of the at least one permission being used to modify a management state of the each of the at least one permission.

13. A wearable device, comprising: The wearable device includes a processor, a memory and a communication interface; the memory and the communication interface are coupled with the processor, the memory is used to store computer program code, the computer program code including computer instructions; wherein when the processor executes the computer instructions, the wearable device executes the method in any one of claims 1-12.

14. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions; when the computer instructions run on the wearable device, the wearable device executes the method in any one of claims 1-12.

15. A chip system, characterized by The chip system comprises a processor and an interface circuit, the processor and the interface circuit are interconnected through a line; wherein the interface circuit is used for receiving a signal from a wearable device and sending the signal to the processor, the signal comprises computer instructions; when the processor executes the computer instructions, the chip system executes the method in any one of claims 1-12.

Images