Application management method, device and system, chip and medium

Abstract

The invention provides an application management method, device and system, a chip and a medium, and relates to the technical field of electronic device.The method is applied to electronic equipment comprising a first processor and a second processor, when the electronic equipment works in a first mode, the first processor works, and when the electronic equipment works in a second mode, the first processor does not work. The power consumption of the first processor is greater than that of the second processor; the method comprises the steps that a first control is displayed, the first control is used for triggering and displaying a management control capable of managing applications of the electronic equipment in a second mode, and management comprises at least one of installation and updating; the first processor sends the equipment information of the second processor to a server of an application market, and receives first information issued by the server according to the equipment information of the second processor; in response to a triggering operation on the first control, a management control of one or more applications which can be managed by the electronic equipment in the second mode is displayed according to the first information, and the one or more applications comprise the first application; in response to a trigger operation on the management control of the first application, the first processor controls the second processor to perform application management. According to the application, proxy management can be carried out on the application in the other working mode in one working mode, so that the application in the other working mode is not limited to pre-installed applications, and the user experience can be improved.

Description

Technical Field

[0001] This application relates to the field of electronic equipment technology, and in particular to an application management method, device, system, chip, and medium. Background Technology

[0002] Electronic devices can exist in two operating modes. In one mode, the device has more complete functions and supports application installation, while in the other mode, the device's functions are limited and it does not support application installation, requiring pre-installation. However, the number of pre-installed applications is limited, affecting the user experience. Summary of the Invention

[0003] This application provides an application management method, device, system, chip, and medium that can manage (e.g., install, update, etc.) applications in one working mode on behalf of others, so that applications in the other working mode are not limited to pre-installed applications, thereby improving the user experience.

[0004] In a first aspect, embodiments of this application provide an application management method applied to a first electronic device. The first electronic device includes a first processor and a second processor. The first processor operates when the first electronic device is in a first mode, and does not operate when the first electronic device is in a second mode. The power consumption of the first processor is greater than that of the second processor. The application management method includes:

[0005] The first control is displayed to trigger the display of management controls for applications that can be managed by the first electronic device in a second mode, including at least one of installation and update; the first processor sends device information of the second processor to the server of the application market; the first processor receives first information from the server of the application market based on the device information of the second processor; in response to the triggering operation of the first control, the management controls for one or more applications that can be managed by the first electronic device in the second mode are displayed according to the first information, including the first application; in response to the triggering operation of the management control of the first application, the first processor controls the second processor to perform application management.

[0006] In this embodiment, the first processor can manage applications in the second mode, so the second mode does not require the installation of an application market client, and the second processor of the electronic device does not need to have high device capabilities.

[0007] In this embodiment, to manage the application of the electronic device in the first / second mode, the corresponding mode parameters are not transmitted; instead, device information of the first / second processor is transmitted. This embodiment achieves application management without transmitting mode parameters for the two operating modes of the electronic device, thus eliminating the need for developers to understand the two operating modes.

[0008] Optionally, displaying the first control includes: displaying the first control in the first mode; displaying one or more application management controls includes: displaying one or more application management controls in the first mode.

[0009] This embodiment supports users issuing application management requests when the first electronic device is operating in the first mode.

[0010] Optionally, before displaying the first control, the application management method further includes: in the second mode, the second processor, in response to a triggering operation on the displayed target application icon, triggers the first processor to operate, wherein the target application icon is an icon related to the client of the application market.

[0011] This embodiment supports users issuing application management requests when the first electronic device is working in the second mode, and the first electronic device can automatically switch to working in the first mode without the user having to manually switch modes.

[0012] Optionally, before the first processor sends the device information of the second processor to the application market's server, the application management method further includes: the first processor, in response to a triggering operation on the application icon of the application market's client, requesting the device information of the second processor from the second processor.

[0013] This embodiment can obtain the first information in advance before the user triggers the first control, so that the management controls of one or more of the above applications can be displayed in a timely manner when the user triggers the first control.

[0014] Optionally, before the first processor sends the device information of the second processor to the application market's server, the application management method further includes: the first processor, in response to a trigger operation on the first control, requesting the device information of the second processor from the second processor.

[0015] This embodiment can obtain the first information only when the user triggers the first control, thus reducing unnecessary processing steps.

[0016] Optionally, the first processor sends the device information of the second processor to the server of the application market, including: the first processor, in response to a trigger operation on the application icon of the client of the application market or a trigger operation on the first control, sends the pre-acquired device information of the second processor to the server of the application market.

[0017] In this embodiment, the first processor can pre-store the device information of the second processor, so that it is not necessary to frequently request the device information from the second processor.

[0018] Optionally, displaying the first control includes: displaying the first control in the second mode; before displaying one or more application management controls, the application management method further includes: in the second mode, the second processor, in response to a triggering operation on the first control, triggers the first processor to operate.

[0019] This embodiment supports users issuing application management requests when the first electronic device is working in the second mode, and the first electronic device can automatically switch to working in the first mode without the user having to manually switch modes.

[0020] Optionally, displaying the first control includes: displaying the first control in a second mode; the application management method further includes: in the second mode, in response to a triggering operation on the first control, the second processor performs a step for displaying management controls for one or more applications based on pre-acquired first information.

[0021] This embodiment allows users to view the manageable applications of the first electronic device in the second mode when the first electronic device is working in the second mode. The device only switches to the first mode when the user requests to install / update an application in the second mode, thus reducing unnecessary mode switching and affecting the device's battery life.

[0022] Optionally, before the first processor controls the second processor to perform application management, the application management method further includes: in the second mode, the second processor triggers the first processor to work in response to a trigger operation of the management control of the first application.

[0023] This embodiment supports users requesting the installation / update of applications in the second mode as needed when the first electronic device is operating in the second mode. The first electronic device can switch operating modes as needed to respond to the user's request.

[0024] Secondly, embodiments of this application provide an application management method applied to a second electronic device, wherein the second electronic device and a first electronic device are connected; the first electronic device includes a first processor and a second processor, wherein the first processor operates when the first electronic device operates in a first mode, and the first processor does not operate when the first electronic device operates in a second mode, and the power consumption of the first processor is greater than the power consumption of the second processor; the application management method includes:

[0025] Display a second control, which is used to trigger the display of management controls for applications that the first electronic device can manage in a second mode, including at least one of installation and update; send device information of the second processor to the server of the application market; receive first information from the server of the application market based on the device information of the second processor; in response to the triggering operation of the second control, display management controls for one or more applications that the first electronic device can manage in the second mode based on the first information, including the first application; and in response to the triggering operation of the management control of the first application, trigger the first processor to control the second processor to perform application management.

[0026] This embodiment can have the beneficial effects of the method described in the first aspect above, which will not be elaborated here.

[0027] Optionally, in response to a trigger operation on the management control of the first application, triggering the first processor to control the second processor to perform application management includes: in response to a trigger operation on the management control of the first application, when the first electronic device is operating in a second mode, sending a first message to the second processor, the first message being used to trigger the first processor to operate; and triggering the first processor to control the second processor to perform application management.

[0028] This embodiment allows users to request and manage the applications that can run on the first electronic device as needed through an auxiliary device when the first electronic device is working in the second mode. The first electronic device can automatically switch to working in the first mode for application management without the user having to manually switch modes.

[0029] Optionally, the application management method further includes: in response to a trigger operation on the application icon of the client in the application market or a trigger operation on the second control, sending a second message to the first processor, the second message being used to request device information of the second processor; and receiving the device information of the second processor sent by the first processor.

[0030] This embodiment enables a second electronic device to obtain first information without transmitting mode parameters.

[0031] Thirdly, embodiments of this application provide an application management method applied to a first electronic device, wherein the first electronic device and a second electronic device are connected; the first electronic device includes a first processor and a second processor, wherein the first processor operates when the first electronic device operates in a first mode, and the first processor does not operate when the first electronic device operates in a second mode, and the power consumption of the first processor is greater than the power consumption of the second processor; the application management method includes:

[0032] The first processor sends the device information of the second processor to the second electronic device. The device information of the second processor is used to supply the server of the application market to issue first information based on the device information of the second processor. The first information is used to support the display of management controls for one or more applications that the first electronic device can manage in the second mode. Management includes at least one of installation and update. The one or more applications include the first application. In response to the control operation performed by the second electronic device when the management control of the first application is triggered, the first processor controls the second processor to perform application management.

[0033] The application management method in the third aspect corresponds to the application management method in the second aspect above, and can have the beneficial effects of the method described in the second aspect above, which will not be elaborated here.

[0034] Optionally, before the first processor controls the second processor to perform application management, the application management method further includes: in the second mode, the second processor receives a first message sent by the second electronic device, the first message being a message sent by the second electronic device in response to a trigger operation of the management control of the first application when the first electronic device is working in the second mode; the second processor responds to the first message and triggers the first processor to work.

[0035] Optionally, the first processor sends the device information of the second processor to the second electronic device, including: the first processor receiving a second message sent by the second electronic device, the second message being a message sent by the second electronic device in response to a trigger operation on the application icon of the application market client or a trigger operation on a displayed second control, the second control being used to trigger the display of management controls of the first electronic device that can manage applications in the second mode; the first processor responding to the second message sending the device information of the second processor to the second electronic device.

[0036] Fourthly, embodiments of this application provide an application management device applied to a first electronic device. The first electronic device includes a first processor and a second processor. The first processor operates when the first electronic device is in a first mode, and does not operate when the first electronic device is in a second mode. The power consumption of the first processor is greater than that of the second processor. The application management device includes:

[0037] The display module is used to display a first control, which triggers the display of management controls for applications that can be managed by the first electronic device in a second mode, including at least one of installation and update; in response to the triggering operation of the first control, the module displays management controls for one or more applications that can be managed by the first electronic device in the second mode according to first information, wherein the one or more applications include the first application;

[0038] The first processor is used to send the device information of the second processor to the server of the application market; receive the first information sent by the server of the application market based on the device information of the second processor; and control the second processor to perform application management in response to the trigger operation of the management control of the first application.

[0039] Fifthly, embodiments of this application provide an application management device applied to a second electronic device, which is connected to a first electronic device. The first electronic device includes a first processor and a second processor. The first processor operates when the first electronic device is in a first mode, and does not operate when the first electronic device is in a second mode. The power consumption of the first processor is greater than that of the second processor. The application management device includes:

[0040] The display module is used to display a second control, which is used to trigger the display of management controls for applications that can be managed by the first electronic device in a second mode, including at least one of installation and update; in response to the triggering operation of the second control, the module displays management controls for one or more applications that can be managed by the first electronic device in the second mode according to first information, wherein the one or more applications include the first application;

[0041] A communication module is used to connect to a first electronic device; send the device information of the second processor to the server of the application market; and receive first information sent by the server of the application market based on the device information of the second processor.

[0042] The processing module is used to respond to the trigger operation of the management control of the first application, and trigger the first processor to control the second processor to perform application management.

[0043] Sixthly, embodiments of this application provide an application management device applied to a first electronic device, wherein the first electronic device and a second electronic device are connected; the first electronic device includes a first processor and a second processor, wherein the first processor operates when the first electronic device operates in a first mode, and the first processor does not operate when the first electronic device operates in a second mode, and the power consumption of the first processor is greater than the power consumption of the second processor; the application management device includes:

[0044] A communication module for connecting to a second electronic device;

[0045] The first processor is used to send device information of the second processor to the second electronic device. The device information of the second processor is used to supply the server of the application market to issue first information based on the device information of the second processor. The first information is used to support the display of management controls for one or more applications that the first electronic device can manage in the second mode. The management includes at least one of installation and update. The one or more applications include the first application. In response to the control operation executed by the second electronic device when the management control of the first application is triggered, the second processor is controlled to perform application management.

[0046] In a seventh aspect, embodiments of this application provide a first electronic device, the first electronic device including one or more memories for storing computer program instructions and one or more processors, wherein when the computer program instructions are executed by one or more processors, the first electronic device is triggered to perform the method as described in any of the first aspects.

[0047] Eighthly, embodiments of this application provide an application management system, including: an application market server and a smartwatch, the smartwatch being used to perform the methods as described in any of the first aspects.

[0048] In a ninth aspect, embodiments of this application provide a second electronic device, the second electronic device including one or more memories for storing computer program instructions and one or more processors, wherein when the computer program instructions are executed by one or more processors, the second electronic device is triggered to perform the method as described in any of the second aspects.

[0049] In a tenth aspect, embodiments of this application provide a first electronic device, the first electronic device including one or more memories for storing computer program instructions and one or more processors, wherein when the computer program instructions are executed by one or more processors, the first electronic device is triggered to perform the method as described in any of the third aspects.

[0050] Eleventhly, embodiments of this application provide an application management system, including: an application market server, a smartphone, and a smartwatch, wherein the smartphone is used to execute the method as described in any of the second aspects, and the smartwatch is used to execute the method as described in any of the third aspects.

[0051] In a twelfth aspect, embodiments of this application provide an electronic chip, including: a processor for executing computer program instructions stored in a memory, wherein when the computer program instructions are executed by the processor, the electronic chip is triggered to perform a method as described in any of the first aspects.

[0052] In a thirteenth aspect, embodiments of this application provide an electronic chip, including: a processor for executing computer program instructions stored in a memory, wherein when the computer program instructions are executed by the processor, the electronic chip is triggered to perform a method as described in any of the second aspects.

[0053] In a fourteenth aspect, embodiments of this application provide an electronic chip, including: a processor for executing computer program instructions stored in a memory, wherein when the computer program instructions are executed by the processor, the electronic chip is triggered to perform a method as described in any of the third aspects.

[0054] In a fifteenth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the method as described in any of the first aspects.

[0055] In a sixteenth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the method as described in any of the second aspects.

[0056] In a seventeenth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the method as described in any of the third aspects.

[0057] In an eighteenth aspect, embodiments of this application provide a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform the method as described in any of the first aspects.

[0058] In a nineteenth aspect, embodiments of this application provide a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform the method as described in any of the second aspects.

[0059] In a twentieth aspect, embodiments of this application provide a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform the method as described in any of the third aspects.

[0060] The technical effects of the aforementioned aspects can be referenced from each other, and will not be elaborated further here. Attached Figure Description

[0061] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly described below.

[0062] Figure 1aA schematic diagram of a watch interface for displaying installed applications on a smartwatch in smart mode, provided as an embodiment of this application;

[0063] Figure 1b A schematic diagram of a watch interface for displaying installed applications on a smartwatch in ultra-long battery life mode, provided as an embodiment of this application;

[0064] Figure 2a A schematic diagram of a mobile phone interface for displaying installed and manageable applications of a smartwatch in smart mode, provided as an embodiment of this application;

[0065] Figure 2b A schematic diagram of a mobile phone interface for displaying installed applications of a smartwatch in ultra-long battery life mode, provided as an embodiment of this application;

[0066] Figure 3a A schematic diagram illustrating a scenario where a smartwatch, as provided in this application embodiment, performs application management in an unassisted environment;

[0067] Figure 3b A schematic diagram illustrating a scenario where a smartphone performs application management in an unassisted environment, as provided in an embodiment of this application.

[0068] Figures 4a to 4d A schematic diagram of a foldable phone provided in an embodiment of this application;

[0069] Figure 5 An interactive schematic diagram illustrating the application management of the first electronic device in an unassisted scenario, as provided in an embodiment of this application;

[0070] Figure 6a A schematic diagram of a watch interface for displaying a list of apps on a smartwatch in smart mode, provided as an embodiment of this application;

[0071] Figure 6b A schematic diagram of a watch interface for displaying a list of apps on a smartwatch in GT mode, provided as an embodiment of this application;

[0072] Figure 7 A schematic diagram of a mobile phone interface for displaying a list of apps on a foldable phone in external screen mode, provided in an embodiment of this application;

[0073] Figures 8a to 8m A timing diagram showing the application management of the first electronic device provided in the embodiments of this application in an unassisted scenario;

[0074] Figure 9 A schematic diagram illustrating a scenario where a smartwatch, as provided in this application embodiment, performs application management in an assisted environment;

[0075] Figure 10An interactive schematic diagram illustrating the application management of the first electronic device provided in this application embodiment in an assisted scenario;

[0076] Figure 11 A schematic diagram of a mobile phone interface for displaying a list of apps on a smartwatch in smart mode, provided as an embodiment of this application;

[0077] Figures 12a to 12f A timing diagram showing the application management of the first electronic device provided in the embodiments of this application in an auxiliary scenario;

[0078] Figure 13 A flowchart illustrating an application management method provided in this application embodiment;

[0079] Figure 14 A flowchart illustrating another application management method provided in this application embodiment;

[0080] Figure 15 A flowchart illustrating yet another application management method provided in this application embodiment;

[0081] Figure 16 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0082] Figure 17 This is a schematic diagram of the software architecture of an electronic device provided in an embodiment of this application. Detailed Implementation

