WO2023280141A1

WO2023280141A1 - Method for refreshing user interface, and electronic device

Info

Publication number: WO2023280141A1
Application number: PCT/CN2022/103812
Authority: WO
Inventors: 贾德祥; 鲁波
Original assignee: 华为技术有限公司
Priority date: 2021-07-09
Filing date: 2022-07-05
Publication date: 2023-01-12
Also published as: CN115599475A

Abstract

Provided in the present application are a method for refreshing a user interface, and an electronic device. The method can be applied to an electronic device. The method comprises: an electronic device detecting a first user interface change request of a first application, wherein the first application is run in the background of the electronic device; the electronic device caching the first user interface change request; and when the electronic device has detected that the first application is switched to be run in the foreground, the electronic device updating a user interface change, which corresponds to the first user interface change request, to a user interface of the first application. By means of the technical solution, a change request corresponding to a user interface change occurring in an application, which is run in the background, can be cached, and when the background application is viewable, the user interface change is applied to a user interface, such that the problem of conflict caused by concurrent access of a plurality of applications can be avoided.

Description

Method and electronic device for refreshing user interface

This application claims the priority of the Chinese patent application with the application number 202110775502.1 and the application name "Method and Electronic Device for Refreshing User Interface" submitted to the China Patent Office on July 09, 2021, the entire contents of which are incorporated by reference in this application middle.

technical field

The present application relates to the field of electronic technology, and more specifically, to a method for refreshing a user interface and an electronic device.

Background technique

In some Internet of Things (IOT) devices with screens, due to the design limitations of the central processing unit (CPU), the chip does not support the memory management unit (MMU) memory mapping, and the global only Able to run one process. If you want to run multiple applications at the same time, you usually run multiple applications concurrently through multi-threading or multi-tasking. In this case, the threads of the multiple applications may simultaneously access the same In the case of shared resources, conflicts arise.

Contents of the invention

The present application provides a method and an electronic device for refreshing a user interface. The technical solution can cache a user interface change request generated by an application running in the background, and apply the user interface change to the user interface when the background application is visible, thereby enabling Avoid conflicts caused by concurrent access by multiple applications.

In a first aspect, a method for refreshing a user interface is provided, the method is applied to an electronic device, and the method includes: the electronic device detects a first user interface UI change request of a first application, and the first application runs on the The background of the electronic device; the electronic device caches the first UI change request; when the electronic device detects that the first application is switched to the foreground, it updates the UI change corresponding to the first UI change request to the UI of the first application.

Based on the embodiment of the present application, when the UI of the first application running in the background is changed, the electronic device can detect the UI change request and cache the UI change request, and when the first application switches to the foreground, the The UI changes are applied to the UI of the first application. The technical solution can avoid conflict problems caused by concurrent access of multiple applications when the electronic device runs multiple applications at the same time.

With reference to the first aspect, in some implementation manners of the first aspect, the first UI change request is generated according to the first information of the first UI change, and the electronic device caches the first UI change request, including: The electronic device adds the first UI change request into a cached data structure.

The first information may be the changed UI component, the property of the UI component, and the value of the changed property.

In the embodiment of the present application, the cached data structure may include a linked list, a queue, an array, etc., which is not limited in the embodiment of the present application.

Based on the embodiment of the present application, the UI change request is cached in the cached data structure, so that the UI change of the background application will not be executed immediately.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the electronic device detecting a second UI change request of the first application, wherein the second UI change request is based on The second information of the second UI change is generated; when the first UI component corresponding to the first UI change request is different from the second UI component corresponding to the second UI change request, or the first UI component is different from the first UI component When the second UI component is the same but the attribute of the first UI component is different from the attribute of the second UI component, the electronic device adds the second UI change request to the cached data structure; when the When the electronic device detects that the first application is switched to the foreground, it updates the UI change corresponding to the second UI change request to the UI of the first application.

The second information may include the changed second UI component, the property of the component, and the value of the changed property, etc. The property of the UI component may include but not limited to the characteristics or styles of the component such as length, width, and color.

In the embodiment of the present application, the UI component may include a directly drawn local (native view) UI component, or may include a document object model (document object model, DOM) component structure in the development of the global wide area network (web). The application examples do not limit this.

Based on the embodiment of this application, when the UI component corresponding to the second UI change request is different from the UI component corresponding to the first UI change request or the attributes of the components are different, the first UI component can be added to the cached data structure, and the application When switching from the background to the foreground, the second UI change is updated to the UI of the application. The technical solution can cache different UI change requests in the data structure when multiple UI changes occur in the application, so that the multiple UI changes are executed sequentially when the application is switched to the foreground.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the electronic device detecting a third UI change request of the first application, wherein the third UI change request is based on The third information of the third UI change is generated; when the third UI component corresponding to the third UI change request is the same as the first UI component corresponding to the first UI change request and the attribute of the third UI component is the same as When the attributes of the first UI component are the same, the electronic device updates the value of the attribute of the first UI component in the cached data structure according to the value of the attribute of the third UI component.

The third information may include the changed third UI component, the attribute of the component, and the value of the changed attribute. The attributes of the UI component may include characteristics or styles of the component such as length, width, and color.

Exemplarily, the attribute of the first UI component corresponding to the first UI change request is color, and the value of the attribute is a specific color, such as red, and the third UI component corresponding to the third UI change request is the same as the first UI component The same, and the attribute of the third UI component is also the color. If the value of the attribute of the third UI component is yellow, the electronic device can update the value (yellow) of the attribute of the third UI component to correspond to the first UI change request. The value of the property of the first UI component, that is, at this time, the cached value of the property of the first UI component is updated to yellow, so that there is no need to cache the third UI change request.

Based on the embodiment of the present application, when the UI component corresponding to the third UI change request is the same as the UI component corresponding to the first UI change request and has the same attributes of the components, update the third UI component with the value of the attribute of the UI component corresponding to the third UI change request. A UI change request corresponds to the value of a property of the UI component. Therefore, it is possible to avoid adding the third UI change request into the data structure of the cache, avoid adding new cache nodes, and thereby reduce memory consumption of the electronic device.

In some other embodiments, the electronic device may also cache the third UI change request.

With reference to the first aspect, in some implementation manners of the first aspect, updating the UI change corresponding to the first UI change request to the UI of the first application includes: calling a system interface by the electronic device Updating the UI change corresponding to the first UI change request to the UI component of the first application.

With reference to the first aspect, in some implementation manners of the first aspect, before the electronic device caches the first UI change request, the method further includes: the electronic device determines that the first UI change request needs to be cached ask.

Based on the embodiment of the present application, before the electronic device caches the first UI change request, it may be pre-determined whether the first UI change request needs to be cached, so as to avoid caching all UI change requests and save power consumption of the electronic device.

