Always-on display method and apparatus

Abstract

An always-on display (AOD) method and apparatus, which relate to the technical field of terminals, and are capable of reducing potential privacy security risks in AOD scenarios. The method may comprise: in an AOD state, a terminal displaying a first card of a first application that comprises first content, wherein the content displayed by the first card does not include second content; and when the terminal displays a lock screen interface in a screen-on state, displaying the first card comprising the first content and the second content. Using the method enables terminals to control the display and hiding of private content (such as second content) of a card on the basis of a display state. Thus, security risks in privacy scenarios can be reduced.

Description

Always-on display method and device

[0001] This application claims priority to Chinese Patent Application No. 202410808263.9, filed on June 20, 2024, entitled “Always-on Display Method and Apparatus”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminal technology, and in particular to a method and apparatus for always-on display. Background Technology

[0003] Currently, users can add cards to the lock screen of the terminal to meet their card usage needs in lock screen scenarios. When the screen supports always-on display (AOD) function, the terminal can display the screen even when the screen is off. As shown in Figure 1(1), the lock screen 100 displays the calendar application card 101 and other cards when the screen is on. As shown in Figure 1(2), the lock screen 100 can continue to display the corresponding cards of different applications even after the screen is off. In the current AOD scenario, since the screen may display some cards for a long time, it may lead to privacy and security risks. Summary of the Invention

[0004] This application provides a method and apparatus for always-on display, which are used to improve the security of always-on display.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, this application provides an always-on display method, applicable to a terminal or components supporting terminal functions (such as a chip system). Taking the method applied to a terminal as an example, the method may include: when the terminal is in an always-on display (AOD) state, displaying a first card containing first content of a first application, wherein the displayed content of the first card does not include second content. When the terminal is on displaying a lock screen interface, the first card containing both the first content and the second content is displayed.

[0007] Using this method, the terminal can control the display and hiding of private content (such as secondary content) of cards based on the display status, thereby reducing security risks in privacy scenarios.

[0008] In one possible design of the first aspect, the terminal, in an Always-On Display (AOD) state, displays a first card of a first application including first content, comprising:

[0009] A mask is displayed in a first area of ​​the first card, the mask covering the second content.

[0010] Using this method, the terminal can cover up a second piece of content involving privacy by masking it, in order to prevent privacy leaks caused by the second piece of content being viewed by others.

[0011] One possible design for the first aspect also includes:

[0012] After the user's identity information is verified, the screen lights up to display the unlock interface, which shows the first card containing the first content and the second content.

[0013] One possible design for the first aspect also includes:

[0014] The desktop is displayed, and the desktop displays a first card that includes the first content and the second content.

[0015] For example, the unlock screen displays the first card containing both the first and second content, while the desktop does not display the first card. Alternatively, the unlock screen displays the first card containing both the first and second content, while the desktop displays a first card that includes the first content but does not include the second content.

[0016] For example, the unlock screen displays the first card containing the first content and the second content, and the desktop also displays the first card containing the first content and the second content.

[0017] For example, the unlock screen includes a first card with first content but does not include a second card, and the desktop displays the first card containing both the first and second content.

[0018] In one possible design of the first aspect, displaying the desktop includes: after the user's identity information is verified, the screen lights up to display the desktop.

[0019] In one possible design of the first aspect, when the user's identity information is verified, the terminal can also jump to other interfaces besides the desktop, such as the interface where the terminal was last exited.

[0020] In one possible design of the first aspect, the first card displays the first content through a first component, the first component being identified by a non-privacy identifier, the non-privacy identifier being used to identify the non-privacy component.

[0021] In one possible design of the first aspect, the first card displays the second content via a second component, the second component being identified as a privacy identifier, the privacy identifier being used to identify the privacy component.

[0022] In one possible design of the first aspect, the terminal, in an Always-On Display (AOD) state, displays a first card of a first application including first content, comprising:

[0023] Based on the privacy identifier of the second component, a mask is displayed in the area corresponding to the second component in the first card.

[0024] For example, the first component may be one or more.

[0025] In one possible design of the first aspect, the identifier of the first component is a non-privacy identifier, and the identifier of the second component is a privacy identifier. The method further includes: in the Always On Display (AOD) state, based on the non-privacy identifier of the first component of the first card and the privacy identifier of the second component, not displaying the second component and displaying the first component; in the screen-on state, the terminal displays the second component.

[0026] Considering that the screen may display some cards for a long time in AOD scenarios, the terminal does not display second components involving privacy in AOD state, which can reduce the probability of privacy leakage.

[0027] In one possible design of the first aspect, when the terminal displays the lock screen interface, it acquires at least one card information of the lock screen interface and displays the card, the card including the first card.

[0028] In one possible design of the first aspect, the first card further includes a third component, the third component being identified as a privacy identifier; the method further includes:

[0029] In the AOD state, the first card, which includes the first content but does not include the second content or the third content, is displayed; the first card displays the third content through the third component.

[0030] The screen is turned on to display the first card, which includes the first content, the second content, and the third content.

[0031] In one possible design of the first aspect, the terminal further includes a second card for a second application, and also includes:

[0032] In the AOD state, a second card of the second application, which includes the fourth content, is displayed, wherein the content displayed on the second card does not include the fifth content;

[0033] In one possible design of the first aspect, when the terminal is in a screen-on state, it displays the second card, which includes the fourth content and the fifth content.

[0034] The terminal further includes a second card for a second application, and the method further includes:

[0035] When the terminal is in the Always On Display (AOD) state, it displays a second card that includes a fourth piece of content, wherein the content displayed on the second card does not include a fifth piece of content;

[0036] When the terminal displays the lock screen interface, it displays the second card, which includes the fifth content and the fourth content.

[0037] In one possible design of the first aspect, the privacy identifier is a preset identifier in the first application. For example, the privacy identifier is preset in the installation package of the first application.

[0038] In one possible design of the first aspect, the first application includes at least one of the following types of applications: payment application, calendar application, note-taking application, messaging application, food delivery application, shopping application, or health application.

[0039] Alternatively, the first content may include at least one of the following: schedule information, barcode information, logistics information, food delivery information, or health information.

[0040] In one possible design of the first aspect, it further includes: displaying a first interface, the first interface including a first setting item, the first setting item being used to enable the always-on display method.

[0041] In one possible design of the first aspect, it further includes: displaying a second interface, the second interface being used to set the application for enabling the always-on display method, the application for enabling the always-on display method including the first application.

[0042] In one possible design of the first aspect, it further includes: in the screen-off state, if a user is detected to be near the terminal and the user's identity information is verified, the terminal displays the first card containing the second content.

[0043] Using this method, the terminal can quickly display the second content from the first card, improving the efficiency of interpersonal interaction. Furthermore, the terminal displays the second content only after the user's identity information has been verified, preventing unauthorized users from viewing the second content.

[0044] In one possible design of the first aspect, it further includes: in the screen-off state, displaying the first card containing the second content based on the user's status information or the terminal's status information.

