Application management method and wearable device

Abstract

The embodiment of the invention discloses an application management method and wearable equipment, and relates to the technical field of intelligent equipment. The method comprises the steps of displaying a first interface in a first application; in response to a first operation for triggering a first function in the first application on the first interface, determining a first permission associated with the first function; searching the management state of the first permission in the permission management state of the first application; under the condition that the management state of the first permission is a closed state, a second interface is displayed, 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, the third interface comprising an operation interface of the first function. By adopting the scheme, the personal information of the user in the wearable equipment can be prevented from being collected under the condition that the user does not perform permission authorization on the first application. Therefore, 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 smart devices, and in particular to an application management method and a wearable device. Background Art

[0002] Nowadays, wearable devices such as smart watches and smart hands have become indispensable tools in people's daily lives. By installing applications (APPs) in wearable devices, the functions of the devices can be improved. However, some APPs in wearable devices will collect and use users' personal information without the knowledge of the users. For example, some APPs automatically use the microphone of the wearable device to collect voice information during work, or automatically read the set location information in the wearable device, etc. In summary, after installing some APPs in wearable devices, these APPs can collect the personal information of users in the wearable devices at will, and there is a lack of effective protection measures for the personal information of users in the wearable devices. Summary of the invention

[0003] The embodiments of the present application provide an application management method and a wearable device, which can prevent an application in a wearable device from collecting personal information of a user in the wearable device without the user's permission, thereby effectively protecting the personal information of the user in the wearable device.

[0004] To achieve the above objectives, the 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, and the method includes: first displaying a first interface in a first application; determining a first permission associated with the first function on the first interface in response to a first operation that triggers a first function in the first application; then, searching for the management status of the first permission in the permission management status of the first application, the permission management status of the first application being closed by default when first saved; when the management status of the first permission is closed, displaying a second interface, the second interface including an enable option corresponding to the first permission; and displaying a third interface in response to a second operation on the enable option, the third interface including an operation interface of the first function.

[0006] It is understandable that when the wearable device first saves the permission management state of the first application, the user does not authorize any permission to the first application, and the permission management state of the first application saved by the wearable device for the first time is closed by default. Furthermore, 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 closed, the second interface is displayed to request the user to authorize the first permission to the first application. The wearable device responds to the user's second operation of the opening option in the second interface, indicating that the user authorizes the first permission to the first application, and then displays the operation interface of the first function normally. When the operation interface of the first function is displayed normally, the first application can collect the user's personal information in the wearable device through the first permission associated with the first function. Since the user has authorized the first permission to the first application, the first application collects the user's personal information in the wearable device through the first permission with the consent of the user.

[0007] In summary, this solution prevents an application from collecting the user's personal information in the wearable device through the permission without the user's authorization, thereby effectively protecting the user's personal information in the wearable device.

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

[0009] It is understandable that when the wearable device displays the second interface to request the user to authorize the first permission for the first application, the user can also choose not to authorize the first application with the first permission by operating the close option in the second interface to avoid the first application collecting the user's personal information in the wearable device through the first permission.

[0010] In combination with the first aspect, in another possible implementation, the method also includes: while displaying the third interface, executing the first behavior permitted by the first permission; generating and saving first behavior information, wherein the first behavior information is used to record the usage information of the first application for the first permission.

[0011] It is understandable that after the wearable device determines that the user has authorized the first permission for the first application, it will normally display the third interface while executing the first behavior allowed by the first permission. The third interface may include the operation interface of the first function. The wearable device may collect some user's personal information during the execution of the first behavior, and then update the operation interface of the first function based on the user's personal information 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 usage information of the first permission by the first application.

[0013] In combination with the first aspect, in another 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 enabled state.

[0014] It is understandable that after the wearable device determines that the user has authorized the first permission for the first application, the management state of the first permission in the permission management state of the first application is updated to an enabled state. In this way, the first application does not need to request the user's authorization the next time it needs to use the first permission, thereby avoiding the user from repeatedly authorizing the same permission for the same application.

[0015] In combination with the first aspect, in another 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. A fourth operation that triggers the first application is received on the fourth interface; in response to the fourth operation, when the management status declared by the first application of the first application is in a canceled state, a fifth interface is displayed, wherein the management status declared by the first application is in a canceled state by default when it is first saved, and the fifth interface includes the first application declaration and a confirmation option corresponding to the first application declaration. In response to the fifth operation on the confirmation option, the management status declared by the first application is updated to a confirmed state, and a sixth interface is displayed, and the sixth interface includes the homepage interface of the first application.

[0016] It is understandable that when the wearable device first saves the first application declaration of the first application and the user does not confirm the first application declaration of the first application, the management status of the first application declaration saved by the wearable device for the first time is the canceled status by default. Furthermore, when the user triggers the first application, if the management status of the first application declaration is the canceled status, the fifth interface is displayed to request the user to confirm the first application declaration. The wearable device responds to the user's fifth operation on the confirmation option in the fifth interface, indicating that the user confirms the first application declaration, and then the homepage interface of the first application is displayed normally. By adopting this solution, it is possible to avoid starting the first application when the user does not confirm the first application declaration of the first application.

[0017] In combination with the first aspect, in another possible implementation, the fifth interface further includes a cancel option corresponding to the first application declaration. After displaying the fifth interface, the method further includes: in response to a sixth operation on the cancel option, displaying the fourth interface.

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

[0019] In combination with the first aspect, in another possible implementation, the method also includes: in a case where the first application is not installed, in response to the seventh operation, obtaining the installation package of the first application, and using the installation package of the first application to install 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 status declared by the first application to a canceled state based on the application declaration file, and saving the management status declared by the first application; setting the permission management status of the first application to a closed state based on the permission application file, and saving the permission management status of the first application, the permission management status of the first application including the management status of each permission of at least one permission.

[0020] It is understandable that the wearable device can obtain the permission application file and the application declaration file during the installation of the first application; then, the management state declared by the first application is created based on the application declaration file, and the permission management state of the first application is created based on the permission application file. The management state declared by the first application is used to determine whether the user confirms the first application declaration, thereby ensuring that the first application is started when the user confirms the first application declaration. The permission management state of the first application is also used to determine whether the user authorizes the permission to the first application, thereby ensuring that the behavior allowed by the permission is executed when the user authorizes the permission to the first application. In summary, this solution realizes the movement of the first application under user confirmation and the execution of the behavior allowed by the permission under user authorization by creating the management state declared by the first application and the permission management state of the first application, thereby protecting the personal information of the user in the wearable device. Secondly, the process of creating the management state declared by the first application and the permission management state of the first application is simple, and consumes less computing resources, which can reduce the impact of this solution on the normal operation of the wearable device.

[0021] In combination with the first aspect, in another possible implementation method, the above-mentioned saving the permission management status of the first application based on the permission application file, and setting the permission management status of the first application to a closed state, includes: based on the permission application file, generating and saving a permission whitelist corresponding to the first application, the permission whitelist includes at least one permission; based on the permission whitelist, saving the permission management status of the first application, and setting the permission management status of the first application to a closed state.

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

[0023] In combination with the first aspect, in another possible implementation, the method further includes: in response to the first operation, when the wearable device does not save the permission management status of the first application, displaying a first prompt message and a first interface. The first prompt message is used to prompt that the first application has not applied for the first permission.