[0083] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0084] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0085] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0086] It should be understood that the term "at least one" as used in this document refers to one or more, and "more than one" refers to two or more. The term "and / or" as used in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. A and B can be singular or plural. Additionally, the character " / " in this document generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0087] It should be understood that although the terms "first," "second," etc., may be used to describe the set thresholds in the embodiments of this application, these set thresholds should not be limited to these terms. These terms are only used to distinguish the set thresholds from each other. For example, without departing from the scope of the embodiments of this application, the first set threshold may also be referred to as the second set threshold, and similarly, the second set threshold may also be referred to as the first set threshold.

[0088] Electronic devices (such as smartwatches, smartphones, and other terminal devices) may include two processors with different power consumption, designated as a first processor and a second processor, with the first processor consuming more power than the second processor. Thus, the processing performance of the first processor may be superior to that of the second processor. For example, the first processor may be an application processor (AP), and the second processor may be a microcontroller unit (MCU). An application processor can also be called a system-on-a-chip (SoC) or a central processing unit (CPU).

[0089] Based on the different operating states of the two processors, electronic devices can exist in two operating modes: a first mode and a second mode. When the device operates in the first mode, the first processor is active; when the device operates in the second mode, the first processor is inactive, and the second processor is active. Regarding the operating state of the second processor when the device is operating in the first mode, in one example, the second processor is active when the device is operating in the first mode; in another example, the second processor is inactive when the device is operating in the first mode. This is not a limitation.

[0090] Conveniently, the electronic device can display a mode switching control when operating in the first mode, and switch to operating in the second mode when the mode switching control is triggered, and can also display a mode switching control when operating in the second mode, and switch to operating in the first mode when the mode switching control is triggered.

[0091] When an electronic device operates in the first mode, the first processor can run any of the installed applications on the electronic device in the first mode. In other words, the installed applications on the electronic device in the first mode are the applications that the first processor can run when the electronic device is operating in the first mode. Applications may also be called application programs (APPs).

[0092] It is feasible for the installed applications on the electronic device in the first mode to be part of the manageable applications on the electronic device in the first mode. Management may include installation, updates, uninstallation, etc.

[0093] In the first mode, the installable applications are those not installed on the electronic device in the first mode (i.e., the installed applications do not include this application). Once installed, the first processor can run the application when the electronic device is operating in the first mode. The updateable applications in the first mode are those already installed but not updated. Once updated, the first processor can run the updated application when the electronic device is operating in the first mode. The uninstallable applications in the first mode are those already installed but not uninstalled. Once uninstalled, the first processor can no longer run the application when the electronic device is operating in the first mode.

[0094] When the electronic device operates in the second mode, the second processor can run any of the applications installed on the electronic device in the second mode. In other words, the applications installed on the electronic device in the second mode are those that the second processor can run when the electronic device is operating in the second mode.

[0095] It is feasible for the installed applications on the electronic device in the second mode to be part of the manageable applications on the electronic device in the second mode.

[0096] In the second mode, the installable applications are those not installed on the electronic device in the second mode (i.e., the installed applications do not include this application). Once installed, the second processor can run the application when the electronic device is operating in the second mode. The updateable applications in the second mode are those already installed but not updated. Once updated, the second processor can run the updated application when the electronic device is operating in the second mode. The uninstallable applications in the second mode are those already installed but not uninstalled. Once uninstalled, the second processor can no longer run the application when the electronic device is operating in the second mode.

[0097] In one example, the electronic device can be a single-display device with one screen. For example, a single-display device could include a smartwatch (e.g., Figure 3a The smartwatch shown), and non-foldable smartphones (such as...) Figure 3b (such as the smartphone shown).

[0098] Feasibly, when the single-display device operates in the first mode, the display screen is used to display the user interface in the first mode, and when the single-display device operates in the second mode, the display screen is used to display the user interface in the second mode.

[0099] For single-display devices such as smartwatches and non-foldable smartphones (hereinafter referred to as non-foldable smartphones), the first mode can be called smart mode, or other feasible names, such as all-around mode, AP mode, etc., without limitation. The second mode can be called ultra-long battery life mode, or other feasible names, such as super power saving mode, GT (energy saving) mode, MCU mode, etc., without limitation.

[0100] In another example, the electronic device can be a dual-display device with two screens. Exemplarily, a dual-display device can include a foldable smartphone (e.g., Figures 4a to 4d (such as the smartphone shown).

[0101] Unlike smartwatches and non-foldable smartphones, which have a single display, foldable smartphones (hereinafter referred to as foldable phones) can have two displays: an inner screen located on the inside of the device and an outer screen located on the outside. The inner screen is larger, for example, approaching the surface size of the foldable phone when fully unfolded, while the outer screen is smaller. See also Figures 4a to 4d A foldable phone can have an inner screen 401 and an outer screen 402. The inner screen 401 is located on the inside of the phone when it is folded, while the outer screen 402 and the external camera module 403 are both located on the outside of the phone when it is folded.

[0102] It is feasible for a foldable phone to be in an open (or unfolded) state or in a folded state. Figure 4a This diagram illustrates a foldable phone in its open state. Figures 4b to 4d A schematic diagram of a foldable phone in its folded state is shown.

[0103] Feasibly, when the foldable phone is in its open state, it can operate in a first mode, displaying the user interface of the first mode on the inner screen. When the foldable phone is in its folded state, it can operate in a second mode, displaying the user interface of the second mode on the outer screen.

[0104] For dual-display devices such as foldable phones, the first mode can be called the inner screen mode, or other feasible names such as smart mode or AP mode, without limitation. The second mode can be called the outer screen mode, or other feasible names such as ultra-long battery life mode or MCU mode, without limitation.

[0105] Based on the processing performance of the first processor, when the electronic device is operating in the first mode, the first processor can not only run the applications installed on the electronic device in the first mode, but also manage the manageable applications on the electronic device in the first mode.

[0106] Conveniently, when the electronic device is operating in the first mode, application icons of the installed applications in the first mode can be displayed to support users in using applications on demand. In response to a user's triggering operation on an application icon, the first processor can run the installed applications in the first mode.

[0107] For example, when the foldable phone is operating in inner screen mode, the inner screen of the phone can display the application icons of the installed applications on the foldable phone in inner screen mode.

[0108] For example, when the smartwatch is working in smart mode, the watch display can show the application icons of the installed applications in smart mode. The corresponding display interface can be, for example, […]. Figure 1a The interface shown.

[0109] Users can view Figure 1a The watch interface shown displays the apps installed on the smartwatch in smart mode. For example... Figure 1a As shown, the installed applications on a smartwatch in smart mode can include an app store, camera, calendar, music, and other applications.

[0110] Feasibly, the shape of the watch display interface can be as follows: Figure 1a The shape shown is circular. In other implementations, the watch display interface can also be other shapes, such as square, and there is no limitation on this.

[0111] Conveniently, when the electronic device is operating in the first mode, management controls for manageable applications in the first mode can be displayed to support user-managed applications as needed. In response to user-triggered operations on the application management controls, the first processor can manage the application.

[0112] In a feasible manner, the installed applications on the electronic device in the first mode may include a client for an application market. The first processor can run the application market client to display management controls for manageable applications on the electronic device in the first mode, and to manage the manageable applications on the electronic device in the first mode.

[0113] The app store's client has the ability to communicate and interact with the app store's server (such as transmitting manageable applications and application installation packages for electronic devices in the first mode), and can be used to display and download applications suitable for electronic devices. The app store's server can be a server, also known as the app store cloud, and can provide application download-related services to the app store's clients.

[0114] The client application for an app store installed on an electronic device can be an app store app, which can be used to display and download applications suitable for the electronic device itself. An app store app can also be called by other permissible names, such as an app store app, etc., without limitation.

[0115] See Figure 1a If the user clicks the application icon 101 of the application market APP, the first processor can run the application market APP to display the management controls of the manageable applications on the smartwatch in smart mode.

[0116] Alternatively, the app store app icon can be used to open the app store app. For example, the app store app can display its homepage user interface after the user clicks the icon.

[0117] For example, when the foldable phone is operating in inner screen mode, the inner screen can display management controls for manageable applications on the foldable phone in inner screen mode. The corresponding display interface can be, for example, […]. Figure 7 The interface shown.

[0118] For example, when the smartwatch is operating in smart mode, the watch display can show management controls for the manageable applications of the smartwatch in smart mode. The corresponding display interface can be, for example, a... Figure 6a The interface shown.

[0119] Users can view Figure 6a The watch interface shown displays the manageable applications of the smartwatch in smart mode. For example... Figure 6a As shown, the applications that can be installed on a smartwatch in smart mode include: Apps, the updatable applications for smartwatches in smart mode include APP.

[0120] See Figure 6a If the user clicks to install control 601, the smartwatch's primary processor can request data from the app store's server through the app store app. The app's installation package, and then install it based on the installation package. APP. If the user clicks to update control 602, the smartwatch's primary processor can request data from the app store's server through the app store. The new version of the app's installation package, and then based on the new version of the installation package, the already installed... The app is being updated.

[0121] In practice, in addition to the electronic device, the application icons of the installed applications on the electronic device in the first mode can also be displayed through other devices (i.e., auxiliary devices) that are bound to the electronic device.

[0122] The client application for the app store installed on the assistive device can be an app store app, a sports and health app, etc. This app store app can be used to display and download applications suitable for the device itself, as well as applications suitable for other devices bound to the device. The sports and health app can be used to display and download applications suitable for other devices bound to the device. The sports and health app can also be called by other feasible names, and there is no limitation on this.

[0123] For example, a user can pair their smartphone and smartwatch, allowing the smartphone to display the app icons of installed applications on the smartwatch in smart mode. The smartphone paired with the smartwatch is an auxiliary device used to help the smartwatch manage applications, and its function in this solution differs from... Figure 3b The non-foldable smartphone 32 shown is an example.

[0124] See one example. Figure 2a When a smartphone and a smartwatch named "HUAWEI WATCH 4Pro-204" are paired, if the user taps the Health app on the smartphone and the smartwatch is in smart mode, the smartphone can run the Health app and display its interface 203. By viewing the smartphone interface 203, the user can see which applications are installed on the smartwatch in smart mode. Figure 2a As shown, the smartwatch has installed apps in smart mode, including an app store, music, alarm clock, etc.

[0125] In other examples, the display interface of the sports and health app may show a control for triggering the display of installed applications on the smartwatch in smart mode. If the user triggers the control, the sports and health app can switch to displaying the application icons of the installed applications on the smartwatch in smart mode. At this time, the smartwatch can work in smart mode or in ultra-long battery life mode, without limitation.

[0126] In other examples, the smartphone can also display the app icons of the smartwatch's installed apps in smart mode by running an app store app. Users can then view the corresponding phone interface to see which apps are installed on the smartwatch in smart mode.

[0127] In practice, in addition to the electronic device, management controls for manageable applications of the electronic device in the first mode can also be displayed through other devices (i.e., auxiliary devices) that are bound to the electronic device.

[0128] For example, a smartphone paired with the smartwatch can display management controls for manageable applications on the smartwatch in smart mode. In response to a user's triggering of these management controls, the smartphone's primary processor can interact with the app store's server via an app store app / health app to control the smartwatch for application management.

[0129] See one example. Figure 11 When a smartphone and smartwatch are paired, if a user clicks on the app store app on the smartphone, the smartphone can run the app store app to display its homepage. This homepage can include the corresponding smartwatch control 1100. If the user clicks on the corresponding smartwatch control 1100, the app store app can switch to displaying the smartwatch's management controls for manageable applications in smart mode. The corresponding display interface could be, for example, […]. Figure 11 The interface shown.

[0130] See one example. Figure 2a If the user clicks on control 201 of the app store APP, the sports and health APP can switch to display interface 204, which can display management controls for manageable applications of the smartwatch in smart mode.

[0131] Users can view a 204 error on their phone's screen to see which applications are manageable on the smartwatch in smart mode. For example... Figure 2a As shown, the smartwatch in smart mode can install applications including applications named 1 to 7.

[0132] See Figure 2a If the user clicks the install control 202, the smartphone can request the installation package for application name 1 from the app store's server, thereby controlling the smartwatch to manage applications. Specifically, the smartwatch's primary processor can run the app store app and process the application installation based on the installation package for application name 1 sent by the smartphone.

[0133] Based on the processing power of the second processor, when the electronic device operates in the second mode, the second processor can not only run the applications already installed on the electronic device in the second mode, but also uninstall uninstallable applications. However, it typically cannot communicate with the application market server to install / update installable / update applications on the electronic device in the second mode. Applications in the second mode of the electronic device need to be supported through pre-installation.

[0134] Taking smartwatches as an example, a smartwatch operating in ultra-long battery life mode has the same device functions as a sports watch and does not have the ability to install / update applications.

[0135] For example, a smartwatch may include an application processing unit (AP) and an MCU, while a sports watch may include an MCU but not an AP. When the smartwatch operates in smart mode, the AP is active and can run apps installed in the app market within smart mode to interact with the app market's server, thereby enabling the installation / update of apps for the smartwatch in smart mode. When the smartwatch operates in ultra-long battery life mode, the MCU is active while the AP is inactive. The MCU does not interact with the app market's server, thus preventing the installation / update of apps for the smartwatch in ultra-long battery life mode. Unlike smartwatches, which can switch between smart mode and ultra-long battery life mode, sports watches essentially always operate in ultra-long battery life mode. The MCU of a sports watch does not interact with the app market's server, thus preventing the installation / update of apps for the sports watch.

[0136] It is feasible to pre-install third-party applications, such as payment and reading apps, in the electronic device before it leaves the factory, so that the second processor can run the pre-installed applications when the device is working in the second mode. However, the number of pre-installed applications is limited, which affects the user experience.

[0137] Conveniently, when the electronic device is operating in the second mode, application icons of the installed applications in the second mode can be displayed to support users in using applications on demand. In response to a user's triggering action on an application icon, the second processor can run the installed applications in the second mode.

[0138] In the second mode, the installed applications on the electronic device may not include the app store client. This prevents the second processor from interacting with the app store server (e.g., it cannot receive application installation packages from the app store server) and thus prevents application installation / updates. Because the second processor does not perform application installation / update processing in the second mode, the power consumption caused by application installation / updates is avoided, thus achieving an extended battery life.

[0139] For example, when the smartwatch is operating in ultra-long battery life mode, the watch display can show the application icons of the installed applications in ultra-long battery life mode. The corresponding display interface can be, for example, […]. Figure 1b The interface shown. Users can view... Figure 1b The watch interface shown displays the apps installed on the smartwatch in Ultra Battery Life mode. For example... Figure 1b As shown, the smartwatch has installed apps such as calculator, camera, calendar, and music in its ultra-long battery life mode.

[0140] Installed apps on a smartwatch in its extended battery life mode can be pre-installed. When the smartwatch is in extended battery life mode, the secondary processor can run any of the pre-installed apps. See also Figure 1b If the user clicks the calculator control 102, the smartwatch's second processor can run the calculator app and display the calculator app's user interface for the user to use.

[0141] For example, when the foldable phone is operating in external screen mode, the external screen can display the app icons of installed applications in external screen mode, as well as other user interfaces in external screen mode, such as... Figure 4b The dial interface shown is 404. Figure 4c The time and date interface shown is 405. Figure 4d The business status interface 406 shown is shown.

[0142] Feasibly, the shape of the external display interface can be as follows: Figures 4a to 4d The shape shown is circular. In other implementations, the shape of the outer screen display interface can also be other shapes, such as square, and there is no limitation on this.

[0143] In practice, in addition to the electronic device itself, the app icons of installed applications in the second mode can also be displayed via other devices (i.e., auxiliary devices) paired with the electronic device. For example, the app icons of installed applications in the ultra-long battery life mode of the smartwatch can be displayed via a smartphone paired with the smartwatch.

[0144] The smartwatch's installed apps in its ultra-long battery life mode do not include app stores. This means that when the smartwatch is in ultra-long battery life mode, the second processor cannot interact with the app store app / health app on the smartphone (e.g., it cannot receive the app installation package obtained and sent by the smartphone from the app store's server), thus preventing the installation / update of apps.

[0145] In one example, a smartphone could have an app store client installed, such as an app store app or a fitness and health app. See also Figure 2bWhen a smartphone and a smartwatch named "HUAWEI WATCH 4Pro-204" are paired, if the user taps the Health app and the smartwatch is in long battery life mode, the smartphone can run the Health app and display its interface 205. By viewing interface 205, the user can see which applications are installed on the smartwatch in long battery life mode. Figure 2b As shown, the smartwatch's installed apps in ultra-long battery life mode include music, alarm clock, etc.