In some other embodiments, the electronic device may determine whether the first UI change request needs to be cached, and some UI change requests may not be cached, and may be directly updated to the UI of the application.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: when the electronic device determines that the first UI change request does not need to be cached, directly corresponding the first UI change request The UI change of is updated to the UI of the first application.

With reference to the first aspect, in some implementation manners of the first aspect, the electronic device caching the first UI change request includes: the electronic device sending the first UI change request to a UI service thread; The UI service thread caches the first UI change request.

In the embodiment of this application, the UI service thread can be used to manage UI changes of all applications. When there are multiple UI change requests, the UI service thread can cache the multiple UI changes in chronological order and execute them sequentially. .

In some other embodiments, the UI service thread may directly update the UI change corresponding to the UI change request to the UI of the application, which is not limited in this embodiment of the present application.

With reference to the first aspect, in some implementation manners of the first aspect, the updating the first UI change to the UI of the first application includes: the UI service thread changing the first UI Requesting that the corresponding UI component be updated to the UI component of the first application.

In a second aspect, a method for refreshing a user interface is provided, the method is applied to an electronic device, and the method includes: the electronic device displays a first interface, and the first interface is a first user interface of a first application UI: the electronic device displays a first interface and a second interface located above the first interface in response to a first operation of the user, wherein the second interface is a second UI of the second application; When the electronic device detects the first UI change request of the first application, it continues to display the first interface and the second interface; the electronic device displays a third interface in response to a second operation of the user, wherein, The third interface is a changed interface of the first UI of the first application.

Based on the embodiment of this application, when the first application in the foreground of the electronic device is switched to run in the background, its first interface is still visible to the user, and when the electronic device detects the UI change request of the first application, it may not immediately The UI of the first application is updated, but when the first application is switched back to the foreground, the UI change is updated to the UI of the first application. The technical solution can avoid conflict problems caused by concurrent access of multiple applications when the electronic device runs multiple applications at the same time.

With reference to the second aspect, in some implementation manners of the second aspect, the second interface is translucent; or, the second interface is displayed in a non-full screen.

In a third aspect, an electronic device is provided, including: one or more processors; one or more memories; the one or more memories store one or more computer programs, and the one or more computer programs include instructions, When the instruction is executed by one or more processors, the method for refreshing the user interface described in the first aspect and any possible implementation manner thereof is executed.

With reference to the third aspect, in some implementation manners of the third aspect, the electronic device is an electronic device with a display screen that does not support memory management unit isolation.

In the embodiment of the present application, the memory management unit isolation means that the memory management unit can divide and protect the actual physical memory, so that each software task can only access its allocated memory space.

Exemplarily, the electronic device may be a wearable device such as a smart watch, augmented reality (augmented reality, AR) glasses, a wristband, or other electronic devices with a display screen.

In a fourth aspect, an electronic device is provided, including: one or more processors; one or more memories; the one or more memories store one or more computer programs, and the one or more computer programs include instructions, When the instruction is executed by one or more processors, the method for refreshing the user interface described in the second aspect and any possible implementation manner thereof is executed.

According to a fifth aspect, a chip is provided, wherein the chip includes a processor and a communication interface, the communication interface is used to receive a signal, and transmit the signal to the processor, and the processor processes the The above signal, so that the method for refreshing the user interface described in the first aspect and any possible implementation manner thereof is executed.

According to a sixth aspect, a chip is provided, wherein the chip includes a processor and a communication interface, the communication interface is used to receive a signal, and transmit the signal to the processor, and the processor processes the The above signal, so that the method for refreshing the user interface as described in the second aspect and any possible implementation manner thereof is executed.

In a seventh aspect, a computer-readable storage medium is provided, wherein computer instructions are stored in the computer-readable storage medium, and when the computer instructions are run on a computer, the first aspect and any possible implementation thereof The method of refreshing the user interface described in the method is executed.

In an eighth aspect, a computer-readable storage medium is provided. Computer instructions are stored in the computer-readable storage medium. When the computer instructions are run on a computer, the second aspect and any possible implementation thereof The method of refreshing the user interface described in the method is executed.

In the ninth aspect, there is provided a computer program product, including computer instructions. When the computer instructions are run on the electronic device, the method for refreshing the user interface as described in the first aspect and any possible implementation thereof is provided. be executed.

In a tenth aspect, a computer program product is provided, including computer instructions, and when the computer instructions are run on an electronic device, the method for refreshing the user interface as described in the second aspect and any possible implementation thereof be executed.

Description of drawings

FIG. 1 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

FIG. 2 is a schematic diagram of a software structure of an electronic device provided by an embodiment of the present application.

Fig. 3 is a schematic diagram of an electronic device starting multiple applications provided by an embodiment of the present application.

FIG. 4 is a schematic diagram of another electronic device starting multiple applications provided by an embodiment of the present application.

FIG. 5 is a schematic flowchart of the electronic device in FIG. 4 starting multiple applications.

FIG. 6 is a schematic diagram of a foreground application and a background application jointly accessing a shared resource provided by an embodiment of the present application.

FIG. 7 is a schematic diagram of installing a three-party application into an electronic device according to an embodiment of the present application.

Fig. 8 is a schematic diagram of a group of GUI provided by the embodiment of the present application.

Fig. 9 is a schematic framework diagram of a method for refreshing a user interface provided by an embodiment of the present application.

FIG. 10 is a schematic flowchart of a method for refreshing an interface provided by an embodiment of the present application.

FIG. 11 is a schematic flowchart of another method for refreshing an interface provided by an embodiment of the present application.

FIG. 12 is a schematic flowchart of a method for refreshing an interface provided by an embodiment of the present application.

FIG. 13 is a schematic flowchart of another method for refreshing an interface provided by an embodiment of the present application.

detailed description

The technical solution in this application will be described below with reference to the accompanying drawings.

The electronic device in the embodiment of the present application may refer to a wearable device, such as a bracelet, a sports watch, etc. The electronic device may also refer to other devices with a display screen, etc. The electronic device may also be a user device, a remote terminal, a mobile device , user terminals, terminals, handheld devices with wireless communication functions, terminal devices in the future 5G network or terminal devices in the future evolved public land mobile network (PLMN), etc., the embodiments of the present application address Not limited.

FIG. 1 shows a schematic structural diagram of an electronic device 100 . The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, and an antenna 2 , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and A subscriber identification module (subscriber identification module, SIM) card interface 195 and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air 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, bone conduction sensor 180M, etc.

It can be understood that, the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components. The illustrated components can be realized in hardware, software or a combination of software and hardware.

The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU) Wait. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