[0024] It is understandable that if the wearable device does not save the permission management status of the first application, the first function triggered by the first operation cannot be started normally, and the first prompt information can be displayed to inform the user why the first function cannot be started normally. This can avoid the user's experience that the wearable device does not respond to the first operation due to the user inputting the first operation without displaying the operation interface of the first function and displaying the first interface.

[0025] In combination with the first aspect, in another possible implementation manner, the operating system of the wearable device is a real-time operating system (RTOS), and the first application is a JS application.

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

[0027] In combination with the first aspect, in another possible implementation, the method also 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 recording option; in response to a ninth operation on the behavior recording option, displaying a ninth interface, the ninth interface including at least one behavior information.

[0028] It is understandable that after each application in the wearable device executes the behavior allowed by the permission, the corresponding behavior information (for example, the first behavior information mentioned above) can be saved locally to record the application's use of the permission. The wearable device provides a query entry through the first setting option in the seventh interface for the user to browse all saved behavior information.

[0029] In combination with the first aspect, in another possible implementation, 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 application in at least one application in the wearable device, the declaration switch corresponding to each application is used to modify the management state of the application declaration of each application, and the at least one application includes the first application.

[0030] It is understandable 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, so that the user can update the management status of the first application declaration of the first application, the wearable device can also provide other setting entrances for application declarations, so that the user can update the management status of the first application declaration of the first application through other setting entrances for application declarations. The other setting entrances for application declarations can include the second setting option in the seventh interface, so that the user can enter the tenth interface through the second setting option, and then update the management status of the first application declaration of the first application through the declaration switch corresponding to the first application in the tenth interface.

[0031] In combination with the first aspect, in another possible implementation, 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 application in at least one application in the wearable device, the at least one application including a 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 includes a permission switch corresponding to each permission of at least one permission required by the first application, and the permission switch corresponding to each permission is used to modify the management status of each permission.

[0032] It is understandable that, in addition to displaying the on and off options corresponding to the first permission when the first application needs to use the first permission, so that the user can update the management status of the first permission required by the first application, the wearable device can also provide other setting entries for permissions, so that the user can update the management status of the first permission required by the first application through other setting entries for permissions. Other setting entries for permissions can include the third setting option in the seventh interface, so that the user can enter the eleventh interface through the third setting option, and then enter the twelfth interface through the fourth setting option corresponding to the first application in the eleventh interface; then, the management status of the first permission required by the first application is updated through at least one permission switch corresponding to the permission in the twelfth interface (including the permission switch corresponding to the first permission).

[0033] In a second aspect, a wearable device is provided, the wearable device comprising: a processor, a memory, and a communication interface. The memory and the communication interface are coupled to the processor, the memory is used to store computer program code, and the computer program code includes computer instructions. When the processor executes the computer instructions, the wearable device executes the method described in any one of the first aspects.

[0034] In a third aspect, a computer-readable storage medium is provided, wherein computer instructions are stored in the computer-readable storage medium. When the computer instructions are executed on a wearable device, the wearable device executes the method described in any one of the above-mentioned first aspects.

[0035] In a fourth aspect, a computer program product comprising computer instructions is provided. When the computer instructions are executed on a wearable device, the wearable device executes the method as described in any one of the above-mentioned first aspects.

[0036] In a fifth aspect, a device (for example, the device may be a chip system) is provided, the device including a processor for supporting a wearable device to implement the method described in the first aspect above. In one possible design, the device also includes a memory for storing program instructions and data necessary for the wearable device. When the device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices.

[0037] Among them, the technical effects brought about by any design method in the second to fifth aspects can refer to the technical effects brought about by different design methods in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 A schematic diagram of the structure of a wearable device provided in an embodiment of the present application;

[0039] Figure 2 A system structure diagram of a wearable device provided in an embodiment of the present application;

[0040] Figure 3 A schematic diagram of an application management method provided in an embodiment of the present application Figure 1 ;

[0041] Figure 4 (a) to (f) are schematic diagrams of interfaces for a wearable device to request a user to confirm an application declaration, provided in an embodiment of the present application;

[0042] Figure 5 (a) to (g) are schematic diagrams of an interface for modifying the management status declared by a first application provided in an embodiment of the present application;

[0043] Figure 6(a) to (b) are schematic diagrams of an interface of a wearable device displaying a first application declaration provided by an embodiment of the present application;

[0044] Figure 7 A schematic diagram of an application management method provided in an embodiment of the present application Figure 2 ;

[0045] Figure 8 (a) to (d) are schematic diagrams of interfaces for a wearable device to request a user to authorize permissions, provided in an embodiment of the present application;

[0046] Fig. 9 (a) to (f) are schematic diagrams of an interface for modifying the permission management status of a first application provided in an embodiment of the present application;

[0047] Fig.10 (a) to (b) are schematic diagrams of an interface for viewing behavior information provided in an embodiment of the present application;

[0048] Fig.11 (a) to (e) are schematic diagrams of an interface for uninstalling an application provided in an embodiment of the present application;

[0049] Fig.12 (a) to (e) are schematic diagrams of interfaces of an installation system application provided in an embodiment of the present application;

[0050] Fig.13 A schematic diagram of an application management method provided in an embodiment of the present application Figure 3 . DETAILED DESCRIPTION

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

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