[0146] In other examples, the display interface of the sports and health app may show a control for triggering the display of installed applications on the smartwatch in the ultra-long battery life mode. If the user triggers the control, the sports and health app can switch to displaying the application icons of the installed applications on the smartwatch in the ultra-long battery life mode. At this time, the smartwatch can work in either ultra-long battery life mode or smart mode, without limitation.

[0147] In other examples, smartphones can also display the smartwatch's installed apps in ultra-long battery life mode by running an app store app.

[0148] As can be seen from the above, electronic devices in the first mode have more complete functions (e.g., the device can interact with the app store's server) and support app installation. However, in the second mode, the device's functions are limited (e.g., the electronic device cannot interact with the app store's server) and does not support app installation. Apps in the second mode must be pre-installed. Thus, when an electronic device is operating in the second mode, users cannot install other apps in the second mode as needed, resulting in a poor user experience.

[0149] To support users in installing applications on their electronic devices in the second mode as needed, an application can have two installation packages, corresponding to the first mode and the second mode respectively. These two installation packages can be referred to as the regular version installation package and the power-saving version installation package.

[0150] To meet the extended battery life requirements of the second mode, the application functionality of the power-saving version installation package is only a subset of the application functionality of the regular version installation package. For example, the application functionality of the regular version installation package for an application (e.g., application a) may include 10 capabilities: call capability, network access capability, audio capability, location capability, video capability, camera capability, 3D (3D) animation, basic controls, map capability, and sensor capability. However, the power-saving version installation package for application a may only include 3 of these 10 capabilities: audio capability, location capability, and basic controls.

[0151] In a feasible scenario, when the electronic device is operating in the first mode, the first processor can run an app store app to simultaneously display both the regular version installation control and the power-saving version installation control for the same app. This example uses app installation; the specific implementation logic also applies to app updates.

[0152] Since an application has two installation packages corresponding to the first and second modes respectively, when a user clicks the install control to request the application installation package for the corresponding mode, the electronic device sends the mode parameters of that mode to the application market's server. Upon receiving the mode parameters, the application market's server can then distribute the application installation package for that mode.

[0153] For example, if a user clicks on the regular version installation control for application A, the first processor can send the mode parameters of the first mode to the application market's server, and obtain the regular version installation package of application A issued by the application market's server based on the mode parameters of the first mode. Then, based on the regular version installation package of application A, the first processor installs application A in the first mode. When the device is operating in the first mode, the first processor can run application A in the first mode to support the user in using the aforementioned 10 capabilities.

[0154] For example, if a user clicks the power-saving version installation control for application A, the first processor can send the mode parameters of the second mode to the application market's server and obtain the power-saving version installation package of application A issued by the application market's server based on the mode parameters of the second mode. Then, based on the power-saving version installation package of application A, the first processor controls the second processor to install application A in the second mode. When the device is working in the second mode, the second processor can run application A in the second mode to support the user in using the above three capabilities.

[0155] As can be seen, in the above implementation scheme where an application has two installation packages, when the device is working in the first mode, the user can install the application in the second mode as needed. However, in this implementation, developers of syscap (SystemCapability), the application, the application market server, and the IDE (Integrated Development Environment) tools all need to understand both working modes. For example, an application developer needs to understand the differences in application functionality between the two working modes and develop both a regular version installation package and a power-saving version installation package for the same application. Due to the large number of applications that can be installed on the device, this solution is quite difficult to implement.

[0156] To support users in installing applications on their electronic devices in the second mode as needed, the installed applications on the electronic devices in the second mode can be configured to include app stores. Furthermore, the second processor of the electronic devices must have high device capabilities, such as the ability to connect to the internet independently and support HTTPS (Hypertext Transfer Protocol Secure) file downloads.

[0157] Feasibly, when the electronic device is operating in the second mode, the second processor can display the icon of the installed app store. If the user clicks the app store icon, the second processor can run the app store to display the installation controls for installable applications in the second mode. This example uses app installation; the specific implementation logic also applies to app updates.

[0158] If the user clicks the application's installation control, the second processor can request the application installation package from the application market's server through the application market APP, and then install the application according to the installation package, thereby completing the on-demand installation of the application in the second mode.

[0159] It is evident that in the above-mentioned implementation scheme of interaction between the second processor and the application market server, the second mode requires the application market APP to be installed and has high requirements for the device capabilities of the second processor, but the current device capabilities are difficult to meet the requirements of the scheme.

[0160] To support users in installing / updating applications on their electronic devices as needed in the second mode, this embodiment of the application can include an application market client installed on the electronic device in the first mode, and a proxy module for the application market client installed in the second mode. The application market client manages the applications in the second mode through this proxy module. Management can include installation, updates, and uninstallation. Thus, in the second mode, it is not necessary to install the application market client, and the second processor of the electronic device does not need to have high device capabilities, such as supporting independent network connectivity or file downloads.

[0161] Unlike app store clients, which have the ability to communicate and interact with the app store's server, the proxy module of the app store client does not have the ability to communicate and interact with the app store's server, but it can have the ability to communicate and interact with the app store's client, such as delivering application installation packages.

[0162] In one example, the proxy module for the app store client can be a Launcher. A Launcher is the desktop launcher in the Android system; the Android system's desktop UI (User Interface) can be collectively referred to as a Launcher.

[0163] This application embodiment manages applications in the second mode by using a client agent from an application market, enabling the second mode to support a rich ecosystem of applications, thus improving the user experience. Furthermore, this technology does not require upgrading the relatively weak hardware and software corresponding to the second mode, thereby reducing product costs.

[0164] In this embodiment of the application, in order to manage the application of electronic devices in the first / second mode, the client of the application market does not transmit the corresponding mode parameters, but transmits the device information of the first / second processor.

[0165] In one embodiment, the device information of the first / second processor may include one or more of the following: device type of the first / second processor, device OS (operating system) version number, API (Application Programming Interface) level, device unique code, device name, etc.

[0166] For example, a smartwatch includes an application processor (AP) and an MCU. The AP's device information includes "device type is wearable, device OS version number is HMOS5.0, API level is 12", and the MCU's device information includes "device type is litewearable, device OS version number is HMOS5.0, API level is 10". Here, litewearable can represent a lightweight HarmonyOS device, while wearable can represent a fully HarmonyOS-enabled device; the two types of devices have different performance characteristics.

[0167] For example, the foldable phone includes an inner screen-side processor and an outer screen-side processor. The device information of the inner screen-side processor includes "device type is phone, device OS version number is HMOS5.0, and API level is 12". The device information of the outer screen-side processor includes "device type is litewearable, device OS version number is HMOS5.0, and API level is 10".

[0168] The device information of the first processor can be used to obtain the applications that can run on the first processor, i.e., to obtain the manageable applications of the electronic device in the first mode. Similarly, the device information of the second processor can be used to obtain the applications that can run on the second processor, i.e., to obtain the manageable applications of the electronic device in the second mode. This application embodiment maps different operating modes of the electronic device to different device types of the processor within the electronic device, thus supporting the management of ecosystem applications in both operating modes.

[0169] The manageable applications in the first mode of an electronic device are those that the first processor can manage when the electronic device is operating in the first mode. Taking the installable applications in the first mode as an example, when the electronic device is operating in the first mode, the first processor can install the application, and after the application is installed, the first processor can run the application when the device is operating in the first mode.

[0170] The manageable applications in the second mode of an electronic device are those that the first processor can manage when the electronic device is operating in the first mode. Taking the installable applications in the second mode as an example, when the electronic device is operating in the first mode, the first processor can install the application on behalf of the device. After the application is installed, the second processor can run the application when the device is operating in the second mode.

[0171] It is feasible to have two applications with partially identical functionalities. One application is used by the electronic device in its first mode, and the other application is used in its second mode, where the functionality of the application in the second mode is a subset of the functionality of the application in the first mode. For example, a smartwatch in its ultra-long battery life mode... The function is for smartwatches in smart mode. Part of the functionality.

[0172] Feasibly, two applications with partially identical functionality can be considered as two independent applications, rather than two versions of the same application. The two applications can have the same application name, application icon, etc., or they can have different application names, application icons, etc., without limitation. For example, see... Figure 1a and Figure 1b The music app icon 103 in smart mode and the music app icon 104 in ultra-long battery life mode of smartwatch can be the same.

[0173] Feasibly, to support users in managing the applications of electronic devices in the first / second modes on demand, the application market client can report the corresponding first / second processor device information to the application market server based on the mapping relationship between the different operating modes of the electronic device and the device information of different processors in the electronic device. Specifically, the first mode can be mapped to the device information of the first processor, and the second mode can be mapped to the device information of the second processor.

[0174] The app store's server can distribute manageable applications (e.g., a list of apps in the first / second mode) to the electronic device based on the device information of the first / second processor. The app store's client, based on this list, can display management controls for the manageable applications in the first / second mode, allowing users to submit application management requests as needed. In response to user application management requests, the app store's client can manage applications in the first mode or act as a proxy for managing applications in the second mode.

[0175] In a feasible manner, the app store's client can determine whether the application requested by the user is an application in the first mode or the second mode. If the user requests to manage an application in the first mode, the app store's client can manage that application. If the user requests to manage an application in the second mode, the app store's client can trigger the proxy module to manage that application, thereby achieving proxy management of applications in the second mode. For example, if the application installation package received by the app store's client is an installation package for an application in the first mode, it can perform application installation processing according to the application installation package. Conversely, if it is an installation package for an application in the second mode, it sends the application installation package to the proxy module, which can then perform application installation processing according to the application installation package.

[0176] For example, the list of apps on a smartwatch in smart mode may include APP and The user interface for displaying the list of apps in the first processor can be, for example,... Figure 6a The interface shown contains... APP installation control 601 and App update control 602.

[0177] For example, the list of apps on a smartwatch in ultra-long battery life mode may include For apps and scientific calculator apps, the first processor displays the user interface of the app list, for example, it can be... Figure 6b The interface shown contains... The uninstallation control for the app and the installation control for the scientific calculator app both returned a 604 error.

[0178] Feasible, such as Figure 6b As shown, this can be achieved through a pop-up window (e.g.) Figure 6b As shown in pop-up 605, the list of apps in the ultra-long battery life mode is overlaid on the display interface that displays the list of apps in smart mode.

[0179] See Figure 6bIf the user clicks to install control 604, the smartwatch's first processor can request the installation package of the scientific calculator app from the app store's server through the app store's client, and then send the installation package to the agent module of the app store's client to trigger the agent module to install the scientific calculator app according to the installation package.

[0180] Feasibly, the client of the application market may include two controls: a control corresponding to the first mode and a control corresponding to the second mode. The control corresponding to the first mode is used by the user to trigger and request the display of management controls for manageable applications on the electronic device in the first mode, and the control corresponding to the second mode is used by the user to trigger and request the display of management controls for manageable applications on the electronic device in the second mode.

[0181] As can be seen, this application embodiment can achieve application management without transmitting mode parameters of the two working modes of the electronic device. Therefore, developers of syscap, applications, application market servers, and IDE tools do not need to understand the two working modes. For example, an application developer does not need to understand the differences in application functions between the two working modes, and can develop only the installation package of the application in the first mode, or only the installation package of the application in the second mode.

[0182] In one embodiment, the electronic device can manage applications independently without the assistance of other devices. For example, the electronic device may be a smartwatch, a non-foldable smartphone, a foldable phone, etc.

[0183] In unassisted scenarios, electronic devices can run application market clients to respond to user management requests for applications on the electronic device in the first / second mode.

[0184] In unassisted scenarios, the client applications of the app store installed on the electronic device (e.g.) Figure 3a or Figure 3b The application market client 1) can include controls corresponding to the first mode and controls corresponding to the second mode. If the user triggers the control corresponding to the first / second mode, the electronic device can display the management controls for the manageable applications in the first / second mode.

[0185] In one example, the electronic device is a smartwatch. The app store on the smartwatch includes controls for a first mode and controls for a second mode. The controls for the first mode can be, for example,... Figure 6a The "Smart Mode" control 603 shown can be a control for the second mode, such as... Figure 6b The “GT Mode” control 606 is shown in the figure. In other embodiments, the two controls may also be called by other feasible names, which are not limited thereto.

[0186] exist Figure 6aIn the interface shown, the "Smart Mode" control 603 is used to identify the manageable applications of the smartwatch displayed in Smart Mode, and the "GT Mode" control is used by the user to request a switch to display the manageable applications of the smartwatch in Ultra Long Battery Life Mode.

[0187] exist Figure 6b In the interface shown, the "GT Mode" control 606 is used to identify the manageable applications displayed on the smartwatch in the ultra-long battery life mode, and the "Smart Mode" control is used by the user to request a switch to display the manageable applications of the smartwatch in the smart mode.

[0188] In one example, the electronic device is a foldable phone. The app store on the foldable phone includes controls for a first mode and controls for a second mode. The controls for the first mode can be, for example,... Figure 7 The inner screen control 702 shown can be a control corresponding to the second mode, such as... Figure 7 The external screen control 701 is shown in the figure. In other embodiments, the two controls may also be called by other feasible names, which are not limited thereto.

[0189] exist Figure 7 In the interface shown, the control 701 corresponding to the outer screen mode is used to identify the manageable applications of the foldable phone displayed in the outer screen mode, and the control 702 corresponding to the inner screen mode is used by the user to request a switch to display the manageable applications of the foldable phone in the inner screen mode.

[0190] See Figure 3a The application management scenario diagram shown indicates that the smartwatch 31 includes a first processor 311 (e.g., AP) and a second processor 312 (e.g., MCU). The installed applications of the smartwatch 31 in smart mode include the client 1 of the application market.

[0191] like Figure 3a As shown, when the smartwatch 31 is operating in smart mode, the first processor 311 can communicate and interact with the application market server 30 by running the application market client 1 (such as an application market APP) to obtain application management information, such as an APP list and application installation packages. Based on this information, the processor can manage the applications on the smartwatch 31 in smart mode or delegate the management of applications on the smartwatch 31 in ultra-long battery life mode. Specific technical implementations can be found in the descriptions of other embodiments of this application and will not be detailed here.

[0192] See Figure 3bThe application management scenario diagram shown includes a smartphone 32 with a first processor 321 (e.g., AP) and a second processor 322 (e.g., MCU). The installed applications of the smartphone 32 in smart mode include the client 1 of the application market.

[0193] like Figure 3b As shown, when the smartphone 32 is operating in smart mode, the first processor 321 communicates and interacts with the application market server 30 by running the application market client 1 (e.g., an application market APP) to obtain application management information, such as an APP list and application installation packages. Based on this information, the processor can manage the applications on the smartphone 32 in smart mode or delegate the management of applications on the smartphone 32 in ultra-long battery life mode. Specific technical implementations can be found in the descriptions of other embodiments of this application and will not be detailed here.

[0194] In other embodiments, Figure 3b The non-folding smartphone 32 in the application management scenario shown can also be replaced with a folding phone, such as... Figure 4a The foldable phone shown.

[0195] In another embodiment, the electronic device may also perform application management with the assistance of other devices. For example, the electronic device may be a smartwatch, and the assisting device may be a smartphone.

[0196] The auxiliary device may include one processor or two processors; for example, the auxiliary device may be... Figure 3b The non-folding smartphone shown Figure 4a The foldable phones shown are not limited to this.

[0197] In assistive scenarios, assistive devices can run app store clients to respond to user management requests for applications on electronic devices in the first / second mode.

[0198] In assistive scenarios, the client applications of the app store installed on the assistive device (e.g., Figure 9 The application market client 2) may include controls corresponding to the first mode and controls corresponding to the second mode. If the user triggers the control corresponding to the first / second mode, the auxiliary device can display the management controls of the manageable applications of the electronic device in the first / second mode.

[0199] In one example, the electronic device is a smartwatch, the auxiliary device is a smartphone, and the app store on the smartphone includes controls corresponding to the first mode and controls corresponding to the second mode. The controls corresponding to the first mode can be, for example,... Figure 11 The "Smart Mode" control 1101 shown can be a control for the second mode, such as... Figure 11The “GT Mode” control 1102 is shown in the figure. In other embodiments, the two controls may also be called by other feasible names, which are not limited thereto.

[0200] In scenarios with auxiliary functions, it is not necessary to specify whether the client application of the app store installed on the electronic device includes these two controls.

[0201] See Figure 9 The illustrated application management scenario diagram shows that the smartwatch 31 includes a first processor 311 (e.g., AP) and a second processor 312 (e.g., MCU). The smartwatch 31 in smart mode has installed applications including an application market client 1 (e.g., an application market APP). The smartphone 33 has an application market client 2 (e.g., an application market APP, a sports and health APP) installed.

[0202] like Figure 9 As shown, the processor 331 in the smartphone 33 can communicate and interact with the application market server 30 by running the application market client 2 to obtain application management information, such as an app list and application installation packages. Based on this information, the processor 331 can assist the first processor 311 in managing applications on the smartwatch 31 in smart mode, or assist the first processor 311 in managing applications on the smartwatch 31 in ultra-long battery life mode. Specific technical implementations can be found in the descriptions of other embodiments of this application, and will not be detailed here.

[0203] Figure 9 In the example shown, the assisted electronic device is a smartwatch. Based on the same technical implementation logic, in other feasible examples, the assisted electronic device can also be other types of electronic devices such as smartphones, and there is no limitation on this.

[0204] The following sections describe some embodiments of this application for application management in both unassisted and assisted scenarios. The implementation methods and beneficial effects of different embodiments can be referenced interchangeably. Although described separately, multiple embodiments can be implemented simultaneously on the same electronic device, and this application does not limit this.

[0205] In unassisted scenarios, electronic devices (e.g. Figure 5 The first electronic device shown can manage the manageable applications of the electronic device in the first / second mode without the assistance of other devices.

[0206] See Figure 5 The first electronic device includes a first processor (such as an application processor, AP) and a second processor (such as an MCU), wherein the processing performance of the first processor is superior to that of the second processor. The first electronic device can be a smartwatch, a non-foldable smartphone, a foldable phone, etc. Figure 5The intelligent mode shown represents the first mode. Figure 5 The extended battery life mode shown indicates the second mode.

[0207] The first electronic device in the first mode has installed applications including an application market client 1 (e.g., an application market APP), and the first electronic device in the second mode has installed applications including an application market client proxy module (e.g., a launcher).

[0208] When the first electronic device is operating in the first mode, the first processor is working. The first processor can run the applications installed on the first electronic device in the first mode, and can also manage the manageable applications on the first electronic device in the first mode and manage the manageable applications on the first electronic device in the second mode by running the application market client 1 (hereinafter referred to as client 1).

[0209] When the first electronic device is operating in the second mode, the first processor is not working, but the second processor is working and can run the applications installed on the first electronic device in the second mode.

[0210] See Figure 5 In a feasible scenario, the first electronic device may execute some or all of the following steps 5.1 to 5.14 to achieve application management. The step numbers are used to distinguish different steps, but not to limit the order in which the steps are executed.

[0211] Step 5.1: The first processor receives the user's trigger operation to start client 1 and starts client 1.

[0212] For example, the first electronic device is a smartwatch, and the application icon of client 1 is... Figure 1a The application icon 101 shown can be clicked by the user to request the launch of client 1.

[0213] Feasibly, after client 1 starts, it can display controls corresponding to Smart Mode and Ultra-Long Battery Life Mode. When a user needs to manage applications in Smart Mode, they can click the control corresponding to Smart Mode to request the display of the app list in Smart Mode. When a user needs to manage applications in Ultra-Long Battery Life Mode, they can click the control corresponding to Ultra-Long Battery Life Mode to request the display of the app list in Ultra-Long Battery Life Mode.

[0214] Step 5.2: The first processor receives the user's trigger operation on the control corresponding to the smart / ultra-long battery life mode displayed on client 1.

[0215] For example, the first electronic device is a smartwatch, and the control corresponding to the smart mode is... Figure 6aThe "Smart Mode" control 603 shown is the control corresponding to the ultra-long battery life mode. Figure 6b The “GT Mode” control 606 shown is shown.

[0216] Feasibly, if the user triggers the control corresponding to the smart mode, client 1 can switch to displaying the app list of the first electronic device in smart mode. If the user triggers the control corresponding to the ultra-long battery life mode, client 1 can switch to displaying the app list of the first electronic device in ultra-long battery life mode.

[0217] Step 5.3: The first processor runs client 1 to display a list of apps in the smart / long battery life mode of the first electronic device. The display interface of the app list includes management controls (install / update / uninstall controls) for manageable applications of the first electronic device in the smart / long battery life mode, and receives user trigger operations on the management controls.

[0218] For example, the first electronic device is a smartwatch, and the display interface of the app list on the smartwatch in smart mode is as follows: Figure 6a The interface shown is the app list display interface of the smartwatch in ultra-long battery life mode. Figure 6b The interface shown.

[0219] Feasibly, if a user clicks the install / update control for an application in smart mode, the first processor can request the application installation package from the application market's server and install / update the application according to the installation package. If the user clicks the install / update control for an application in ultra-long battery life mode, the first processor can request the application installation package from the application market's server, send the application installation package to the application market's client's proxy module (hereinafter referred to as the proxy module), and trigger the proxy module to install / update the application according to the installation package. That is, the first processor acts as an agent for installing / updating applications in ultra-long battery life mode.

[0220] Feasibly, if the user clicks the uninstall control of an application in smart mode, the first processor can uninstall the application. If the user clicks the uninstall control of an application in ultra-long battery life mode, the first processor can trigger the agent module to uninstall the application, that is, the first processor acts as an agent to uninstall the application in ultra-long battery life mode.

[0221] Step 5.4: The first processor reports the device information of the first processor and / or the second processor to the server of the application market, and receives the list of apps of the first electronic device in the smart / ultra-long battery life mode issued by the server of the application market based on the device information of the first processor and / or the second processor. The list of apps includes the manageable applications of the first electronic device in the smart / ultra-long battery life mode.

[0222] In one example, the first processor can report the real-time device information of the second processor to the application market's server. For instance, the first processor can obtain the second processor's device information in real-time through a proxy module when the user launches client 1, or it can obtain the second processor's device information in real-time through the proxy module when the user clicks the control corresponding to the extended battery life mode.

[0223] In another example, the first processor can report the pre-configured device information of the second processor to the application market's server. For instance, the device information of the second processor can be pre-configured before the device leaves the factory.

[0224] In another example, the first processor can report the device information of the second processor, which it has acquired and recorded in advance, to the application market's server. For instance, the first processor can acquire the device information of the second processor during interaction with it and record it the first time it acquires the device information.

[0225] In one example, the first processor can report its device information to request a list of apps in smart mode, and report the second processor's device information to request a list of apps in ultra-long battery life mode.

[0226] In another example, the first processor can report its device information to request both the app list for smart mode and the app list for extended battery life mode. For instance, when the user launches client 1, the first processor can report its device information and receive both app lists from the app store's server based on that information. If the user then clicks the control corresponding to smart mode, the app list for smart mode will be displayed on client 1. If the user then clicks the control corresponding to extended battery life mode, the app list for extended battery life mode will be displayed on client 1.

[0227] In one example, the first processor can send a message to the app store's server requesting a list of apps. This message may carry device information for the first processor and / or the second processor. In other feasible examples, the first processor may also send the device information for the second processor to the app store's server to indicate a request for a list of apps in the extended battery life mode.

[0228] Step 5.5: The first processor requests the application of the first electronic device in smart / long battery life mode from the application market server, and receives the application installation package sent by the application market server.

[0229] It is feasible for the first processor to request the application installation package from the application market's server when the user clicks to install or update the control.

[0230] Step 5.6: The first processor triggers the buddle manager system (BMS) to manage the application of the first electronic device in smart mode by running client 1.

[0231] Feasibly, in response to a user's triggering action on the install / update control, client 1 can trigger the package management system to install / update the application based on the application installation package distributed by the application market's server. In response to a user's triggering action on the uninstall control, client 1 can trigger the package management system to uninstall the application.

[0232] Step 5.7: The first processor obtains the device information of the second processor sent by the agent module by running client 1.

[0233] Step 5.8: The first processor sends the list of apps in the ultra-long battery life mode of the first electronic device to the agent module by running client 1.

[0234] Feasibly, the proxy module can receive and store the list of apps in the long battery life mode, and display the stored list of apps when the user clicks the control corresponding to the long battery life mode displayed by the proxy module.

[0235] Step 5.9: The first processor sends application management information (such as the installation package / uninstallation notification of the application of the first electronic device in the ultra-long battery life mode) to the agent module by running client 1.

[0236] The first processor can send the application management information of the application in the ultra-long battery life mode to the agent module through client 1, so as to trigger the agent module to manage the application in the ultra-long battery life mode, thereby realizing the agent management of the application in the ultra-long battery life mode.

[0237] Step 5.10: The second processor triggers the first processor to run client 1.

[0238] Feasibly, when the device is operating in ultra-long battery life mode, the second processor can trigger the first processor to run client 1 when the first processor needs to manage applications in ultra-long battery life mode (for example, when any of steps 5.11 to 5.13 exists). At this time, the device's operating mode switches from ultra-long battery life mode to smart mode.

[0239] Step 5.11: The second processor receives the user's trigger operation to start the agent module and starts the agent module.

[0240] In one example, the agent module can display the controls corresponding to the extended battery life mode after it is started.

[0241] In another example, after the proxy module starts, it may not display the controls corresponding to the long battery life mode. Instead, it may trigger client 1 to run, and then display the controls corresponding to the long battery life mode through client 1.

[0242] Step 5.12: The second processor receives the user's trigger operation on the control corresponding to the ultra-long battery life mode displayed by the agent module.

[0243] In one example, the agent module can display a pre-obtained list of apps in the extended battery life mode, such as the list obtained through step 5.8.

[0244] In another example, the agent module can trigger client 1 to run, and then client 1 will display the list of apps in the long battery life mode.

[0245] Step 5.13: The second processor, by running the agent module, displays a list of apps in the ultra-long battery life mode of the first electronic device. The display interface of the app list includes management controls for manageable applications of the first electronic device in the ultra-long battery life mode, and receives user trigger operations on the management controls.

[0246] Feasibly, if the user clicks the uninstall control, the proxy module triggers the package management system to uninstall the application. If the user clicks the install / update control, the proxy module can trigger the first processor to run client 1, and then install / update the application in the extended battery life mode through client 1.

[0247] Step 5.14: The second processor triggers the package management system to manage the application of the first electronic device in ultra-long battery life mode by running the agent module.

[0248] The steps shown above are merely illustrative examples, and other feasible steps may also exist, such as the first processor receiving the user's refresh operation on the APP list displayed by client 1, the second processor receiving the user's refresh operation on the APP list displayed by the agent module, etc., which are not limited.

[0249] The following is combined Figure 5 The following describes some implementation examples of application management in unassisted scenarios.

[0250] It is feasible that, when the first electronic device is operating in smart mode, client 1 can manage the applications of the first electronic device in smart mode.

[0251] like Figure 8a As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 8a.1 to 8a.6.

[0252] Step 8a.1: Client 1 starts running when the user clicks the application icon of Client 1. At this time, the first electronic device is operating in smart mode.

[0253] Feasibly, the first processor can launch client 1 when the user clicks the application icon of client 1.

[0254] Step 8a.2: Client 1 displays control 1 corresponding to the smart mode.

[0255] Feasibly, after client 1 starts, it can display the homepage interface, which may include control 1 and control 2 corresponding to the ultra-long battery life mode.

[0256] Feasibly, users can click control 1 to request the display of the app list in smart mode, thereby managing apps in smart mode on demand, and click control 2 to request the display of the app list in ultra-long battery life mode, thereby managing apps in ultra-long battery life mode on demand.

[0257] Step 8a.3: When client 1 detects that the user clicks control 1, it obtains device information 1 of the first processor and reports device information 1 to the application market server to request the APP list 1 of the first electronic device in smart mode.

[0258] Step 8a.4: The application market server sends the APP list 1 to the client 1 based on the device information 1.

[0259] Figure 8a In the illustrated embodiment, in response to the user's click operation on control 1, client 1 reports device information 1 to the application market's server. The application market's server returns APP list 1 based on device information 1, instead of reporting the smart mode parameters so that the application market's server can return the corresponding APP list based on the mode parameters.

[0260] Step 8a.5: Client 1 displays APP list 1, and the display interface includes management controls for the applications in APP list 1.

[0261] Figure 8a In the illustrated embodiment, after client 1 starts, it can first display control 1, and then display the APP list 1 only after the user clicks control 1. In other embodiments, client 1 can also directly display the APP list 1 after starting without requiring a user request.

[0262] Feasibly, when client 1 displays the app list, the corresponding display interface may also include control 1 and control 2, and control 1 and control 2 can be displayed separately. By displaying control 1 and control 2, users can switch to displaying the app list in another working mode as needed. By distinguishing between displaying control 1 and control 2, users can know the device working mode corresponding to the displayed app list.

[0263] Feasibly, client 1 can obtain and report device information after the user clicks control 1 / control 2 to obtain the APP list, and then display the obtained APP list. In the embodiment shown in Figure 8, after the user triggers the display of control 1 (see step 8a.2), client 1 uploads device information 1 to the application market server to request APP list 1 (see step 8a.3), then... Figure 5 In one feasible implementation of the illustrated embodiment, client 1 may first execute step 5.2 above, and then execute step 5.4 above (corresponding to executing step 8a.2 first and then step 8a.3).

[0264] Step 8a.6: When client 1 detects that the user clicks on the management control of an application in APP list 1, it triggers the package management system to manage the application.

[0265] Figure 8a In the illustrated embodiment, client 1 obtains device information 1 in real time when the user clicks control 1. In other embodiments, client 1 may also obtain device information 1 before the user clicks control 1, when the user clicks the application icon of client 1. For specific implementation logic, please refer to the relevant descriptions in other embodiments of this application, which will not be repeated here.

[0266] Feasibly, when the first electronic device is operating in smart mode, client 1 can not only manage the applications of the first electronic device in smart mode, but also delegate the management of the applications of the first electronic device in ultra-long battery life mode.

[0267] like Figure 8b As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 8b.1 to 8b.7.

[0268] Step 8b.1 is the same as step 8a.1.

[0269] Step 8b.2, Client 1 displays control 2 corresponding to the ultra-long battery life mode.

[0270] Step 8b.3: When client 1 detects that the user clicks control 2, it requests device information 2 of the second processor from the proxy module and reports the device information 2 returned by the proxy module to the application market server to request the list of apps 2 of the first electronic device in ultra-long battery life mode.

[0271] Step 8b.4: The app store server sends the app list 2 to the client 1 based on the device information 2.

[0272] Step 8b.5: Client 1 displays APP list 2, and the display interface includes management controls for the applications in APP list 2.

[0273] The technical implementation logic of steps 8b.1 to 8b.5 is the same as that of steps 8a.1 to 8a.5, and will not be repeated here.

[0274] Step 8b.6: When client 1 detects that the user clicks on the management control of an application in the APP list 2, it sends application management information to the agent module.

[0275] Feasibly, when the device is operating in smart mode, the second processor can run an agent module to receive application management information. This application management information could include, for example, application installation packages and application uninstallation notifications.

[0276] Step 8b.7: The proxy module triggers the package management system to perform application management.

[0277] Referring to steps 8b.6 to 8b.7, when the first electronic device is operating in smart mode, the first processor, by running client 1, can manage the applications of the first electronic device in ultra-long battery life mode. Thus, the first electronic device does not need to install an app store client in ultra-long battery life mode, and the second processor does not need to have high device capabilities, such as supporting independent network connectivity or file downloads.

[0278] exist Figure 8b In one feasible implementation of the illustrated embodiment, the management control clicked by the user in step 8b.6 can be an installation / update control, then see [link to relevant documentation]. Figure 8c The implementation process of the client 1 agent management application may include the following steps 8c.1 to 8c.3.

[0279] Step 8c.1: Client 1 detects that the user clicks the install / update control of an application in the APP list 2, requests the application to be installed / updated from the application market's server, and receives the application installation package returned by the application market's server.

[0280] Step 8c.2: Client 1 sends the application installation package to the agent module.

[0281] Step 8c.3: The agent module triggers the package management system to install / update applications.

[0282] As can be seen, when the device is working in smart mode, client 1 can act as an agent to install / update applications of the first electronic device in ultra-long battery life mode.

[0283] exist Figure 8b In another feasible implementation of the illustrated embodiment, the management control clicked by the user in step 8b.6 can be an uninstallation control, then see [link to relevant documentation]. Figure 8d The implementation process of the client 1 agent management application may include the following steps 8d.1 to 8d.2.

[0284] Step 8d.1: Client 1 detects that the user clicks the uninstall control of an application in the APP list 2 and sends an application uninstallation notification to the agent module.

[0285] Step 8d.2: The proxy module triggers the package management system to uninstall the application.

[0286] It is evident that, in addition to uninstalling applications of the first electronic device in ultra-long battery life mode when the device is working in ultra-long battery life mode, it is also possible to uninstall applications of the first electronic device in ultra-long battery life mode through client 1 agent when the device is working in smart mode.

[0287] The above Figure 8a / Figure 8b In the illustrated embodiment, client 1 can report device information 1 / device information 2 to obtain APP list 1 / APP list 2 after the user clicks control 1 / control 2, and then display the obtained APP list. Figure 5 In one feasible implementation of the illustrated embodiment, client 1 may first execute step 5.2 and then execute step 5.4.

[0288] And in Figure 5 In other feasible implementations of the illustrated embodiment, client 1 may first execute step 5.4 and then execute step 5.2. That is, client 1 may also report device information 1 / device information 2 to obtain APP list 1 / APP list 2 before the user clicks control 1 / control 2 (for example, when the user clicks the application icon of client 1, device information can be obtained and reported to obtain the APP list), and the obtained APP list can be displayed when the user clicks control 1 / control 2.

[0289] like Figure 8e As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 8e.1 to 8e.6.

[0290] Step 8e.1 is the same as step 8a.1.

[0291] Step 8e.2: Client 1 displays the control 2 corresponding to the ultra-long battery life mode, requests the device information 2 of the second processor from the proxy module, and reports the device information 2 returned by the proxy module to the application market server to request the APP list 2 of the first electronic device in ultra-long battery life mode.

[0292] Step 8e.3 is the same as step 8b.4.

[0293] Step 8e.4: When client 1 detects that the user clicks on control 2, it displays APP list 2, and the display interface includes management controls for the applications in APP list 2.

[0294] Figure 8e In the illustrated embodiment, client 1 can display the APP list 2 only when the user clicks control 2. In other embodiments, client 1 can also display the APP list 2 directly after obtaining it, without being triggered by the user clicking control 2.

[0295] Steps 8e.5 to 8e.6 are the same as steps 8b.6 to 8b.7.

[0296] and Figure 8b The embodiments shown are the same. Figure 8e The illustrated embodiment can also implement proxy management of applications in ultra-long battery life mode in smart mode. Related technical implementations can be found in [reference needed]. Figure 8b The relevant descriptions in the illustrated embodiments will not be repeated here.

[0297] The main difference between the two embodiments is: Figure 8b The illustrated embodiment only retrieves device information 2 in real time when the user clicks control 1 to request the APP list 2, and then displays it. Figure 8e In the illustrated embodiment, when the user clicks the application icon on client 1, device information 2 is obtained to request the APP list 2. Therefore, when the user clicks control 2, client 1 has already obtained the APP list 2 in advance, so the APP list 2 can be displayed in a timely manner.

[0298] The above Figure 8b In the illustrated embodiment, client 1 can request device information 2 from the proxy module in real time when the user clicks control 2; that is, device information 2 can be obtained in real time. In other embodiments, device information 2 can also be obtained through pre-storage.

[0299] like Figure 8f As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 8f.1 to 8f.7.

[0300] Steps 8f.1 to 8f.2 are the same as steps 8b.1 to 8b.2.

[0301] Step 8f.3: When client 1 detects that the user clicks on control 2, it reports the pre-stored device information 2 of the second processor to the application market server to request the list of apps 2 of the first electronic device in ultra-long battery life mode.

[0302] Unlike step 8b.3, where client 1 can obtain device information 2 by requesting the proxy module in real time, in step 8f.3, client 1 can also obtain device information 2 from pre-stored information.

[0303] Feasibly, device information 2 can be pre-set before the device leaves the factory. In this implementation, the first processor may not need to execute the step of obtaining the device information of the second processor from the proxy module, thus the above... Figure 5 In one feasible implementation of the illustrated embodiment, step 5.7 above may be omitted.

[0304] Feasibly, the first processor can acquire device information 2 during interaction with the second processor and record it upon first acquisition. In this implementation, the first processor does not need to frequently execute the step of acquiring device information from the proxy module, thus avoiding the aforementioned... Figure 5 In one feasible implementation of the illustrated embodiment, it is not necessary to frequently execute step 5.7 above.

[0305] Steps 8f.4 to 8f.7 are the same as steps 8b.4 to 8b.7.

[0306] The above Figure 8e In the illustrated embodiment, client 1 can request device information 2 from the proxy module in real time when the user clicks the application icon of client 1; that is, device information 2 can be obtained in real time. In other embodiments, device information 2 can also be obtained through pre-storage.

[0307] like Figure 8g As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 8g.1 to 8g.6.

[0308] Step 8g.1 is the same as step 8a.1.

[0309] Step 8g.2: Client 1 displays the control 2 corresponding to the ultra-long battery life mode, obtains the pre-stored device information 2 of the second processor, and reports the device information 2 to the application market server to request the APP list 2 of the first electronic device in ultra-long battery life mode.

[0310] Unlike step 8e.2, where client 1 can obtain device information 2 by requesting it from the proxy module in real time, in step 8g.2, client 1 can also obtain device information 2 from pre-stored information. For the specific technical implementation of the pre-stored device information 2, please refer to the relevant explanation in step 8f.3, which will not be elaborated here.

[0311] Steps 8g.3 to 8g.6 are the same as steps 8e.3 to 8e.6.

[0312] Electronic devices typically have a large number of manageable applications in Smart / Extra Long Battery Life mode, and the applications in the app list in Smart / Extra Long Battery Life mode can be a subset of these. To allow users to view other manageable applications outside the currently displayed app list as needed, the first processor can also refresh the app list. The refreshed app list can include one or more other manageable applications outside the currently displayed app list.

[0313] like Figure 8h As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 8h.1 to 8h.4.

[0314] Step 8h.1: Client 1 displays the list 2 of apps on the first electronic device in ultra-long battery life mode.

[0315] It is feasible that step 8h.1 can be any one of steps 8b.5, 8e.4, 8f.5, 8g.4, or other steps that display the APP list 2, and there is no limitation on this.

[0316] Step 8h.2: When client 1 detects that a user has requested to refresh the APP list 2, it requests the application market's server to refresh the APP list 2.

[0317] In one example, the display interface of APP list 2 may include a control for requesting a refresh of the APP list. If the user clicks the control, client 1 can detect that the user has requested a refresh of APP list 2.

[0318] In another example, if a user performs a preset gesture to refresh the app list on the display screen of app list 2, client 1 can detect that the user has requested to refresh app list 2.

[0319] Step 8h.3: The app store server returns the list of apps 3 of the first electronic device in the ultra-long battery life mode, that is, the list of new apps in the ultra-long battery life mode.

[0320] In one example, client 1 can report device information 2 to the app store's server again, and the app store's server can then issue an app list 3 based on device information 2.

[0321] Step 8h.4: Client 1 displays APP list 3, and the display interface includes management controls for the applications in APP list 3.

[0322] Feasibly, after the APP list 3 is displayed on client 1, the user can refresh the displayed APP list again as needed, and so on. The relevant technical implementation can be referred to steps 8h.1 to 8h.4.

[0323] above Figure 8a The illustrated embodiment~ Figure 8h In the illustrated embodiment, the user can request the management application when the device is operating in smart mode; in other embodiments, the user can also request the management application when the device is operating in ultra-long battery life mode.

[0324] Feasibly, when the device is working in ultra-long battery life mode, the application icon of the agent module can be displayed. If the user clicks the application icon of the agent module to request application management, the device can automatically switch (not manually switched by the user clicking the mode switching control) to work in smart mode and perform application management in smart mode.

[0325] like Figure 8i As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 8i.1 to 8i.7.

[0326] Step 8i.1: When the agent module detects that the user has clicked the application icon of the agent module, it starts running and sends a notification message to client 1. This notification message can be used to trigger client 1 to display control 2. At this time, the first electronic device is operating in ultra-long battery life mode.

[0327] Feasibly, the second processor can start the agent module when the user clicks the application icon of the agent module.

[0328] Feasibly, the second processor can trigger the first processor to start after the agent module is started, at which point the device switches from working in ultra-long battery life mode to working in smart mode.

[0329] In step 8i.2, client 1 responds to the notification message sent by the agent module and displays control 2 corresponding to the ultra-long battery life mode. Alternatively, control 1 corresponding to the smart mode can also be displayed on the interface.

[0330] In this embodiment, the proxy module may not display a user interface. After the proxy module is started, it can trigger the client 1 to run in order to display the control 2.

[0331] Steps 8i.3 to 8i.7 are the same as steps 8b.3 to 8b.7.

[0332] Figure 8i In the illustrated embodiment, after the device switches to Smart Mode, the first processor can manage applications in the extended battery life mode. In other embodiments, when the device switches to Smart Mode, the first processor can manage applications in Smart Mode. The relevant technical implementations can be found in the descriptions of other embodiments of this application, and will not be repeated here.

[0333] The above Figure 8iIn the illustrated embodiment, the proxy module may not display the user interface, thus not displaying control 2, but instead triggers client 1 to display control 2. In other embodiments, the proxy module may display the user interface to display control 2, and after the user clicks control 2, it may trigger client 1 to run, displaying the APP list 2 of the first electronic device in ultra-long battery life mode.

[0334] like Figure 8j As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 8j.1 to 8j.8.

[0335] Step 8j.1: The proxy module starts running when it detects that the user has clicked the application icon of the proxy module.

[0336] Step 8j.2: The agent module displays control 2 corresponding to the ultra-long battery life mode. Alternatively, the display interface can also show installed applications in ultra-long battery life mode.

[0337] In step 8j.3, when the agent module detects that the user clicks on control 2, it sends the device information 2 of the second processor to client 1. While the user clicks on control 2, the first electronic device remains in ultra-long battery life mode.

[0338] Feasibly, the second processor can trigger the first processor to start when the user clicks control 2, at which point the device switches from operating in ultra-long battery life mode to operating in smart mode. After the first processor starts, it can run client 1 to receive device information 2 sent by the agent module.

[0339] In this embodiment, the proxy module can display control 2, but not the APP list 2. After the user clicks control 2, the proxy module can trigger client 1 to run and display the APP list 2.

[0340] Step 8j.4: Client 1 reports the device information 2 sent by the agent module to the application market server to request the list of apps 2 of the first electronic device in the ultra-long battery life mode.

[0341] Steps 8j.5 to 8j.8 are the same as steps 8b.4 to 8b.7.

[0342] Figure 8j In the illustrated embodiment, when the proxy module triggers the client 1 to run, it can provide the device information 2 to the client 1 in real time, so that the client 1 can request the APP list 2 based on the device information 2. In other embodiments, the client 1 may have the device information 2 pre-stored, so the proxy module can trigger the client 1 to start after the user clicks the control 2, but it does not send the device information 2 to the client 1.

[0343] The above Figure 8jIn the illustrated embodiment, after the user clicks control 2, the proxy module can trigger client 1 to start. After starting, client 1 can request the APP list 2 from the application market server in real time based on device information 2. In other embodiments, if client 1 has previously requested and stored the APP list 2 from the application market server, client 1 can also display the pre-stored APP list 2.

[0344] like Figure 8k As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 8k.1 to 8k.6.

[0345] Steps 8k.1 to 8k.2 are the same as steps 8j.1 to 8j.2.

[0346] In step 8k.3, when the agent module detects that the user has clicked on control 2, it sends a notification message to client 1. This notification message can be used to trigger client 1 to display the APP list 2. When the user clicks on control 2, the first electronic device is still operating in ultra-long battery life mode.

[0347] Feasibly, the second processor can trigger the first processor to start when the user clicks control 2, at which point the device switches from operating in ultra-long battery life mode to operating in smart mode. After starting, the first processor can run client 1 to respond to notification messages sent by the agent module.

[0348] Step 8k.4: In response to the notification message sent by the agent module, client 1 displays the pre-stored list 2 of apps in the long battery life mode of the first electronic device. The display interface includes management controls for the applications in the list 2.

[0349] Steps 8k.5 to 8k.6 are the same as steps 8b.6 to 8b.7.

[0350] The above Figure 8j and Figure 8k In the illustrated embodiment, the proxy module can trigger the client 1 to start after the user clicks control 2, thereby displaying the APP list 2 of the first electronic device in ultra-long battery life mode. In other embodiments, the proxy module can also display a pre-stored APP list 2 for the user to view and request management of applications in the APP list 2 as needed, and the client 1 is only triggered to start when the user clicks the install / update control of an application in the APP list 2, so as to proxy the installation / update of the applications in the APP list 2.

[0351] like Figure 8l As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 81.1 to 81.7.

[0352] Steps 8l.1 to 8l.2 are the same as steps 8j.1 to 8j.2.

[0353] Step 8l.3: When the agent module detects that the user clicks on control 2, it displays the pre-stored list 2 of apps in the ultra-long battery life mode of the first electronic device.

[0354] Feasibly, after each time client 1 obtains the APP list 2, it can not only display the obtained APP list 2, but also send the obtained APP list 2 to the proxy module, so that the proxy module stores the APP list 2. Figure 5 In one feasible implementation of the illustrated embodiment, step 5.8 may be present, through which the proxy module obtains the APP list 2.

[0355] In step 81.4, the agent module detects that the user clicks on the management control of an application in the APP list 2. If the click is on the application installation / update control, a notification message is sent to client 1 and step 81.5 is executed. If the click is on the application uninstall control, the package management system is triggered to uninstall the application.

[0356] The notification message in step 8l.4 can be used to trigger the client 1 agent to install / update the application.

[0357] When the user clicks the management control for an application in APP list 2, the first electronic device remains in ultra-long battery life mode. If the user clicks the application install / update control, the first electronic device switches to smart mode, and client 1 handles the application installation / update. If the user clicks the application uninstall control, the first electronic device remains in ultra-long battery life mode, and the application is uninstalled by the proxy module.

[0358] Feasibly, the second processor can trigger the first processor to start when the user clicks the application installation / update control, at which point the device switches from operating in ultra-long battery life mode to operating in smart mode. After starting, the first processor can run client 1 to respond to notification messages sent by the agent module.

[0359] In step 8l.5, client 1 responds to the notification message sent by the proxy module, requests the application market server to install / update the application, and receives the application installation package returned by the application market server.

[0360] Steps 8l.6 to 8l.7 are the same as steps 8c.2 to 8c.3.

[0361] The above Figure 8hIn the illustrated embodiment, when the device is operating in smart mode, the client 1 displays the list of apps of the first electronic device in smart / long battery life mode, and the client 1 can refresh the list of apps when the user requests to refresh the list.

[0362] In contrast, the above Figure 8l In the illustrated embodiment, when the device is operating in ultra-long battery life mode, the proxy module displays the list of apps available to the first electronic device in ultra-long battery life mode. To support users in viewing other manageable applications outside the currently displayed app list as needed, the proxy module can trigger client 1 to run when the user requests a refresh of the app list, in order to request a new app list from the app market's server and display it.

[0363] like Figure 8m As shown, one embodiment of application management by the first electronic device in an unassisted scenario may include the following steps 8m.1 to 8m.7.

[0364] Steps 8m.1 to 8m.3 are the same as steps 8l.1 to 8l.3.

[0365] In step 8m.4, the agent module detects a user request to refresh the APP list 2 and sends a notification message to client 1. This notification message can be used to trigger client 1 to request a new APP list from the app store's server and display it. While the user is requesting a refresh of APP list 2, the electronic device remains in ultra-long battery life mode.

[0366] Feasibly, the second processor can trigger the first processor to start when the user requests a refresh of the APP list 2, at which point the device switches from operating in ultra-long battery life mode to operating in smart mode. After starting, the first processor can run client 1 to respond to notification messages sent by the agent module.

[0367] In one example, the display interface of APP list 2 may include a control for requesting a refresh of the APP list. If the user clicks the control, the agent module can detect that the user has requested a refresh of APP list 2.

[0368] In another example, if a user performs a preset gesture to refresh the app list on the display screen of app list 2, the agent module can detect that the user has requested to refresh app list 2.

[0369] In step 8m.5, client 1 responds to the notification message sent by the proxy module and requests the application market server to refresh the APP list 2.

[0370] Steps 8m.6 to 8m.7 are the same as steps 8h.3 to 8h.4.

[0371] The above Figure 8a The illustrated embodiment~ Figure 8m The embodiments shown are merely some feasible examples of application management in unassisted scenarios. Other feasible embodiments may exist in unassisted scenarios, which will not be described one by one here.

[0372] In scenarios with assistance, electronic devices (e.g.) Figure 10 The first electronic device shown) is in the presence of other devices (e.g. Figure 10 Application management is performed with the assistance of the second electronic device shown.

[0373] Feasible, Figure 10 The first electronic device shown can be Figure 5 The first electronic device shown can perform application management independently, both with and without the assistance of other devices. Some of the technical implementation logic of the first electronic device in unassisted scenarios is also applicable to assisted scenarios, and will not be elaborated upon here.

[0374] See Figure 10 The second electronic device is an auxiliary device to the first electronic device, used to assist in managing the applications of the first electronic device in smart / ultra-long battery life mode. The second electronic device can be a smartphone, etc. The second electronic device may include a third processor (such as an AP), which can run the client 2 of the application market installed on the second electronic device (such as an application market APP, sports and health APP). Figure 10 The intelligent mode shown represents the first mode. Figure 10 The extended battery life mode shown indicates the second mode.

[0375] Feasibly, if client 2 needs to communicate with client 1 (e.g., requesting device information from the first / second processor, sending application management information), and the first electronic device is operating in ultra-long battery life mode, then client 2 can send a notification message to the agent module to trigger client 1 to start. In this case, the first electronic device switches to smart mode.

[0376] For example, the third processor can communicate and interact with the first processor via communication methods such as Wi-Fi (Wireless Local Area Network), for example, by transmitting application installation packages. For example, the third processor can communicate and interact with the second processor via communication methods such as Bluetooth, for example, by transmitting notification messages.

[0377] See Figure 10In a feasible scenario, the second electronic device may execute some or all of steps 10.1 to 10.9 to achieve application management. Similarly, in a scenario with assistance, the first electronic device may execute some or all of steps 10.10 to 10.14 to assist in application management. The step numbers are used to distinguish different steps but do not limit the order in which they are executed.

[0378] Step 10.1: The third processor receives the user's trigger operation to start client 2 and starts client 2.

[0379] Step 10.2: The third processor receives the user's trigger operation on the control corresponding to the smart / ultra-long battery life mode displayed on client 2.

[0380] Step 10.3: The third processor runs client 2 to display a list of apps for the first electronic device in smart / long battery life mode. The display interface of the app list includes management controls for manageable applications of the first electronic device in smart / long battery life mode, and receives user trigger operations on the management controls.

[0381] For example, the first electronic device is a smartwatch, the second electronic device is a smartphone, and the control corresponding to the smart mode is... Figure 11 The "Smart Mode" control 1101 shown is the control corresponding to the ultra-long battery life mode. Figure 11 The “GT Mode” control 1102 shown is... Figure 11 This is a mobile phone display interface used to show the list of apps on a smartwatch in smart mode.

[0382] Step 10.4: The third processor reports the device information of the first processor and / or the second processor to the server of the application market, and receives the list of apps of the first electronic device in the smart / ultra-long battery life mode issued by the server of the application market based on the device information of the first processor and / or the second processor. The list of apps includes the manageable applications of the first electronic device in the smart / ultra-long battery life mode.

[0383] In one example, the third processor can report the device information of the second processor, which is acquired in real time, to the application market's server. For instance, the third processor can request the device information of the first processor and / or the second processor from the first processor in real time when the user launches client 2, or it can request the device information of the first / second processor from the first processor in real time when the user clicks the control corresponding to the smart / long battery life mode.

[0384] The first processor can pre-store the device information of the second processor, or it can obtain the device information of the second processor in real time through the proxy module. For specific technical implementation, please refer to the relevant descriptions in other embodiments of this application, which will not be repeated here.

[0385] In another example, the third processor can report the device information of the first processor and / or the second processor, which it has acquired and recorded in advance, to the application market's server. For instance, the third processor can acquire the device information of the first processor and / or the second processor during its interaction with the first processor, and record it upon first acquisition of the device information.

[0386] Step 10.5: The first processor requests the application of the first electronic device in smart / long battery life mode from the application market server and receives the application installation package sent by the application market server.

[0387] Steps 10.1 to 10.5 are similar in technical implementation logic to steps 5.1 to 5.5. The main difference lies in the execution: in unassisted scenarios, client 1 handles tasks such as displaying controls corresponding to the Smart / Extra Long Battery Life mode, interacting with the app store server, and displaying the app list of the first electronic device in Smart / Extra Long Battery Life mode; while in assisted scenarios, client 2 handles these tasks. For a detailed explanation of the relevant technologies, please refer to the description of steps 5.1 to 5.5, which will not be elaborated upon here.

[0388] Step 10.6: The third processor obtains the device information of the second processor sent by client 1 by running client 2.

[0389] In step 10.7, in response to steps 10.1 / 10.2, the third processor sends an application icon / control click notification to client 1 by running client 2. Practically, the application icon / control click notification can be used to request device information from the first processor and / or the second processor from client 1.

[0390] Step 10.8: The third processor sends application management information (such as installation package / uninstallation notifications for applications in smart / long battery life mode of the first electronic device) to client 1 by running client 2.

[0391] Step 10.9: The third processor, by running client 2, sends a notification message to the agent module when the first electronic device is operating in ultra-long battery life mode, so that the second processor triggers the first processor to run client 1.

[0392] In a feasible manner, in response to a notification message received by the agent module, the second processor can trigger the first processor to run client 1. At this time, the operating mode of the first electronic device switches from ultra-long battery life mode to smart mode. After being woken up, client 1 can communicate and interact with client 2 and the application market server. For example, it can send device information of the first processor to client 2, send device information of the second processor to client 2, and receive application management information sent by client 2.

[0393] Step 10.10 is the same as step 5.6.

[0394] Step 10.11 is the same as step 5.7.

[0395] Step 10.12 is the same as step 5.10.

[0396] Step 10.13 is the same as step 5.9.

[0397] Step 10.14 is the same as step 5.14.

[0398] The steps shown above are merely illustrative examples, and other feasible steps may also exist, such as the third processor receiving the user's refresh operation on the APP list displayed by client 2, etc., which are not limited.

[0399] The following is combined Figure 10 The following describes some implementation examples of application management in auxiliary scenarios.

[0400] Feasibly, when the first electronic device is operating in smart mode, client 2 can assist in managing the applications of the first electronic device in smart mode.

[0401] like Figure 12a As shown, one embodiment of the first electronic device performing application management in an assisted scenario may include the following steps 12a.1 to 12a.9.

[0402] Step 12a.1: Client 2 starts running when the user clicks the application icon of Client 2.

[0403] Feasibly, the third processor can launch client 2 when the user clicks the application icon of client 2.

[0404] Step 12a.2: Client 2 displays control 1 corresponding to the smart mode.

[0405] Feasibly, after client 2 starts, it can display a homepage interface, which may include control 1 and control 2 corresponding to the ultra-long battery life mode.

[0406] Step 12a.3: When client 2 detects that the user clicks control 1, it sends a control click notification to client 1 to request device information 1 from the first processor.

[0407] In one example, if client 2 detects that the user clicks control 1 and the first electronic device is working in smart mode, the third processor can trigger the first processor to run client 1, and then client 2 can send the control click notification to client 1.

[0408] In another example, if client 2 detects that the first electronic device is operating in ultra-long battery life mode when the user clicks control 1, client 2 can send a notification message to the agent module (see step 10.9 above) to wake up client 1 and switch the first electronic device to smart mode. After being woken up, client 1 can receive the control click notification from client 2.

[0409] Step 12a.4: Client 1 obtains device information 1 and sends device information 1 to client 2.

[0410] Step 12a.5: Client 2 reports device information 1 to the application market server to request the list of apps 1 for the first electronic device in smart mode.

[0411] Step 12a.6: The application market server sends the APP list 1 to the client 2 based on device information 1.

[0412] Step 12a.7: Client 2 displays APP list 1, and the display interface includes management controls for the applications in APP list 1.

[0413] Step 12a.8: When client 2 detects that the user clicks on the management control of an application in the APP list 1, it sends application management information to client 1.

[0414] Step 12a.9: Client 1 triggers the package management system to perform application management based on the application management information.

[0415] Figure 8a The illustrated embodiments and Figure 12a The technical implementation logic of the embodiments shown is similar, with the main difference being whether there is auxiliary processing by a second electronic device. Figure 12a For some technical understanding of the embodiments shown, please refer to... Figure 8a The relevant descriptions in the illustrated embodiments will not be repeated here.

[0416] In practice, client 2 can assist in managing the application of the first electronic device in smart mode, and also in managing the application of the first electronic device in ultra-long battery life mode.

[0417] like Figure 12b As shown, one embodiment of the first electronic device performing application management in an assisted scenario may include the following steps 12b.1 to 12b.7.

[0418] Step 12b.1 is the same as step 12a.1.

[0419] Step 12b.2: Client 2 displays control 2 corresponding to the ultra-long battery life mode.

[0420] Step 12b.3: When client 2 detects that the user clicks control 2, it sends a control click notification to request device information 2 from the second processor.

[0421] In one example, if client 2 detects that the user clicks control 2, and the first electronic device is working in smart mode, then the third processor can trigger the first processor to run client 1, and then client 2 can send the control click notification to client 1.

[0422] In another example, if client 2 detects that the first electronic device is operating in ultra-long battery life mode when the user clicks control 2, client 2 can send a notification message to the agent module (see step 10.9 above) to wake up client 1 and switch the first electronic device to smart mode. After being woken up, client 1 can receive the control click notification from client 2.

[0423] Step 12b.4: Client 1 requests device information 2 of the second processor from the proxy module and sends the device information 2 returned by the proxy module to Client 2.

[0424] Step 12b.5: Client 2 reports device information 2 to the application market server to request the list of apps 2 for the first electronic device in ultra-long battery life mode.

[0425] Step 12b.6: The application market server sends the APP list 2 to the client 2 based on the device information 2.

[0426] Step 12b.7: Client 2 displays APP list 2, and the display interface includes management controls for the applications in APP list 2.

[0427] Step 12b.8: When client 2 detects that the user clicks on the management control of an application in the APP list 2, it sends application management information to client 1.

[0428] Step 12b.9: Client 1 sends application management information to the agent module.

[0429] Step 12b.10: The proxy module triggers the package management system to perform application management.

[0430] Figure 8b The illustrated embodiments and Figure 12b The technical implementation logic of the embodiments shown is similar, with the main difference being whether there is auxiliary processing by a second electronic device. Figure 12b For some technical understanding of the embodiments shown, please refer to... Figure 8b The relevant descriptions in the illustrated embodiments will not be repeated here.

[0431] exist Figure 12b In one feasible implementation of the illustrated embodiment, the management control clicked by the user in step 12b.8 can be an installation / update control, then see [link to relevant documentation]. Figure 12c The implementation process of the client 2 auxiliary management application may include the following steps 12c.1 to 12c.4.

[0432] Step 12c.1: Client 2 detects that the user clicks the install / update control of an application in APP list 2, requests the application to be installed / updated from the application market's server, and receives the application installation package returned by the application market's server.

[0433] In step 12c.2, client 2 sends the application installation package to client 1. At this point, the first electronic device can operate in smart mode.

[0434] Step 12c.3: Client 1 sends the application installation package to the agent module.

[0435] Step 12c.4: The agent module triggers the package management system to install / update applications.

[0436] It is evident that when the device is operating in smart mode, client 2 can assist client 1 in installing / updating applications of the first electronic device in ultra-long battery life mode.

[0437] exist Figure 12b In another feasible implementation of the illustrated embodiment, the management control clicked by the user in step 12b.6 can be an uninstallation control, then see [link to relevant documentation]. Figure 12d The implementation process of the client 2 auxiliary management application may include the following steps 12d.1 to 12d.3.

[0438] Step 12d.1: Client 2 detects that the user clicked the uninstall control of an application in the APP list 2 and sends an application uninstallation notification to Client 1. At this time, the first electronic device can operate in smart mode.

[0439] Step 12d.2: Client 1 sends the application uninstallation notification to the agent module.

[0440] Step 12d.3: The proxy module triggers the package management system to uninstall the application.

[0441] It is evident that, in addition to uninstalling the applications of the first electronic device in the ultra-long battery life mode when the device is working in ultra-long battery life mode, client 2 can also assist client 1 in uninstalling the applications of the first electronic device in the ultra-long battery life mode when the device is working in smart mode.

[0442] The above Figure 12b In the illustrated embodiment, client 2 requests device information 2 from client 1 in real time to obtain the list of apps 2 sent by the client from the app market. In other embodiments, client 2 may also pre-store device information 2 or the list of apps 2.

[0443] like Figure 12e As shown, one embodiment of the first electronic device performing application management in an assisted scenario may include the following steps 12e.1 to 12e.10.

[0444] Steps 12e.1 to 12e.2 are the same as steps 12b.1 to 12b.2.

[0445] Step 12e.3: When client 2 detects that the user clicks control 2, it displays the pre-stored list 2 of apps in the long battery life mode of the first electronic device. The display interface includes management controls for the applications in the list 2.

[0446] Step 12e.4: When client 2 detects that the user clicks the install / update control of an application in the APP list 2, it requests the application to be installed / updated from the application market's server.

[0447] Step 12e.5: Client 2 receives the application installation package returned by the application market's server.

[0448] In step 12e.6, client 2 detects that the first electronic device is operating in ultra-long battery life mode and sends a notification message to the agent module. This notification message can be used to instruct the agent module to trigger client 1 to run, so that client 1 can obtain the application installation package from the second electronic device.

[0449] Feasibly, when a user requests to launch client 2, client 2 can report pre-stored device information 2 to the app store client and obtain the app list 2 sent by the app store client. Thus, client 2 can display the pre-obtained app list 2 when the user clicks control 2. During this period, the first electronic device can operate in smart mode or ultra-long battery life mode.

[0450] If the first electronic device is operating in ultra-long battery life mode, client 2 cannot send the application installation package to client 1. In this case, client 2 can send a notification message to the proxy module to wake up client 1 through the proxy module. After being woken up, client 1 can receive the application installation package sent by client 2.

[0451] In step 12e.7, the agent module responds to the notification message sent by client 2, triggering client 1 to run. At this time, the first electronic device switches to smart mode.

[0452] Step 12e.8: Client 1 requests the application installation package from Client 2.

[0453] Step 12e.9: Client 1 sends the application installation package sent by Client 2 to the proxy module.

[0454] Step 12e.10: The agent module triggers the package management system to install / update applications.

[0455] The above Figure 12e In the illustrated embodiment, after being woken up, client 1 obtains the application installation package from the second electronic device. In other embodiments, after being woken up, client 1 may also obtain the application installation package from the application market server.

[0456] like Figure 12f As shown, one embodiment of the first electronic device performing application management in an assisted scenario may include the following steps 12f.1 to 12f.9.

[0457] Steps 12f.1 to 12f.4 are the same as steps 12e.1 to 12e.4.

[0458] Steps 12f.5 to 12f.6 are the same as steps 12e.6 to 12e.7.

[0459] Step 12f.7: Client 1 requests the application installation package from the application market's server and receives the application installation package returned by the application market's server.

[0460] In this embodiment, the notification message can be used to notify the agent module to trigger client 1 to run, so that client 1 can obtain the application installation package from the application market's server.

[0461] Steps 12f.8 to 12f.9 are the same as steps 12e.9 to 12e.10.

[0462] like Figure 13 As shown, one embodiment of this application provides an application management method suitable for unassisted scenarios, applied to a first electronic device (e.g., Figure 5The first electronic device shown includes a first processor and a second processor, such as an AP and an MCU. When the first electronic device is working in a first mode, the first processor is working. When the first electronic device is working in a second mode, the first processor is not working and the second processor is working. The power consumption of the first processor is greater than that of the second processor. The application management method may include the following steps 1301 to 1305.

[0463] In other embodiments, steps 1301 to 1305 above can be executed in other orders, such as executing steps 1302 and 1303 first, and then executing step 1301. There is no limitation on this.

[0464] Step 1301: Display a first control. The first control is used to trigger the display of management controls for applications that can be managed by the first electronic device in a second mode. Management includes at least one of installation and update. Alternatively, management may also include uninstallation, etc.

[0465] Practically, the first control can be the control corresponding to the second mode described in other embodiments of this application, such as... Figure 6a and Figure 6b The "GT mode" control shown, or for example Figure 7 The “external screen” control 701 shown is shown.

[0466] For example, the first control can be Figures 8a to 8m If the control 2 described in any of the embodiments shown is used, then step 1301 can be the step of displaying the control 2 in that embodiment, such as referring to steps 8b.2, 8e.2, 8g.2, 8i.2, 8j.2, etc. above. Specifically, the control 2 can be displayed in the first mode or in the second mode.

[0467] Step 1302: The first processor sends the device information of the second processor to the application market's server.

[0468] For example, the device information of the second processor can be Figures 8b to 8m If the device information 2 is described in any of the embodiments shown, then step 1302 can be the step of the first processor in that embodiment reporting the device information 2 by running client 1.

[0469] Step 1303: The first processor receives the first information sent by the application market server based on the device information of the second processor.

[0470] For example, the first information can be Figures 8b to 8m In any of the embodiments shown, if the APP list 2 is described, then step 1303 can be the step in which the first processor in that embodiment receives the APP list 2 by running client 1.

[0471] Step 1304: In response to a trigger operation on the first control, display, according to the first information, a management control for one or more applications that the first electronic device can manage in the second mode, wherein the one or more applications include the first application. The first application can be any of the one or more applications.

[0472] The one or more applications are applications that are not installed on the first electronic device in the second mode, are installed and can be updated, or are installed and can be uninstalled.

[0473] For example, the one or more applications can be Figures 8b to 8m For each application in the APP list 2 described in any of the embodiments shown, step 1304 can be the step of displaying the APP list 2 in that embodiment, such as referring to steps 8b.5, 8e.4, 8h.1, 8k.4, 8l.3, etc. above. Specifically, the APP list 2 can be displayed in the first mode or in the second mode.

[0474] Step 1305: In response to the trigger operation of the management control of the first application, the first processor controls the second processor to perform application management.

[0475] For example, the management control of the first application can be Figures 8b to 8m If the management control of a certain application in the APP list 2 described in any of the embodiments is used, then step 1305 can be the step of the first processor controlling the second processor to install / update / uninstall the application of the first electronic device in the second mode in this embodiment. For example, see steps 8b.6 to 8b.7, 8c.1 to 8c.3, 8d.1 to 8d.2, 8l.4 to 8l.7, etc. as described above. Specifically, the client 1 can respond to the user's trigger operation on the management control, or the proxy module can respond to the user's trigger operation on the management control.

[0476] exist Figure 13 In one feasible implementation of the illustrated embodiment, displaying the first control includes: displaying the first control in a first mode; displaying management controls for one or more applications includes: displaying management controls for one or more applications in the first mode. This implementation allows users to issue application management requests when the first electronic device is operating in the first mode.

[0477] exist Figure 13In one feasible implementation of the illustrated embodiment, before displaying the first control, the application management method further includes: in a second mode, the second processor, in response to a trigger operation on a target application icon to be displayed, triggers the first processor to operate, wherein the target application icon is an icon related to the client of the application market. After the second processor wakes up the first processor, the first processor can perform the operation of displaying the first control.

[0478] Alternatively, the target application icon can be the application icon of the proxy module described in other embodiments of this application. In this implementation, the proxy module may not display a user interface. This implementation supports users issuing application management requests when the first electronic device is operating in the second mode, and the first electronic device can automatically switch to operating in the first mode without requiring manual mode switching by the user.

[0479] exist Figure 13 In one feasible implementation of the illustrated embodiment, before step 1302, the application management method further includes: the first processor, in response to a triggering operation on the application icon of the client in the application market, requesting device information from the second processor. This implementation can obtain the first information in advance before the user triggers the first control, thus enabling the timely display of the APP list in the second mode when the user triggers the first control.

[0480] exist Figure 13 In one feasible implementation of the illustrated embodiment, before step 1302, the application management method further includes: the first processor, in response to a triggering operation on the first control, requesting device information from the second processor. This implementation can obtain the first information only when the user triggers the first control, thus reducing unnecessary processing steps.

[0481] exist Figure 13 In one feasible implementation of the illustrated embodiment, step 1302 may include: the first processor, in response to a trigger operation on the application icon of the application market client or a trigger operation on the first control, sending the pre-acquired device information of the second processor to the application market server.

[0482] In one example, the device information of the second processor can be pre-configured before the device leaves the factory. In another example, the device can store the acquired device information when it first obtains the device information of the second processor. That is, the first processor can obtain the device information of the second processor before the user triggers the application icon in the app store client, or before the user clicks the first control.

[0483] In this implementation, the first processor can pre-store the device information of the second processor, thus eliminating the need to frequently request the device information from the second processor.

[0484] exist Figure 13 In one feasible implementation of the illustrated embodiment, displaying the first control includes: displaying the first control in a second mode; before displaying the management controls of one or more applications, the application management method further includes: in the second mode, a second processor, in response to a triggering operation on the first control, triggers the first processor to operate. After the second processor wakes up the first processor, the first processor can perform the operation of displaying the management controls of one or more applications.

[0485] Feasibly, the control information of the first control can be pre-stored, and both the first processor and the second processor can display the first control according to the pre-stored control information.

[0486] It is feasible that the interface displayed by the second processor on the first control is the same as or different from the interface displayed by the first processor on the first control; there is no limitation on this.

[0487] This implementation allows users to issue application management requests when the first electronic device is operating in the second mode, and the first electronic device can automatically switch to operating in the first mode without requiring the user to manually switch modes.

[0488] In other embodiments, the first electronic device may also display controls corresponding to the first mode in the second mode. If the user triggers the controls corresponding to the first mode, the second processor can trigger the first processor to work, so that the first processor displays the list of apps in the second mode. This implementation allows the user to trigger the first electronic device to automatically switch to the first mode for application management when the first electronic device is working in the second mode.

[0489] exist Figure 13 In one feasible implementation of the illustrated embodiment, displaying the first control includes: displaying the first control in a second mode; the application management method further includes: in the second mode, a second processor, in response to a triggering operation on the first control, performs a step for displaying the management controls of one or more applications based on pre-acquired first information.

[0490] This implementation allows users to view the manageable applications on the first electronic device in the second mode. The device only switches to the first mode when the user requests to install / update an application in the second mode, thus reducing unnecessary mode switching and affecting the device's battery life.

[0491] In other embodiments, the first electronic device may also display controls corresponding to the first mode in the second mode. If the user triggers a control corresponding to the first mode, the second processor can display a pre-stored list of apps in the second mode. When the user triggers the management control of any application in the app list, the first processor is triggered to work for application management. This implementation allows the user to view the manageable applications of the first electronic device in the first mode when the first electronic device is working in the second mode, and can trigger the first electronic device to automatically switch to the first mode for application management.

[0492] exist Figure 13 In one feasible implementation of the illustrated embodiment, before the first processor controls the second processor to perform application management, the application management method further includes: in a second mode, the second processor triggers the first processor to operate in response to a trigger operation on the management control of the first application. After the second processor wakes up the first processor, the first processor can execute the steps of controlling the second processor to perform application management.

[0493] This implementation allows users to request the installation / update of applications in the second mode as needed when the first electronic device is operating in the second mode. The first electronic device can switch operating modes as needed to respond to the user's request.

[0494] exist Figure 13 In one feasible implementation of the illustrated embodiment, the application management method further includes: in the second mode, the second processor, in response to a refresh request for the management controls of one or more of the aforementioned applications, triggers the first processor to operate; the first processor requests a refresh of the first information from the application market server, and displays the management controls for applications that the first electronic device can manage in the second mode based on the second information returned by the application market server. For example, the first information is the original list of apps on the device in the second mode, and the second information is the new list of apps on the device in the second mode.

[0495] exist Figure 13 In one feasible implementation of the illustrated embodiment, the first electronic device is a smartwatch or a smartphone.

[0496] exist Figure 13 In one feasible implementation of the illustrated embodiment, the first electronic device includes a first display screen and a second display screen; the first display screen is used to display the user interface in the first mode; and the second display screen is used to display the user interface in the second mode.

[0497] exist Figure 13 In one feasible implementation of the illustrated embodiment, the first electronic device is a foldable mobile phone, the first display screen is the inner screen of the mobile phone, and the second display screen is the outer screen of the mobile phone.

[0498] like Figure 14 As shown, one embodiment of this application provides an application management method suitable for auxiliary scenarios and applied to a second electronic device (e.g., Figure 10 The second electronic device shown is an auxiliary device, and the second electronic device and the first electronic device (e.g., Figure 10 The first electronic device shown is connected; the first electronic device includes a first processor and a second processor. When the first electronic device is working in a first mode, the first processor is working, and when the first electronic device is working in a second mode, the first processor is not working. The power consumption of the first processor is greater than the power consumption of the second processor. The application management method may include the following steps 1401 to 1405.

[0499] In other embodiments, steps 1401 to 1405 above can be executed in other orders, such as executing steps 1402 and 1403 first, and then executing step 1401. There is no limitation on this.

[0500] Step 1401: Display a second control. The second control is used to trigger the display of management controls for applications that can be managed by the first electronic device in a second mode, including at least one of installation and update.

[0501] Practically, the second control can be the control corresponding to the second mode described in other embodiments of this application, such as... Figure 11 The “GT Mode” control 1102 shown is an example. Although both are controls corresponding to the second mode, the first control is displayed in the user interface of the first electronic device, and the second control is displayed in the user interface of the second electronic device.

[0502] For example, the second control can be Figures 12a to 12f If the control 2 described in any of the embodiments shown is used, then step 1401 can be the step of displaying the control 2 in that embodiment, such as step 12b.2 above.

[0503] Step 1402: Send the device information of the second processor to the application market's server.

[0504] For example, the device information of the second processor can be Figures 12b to 12f If the device information 2 is described in any of the embodiments shown, then step 1402 can be the step of the client 2 reporting the device information 2 in that embodiment.

[0505] exist Figure 14 In one feasible implementation of the illustrated embodiment, the application management method further includes: in response to a trigger operation on the application icon of the client in the application market or a trigger operation on the second control, sending a second message to the first processor, the second message being used to request device information of the second processor; and receiving the device information of the second processor sent by the first processor.

[0506] In this implementation, the second electronic device can request device information from the first processor on demand to obtain device information in real time, enabling the second electronic device to obtain the first information without transmitting mode parameters. In other embodiments, the second electronic device may also pre-store the device information of the second processor.

[0507] Step 1403: Receive the first information sent by the application market server based on the device information of the second processor.

[0508] For example, the first information can be Figures 12b to 12f If the APP list 2 is described in any of the embodiments shown, then step 1403 can be the step of the client 2 receiving the APP list 2 in that embodiment.

[0509] Step 1404: In response to the triggering operation of the second control, the management control of one or more applications that the first electronic device can manage in the second mode is displayed according to the first information. The one or more applications include the first application.

[0510] For example, the one or more applications can be Figures 12b to 12f For each application in the APP list 2 shown in any of the embodiments, step 1404 can be the step of displaying the APP list 2 in that embodiment, such as step 12b.7, step 12e.3, etc. above.

[0511] Step 1405: In response to the trigger operation of the management control of the first application, the first processor is triggered to control the second processor to perform application management.

[0512] For example, the management control of the first application can be Figures 12b to 12f If the management control of a certain application in the APP list 2 described in any of the embodiments is used, then step 1405 can be the step of triggering the first processor to control the second processor to install / update / uninstall the application of the first electronic device in the second mode in this embodiment. For example, see steps 12b.8 to 12b.10, 12c.1 to 12c.4, 12d.1 to 12d.3, 12e.4 to 12e.10, etc. Specifically, the triggering of the first processor can be implemented when the first electronic device is working in the first mode, or the triggering of the first processor can be implemented when the first electronic device is working in the second mode.

[0513] In one embodiment, step 1405 may include: in response to a triggered operation of the installation / update control of the first application, requesting the installation package of the first application from the server of the application market; when the first electronic device is operating in a first mode, sending the installation package of the first application sent by the server of the application market to the first processor (see step 10.8 above). After receiving the installation package of the first application, the first processor may send the installation package of the first application to the second processor (see step 10.13 above), and the second processor may install / update the first application according to the installation package of the first application.

[0514] exist Figure 14 In one feasible implementation of the illustrated embodiment, step 1405 may include: in response to a trigger operation of the management control of the first application, when the first electronic device is working in the second mode, sending a first message to the second processor (see step 10.9 above), the first message being used to trigger the first processor to work; triggering the first processor to control the second processor to perform application management.

[0515] This implementation allows users to manage applications that can run on the first electronic device as needed through an auxiliary device when the first electronic device is working in the second mode. The first electronic device can automatically switch to working in the first mode without requiring the user to manually switch modes.

[0516] The technical implementation logic of the first electronic device in unassisted scenarios can also be applied to assisted scenarios, and will not be elaborated here.

[0517] exist Figure 14 In one feasible implementation of the illustrated embodiment, the first electronic device is a smartwatch and the second electronic device is a smartphone.

[0518] like Figure 15 As shown, one embodiment of this application provides an application management method, applicable to auxiliary scenarios, and applied to a first electronic device (e.g., Figure 10 The first electronic device shown), the first electronic device and the second electronic device (e.g. Figure 10 The second electronic device (i.e., auxiliary device) is connected; the first electronic device includes a first processor and a second processor. When the first electronic device is working in a first mode, the first processor is working, and when the first electronic device is working in a second mode, the first processor is not working. The power consumption of the first processor is greater than that of the second processor. The application management method may include the following steps 1501 to 1502.

[0519] Step 1501: The first processor sends the device information of the second processor to the second electronic device. The device information of the second processor is used to supply the server of the application market to issue first information based on the device information of the second processor. The first information is used to support the display of management controls for one or more applications that the first electronic device can manage in the second mode. The management includes at least one of installation and update, and the one or more applications include the first application.

[0520] In one embodiment of this application, the first processor sends device information of the second processor to the second electronic device, including: the first processor receiving a second message sent by the second electronic device, the second message being a message sent by the second electronic device in response to a trigger operation on the application icon of the application market client or a trigger operation on a displayed second control, the second control being used to trigger the display of management controls of the first electronic device that can manage applications in a second mode; the first processor responding to the second message sending the device information of the second processor to the second electronic device.

[0521] Step 1502: In response to the control operation performed by the second electronic device when the management control of the first application is triggered, the first processor controls the second processor to perform application management.

[0522] In one embodiment, step 1502 may include: the first processor receiving the installation package of the first application sent by the second electronic device (see step 10.8 above), or obtaining the installation package of the first application issued by the server of the application market; the first processor sending the installation package of the first application to the second processor (see step 10.13 above); and the second processor installing / updating the first application according to the installation package of the first application.

[0523] In one embodiment of this application, before the first processor controls the second processor to perform application management, the application management method further includes: in the second mode, the second processor receives a first message sent by the second electronic device (see step 10.9 above), the first message being a message sent by the second electronic device in response to a trigger operation of the management control of the first application when the first electronic device is working in the second mode; the second processor responds to the first message and triggers the first processor to work.

[0524] Figure 15 The illustrated embodiments and Figure 14 The implementation process of the illustrated embodiment corresponds to that of the specific technical implementation. Figure 14 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0525] exist Figure 15 In one feasible implementation of the illustrated embodiment, the first electronic device is a smartwatch and the second electronic device is a smartphone.

[0526] The application management method provided in any embodiment of this application can be applied to electronic devices such as mobile phones, tablets, personal digital assistants (PDAs), desktops, laptops, notebook computers, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, and wearable devices. This application does not impose any special restrictions on the specific form of the above-mentioned electronic devices.

[0527] The application management method provided in any embodiment of this application can be applied to... Figure 16 In the electronic device 100 shown. Figure 16 A schematic diagram of the structure of the electronic device 100 is shown.

[0528] The electronic device 100 may include a first processor 110, a second processor 111, an internal memory 121, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, a sensor module 180, a display screen 194, etc. The sensor module 180 may include a pressure sensor, a touch sensor, etc.

[0529] Among them, the power consumption of the first processor 110 (e.g., AP) is greater than that of the second processor 111 (e.g., MCU).

[0530] In one embodiment, the electronic device 100 can be Figure 5 or Figure 10 The first electronic device shown can communicate with external devices (such as application market servers, the aforementioned auxiliary devices, etc.) via a mobile communication module 150 or a wireless communication module 160 (such as WLAN), and the second processor 111 can communicate with external devices (such as the aforementioned auxiliary devices, etc.) via a wireless communication module 160 (such as BT).

[0531] In another embodiment, the electronic device 100 can be Figure 10 The second electronic device shown can communicate with external devices (such as application market servers, assisted electronic devices, etc.) via a mobile communication module 150 or a wireless communication module 160.

[0532] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0533] The first processor 110 may include one or more processing units, such as an access point (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors. The controller can generate operation control signals based on the instruction opcode and timing signals to control instruction fetching and execution.

[0534] In some embodiments, the first processor 110 may be a system-on-chip (SoC), which may include a central processing unit (CPU) and may further include other types of processors. In some embodiments, the first processor 110 may be a PWM control chip.

[0535] The first processor 110 may also include necessary hardware accelerators or logic processing hardware circuits, such as an ASIC, or one or more integrated circuits for controlling the execution of the technical solution program. Furthermore, the first processor 110 may have the function of operating one or more software programs, which may be stored in a storage medium.

[0536] The first processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the first processor 110 is a cache memory. This memory can store instructions or data that the first processor 110 has just used or that are used repeatedly. If the first processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the first processor 110, and thus improves the efficiency of the system.

[0537] In some embodiments, the memory of the electronic device 100 may be a read-only memory (ROM), other types of static storage devices capable of storing static information and instructions, random access memory (RAM), or other types of dynamic storage devices capable of storing information and instructions. It may also be an electrically erasable programmable read-only memory (EEPROM), or any computer-readable medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer.

[0538] In some embodiments, the first processor 110 and the memory can be combined into a single processing device, or they can be independent components. The first processor 110 can be used to execute program code stored in the memory. In specific implementations, the memory can be integrated into the first processor 110, or it can be independent of the first processor 110.

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

[0540] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0541] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0542] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0543] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the first processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the first processor 110 may be housed in the same device.

[0544] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs a sound signal through an audio device or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the first processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0545] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to the first processor 110. The wireless communication module 160 can also receive signals to be transmitted from the first processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0546] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0547] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The first processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0548] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0549] In one embodiment, the electronic device 100 is a single-display device, such as a smartwatch. In another embodiment, the electronic device 100 is a dual-display device, such as a foldable phone.

