Display control method and electronic equipment

By adding a removal reason identifier to the display elements of smartphones and managing their removal and recovery according to different information, the problem of complex logic control is solved, flexible and accurate display elements are achieved and development efficiency is improved.

CN120343152APending Publication Date: 2025-07-18HONOR DEVICE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410042427.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-01-10
Publication Date
2025-07-18

AI Technical Summary

Technical Problem

How to flexibly and accurately control and manage the removal and recovery of display elements on the smartphone desktop, especially when users use multiple applications, avoiding complex logical operations.

Method used

By adding a removal reason identifier to the display element, the removal and recovery of the display element is managed based on different information (such as manual deletion by the user, changes in the entry control status, changes in the service node priority, etc.), and the identification mark is used to determine the removal and recovery timing of the display element.

Benefits of technology

It realizes flexible and accurate control of display elements, simplifies operation logic, and improves development efficiency and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120343152A_ABST
    Figure CN120343152A_ABST
Patent Text Reader

Abstract

The invention discloses a display control method and electronic equipment. When the method is applied to the electronic equipment, the method comprises the steps that first information is detected, and the first information is used for determining display elements of a display entrance needing to be removed; determining a first removal reason identifier for removing a display element of the display entrance according to the first information; a first removal reason identifier is added to the display element of the display entrance, the display element of the display entrance corresponds to at least one removal reason identifier after the first removal reason identifier is added, and the at least one removal reason identifier is used for recovering the display element of the display entrance. By adopting the method and the device, the removal or recovery of the display elements of the entrance can be flexibly and accurately controlled.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the technical field of terminals, and in particular, to a display control method and an electronic device. Background Art

[0002] Smartphones are becoming more and more powerful. People can use smartphones to hail a taxi, order takeout, book train tickets, book flights, watch movies, etc. To use these services, smartphones often need to install a large number of applications. In order to track the progress of the services, users have to enter the corresponding applications to query. For example, users must enter the taxi-hailing software to check whether the driver has accepted the order and how far the driver is from themselves. Another example is to enter the takeout software to check whether the takeout has been shipped. When the phone has installed enough applications, users constantly search for the corresponding applications and enter the applications to view the service progress information. To facilitate users' viewing, the service progress information will be displayed at various entrances. For example, it is displayed in the form of cards at the desktop entrance. However, how to flexibly and accurately control the removal or restoration of the display elements at various entrances has become an urgent problem to be solved. Summary of the Invention

[0003] The purpose of this application is to provide a display control method and an electronic device. By superimposing removal reason identifiers, it is possible to simply and accurately manage one or more removal reasons for removing the display elements of the display entrance, which is convenient for flexibly and accurately controlling whether to restore the display elements of the display entrance, making both the removal and restoration of the display elements of the display entrance flexible and accurate, and without complex logic, it can also improve the development efficiency.

[0004] The above objectives and other objectives will be achieved by the features in the independent claims. Further implementation means are reflected in the dependent claims, the description, and the drawings.

[0005] In a first aspect, a display control method is provided, including:

[0006] Detecting a first piece of information, where the first piece of information is used to determine the display elements of the display entrance that need to be removed;

[0007] Determining a first removal reason identifier for removing the display elements of the display entrance according to the first piece of information;

[0008] Adding the first removal reason identifier to the display elements of the display entrance. After adding the first removal reason identifier, the display elements of the display entrance correspond to at least one removal reason identifier, and the at least one removal reason identifier is used to restore the display elements of the display entrance.

[0009] When implementing the method of the first aspect, when the first information for determining the display element that needs to remove the display entry is detected, the removal reason identifier for the display element that removes the display entry this time is determined according to the first information, so as to add the removal reason identifier to the display element of the display entry. One or more removal reason identifiers can be superimposed on the display element of the display entry. Through the superimposed one or more removal reason identifiers, it is relatively simple and accurate to manage one or more removal reasons for the display element that removes the display entry, which is convenient for flexibly and accurately controlling the timing of restoring the display element of the display entry, making both the display element that removes the display entry and the display element that restores the display entry flexible and accurate, and without complex logic, it can also improve the development efficiency.

[0010] Combined with the first aspect, in a possible implementation manner, before the first information is detected, the display element of the display entry is in a created state or an updated state. After adding the first removal reason identifier, the display element of the display entry corresponds to one removal reason identifier, and the one removal reason identifier is the first removal reason identifier; the method further includes: removing the display element of the display entry;

[0011] Before the first information is detected, the display element of the display entry is in a removed state. After adding the first removal reason identifier, the display element of the display entry corresponds to at least two removal reason identifiers, and the at least two removal reason identifiers include the first removal reason identifier.

[0012] In this implementation manner, before adding the removal reason identifier determined according to the first information, the display element of the display entry has not been removed, so it can be understood that the first removal reason identifier is added to the display element of the display entry, and the display element of the display entry is removed, so as to accurately control the removal timing of the display element of the display entry. If the display element of the display entry has been removed before adding the removal reason determined according to the first information, the removal reasons are superimposed, so that various removal reasons for the display element that removes the display entry can be effectively managed, and it is also convenient to control the restoration timing of the display element of the display entry.

[0013] Combined with the first aspect, in a possible implementation manner, the first information is a deletion instruction for instructing the user to manually delete the display element of the display entry;

[0014] The display element of the display entry that needs to be removed is the display element of the display entry manually deleted by the user;

[0015] The first removal reason identifier is the first identifier, and the first identifier indicates that the removal reason is manual deletion by the user.

[0016] In this embodiment, when a deletion instruction for a display element of a display entry manually deleted by the user is detected, a first identifier for indicating that the user has manually deleted it is added to the display element of the display entry manually deleted by the user, so as to effectively manage the reason for removing the display element of the display entry manually deleted by the user.

[0017] In combination with the first aspect, in a possible implementation, the first information is a first switch change instruction for indicating the closing of a first entry control, and the first entry control is associated with display elements of one or more display entries;

[0018] The display elements of the display entry to be removed are the display elements of the one or more display entries associated with the first entry control;

[0019] The first removal reason identifier is a second identifier, and the second identifier indicates that the reason for removal is the closing of the entry control.

[0020] In this embodiment, when a switch change instruction for the user to close the entry control is detected, a second identifier for indicating the closing of the entry control is added to the display elements of the associated display entry, so as to effectively manage the reason for the user to manually close the entry control and remove it.

[0021] In combination with the first aspect, in a possible implementation, the first information is first priority change information for indicating that an application service is switched from a high-priority service node to a low-priority service node;

[0022] The display elements of the display entry to be removed are the display elements of the display entry other than the display elements of the one or more display entries associated with the low-priority service node among the display elements of the one or more display entries associated with the high-priority service node;

[0023] The first removal reason identifier is a third identifier, and the third identifier indicates that the reason for removal is the reduction of the priority of the service node.

[0024] In this embodiment, when the priority change information when the application service is switched from a high-priority service node to a low-priority service node, a third identifier for indicating the reduction of the priority is added to the display elements of the display entry to be removed, so as to effectively manage the reason for the display elements of the display entry to be removed when the service node is reduced from a high service node to a low-priority service node.

[0025] In combination with the first aspect, in a possible implementation, the first information is first switching information for indicating that a foreground application is switched to a first application, and the first application is the application to which the service progress information to be displayed by the display elements of the display entry to be removed belongs; The method further includes:

[0026] The display element of the display entry to be removed is the display element of the display entry that is on the same user interface as the application page of the foreground application;

[0027] The first removal reason identifier is the fourth identifier, and the fourth identifier indicates that the removal reason is a conflict with the foreground application.

[0028] In this embodiment, when the display element of the display entry conflicts with the foreground application in display, the conflict display can be understood as the repeated display of service progress information on the same user interface, and a fourth identifier for indicating a conflict with the foreground application can be added to the display element of the associated display entry. Thus, the removal reasons conflicting with the foreground application can be effectively managed.

[0029] Combined with the first aspect, in a possible embodiment, the method further includes:

[0030] Detecting second information, where the second information is used to determine the display element of the display entry to be restored;

[0031] Determining a second removal reason identifier for restoring the display element of the display entry according to the second information;

[0032] If the display element of the display entry corresponds to one removal reason identifier, and the one removal reason identifier is the second removal reason identifier, then restore the display element of the display entry;

[0033] If the display element of the display entry corresponds to at least two removal reason identifiers, and the at least two removal reason identifiers include the second removal reason identifier, then delete the second removal reason identifier.

[0034] In this embodiment, when the second information for restoring the display element of the display entry is detected, if the display element of the display entry corresponds to one removal reason identifier, and it is the removal reason determined according to the second information, then directly restore the display element of the display entry and delete the removal reason identifier determined according to the second information. If the display element of the display entry corresponds to multiple removal reason identifiers, then delete the removal reason identifier determined according to the second information, and the display element of the display entry will not be restored. This method accurately controls the restoration timing of the display element of the display entry by deleting the removal reason identifiers of the display element of the display entry layer by layer. This restoration method has simple and clear control logic and can also reduce development efficiency.

[0035] Combined with the first aspect, in a possible embodiment, the second information is status update information for indicating an update of a service node of an application service;

[0036] The display element of the display entry to be restored is the display element of the display entry manually deleted by the user;

[0037] The second removal cause is identified as a first identifier, and the first identifier indicates that the removal cause is manual deletion by the user.

[0038] In this embodiment, when the application service updates service nodes, the first identifier indicating manual deletion by the user can be deleted, so as to accurately indicate that the cause of manual deletion by the user has been eliminated. If there are other removal cause identifiers after deleting the first identifier, they will not be restored. If there are no other removal cause identifiers after deleting the first identifier, the display elements of the display entry will be restored, so that it is also possible to flexibly and accurately control whether to restore the display elements of the display entry.