[0053] At present, due to the RTOS system (or RTOS) in terms of function provision compared to the Android system (Android TMTherefore, RTOS systems do not have some functions provided by general operating systems. For example, in order to protect the personal data of users in electronic devices, Android TM General operating systems such as RTOS systems have established multiple different permissions, such as the permission to read location information, the permission to use the microphone, the permission to use the wireless network, etc. After an APP is installed on an electronic device, the APP needs to apply to the general operating system for some permissions. The electronic device can display a notification box to obtain permission authorization for the APP from the user, thereby achieving reasonable control over the APP's usage permissions. However, the RTOS system lacks management of APP application declarations and lacks management of APP permissions.

[0054] Since the RTOS system lacks management of APP application declarations and APP permissions, after installing an APP on a wearable device using the RTOS system, the APP's application declaration is accepted by default, and the APP is allowed to collect the user's personal information in the wearable device at will by default. For example, the APP can use the microphone of the wearable device to collect voice information, and can also read the set location information in the wearable device, etc. As a result, the user's personal information in the wearable device is collected by the APP without the user's permission.

[0055] Furthermore, wearable devices also lack records of some sensitive behaviors of apps. Sensitive behaviors can refer to behaviors related to collecting users' personal information, such as apps reading the location information of wearable devices, apps using the microphone of wearable devices to collect voice information, etc.

[0056] In response to the above problems, an embodiment of the present application provides an application management method. After the wearable device installs each APP, the management state of the application declaration of the APP can be initialized to a canceled state and saved, and the management state of each of the at least one permission required by the APP can also 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 function in the APP. If the wearable device determines that the management state of the application declaration of the APP is a canceled state, and the management state of the permission associated with the function is a closed state, a declaration pop-up window can be displayed to obtain confirmation of the application declaration of the APP from the user, and a permission pop-up window can also be displayed to obtain authorization of the permission associated with the function from the user. Furthermore, the wearable device can only execute the function in the APP when it determines that the management state of the application declaration of the APP is a confirmed state and the management state of the permission associated with the function is an open state.

[0057] By adopting this solution, the wearable device initializes the management state of an APP's application declaration to the canceled state, and initializes the management state of at least one permission required by the APP to the closed state, so as to prevent the APP from collecting the user's personal information in the wearable device without the user's permission. Thus, the user's personal information in the wearable device is effectively protected.

[0058] In addition, while executing the function in the APP, the wearable device can also save behavior information (or sensitive behavior information), which is used to record the usage information of the APP for the permissions associated with the function.

[0059] An embodiment of the present application provides an application management method, which can be applied to a wearable device with a display screen, such as a smart bracelet and a smart watch. The embodiment of the present application does not impose any restrictions on the specific type of the wearable device.

[0060] In the following embodiments, a wearable device is taken as an example to illustrate. Figure 1 A schematic structural diagram of a wearable device provided in an embodiment of the present application is shown.

[0061] like Figure 1 As shown, the smart watch 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, the watch 10 may also include an ambient temperature sensor, an antenna, a wireless fidelity (Wi-Fi) module, a near field communication technology (NFC) module, a global positioning system (GPS) module, a speaker, a gyroscope sensor, and the like.

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

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

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

[0066] The power source 5 is logically connected to the processor 1 through the power management system 4, so that the power management system 4 can manage charging, discharging, power consumption and other functions.

[0067] The display screen 6 may be used to display information output by the smart watch 10 , for example, the desktop interface of the smart watch 10 , or the interface of any APP in the smart watch 10 .

[0068] The touch screen 7, also called a touch panel, can collect touch operations performed by the user of the smart watch 10. The touch panel 7 can be covered on the display screen 6. When the touch panel 7 detects a touch operation acting on the touch panel 7, it is transmitted to the processor 1 to determine the type of the touch event, and then the processor 1 provides a corresponding visual output on the display screen 6 according to the type of the 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. In the following embodiments, a display screen including a touch panel is used as an example for schematic description.

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

[0071] The microphone 9 is also called a microphone. The microphone 9 can convert the sound signal of the smart watch 10 into an electrical signal, which is received by the audio circuit and converted into audio data. The audio circuit can also convert the audio data into an electrical signal, transmit it to the speaker, and convert it into a sound signal for output by the speaker.

[0072] Bluetooth 8, the smart watch 10 can establish a connection with other terminal devices via Bluetooth.

[0073] Understandably, the above Figure 1 The figure is only an exemplary description when the wearable device is in the form of a smart watch. If the wearable device is in other device forms such as a smart bracelet, the structure of the wearable device may include Figure 1 The structure shown in the figure is less than Figure 1 More structures are shown in the figure, which are not limited here.

[0074] It is understandable that the realization of wearable device functions requires not only hardware support but also the cooperation of software architecture. Figure 2As shown, taking the RTOS system used by the wearable device as an example, the software architecture of the wearable device provided in this application may 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).

[0075] In some embodiments, the application layer may include a series of APPs. This series of APPs can be divided into system APPs that come with the wearable device and third-party APPs that the user downloads to the wearable device. For example, Figure 2 As shown, the system APP may include a setting APP, a music APP, a text message APP, and a workout APP, etc.; the third-party APP may include a multimedia playback APP, etc., and the embodiments of the present application do not impose any restrictions on this.