[0045] Using this method, the terminal can determine the user's intention to view the second content based on the user's status information or the terminal's status information, and quickly display the second content when the user intends to view it, so as to meet the user's need to view the second content.

[0046] In one possible design of the first aspect, the terminal's state information includes at least one of the following: the terminal's location, the connection status of the terminal's external devices, or the terminal's device posture. Alternatively, the user's state information includes at least one of the following: the user's behavior, or the user's habits during a corresponding time period.

[0047] In one possible design of the first aspect, displaying the first card containing the second content based on the user's status information or the terminal's status information includes: if it is detected that the terminal is flipped to an angle with the horizontal plane that satisfies a first range, then displaying the first card containing the second content; the second content includes barcode information.

[0048] Secondly, a method for displaying an always-on display is provided. Taking the method applied to a terminal as an example, the method may include: when the lock screen is on, displaying a first card that includes first content but does not include second content; when the user's identity information is verified, displaying an unlock screen, wherein the unlock screen displays the first card that includes the first content and the second content.

[0049] In one possible design of the second aspect, when the lock screen interface is displayed on the screen, displaying a first card that includes first content but does not include second content includes: displaying a mask in a first area of ​​the first card, the mask covering the second content.

[0050] In one possible design of the second aspect, when the terminal is in Always-On Display (AOD) state, it displays a first card of a first application that includes first content, wherein the content displayed on the first card does not include second content.

[0051] In one possible design of the second aspect, the terminal, in an Always-On Display (AOD) state, displays a first card of a first application including first content, including: displaying a mask in a first area of ​​the first card, the mask covering the second content.

[0052] In one possible design of the second aspect, the first card displays the first content through a first component, the first component being identified by a non-privacy identifier, the non-privacy identifier being used to identify the non-privacy component.

[0053] In one possible design of the second aspect, the first card displays the second content through a second component, the second component being identified as a privacy identifier, the privacy identifier being used to identify the privacy component.

[0054] Thirdly, a screen-off display method is provided. Taking the method applied to a terminal as an example, the method may include: when the terminal is in an always-on display (AOD) state, displaying a first card containing first content of a first application, wherein the displayed content of the first card does not include second content. In the AOD state, if a user is detected approaching the terminal and the user's identity information is verified, the terminal displays the first card containing the second content.

[0055] Fourthly, a screen-off display method is provided. Taking the method applied to a terminal as an example, the method may include: when the terminal is in an always-on display (AOD) state, displaying a first card containing first content of a first application, wherein the displayed content of the first card does not include second content. In the AOD state, the first card containing the second content is displayed based on the user's status information or the terminal's status information.

[0056] The descriptions of user status information and terminal status information can be found in the relevant section in Part One, and will not be repeated here.

[0057] Fifthly, a screen-off display method is provided. Taking the method applied to a terminal as an example, the method may include: displaying second content. Upon detecting another user approaching the terminal, a mask is displayed, the mask covering the second content.

[0058] This method can be applied in non-AOD scenarios, for example, the first content can be work minutes.

[0059] Alternatively, if other privacy-related scenarios are detected, the terminal can also display a mask to cover secondary content involving privacy. For example, when the display is set to never sleep, it may remain on. In this case, to reduce the risk of privacy leakage, the terminal can display a mask to cover secondary content involving privacy. For other content on the display that does not involve privacy, the terminal may not display a mask for that other content.

[0060] Sixthly, the present application provides an apparatus comprising: one or more processors, a memory, and one or more computer programs; wherein the processor is coupled to the memory, and the one or more computer programs are stored in the memory; when the apparatus is running, the processor executes the one or more computer programs stored in the memory to cause the apparatus to perform the method in any of the above-described designs.

[0061] In a seventh aspect, this application provides an apparatus including a functional module for performing the methods described in any of the possible designs of any of the above aspects of this application. This module may be implemented by software or hardware, or by a combination of software and hardware. For example, it may include a processing unit and a communication unit.

[0062] Eighthly, the present application provides a computer-readable storage medium including computer instructions that, when executed on a device, cause the device to perform any of the possible designs described above.

[0063] Ninthly, the present application provides a computer program product that, when run on a device, causes the device to perform any of the possible designs in any of the above aspects.

[0064] In a tenth aspect, this application provides a circuit system including a processing circuit configured to perform the methods in any possible design of any of the above aspects. The processing circuit can be implemented as a corresponding circuit component, such as one or more processors. Alternatively, it can be implemented as a processor and a memory. Yet another example is a processor and a transceiver.

[0065] Eleventhly, an electronic device is provided, comprising: a display screen, a processor, and a memory, the display screen, the memory, and the processor being coupled together, the memory being used to store program code including instructions, and the processor reading the instructions from the memory to cause the electronic device to perform the method as described in any of the preceding aspects and any of the designs therein.

[0066] In a twelfth aspect, this application provides a chip system including at least one processor and at least one interface circuit, the at least one interface circuit being used to perform transceiver functions and send instructions to at least one processor, and when at least one processor executes instructions, at least one processor performs the method as described in the first aspect and any of the designs therein. Attached Figure Description

[0067] Figure 1 is a schematic diagram of the always-on display method provided by related technologies;

[0068] Figure 2 is a schematic diagram of the development process of the card application provided in the embodiments of this application;

[0069] Figure 3 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0070] Figure 4A is a schematic diagram of the software architecture of an electronic device provided in an embodiment of this application;

[0071] Figure 4B is a schematic diagram of the component tree provided in an embodiment of this application;

[0072] Figure 5 is a schematic diagram of the interface of the always-on display method provided in the embodiment of this application;

[0073] Figures 6A and 6B are schematic diagrams of the interface of the always-on display method provided in the embodiments of this application;

[0074] Figure 7 is a schematic diagram of an always-on display method provided in an embodiment of this application;

[0075] Figure 8 is a flowchart illustrating an always-on display method provided in an embodiment of this application;

[0076] Figures 9-12 are schematic diagrams of scenarios provided in the embodiments of this application;

[0077] Figure 13 is a schematic diagram of the interface of the always-on display method provided in the embodiment of this application;

[0078] Figure 14 is a flowchart illustrating another always-on display method provided in an embodiment of this application;

[0079] Figure 15 is a schematic diagram of the structure of another electronic device provided in an embodiment of this application;

[0080] Figure 16 is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0081] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, “at least one” and “one or more” refer to one or more (including two).

[0082] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0083] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0084] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information in the technical solutions of this application comply with relevant laws and regulations and do not violate public order and good morals. For example, in the technical solutions of this application, the processing of user personal information is carried out with the user's authorization, which will be uniformly stated here and will not be repeated below.

[0085] "Used for" can mean "dedicated to" or "available for," without being limited to "dedicated to." For example, "The interface is used for xx" in some examples means that the interface is dedicated to xx. In other examples, the interface may have other functions besides xx, without restriction.