[0039] In combination with the first aspect, in a possible embodiment, the second information is a second switch change instruction for indicating the opening of a second entry control, and the second entry control is associated with display elements of one or more display entries;

[0040] The display elements of the display entry to be restored are the one or more display elements associated with the second entry control;

[0041] The second removal cause is identified as a second identifier, and the second identifier indicates that the removal cause is the closing of the entry control.

[0042] In this embodiment, when the entry control is opened, the second identifier indicating the closing of the entry control corresponding to the display elements of the associated display entry can be deleted, so as to accurately indicate that the removal cause of the entry control closing has disappeared, and it is also possible to flexibly and accurately control whether to restore the display elements of the display entry.

[0043] In combination with the first aspect, in a possible embodiment, the second information is second priority change information for indicating that the application service switches from a low-priority service node to a high-priority service node;

[0044] The display elements of the display entry to be restored are the display elements of the display entry other than the one or more display elements associated with the low-priority service node among the one or more display elements associated with the high-priority service node;

[0045] The second removal cause is identified as a third identifier, and the third identifier indicates that the removal cause is the reduction of the priority of the service node.

[0046] In this embodiment, when the application service switches from a low-priority service node to a high-priority service node, the removal cause identifier indicating the reduction of the service node priority of the relevant display entry display elements can be deleted, so as to accurately indicate that the removal cause of the priority reduction has disappeared, and it is possible to flexibly and accurately control whether to restore the display elements of the display entry.

[0047] In combination with the first aspect, in a possible implementation, the second information is second switching information for instructing a first application to switch to running in the background, and the first application is the application to which the service progress information to be displayed by the display element of the display entry to be restored belongs;

[0048] The display element of the display entry to be restored is the display element of the display entry that is on the same user interface as the application page of the foreground application;

[0049] The second removal reason identifier is a fourth identifier, and the fourth identifier indicates that the removal reason is a conflict with the foreground application.

[0050] In this implementation, when the application associated with the service progress information displayed by the display element of the display entry switches to running in the background, the removal reason identifier for the conflict with the foreground application of the display element of the relevant display entry can be deleted, thereby indicating that the removal reason for the conflict with the foreground application has been eliminated, and whether to restore the display element of the display entry can be flexibly and accurately controlled.

[0051] In a second aspect, a display control method is provided, including:

[0052] Detecting second information, the second information being used to determine a display element of a display entry to be restored;

[0053] Determining a second removal reason identifier for restoring the display element of the display entry according to the second information;

[0054] If the display element of the display entry corresponds to one removal reason identifier, and the one removal reason identifier is the second removal reason identifier, then restore the display element of the display entry;

[0055] If the display element of the display entry corresponds to at least two removal reason identifiers, and the at least two removal reason identifiers include the second removal reason identifier, then delete the second removal reason identifier.

[0056] In combination with the second aspect, in a possible implementation, first information is detected, the first information being used to determine a display element of a display entry to be removed;

[0057] Determining a first removal reason identifier for removing the display element of the display entry according to the first information;

[0058] Adding the first removal reason identifier to the display element of the display entry, and after adding the first removal reason identifier, the display element of the display entry corresponds to at least one removal reason identifier, and the at least one removal reason identifier is used to restore the display element of the display entry.

[0059] For other possible implementation manners of the second aspect and the beneficial effects, reference may be made to the various possible implementation manners of the first aspect and the beneficial effects of the various possible implementation manners of the second aspect, which will not be elaborated herein.

[0060] In a third aspect, an embodiment of the present application provides an electronic device, which includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the electronic device to execute the method in the first aspect or any possible implementation manner of the first aspect, or the one or more processors call the computer instructions to enable the electronic device to execute the method in the second aspect or any possible implementation manner of the second aspect.

[0061] In a fourth aspect, a chip system is provided. The chip system is applied to an electronic device. The chip system includes one or more processors, and the processors are used to call computer instructions to enable the electronic device to execute the method in the first aspect or any possible implementation manner of the first aspect, or the processors are used to call computer instructions to enable the electronic device to execute the method in the second aspect or any possible implementation manner of the second aspect.

[0062] In a fifth aspect, a computer-readable storage medium is provided, including instructions. When the above instructions run on an electronic device, the above electronic device is enabled to execute the method in the first aspect or any possible implementation manner of the first aspect, or the above electronic device is enabled to execute the method in the second aspect or any possible implementation manner of the second aspect.

[0063] For the technical solutions provided in the second to fifth aspects of the present application, the beneficial effects can refer to the beneficial effects of the technical solution provided in the first aspect, which will not be elaborated herein. Description of the Drawings

[0064] Figures 1 - 4 Schematic diagrams of some user interfaces provided by an embodiment of the present application;

[0065] Figure 5 An architecture diagram of an electronic device provided by an embodiment of the present application;

[0066] Figure 6 A schematic diagram of a user interface for deleting a desktop card provided by an embodiment of the present application;

[0067] Figure 7 A schematic diagram of state switching provided by an embodiment of the present application;

[0068] Figure 8 Schematic diagram for adding or deleting the removal reason flag provided by the embodiment of the present application;

[0069] Figure 9 Schematic diagram for state transition in the service node update scenario provided by the embodiment of the present application;

[0070] Figure 10 Schematic diagram for state transition in the user manual deletion scenario provided by the embodiment of the present application;

[0071] Figure 11 Schematic diagram for state transition in the switch-on and switch-off scenarios provided by the embodiment of the present application;

[0072] Figure 12 Schematic diagram for state transition in the new conflict addition scenario provided by the embodiment of the present application;

[0073] Figures 13 - 16 Flowchart of the display control method provided by the embodiment of the present application. Detailed implementation manners

[0074] The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification and claims of the present application, the singular forms "a", "an", "the", "above", "said", "this" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in the present application refers to and includes any or all possible combinations of one or more of the listed items.

[0075] Since the embodiments of the present application relate to a display control method and an electronic device, for the sake of easy understanding, the global reach scenario related to the embodiments of the present application will be introduced first below.

[0076] Global reach provides an application service for an electronic device, that is, it transmits and displays the service progress information of the application programs opened by the user at each display entry. For example, it is displayed at various entries such as the desktop entry, the negative first screen entry, the lock screen entry, the notification center entry, the lock screen entry, the global entry, etc., so that the user can view the service progress information that they want to know or pay attention to based on each entry. The display form of the service progress information can be a card and / or a capsule (the card or the capsule can be called a display element). No matter which one of the desktop, the negative first screen, the lock screen, the standby, the notification center, and the application program page the user interface is displayed as, the user can view the service progress information of each opened application program through the card or the capsule in the user interface and know the business service progress. For example, when the user interface displays the home screen page, the service progress information is viewed through the desktop entry; when the user interface displays the negative first screen page, it is viewed through the negative first screen entry. The application service of global reach can improve the convenience for users to view business information. Users do not need to view the service progress information through the specified application program page of the electronic device, and the application service of global reach can improve the user experience.

[0077] The following takes a taxi-hailing application program as an example. As Figure 1 shown, in Figure 1 as shown in (A), the user can start the taxi-hailing application by operating the application icon of the taxi-hailing application, such as a click operation. In Figure 1 as shown in (B), the user inputs the departure place and the destination and operates the confirmation call control. The electronic device responds to the user's operation on the confirmation call control and initiates a call for a network car. After that, in the case of enabling the application service of global reach, the service progress information of taking a taxi can reach each display entry, and the display form can be a card or a capsule. The following will give an example in combination with Figure 2 and Figure 3 It should be noted that the system interface can be displayed in both the form of a card and a capsule at the same time, or can be displayed only in the form of a card or a capsule according to actual needs. When one of the display forms of a card and a capsule is representatively shown in the drawings in the embodiments of the present application, it does not constitute a limitation that only a card or only a capsule can be displayed in the user interface shown in the drawings. Figure 2 In (A) corresponds to the user interface that displays the taxi-taking progress information in the form of a card at the desktop entry. It can be understood that the taxi-taking progress information can also be displayed in the form of a capsule. Figure 2 The service progress information displayed in the card shown in (A) in Figure 2On the left side of "Contact Driver" in (A), the service progress bar has no progress yet. The card provides a display of the taxi-hailing progress information, enabling users to more quickly and clearly understand the progress of taxi-hailing. Alternatively, Figure 2 The desktop card in (A) can also be replaced with a capsule display, which can show the application icon of the taxi-hailing application and the service progress as "Calling". Figure 2 In (B), it corresponds to a user interface where the global entry is displayed in the form of a capsule. In the capsule, the application icon of the taxi-hailing application and the service progress as "Calling" can be shown. Alternatively, Figure 2 The capsule in (B) can also be replaced with a banner card. Figure 2 In (C), it corresponds to a user interface where the global entry is displayed in the form of a banner card. As Figure 2 As shown in (C), the banner card shows service progress information including but not limited to the service progress that the driver has accepted the order, the license plate number of the accepted vehicle and the duration since the order was accepted, the estimated duration from the current moment to the estimated arrival time of the driver, and the other optional service as "Contact Driver". Since the driver has accepted the order during the call, the service progress bar shown in the card has progress. In Figure 2 In (A), Figure 2 In (B) and Figure 2 In the user interfaces shown in (C), taking the display form as an example, the specific displayed content is not limited. For example, Figure 2 The banner card in the user interface shown in (C) can also show the service progress information of "Calling".

[0078] Figure 2 In (A), Figure 2 In (B) and Figure 2 In (A), (B), and (C), the service progress information is shown in the form of a capsule or a card with a relatively small display size and generally placed at the top of the user interface, which can facilitate users to view without affecting their use. Figure 2 Since the banner card in (C) occupies space and affects the display of some application icons, optionally, the banner card can end the display after showing the default duration.