[0076] In some embodiments, the JS application framework layer may include: a JS data binding module, a JS runtime module, and a JS framework module. Among them, the JS data binding module can be used to provide a set of basic data binding capabilities using JS code, including view model instances, classes (subjects), and observers (observers). 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 JS application programming interfaces (application programming interfaces, APIs) and component framework mechanisms using C++ language. The JS framework module may include a user interface component adapter layer (user interface component adapter layer, UI component adapter layer) and an API adapter layer (API adapter layer); the UI component adapter layer may include basic components (basic components), animations (animation), rendering modules (Render modules), routers (router), style management (style manager), and context objects. The API adapter layer may include basic components (basic components), rendering modules (render modules), and style management (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 may include a UI kit (UI kit) for the ability management service (AMS) for application startup, and a bundle management service (BMS) for application updates, etc.

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

[0079] In the embodiment of the present application, the JS framework module may further include a declaration management module, a permission management module, a behavior reporting module, and at least one behavior calling interface. Figure 2 As shown, at least one behavior calling interface may include: an interface for making a phone call, a microphone interface, an interface for sending text messages, a Bluetooth interface, an interface for reading location information, and an interface for reading media audio and video data, etc.

[0080] The declaration management module may be used to save and manage the management status 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 status of all permissions required by each APP in the wearable device. Optionally, the permission management module can be called 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. Optionally, the behavior reporting capability can be called a sensitive behavior log reporting module.

[0083] Each behavior call interface in at least one behavior call interface can be used to control the display of a permission pop-up window for the permission based on the management status of the permission corresponding to the behavior call interface. Optionally, each behavior call interface can also be used to report to the behavior reporting module an event that an APP uses the permission corresponding to the behavior call interface. Optionally, each behavior call interface can be an interface defined in the C++ programming language.

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

[0085] Reference Figure 3 As shown, it is a flowchart of an application management method provided by an embodiment of the present application. Figure 3 As shown, the method may include S301 - S310 .

[0086] S301. When the first APP is not installed, the smart watch obtains an installation package of the first APP in response to triggering an installation operation to install the first APP, and installs the first APP using the installation package of the first APP.

[0087] When the first APP is not installed, the smartwatch may display an application installation interface, which may include an installation option corresponding to the first APP. Then, the smartwatch may receive an installation operation that triggers the installation of the first APP on the application installation interface. For example, the installation operation may be a click operation on the installation option. In response to the installation operation, the smartwatch obtains the installation package of the first APP. After the smartwatch obtains the installation package of the first APP, the first APP may be installed using the installation package of the first APP.

[0088] The first APP may be any APP that can be installed in the smart watch, for example, a system APP or a third-party APP. Figure 1 As shown, the first APP may be a workout APP.

[0089] In some embodiments, the smart watch may include an application market APP, and the application installation interface may be an interface in the application market APP. Alternatively, the application installation interface may also be an interface in other APPs, and the other APPs are APPs in the smart watch that are different from the application market APP.

[0090] In some embodiments, the operating system of the smart watch is RTOS, and all apps (including the first app) in the smart watch may be JS (JavaScript) applications. JS applications generally refer to applications written in JavaScript and running on the smart watch.

[0091] S302. The smart watch parses the installation package of the first APP to obtain a permission application file and an application declaration file, where the permission application file includes at least one permission required by the first APP, and the application declaration file includes a first application declaration of the first APP.

[0092] When the smartwatch uses the installation package of the first APP to install the first APP, the installation package of the first APP can be parsed to obtain the permission application file and the application declaration file. Optionally, the application declaration of the first APP can be called a first application declaration.

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

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

[0095] In some embodiments, if the smartwatch can parse the application declaration file from the installation package of the first APP, the smartwatch can request the user to confirm the application declaration of the first APP when starting the first APP. If the smartwatch cannot obtain the application declaration file from the installation package of the first APP, the smartwatch cannot request the user to confirm the application declaration of the first APP. Furthermore, if the user does not confirm the application declaration of the first APP, the smartwatch cannot start the first APP normally, let alone run the first APP.

[0096] In some embodiments, if the smartwatch can parse the permission application file from the installation package of the first APP, the smartwatch can request the user to obtain authorization for the first APP to use the permission when the first APP needs to use one or more permissions in the permission application file. If the smartwatch cannot obtain the permission application file from the installation package of the first APP, the smartwatch cannot request the user to obtain authorization for the first APP to use the permission when the first APP needs to use the permission in the smartwatch. Furthermore, if the user does not authorize the first APP to use the permission, the first APP cannot use the permission.

[0097] For example, taking the first APP as an exercise APP in a smart watch, such as Figure 1 As shown, the exercise APP may include a permission application file and an application declaration file.

[0098] It should be noted that, in addition to Figure 1 The exercise APP in the smart watch shown includes a permission application file and an application declaration file, and the exercise APP in the smart watch may not include the permission application file and the application declaration file. Optionally, the smart watch parses the permission application file and the application declaration file from the installation package of the exercise APP, and after using the permission application file and the application declaration file, the permission application file and the application declaration file can be deleted.

[0099] S303: After successfully installing the first APP, 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, and saves the management state of the first application declaration.

[0100] After successfully installing the first APP, the declaration management module in the smart watch can generate and save the management status of the first application declaration based on the application declaration file. When the smart watch generates the management status of the first application declaration based on the application declaration file, the management status of the first application declaration can be set to a canceled state.

[0101] It is understandable that after the smart watch successfully installs the first APP, the user has not yet confirmed the application declaration of the first APP. Therefore, the declaration management module can first set the management status of the first application declaration to a canceled state.

[0102] In some embodiments, the smart watch may 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 a permission whitelist corresponding to the first APP based on the permission application file. The permission whitelist includes at least one permission required by the first APP.

[0104] After successfully installing the first APP, the smart watch can also generate and save a permission whitelist corresponding to the first APP based on the permission application file. The permission whitelist can be used as a basis for the smart watch to determine whether to request the user to obtain authorization for the first APP to use any permission.

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

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

[0107] The smartwatch generates and saves the management status of all permissions in the permission whitelist based on the permission whitelist. When the smartwatch generates the permission management status of the first APP based on the permission whitelist, the permission management status of the first APP can be set to a canceled state.

[0108] The permission management state of the first APP includes the management state of all permissions in the permission whitelist, 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 setting the permission management state of the first APP to the cancel state may include: setting all the management states of the permissions required by the first APP to the cancel state.

[0109] It is understandable that after the smart watch successfully installs the first APP, the user has not yet authorized the first APP to use the permissions in the smart watch. Therefore, the smart watch can first set the management status of all permissions required by the first APP to be closed.

[0110] Optionally, different from the description in S304-S305, the smart watch can directly generate the permission management status of the first APP based on the permission application file.

[0111] S306: The smart watch displays a desktop interface, and receives a first startup operation that triggers a first APP on the desktop interface.

[0112] After the smart watch successfully installs the first APP, the displayed desktop interface may include the icon of the first APP. Then, the smart watch may receive a user's click operation on the icon of the first APP. The click operation on the icon of the first APP belongs to the first startup operation of triggering the first APP.

[0113] For example, taking the first APP as an exercise APP in a smart watch, such as Figure 4 As shown in (a) of FIG. 1 , the smart watch 10 displays a desktop interface 410, and the desktop interface 410 includes an icon 411 of the exercise APP. The smart watch 10 can receive a user's click operation on the icon 411 of the exercise APP.

[0114] S307: In response to the first startup operation, the smart watch reads the management status of the first application declaration of the first APP from the declaration management module.

[0115] After the smart watch reads the management status declared by the first application of the first APP from the declaration management module, it can determine whether the management status declared by the first application is a canceled state. If the management status declared by the first application is a canceled state, S308 is executed. If the management status declared by the first application is not a canceled state, or the management status declared by the first application is a confirmed state, the homepage interface of the first APP is displayed.

[0116] S308. When the management status of the first application declaration is a cancel status, the smart watch displays a declaration confirmation interface, wherein the declaration confirmation interface includes the first application declaration and a confirmation option corresponding to the first application declaration, and a cancel option corresponding to the first application declaration.

[0117] In some embodiments, in response to the first startup operation, the smartwatch displays a declaration pop-up window corresponding to the first APP when the management state of the first application declaration of the first APP is a cancel state, so as to obtain confirmation of the first application declaration from the user. The declaration pop-up window may include: a first application declaration, a confirmation option, and a cancel option. Optionally, the interface including the declaration pop-up window may be referred to as a declaration confirmation interface.

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

[0119] However, due to the limited display area of ​​the smart watch 10, only a portion of the content in the declaration pop-up window 420 can be displayed, for example, Figure 4 As shown in (b) of FIG. 1 , the smart watch 10 displays a portion 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 where the declaration pop-up window 420 is located in the smart watch 10 to view other contents in the declaration pop-up window 420, such as the confirmation option 422 and the cancel option 423. Figure 4 As shown in (d) in FIG. 1 , the smart watch 10 displays a confirmation option 422 and a cancel option 423 in the declaration pop-up window 420 in response to an upward 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 declared by the first application is in a canceled state by default when it is saved for the first time. Optionally, saving the management state declared by the first application after the smartwatch generates the management state declared by the first application based on the application declaration file can be called saving the management state declared by the first application for the first time.

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

[0122] When the smartwatch displays a declaration confirmation interface including a confirmation option, it can receive and respond to a click operation on the confirmation option, update the management state of the first application declaration in the declaration management module to a confirmation state, and start the first APP normally. The smartwatch normally starts the first APP including displaying the homepage interface of the first APP.

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

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

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

[0126] For example, Figure 4 As shown in (f) in FIG. 4 , the smart watch 10 continues to display the desktop interface 410 in response to the user clicking the cancel option 423 .

[0127] In some embodiments, in addition to displaying a declaration pop-up window before launching the first APP for the first time after installing the first APP, so that the user can update the management status of the first application declaration of the first APP through the declaration pop-up window, the smart watch can also provide other setting entries for the application declaration, so that the user can update the management status of the first application declaration of the first APP through other setting entries for the application declaration.

[0128] Exemplarily, other setting entries of application declaration may include a first setting entry in the setting APP. The process of a user updating the management status of the first application declaration of the first APP through the first setting entry may include: the smart watch displays a first setting interface in the setting APP, and the first setting interface may include an application and privacy option; the smart watch responds to a click operation on the application and privacy option and displays a second setting interface, and the second setting interface may include a declaration management option; the smart watch may respond to a click operation on the declaration management option and display a third setting interface, and the third setting interface may include a declaration switch corresponding to the first APP, and the user may modify the management status of the first application declaration of the first APP by operating the declaration switch corresponding to the first APP.

[0129] Wherein, in the case where the management status declared by the first application is a canceled state, the declaration switch corresponding to the first APP is displayed as a closed state. At this time, the smart watch can respond to a click operation on the declaration switch corresponding to the first APP, update the saved management status declared by the first application to a confirmed state, and update the declaration switch corresponding to the first APP to an open state. Wherein, in the case where the management status declared by the first application is a confirmed state, the declaration switch corresponding to the first APP is displayed as an open state. At this time, the smart watch can respond to a click operation on the declaration switch corresponding to the first APP, update the saved management status declared by the first application to a canceled state, and update the declaration switch corresponding to the first APP to a closed state.

[0130] Optionally, the third setting interface may include a declaration switch corresponding to each application in all applications included in the smart watch, and the 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 the user modifies the management status of the first application declaration of the first APP to a canceled status by operating the declaration switch corresponding to the first APP, the smart watch 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 a 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 a closed status, or keep the permission management status of the first APP unchanged in a closed status.

[0132] Secondly, when the 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 smart watch is running the first APP in the background, the smart watch also needs to close the first APP running in the background.

[0133] For example, taking the first APP as a training APP in a smartwatch, and the management status declared by the first application of the training APP as a confirmation status, the process of updating the management status declared by the first application of the first APP through the first setting entry in the setting APP is introduced. Figure 5 As shown in (a) of FIG. 1 , the smart watch 10 displays a first setting interface 510 in the setting APP, and the first setting interface 510 may include an application and privacy option 511; the smart watch 10 receives a user's click operation on the application and privacy option 511. Figure 5 As shown in (b), the smart watch 10 displays the second setting interface 520 in response to the click operation on the application and privacy option 511, and the second setting interface 520 may include the declaration management option 521; then, the smart watch 10 receives the click operation on the declaration management option 521. The smart watch 10 may display the fourth setting interface 530 or the fifth setting interface 540 in response to the click operation on the declaration management option 521. The fourth setting interface 530 and the fifth setting interface 540 both belong to the third setting interface.

[0134] like Figure 5 As shown in (c) in the figure, when the management status of the first application declaration of the exercise APP is in the canceled state, the smart watch 10 can display the fourth setting interface 530 in response to the click operation on the declaration management option 521, and the declaration switch 531 corresponding to the exercise APP in the fourth setting interface 530 is in the closed state. Then, in response to the click operation on the declaration switch 531 corresponding to the exercise APP, the smart watch 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 open state. Figure 5 As shown in (d) in FIG. 1 , the declaration switch 531 corresponding to the exercise APP is in the on state.

[0135] like Figure 5 As shown in (e) of FIG. 1 , when the management status of the first application declaration of the exercise APP is in the confirmed state, the smart watch 10 can display the fifth setting interface 540 in response to the click operation on the declaration management option 521, and the declaration switch 541 corresponding to the exercise APP in the fifth setting interface 540 is in the turned-on state. Then, as Figure 5 As shown in (f) of FIG. 1 , the smart watch 10 can respond to a click operation on the declaration switch 541 corresponding to the exercise APP by displaying a close prompt message 550, and the close prompt message 550 is used to prompt that the APP cannot be used normally after the application declaration of the APP is not agreed to. Figure 5 As shown in (g) in FIG. 1 , in response to the user triggering the operation of confirming the cancellation of the first application declaration, the smart watch 10 displays an updated setting interface 560. The updated setting interface 560 does not include the declaration switch 541 corresponding to the exercise APP.

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

[0137] Optionally, if the smart watch does not include a management declaration of an application whose status is a confirmation status, the second setting interface displayed by the smart watch may not include a declaration management option.

[0138] In some embodiments, the declaration pop-up window in the declaration confirmation interface may also include an information collection option for the first APP. The smartwatch receives and responds to a click operation on the information collection option in the declaration confirmation interface, and displays a declaration of the information collection and usage rules of the first APP. For example, taking the first APP as an exercise APP in the smartwatch, Figure 6 As shown in (a) of FIG. 1 , when the smart watch 10 displays the declaration pop-up window 420, the user clicks on the information collection option 424 in the declaration pop-up window 420. Figure 6 As shown in (b) of FIG. 1 , in response to a click operation on the information collection option 424 , the smart watch 10 displays a statement 610 of information collection and usage rules of the exercise APP.

[0139] In some embodiments, the smartwatch can run the first APP if the management status declared by the first application of the first APP is in the confirmed state. When the first APP needs to use one or more permissions in the smartwatch during the running of the first APP, the smartwatch can determine whether to request the user to obtain authorization for the first APP to use the permission based on the permission whitelist corresponding to the first APP and the permission management status of the first APP. Figure 7 As shown, the application management method provided in the embodiment of the present application may also include S701-S709.

[0140] S701. When the management status declared by the first application is a confirmed status, the smart watch displays a first application interface in the first APP.

[0141] When the smartwatch runs the first APP normally, the first application interface can be displayed. For example, the first application interface can be the homepage interface of the first APP.

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

[0143] S702: The smart watch determines, on the first application interface, a first permission associated with the first function in response to a second startup operation that triggers a first function in the first APP.

[0144] In response to the second startup operation, the smart watch may determine one or more permissions associated with the first function. The first permission associated with the first function may include all permissions associated with the first function.

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

[0146] S703: The smart watch searches for the management status of the first permission from the permission management status of the first APP saved by the permission management module. The permission management status of the first APP is closed by default when it is saved for the first time.

[0147] The smart watch may first search for the management status of the first permission in the permission management status of the first APP, and then determine whether to request the user to obtain authorization for the first APP to use the first permission based on the management status of the first permission.

[0148] Optionally, saving the permission management status of the first APP after the smart watch generates the permission management status of the first APP based on the permission application file can be called saving the permission management status of the first APP for the first time.

[0149] In some embodiments, the smart watch may save a permission whitelist corresponding to the first APP and the permission management status of the first APP. The smart watch may first read the permission whitelist corresponding to the first APP from the permission management module, and then determine whether the permission whitelist includes the first permission. If the permission whitelist includes the first permission, the smart watch may read the permission management status of the first APP from the permission management module, and search for the management status of the first permission from the permission management status of the first APP. If the permission whitelist does not include the first permission, the smart watch may not start the first function and display the first prompt information. The first prompt information can be used to prompt that the first APP has not applied for the first permission.

[0150] In some embodiments, if the smart watch does not save the permission whitelist or the permission management status of the first APP, the smart watch may not start the first function and display the first prompt information.

[0151] S704: When the management state of the first permission is closed, the smart watch displays a permission request interface, where the permission request interface includes an enable option corresponding to the first permission and a disable option corresponding to the first permission.

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

[0153] In some embodiments, in response to the second startup operation, the smartwatch displays a permission pop-up window corresponding to the first APP when the management state of the first permission is closed, so as to obtain authorization from the user for the first APP to use the first permission. The permission pop-up window may include: an on option and a off option corresponding to the first permission. Optionally, the interface including the permission pop-up window may be called a permission request interface.

[0154] For example, taking the first permission only including the permission to read location information as an example, Figure 8As shown in (b) of FIG. 1 , when the management state of the permission to read location information is closed, the smart watch 10 displays a permission pop-up window 820 corresponding to the exercise APP. The permission pop-up window 820 may include: prompt information 821 for prompting 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 operation on the enable option, the smart watch calls a behavior calling interface corresponding to the first permission through the first APP to execute a first behavior permitted by the first permission, and displays an operation interface of the first function.

[0156] In response to the click operation on the start option, the smart watch starts the first function and displays the operation interface of the first function in the first APP. When the smart watch starts the first function in the first APP, the first APP can call the behavior calling interface corresponding to the first permission to perform the first behavior allowed by the first permission. For example, the interface for reading location information is called to read the location information of the smart watch, the interface for making a call is called to start the phone APP in the smart watch, the interface for sending SMS is called to start the SMS APP in the smart watch, the Bluetooth interface is called to start the Bluetooth APP in the smart watch, the interface for reading media audio and video data is called to read the media impact data in the smart watch, or the microphone interface is called to start the microphone in the smart watch, etc.

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

[0158] In some embodiments, when the management state of a permission required by an APP in a smartwatch is closed, the behavior calling interface corresponding to the permission cannot be called. When the management state of a permission required by an APP in a smartwatch is open, the APP can call the behavior calling interface corresponding to the permission to perform the behavior allowed by the permission.

[0159] S706: The behavior calling interface corresponding to the first permission in the smart watch reports a first event to the behavior reporting module, where the first event refers to an event in which the first APP executes the first behavior.

[0160] The behavior calling interface corresponding to each permission in the smart watch can not only be used to control whether an APP can execute the behavior allowed by the permission, but also report the first event of the APP executing the behavior allowed by the permission to the behavior reporting module after the APP executes the behavior allowed by the permission.

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

[0162] The first behavior information is used to record the usage information of the first APP for the first permission, and the usage information may include the usage time of the first APP for the first permission. For example, the first behavior information may include: the exercise APP reads the location information of the smart watch 10 at a time.

[0163] S708. In response to the click operation on the enable option, the smart watch updates the management state of the first permission in the permission management state of the first APP to an enable state in the permission management module.

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

[0165] When the smart watch displays the permission request interface including the close option, it can receive and respond to a click operation on the close option, and continue to keep the management state of the first permission in the closed state. When the smart watch continues to keep the management state of the first permission in the closed state, the smart watch may not start the first function and continue to display the first application interface.

[0166] In some embodiments, in response to a click operation 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 be used to prompt that the first function in the first APP cannot be started because the first permission is not authorized to the first APP.

[0167] For example, Figure 8 As shown in (d) in FIG. 1 , when the smart watch 10 displays the permission pop-up window 820, in response to a click operation on the close option 823 in the permission pop-up window 820, a second prompt message 840 is displayed. The second prompt message 840 may include: the exercise APP is not authorized to read the location information, and the running information cannot be started.

[0168] It should be noted that, in the case where the first permission includes multiple permissions, the smart watch can execute the processing of the first permission described in S701-S709 above for each permission in the first permission.

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

[0170] The situation where the first permission is not authorized to the first APP may include: the smart watch does not save the permission whitelist, the smart watch does not save the permission management status of the first APP, the permission whitelist does not include the first permission, and the management status of the first permission is closed. The situation where the first permission is authorized to the first APP may include: the management status of the first permission is open.

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

[0172] Exemplarily, other setting entries for permissions may include a second setting entry in the settings APP. The process in which a user updates the management status of a first permission required by a first APP through the second setting entry may include: the second setting interface in the settings APP displayed by the smartwatch may also include a permission management option; the smartwatch may display a sixth setting interface in response to a click operation on the permission management option, and the sixth setting interface may include a sub-permission management option corresponding to the first APP; the smartwatch displays a seventh setting interface in response to a 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 of at least one permission required by the first APP, and the user may modify the management status of the permission in the permission management status of the first APP by operating the permission switch corresponding to each permission.

[0173] Wherein, in the case where the management status of a permission required by the first APP is in the closed state, the permission switch corresponding to the permission is displayed as closed. At this time, the smart watch can respond to a click operation on the permission switch corresponding to the permission, update the management status of the permission in the permission management status of the first APP to the open state, and update the permission switch corresponding to the permission to the open state. Wherein, in the case where the management status of a permission required by the first APP is in the open state, the permission switch corresponding to the permission is displayed as open. At this time, the smart watch can respond to a click operation on the permission switch corresponding to the permission, update the management status of the permission in the permission management status of the first APP to the closed state, and update the permission switch corresponding to the permission to the closed state.

[0174] Optionally, the sixth setting interface may include a sub-permission management option corresponding to each application in all applications included in the smart watch. The sub-permission management option corresponding to each application is used to trigger and display a permission switch corresponding to each permission in at least one permission required for each application.

[0175] For example, taking the first APP as a training APP in a smartwatch, and the management status declared by the first application of the training APP as the enabled state, the process of updating the management status declared by the first application of the first APP through the second setting entry in the setting APP is introduced. Fig. 9 As shown in (a) of FIG. 1 , the second setting interface 520 displayed by the smart watch 10 may also include a permission management option 522; the smart watch 10 receives a user's click operation on the permission management option 522. Fig. 9 As shown in (b), the smart watch 10 displays the sixth setting interface 910 in response to a click operation on the permission management option 522. The sixth setting interface 910 may include sub-permission management options corresponding to all APPs included in the smart watch 10, for example, a sub-permission management option 911 corresponding to the exercise APP. The smart watch 10 displays the eighth setting interface 920 or the ninth setting interface 930 in response to a click operation on the sub-permission management option 911 corresponding to the exercise APP. The eighth setting interface 920 and the ninth setting interface 930 both belong to the seventh setting interface. Both the eighth setting interface 920 and the ninth setting interface 930 may include a permission switch corresponding to each permission of at least one permission required by the exercise APP, for example, a permission switch corresponding to the permission to read location information. The display states of the permission switches in the eighth setting interface 920 and the ninth setting interface 930 are different.

[0176] like Fig. 9As shown in (c) in FIG. 1 , when the management state of the permission to read location information required by the exercise APP is in the closed state, the smart watch 10 displays the eighth setting interface 920 in response to a click operation on the sub-permission management option 911 corresponding to the exercise APP. The permission switch 921 corresponding to the permission to read location information in the eighth setting interface 920 is in the closed state.

[0177] like Fig. 9 As shown in (d) in FIG. 1 , when the management state of the permission to read location information required by the exercise APP is turned on, the smart watch 10 displays the ninth setting interface 930 in response to a click operation on the sub-permission management option 911 corresponding to the exercise APP, and the permission switch 931 corresponding to the permission to read location information in the ninth setting interface 930 is turned on. Then, as Fig. 9 As shown in (e) of FIG. 1 , the smart watch 10 may display a third prompt message 941, a confirmation close option 942, and a cancel close option 943 in response to a click operation on the permission switch 931 corresponding to the permission to read location information. The third prompt message 941 is used to prompt the user that the exercise APP cannot be used normally after closing the permission to read location information. Fig. 9 As shown in (f), in response to a click operation on the confirmation close option 942, the smart watch updates the management status of the permission to read location information required by the exercise APP to a closed state, and updates the permission switch 931 corresponding to the permission to read location information to a closed state.

[0178] In addition, in response to the click operation on the cancel shutdown option 943 , the smart watch 10 may continue to keep the management state of the permission to read location information required by the exercise APP turned on, and display the ninth setting interface 930 .

[0179] In some embodiments, after each APP in the smartwatch executes the behavior allowed by the permission, the corresponding behavior information (for example, the first behavior information mentioned above) can be saved locally to record the usage information of the APP for the permission. The smartwatch provides a query portal for the user to browse all the saved behavior information.

[0180] Exemplarily, the query entry for behavior information may be located in the settings APP. The process of the user viewing the behavior information through the query entry in the settings APP may include: the second setting interface in the settings APP displayed by the smartwatch may also include a behavior record option; the smartwatch may display the tenth setting interface in response to a click operation on the behavior record option, and the tenth setting interface may include at least one behavior information within a preset time period. Due to the limited display area of ​​the smartwatch, part of the content of at least one behavior information may be displayed, and the user may slide up and down in the area where the tenth setting interface is located to view other content in at least one behavior information.

[0181] For example, taking the first APP as an exercise APP in a smart watch as an example, the process of updating the management status declared by the first application of the first APP through the second setting entry in the setting APP is introduced. Fig.10 As shown in (a) of FIG. 1 , the second setting interface 520 displayed by the smart watch 10 may also include a behavior record option 523; the smart watch 10 receives a user's click operation on the behavior record option 523. Fig.10 As shown in (b), the smart watch 10 displays the tenth setting interface 1010 in response to the click operation on the behavior record option 523. The tenth setting interface 1010 may include at least one behavior information within a week, and the at least one behavior information may include the location information of the smart watch 10 read by the exercise APP at a time.

[0182] In some embodiments, the smart watch supports uninstalling any APP in the smart watch. When the smart watch displays the desktop interface, it can display the editing interface in response to the editing trigger operation that triggers the editing mode. The editing interface may 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 may display an uninstall prompt interface in response to a click operation on an APP icon in the editing interface. The uninstall prompt interface may include a fourth prompt message, a confirmation uninstall option, and a cancel uninstall option. The smart watch may uninstall the APP in response to a click operation on the confirmation uninstall option; or may not uninstall the APP in response to a click operation on the cancel uninstall option.

[0183] The fourth prompt information may be used to prompt the user to confirm whether to uninstall the APP, and may also prompt the installation path of the APP. For example, since the installation paths of the system APP and the third-party APP may 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), it can send a second broadcast message to the declaration management module to control the declaration management module to delete the management status of the APP's application declaration (for example, the management status declared by the first application); it can also send a second broadcast message to the permission management module to control the permission management module to delete the permission management status of the APP.