[0086] In the AOD display scheme of the related technology shown in Figure 1, some application cards can be displayed when the screen is off. In some cases, if the cards contain private data, this private data may be viewed by others, posing a security risk.

[0087] In view of this, embodiments of this application provide an always-on display method, in which the terminal provides the ability to mask privacy, enabling control over the display and hiding of private card content, thereby reducing security risks in privacy scenarios.

[0088] In this embodiment of the application, the application that displays cards can be referred to as a card application. As shown in Figure 1(1), the calendar application can display card 101 on the display screen. Accordingly, the calendar application can be referred to as a card application.

[0089] Figure 2 illustrates an example of the development and usage process for a card application, which may include:

[0090] 1. Developers use user interface (UI) engines to develop card applications. For example, UI engines include, but are not limited to, the ArkUI framework.

[0091] 2. Application development. The application development process includes the following steps:

[0092] 1) Script development: Through script development, you can obtain a logic script (also known as logic code) that describes the specific business logic of the card application.

[0093] 2) Debugging and Development: During this process, developers can use the UI framework to debug the functionality of the card application.

[0094] 3) Compile and package: After the card application's functions are developed and debugged, developers can use the compilation and packaging functions provided by the UI framework to package the entire card application project into an executable file, such as an APK installation package.

[0095] The compiled and packaged installation package contains logic code derived from script development.

[0096] In this embodiment, the card application can call the interface provided by the UI engine in the UI framework to declare privacy components in the card. For example, the developer adds corresponding code to the logic code of the card application to enable the card application to call the corresponding interface and declare the privacy components in the card.

[0097] A privacy component can refer to a component that contains privacy data. As one possible implementation, a card application can call this interface to define the privacy attributes (sensitive attributes) of the privacy component. In other words, if a component defines or declares privacy attributes, then that component can be considered a privacy component. For example, the interface used to declare a privacy component is the PrivacySensitive interface.

[0098] Optionally, the default properties of a component are either non-sensitive or non-privacy properties.

[0099] In this application embodiment, privacy attributes may also be referred to as privacy identifiers. Non-privacy attributes may also be referred to as non-privacy identifiers; the names are not limited.

[0100] The privacy-related interfaces involved in the embodiments of this application may be collectively referred to as privacy-hiding interfaces, or other names, without limitation.

[0101] As shown in Figure 1(2), the part outlined by the dashed line in card 101 is the component for displaying the schedule. This component involves sensitive information such as the schedule, therefore, this component can be regarded as a privacy component.

[0102] In this application embodiment, components may sometimes be referred to as controls, and the name is not limited. Privacy components may also be referred to as sensitive components or privacy-sensitive components, and the name is not limited.

[0103] In this application embodiment, a collection of one or more privacy components may be referred to as a privacy component tree (or privacy tree), or a privacy component set (or privacy set).

[0104] 3. After the developers complete the development of the card application, they will launch the card application on the app store through operational activities, making it available for users to download and use.

[0105] 4. Users download the application installation package through the app store. Users open the card application on their terminal (such as a mobile phone), and the card application runs on the terminal.

[0106] After developers declare privacy components for card applications, in some scenarios where the card application runs, the phone may not display the privacy components in the card, or may replace the privacy components in the card with other display content.

[0107] This method can be applied to electronic devices or systems containing electronic devices. For example, electronic devices can be mobile phones, tablets, handheld computers, netbooks, as well as personal digital assistants (PDAs), artificial intelligence (AI) devices, and wearable devices. Wearable devices include, but are not limited to, smartwatches, smart bracelets, smart ankle bracelets, and various other devices with displays. The operating system installed on the electronic device is not limited. This application does not limit the specific type of electronic device or the operating system installed.

[0108] For example, Figure 3 shows a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0109] As shown in Figure 3, the electronic device 500 may include a processor 510, a memory 520, and a display screen 530, etc.

[0110] Processor 510 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0111] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0112] The processor 510 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 510 is a cache memory. This memory can store instructions or data that the processor 510 has just used or that are used repeatedly. If the processor 510 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 processor 510, and thus improves the efficiency of the system.

[0113] In some embodiments, the processor 510 may include one or more interfaces. These one or more interfaces can be used to connect the processor 510 to the memory 520, the display 530, and the like.

[0114] In some embodiments of this application, the processor 510 can be used to determine whether a component in the card is a privacy component. If the component is a privacy component, the display content of the privacy component is masked to prevent the privacy content of the privacy component from being viewed by others. Please refer to the following description for details.

[0115] The memory 520 can be used to store computer executable program code, which includes instructions. The memory 520 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 image playback), etc. The data storage area may store data created during the use of the electronic device 500, etc. The processor 510 executes various functional applications and data processing of the electronic device 500 by running instructions stored in the memory 520 and / or instructions stored in memory located within the processor.

[0116] Electronic device 500 implements display functions through a GPU, display screen 530, and application processor. The GPU is a microprocessor for image processing, connected to the display screen 530 and the application processor. The GPU performs mathematical and geometric calculations and is used for graphics rendering. Processor 510 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0117] The display screen 530 is used to display images, videos, etc. The display screen 530 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, the electronic device 500 may include one or N displays 530, where N is a positive integer greater than 1.

[0118] In some embodiments of this application, the display screen 530 can be used to display various interfaces. For example, it can display an interface containing cards in a screen-off state. If the card contains private data, then when the card is displayed in a screen-off state, the private data in the card is not displayed, or the private data is replaced with other non-private content for display.

[0119] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device. In other embodiments of this application, the electronic device may include more or fewer components than those shown in FIG3, 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.

[0120] Figure 4A illustrates an example architecture of the software system of electronic device 100. As shown in Figure 4A, the software system may include: a UI engine, a card user, a card management service, and a card provider.

[0121] Among them, the UI engine and card management service provide the ability to mask privacy, and card applications and lock screen applications can control the display and hiding of privacy content based on this capability.

[0122] The card user can refer to the host application that displays the card content. For example, a lock screen application or a home screen application can be a card user. Taking a lock screen application as an example, when the screen is locked, the lock screen application can instruct the card management service whether to hide the private content of the card.

[0123] The card management service can be used to manage cards. It also provides capabilities such as periodic card refresh. In this embodiment, the card management service can provide an interface to the card user to set a privacy hiding switch for the card and cache the state of this switch. In some examples, when the switch is turned on, it enables the method for controlling the display and hiding of privacy content according to this embodiment.

[0124] In some embodiments, the card management service can also be used for privacy scenario awareness. A privacy scenario is a situation where it may be necessary to hide private content on the card. Privacy scenarios include, but are not limited to, AOD (Away From Home) scenarios on the lock screen.

[0125] In some embodiments, the card management service can also be used in privacy scenarios to mask UI components in the card's UI component tree or to display card content normally.