[0079] In some embodiments, the service progress information can also be shown at more display entrances. Next, continue to give examples in combination with Figure 3 for illustration. Figure 3 In (A), it corresponds to a user interface where the negative first screen entry is displayed in the form of a card, and the taxi-hailing service progress information can be shown in the card at the negative first screen entry. Figure 3 In (B), it corresponds to a user interface where the screen-off entry is displayed in the form of a card for the taxi-hailing service progress information. Alternatively, in Figure 3 the card in (B) can also be replaced with a capsule form for display. Figure 3In (C), it corresponds to a user interface where the notification center entry is displayed in the form of a card, and the service progress information of taking a taxi can be displayed in the card of the notification center. Figure 3 In (D), it corresponds to a user interface where the lock screen entry is displayed in the form of a card, and the service progress information of taking a taxi is displayed in the form of a card at the lock screen entry. Optionally, in Figure 3 the card in (D) can also be replaced with a capsule form for display.

[0080] Figure 2 and Figure 3 It is introduced that the service progress information of taking a taxi can be displayed in the form of a card or a capsule at each display entry, and the specific displayed content is not limited. Figure 2 and Figure 3 The displayed content in is only for example. For example, Figure 2 and Figure 3 the service progress information of the ongoing call can be displayed at each display entry.

[0081] The service progress information displayed in the capsule and the card can be updated according to the service progress of the application service. For example, the application service usually divides multiple service nodes according to business requirements, which can also be called multiple scenarios. Taking the taxi application service as an example, calling a network car is a service node, the driver receiving the order is a service node, the driver arriving is a service node, and the passenger getting on the car is a service node. One service node follows another in multiple service nodes. As the service progress changes, it can transfer to the next service node. When transferring from one service node to the next service node, the service progress information in the capsule or the card will be updated. Important service nodes (which can also be called high-priority service nodes) can be configured in multiple service nodes. When transferring to an important service node, the entry can be increased to display the service progress information. For example, if the service progress reaches an important service node, the global banner card will display the service progress information. Among them, the important service nodes of each application service can be configured according to the business. For example: in the business of calling a driver to receive an order, the driver arriving can be configured as an important service node. The examples of service nodes and important service nodes in the embodiments of the present application are only for illustration.

[0082] In some implementation manners, in the above example, when the taxi application is in the background and the user enables the application service with global reach, it is controlled to display the service progress information of the taxi application in the form of a card or a capsule at each entry. It should be noted that when the application service with global reach is not enabled and the target application is in the background, it can be controlled to display the service progress information of the taxi application in the form of a card or a capsule at a specified entry.

[0083] Taking the taxi application as an example above, it can also be the display of the service progress of other applications, such as takeout, movie reservation, and so on.

[0084] In the embodiments of the present application, the service progress information of which applications can be displayed in a globally reachable form, and the user can set it. Further optionally, the display entry for global reach can also be set by the user. Take Figure 4 as an example. For example, the user can enter the service management page through settings. On this service management page, the user can operate the switch control 1 to control whether the service progress information of the ride-hailing application is globally reached to each display entry. The user can operate the switch control 2 to control whether the service progress information of the food delivery application is globally reached to each display entry. The user can operate the switch control 3 to control whether the service progress information of the movie reservation application is globally reached to each display entry.

[0085] As an example, each display entry for global reach can be default. For example, when the user enables the application service for global reach, the display entries where the service progress information will be reached can include the desktop entry, the negative first screen entry, the screen-off entry, the notification center entry, the lock screen entry, and the global entry. The display form (capsule or card) of each display entry can be default. The display form of each display entry can also be referred to as a display element.

[0086] As another example, the opening or closing of each display entry for global reach can be set by the user. For example, as Figure 4 shown, on the service management page, controls for controlling each display entry can be displayed. For example, the user can operate the entry control 1 to control whether the service progress information is displayed on the desktop card. The user can operate the entry control 2 to control whether the service progress information is displayed in the capsule of the global entry. The user can operate the entry control 3 to control whether the service progress information is displayed on the card of the negative first screen. The user can operate the entry control 4 to control whether the service progress information is displayed on the card of the notification center entry. The user can operate the entry control 5 to control whether the service progress information is displayed on the card of the screen-off entry. The user interface for each display entry to display the service progress information can refer to Figure 2 and Figure 3 's description, which will not be elaborated here. In some embodiments, one switch control can also control the opening or closing of multiple display entries. For example, one switch control can control the display or removal of the capsule of the global entry and the card of the desktop entry.

[0087] In some embodiments, the number of display entrances for displaying service progress information may also be updated along with the progress of the application service. For example, for some important service nodes (which may also be referred to as high-priority service nodes), the number of display entrances for displaying service progress information will increase. For example, when using a ride-hailing application to request a ride, the driver's arrival is an important service node. When the service progress reaches the service node of the driver's arrival, a display entrance will be added to display the service progress information "The driver has arrived". For example, a banner card of the global entrance may be added to display the service progress information. Along with the update of the service progress, when reaching the next non-important service node (which may also be referred to as a low-priority service node), the number of display entrances for displaying service progress information will be reduced. For example, when the service progress reaches the service node after the user has boarded the vehicle, the number of display entrances for displaying service progress information may be reduced. For example, the banner card of the global entrance may be removed.

[0088] In this scenario, it can be understood that the urgency of the driver's arrival at this service node is relatively high, which can be regarded as an important service node with a relatively high priority, and this will trigger an increase in the number of display entrances to display the service progress information. As the service progress advances, when the service progress reaches the service node after the user has boarded the vehicle, the urgency of this service node is not high, which can be regarded as a non-important service node with a relatively low priority. The service node changes from a high-priority service node to a low-priority service node, which will trigger a reduction in the number of display entrances to display the service progress information. For example, the card or capsule created in the added display entrance can be removed. That is, the change in the number of display entrances for displaying service progress information can vary with the change in the priority of the transferred service node. When the priority of the transferred service node becomes higher, the number of display entrances for displaying service progress information increases; when the priority of the transferred service node becomes lower, the number of display entrances for displaying service progress information decreases.

[0089] In the embodiments of the present application, the cards or capsules of each display entrance may be removed or restored due to changes in priority, and may also be removed due to reasons such as the user actively deleting the cards or capsules, the user closing the entrance control, or conflicts with the foreground application. However, how to flexibly control the display or removal of the cards or capsules of the display entrance is an urgent problem to be solved. Among them, conflicts with the foreground application can be understood as follows: when the application corresponding to the service progress information is running in the foreground, at this time, the cards or capsules displayed by each display entrance or the cards or capsules of the display entrances belonging to the same user interface as the application page of the foreground application may not need to be displayed. For example, when the service progress information is the service progress information of a ride-hailing application, when the user opens the ride-hailing application, that is, when the ride-hailing application is running in the foreground, at this time, the service progress information of the ride-hailing application may not need to be displayed, and the banner card or capsule of the global entrance can be removed.

[0090] In view of the above defects, the present application provides a display control method and an electronic device. When the display control method is applied to the electronic device, when a card or capsule at a display entry of the electronic device displays service progress information and needs to be removed due to at least one removal reason, at least one removal reason identifier is added to the card or capsule at the display entry. The at least one removal reason may include, but is not limited to, at least one of the following: transfer from a high-priority service node to a low-priority service node, active deletion by the user, the user closing the entry control, conflict with the foreground application, etc. When it is necessary to resume displaying the card or capsule at the display entry, the corresponding removal reason for resuming display is determined, and the removal reason identifier of the card or capsule at the display entry is deleted. If there are no other removal reason identifiers for the card or capsule at the display entry, it can be resumed for display; if there are still other removal reason identifiers, it cannot be resumed for display. Thus, the removal or resumption of the cards or capsules at each entry can be flexibly and accurately controlled, improving the development efficiency.

[0091] The following introduces the electronic device provided in the embodiments of the present application.

[0092] The electronic device may be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc. The present application does not impose any restrictions on the specific type of the electronic device.

[0093] Figure 5 The structure of the electronic device is exemplarily shown.

[0094] As Figure 5As shown in the figure, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0095] It can be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the electronic device 100. In some other embodiments of the present application, the electronic device 100 may include more or fewer components than those shown in the figure, or combine certain components, or split certain components, or have different component arrangements. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0096] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics 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), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0097] The controller may generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

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

[0099] In some embodiments, the 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.

[0100] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 may be respectively coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through the I2C interface, enabling the processor 110 to communicate with the touch sensor 180K through the I2C bus interface to implement the touch function of the electronic device 100.

[0101] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple groups of I2S buses. The processor 110 may be coupled to the audio module 170 through the I2S bus to implement communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through the I2S interface to implement the function of answering a call through a Bluetooth headset.

[0102] The PCM interface can also be used for audio communication to sample, quantize, and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled through the PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface to implement the function of answering calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0103] The UART interface is a general-purpose serial data bus for asynchronous communication. This bus can be a two-way communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

[0104] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate through the CSI interface to implement the shooting function of the electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100.

[0105] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to the camera 193, the display screen 194, the wireless communication module 160, the audio module 170, the sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0106] The USB interface 130 is an interface that complies with the USB standard specification, and can specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used for data transmission between the electronic device 100 and peripheral devices. It can also be used to connect a headset to play audio through the headset. This interface can also be used to connect other electronic devices, such as AR devices, etc.

[0107] It can be understood that the interface connection relationships among the modules illustrated in the embodiments of the present invention are only illustrative descriptions and do not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners in the above embodiments, or a combination of multiple interface connection manners.

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