[0185] For example, Fig.11As shown in (a) of FIG. 1 , 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 player APP. The exercise APP is a system APP, and the multimedia player APP is a third-party APP. Then, the smart watch 10 can receive a long press operation input by the user on the desktop interface 410, which is an edit trigger operation. Fig.11 As shown in (b) of FIG. 1 , the smart watch 10 displays the fifth prompt message 1110 in response to the long press operation. The fifth prompt message 1110 is used to prompt the operation of entering the editing mode and exiting the editing mode. Fig.11 As shown in (c) of FIG. 1 , the smart watch 10 turns off the fifth prompt message 1110 after a certain period of time, and then displays the editing interface 1120. The editing interface 1120 includes an editing mark corresponding to each application icon, for example, an editing mark 1122 corresponding to the icon 1121 of the exercise APP, and an editing mark 1124 corresponding to the icon 1123 of the multimedia playback APP.

[0186] Then, if Fig.11 As shown in (d) in FIG. 1 , the smart watch 10 may display a fourth prompt message 1131 corresponding to the exercise APP, a confirm uninstall option 1132, and a cancel uninstall option 1133 in response to the user clicking the icon 1121 corresponding to the exercise APP. The installation path indicated by the fourth prompt message 1131 corresponding to the exercise APP may be located in the setting APP.