[0550] Internal memory 121 can be used to store computer executable program code, which includes instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The first processor 110 executes various functional applications and data processing of electronic device 100 by running instructions stored in internal memory 121 and / or instructions stored in memory disposed in the processor.

[0551] A pressure sensor is used to sense pressure signals and convert them into electrical signals. In some embodiments, the pressure sensor may be located on the display screen 194. There are many types of pressure sensors, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. When a touch operation is applied to the display screen 194, the electronic device 100 detects the intensity of the touch operation based on the pressure sensor. The electronic device 100 may also calculate the touch location based on the detection signal from the pressure sensor. In some embodiments, touch operations applied to the same touch location but with different touch operation intensities may correspond to different operation commands.

[0552] A touch sensor, also known as a "touch device," can be located on the display screen 194. The touch sensor and the display screen 194 together form a touchscreen, also known as a "touchscreen." The touch sensor detects touch operations applied to or near it. The touch sensor can then transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In some embodiments, the touch sensor may also be located on the surface of the electronic device 100, in a different position than the display screen 194.

[0553] In addition, the electronic device runs an operating system on top of the aforementioned components. For example... operating system, operating system, Operating systems, etc. Applications can be installed and run on an operating system.

[0554] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses the layered architecture Android system as an example to exemplify the software structure of electronic device 100.