[0109] The power management module 141 is configured to connect to the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives the inputs from the battery 142 and / or the charging management module 140 and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, the wireless communication module 160, etc. The power management module 141 may also be used to monitor parameters such as the battery capacity, the number of battery charge cycles, and the battery health status (leakage, impedance). In some other embodiments, the power management module 141 may also be disposed in the processor 110. In some other embodiments, the power management module 141 and the charging management module 140 may also be disposed in the same device.

[0110] The wireless communication function of the electronic device 100 may be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, and the baseband processor, etc.

[0111] The antenna 1 and the antenna 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication frequency bands. Different antennas may also be multiplexed to improve the utilization rate of the antennas. For example, the antenna 1 may be multiplexed as the diversity antenna of the wireless local area network. In some other embodiments, the antenna may be used in combination with a tuning switch.

[0112] The mobile communication module 150 may provide a solution for wireless communication including 2G / 3G / 4G / 5G, etc., which is 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 may receive electromagnetic waves through the antenna 1, filter, amplify, and perform other processing on the received electromagnetic waves, and then transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modulation and demodulation processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least some functional modules of the mobile communication module 150 may be provided in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be provided in the same device.

[0113] The modulation and demodulation processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. Subsequently, the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed 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 (not limited to the speaker 170A, receiver 170B, etc.), or displays an image or video through the display screen 194. In some embodiments, the modulation and demodulation processor may be an independent device. In other embodiments, the modulation and demodulation processor may be independent of the processor 110 and be provided in the same device as the mobile communication module 150 or other functional modules.

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

[0115] 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, such that electronic device 100 can communicate with a network and other devices through wireless communication technologies. The wireless communication technologies 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 global positioning system (GPS), global navigation satellite system (GLONASS), beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

[0116] Electronic device 100 implements a display function through a GPU, display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, and is connected to display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or change display information. For example, in this application, the GPU may create cards or capsules at each entry and display service progress information in the cards or capsules.

[0117] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

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

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

[0120] The camera 193 is used to capture static images or videos. An object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in standard RGB, YUV, etc. formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0121] The digital signal processor is used to process digital signals. Besides being able to process digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform and the like on the frequency point energy.

[0122] The video codec is used to compress or decompress digital videos. The electronic device 100 can support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple coding formats, such as: Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0123] The NPU is a neural-network (NN) computing processor. By drawing on the structure of the biological neural network, for example, drawing on the transmission mode between human brain neurons, it can quickly process the input information and can also continuously learn by itself. Through the NPU, applications such as intelligent cognition of the electronic device 100 can be realized, such as: image recognition, face recognition, voice recognition, text understanding, etc.

[0124] The external memory interface 120 can be used to connect to an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. For example, files such as music and videos are saved in the external memory card.

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

[0126] The electronic device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor, etc. For example, music playback, recording, etc.

[0127] The audio module 170 is used to convert digital audio information into an analog audio signal for output, and is also used to convert an analog audio input into a digital audio signal. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 can be disposed in the processor 110, or some functional modules of the audio module 170 can be disposed in the processor 110.

[0128] The speaker 170A, also known as the "loudspeaker", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or hands-free calls through the speaker 170A.

[0129] The receiver 170B, also known as the "earpiece", is used to convert an audio electrical signal into a sound signal. When the electronic device 100 answers a call or a voice message, the voice can be listened to by placing the receiver 170B close to the human ear.

[0130] The microphone 170C, also known as the "microphone" or "transmitter", is used to convert a sound signal into an electrical signal. When making a call or sending a voice message, the user can speak close to the microphone 170C with the mouth, and input the sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In some other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also implement a noise reduction function. In some other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and implement a directional recording function, etc.

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

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

[0133] The gyro sensor 180B can be used to determine the motion posture of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 around three axes (i.e., x, y, and z axes) can be determined by the gyro sensor 180B. The gyro sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyro sensor 180B detects the angle of the electronic device 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking of the electronic device 100 through reverse movement to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenes.

[0134] The air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

[0135] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip leather case. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover according to the magnetic sensor 180D. Then, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, the flip cover can be automatically unlocked.

[0136] The acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in all directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device and is applied to applications such as horizontal and vertical screen switching and pedometers.

[0137] A distance sensor 180F is used to measure distance. The electronic device 100 can measure distance by infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 can use the distance sensor 180F to measure distance to achieve fast focusing.

[0138] The proximity light sensor 180G may include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The light-emitting diode may be an infrared light-emitting diode. The electronic device 100 emits infrared light outward through the light-emitting diode. The electronic device 100 uses the photodiode to detect the infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 can use the proximity light sensor 180G to detect that the user holds the electronic device 100 close to the ear during a call, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used for automatic unlocking and locking of the holster mode and pocket mode.

[0139] The ambient light sensor 180L is used to sense the ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the sensed ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in the pocket to prevent accidental touch.

[0140] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access application locks, fingerprint photography, fingerprint answering of incoming calls, etc.

[0141] The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 executes a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of the processor located near the temperature sensor 180J in order to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to avoid abnormal shutdown of the electronic device 100 caused by low temperature. In still other embodiments, when the temperature is lower than yet another threshold, the electronic device 100 boosts the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

[0142] The touch sensor 180K, also known as the "touch control device". The touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also known as the "touch control screen". The touch sensor 180K is used to detect touch operations acting thereon or nearby. The touch sensor can 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 other embodiments, the touch sensor 180K can also be disposed on the surface of the electronic device 100, at a different position from that of the display screen 194.

[0143] The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire vibration signals of the vibrating bone mass of the human vocal part. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure pulsation signals. In some embodiments, the bone conduction sensor 180M can also be disposed in the earphone to form a bone conduction earphone. The audio module 170 can parse out voice signals based on the vibration signals of the vibrating bone mass of the human vocal part acquired by the bone conduction sensor 180M to implement the voice function. The application processor can parse out heart rate information based on the blood pressure pulsation signals acquired by the bone conduction sensor 180M to implement the heart rate detection function.

[0144] The button 190 includes a power-on button, a volume button, etc. The button 190 can be a mechanical button or a touch button. The electronic device 100 can receive button inputs to generate key signal inputs related to the user settings and function control of the electronic device 100.

[0145] The motor 191 can generate vibration prompts. The motor 191 can be used for incoming call vibration prompts and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playing, etc.) can correspond to different vibration feedback effects. Touch operations acting on different areas of the display screen 194 can also correspond to different vibration feedback effects by the motor 191. Different application scenarios (such as time reminder, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0146] The indicator 192 can be an indicator light and can be used to indicate the charging state, power change, and can also be used to indicate messages, missed calls, notifications, etc.

[0147] The SIM card interface 195 is used to connect to a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0148] In the embodiments of the present application, when the processor 110 displays service progress information on the card or capsule at the display entry, if it is necessary to remove the card or capsule at the display entry, the processor 110 can add at least one removal reason identifier to the card or capsule at the display entry. When it is necessary to display the card or capsule at the display entry, the processor 110 can also delete the corresponding removal reason identifier. If there are no other removal reason identifiers for the card or capsule at the display entry, the display can be restored; if there are still other removal reason identifiers, the display cannot be restored.

[0149] The following describes the removal reasons for the card or capsule at the display entry involved in the embodiments of the present application. It can be understood that the reasons listed below are only examples, and other removal reasons may also be included, which are not limited in the present application.

[0150] 1. Manually deleted by the user. When the card or capsule at the display entry is displayed, the user can manually delete the card or capsule at the display entry. Taking the deletion of the card at the desktop entry as an example, as shown in (A) below, the user can operate on the card at the desktop entry. The operation can be a long press or a swipe, etc., which is not limited in the present application. The electronic device responds to the user's operation and displays a delete control. As shown in (B) below, the delete control is displayed in the card, and the user can operate on the delete control displayed in the card. The electronic device responds to the user's operation on the delete control and deletes the desktop card. As shown in Figure 6 for example, when deleting the card at the desktop entry, as shown in (A) below, the user can operate on the card at the desktop entry. The operation can be a long press or a swipe, etc., which is not limited in the present application. The electronic device responds to the user's operation and displays a delete control. As shown in (B) below, the delete control is displayed in the card, and the user can operate on the delete control displayed in the card. The electronic device responds to the user's operation on the delete control and deletes the desktop card. As shown in Figure 6 below (A), the user can operate on the card at the desktop entry. The operation can be a long press or a swipe, etc., which is not limited in the present application. The electronic device responds to the user's operation and displays a delete control. As shown in (B) below, the delete control is displayed in the card, and the user can operate on the delete control displayed in the card. The electronic device responds to the user's operation on the delete control and deletes the desktop card. As shown in Figure 6 below (B), the delete control is displayed in the card, and the user can operate on the delete control displayed in the card. The electronic device responds to the user's operation on the delete control and deletes the desktop card. As shown in Figure 6As shown in (C), the user interface after deleting the card of the desktop entry is presented. In some embodiments, the removal reason manually deleted by the user may correspond to a first flag. For example, the first flag is int REMOVED_FLAG_USER_DELETED = 0x00000001. This first flag indicates that the reason for removing the card or capsule of the display entry is manually deleted by the user. The first flag may also be referred to as the first identifier.

[0151] In the scenario where the user manually deletes the card or capsule of the display entry, if the subsequent application service updates information, for example, when the service progress reaches the next service node, for example, the service node changes from calling a network car-hailing service to the driver accepting the order, the removed card or capsule of the display entry can be restored for display.

[0152] 2. The user manually closes the entry control. Each card or capsule of the display entry can be manually closed or opened by the user. As Figure 4 shown, the user can close or open the display of the card or capsule corresponding to the entry through the entry control. For example, when the user closes the display of the card of the desktop entry through the entry control 1, the service progress information will not be displayed in the card of the desktop entry. Further optionally, the user can also open the display of the card of the desktop entry through the entry control 1. If there is no other removal reason, the card of the desktop entry can be redisplayed. In some embodiments, the removal reason for the user manually closing the entry control may correspond to a second flag. For example, the second flag is int REMOVED_FLAG_SWITCH_CLOSED = 0x00000002. This second flag indicates that the reason for removing the card or capsule of the display entry is that the user manually closes the entry control. The second flag may also be referred to as the second identifier.