[0187] Or, if Fig.11 As shown in (e), the smart watch 10 can respond to the user's click operation on the icon 1123 corresponding to the multimedia playback APP, and display the fourth prompt information 1141 corresponding to the exercise APP, the confirmation uninstall option 1142 and the cancel uninstall option 1143. The installation path prompted by the fourth prompt information 1141 corresponding to the multimedia playback APP can be located in the application market APP.

[0188] It should be noted that the display styles of the application icons in the editing interface and the application icons in the desktop interface may be different. For example, the application icons in the editing interface may be larger in size, brighter in color, and have thicker lines.

[0189] In some embodiments, in addition to supporting the uninstallation of the system APP in the smart watch, the smart watch can also provide an installation entry for the uninstalled system APP. Exemplarily, the installation entry for the uninstalled system APP can be located in the settings APP.

[0190] For example, taking the uninstalled system APP as an example, the process of reinstalling the uninstalled system APP on a smart watch is introduced. Fig.12As shown in (a) of FIG. 1 , the second setting interface 520 displayed by the smart watch 10 may also include an option 524 for retrieving system applications; the smart watch 10 receives a user's click operation on the option 524 for retrieving system applications. Fig.12 As shown in (b) of FIG. 1 , the smart watch 10 displays the eleventh setting interface 1210 in response to the click operation on the option 524 for retrieving the system application. The eleventh setting interface 1210 may include installation options corresponding to each uninstalled system APP, for example, an installation option 1211 corresponding to the uninstalled exercise APP. Fig.12 As shown in (c) of FIG. 1 , the smart watch 10 displays a sixth prompt message 1220 in response to a click operation on the installation option 1211 corresponding to the exercise APP. The sixth prompt message 1220 is used to prompt that the installation is in progress. Then, as shown in FIG. Fig.12 As shown in (d) in FIG. 1 , when the exercise APP is successfully installed, the smart watch 10 displays the seventh prompt information 1230, and the seventh prompt information 1230 is used to prompt that the exercise APP is successfully installed. Fig.12 As shown in (e), the smart watch 10 may display a twelfth setting interface 1240 after the seventh prompt information 1230. The twelfth setting interface 1240 may include an opening option 1241 corresponding to the exercise APP, and the opening option 1241 corresponding to the exercise APP may be used to start the exercise APP.