[0555] Figure 17 This is a software structure block diagram of an electronic device 100 according to an embodiment of this application. The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into multiple layers, from top to bottom: application layer, application framework layer (Framework, FWK), system library and runtime layer, hardware abstraction layer (HAL), and kernel layer.

[0556] The application layer can include a series of application packages, such as an app store, an app store proxy module (such as Launcher), WLAN, Bluetooth and other applications.

[0557] In one embodiment, when the electronic device 100 operates in the first mode, it can run an application market APP. By running the application market APP, the applications of the electronic device 100 in the first mode can be managed, and the application market's proxy module can be triggered to manage the applications of the electronic device 100 in the second mode. Both the application market APP and the proxy module can be managed through a package management system. The relevant technical implementations can be found in other embodiments of this application and will not be elaborated upon here.

[0558] The application framework layer provides an Application Programming Interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions. For example... Figure 17 As shown, the application framework layer may include a package management system, a view system, a notification manager, a resource manager, a window manager, a content provider, etc.

[0559] Package management systems can be used to manage (such as installing / updating / uninstalling) applications that can run on electronic devices.

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

[0561] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating the device, and flashing indicator lights.

[0562] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0563] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0564] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0565] The system library and runtime layer includes the system library and the Android Runtime.

[0566] System libraries can include multiple functional modules. For example: 3D graphics processing libraries (e.g., OpenGL ES), surface managers, 2D graphics engines (e.g., SGL), media libraries, etc.