[0153] In the scenario where the user manually closes the entry control, the removed card or capsule of the display entry can be redisplayed only if the user manually opens the entry control subsequently.

[0154] 3. The application service switches from a high-priority service node to a low-priority service node. The application service usually divides multiple service nodes according to business requirements, which can also be called multiple scenarios. Taking the car-hailing application service as an example, calling a network car-hailing service is a service node, the driver accepting the order is a service node, the driver arriving is a service node, and the passenger getting on the car is a service node. One service node follows another among the multiple service nodes, and as the service progress changes, it can transfer to the next service node. The transfer between service nodes can be achieved through status updates.

[0155] For some relatively important service nodes, such as service nodes with a relatively high level of urgency, the priority of such service nodes is relatively high. In the embodiments of the present application, such service nodes are referred to as high-priority service nodes. When switching to a high-priority service node, the number of display entrances for displaying service progress information will increase. For example, taking a taxi application service as an example, the driver's arrival is a high-priority service node. When the service progress reaches the service node of the driver's arrival, a display entrance will be added to display the service progress information "The driver has arrived". For example, a banner card of the global entrance will be added to display the service progress information.

[0156] As the service progress is updated, when reaching a low-priority service node, the display entrances for displaying service progress information will be reduced. For example, remove the cards or capsules in the display entrances that were added when switching to a high-priority service node last time. For example, when the service progress reaches the service node after the user has got in the car, the cards or capsules in the display entrances that were added when switching to a high-priority service node last time can be removed. For example, remove the banner card of the global entrance.

[0157] In some embodiments, the reason for the removal of the cards or capsules of the display entrance due to the reduction of the priority of the service node can correspond to the third flag.

[0158] For example, the third flag is int REMOVED_FLAG_LOWER_DEGREE_LEVEL = 0x00000004. This third flag indicates that the reason for the removal of the cards or capsules of the display entrance is the reduction of the priority of the service node. The third flag can also be referred to as the third identifier.

[0159] In the scenario where the cards or capsules of the display entrance are removed due to the reduction of the priority of the service node, if the subsequent service progress reaches the next relatively high-priority service node, the removed cards or capsules of the display entrance can be redisplayed.

[0160] 4. The display of the cards or capsules of the display entrance conflicts with the foreground application. The foreground application can refer to the application corresponding to the service progress information displayed by the cards or capsules of the display entrance. For example, if the cards or capsules of the display entrance display the service progress information of a taxi application, the application corresponding to the service progress information is the taxi application. In other words, when the user opens the taxi application and it is running in the foreground, the cards or capsules of the display entrance on the same user interface as the application page of the taxi application can not display the service progress information of this application, and the cards or capsules of the display entrance are removed. For example, remove the banner card of the global entrance.

[0161] In some embodiments, the removal reason corresponding to the fourth flag may be that the display of the card or capsule at the display entry conflicts with the foreground application, resulting in the removal of the card or capsule at the display entry. The fourth flag indicates that the display of the card or capsule at the display entry conflicts with the foreground application.

[0162] For example, the fourth flag is int REMOVED_FLAG_FOREGROUND_CONFLICT = 0x00000008. The fourth flag may also be referred to as the fourth identifier.

[0163] In a scenario where the display of the card or capsule at the display entry conflicts with the foreground application, if the application switches to the background application, the closed card or capsule at the display entry may be redisplayed.

[0164] The above removal reasons are only examples, and other reasons may also be included. For example, the card or capsule of one entry and the card or capsule of another entry are displayed in the same user interface. For example, if the card at the desktop entry displays service progress information, it may not need to be displayed again through the capsule at the global entry, or if the capsule at the global entry displays service progress information, it may not need the card at the desktop entry to display service progress information.

[0165] In the embodiments of the present application, the display process of the card or capsule at each display entry may be implemented through state switching, which is illustrated below. The display entries in the embodiments of the present application may include at least one of the following: desktop entry, negative first screen entry, screen-off entry, notification center entry, lock screen entry, global entry, and other display entries. The display forms of each display entry may include cards or capsules. In the embodiments of the present application, the cards or capsules are referred to as display elements. The card or capsule of a display entry can uniquely determine a display position. For example, the global capsule corresponds to the global entry and the display form capsule, as shown in Figure 2 in (B). The banner card corresponds to the global entry and the display form card, as shown in Figure 2 in (C). The notification center card corresponds to the notification center entry and the display form card, as shown in Figure 3 in (C). The desktop card corresponds to the desktop entry and the display form card, as shown in Figure 2 in (A). The negative first screen card corresponds to the negative first screen entry and the display form card, as shown in Figure 3 in (A). The screen-off card corresponds to the screen-off entry and the display form card, as shown in Figure 3 in (B). The lock screen card corresponds to the lock screen entry and the display form card, as shown in Figure 3 in (D).

[0166] For ease of description, a display form of a display entry is simply referred to as an entry display position, that is, an entry display position includes a display entry and a display element. A status is set for each entry display position. The following combines Figure 7 to illustrate the schematic diagram of the relationship between the status of each entry display position and the callback function of the display entry.

[0167] As Figure 7 shown, if the status of an entry display position is the creating state (CREATING), the creation function (onCreate function) of the corresponding display entry needs to be called back to create a card or capsule at the corresponding entry display position. After the callback ends, the status of this entry display position is set to the created state (CREATED).

[0168] If the status of an entry display position is the updating state (UPDATING), the update function (onUpdate) of the corresponding display entry needs to be called back to update the card or capsule at the corresponding entry display position. For example, when updating the data in the card or capsule, such as when updating to the next service node, the service progress information in the card or capsule needs to be updated. After the callback ends, the status of this entry display position is set to the updated state (UPDATED).

[0169] If the status of an entry display position is the removing state (REMOVING) or the stopping state (STOPPING), the removal function (onRemove) of the corresponding entry needs to be called back to remove the card or capsule at the corresponding entry display position. After the callback ends, the status of this entry display position is set to the removed state (REMOVED) or the stopped state (STOPPED).

[0170] As can be seen from the above description, by setting a status for the entry display position, the corresponding function of the display entry will be called, thereby realizing the creation, update, or removal of the cards or capsules at each entry display position, etc.

[0171] The reason for removing the card or capsule at an entry display position can refer to the removal reasons described in the foregoing embodiments. When the card or capsule at an entry display position is removed, a removal reason flag can be added. The removal reason flag can be at least one of the first flag, the second flag, the third flag, or the fourth flag. Exemplarily, as Figure 8 shown in (A) below, when the status of an entry display position changes from other statuses (such as the created state or the updated state) to the removing state (REMOVING) or the removed state (REMOVED), a removal reason flag is added for this entry display position, and the removal reason flag can be at least one.

[0172] When a card or capsule with its entry display position removed needs to be restored, determine the removal reason flag associated with the restoration reason. Here, the removal reason associated with the restoration reason can be understood as the removal reason has been eliminated due to this restoration reason. For example, the restoration reason associated with the removal reason of manual deletion by the user is that the service progress has been updated to the next service node. Another example, the restoration reason associated with the removal reason that the user manually closed the entry control is that the user manually opened the entry control. Another example, the restoration reason associated with the removal reason that the display of the card or capsule at the entry display position is removed due to the decreased priority of the service node is that the priority of the transferred service node has increased. Another example, the restoration reason associated with the removal reason that the display of the card or capsule at the entry display position conflicts with the foreground application is that the application has switched to running in the background.

[0173] As Figure 8 shown in (B) below, when a card or capsule with its entry display position removed is restored, determine the removal reason flag associated with the restoration reason and delete the removal reason flag. After deleting the removal reason flag, determine whether there are other removal reason flags. If there are no other removal reason flags, a card or capsule can be re-created at the entry display position. If there are still other removal reason flags, the removed state is continued to be maintained.

[0174] The following uses specific scenarios as examples to illustrate the switching schematic diagram between various states of the entry display position. An entry display position is uniquely determined by a display entry and a display element (the display element can be a capsule or a card, for example).

[0175] As Figure 9 shown, it is the state switching involved in the service node update process. In Figure 9 (A) below, when the entry display position is in the updated state or the created state, if the service progress of the application service is transferred to the next service node, the electronic device will set the state of this entry display position to the update state, thereby calling back the update function to update the service progress information displayed in the entry display position. After the call ends, the electronic device sets the state of this entry display position to the updated state. For example, in a taxi-hailing application scenario, when the service node of calling a network car is switched to the service node where the driver has accepted the order, the service progress information displayed on the card or capsule at the entry display position will be updated once.

[0176] In Figure 9In (B), it is the user manual deletion and recovery scenario. The status of the entry display position is the removed status. The reasons for removal corresponding to this entry display position include the user manual deletion flag, for example, the first identifier. When the electronic device determines that the service progress is updated to the next service node, if the reason for removal of the entry display position only has the user manual deletion flag, the electronic device updates the status of the entry display position to the created status, thereby calling back the creation function to create a card or capsule at the entry display position to display the service progress information. If the reason for removal of the entry display position still has other flags after deleting the manual deletion flag, the removed status is continued to be maintained.