[0126] A UI component tree, also known as a UI node tree (frame node tree), is a data structure formed by multiple UI components (elements). Figure 4B shows an example of a UI component tree for a card. A UI component tree includes multiple UI components (or UI nodes).

[0127] In some examples, in privacy scenarios, if a privacy component exists in the card's UI component tree, the card management service can mask the content of that privacy component to prevent privacy leaks. In other examples, if a privacy component does not exist in the card's UI component tree, the card management service can display the card normally.

[0128] Optionally, the software system may also include a card rendering process (also known as a card rendering service). As one possible implementation, the lock screen application calls the formComponent.obscured method, whose parameters are passed to the card rendering process via inter-process communication (IPC).

[0129] In one scenario, the `formComponent.obscured` method is passed an empty array to indicate that the mask should be removed or not displayed. In this case, the card rendering process instructs, notifies, or requests the card management service to display the card content normally, without needing to display the mask.

[0130] In another scenario, the `formComponent.obscured` method passes the `ObscuredReasons.PLACEHOLDER` parameter to indicate that a mask needs to be displayed. In this case, the card rendering process calls the interface provided by the UI engine, traverses the card's UI component tree, and queries the UI engine to determine if the card's UI component tree contains privacy components.

[0131] For example, the card rendering service executes `IsPrivacySensitive` to query the UI engine for properties of the card's UI components. If the UI engine returns `true` for one or more components, meaning that one or more components specify privacy properties, the card rendering service can determine that one or more components are privacy components. The card rendering process can then instruct, notify, or request the card management service to mask the display of that one or more privacy components of the card.

[0132] The card provider is the application that provides the card display content and can control the displayed content, control layout, and control click events. As shown in Figure 4A, the display content that the card provider can provide includes, but is not limited to, icons, text, and images.

[0133] In this embodiment of the application, the card provider may also be referred to as the card application.

[0134] Referring to Figure 1(2), the card provider of card 101 is the calendar application, and the card user of card 101 is the lock screen application. The lock screen application displays the calendar application's card 101 when the lock screen is off. Text is displayed on card 101.

[0135] The UI engine provides an interface that card applications can call to declare privacy components for cards. For details on developing card applications and implementing privacy component declarations, please refer to the description in Figure 2; further details will not be provided here.

[0136] In some embodiments, the UI engine can obtain information about the card application from the card application, such as obtaining card data.

[0137] In some embodiments, the UI engine can also provide card parsing and card rendering related functions. For example, it can parse the component tree of the card and send the component tree information to the backend rendering service, which then performs rendering and sends it to the graphics card.

[0138] In some embodiments, the UI engine can also be used to parse the privacy attributes of privacy components. In some examples, the card rendering process can query the UI engine for the attributes of the card component and determine whether the component is a privacy component based on the attributes. For example, as mentioned above, if a component declares privacy attributes, then the component is a privacy component.

[0139] The technical solutions involved in the following embodiments can all be implemented in a device with the structure shown in Figure 3.

[0140] In this embodiment of the application, when a privacy scenario is met, a mask can be displayed at the location of the privacy component in the card to prevent others from accidentally viewing the privacy content of the privacy component. The technical solution provided by this embodiment of the application will be described below with reference to the accompanying drawings, using a mobile phone as an example.

[0141] Scene 1:

[0142] As shown in Figure 5(1), card 101 can be displayed when the phone screen is off. When the phone screen is off, the private content of non-privacy components on card 101 is displayed, such as the text "Wednesday" and "5th", as well as the UI icon of component 102. Furthermore, when the phone screen is off, the private content of privacy components on card 101 is not displayed.

[0143] As one possible implementation, when the phone screen is off, the privacy content of the privacy component on card 101 is not displayed. This can be achieved by not displaying the content at the location corresponding to the privacy component. As shown in Figure 5(1), the location corresponding to the privacy component (defined by a dashed box) does not display any content.

[0144] As another possible implementation, when the phone screen is off, the privacy content of the privacy component on card 101 is not displayed. Instead, the desensitized content can be displayed at the location corresponding to the privacy component. As shown in Figure 5(3), the location corresponding to the privacy component (marked with a dashed box) displays the text "No recent schedule". This text does not involve sensitive privacy and can prevent others from maliciously viewing the user's schedule.

[0145] Using this method, in AOD scenarios, when the screen is off, the terminal does not display the privacy content of the privacy component, or replaces the privacy content with desensitized content for display. This can avoid privacy leaks caused by prolonged screen-off display and improve the security of AOD.

[0146] As shown in Figure 5(2), the phone screen lights up in response to the user's operation. The card 101 on the lock screen 103 under the lit screen can include the display content of privacy components. For example, card 101 can include schedule information such as "Today's meeting 2:30-3:30 pm①". That is, the terminal displays the card content normally when the unlocked screen is lit. In this way, the user can quickly view recent schedules through card 101.

[0147] Optionally, actions that trigger the phone to turn on the screen include, but are not limited to, double-tapping the screen or clicking the power button.

[0148] Scene 2:

[0149] Unlike Scenario 1, in Scenario 2, when the terminal is unlocked and the screen is on, it can verify the user's identity information and determine whether to display the privacy component on the card.

[0150] For example, as shown in Figure 6A(1), in an AOD scenario, the phone does not display privacy content (such as meeting schedules) of privacy components when the screen is off. As shown in Figure 6A(2), the phone responds to the user's operation by turning on the screen and displays a card 101 that does not contain privacy content on the screen-on lock screen interface 103.

[0151] For example, in response to a legitimate user's successful face verification, as shown in Figure 6A(3), the phone can refresh the display content of card 101 on interface 103 (an example of the unlock interface) to display the meeting schedule information in card 101. In response to an unauthorized user's failed face verification, as shown in Figure 6A(4), the phone does not refresh the display content of card 101, and the phone still does not display the meeting schedule information in card 101.

[0152] Using this method, when the terminal displays the lock screen, it controls whether to display the private content in the card based on the user's identity verification result. This reduces the security risks of AOD (Audience On Demand) while providing card information to legitimate users in a timely manner, ensuring a smooth user experience.

[0153] Scene 3:

[0154] Unlike Scenario 2, where the terminal verifies the user's identity information and determines whether to display the privacy component's content on the lock screen, in Scenario 3, the terminal determines whether a legitimate user wants to view the privacy component's content and displays it on the desktop or other interfaces displayed after unlocking.

[0155] As shown in Figure 6B(1), the phone displays card 101 on the lock screen 103, with the meeting schedule information in card 101 hidden by a mask. In some examples, the user can click on card 101 and perform facial verification. In response to successful facial verification, the phone can display desktop 301 as shown in Figure 6B(2). Desktop 301 includes card 101, which displays the meeting schedule information.

[0156] Conversely, in some examples, if the user does not click on the card shown in Figure 6B(1), or the phone does not detect the user's intention to view card 101, the phone may display the desktop after the face verification is successful. This desktop does not include card 101. Alternatively, the desktop includes card 101, but the meeting schedule information is not displayed on card 101.