[0191] Optionally, if the smart watch does not include the uninstalled system APP, the second setting interface displayed by the smart watch may not include an option to retrieve the system application.

[0192] Reference Fig.13 As shown, it is a flowchart of an application management method provided by an embodiment of the present application. Fig.13 As shown, the method may also include the following S1301-S1305.

[0193] S1301. The smart watch displays a first interface in a first application.

[0194] Exemplarily, the first interface may be the first application interface described above, for example, Figure 8 The first application interface 810 in the exercise APP shown in (a).

[0195] Illustratively, S1301 may include the above-mentioned S701.

[0196] S1302: In response to a first operation on a first interface triggering a first function in a first application, the smart watch determines a first permission associated with the first function.

[0197] Exemplarily, the first operation may be the second start-up operation described above.

[0198] Illustratively, S1302 may include the above-mentioned S702.

[0199] S1303: The smart watch searches for the management status of the first permission in the permission management status of the first application. The permission management status of the first application is closed by default when it is saved for the first time.

[0200] Exemplarily, S1303 may include the above-mentioned S703.

[0201] S1304: When the management state of the first permission is closed, the smart watch displays a second interface, where the second interface includes an opening option corresponding to the first permission.

[0202] Exemplarily, the second interface may be the above-mentioned permission request interface, for example, Figure 8 The interface shown in (b) includes a permission pop-up window 820.

[0203] Exemplarily, S1304 may include the above-mentioned S704.

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

[0205] For example, the second operation may be the above-mentioned click operation on the opening option. The third interface may be the operation interface of the above-mentioned first function, for example, Figure 8 The operation interface 830 for recording operation information shown in (c) in FIG.

[0206] Exemplarily, S1305 may include the above-mentioned S705.

[0207] Optionally, the second interface further includes a close option corresponding to the first permission; after displaying the second interface, the method further includes: in response to a third operation on the close option, displaying the first interface. Exemplarily, the third operation may be the above-mentioned click operation on the close option.

[0208] Optionally, before displaying the first interface in the first application, the method also includes: displaying a fourth interface; the fourth interface includes a desktop interface of the wearable device; receiving a fourth operation that triggers the first application on the fourth interface; in response to the fourth operation, when the management status declared by the first application of the first application is a canceled status, displaying a fifth interface, wherein the management status declared by the first application defaults to a canceled status when it is first saved, and the fifth interface includes the first application declaration and a confirmation option corresponding to the first application declaration; in response to the fifth operation on the confirmation option, updating the management status declared by the first application to a confirmed status, and displaying a sixth interface, the sixth interface including the homepage interface of the first application.

[0209] Exemplarily, the fourth interface may be the above-mentioned desktop interface, for example, Figure 4 The display desktop interface 410 shown in (a) of FIG. 4 may be the first startup operation described above. The fifth interface may be the declaration confirmation interface described above, for example, Figure 4 The interface including the declaration pop-up window 420 shown in (b) of FIG. 6 can be Figure 4 The home page interface 430 of the exercise APP shown in (e) in FIG.