[0177] In Figure 9 In (C), it is the scenario of adding a new entry when the priority is increased for the first time, that is, the scenario of switching to a high-priority service node for the first time and adding a display entry for the first time. When the electronic device determines that the service progress is updated to a high-priority service node, for example, a service node with a relatively high urgency. Taking the taxi application service as an example, the priority for the driver to reach this service node is relatively high. The electronic device will add a display entry to display the service progress information. For example, it will add a banner card of the global entry to display the service progress information. The electronic device sets the status of the newly added entry display position to the created status, thereby calling back the creation function to create a card or capsule at the newly added entry display position to display the service progress information. After the call ends, the electronic device sets the status of this entry display position to the created status.

[0178] Optionally, in Figure 9 In (C), when the entry display position is in the created status, if the electronic device determines that the display of the entry display position conflicts with the display of the capsule or card, for example, the user interface already has a card or capsule to display the service progress information, the status of the entry display position is updated to the removed status, and a display conflict flag is added. This display conflict flag indicates that the reason for removal includes display conflict.

[0179] In Figure 9 In (D), it is the scenario of reducing the display entry when the priority is decreased, that is, the application service switches from a high-priority service node to a low-priority service node. When the electronic device determines that the service progress is updated to a service node with a relatively low priority, for example, a service node with a relatively low urgency. Taking the taxi application service as an example, the priority of the service node during the process of the driver driving to the passenger's location after receiving the order is relatively low. The electronic device will reduce the display entry to display the service progress information. For example, it will remove the banner card of the global entry. Exemplarily, such as Figure 9As shown in (D) therein, the status of the entry display position of the card or capsule to be removed is the created status or the updated status. The electronic device sets the status of the entry display position to the removed status, thereby calling back the removal function to remove the card or capsule at the entry display position, and adding a removal reason flag with a lower priority flag, such as a third identifier, to the entry display position. After the call ends, the electronic device sets the status of the entry display position to the removed status.

[0180] Optionally, in Figure 9 as shown in (D) therein, when the service progress is updated to a low-priority service node, if the electronic device determines that the status of the entry display position of the card or capsule to be removed is the removed status, the lower priority flag, such as a third identifier, can be superimposed, so that there can be multiple removal reason flags for the entry display position.

[0181] In Figure 9 (E) therein is a display entry scenario for increasing the priority again, that is, the application service switches from a low-priority service node to a high-priority service node. At this time, the status of the entry display position is the removed status. In other words, the reason for the removed status of the entry display position in this scenario includes a lower priority. When the electronic device determines that the service progress is updated to a service node with a relatively high priority, for example, a service node with a relatively high urgency, taking the taxi application service as an example, the priority of the driver arriving at this service node is relatively high. The electronic device will increase the display of the entry to show the service progress information. For example, it will increase the display of a banner card for the global entry to show the service progress information. The electronic device determines whether the removal reason is only the lower priority flag. If it is only the lower priority flag, the electronic device deletes the lower priority flag and sets the status of the newly added entry display position to the created status, thereby calling back the creation function to create a card or capsule at the entry display position to show the service progress information. After the call ends, the electronic device sets the status of the entry display position to the created status. If there are other removal reason flags after the electronic device deletes the lower priority flag, the entry display position continues to maintain the removed status.

[0182] In the above description, the lower or higher priority can be configured by the application service. For example, it will be pre-configured which service nodes are high-priority service nodes and which service nodes are low-priority nodes. The process of switching from a high-priority service node to a low-priority service node requires reducing the display of the entry, and the process of switching from a low-priority service node to a high-priority service node requires increasing the display of the entry.

[0183] As Figure 10 shown, it is a schematic diagram of the status switch for the user manual deletion scenario. The user manual deletion scenario is as Figure 6As shown. When the entrance display position is in the created state or the updated state, if the electronic device determines that the user deletes the card or capsule of the entrance display position, a user deletion flag is added to the entrance display position, and the state of the entrance display position is updated to the removed state, thereby calling back the removal function to remove the card or capsule in the entrance display position. After the callback ends, the electronic device updates the state of the entrance display position to the removed state. If Figure 10 the state of the entrance display position in Figure 10 is the removed state, a user deletion flag can be added to the entrance display position.

[0184] Figure 11 As shown, it is a schematic diagram of state switching in the scenario of closing or opening the entrance control. For example, the user can Figure 4 open or close the switch of an entrance display position through the entrance control shown. As Figure 11 shown in (A) of Figure 11 , it is a schematic diagram of state switching in the scenario of opening the switch of the entrance control. When the entrance display position is in the removed state, the removal reason may include, for example, that the switch of the entrance control of the entrance display position is closed. When the electronic device determines that the switch of the entrance control associated with the entrance display position is opened, the switch-off flag is removed. If there is only the switch-off flag, the state of the entrance display position is updated to the created state, thereby calling back the creation function to create a capsule or a card at the entrance display position and display the service progress information. When the state of the entrance display position is the created state, if there is a conflict with the display of the capsule or the card, a display conflict flag is added and the state is switched to the removed state.

[0185] If there are other removal reason flags after removing the switch-off flag, the entrance display position continues to remain in the removed state.

[0186] As Figure 11 shown in (B) of Figure 11 , it is a schematic diagram of state switching in the scenario of closing the entrance control. When the entrance display position is in the created state or the updated state and the electronic device determines that the switch of the entrance display position is closed, the electronic device adds an entrance control closed flag to the entrance display position and updates the state of the entrance display position to the removed state, thereby calling the removal function to remove the card or capsule of the entrance display position. After the call ends, the electronic device updates the state of the entrance display position to the removed state.

[0187] If the state of the entrance display position is the removed state and the electronic device determines that the switch of the entrance control of the entrance display position is closed, the electronic device adds an entrance control closed flag, that is, the removal reason is superimposed.

[0188] Figure 12As shown, it is a schematic diagram of state transition in the scenarios of adding new conflicts and the disappearance of conflicts. The conflicts may include, but are not limited to: display conflicts with other entry display positions (for example, the service progress information is the same as that of other entry display positions in the same user interface), and conflicts with foreground applications (for example, the user opens the application corresponding to the service progress information).

[0189] In Figure 12 as shown in (A), when the entry display position is in the created state or the updated state, if the electronic device determines to add a conflict, a conflict flag is added to the entry display position, and the state of the entry display position is switched to the removed state, so as to call the removal function to remove the card or capsule of the entry display position, and the state of the entry display position is updated to the removed state.

[0190] If the state of the entry display position is the removed state, if the electronic device determines to add a conflict, a conflict flag will also be added, so as to stack the removal reasons.

[0191] In Figure 12 as shown in (B), the entry display position is in the removed state, and the conflict in the removal reason disappears. For example, if the application is running in the background, the corresponding conflict flag can be deleted. If the entry display position only has this conflict flag, the state of the entry display position is switched to the created state, so as to call the creation function to create a card or capsule at the entry display position to display the service progress information. The state of the entry display position is switched to the created state.

[0192] If there are still other removal reason flags after the conflict flag of the entry display position is deleted, the removed state will continue to be maintained.

[0193] In the above Figures 9 - 12 , the unregistered entry can be understood as that the display entry is not yet ready, and the state will still be converted to facilitate the subsequent display or removal after the display entry is ready.

[0194] Next, in combination with Figures 13 to 15 , the flowchart of the display control method provided by the embodiment of the present application will be introduced. In Figures 13 to 15Among them, taking the display framework including a service module, a control module, and a data module as an example, in some embodiments, the modules can also be combined or split, or the display framework includes more modules, which is not limited in this application. Among them, the display entry can be understood as each entry that can be globally reached, such as a global entry, a notification entry, a desktop entry, etc., which is not limited in this application. The business side can refer to application services, such as intelligent services, and the business side can also refer to each display entry, such as a desktop entry, etc. It can be understood that the following business side, system side, display framework, and display entry are different components within the electronic device. The combination of the display entry and the display element in the following description can be replaced by the entry display position, and the display element can be, for example, a card or a capsule, that is, a display entry and a display element can uniquely determine the display position.

[0195] Please refer to Figure 13 , the display control method may include but is not limited to the following steps, and in some embodiments, it may also only include some of the following steps:

[0196] 101. The business side sends an operation instruction.

[0197] As an example, the operation instruction can be a deletion instruction for the card or capsule of the display entry (the card or capsule of the display entry can be called the display element of the display entry), and the deletion instruction can be called the first information. The business side can refer to the display entry. For example, when the display element of the display entry displays service progress information, when it detects that the user deletes the display element of the display entry, the display entry sends a deletion instruction to the display framework, and the deletion instruction instructs to delete the display element of the display entry. The display and operation of the user interface can refer to Figure 6 the description, which will not be elaborated here.

[0198] As another example, the operation instruction can be a switch change instruction for the entry control. The business side can be an intelligent service. The switch change instruction is used to indicate the closing or opening of the entry control. An entry control can be associated with one or more display elements of the display entry, that is, an entry control can be used to control the removal or restoration of one or more display elements of the display entry.

[0199] Exemplarily, an electronic device displays a service management user interface, which includes one or more entry controls. When a closing operation of the user on the first entry control is detected, in response to the closing operation of the first entry control, the intelligent service can send a first switch change instruction to the display framework. The first switch change instruction can be referred to as the first information, and this first switch change instruction indicates the closing of the first entry control. The first entry control is associated with display elements of one or more display entries. When an opening operation of the user on the second entry control is detected, in response to the opening operation of the second entry control, the intelligent service can send a second switch change instruction to the indication framework. The second switch change instruction can be referred to as the second information, and this second switch change instruction indicates the opening of the second entry control. The second entry control is associated with display elements of one or more display entries. For the relevant description of the entry control, please refer to Figure 4 the relevant description, which will not be elaborated here.

[0200] 102. The service module obtains the current first state of the display elements of the display entry.

[0201] When receiving an operation instruction, the service module obtains the current first state of the display elements of the associated display entry. The first state can be one of the following: created state, updated state, or removed state.