[0157] In other examples, besides clicking on card 101 shown in (1) of Figure 6B, users can also express their intention to view card 101 in other ways.

[0158] In other examples, if the terminal detects that the user intends to view information related to card 101, it can redirect to the application interface corresponding to card 101 after facial verification is successful. For example, it could redirect to the calendar application interface, which might include meeting schedule information.

[0159] In other examples, if the terminal detects the user's intent to view information related to card 101, it can navigate to the previous display screen before the screen locks after facial verification is successful. For example, the terminal displays a floating window corresponding to card 101 on this screen. The user can quickly view information related to card 101 by interacting with this floating window.

[0160] In other examples, the terminal does not detect whether the user intends to view card 101. When the terminal successfully unlocks in the scenario shown in Figure 6B(1), it directly jumps to the corresponding interface. For example, the interface to which it jumps includes card 101, which displays meeting schedule information.

[0161] This article only lists a few examples of ways to display card 101 information on the unlocked interface of the terminal, and does not limit the scope of the example.

[0162] This article takes facial recognition as an example of identity verification. In other embodiments, the identity verification method can be other methods, such as verifying the user's fingerprint or iris.

[0163] Figure 7 illustrates the application of this application embodiment in the field of barcodes. As shown in Figure 7(1), the mobile phone screen is off, and a card 202 is displayed on the lock screen interface 201. The card 202 includes a QR code mask 203. The mask 203 is used to cover or hide the QR code used for payment to prevent the QR code from being maliciously scanned.

[0164] Then, as shown in Figure 7(2), the phone screen lights up and displays card 202 on the lock screen 204, with the QR code in card 202 hidden by mask 203. In some examples, in response to a legitimate user unlocking with the correct face, the phone can refresh the display content of card 202. As shown in Figure 7(3), when a legitimate user unlocks with their face, the phone triggers the removal of the mask at the dotted frame position in card 202 and displays QR code 203' at that position.

[0165] Conversely, in other examples, in response to an unauthorized user unlocking the phone with an incorrect face, the phone does not refresh the display content of card 202. As shown in Figure 7(4), if the unauthorized user does not unlock the phone with a face, the phone retains the mask 203 in the display card 202 to reduce security risks.

[0166] This method offers two advantages: firstly, users can quickly access the payment QR code from the lock screen, improving payment efficiency; secondly, only verified, authorized users can trigger the rapid QR code display, ensuring payment security.

[0167] The following describes the solution of the embodiment of this application with reference to process examples.

[0168] As an example, Figure 8 illustrates a process example. As shown in Figure 8, the process may include the following steps:

[0169] S101, The card application calls the interface provided by the UI engine to declare the card's privacy components.

[0170] For details on the implementation of S101, please refer to the description of the card application development process shown in Figure 2, which will not be repeated here.

[0171] As mentioned above, after the developer completes the card application development, they release it to the app store through promotional activities for users to download and use. After the user downloads and installs the card application on their device, the device can obtain relevant information about the card components of the card application and display the card on the screen based on this information. For details on how the device displays the card based on the relevant card component information, please refer to other sections of this document, such as the description in Figure 4A.

[0172] For example, card applications include, but are not limited to, at least one of the following types of applications: payment applications, calendar applications, note-taking applications, messaging applications, food delivery applications, shopping applications, or health applications.

[0173] For example, privacy-related content (such as the second type of content) in a card application may include at least one of the following: schedule information, barcode information, logistics information, food delivery information, or health information. For instance, privacy-related content in a calendar application may include meeting schedule information.

[0174] S102. When the screen is on, the lock screen application displays the lock screen interface.

[0175] For example, as shown in Figure 5(2), in the screen-on state, the lock screen application displays the lock screen interface 103.

[0176] S103, The lock screen app instructs the card management service not to display the privacy mask.

[0177] As one possible implementation, the lock screen app calls the `formComponent.obscured` method, passing an empty array to indicate whether to cancel or not display the privacy mask (or simply mask). For example, the format of the `formComponent.obscured` method to indicate that the privacy mask should not be displayed is `formComponent.obscured([])`. `[]` can represent an empty array.

[0178] S104. The card management service displays card content normally on the lock screen.

[0179] As shown in Figure 5(2), in the screen-on state, the phone displays the contents of card 101 normally on the lock screen interface 103, without needing to display a privacy mask in the position of the dotted frame of card 101.

[0180] The card management service displays content on the interface, which can be understood or replaced as: the card management service controls the content displayed on the interface. For example, the card management service determines that the card content should be displayed normally and instructs the UI engine to send the card's component tree information to the backend rendering service, which then performs rendering and displays the card content accordingly.

[0181] As one possible implementation, the lock screen application executes S103, calling formComponent.obscured([]), and an empty array [] is passed to the card rendering process. The card rendering process traverses the UI component tree of the card. In the screen-on state, the terminal does not consider the privacy attributes of the UI components. The terminal can send the display data of the graphics card to the display screen according to the traversed UI component tree to achieve normal display of the card in the screen-on state.

[0182] As shown in Figure 4B, the terminal can traverse the card's components 1-11 and other components, and send the display data of the card to the display screen according to the traversed UI component tree.

[0183] Optionally, the card rendering process iterates through N cards from the M applications that need to be displayed on the lock screen. M and N are both positive integers.