Wherein, the controller may be the nerve center and command center of the electronic device 100 . The controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. The memory may hold 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 called directly from the memory. Repeated access is avoided, and the waiting time of the processor 110 is reduced, thereby improving the efficiency of the system.

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

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (serial data line, SDA) and a serial clock line (derail clock line, SCL).

The I2S interface can be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 through an I2S bus to implement communication between the processor 110 and the audio module 170 .

The PCM interface can also be used for audio communication, sampling, quantizing and encoding the analog signal. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface.

The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 and the wireless communication module 160 .

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 .

The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193 , the display screen 194 , the wireless communication module 160 , the audio module 170 , the sensor module 180 and so on.

The USB interface 130 is an interface conforming to the USB standard specification, specifically, it can be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100 , and can also be used to transmit data between the electronic device 100 and peripheral devices.

It can be understood that the interface connection relationship between the modules shown in the embodiment of the present application is only a schematic illustration, and does not constitute a structural limitation of the electronic device 100 . In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.

The charging management module 140 is configured to receive a charging input from a charger. Wherein, the charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger through the USB interface 130 . In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 100 . While the charging management module 140 is charging the battery 142 , it can also provide power for electronic devices through the power management module 141 .

The power management module 141 is used for connecting the battery 142 , the charging management module 140 and the processor 110 .

The wireless communication function of the electronic device 100 can be realized by the antenna 1 , the antenna 2 , the mobile communication module 150 , the wireless communication module 160 , a modem processor, a baseband processor, and the like.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the electronic device 100 .