[0202] If the operation instruction is a deletion instruction, the display elements of the associated display entry can refer to the display elements of the display entry deleted by the user indicated by the deletion instruction.

[0203] If the operation instruction is a switch change instruction, the display elements of the associated display entry can be the display elements of one or more display entries associated with the entry control indicated in the switch change instruction.

[0204] The service module obtains the current first state of the display elements of the associated display entry from the data module. The data module stores the relevant state data and removal reason identifiers of the display elements of each display entry.

[0205] 103. The service module sends the operation instruction and the first state.

[0206] The service module sends the received operation instruction and the current first state of the display elements of the associated display entry to the control module.

[0207] 104. The control module adds or deletes a removal reason identifier for the display elements of the display entry according to the operation instruction.

[0208] If the operation instruction is a deletion instruction, the control module adds a user manual deletion flag to the display elements of the associated display entry in the data module.

[0209] If the first state of the display element of the display entry is the removed state, it can be understood that a removal reason identifier is superimposed on the display element of the display entry, and the removal reason identifier of the display element of the display entry includes at least two. And keep the state of the display element of the display entry as the removed state.

[0210] If the first state of the display element of the display entry is the created state or the updated state, steps 105 - 107 can be executed to remove the display element of the display entry.

[0211] If the operation instruction is a switch change instruction, and the switch change instruction instructs to close the first entry control, for example, the first switch change instruction, the control module adds an entry control closed flag to the display element of the display entry associated with the first entry control.

[0212] If the first state of the display element of the display entry is the removed state, it can be understood that a removal reason identifier is superimposed on the display element of the display entry, and the removal reason identifier of the display element of the display entry includes at least two. And keep the state of the display element of the display entry as the removed state.

[0213] If the first state of the display element of the display entry is the created state or the updated state, steps 105 - 107 can be executed to remove the display element of the display entry.

[0214] If the operation instruction is a switch change instruction, and the switch change instruction instructs to open the second entry control, for example, the second switch change instruction, the control module deletes the entry control closed flag of the display element of the display entry associated with the second entry control. In this scenario, the first state is the removed state.

[0215] If there are still other removal reason identifiers remaining in the removal reason identifier of the display element of the display entry associated with the second entry control, keep the state of the display element of the display entry as the removed state.

[0216] If there are no other removal reason identifiers in the removal reason identifier of the display element of the display entry associated with the second entry control, steps 105 - 107 can be executed to create the display element of the display entry.

[0217] 105. The control module updates the state of the display element of the display entry to the second state according to the operation instruction and the first state.

[0218] 106. The control module calls back the function corresponding to the second state to remove or restore the display element of the display entry.

[0219] 107. The control module updates the state of the display element of the display entry to the third state.

[0220] If the operation instruction is a deletion instruction and the first state is the created state or the updated state, the state of the display element of the display entry can be updated to the removed state (i.e., the second state), and the removal function corresponding to the entry can be called to remove the display element of the display entry, and the state of the display element of the display entry is updated to the removed state (i.e., the third state).

[0221] If the operation instruction is a switch change instruction and the switch change instruction indicates to close the first entry control, such as the first switch change instruction, and the first state is the created state or the updated state, the state of the display element of the display entry can be updated to the removed state (i.e., the second state), and the removal function corresponding to the entry can be called to remove the display element of the display entry, and the state of the display element of the display entry is updated to the removed state (i.e., the third state).

[0222] If the operation instruction is a switch change instruction and the switch change instruction indicates to open the second entry control, such as the second switch change instruction, and the first state is the removed state and there is no other removal reason identifier after deleting the close flag of the entry control in the removal reason identifier, the state of, for example, the second switch change instruction can be updated to the created state (i.e., the second state), and the creation function corresponding to the entry can be called to create the display element of the display entry, and the state of the display element of the display entry is updated to the created state (i.e., the third state).

[0223] After the user manually deletes the display element of the display entry, the display element of the display entry can be restored when the application service is updated to the next service node. Exemplarily, when the control module determines that the application service is updated to the next service node, the user manual deletion flag of the display element of the display entry is deleted, and if there is no other removal reason identifier for the display element of the display entry, the display element of the display entry can be restored.

[0224] Embodiments of the present application can, through user operations, achieve flexible removal or creation of the display elements of the display entry.

[0225] Please refer to Figure 14 , the display control method may include but is not limited to the following steps. In some embodiments, it may also only include some of the following steps:

[0226] 201, The business side sends priority change information.

[0227] The business side may refer to an application service, such as a ride-hailing application. The priority may refer to the priority of a service node, and for details, reference may be made to the description of the foregoing embodiments. When switching from a low-priority service node to a high-priority service node, or from a high-priority service node to a low-priority service node, the business side will send priority change information to indicate the change in the priority of the service node.

[0228] As an example, the priority change information may be first priority change information, which may also be referred to as first information. The first priority change information indicates that the application service switches from a high-priority service node to a low-priority service node.

[0229] As another example, the priority change information may be second priority change information, which may also be referred to as second information. The second priority change information indicates that the application service changes from a low-priority service node to a high-priority service node.

[0230] 202, the service module obtains the current first state of the display element of the display entry.

[0231] After receiving the priority change information, the service module determines the display elements of one or more display entries associated with the changed priority, and the display elements of one or more display entries associated with the priority before the change. For example, if switching from a low-priority service node to a high-priority service node, the display elements of the display entry need to be increased. If switching from a high-priority service node to a low-priority service node, the display elements of the display entry need to be decreased. That is, the number of display elements of the display entry associated with the high-priority service node is greater than the number of display elements of the display entry associated with the low-priority service node. The display elements of the display entry that need to be increased or decreased are the display elements of the display entry among the display elements of one or more display entries associated with the high-priority service node that are not the display elements of one or more display entries associated with the low-priority service node.

[0232] For the scenario where the display entry needs to be increased, the service module needs to obtain the current first state of the display element of the display entry that needs to be increased from the data module. For the display element of the display entry that is increased for the first time, the service module may set the state of the display element of the display entry to the created state, so as to call the creation function to create the display element of the display entry. For the first state of the display element of the display entry that is not increased for the first time, it is the removed state, and the priority reduction flag is deleted for it. For details, reference may be made to steps 203-step 207.

[0233] For the scenario where the display entry needs to be decreased, the service module needs to obtain the current first state of the display element of the display entry that needs to be decreased from the data module. The first state may be the created state, the updated state, or the removed state.

[0234] 203. The service module sends priority change information and the first status.

[0235] 204. The control module adds or deletes a removal reason identifier for the display element of the display entry according to the priority change information.

[0236] If it is a conversion from a low-priority service node to a high-priority service node, delete the priority decrease flag for the display element of the display entry that needs to be added. If there is no other removal reason flag after the priority decrease flag of the display element of the display entry is deleted, the descriptions in steps 205 - 207 can be executed to create the display element of the display entry.

[0237] If there are still other removal reason flags after the priority decrease flag of the display element of the display entry is deleted, keep the display element of the display entry in the removed state.

[0238] If it is a conversion from a high-priority service node to a low-priority service node, add a priority decrease flag for the display element of the display entry that needs to be reduced. If the first status is the created status or the updated status, execute the descriptions in steps 205 - 207 to create the display element of the display entry. If the first status is the removed status, it can be understood that the removal reason identifier is superimposed on the display element of the display entry.

[0239] 205. The control module updates the status of the display element of the display entry to the second status according to the priority change information and the first status.

[0240] 206. The control module calls the function corresponding to the second status to remove or restore the display element of the display entry.

[0241] 207. The control module updates the removed or restored status of the display element of the display entry to the third status.

[0242] If it is a conversion from a low-priority service node to a high-priority service node, and there is no other removal reason identifier after the priority decrease flag of the display element of the display entry that needs to be added is deleted, the status of the display element of the display entry that needs to be added can be updated to the created status (i.e., the second status), and the creation function of the corresponding entry can be called to create the display element of the display entry, and the status of the display element of the display entry is updated to the created status (i.e., the third status).

[0243] If it is a conversion from a high-priority service node to a low-priority service node, update the status of the display elements of the display entry to be reduced to the removed status (i.e., the second status), and call the removal function of the corresponding entry to remove the display elements of the display entry, and update the status of the display elements of the display entry to the removed status (i.e., the third status).

[0244] The above service nodes can be converted from low priority to high priority, or from high priority to low priority in a continuous loop. Each conversion process can refer to Figure 14 the description of

[0245] Please refer to Figure 15 , the display control method may include but is not limited to the following steps. In some embodiments, it may also only include some of the following steps:

[0246] 301, the system side sends foreground application switching information.

[0247] The system side may refer to the system of the electronic device. The system can send foreground application switching information to the display framework. For example, when the application running in the foreground changes, it can send foreground application switching information to the display framework.

[0248] As an example, the foreground application switching information may be the first switching information, and the first switching information may also be referred to as the first information. The first switching information indicates that the foreground application is switched to the first application, and the first application is the application corresponding to the service progress information to be displayed by the display elements of the display entry.

[0249] As another example, the foreground application switching information may be the second switching information, and the second switching information may also be referred to as the second information. The second switching information indicates that the first application is switched to run in the background.

[0250] 302, the service module obtains the current first status of the display elements of the display entry.

[0251] The first status may be the created status, the updated status, or the removed status.

[0252] 303, the service module sends the foreground application switching information and the first status.

[0253] 304, the control module adds or deletes a removal reason identifier for the display elements of the display entry according to the foreground application switching information.

[0254] If the foreground application is switched from another application to the first application, it indicates that the display elements of the display entry do not need to display the service progress information related to the first application. The control module adds a foreground application conflict flag to the display elements of the display entry. If the first state is the created state or the updated state, the descriptions in steps 305 to 307 are executed to remove the display elements of the display entry. If the first state is the removed state, it can be understood that the display elements of the display entry are superimposed with the removal reason identifier.