[0184] As mentioned above, as a possible implementation, in the screen-on state, after the user's identity information is verified, the terminal can display components involving privacy. As shown in Figure 7(3), after the legitimate user's face unlock is successful, the mobile phone can remove the mask on component 206 in card 205 so that the display content of component 206 (such as the user's step count) can be displayed.

[0185] S105. When the screen is off, the lock screen application displays the lock screen interface.

[0186] For example, as shown in Figure 5(1), in the screen-off state, the lock screen application displays the lock screen interface under the screen-off state.

[0187] S106. The lock screen app instructs the card management service to display a privacy mask.

[0188] As one possible implementation, the lock screen app calls the formComponent.obscured method and passes relevant parameters for mask display in the method to indicate whether to display the privacy mask or to indicate that the mask should be activated.

[0189] For example, the format of the formComponent.obscured method to indicate that the privacy mask should not be displayed is formComponent.obscured([ObscuredReasons.PLACEHOLDER]). The ObscuredReasons.PLACEHOLDER parameter can indicate that the displayed data is replaced by a mask.

[0190] Using this method, the terminal can determine whether to enable or disable the privacy mask by checking whether the formComponent.obscured method has the ObscuredReasons.PLACEHOLDER parameter, thereby enabling control over the display and hiding of privacy content.

[0191] S107a, Card management service obtains privacy components on the card.

[0192] As illustrated above, the lock screen application calls the method `formComponent.obscured([ObscuredReasons.PLACEHOLDER])`. After the `ObscuredReasons.PLACEHOLDER` parameter is passed to the card rendering process, the process can traverse the card's UI component tree and query the UI engine for the card components' attributes. If a component has privacy attributes, the rendering process can determine that the component is a privacy component. The rendering process can then indicate the privacy attributes of the corresponding component to the card management service, allowing the service to recognize that the component is a privacy component. Alternatively, the rendering process can directly indicate that the corresponding component is a privacy component to the card management service. In this way, the card management service can hide privacy components within the card.

[0193] For example, as shown in Figure 7(1), in AOD state, the phone displays card 205 on interface 201. The attribute of component 206 in card 205 is a privacy attribute. The attributes of other components in card 205 are non-privacy attributes. The phone can hide the displayed content in component 206 according to the privacy attribute of component 206, such as hiding the user's step count information. The phone can display corresponding content through other components according to their non-privacy attributes. For example, displaying a shoe icon.

[0194] S107b, the card management service masks the display content of privacy components on the card on the lock screen.

[0195] For example, in Figure 5(1), when the screen is off and in AOD state, the phone displays card 101 on the lock screen interface. The content of the privacy component outlined in the dotted frame of card 101 is covered to prevent the privacy content from being viewed by others.

[0196] In some embodiments, the cards displayed on the lock screen or in the Always-On Display (AOD) state can be the card examples shown in Figures 6A, 6B, 7, 9, 10, and 11, and these cards can be displayed together on the same lock screen. For example, in some scenarios, the lock screen includes both the calendar component in Figure 6B and the QR code component in Figure 7.

[0197] For example, in a QR code scenario, when the screen is off, the lock screen application displays a privacy mask over the QR code. The card management service can then determine the privacy components within the QR code card. As shown in Figure 7(1), the dashed box area in the QR code card 202 (an example of the first card) is the area where the privacy components are located. Other areas are areas where the privacy components are not. The card management service displays a mask 203 over the QR code in the dashed box area (an example of the first area) to cover the QR code (an example of the second content) displayed through the QR code component (an example of the second component). The card management service displays the content of the non-privacy components in the corresponding areas in other areas, such as displaying the words "Pay" (an example of the first content of the first component).

[0198] The terminal can mask the display content of the privacy component on the card, or it can be understood or replaced as the terminal replacing the display content of the privacy component with the mask. The pattern, color, style, etc., of the mask are not limited.

[0199] Using this method, the terminal can intelligently and automatically mask displaying content involving privacy, eliminating the need for users to anonymize information through methods such as manual drawing, making it more efficient and convenient.

[0200] This application also provides an always-on display method, in which the terminal can determine whether to hide the content of the privacy component in the card by combining the terminal's status information or the user's status information.

[0201] The terminal's status information includes at least one of the following: the terminal's location, the connection status of external devices connected to the terminal, or the terminal's device posture. Alternatively, the user's status information includes at least one of the following: the user's behavior, or the user's habits during the corresponding time period.

[0202] Taking barcode scenarios as an example, the terminal can determine the user's intention to use the barcode and quickly retrieve the corresponding barcode when the user expresses this intention, thus meeting the user's barcode usage needs. In other scenarios, the terminal restores the mask over the barcode to reduce the security risks associated with exposing the barcode.

[0203] In one or more embodiments of this application, the barcode can be any type of barcode or QR code. For example, a payment code, a subway code, or a bus code; there is no limitation.

[0204] For example, as shown in Figure 9(1), the phone screen is off, and a card 202 is displayed on the lock screen interface 201. The card 202 includes a QR code mask 203. As shown in Figure 9(2), if the phone is detected to be flipped, with the screen facing down and the back facing up, and the angle between the screen and the horizontal plane meets the condition, indicating that the user is likely to intend to use QR code payment, the phone can remove the mask 203 at the position of the dotted frame in the card 202, allowing the QR code to be displayed on the screen. Using this method, on the one hand, the probability of privacy leakage is low when the terminal screen is facing down. On the other hand, the user does not need to manually operate the terminal to trigger the display of the QR code. This method can balance the requirements of security and efficiency.

[0205] For example, when a phone detects that a user has arrived at the subway, and the user flips the phone so that the screen is facing away from them (towards the subway turnstile), it means the user wants to scan a QR code on the subway station. In this case, the phone can either turn the screen off or on to display a card containing the QR code. This way, the user can refresh the subway code without manually operating the phone, improving the efficiency of human-computer interaction.

[0206] For example, a phone can be set to display cards containing private information when the screen is off while at home. Taking the calendar app as an example, in this setting, when the phone is detected as being at home, it can display cards from the calendar app containing meeting schedule information using AOD (Always On Demand). When the phone is detected as not being at home (e.g., in the office), the calendar cards displayed using AOD will not include meeting schedule information, thus preventing privacy leaks in high-security situations.

[0207] For example, based on user habits, the phone is set to display a card containing private content when the screen is off between 8:00 PM and 10:00 PM.

[0208] For example, as shown in Figure 10(1), the phone's screen-off display interface 401 includes cards 402 recommended by Xiaoyi. The dashed frame area of ​​card 402 includes the privacy component of the audio application, the content of which is hidden by a mask. When the phone is detected to be connected to headphones, or the headphones are close to the phone, it means that the user is likely to want to listen to the audio of the audio application. In this case, as shown in Figure 10(2), the phone can remove the mask of the dashed frame area to display the audio list of the audio application. In this way, the terminal can quickly display the audio list in the card according to the user's audio listening needs.

[0209] Optionally, as one possible implementation, upon detecting that the phone is connected to the headphones, the phone can unmask the area within the dotted box, indicating that the phone has detected a previously connected headphone. In other words, the phone is connected to a previously verified headphone.

[0210] In some embodiments, the terminal can also combine the verification results of user status and identity information to determine whether to hide the content of privacy components in the card. For example, an under-display fingerprint collection module can be set in the mobile phone, or a fingerprint collection module can be set in a position such as the power button. As shown in Figure 9(1), the mobile phone displays a card 202 without QR code information when the screen is off. Then, as shown in Figure 9(2), it is detected that the mobile phone has been flipped to face down and the user's fingerprint collected by the fingerprint collection module has been verified. The mobile phone can remove the cover on the QR code information to facilitate the user to use the QR code quickly.

[0211] In some embodiments, the terminal may also combine the verification results of the terminal status and identity information to determine whether to hide the content of the privacy components in the card.

[0212] Alternatively, other methods can be used to enable the terminal to display the private content in the card when the screen is off, in scenarios where the user needs to view private content and the probability of privacy leakage is low, so as to balance the requirements of security and usage efficiency.

[0213] The solution of displaying private content in a card when the screen is off, based on the user's or the terminal's status, can also be applied to scenarios where the screen is on. For example, when the screen-on conditions are met (such as when the user double-tap the screen), the phone detects that the user is in a shopping mall, the phone is flipped face down, and the user's fingerprint verification is successful, the phone can quickly display a payment QR code.

[0214] The above examples use the case where the lock screen when the screen is off and the lock screen when the screen is on as being the same or similar. In other examples, the lock screen when the screen is off and the lock screen when the screen is on are different. For example, the lock screen when the screen is off includes cards 1 and 2, while the lock screen when the screen is on includes cards 1-4, and so on.

[0215] In the above-mentioned schemes such as the one corresponding to Figure 5, taking the screen turning off first and then turning on as an example, in some embodiments, the screen can also be turned on first and then turned off, without restriction.

[0216] This application also provides an always-on display method, in which the terminal, by default, displays a mask over the privacy components in the card when displaying on AOD. When a legitimate user's face is detected approaching the terminal, the terminal automatically removes the mask.

[0217] As shown in Figure 11(1), the mobile phone AOD display interface 301 includes a sports and health card 302, which does not display specific sports and health information. As shown in Figure 11(2), when the mobile phone detects a legitimate user's face approaching the phone, it can display specific sports and health information in the card 302. Here, facial recognition is used as the authentication method. The authentication method involved in one or more embodiments of this application can also be replaced by fingerprint verification or other methods.

[0218] The above only lists a few scenarios in which the solutions of this application are applicable. Other scenarios, such as message notifications, food delivery, and logistics information of shopping software, can also adopt this solution.

[0219] The above example uses a masking scheme in an AOD (Away From Home) scenario. The scheme in this application can also be applied to non-AOD scenarios, and this application does not limit the applicable scenarios. As long as certain conditions are met to cover the content of the privacy components in the card, and under other conditions to display the content of the privacy components in the card, all are within the scope of protection of this application.

[0220] For example, as shown in Figure 12(1), the mobile phone displays interface 501, which includes the content of the work minutes. If the mobile phone detects that someone else is approaching the phone while the user is reading the work minutes, a mask can be displayed in the dashed box area shown in Figure 12(2) to hide the sensitive information in the work minutes.

[0221] In some embodiments, the terminal may also provide a settings interface related to always-on display. For example, as shown in Figure 13(1), the phone displays interface 601, which (an example of a first interface) may include a switch 602 and a settings item 604. When the switch 602 is turned on, enabling the scheme of this application embodiment, the phone can hide or show the content of privacy components. In some examples, in response to the user clicking the settings item 604, the phone can jump to interface 603 (an example of a second interface) as shown in Figure 13(2). The user can set the applications that need to be masked through this interface. As shown in Figure 13(2), if the calendar application is checked, the phone can mask the privacy content of the calendar application's cards. Similarly, the phone can mask the privacy content of the food delivery application's cards. Using this method, applications that need to hide privacy content can be set in a personalized way to meet the user's privacy protection needs.

[0222] In one or more embodiments of this application, in order to reduce the power consumption of AOD (Ahead-On Display), AOD can be activated only when certain conditions are met. For example, AOD can be activated when a user is detected approaching. Or, AOD can be deactivated when the phone is detected being put into a pocket, and AOD can be activated when the phone is detected being taken out of a pocket.

[0223] The interfaces shown in the embodiments of this application are illustrative, and the implementation of some interfaces can be referred to the description in other parts of this document, which will not be repeated here. For example, the implementation of (2) and (4) in Figure 7 can be referred to the similar methods in this document.

[0224] For example, Figure 14 shows a schematic flowchart of another always-on display method provided in an embodiment of this application. This method can be applied to a terminal with a display screen. As shown in Figure 14, the method includes the following steps:

[0225] S201. When the terminal is in Always-On Display (AOD) state, it displays a first card of a first application that includes first content, wherein the content displayed on the first card does not include second content.

[0226] For example, as shown in Figure 5(1), when the terminal is in Always On Display (AOD) state, it displays a card 101 of a calendar application that includes date information (an example of the first content), wherein the content displayed on the card 101 does not include meeting schedule information (an example of the second content).

[0227] As one possible implementation, when the terminal is in AOD state, displaying a first card of a first application including first content can be achieved by displaying a mask in a first area of ​​the first card, with the mask covering the second content.

[0228] For example, as shown in (1) of FIG7, the terminal displays a mask 203 of the QR code in the dashed box area (an example of the first area) of the QR code card 202 to cover the QR code involving privacy.

[0229] Optionally, the first card displays first content through a first component, the first component being identified by a non-privacy identifier, which is used to identify the non-privacy component. The first card displays second content through a second component, the second component being identified by a privacy identifier, which is used to identify the privacy component.

[0230] Optionally, the privacy flag is preset in the installation package of the first application.

[0231] As one possible implementation, in AOD state, the terminal does not display the second component and displays the first component based on the non-privacy identifier of the first component of the first card and the privacy identifier of the second component; in screen-on state, the second component is displayed.

[0232] As one possible implementation, when the terminal is in Always-On Display (AOD) state, it displays a first card containing the first content of the first application. This can be achieved by displaying a mask in the area corresponding to the second component in the first card according to the privacy identifier of the second component.

[0233] Optionally, the first card may further include a third component, wherein the first card displays third content through the third component. The method may further include: displaying a first card including the first content but excluding the second and third content when the screen is off (AOD); and displaying a first card containing the first, second, and third content when the terminal is in a screen-on state.

[0234] Optionally, the terminal also includes a second card for the second application. Correspondingly, the method may further include: displaying a second card for the second application that includes fourth content but does not include fifth content in an Always-On Display (AOD) state; and displaying a second card that includes both the fourth and fifth content when the terminal is in a screen-on state.

[0235] Other specific implementations of S201 can be found in the relevant steps of the foregoing embodiments, such as S105-S107, and will not be repeated here.

[0236] S202. When the terminal screen is on and the lock screen interface is displayed, a first card including first content and second content is displayed.

[0237] For example, as shown in Figure 5(2), when the terminal screen is lit up and the lock screen interface is displayed, a card 101 including date information and meeting schedule information is displayed.

[0238] The specific implementation of S202 can be referred to the relevant steps of the foregoing embodiments, such as S101-S104, and will not be repeated here.

[0239] The above primarily describes the solutions provided by the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the above functions, the electronic device includes hardware structures and / or software modules corresponding to the execution of each function. Based on the units and algorithm steps of the various examples described in the embodiments disclosed in this application, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by a computer driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solutions of the embodiments of this application.

[0240] This application provides embodiments for dividing an electronic device into functional modules based on the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into a single processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the unit division in this application embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used.

[0241] Figure 15 shows a schematic diagram of an electronic device provided in an embodiment of this application. This electronic device 2200 can be used to implement the methods described in the above method embodiments. For example, the electronic device 2200 may specifically include a processing unit 2201 and a display unit 2202.

[0242] The processing unit 2201 is used to support the electronic device 2200 in performing the processing function described in any one of Figures 2 to 14.

[0243] Display unit 2202 is used to support electronic device 2200 in performing the display function described in any one of Figures 2 to 14.

[0244] Optionally, the electronic device 2200 shown in FIG15 may further include a communication unit (not shown in FIG15) for supporting the electronic device 2200 in performing the steps of communication between the electronic device and other electronic devices in the embodiments of this application.

[0245] Optionally, the electronic device 2200 shown in FIG15 may further include a storage unit 2203, which stores programs or instructions. When the processing unit 2201 executes the program or instructions, the electronic device 2200 shown in FIG15 can perform the method shown in the above-described method embodiment.

[0246] The technical effects of the electronic device 2200 shown in Figure 15 can be referred to the technical effects of the method shown in the above method embodiments, and will not be repeated here. The processing unit 2201 involved in the electronic device 2200 shown in Figure 15 can be implemented by a processor or processor-related circuit components, and can be a processor or a processing module. The communication unit can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or a transceiver module. The display unit 2202 can be implemented by display screen-related components.

[0247] This application also provides a chip system, as shown in FIG16, which includes at least one processor 2301 and at least one interface circuit 2302. The processor 2301 and the interface circuit 2302 can be interconnected via lines. For example, the interface circuit 2302 can be used to receive signals from other devices. As another example, the interface circuit 2302 can be used to send signals to other devices (e.g., the processor 2301). Exemplarily, the interface circuit 2302 can read instructions stored in a memory and send the instructions to the processor 2301. When the instructions are executed by the processor 2301, the electronic device can perform the various steps performed by the electronic device in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in this application.

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

[0249] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application does not specifically limit the type of memory or the arrangement of the memory and processor.

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

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

[0252] This application also provides a computer storage medium storing computer instructions, which, when executed on an electronic device, cause the electronic device to perform the methods described in the above-described method embodiments.

[0253] This application provides a computer program product, which includes a computer program or instructions that, when run on a computer, cause the computer to perform the methods described in the above-described method embodiments.

[0254] In addition, this application also provides an apparatus, which may specifically be a chip, component or module. The apparatus may include a connected processor and a memory. The memory is used to store computer execution instructions. When the apparatus is running, the processor can execute the computer execution instructions stored in the memory to cause the apparatus to perform the methods in the above-described method embodiments.

[0255] In this embodiment, the electronic device, computer storage medium, computer program product or chip are all used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding method provided above, and will not be repeated here.

[0256] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0257] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The embodiments can be combined with or referenced to each other without conflict. The apparatus embodiments described above are merely illustrative; for example, the division of modules or 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 device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0258] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0259] 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 as a software functional unit.