[0210] Optionally, the method also includes: in response to the seventh operation, obtaining an installation package of the first application and installing the first application using the installation package of the first application when the first application is not installed; parsing a permission application file and an 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 status declared by the first application to a canceled status based on the application declaration file, and saving the management status declared by the first application; setting the permission management status of the first application to a closed status based on the permission application file, and saving the permission management status of the first application, the permission management status of the first application including the management status of each permission of at least one permission.

[0211] Exemplarily, the seventh operation may be the above-mentioned installation operation.

[0212] Optionally, the method also 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 recording option; in response to a ninth operation on the behavior recording option, displaying a ninth interface, the ninth interface including at least one behavior information.

[0213] Exemplarily, the seventh interface may be the first setting interface, for example, the first setting interface 510. The first setting option may be the application and privacy option. The eighth interface may be the second setting interface, for example, the second setting interface 520. The ninth interface may 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 application in at least one application in the wearable device, the declaration switch corresponding to each application being used to modify the management state of the application declaration of each application, the at least one application including the first application.

[0215] Exemplarily, the second setting option may be the above-mentioned declaration management option. The tenth interface may be the above-mentioned third setting interface, 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 application in at least one application in the wearable device, the at least one application including a 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 permission in at least one permission required by the first application.

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

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

[0219] The embodiment of the present application can divide the functional modules of the above-mentioned wearable device according to the above-mentioned method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present invention is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0220] An embodiment of the present application also provides a wearable device, which includes: a memory and one or more processors; the memory is coupled to the processor; wherein computer program code is stored in the memory, and the computer program code includes computer instructions, and when the computer instructions are executed by the processor, the wearable device executes the application management method provided in the aforementioned embodiment.

[0221] An embodiment of the present application also provides a computer-readable storage medium, which includes computer instructions. When the computer instructions are executed on a wearable device, the wearable device executes the application management method provided in the aforementioned embodiment.

[0222] An embodiment of the present application also provides a computer program product, which includes executable instructions. When the computer program product is run on a wearable device, the wearable device executes the application management method provided in the above embodiment.

[0223] The present application also provides a chip system, such as Fig.13 As shown, the chip system 1300 includes 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 a memory of a wearable device). For another example, the interface circuit 1302 can be used to send signals to other devices (such as the processor 1301).

[0224] Exemplarily, the interface circuit 1302 can read the instruction stored in the memory and send the instruction to the processor 1301. When the instruction is executed by the processor 1301, the chip system can execute the various steps in the above embodiment. Of course, the chip system can also include other discrete devices, which is not specifically limited in the embodiment of the present application.

[0225] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0226] In the 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 schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0227] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0228] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0229] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0230] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An application management method, characterized in that: Applied to a wearable device, the method comprises: Displaying a first interface in a first application; In response to a first operation triggering a first function in the first application on the first interface, determining a first permission associated with the first function; Searching for the management status of the first permission in the permission management status of the first application, where the permission management status of the first application is closed by default when it is saved for the first time; When the management state of the first permission is closed, displaying a second interface, the second interface including an enabling option corresponding to the first permission; In response to a second operation on the enable option, a third interface is displayed, wherein the third interface includes an operation interface of the first function.

2. The method according to claim 1, characterized in that The second interface further includes a close option corresponding to the first permission; after displaying the second interface, the method further includes: In response to a third operation on the close option, the first interface is displayed.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: While displaying the third interface, executing a first behavior permitted by the first permission; First behavior information is generated and saved, where the first behavior information is used to record usage information of the first permission by the first application.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: In response to the second operation, the management state of the first permission in the permission management state of the first application is updated to an enabled state.

5. The method according to any one of claims 1 to 4, characterized in that 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, on the fourth interface, a fourth operation that triggers the first application; In response to the fourth operation, when the management state of the first application declaration of the first application is in a cancel state, displaying a fifth interface, wherein the management state of the first application declaration is in a cancel state by default when it 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 on the confirmation option, the management status declared by the first application is updated to a confirmation status, and a sixth interface is displayed, wherein the sixth interface includes a homepage interface of the first application.

6. The method according to claim 5, characterized in that The fifth interface also includes a cancel option corresponding to the first application statement; wherein, after displaying the fifth interface, the method further includes: In response to a sixth operation on the cancel option, the fourth interface is displayed.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: If 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 using the installation package of the first application; Parsing the installation package of the first application to obtain a permission application file and an application declaration file, wherein the permission application file includes at least one permission required by the first application, and the application declaration file includes the first application declaration; After the first application is successfully installed, setting the management state declared by the first application to a canceled state based on the application declaration file, and saving the management state declared by the first application; The permission management state of the first application is set to a closed state based on the permission application file, and the permission management state of the first application is saved, where the permission management state of the first application includes the management state of each permission of the at least one permission.

8. The method according to claim 7, characterized in that The step of saving the permission management state of the first application based on the permission application file and setting the permission management state of the first application to a closed state includes: Based on the permission application file, generate and save a permission whitelist corresponding to the first application, where the permission whitelist includes the at least one permission; Based on the permission whitelist, the permission management state of the first application is saved, and the permission management state of the first application is set to a closed state.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: In response to the first operation, when the wearable device does not save the permission management status of the first application, a first prompt message is displayed, and then the first interface is displayed, wherein the first prompt message is used to prompt that the first application has not applied for the first permission.

10. The method according to any one of claims 1 to 9, characterized in that The operating system of the wearable device is a real-time operating system RTOS, and the first application is a JS application.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: Displaying a seventh interface, wherein the seventh interface includes a first setting option; In response to an eighth operation on the first setting option, displaying an eighth interface, wherein the eighth interface includes a behavior recording option; In response to a ninth operation on the behavior recording option, a ninth interface is displayed, wherein the ninth interface includes at least one behavior information.

12. The method according to claim 11, characterized in that The seventh interface includes a second setting option; after displaying the seventh interface, the method further includes: In response to the tenth operation on the second setting option, a tenth interface is displayed, wherein the tenth interface includes a declaration switch corresponding to each application in at least one application in the wearable device, wherein the declaration switch corresponding to each application is used to modify the management status of the application declaration of each application, and the at least one application includes the first application.

13. The method according to claim 11, characterized in that 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 application in at least one application in the wearable device, the at least one application including the first application; In response to the eleventh operation on the fourth setting option corresponding to the first application, a twelfth interface is displayed, and the twelfth interface includes a permission switch corresponding to each permission of at least one permission required by the first application, and the permission switch corresponding to each permission is used to modify the management status of each permission.

14. A wearable device, characterized in that: The wearable device comprises: a processor, a memory and a communication interface; the memory and the communication interface are coupled to the processor, the memory is used to store computer program code, and the computer program code comprises computer instructions; wherein, when the processor executes the computer instructions, the wearable device executes the method as described in any one of claims 1-13.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions; when the computer instructions are executed on the wearable device, the wearable device executes the method according to any one of claims 1 to 13.

16. A chip system, characterized in that: The chip system includes a processor and an interface circuit, and the processor and the interface circuit can be interconnected via lines; wherein the interface circuit is used to receive a signal from a wearable device and send the signal to the processor, and the signal includes a computer instruction; when the processor executes the computer instruction, the chip system executes the method as described in any one of claims 1-13.

Images