[0567] The 3D graphics processing library is used for 3D graphics drawing, image rendering, compositing, and layer processing. The surface manager manages the display subsystem and provides fusion of 2D and 3D layers for multiple applications. The 2D graphics engine is the drawing engine for 2D graphics. The media library supports playback and recording of various common audio and video formats, as well as still image files. The media library supports multiple audio and video encoding formats, such as: Moving Picture Experts Group (MPEG4), High-Compression Digital Video Codec Standard (H.264), Moving Picture Experts Compression Standard Audio Layer 3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate Codec (AMR), Joint Picture Experts Group (JPG), Portable Web Graphics (PNG), etc.

[0568] The Android runtime consists of the core libraries and the virtual machine. The Android runtime is responsible for scheduling and managing the Android system. The core libraries comprise two parts: one part contains the functionalities that Java calls, and the other part is the core Android library itself. The application layer and application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0569] The Hardware Abstraction Layer (HAL) acts as a bridge between software and hardware. It encapsulates the underlying hardware driver, providing a generic interface for the application framework to call the driver. The HAL is an abstract interface for the device kernel driver, providing application programming interfaces (APIs) for accessing the underlying device to higher-level Java API frameworks. The HAL contains multiple library modules, each implementing an interface for a specific type of hardware component. The HAL provides APIs for higher-level Java API frameworks to access the underlying device; when an API framework requests access to the electronic device's hardware, the Android system loads the corresponding library module for that hardware component.