[0260] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0261] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for displaying an always-on display, characterized in that, The method includes: When the terminal is in Always On Display (AOD) state, it displays a first card of a first application that includes first content, wherein the content displayed on the first card does not include second content; When the terminal displays the lock screen interface, it displays the first card, which includes the first content and the second content.

2. The method according to claim 1, characterized in that, When the terminal is in Always-On Display (AOD) mode, it displays a first card for a first application that includes first content, including: A mask is displayed in a first area of ​​the first card, the mask covering the second content.

3. The method according to claim 1 or 2, characterized in that, Also includes: After the user's identity information is verified, the screen lights up to display the unlock interface, which shows the first card containing the first content and the second content.

4. The method according to any one of claims 1-3, characterized in that, Also includes: After the user's identity information is verified, the screen lights up to display the desktop, which displays a first card that includes the first content and the second content.

5. The method according to any one of claims 1-4, characterized in that, The first card displays the first content through a first component, the first component being identified by a non-privacy identifier, which is used to identify the non-privacy component.

6. The method according to any one of claims 1-5, characterized in that, The first card displays the second content through a second component, the second component being identified by a privacy identifier, which is used to identify the privacy component.

7. The method according to any one of claims 1-6, characterized in that, The first component is identified as a non-privacy identifier, the second component is identified as a privacy identifier, and the method further includes: In the Always On Display (AOD) state, based on the non-privacy identifier of the first component and the privacy identifier of the second component on the first card, the second component is not displayed, and the first component is displayed; in the screen-on state, the second component is displayed.