A modem processor may include a modulator and a demodulator. Wherein, the modulator is used for modulating 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. Then the demodulator sends the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal is passed to the application processor after being processed by the baseband processor. The application processor outputs sound signals through audio equipment (not limited to speaker 170A, receiver 170B, etc.), or displays images or videos through display screen 194 . In some embodiments, the modem processor may be a stand-alone device. In some other embodiments, the modem processor may be independent of the processor 110, and be set in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide wireless local area networks (wireless local area networks, WLAN) (such as wireless fidelity (Wireless Fidelity, Wi-Fi) network), bluetooth (bluetooth, BT), global navigation satellite, etc. applied on the electronic device 100. System (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions.

In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology.

The electronic device 100 realizes the display function through the GPU, the display screen 194 , and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

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

The electronic device 100 can realize the shooting function through the ISP, the camera 193 , the video codec, the GPU, the display screen 194 and the application processor.

The ISP is used for processing the data fed back by the camera 193 . Camera 193 is used to capture still images or video.

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, so as to expand the storage capacity of the electronic device 100.

The internal memory 121 may be used to store computer-executable program codes including instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the internal memory 121 .

The electronic device 100 can implement audio functions through the audio module 170 , the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playback, recording, etc.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal.

Speaker 170A, also referred to as a "horn", is used to convert audio electrical signals into sound signals.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals.

The microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals.

The earphone interface 170D is used for connecting wired earphones.

The pressure sensor 180A is used to sense the pressure signal and convert the pressure signal into an electrical signal. In some embodiments, pressure sensor 180A may be disposed on display screen 194 .

The gyro sensor 180B can be used to determine the motion posture of the electronic device 100 .

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

The acceleration sensor 180E can detect the acceleration of the electronic device 100 in various directions (generally three axes).

The distance sensor 180F is used to measure the distance.

The fingerprint sensor 180H is used to collect fingerprints.

Touch sensor 180K, also known as "touch panel". 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 called a “touch screen”.

The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire the vibration signal of the vibrating bone mass of the human voice. The bone conduction sensor 180M can also contact the human pulse and receive the blood pressure beating signal.

The keys 190 include a power key, a volume key and the like.

The motor 191 can generate a vibrating reminder.

The indicator 192 can be an indicator light, and can be used to indicate charging status, power change, and can also be used to indicate messages, missed calls, notifications, and the like.

The SIM card interface 195 is used for connecting a SIM card.

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100 .

FIG. 2 is a block diagram of the software structure of the electronic device 100 according to the embodiment of the present application. The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, which are respectively the application program layer, the application program framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer from top to bottom. The application layer can consist of a series of application packages.

As shown in Figure 2, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 2, the application framework layer can include window managers, content providers, view systems, phone managers, resource managers, notification managers, and so on.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data and make it accessible to applications. Said data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebook, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. The view system can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100 . For example, the management of call status (including connected, hung up, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and so on.

The notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify the download completion, message reminder, etc. The notification manager can also be a notification that appears on the top status bar of the system in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, issuing a prompt sound, vibrating the electronic device, and flashing the indicator light, etc.

Android runtime includes core library and virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one part is the function function that the java language needs to call, and the other part is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application program layer and the application program framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

A system library can include multiple function modules. For example: surface manager (surface manager), media library (media libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of various commonly used audio and video formats, as well as still image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing, etc.

2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver.

Before introducing the technical solution of the application, some technical terms that may be involved in the solution of the application are briefly introduced below.

Process: It is a running activity of a program in a computer on a certain data set. It is the basic unit for system resource allocation and scheduling, and the basis of the operating system structure.

Thread: It is the smallest unit that the operating system can perform operation scheduling. It is included in the process and is the actual operating unit in the process. A thread refers to a single sequential flow of control in a process. Multiple threads can run concurrently in a process, and each thread performs different tasks in parallel. Multiple threads in the same process will share all system resources in the process, such as virtual address space, file descriptors, signal processing, and so on.

MMU isolation: The memory management unit can divide and protect the actual physical memory, so that each software task can only access the allocated memory space.

User interface (user interface, UI): It is a medium for interaction and information exchange between the system and users, which realizes the conversion between the internal form of information and the form acceptable to humans. Currently commonly used is the graphical user interface, which displays a direct image and is easy to operate. It is also called a man-machine interface, or interface for short.

Referring to Fig. 3, the chip of the electronic device 1 supports MMU isolation, that is, every time the system starts an application (application, App), it will create an independent process for the App to run the App, and the process as the smallest resource scheduling resource can be isolated from other processes.

As shown in FIG. 3 , when the electronic device 1 starts App1, a process 1 is created for the App1, and the process 1 may include a UI thread 1, and the UI thread 1 is used to uniformly process the update of the UI by App1, and the UI thread 1 may Access resource 1 allocated by the system for this process 1.

When the electronic device 1 starts App2, a process 2 can be created for the App2, and the process 2 can include a UI thread 2. The UI thread 2 is used to uniformly process the update of the UI by App2. The UI thread 2 can access the system for the Resource 2 allocated by process 2.

Wherein, the resource 1 and the resource 2 are isolated from each other, therefore, even if App1 and App2 run concurrently, the resources they access are different.

However, not all electronic devices support MMU isolation. For example, in some IOT lightweight devices, their chips do not support MMU isolation.

Referring to FIG. 4, the electronic device 2 does not support MMU isolation, that is, the electronic device can only run one process globally, and each application is executed by a UI thread, that is, when the system runs multiple applications at the same time, The UI threads corresponding to the multiple applications will jointly access the resources allocated by the system to the process 1 .

As shown in Figure 4, when the electronic device starts App1, a process 1 is created, which may include a UI thread 1 of App1, and the UI thread 1 is used to process the update of the UI by App1, and the UI thread 1 can access the system as Resource 1 allocated by process 1.

When the electronic device starts App2, it continues to create a UI thread 2 of App2 in the process 1, and the UI thread 2 is used to process the update of the UI by App2, and the UI thread 2 can also access the resource 1.

Therefore, when App1 and App2 run concurrently, it is possible to call the same resource together. For example, if UI thread 1 and UI thread 2 both call the same system function, an access conflict will occur, which will cause a functional exception. question.

The problem of the access conflict will be described in detail below with reference to FIGS. 5-6 .

FIG. 5 is a schematic flowchart of the electronic device in FIG. 4 starting multiple applications. The scheme may include step 101 to step 113 .

101. The system starts up.

For example, the user presses and holds the power button of the electronic device, so that the electronic device is turned on.

102. Start the management module, and create a system graphics sending and display thread.

Among them, the thread is responsible for processing the graphic display of the system, such as boot animation, desktop display and so on.

103. The graphics drawing module creates a system graphics root node.

Wherein, the system graphic root node is a root container responsible for mounting the graphic component trees of all applications, and the component tree of each application may be a subcomponent tree of the graphic root node.

104. The image drawing module renders the system graphics.

In this step, the rendering of the system graphics by the image drawing module can be understood as the image drawing module traversing all sub-component trees starting from the system root node, and sequentially drawing the components in the sub-component tree and outputting them to a unified graphics buffer (buffer).

105. Send the rendered system graphics to the screen for display.

In this step, the system interface can be called to send the rendered system graphics (that is, the components in the graphics buffer) to the screen driver for output and display. At this point, the system desktop may be displayed on the screen of the electronic device.

It should be understood that the steps from step 101 to step 105 are optional steps, and in some embodiments, the technical solution can be executed from the electronic device that is already in the power-on state, that is, it can be executed from step 106 .

106. Start App1.

For example, the user clicks the application icon of the App1 on the desktop of the electronic device to start the App1.

107. Start the management module to create the main thread of App1.

108. The startup management module sends the App1 information to the application operation management module.

The information of the App1 may include the package name of the App1, user identification (user identification, UID) and other information.

109. The application operation management module loads and runs the code of App1.

110. The application operation management module creates a component tree 1 of App1.

111. The application operation management module sets UI attributes on the component tree 1.

For example, set UI properties such as length, width, color, and transparency of the display component.

112. The application operation management module connects the component tree 1 root node to the system root node.

Wherein, the application operation management module hooks the root node of the component tree 1 with the UI attribute set to the root node of the system, so that the graphic drawing module draws the UI of App1.

113. The UI changes.

It should be understood that the above steps 106 to 113 show the process of starting App1, and the above steps can be referred to for starting App2, and details are not repeated for brevity.

Through the above steps, we can see that each App has its own thread and component tree, and UI changes are all performed on its own main thread. Since a thread is the smallest unit of CPU execution scheduling, in the execution of program code statements, for the same A function may be executed concurrently, which may cause access violations, which may cause functional exceptions.

For example, the caller will pass in the font size and text string of the posture to be set through the SetText(int fontsize, const char*text) interface in the UI function library, assuming that the SetText interface uses a global variable in its implementation g_fontsize to record the size of the text to be displayed.

When the UI thread 1 of App1 and the UI thread 2 of App2 both call the SetText interface at the same time, access conflicts may occur, resulting in text blur and other phenomena.

Referring to FIG. 6 , FIG. 6 is a schematic diagram of a foreground application and a background application jointly accessing a shared resource provided by an embodiment of the present application.

App1 is a foreground application, App2 and App3 are background applications, that is, the interface displayed on the current interface of the electronic device is the display interface of App1, and App2 and App3 run concurrently with App1, but the display interfaces of App2 and App3 are invisible to the user.

Wherein, the component tree of App1 is component tree 1, the component tree of App2 is component tree 2, and the component tree of App3 is component tree 3.

For example, node 1 of App1 calls SetText("AA", fontsize: 30), node 2 of App2 calls SetText("AA", fontsize: 38), it can be seen that the two applications access the font library public resources at the same time, then there is It may cause the phenomenon of text blur.

In view of this, the embodiment of the present application provides a method for refreshing the interface. The technical solution can cache the UI change request corresponding to the UI change of the application running in the background, and apply the UI change to the user interface when the background application is visible. In this way, conflicts caused by concurrent access by multiple applications can be avoided.

Referring to FIG. 7, the electronic device 200a may be a mobile phone, and the electronic device 200b may be a wearable device, such as a sports watch. Among them, the sports watch can establish a connection with the mobile phone through Bluetooth, wireless or wired methods.

The sports watch can install a third-party application with the assistance of the mobile phone. For example, the mobile phone downloads the installation package of the third-party application in the application market in the cloud, and installs it in the sports watch.

As shown in Figure 7, the third-party application can be "Weather", "Music", App2, etc. When the application is installed in the sports watch, through the user's operation, the installed information can be displayed on the display interface of the sports watch. App icon and app name etc. for multiple apps.

When the user clicks on the icon or text of "Music", the sports watch can display the display interface of "Music", and "Music" is the foreground application of the sports watch. At this time, the sports watch can still receive the instruction of starting the application from the mobile phone. For example, if the user pulls up App2 on the mobile phone, the sports watch will switch "Music" from the foreground to the background, and display the interface of App2 in the foreground. At this time, both "Music" and App2 are running. The foreground App2 can directly change the UI in response to user touch and other operation events, while the background application "Music" may still trigger UI changes due to its own processing logic.

FIG. 8 is a schematic diagram of a group of graphical user interfaces (graphics user interface, GUI) provided by the embodiment of the present application. Among them, (a) to (h) in FIG. 8 show the user's operation process on the sports watch in the mobile phone and the sports watch.

Referring to (a) in FIG. 8, the GUI is the display interface 310 of the sports watch 300b, and the display interface 310 may include multiple applications installed on the sports watch, including the applications "weather", "music" and "App2" etc., when the sports watch detects that the user clicks on the application icon 311 of App2 or the application name or the area where the application name is located, the GUI as shown in (b) in FIG. 8 may be displayed.

It should be understood that when the user slides the screen of the sports watch up or down with a finger, other applications installed on the sports watch may be displayed in a scrolling manner.

Referring to (b) in FIG. 8 , the GUI is the display interface 320 of App2. The display interface 320 may include an image 321 and other graphics and the like.

Referring to (c) in FIG. 8, the GUI is a display desktop 350 of the mobile phone 300a, and the display desktop 350 may include multiple applications installed in the mobile phone. After the mobile phone detects that the user clicks the application icon 351 of sports and health, the GUI as shown in (d) in FIG. 8 may be displayed.

Referring to (d) in FIG. 8 , the GUI is the first display interface 360 of sports health. The display interface 360 may include a plurality of function cards and a plurality of function controls, and each function control may correspond to a display interface. After the mobile phone detects that the user clicks on the function control 361, it may display a GUI as shown in (e) in FIG. 8 .

Referring to (e) in FIG. 8 , the GUI is the display interface 370 corresponding to the function control 361 . The display interface 370 may include a function card 371, and the function card 371 may include the name of the sports watch currently connected to the mobile phone, HUAWEI WATCH GT2 PRO, and the icon of the HUAWEI WATCH GT2 PRO. The display interface 370 may also include other smart devices that have been connected to the mobile phone, such as Huawei body fat scales, Huawei speakers, and the like. After the mobile phone detects that the user clicks on the function card 371, the GUI shown in (f) in FIG. 8 may be displayed.

Referring to (f) in FIG. 8 , the GUI is the display interface 380 corresponding to the function card 371 . The display interface 380 may include a status card 382 of the HUAWEI WATCH GT2 PRO, which may include the connection status, power, etc. of the sports watch; Download the corresponding dial from the watch face market and install it into the sports watch; the display interface 380 may also include some applications, including "weather", "health monitoring", "heart health research experience" and "App1". After the user clicks on the operation of the card 381 of "App1", the sports watch may display a GUI as shown in (g) in FIG. 8 .

Referring to (g) in FIG. 8 , the GUI is the display interface 330 of App1, wherein the display interface 330 can be in a translucent state, that is, the upper layer of the display interface 330 displays the display interface of App1, but the user can still view the display interface through the display interface. A display interface 320 of App2 located in the background can be seen.

After the sports watch detects the user's operation of sliding up or down on the screen 330, a GUI as shown in (h) in FIG. 8 may be displayed.

In some examples, the display interface 330 may not be translucent, that is, only the display interface of App1 is displayed on the display interface 330, and the display interface of App2 running in the background is invisible to the user.

In other examples, the display interface 330 may also be in a non-full-screen state, for example, the display interface 330 may be displayed on a half-screen, and the other half-screen may be used to display the display interface of the background application App2 and the like.

Referring to (h) in FIG. 8 , the GUI is the display interface 340 of App2, and the color of the graphic 341 in the display interface 340 has changed compared with that of the image 321 in (b) in FIG. 8 .

It should be understood that when App2 is running in the background, when a UI change occurs, the UI change will not be executed immediately, but will be displayed on the display interface only after the App2 is switched to the foreground.

The technical solution can avoid the problem of access conflict caused when applications running concurrently in the foreground and the background access the same resource.

Fig. 9 is a schematic framework diagram of a method for refreshing a user interface provided by an embodiment of the present application. The components of the component tree in the embodiment of the present application may also be referred to as nodes.

Referring to FIG. 9 , App1 is an application in the foreground of the electronic device, that is, App1 is an application currently displayed on the screen of the electronic device, and its UI is visible to the user. When the component 1 of the component tree 1 of App1 is changed, the change can be directly applied to the component 1, that is, the UI change can be directly displayed on the display interface of the electronic device.

App2 is a background application on the electronic device, that is, although the App2 is running, its UI is not visible to the user. When the component 2 of the component tree 2 of the App2 is changed, instead of directly applying the change to the component 2, the UI change can be cached, and when the App2 is switched to the foreground display, the electronic device draws the App2 Before the first frame, the UI change is applied to component 2, that is, when the electronic device displays the UI of App2, the UI is an interface including the above UI change.

It should be understood that when multiple UI components of the component tree 2 of the App2 are changed, the multiple UI changes can be cached sequentially, and when the App2 is switched to the foreground display, before the electronic device draws the first frame of the App2 , applying the multiple UI changes to corresponding components in the component tree in sequence, that is, when the electronic device displays the UI of App2, the UI is an interface that includes the above multiple UI changes.

In the embodiment of the present application, the electronic device can generate a UI change request for the UI change according to the change details of the UI change of the background application, and can add the UI change request to the cached data structure, and the data structure can be an array, a queue , linked list, etc. Exemplarily, the data structure is a queue, and the electronic device can add the UI change request to the cache queue, or when there are multiple UI change requests, it can place the multiple UI change requests according to the time sequence of the multiple UI change requests UI change requests are sequentially added to the cache queue.

It should be understood that the UI change requests in the cache queue may be executed sequentially according to the principle of first-in-first-out.

The change details may include but not limited to the UI component corresponding to the UI change, the properties of the UI component, and the value of the changed property, etc. The properties of the UI component may include but not limited to the length, width, and color of the component etc. features or styles etc.

In some embodiments, the background triggers multiple UI changes one after another, and the electronic device generates a UI change request for each UI change in the multiple UI changes. When the attributes of the UI component of the UI change corresponding to the multiple UI change requests are When the same, the UI change request corresponding to the detected UI change may be cached, and the previous cached UI change request with the same property as the UI component corresponding to the UI change request may be deleted. For example, the attribute of UI component 1 corresponding to UI change request 1 is color, such as red, and the attribute of UI component 1 corresponding to UI change request 2 is also the color, such as yellow, and UI change request 1 is in front, and UI change request 2 is in Afterwards, the electronic device first caches the UI change request 1, and after generating the UI change request 2, deletes the cached UI change request 1 and caches the UI change request 2, thereby avoiding additional cache nodes and reducing memory overhead. and redundant UI refresh overhead.

In other embodiments, the background triggers multiple UI changes successively, and the electronic device generates a UI change request for each of the multiple UI changes. When the multiple UI change requests correspond to the properties of the UI component of the UI change When they are the same, the value of the attribute of the UI component corresponding to the latter UI change request can be used to update the value of the attribute of the UI component corresponding to the cached UI change request, so that there is no need to add a new cache node. For example, UI change request 1 is cached in the cache queue, and the corresponding property of UI component 1 is color, such as red. At a later moment, the cache queue receives UI change request 2, and the corresponding property of UI component 1 is also color, If it is yellow, you only need to change the color of the corresponding UI component 1 in the cached UI change request 1 to yellow, without caching the UI change request 2, so as to avoid additional cache nodes, reduce memory overhead, and redundant UI Refresh overhead.

FIG. 10 is a schematic flowchart of a method for refreshing a user interface provided by an embodiment of the present application. As shown in FIG. 10 , the method may be applied to an electronic device, and the method may include steps 501 to 514 .

501. An application running in the background triggers a UI change.

It should be understood that the application runs in the background and can run concurrently with the foreground application. For example, when the application is in the background and receives a distributed message from the system, a UI change can be triggered.

In some embodiments, the distributed message may be the communication information pushed by the mobile phone to the background application of the watch. For example, the cycling navigation application is running on the watch, and the application will continuously receive information from the corresponding cycling navigation application on the mobile phone during operation. The navigation direction prompt information sent by the application is displayed on the display screen of the watch; when the cycling navigation application in the watch is switched to the background, although the UI information of the cycling navigation application is no longer displayed on the display screen of the watch , but the app will continue to receive messages from the phone.

In some other embodiments, a certain application is started on the watch, and the application will change the UI every interval, but during the interval period, the user switches the application to the background, after the interval time is reached, it will still trigger UI changes.

502. The electronic device detects a UI change.

In some embodiments, step 502 may be performed by an application framework in the electronic device. The application framework may provide the application with an application programming interface (application programming interface, API) and a programming framework. For example, the application framework may include some predefined functions and the like. The application can access the system capability of the electronic device by calling the system API. When the UI of the application changes, the application will call the corresponding API, so the application framework can detect the UI change.

In some optional embodiments, the electronic device may determine whether the UI change needs to be cached, and the process may include step 503 to step 505 .

503. The application framework queries the change management module whether the UI changes need to be cached.

Wherein, the change management module is used to handle all cache actions and cache update application process.

504. The change management module determines whether the UI change belongs to the background.

When the change management module determines that the UI change belongs to the background, step 505 can be performed; when the change management module determines that the UI change does not belong to the background, that is, the UI change belongs to the foreground, step 514 can be performed.

505. When the change management module determines that the UI change belongs to the background, return a confirmation result that the change needs to be made to the application framework.

Exemplarily, when the change management module determines that the UI change belongs to the background, a confirmation result of "yes" is returned to the application framework.

It should be understood that, in some embodiments, the electronic device may also generate a UI change request according to the change details of the UI change without determining whether the UI change needs to be cached.

Exemplarily, the process for the electronic device to generate a UI change request according to the change details of the UI may include steps 506 to 507 .

506. The application framework submits the UI change details to the change generating module.

Exemplarily, the application framework can submit the UI change details to the change generation module through the system interface.

Wherein, the UI change details may include: the changed UI component, what attribute is changed, the changed value, etc. The attribute may include but not limited to the width, height, etc., color, transparency, etc. of the component.

Exemplarily, the UI component originally corresponds to a function card in the interface, and its background color is yellow, so the UI change details may be to change the background color to red.

507. The change generation module generates a UI change request according to the UI change details.

The change generation module generates a UI change request according to the UI change details, that is, the change generation module sets the received UI change details into the data structure of the UI change request.

After the electronic device generates the UI change request, it may cache the UI change request, wherein the process for the electronic device to cache the UI change request may include steps 508 to 509 .

508. The change generation module submits the UI change request to the change cache module.

Exemplarily, the change generation module submits the UI change request to the change cache module through the system interface.

509. The change cache module adds the UI change request into a cached data structure.

Wherein, the cached data structure may include but not limited to structures such as linked list, array or queue.

Exemplarily, the data structure of the cache adopts a queue structure, then the change cache module adds the UI change request to the cache queue, and when there are multiple UI change requests, the multiple UI change requests are sequentially added to the cache queue , the cache queue may adopt a first-in-first-out manner, that is, the UI change request that first enters the cache queue is processed first.

It should be understood that when the application is switched back to the foreground display, the electronic device may update the UI change corresponding to the UI change request to the UI of the application, and this process may include steps 510 to 513 .

510. The application switches back to the foreground display.

For example, as shown in (g) and (h) in Figure 8, in response to the user's operation of sliding on the screen of the sports watch, the application App2 is switched from the background to the foreground display.

Alternatively, after the foreground app exits, the app is scheduled from the background to the foreground.

511. The application will switch back to the state displayed in the foreground to notify the change management module.

Exemplarily, the application notifies the change management module of the status of switching the application back to the foreground display by calling the system interface.

512. The change management module traverses the UI change requests cached in the cache list, and determines the UI change requests that need to be executed.

Exemplarily, the cache list is a cache queue, and the change management module sequentially traverses the UI change requests cached in the cache queue to determine the UI change requests that need to be executed.

513. Apply the UI change to the UI component.

In this step, the UI change can be applied to the corresponding UI component by calling the corresponding system interface, so that the display interface corresponding to the UI component changes or partially changes.

It should be understood that when there are multiple UI changes, the multiple UI changes can be applied to the corresponding UI components in sequence before the first frame is drawn when the application switches back to the foreground display, that is, the interface that the application switches back to the foreground display has been It is the interface after multiple UI changes.

514. Clear the cache list.

After the UI change request cached in the cache list is executed, the cache list is cleared.

It should be understood that step 514 is an optional step.

It should also be understood that the above steps are only illustrative, and the implementation sequence of the above steps is not limited in the embodiment of the present application. In some embodiments, other modules in the electronic device may also be used to implement the above functions or steps, which is not limited in this embodiment of the present application.

Based on the embodiment of this application, the UI change message of the application in the background will be cached in the list, and when the application is switched back to the foreground display, the cached UI changes will be applied to the UI components in sequence, so as to avoid multiple concurrently running Functional abnormalities that may be brought about by the application.

FIG. 11 is a schematic flowchart of another method for refreshing a user interface provided by an embodiment of the present application. As shown in FIG. 11 , the method may include steps 601 to 617 .

601. The system starts up.

For example, the user may press and hold the power button of the electronic device to start the electronic device.

It should be understood that step 601 is an optional step, and in some embodiments, this technical solution may also be implemented in an electronic device that has already been started.

602. Start the system UI service thread.

603. Start App1.

In some embodiments, step 602 may also be located after step 603, and the application does not limit the execution sequence of step 602 and step 603.

604. The start management module starts thread 1 of App1.

605. Thread 1 loads and runs the code of App1.

606. Thread 1 loads the user interface of App1.

607. Thread 1 sets the property of the UI component of App1.

For example, setting properties of corresponding UI components on the component tree.

Specifically, the UI service thread invokes the system interface to set the change in the UI component.

608. Start App2.

For example, the user clicks the application icon of the App2 on the desktop of the electronic device to start the App2. Alternatively, the App2 can be started by another electronic device, for example, referring to (f) and (g) in FIG. 8 , the application in the sports watch can be started by the mobile phone.

609. The startup management module starts thread 2 of App2.

610. Thread 2 loads and runs the code of App2.

611. Thread 2 loads the user interface of App2.

612. Thread 2 sets the property of the UI component of App2.

613. When the first UI of App1 is changed, thread 1 sends the UI change message to the UI service thread.

In some other embodiments, when the UI service thread receives multiple UI change messages, the multiple UI change messages may be put into a queue and executed sequentially.

614. The UI service thread applies the first UI change to the UI component.

In some embodiments, the UI service thread applies the information of the first UI change to the corresponding UI component, and attaches the component tree of App1 to the system root node of the electronic device, and the graphics drawing module of the electronic device can be accessed from the system The root node starts to traverse all the sub-component trees, draws the components of the sub-component tree in turn, and sends the drawn components to the screen driver for display, so that the changed UI of App2 can be displayed on the screen of the electronic device.

Exemplarily, the UI service thread may sequentially apply the multiple received UI changes to the UI component according to the time sequence of the received multiple UI changes.

615. When the second UI of App2 is changed, thread 2 sends the second UI change message to the UI service thread.

616. The UI service thread applies the second UI change to the UI component.

For this step 616, reference may be made to the relevant description of step 614, and for the sake of brevity, details are not repeated here.

It should be understood that when the UI service thread receives multiple UI change messages, it can execute the UI changes sequentially according to the order in which they are received, and when receiving multiple UI change messages at the same time, it can randomly add the UI change messages to the queue. Then execute in sequence.

The above steps are only illustrative, and the implementation sequence of the above steps is not limited in the embodiment of the present application. In some embodiments, other modules in the electronic device may also be used to implement the above functions or steps, which is not limited in this embodiment of the present application.

Based on the embodiment of this application, a UI service thread can be introduced to uniformly manage the UI changes of all applications. The UI service thread can execute all UI changes sequentially according to the time sequence of receiving UI changes, thereby avoiding multiple concurrent The problem of functional abnormality that may be caused by UI changes in the running application at the same time.

FIG. 12 is a schematic flowchart of a method for refreshing a user interface provided by an embodiment of the present application. As shown in FIG. 12 , the method may be applied to an electronic device, and the method may include steps 710 to 730 .

710. The electronic device detects a first user interface UI change request of a first application, where the first application runs in the background of the electronic device.

In step 710, the first application runs in the background of the electronic device, and when the first UI of the first application is changed, the electronic device can detect a UI change request corresponding to the UI change.

720. The electronic device caches the first UI change request.

In step 720, after detecting the first UI change request, the electronic device may cache the UI change request.

In some embodiments, the first UI change request is generated according to the first UI change information, and the electronic device adds the first UI change request into a cached data structure.

Wherein, the first information may include the UI component corresponding to the first UI change request, the attribute of the component, the value of the attribute, and the like. The data structure of the cache may be a linked list, a queue, an array, and the like.

Exemplarily, the attribute of UI component 1 is a color, such as red, and the first information corresponding to the first UI change may be to change the color of the attribute of UI component 1 to yellow.

730. When the electronic device detects that the first application is switched to run in the foreground, update the UI change corresponding to the first UI change request to the UI of the first application.

In step 730, the first application is switched from the background to the foreground. It may be that the user closes the foreground application, so that the first application becomes the foreground, or the user switches the original foreground application to the background, or the user switches the first application to the foreground. An application is switched to the foreground and so on.

When the first application is switched to run in the foreground, the electronic device can update the UI change corresponding to the UI change request to the UI of the first application before displaying the first frame of the first application, so that the user can directly see The updated UI of the first app.

Based on the embodiment of the present application, when the UI of the first application running in the background changes, the electronic device can detect the UI change request and cache the UI change request instead of executing it immediately. When the first application switches to When in the foreground, apply the UI change to the UI of the first application. The technical solution can avoid conflict problems caused by concurrent access of multiple applications when the electronic device runs multiple applications at the same time.

Optionally, the method further includes: the electronic device detecting a second UI change request of the first application, wherein the second UI change request is generated according to second information of the second UI change; when The first UI component corresponding to the first UI change request is different from the second UI component corresponding to the second UI change request, or the first UI component is the same as the second UI component but the first UI When the attribute of the component is different from the attribute of the second UI component, the electronic device adds the second UI change request to the cached data structure list; when the electronic device detects that the first application is switched When running in the foreground, update the UI change corresponding to the second UI change request to the UI of the first application.

The second information may include a UI component corresponding to the second UI change, an attribute of the component, a value of the attribute, and the like.

The UI component may include a local UI component that can be drawn directly, or may include a document object model DOM component structure in global wide area network (web) development, etc., which is not limited in this embodiment of the present application.

Optionally, the method further includes: the electronic device detecting a third UI change request of the first application, wherein the third UI change request is generated according to third information of the third UI change; when When the third UI component corresponding to the third UI change request is the same as the first UI component corresponding to the first UI change request, and the attributes of the third UI component are the same as the attributes of the first UI component, The electronic device updates the value of the property of the first UI component in the cached data structure according to the value of the property of the third UI component.

The third information may include the changed third UI component, the attribute of the component, and the value of the changed attribute. The properties of the UI component may include characteristics or styles of the component such as length, width, and color.

In some embodiments, the electronic device may also cache the third UI change request, that is, there is no need to update the value of the attribute of the UI component corresponding to the first UI change request with the value of the attribute of the UI component corresponding to the third UI change request. The embodiment does not limit this.

Optionally, the updating the UI change corresponding to the first UI change request to the UI of the first application includes: the electronic device calling a system interface to change the UI corresponding to the first UI change request Update to the UI component of the first application.

Optionally, before the electronic device caches the first UI change request, the method further includes: the electronic device determines that the first UI change request needs to be cached.

Optionally, the method further includes: when the electronic device determines that the first UI change request does not need to be cached, directly updating the UI change corresponding to the first UI change request to the UI of the first application middle.

In some embodiments, when the first application is running in the foreground, the first UI change request generally does not need to be cached, and the UI change corresponding to the first UI change request can be directly updated to the UI of the first application .

In other embodiments, when the first application is running in the background, the UI change corresponding to the first UI change request may not need to be cached, and the UI change corresponding to the first UI change request may be directly updated to In the UI of the first application.

Optionally, the electronic device caching the first UI change request includes: the electronic device sending the first UI change request to a UI service thread; the UI service thread caching the first UI change request .

For example, referring to FIG. 11 , the UI service thread may cache the received UI change request of App1 and the UI change request of App2, and execute them sequentially.

In some other embodiments, the UI service thread may directly update the UI change to the UI of the application, which is not limited in this embodiment of the present application.

Optionally, the updating the UI change corresponding to the first UI change request to the UI of the first application includes: the UI service thread updating the component corresponding to the first UI change to the In the UI component of the first application.

FIG. 13 is a schematic flowchart of another method for refreshing a user interface provided by an embodiment of the present application. The method may be applied to electronic devices, and as shown in FIG. 13 , the method may include steps 810 to 840.

810. The electronic device displays a first interface, where the first interface is a first user interface UI of a first application.

Exemplarily, as shown in (b) in FIG. 8 , the electronic device may be a smart watch, the first application may be App2, and the first user interface may be the display interface 320 of App2.

820. The electronic device displays a first interface and a second interface located above the first interface in response to a first operation of the user, where the second interface is a second UI of the second application.

Exemplarily, as shown in (f) and (g) in FIG. 8 , the first operation may be that the user clicks the card 381 of App1 in the mobile phone, and the second interface may be the display interface of App1.

830. When the electronic device detects the first UI change request of the first application, continue to display the first interface and the second interface.

Exemplarily, as shown in (g) in FIG. 8, when the electronic device detects the first UI change request of the background application App2, the smart watch continues to display the interface of App2 and the interface of App1 without any change.

Optionally, the second interface is translucent; or, the second interface is displayed in a non-full screen.

When the second interface is translucent or displayed in a non-full screen, the user can see the first interface under the second interface.

840. The electronic device displays a third interface in response to the second operation of the user, where the third interface is an interface after changing the first UI of the first application.

Exemplarily, as shown in (g) and (h) in FIG. Interface 340 is the interface after the change of the first UI.

Based on the embodiment of this application, when the first application in the foreground of the electronic device is switched to run in the background, its first interface is still visible to the user, and when the electronic device detects the first UI change request of the first application, it may not The UI of the first application is updated immediately, but when the first application is switched back to the foreground, the UI change is updated to the UI of the first application. The technical solution can avoid conflict problems caused by concurrent access of multiple applications when the electronic device runs multiple applications at the same time.

The embodiment of the present application also provides an electronic device, including one or more processors; one or more memories; the one or more memories store one or more computer programs, and the one or more computer programs include instructions, When the instruction is executed by one or more processors, the method for refreshing the user interface described in any possible implementation manner above is executed.

Optionally, the electronic device is an electronic device with a display screen that does not support memory management unit isolation.

Exemplarily, the electronic device may be wearable devices such as smart watches, AR glasses, and bracelets, or other electronic devices with display screens.

The embodiment of the present application also provides a chip, the chip includes a processor and a communication interface, the communication interface is used to receive a signal, and transmit the signal to the processor, and the processor processes the signal, The method for refreshing the user interface described in any one of the possible implementation manners above is executed.

This embodiment also provides a computer-readable storage medium, where computer instructions are stored in the computer-readable storage medium, and when the computer instructions are run on the electronic device, the electronic device executes the above-mentioned relevant method steps to realize the steps in the above-mentioned embodiments. Method to refresh the user interface.

This embodiment also provides a computer program product, which, when running on a computer, causes the computer to execute the above related steps, so as to implement the method for refreshing the user interface in the above embodiment.

In addition, an embodiment of the present application also provides a device, which may specifically be a chip, a component or a module, and the device may include a connected processor and a memory; wherein the memory is used to store computer-executable instructions, and when the device is running, The processor can execute the computer-executable instructions stored in the memory, so that the chip executes the window display method in the above method embodiments.

Wherein, the electronic device, computer-readable storage medium, computer program product or chip provided in this embodiment is all used to execute the corresponding method provided above, therefore, the beneficial effects it can achieve can refer to the above-mentioned The beneficial effects of the corresponding method will not be repeated here.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A method for refreshing a user interface, characterized in that the method is applied to an electronic device, and the method includes:

The electronic device detects a first user interface UI change request of a first application, and the first application runs in the background of the electronic device;

The electronic device caches the first UI change request;

When the electronic device detects that the first application is switched to run in the foreground, the UI change corresponding to the first UI change request is updated to the UI of the first application.
The method according to claim 1, wherein the first UI change request is generated according to the first information of the first UI change, and the electronic device caches the first UI change request, comprising:

The electronic device adds the first UI change request into a cached data structure.
The method according to claim 1 or 2, characterized in that the method further comprises:

The electronic device detects a second UI change request of the first application, wherein the second UI change request is generated according to second information of the second UI change;

When the first UI component corresponding to the first UI change request is different from the second UI component corresponding to the second UI change request, or the first UI component is the same as the second UI component but the first When the attribute of the UI component is different from the attribute of the second UI component, the electronic device adds the second UI change request to the cached data structure;

When the electronic device detects that the first application is switched to run in the foreground, the UI change corresponding to the second UI change request is updated to the UI of the first application.
The method according to any one of claims 1-3, further comprising:

The electronic device detects a third UI change request of the first application, wherein the third UI change request is generated according to third information of the third UI change;

When the third UI component corresponding to the third UI change request is the same as the first UI component corresponding to the first UI change request and the attributes of the third UI component are the same as the attributes of the first UI component, The electronic device updates the value of the property of the first UI component in the cached data structure according to the value of the property of the third UI component.
The method according to claim 1, wherein the electronic device caches the first UI change request, comprising:

The electronic device sends the first UI change request to a UI service thread;

The UI service thread caches the first UI change request.
A method for refreshing a user interface, characterized in that the method is applied to an electronic device, and the method includes:

The electronic device displays a first interface, and the first interface is a first user interface UI of a first application;

The electronic device displays a first interface and a second interface located above the first interface in response to a user's first operation, where the second interface is a second UI of the second application;

When the electronic device detects the first UI change request of the first application, it continues to display the first interface and the second interface;

The electronic device displays a third interface in response to the second operation of the user, wherein the third interface is an interface after the first UI of the first application is changed.
The method according to claim 6, wherein the second interface is translucent; or, the second interface is displayed in a non-full screen.
An electronic device, characterized in that it includes: one or more processors; one or more memories; the one or more memories store one or more computer programs, and the one or more computer programs include instructions, when When the instruction is executed by one or more processors, the method for refreshing the user interface according to any one of claims 1-5 or 6-7 is executed.
The electronic device according to claim 8, wherein the electronic device is an electronic device with a display screen that does not support memory management unit isolation.
A kind of chip, it is characterized in that, described chip comprises processor and communication interface, and described communication interface is used for receiving signal, and described signal is transmitted to described processor, and described processor processes described signal, makes as follows The method for refreshing the user interface described in any one of claims 1-5 or 6-7 is executed.
A computer-readable storage medium, characterized in that computer instructions are stored in the computer-readable storage medium, and when the computer instructions are run on a computer, any of claims 1-5 or 6-7 A method for refreshing a user interface is performed.