[0255] If the foreground application is switched from the first application to another application, that is, the first application is switched to run in the background, it indicates that the display elements of the display entry need to be restored. The control module deletes the foreground application conflict flag from the display elements of the display entry. If there is no other removal reason flag after the foreground application conflict flag of the display elements of the display entry is deleted, the descriptions in steps 305 to 307 can be executed to create the display elements of the display entry.

[0256] If there is still other removal reason flag after the foreground application conflict flag of the display elements of the display entry is deleted, the display elements of the display entry are kept in the removed state.

[0257] 305. The control module updates the state of the display elements of the display entry to the second state according to the foreground application switching information and the first state.

[0258] 306. The control module calls the function corresponding to the second state to remove or restore the display elements of the display entry.

[0259] 307. The control module updates the state of the display elements of the display entry to the third state.

[0260] If the foreground application is switched from another application to the first application, the state of the display elements of the display entry is updated to the removed state (i.e., the second state), and the removal function of the corresponding entry is called to remove the display elements of the display entry, and the state of the display elements of the display entry is updated to the removed state (i.e., the third state).

[0261] If the foreground application is switched from the first application to another application and there is no other removal reason identifier after deleting the foreground conflict flag of the display elements of the display entry, the state of the display elements of the display entry can be updated to the created state (i.e., the second state), and the creation function of the corresponding entry is called to create the display elements of the display entry, and the state of the display elements of the display entry is updated to the created state (i.e., the third state).

[0262] The above describes that when the service progress information displayed by the display elements of the display entry conflicts or does not conflict with the foreground application, the creation or removal of the display elements of the display entry can be flexibly controlled.

[0263] Please refer to Figure 16 , the display control method may include but is not limited to the following steps. In some embodiments, it may also only include some of the following steps:

[0264] 401. The first information is detected.

[0265] The first information in the embodiments of the present application is information about a display element that can be used to determine a display entry to be removed.

[0266] Exemplarily, the first information may be a deletion instruction indicating that the user manually deletes the display element of the display entry. This deletion instruction may be triggered when the display entry detects a user deletion operation.

[0267] Exemplarily, the first information may be a switch change instruction for indicating the closing of an entry control. This entry control is associated with the display elements of one or more display entries, that is, the removal or restoration of the display elements of the one or more display entries can be controlled by the opening or closing of this display entry control.

[0268] Exemplarily, the first information may be priority change information indicating that the application service switches from a high-priority service node to a low-priority service node. Through this priority change information, it can be determined which display elements of the display entries need to be removed.

[0269] Exemplarily, the first information may be an indication that the foreground application switches to the application to which the service progress information to be displayed belongs.

[0270] It can be understood that the first information may also include other information for determining the information about the display elements of the display entry to be deleted. The above are only examples and do not constitute a limitation to the present application.

[0271] 402. Determine a first removal reason identifier for removing the display elements of the display entry according to the first information.

[0272] Furthermore, the first information can also be used to determine the first removal reason identifier. For example, if the first information is a deletion instruction for the user to manually delete, then the first removal reason identifier is a user manual deletion identifier. The specific removal reason identifier when the first information is other information can be specifically referred to the description of the foregoing embodiments and will not be elaborated here.

[0273] 403. Add the first removal reason identifier to the display elements of the display entry.

[0274] After determining the display elements of the display entry, the determined first removal reason identifier can be added to the display elements of the display entry. After adding the first removal reason identifier, the display elements of the display entry can correspond to at least one removal reason identifier. That is, the removal reason identifiers can be superimposed.

[0275] An embodiment of the present application further provides an electronic device, which includes: one or more processors and a memory; wherein, the memory is coupled to the one or more processors, and the memory is used to store computer program code, and the computer program code includes computer instructions, and the one or more processors call the computer instructions to cause the electronic device to execute the method shown in the foregoing embodiment.

[0276] As used in the foregoing embodiments, depending on the context, the term "when..." can be interpreted to mean "if...", or "after...", or "in response to determining...", or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if detecting (the stated condition or event)" can be interpreted to mean "if determining...", or "in response to determining...", or "when detecting (the stated condition or event)", or "in response to detecting (the stated condition or event)".

[0277] In the foregoing embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid-state drive), etc.

[0278] Those of ordinary skill in the art can understand all or part of the processes in the methods of the foregoing embodiments. These processes can be completed by relevant hardware instructed by a computer program. The program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the foregoing method embodiments. The foregoing storage medium includes: various media that can store program code, such as ROM or random access memory RAM, magnetic disk, or optical disc.

Claims

1. A display control method, characterized in that, Including: Detecting a first piece of information, where the first piece of information is used to determine a display element of a display entry to be removed; Determining a first removal reason identifier for removing the display element of the display entry according to the first piece of information; Adding the first removal reason identifier to the display element of the display entry, and after adding the first removal reason identifier, the display element of the display entry corresponds to at least one removal reason identifier, and the at least one removal reason identifier is used to restore the display element of the display entry.

2. The method according to claim 1, wherein Before the first piece of information is detected, the display element of the display entry is in a created state or an updated state. After adding the first removal reason identifier, the display element of the display entry corresponds to one removal reason identifier, and the one removal reason identifier is the first removal reason identifier; the method further includes: removing the display element of the display entry; Before the first piece of information is detected, the display element of the display entry is in a removed state. After adding the first removal reason identifier, the display element of the display entry corresponds to at least two removal reason identifiers, and the at least two removal reason identifiers include the first removal reason identifier.

3. The method according to claim 1 or 2, characterized in that, The first piece of information is a deletion instruction for instructing a user to manually delete a display element of a display entry; The display element of the display entry to be removed is the display element of the display entry manually deleted by the user; The first removal reason identifier is a first identifier, and the first identifier indicates that the removal reason is user manual deletion.

4. The method according to claim 1 or 2, characterized in that, The first piece of information is a first switch change instruction for instructing a first entry control to close, and the first entry control is associated with display elements of one or more display entries; The display element of the display entry to be removed is the display element of the one or more display entries associated with the first entry control; The first removal reason identifier is a second identifier, and the second identifier indicates that the removal reason is entry control closure.

5. The method according to claim 1 or 2, characterized in that, The first piece of information is a first priority change information for instructing an application service to switch from a high-priority service node to a low-priority service node; The display element of the display entry to be removed is the display element of the display entry other than the display elements of the one or more display entries associated with the low-priority service node among the display elements of the one or more display entries associated with the high-priority service node; The first removal reason identifier is a third identifier, and the third identifier indicates that the removal reason is a decrease in the priority of the service node.

6. The method according to claim 1 or 2, characterized in that, The first piece of information is a first switching information for instructing a foreground application to switch to a first application, where the first application is the application to which the service progress information to be displayed by the display element of the display entry to be removed belongs; the method further includes: The display element of the display entry to be removed is the display element of the display entry on the same user interface as the application page of the foreground application; The first removal reason identifier is a fourth identifier, and the fourth identifier indicates that the removal reason is a conflict with the foreground application.

7. The method according to any one of claims 1 to 6, characterized in that The method further includes: The second information is detected, and the second information is used to determine the display elements of the display entry that needs to be restored; Determine a second removal reason identifier for restoring the display elements of the display entry according to the second information; If the display elements of the display entry correspond to one removal reason identifier, and the one removal reason identifier is the second removal reason identifier, then restore the display elements of the display entry; If the display elements of the display entry correspond to at least two removal reason identifiers, and the at least two removal reason identifiers include the second removal reason identifier, then delete the second removal reason identifier.

8. The method according to claim 7, wherein The second information is status update information used to indicate the update of the service node of the application service; The display elements of the display entry that needs to be restored are the display elements of the display entry manually deleted by the user; The second removal reason identifier is a first identifier, and the first identifier indicates that the removal reason is manual deletion by the user.

9. The method according to claim 7, wherein The second information is a second switch change instruction used to indicate the opening of a second entry control, and the second entry control is associated with the display elements of one or more display entries; The display elements of the display entry that needs to be restored are the display elements of the one or more display entries associated with the second entry control; The second removal reason identifier is a second identifier, and the second identifier indicates that the removal reason is the closing of the entry control.

10. The method according to claim 7, characterized in that The second information is second priority change information used to indicate that the application service switches from a low-priority service node to a high-priority service node; The display elements of the display entry that needs to be restored are the display elements of the display entry other than the display elements of the one or more display entries associated with the low-priority service node among the display elements of the one or more display entries associated with the high-priority service node; The second removal reason identifier is a third identifier, and the third identifier indicates that the removal reason is the reduction of the priority of the service node.

11. The method according to claim 7, wherein The second information is second switching information used to indicate that a first application switches to running in the background, and the first application is the application to which the service progress information to be displayed by the display elements of the display entry that needs to be restored belongs; The display elements of the display entry that needs to be restored are the display elements of the display entry on the same user interface as the application page of the foreground application; The second removal reason identifier is a fourth identifier, and the fourth identifier indicates that the removal reason is conflict with the foreground application.

12. An electronic device, characterized in that, The electronic device includes: one or more processors, a memory, and a display screen; The memory is coupled to the one or more processors, and the memory is used to store computer program code. The computer program code includes computer instructions, and the one or more processors call the computer instructions to cause the electronic device to execute the method according to any one of claims 1-11.

13. A chip system, characterized in that, The chip system is applied to an electronic device. The chip system includes one or more processors, and the processors are used to call computer instructions to cause the electronic device to execute the method according to any one of claims 1-11.

14. A computer-readable storage medium, comprising instructions, characterized in that, When the instruction runs on the electronic device, the electronic device is caused to execute the method according to any one of claims 1 to 11.