8. The method according to any one of claims 1-7, characterized in that, When the terminal displays the lock screen interface, it acquires at least one card information from the lock screen interface and displays the card, which includes the first card.

9. The method according to any one of claims 1-8, characterized in that, When the terminal is in Always-On Display (AOD) mode, it displays a first card for a first application that includes first content, including: Based on the privacy identifier of the second component, a mask is displayed in the area corresponding to the second component in the first card.

10. The method according to any one of claims 1-9, characterized in that, The first card further includes a third component, the third component being identified as a privacy identifier; the method further includes: In the Always-On Display (AOD) state, a first card is displayed that includes the first content but does not include the second content or the third content; the first card displays the third content through the third component. When the terminal is in the screen-on state, it displays the first card containing the first content, the second content, and the third content.

11. The method according to any one of claims 1-10, characterized in that, The terminal also includes a second card for the second application, and further includes: In the Always On Display (AOD) state, a second card of a second application is displayed, which includes the fourth content, wherein the content displayed on the second card does not include the fifth content; When the terminal is in the screen-on state, it displays the second card, which includes the fourth content and the fifth content.

12. The method according to any one of claims 1-11, wherein the terminal further comprises a second card for a second application, characterized in that, The method further includes: When the terminal is in the Always On Display (AOD) state, it displays a second card that includes a fourth piece of content, wherein the content displayed on the second card does not include a fifth piece of content; When the terminal displays the lock screen interface, it displays the second card, which includes the fifth content and the fourth content.

13. The method according to any one of claims 6, 7, 9 or 10, characterized in that, The privacy identifier is preset in the installation package of the first application.

14. The method according to any one of claims 1-13, characterized in that, The first application includes at least one of the following categories: payment application, calendar application, note-taking application, messaging application, food delivery application, shopping application, or health application; Alternatively, the second content may include at least one of the following: schedule information, barcode information, logistics information, food delivery information, or health information.

15. The method according to any one of claims 1-14, characterized in that, Also includes: The first interface is displayed, and the first interface includes a first setting item, which is used to enable the always-on display method.

16. The method according to any one of claims 1-15, characterized in that, Also includes: The second interface is displayed, which is used to set the application that enables the always-on display method. The application that enables the always-on display method includes the first application.

17. A computer-readable storage medium, characterized in that, Includes a program or instructions that, when executed, implement the method as described in any one of claims 1 to 16.

18. A computer program product, characterized in that, It includes a program or instructions that, when the computer program product is run on a communication device, cause the communication device to perform the method as described in any one of claims 1 to 16.

19. An always-on display device, characterized in that, Includes units or modules for performing the method as described in any one of claims 1 to 16.

20. An always-on display device, characterized in that, Includes a processor for implementing the method as described in any one of claims 1 to 16.

21. An electronic device, characterized in that, include: The electronic device includes a display screen, a processor, and a memory, wherein the display screen, the memory, and the processor are coupled together, the memory being used to store program code including instructions, and the processor reading the instructions from the memory to cause the electronic device to perform the method as described in any one of claims 1-16.

Images