[0570] The Hardware Abstraction Layer (HAL) can communicate with the application framework layer through the Hardware Abstraction Layer Interface Definition Language (HIDL). HIDL is an interface description language that specifies the interface between HAL and FWK.

[0571] The kernel layer is the layer between hardware and software. It contains at least camera drivers, display drivers, Bluetooth drivers, audio drivers, and sensor drivers. The kernel layer is the foundation of the Android system, through which the system's final functionalities are implemented.

[0572] Understandable, Figure 17 The layers in the illustrated software structure and the components contained in each layer do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer layers than illustrated, and each layer may include more or fewer components; this application does not impose any limitations.

[0573] One embodiment of this application provides an application management device applied to a first electronic device. The first electronic device includes a first processor and a second processor. The first processor operates when the first electronic device is in a first mode, and does not operate when the first electronic device is in a second mode. The power consumption of the first processor is greater than that of the second processor. The application management device includes: a display module for displaying a first control, which triggers the display of management controls for applications that the first electronic device can manage in the second mode, including at least one of installation and update; in response to the triggering operation of the first control, displaying management controls for one or more applications that the first electronic device can manage in the second mode according to first information, including the first application; a first processor for sending device information of the second processor to a server of an application market; receiving first information sent by the server of the application market according to the device information of the second processor; and controlling the second processor to perform application management in response to the triggering operation of the management controls of the first application.

[0574] One embodiment of this application provides an application management device applied to a second electronic device, which is connected to a first electronic device. The first electronic device includes a first processor and a second processor. The first processor operates when the first electronic device is in a first mode, and does not operate when the first electronic device is in a second mode. The power consumption of the first processor is greater than that of the second processor. The application management device includes: a display module for displaying a second control, which triggers the display of management controls for applications that the first electronic device can manage in the second mode, including at least one of installation and update; in response to the triggering operation of the second control, displaying management controls for one or more applications that the first electronic device can manage in the second mode according to first information, including the first application; a communication module for connecting to the first electronic device; sending device information of the second processor to a server of an application market; receiving first information sent by the server of the application market according to the device information of the second processor; and a processing module for triggering the first processor to control the second processor to perform application management in response to the triggering operation of the management controls of the first application.

[0575] One embodiment of this application provides an application management device applied to a first electronic device, which is connected to a second electronic device. The first electronic device includes a first processor and a second processor. The first processor operates when the first electronic device is in a first mode and does not operate when the first electronic device is in a second mode. The power consumption of the first processor is greater than that of the second processor. The application management device includes: a communication module for connecting to the second electronic device; a first processor for sending device information of the second processor to the second electronic device. The device information of the second processor is used to supply the server of the application market to issue first information based on the device information of the second processor. The first information is used to support the display of management controls for one or more applications that the first electronic device can manage in the second mode. Management includes at least one of installation and update, and the one or more applications include the first application. In response to the control operation executed by the second electronic device when the management control of the first application is triggered, the second processor is controlled to perform application management.

[0576] One embodiment of this application provides an application management system, including: an application market server and a smartwatch, wherein the smartwatch is used to execute the application management method applied to a first electronic device as described in any embodiment of this application.

[0577] One embodiment of this application provides an application management system, including: an application market server, a smartphone, and a smartwatch. The smartphone is used to execute the application management method for a second electronic device as described in any embodiment of this application, and the smartwatch is used to execute the application management method for a first electronic device as described in any embodiment of this application.

[0578] This application also provides an electronic chip, which is installed in an electronic device (UE). The electronic chip includes a processor for executing computer program instructions stored in a memory. When the computer program instructions are executed by the processor, the electronic chip is triggered to execute the method steps provided in any method embodiment of this application for a first electronic device or a second electronic device.

[0579] This application also proposes a terminal device, which includes a communication module, a memory for storing computer program instructions, and a processor for executing the program instructions. When the computer program instructions are executed by the processor, the terminal device is triggered to execute the method steps provided in any method embodiment of this application for a first electronic device or a second electronic device.

[0580] This application also proposes a server device, which includes a communication module, a memory for storing computer program instructions, and a processor for executing the program instructions. When the computer program instructions are executed by the processor, the server device is triggered to execute the method steps provided in any method embodiment of this application for a first electronic device or a second electronic device.

[0581] This application also provides an electronic device, which includes multiple antennas, a memory for storing computer program instructions, a processor for executing the computer program instructions, and a communication device (such as a communication module that can implement 5G communication based on the NR protocol). When the computer program instructions are executed by the processor, the electronic device is triggered to execute the method steps provided in any method embodiment of this application for a first electronic device or a second electronic device.

[0582] Specifically, in the embodiments of this application, one or more computer programs are stored in the aforementioned memory. The one or more computer programs include instructions that, when executed by the aforementioned device, cause the aforementioned device to perform the method steps applied to a first electronic device or a second electronic device as described in the embodiments of this application.

[0583] Furthermore, the devices, apparatuses, and modules described in the embodiments of this application may be implemented by computer chips or physical entities, or by products with certain functions.

[0584] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program code.

[0585] In the several embodiments provided in this application, any function, if implemented as a software functional unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0586] Specifically, this application also provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to execute the method steps provided in this application for a first electronic device or a second electronic device.

[0587] This application also provides a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform the method steps provided in this application embodiment for a first electronic device or a second electronic device.

[0588] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, apparatuses, or units, and may be electrical, mechanical, or other forms.

[0589] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0590] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.

[0591] An integrated unit implemented as a software functional unit can be stored in a computer-readable storage medium. This software functional unit, stored in a storage medium, includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk.

[0592] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0593] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0594] Those skilled in the art will recognize that the units and algorithm steps described in the embodiments of this application can be implemented using electronic hardware, computer software, or a combination of electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0595] Those skilled in the art will readily understand that, for the sake of convenience and brevity, the same or similar parts between the various embodiments of this application can be referred to mutually. For example, the specific working processes of the systems, devices, and units described in the embodiments of this application can be referred to the corresponding processes in the method embodiments of this application, and will not be repeated here.

[0596] The above description is merely a specific embodiment of this application and is not intended to limit this application. The scope of protection of this application shall be determined by the claims.

Claims

1. An application management method, characterized in that, The first electronic device includes a first processor and a second processor. When the first electronic device is working in a first mode, the first processor is working. When the first electronic device is working in a second mode, the first processor is not working. The power consumption of the first processor is greater than that of the second processor. The method includes: Display a first control, which triggers the display of management controls for applications that the first electronic device can manage in the second mode, the management including at least one of installation and update; The first processor sends the device information of the second processor to the application market's server; The first processor receives first information from the application market's server based on the device information of the second processor; In response to a trigger operation on the first control, the management control of one or more applications that the first electronic device can manage in the second mode is displayed according to the first information, wherein the one or more applications include the first application; In response to a trigger operation on the management control of the first application, the first processor controls the second processor to perform application management.

2. The method according to claim 1, characterized in that, The display of the first control includes: displaying the first control in the first mode; Displaying the management controls for one or more applications includes: displaying the management controls for one or more applications in the first mode.

3. The method according to claim 2, characterized in that, Before displaying the first control, the method further includes: In the second mode, the second processor, in response to a trigger operation on a displayed target application icon, triggers the first processor to operate, wherein the target application icon is an icon related to the client of the application market.

4. The method according to claim 2 or 3, characterized in that, Before the first processor sends the device information of the second processor to the application market server, the method further includes: In response to a trigger operation on the application icon of the client in the application market or a trigger operation on the first control, the first processor requests device information from the second processor.

5. The method according to claim 2 or 3, characterized in that, The first processor sends the device information of the second processor to the application market server, including: In response to a trigger operation on the application icon of the application market client or a trigger operation on the first control, the first processor sends the pre-acquired device information of the second processor to the application market server.

6. The method according to claim 1, characterized in that, The display of the first control includes: displaying the first control in the second mode; Before displaying the management controls for the one or more applications, the method further includes: In the second mode, the second processor responds to the triggering operation of the first control, triggering the first processor to work.

7. The method according to claim 1, characterized in that, The display of the first control includes: displaying the first control in the second mode; The method further includes: In the second mode, in response to a triggering operation on the first control, the second processor executes steps for displaying management controls for the one or more applications based on the first information obtained in advance.

8. The method according to claim 7, characterized in that, Before the first processor controls the second processor to perform application management, the method further includes: In the second mode, the second processor responds to a trigger operation of the management control of the first application, triggering the first processor to operate.

9. An application management method, characterized in that, It is applied to a second electronic device, which is connected to a first electronic device; the first electronic device includes a first processor and a second processor, the first processor works when the first electronic device is in a first mode, and the first processor does not work when the first electronic device is in a second mode, and the power consumption of the first processor is greater than that of the second processor; The method includes: Display a second control, which triggers the display of management controls for applications that the first electronic device can manage in the second mode, the management including at least one of installation and update; Send the device information of the second processor to the application market's server; Receive the first information sent by the application market server based on the device information of the second processor; In response to a triggering operation on the second control, the management control of one or more applications that the first electronic device can manage in the second mode is displayed according to the first information, wherein the one or more applications include the first application; In response to a trigger operation on the management control of the first application, the first processor is triggered to control the second processor to perform application management.

10. The method according to claim 9, characterized in that, The step of triggering the first processor to control the second processor to perform application management in response to a trigger operation on the management control of the first application includes: In response to a trigger operation of the management control of the first application, when the first electronic device is operating in the second mode, a first message is sent to the second processor, the first message being used to trigger the first processor to operate; The first processor is triggered to control the second processor to perform application management.

11. The method according to claim 9 or 10, characterized in that, The method further includes: In response to a trigger operation on the application icon of the client in the application market or a trigger operation on the second control, a second message is sent to the first processor, the second message being used to request device information from the second processor; Receive device information of the second processor sent by the first processor.

12. An application management method, characterized in that, It is applied to a first electronic device, which is connected to a second electronic device; the first electronic device includes a first processor and a second processor, the first processor works when the first electronic device is working in a first mode, and the first processor does not work when the first electronic device is working in a second mode, and the power consumption of the first processor is greater than the power consumption of the second processor. The method includes: The first processor sends the device information of the second processor to the second electronic device. The device information of the second processor is used to supply the server of the application market to issue first information based on the device information of the second processor. The first information is used to support the display of management controls for one or more applications that the first electronic device can manage in the second mode. The management includes at least one of installation and update. The one or more applications include the first application. In response to a control operation performed by the second electronic device when the management control of the first application is triggered, the first processor controls the second processor to perform application management.

13. The method according to claim 12, characterized in that, Before the first processor controls the second processor to perform application management, the method further includes: In the second mode, the second processor receives a first message sent by the second electronic device. The first message is a message sent by the second electronic device in response to a trigger operation of the management control of the first application when the first electronic device is working in the second mode. The second processor responds to the first message and triggers the first processor to operate.

14. The method according to claim 12 or 13, characterized in that, The first processor sends the device information of the second processor to the second electronic device, including: The first processor receives a second message sent by the second electronic device. The second message is a message sent by the second electronic device in response to a trigger operation on the application icon of the client in the application market or a trigger operation on a displayed second control. The second control is used to trigger the display of a management control of the application that the first electronic device can manage in the second mode. In response to the second message, the first processor sends the device information of the second processor to the second electronic device.

15. A first electronic device, characterized in that, The first electronic device includes one or more memories for storing computer program instructions and one or more processors, wherein when the computer program instructions are executed by the one or more processors, the first electronic device is triggered to perform the method as described in any one of claims 1-8.

16. An application management system, characterized in that, include: An application marketplace server and a smartwatch, wherein the smartwatch is used to perform the method as described in any one of claims 1-8.

17. A second electronic device, characterized in that, The second electronic device includes one or more memories for storing computer program instructions and one or more processors, wherein when the computer program instructions are executed by the one or more processors, the second electronic device is triggered to perform the method as described in any one of claims 9-11.

18. A first electronic device, characterized in that, The first electronic device includes one or more memories for storing computer program instructions and one or more processors, wherein when the computer program instructions are executed by the one or more processors, the first electronic device is triggered to perform the method as described in any one of claims 12-14.

19. An application management system, characterized in that, include: The application market server, smartphone, and smartwatch, wherein the smartphone is used to perform the method as described in any one of claims 9-11, and the smartwatch is used to perform the method as described in any one of claims 12-14.

20. An electronic chip, characterized in that, include: A processor for executing computer program instructions stored in a memory, wherein, when the computer program instructions are executed by the processor, the electronic chip is triggered to perform the method as described in any one of claims 1-8, or the method as described in any one of claims 9-11, or the method as described in any one of claims 12-14.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed on a computer, causes the computer to perform the method as described in any one of claims 1-8, or the method as described in any one of claims 9-11, or the method as described in any one of claims 12-14.

22. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1-8, or the method as described in any one of claims 9-11, or the method as described in any one of claims 12-14.

Images