Interface display method and apparatus, device, storage medium, and product

Abstract

The present application relates to the technical field of wearable devices, and provides an interface display method and apparatus, a device, a storage medium, and a product. The method is executed by a wearable device, and the wearable device comprises a first system and a second system. The method comprises: converting a first interface resource file of a first target interface by means of a first system to obtain a second interface resource file; displaying the first target interface by means of the first system and the first interface resource file; and / or displaying a second target interface by means of the second system and the second interface resource file. In some embodiments of the present application, a target interface can be displayed in a dual-core, dual-system wearable device.

Description

Interface display methods, devices, equipment, storage media and products Technical Field

[0001] This application relates to the field of wearable device technology, and in particular to an interface display method, apparatus, device, storage medium and product. Background Technology

[0002] Current wearable devices consist of two operating systems: a primary operating system and a secondary operating system. The primary operating system is a high-performance (large-core) system, while the secondary operating system is a low-performance (small-core) system. Wearable devices can switch to the high-performance system when handling high-performance tasks and switch to the low-performance system when idle or handling low-performance tasks. When neither operating system is processing any tasks, the device switches to the watch face application, which displays watch face resources.

[0003] Summary of the Invention

[0004] This application provides an interface display method, apparatus, device, storage medium, and product to realize the display of a target interface in a dual-core, dual-system wearable device. The technical solution is as follows:

[0005] On one hand, an interface display method is provided, executed by a wearable device, the wearable device including a first system and a second system; the method includes:

[0006] The first interface resource file is obtained by converting the first interface resource file of the first target interface through the first system;

[0007] Display the first target interface using the first system and the first interface resource file; and / or,

[0008] The second target interface is displayed using the second system and the second interface resource file.

[0009] On the other hand, an interface display device is provided, the device being deployed in a wearable device, the wearable device including a first system and a second system; the device includes:

[0010] The conversion module is used to convert the first interface resource file of the first target interface through the first system to obtain the second interface resource file;

[0011] The first display module is configured to display the first target interface using the first system and the first interface resource file; and / or,

[0012] The second display module is used to display the second target interface through the second system and the second interface resource file.

[0013] On the other hand, a wearable device is provided, the wearable device including a processor and a memory, the memory storing at least one piece of program code, the at least one piece of program code being loaded and executed by the processor to implement the interface display method described above.

[0014] On the other hand, a computer-readable storage medium is provided, wherein at least one piece of program code is stored in the storage medium, the at least one piece of program code being loaded and executed by a processor to implement the interface display method described above.

[0015] On the other hand, a computer program product is provided, which stores at least one piece of program code for execution by a processor to implement the interface display method described above.

[0016] In some embodiments of this application, the first interface resource file is adapted to the first system but not to the second system. Therefore, the first system can parse the first interface resource file to display the target interface, while the second system cannot display the target interface because it cannot parse the first interface resource file. In this embodiment, the first system converts the first interface resource file into a second interface resource file that the second system can parse, thereby enabling the second system to display the target interface. Thus, in this embodiment, when developing the target interface for a dual-core, dual-system wearable device, only one interface resource file (the first interface resource file) needs to be developed to achieve dual-core, dual-system display of the target interface, reducing the tediousness and cost of manual development. Attached Figure Description

[0017] Figure 1 shows a flowchart illustrating an exemplary embodiment of the interface display method of this application;

[0018] Figure 2 shows a flowchart illustrating an exemplary embodiment of the interface display method of this application;

[0019] Figure 3 shows a schematic diagram of an interface display method according to an exemplary embodiment of this application;

[0020] Figure 4 shows a flowchart illustrating an exemplary embodiment of the interface display method of this application;

[0021] Figure 5 shows a flowchart illustrating an exemplary embodiment of the interface display method of this application;

[0022] Figure 6 shows a flowchart illustrating an exemplary embodiment of the interface display method of this application;

[0023] Figure 7 shows a block diagram of an interface display device illustrated in an exemplary embodiment of this application;

[0024] Figure 8 shows a block diagram of a wearable device illustrated in an exemplary embodiment of this application. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0026] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0027] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the first interface resource files and the second interface resource files involved in this application were obtained with full authorization.

[0028] This application proposes a solution for the interface display of wearable devices with dual cores and dual systems. It is understood that dual cores can refer to two processing units (such as processors), which can be packaged in a single chip. For example, the processing unit can be an integrated circuit or a chip; alternatively, dual cores can also be understood as two independently packaged chips. Dual systems can refer to programs running on both processing units, such as an operating system.

[0029] For example, the power consumption of the first system is greater than that of the second system, and / or the performance of the first system is higher than that of the second system. In related technologies, when developers of dual-core dual-system wearable devices only develop the first interface resource file for the target interface of the first system, the second system's performance limitations prevent it from directly parsing the first interface resource file. This results in the wearable device only displaying the target interface when the first system controls the screen, and failing to display the target interface when the second system controls the screen, leading to display asynchrony, especially when the two systems switch screen control.

[0030] In some embodiments, the wearable device may include multiple modes, such as a first mode and / or a second mode. The first operating mode refers to an operating mode where the first system and the second system can switch control. For example, this control includes, but is not limited to, control of the display screen. Understandably, in the first operating mode, control can be switched between the first and second systems according to business needs or user triggers. For example, when switching to the first system control, the second system may enter sleep mode; for example, when switching to the first system control, it may not enter sleep mode; for example, when switching to the second system control, the first system may or may not enter sleep mode; for example, when switching to the second system control, the first system may not enter sleep mode. The first operating mode can also be called a fully intelligent mode or a hybrid mode. For example, the second operating mode refers to an operating mode where the second system is in a running or sleep state while the first system is in a turned-off state. In this mode, the overall power consumption may be the lowest, but the processing performance is not high. Therefore, the second operating mode can be called a light intelligent mode or a low-power mode. Since the wearable device can switch between different modes, there are requirements for the consistency of the target interface display during mode switching, as well as the issue of ensuring the convenience of the user settings interface.

[0031] Alternatively, in related technologies, if both systems need to display the target interface, developers need to develop a separate interface resource file for each system, increasing development costs. In some embodiments of this application, developers only need to develop a first interface resource file for the first system. The first system then parses and converts this first interface resource file into a second interface resource file that the second system can parse. Thus, the first system displays the target interface based on the first interface resource file, and the second system displays the target interface based on the second interface resource file. This not only reduces development costs but also maintains the synchronization of the target interface display between the first and second systems. Furthermore, users only need to make one setting to synchronize the interfaces for at least two systems, making it more convenient.

[0032] Understandably, the target interface includes one or more of the following: a watch face, an application list, and a card interface. For example, the target interface is a theme interface. For example, the target interface may include a first target interface and a second target interface, with the first target interface displayed on a first system and the second target interface displayed on a second system.

[0033] In some embodiments, the data packet packaging rules corresponding to the first target interface and the second target interface are different, and the first system and the second system have different capabilities to parse data packets. Therefore, it is necessary to provide the target interface data resources synchronously to the two systems through the embodiments provided in this application.

[0034] For example, the target interface displayed by the first system based on the first interface resource file can be called the first target interface, and the target interface displayed by the second system based on the second interface resource file can be called the second target interface. The first target interface and the second target interface can be completely identical; or, the first target interface and the second target interface are partially the same, that is, the interface element resources of the first target interface and the interface element resources of the second target interface are partially the same; for example, the second target interface includes some of the interface element resources of the first target interface.

[0035] In some embodiments, the first system can parse the first interface resource file, while the second system cannot parse the first interface resource file. For example, the first interface resource file is a file packaged according to the parsing rules applicable to the first system. The second system cannot parse the first interface resource file, so the first system needs to generate a second interface resource file that the second system can parse based on the first interface resource file before providing it to the second system for parsing and displaying the second target interface.

[0036] For example, the power consumption of the first system being greater than that of the second system can be understood as the standby power consumption of the first system being greater than that of the second system, or the power consumption of the first system when processing business being greater than that of the second system when processing the same business, or the overall power consumption of the first system being greater than that of the second system. For example, the performance of the first system being higher than that of the second system can be understood as the computing power or hardware resources of the first system being lower than those of the second system. The first system can be an intelligent system; in some embodiments, the first system is HarmonyOS, Android, or iOS; for example, the first system is WearOS. The second system can be an embedded system; for example, the second system is a Real-Time Operating System (RTOS) or HarmonyOS. For example, a wearable device can include two processors, a first processor and a second processor, with the first processor running the first system and the second processor running the second system. The first processor can be a Central Processing Unit (CPU). The second processor can be a Microcontroller Unit (MCU). It should be noted that the first processor and the second processor can be two independently packaged chips or packaged in the same chip. Alternatively, the wearable device may include a processor with multiple cores, each running a first system and a second system respectively.

[0037] In some embodiments, the wearable device may include two or more systems, that is, the wearable device may include at least three systems; the at least three systems include at least two embedded systems and at least one smart system; or, the at least three systems include at least two smart systems and at least one embedded system. Accordingly, the wearable device includes at least three processors for running at least three systems, one of which is used to run one system; or, the wearable device includes multiple cores of a processor for running at least three systems.

[0038] Please refer to Figure 1, which shows a flowchart of an interface display method illustrated in an exemplary embodiment of this application. The method is executed by a wearable device, which includes a first system and a second system; referring to Figure 1, the method includes:

[0039] Step 101: The first interface resource file of the first target interface is converted and processed by the first system to obtain the second interface resource file.

[0040] As is understandable, a target interface (the first target interface and / or the second target interface) refers to a user interface containing specific element information; for example, a target interface (the first target interface and / or the second target interface) can be a dial interface, a welcome screen, or a screensaver interface, etc. The first interface resource file is the interface resource file that the first system can parse.

[0041] In some embodiments, the power consumption of the first system is greater than that of the second system; and / or, the performance of the first system is higher than that of the second system, i.e., the first system is a large-core system and the second system is a small-core system. In this case, the first interface resource file includes interface element files and style files. The interface element files include interface element resources and style resources. The interface element resources may include image resources and text resources, etc. Image resources are used to represent images included in the first target interface; for example, image resources include at least one of images such as preview images and background images. Text resources are used to represent text included in the first target interface; for example, text resources may include at least one of time resources and weather resources, etc. Interface element resources may also include other resources, such as animated image resources, etc. The first processor stores logic code, which is used to parse the first interface resource file to obtain interface resource data. The interface resource data includes interface element files and style files that the first system can parse and render, and the interface resource data is used to display the first target interface. The first processor is used to run the first system. Style resources include at least one of resources such as layout resources, style resources, font resources, and language resources.

[0042] Because the format of interface element files (such as images) is relatively complex, the second system (small-core system) cannot directly parse them, thus preventing the second system from directly parsing the first interface resource file to display the second target interface. Therefore, the first system (large-core system) converts the first interface resource file to obtain a second interface resource file that the second system (small-core system) can parse, allowing the second system to directly parse the second interface resource file to display the second target interface. The step of converting the first interface resource file of the first target interface to obtain the second interface resource file is described in detail in the next embodiment. After obtaining the second interface resource file through the first system, it can be directly sent to the second system; or, the second interface resource file can be stored in the first interface directory of the first system, and retrieved from the first interface directory when the second system needs to display the second interface; or, the second interface resource file can be stored in the second interface directory of the second system, and retrieved from the second interface target when the second system needs to display the second interface. The first interface directory of the first system can be a directory of the independent storage space of the first system or a directory of the shared storage space of the first system; the second interface directory of the second system can be a directory of the independent storage space of the second system or a directory of the shared storage space of the second system.

[0043] In other embodiments, the power consumption of the first system is less than that of the second system; and / or, the performance of the first system is lower than that of the second system, that is, the first system is a small-core system and the second system is a large-core system. In this case, the first interface resource file includes interface rendering data, that is, the interface rendering data of the target interface developed by the developers for the small-core system. The small-core system encapsulates the interface rendering data of the first target interface into a second interface resource file, so that the large core parses the second interface resource file to display the second target interface.

[0044] Step 102: Display the first target interface using the first system and first interface resource files;

[0045] It should be noted that displaying the first target interface through the first system and the first interface resource file can be understood as the first system controlling the display screen to display the first target interface based on the first interface resource file.

[0046] In some embodiments, displaying a first target interface through a first system and a first interface resource file includes: when the system running in the foreground of the wearable device is the first system, displaying the first target interface through the first system and the first interface resource file.

[0047] In some embodiments, the system running in the foreground can refer to a system that controls the display screen. For example, it may display a dial for the system or an interface for an application running on the system. For instance, controlling the display screen includes controlling whether the screen is on, off, or in a state of off-screen display.

[0048] In some embodiments, the system running in the foreground can perform other business processes in addition to controlling the display screen, such as running related applications, interacting with users, and receiving and processing sensor data.

[0049] In some embodiments, the system running in the foreground can be a system that controls the display screen.

[0050] In some embodiments, the system running in the foreground may be a system that controls the display screen and is in a wake-up state; for example, controlling the display screen includes controlling the display screen to turn on, turn off, or turn off the display.

[0051] In some embodiments, the system running in the foreground can be a system that controls the display screen and is in a wake-up state.

[0052] In some embodiments, when there is no business demand, both the first and second systems can enter a sleep state, but the display can be controlled by one of the systems to be in a screen-off state.

[0053] For example, if both systems are in sleep mode, the display is controlled by the low-power or high-power system; if both systems are running, the display is controlled by the high-power system; if the low-power system is running and the high-power system is in sleep mode, the display is controlled by the low-power system.

[0054] In some embodiments, the system running in the background may be a system without a control display screen.

[0055] In some embodiments, the background-running system may be a system that is in a wake-up state without controlling the display screen. For example, the background-running system may perform business processing in the background or provide auxiliary support to the foreground system.

[0056] In some embodiments, while the high-power system controls the display screen in the foreground, the low-power system runs in the background, for example, acquiring sensor data, running algorithms, or receiving Bluetooth data.

[0057] In some embodiments, while the low-power system controls the display screen in the foreground, the high-power system runs in the background, for example, processing application data or receiving data synchronized from the low-power system.

[0058] It is understood that a wake-up state can be understood as the system's modules used for processing business being in a running state; different business processes may consume different amounts of power. A sleep state can be understood as the system's modules used for processing business not running, but in a non-shutdown state. For example, there can be various types of sleep states, and different types have different power consumption; lower power consumption may require a longer wake-up time. Of course, the general understanding of wake-up and sleep states in the field of wearable devices can also be referenced, and no limitation is made here. It is understood that, without conflict, the above embodiments and their features can be combined or substituted to form other definitions regarding a foreground running system or a background running system. Related definitions can also be further combined with other embodiments of this application.

[0059] In some embodiments, the power consumption of the first system is greater than that of the second system; and / or, the performance of the first system is higher than that of the second system, that is, the first system is a big-core system and the second system is a small-core system. In this case, the step of displaying the first target interface through the first system and the first interface resource file can be: parsing the first interface resource file through the logic code on the first processor to obtain interface resource data; displaying the first target interface based on the interface resource data, wherein the first processor is used to run the first system.

[0060] In other embodiments, the power consumption of the first system is less than the functionality of the second system; and / or, the performance of the first system is lower than that of the second system, i.e., the first system is a small-core system and the second system is a large-core system. In this case, the step of displaying the first target interface through the first system and the first interface resource file can be: parsing the interface rendering data in the first interface resource file through the firmware code on the first processor, rendering the interface rendering data to display the first target interface, and the first processor is used to run the first system.

[0061] Step 103: Display the second target interface through the second system and second interface resource files.

[0062] It should be noted that displaying the second target interface through the second system and the second interface resource file can be understood as the second system controlling the display screen to show the second target interface based on the second interface resource file.

[0063] In some embodiments, displaying the second target interface through the second system and the second interface resource file includes: when the system running in the foreground of the wearable device is the second system, displaying the second target interface through the second system and the second interface resource file.

[0064] It is understood that the order of steps 102 and 103 is not limited, and in some embodiments there may be only step 102, in some embodiments there may be only step 103, and in some embodiments there may be both steps 102 and 103.

[0065] In some embodiments, the power consumption of the first system is greater than that of the second system; and / or, the performance of the first system is higher than that of the second system, that is, the first system is a big-core system and the second system is a small-core system. In this case, the step of displaying the second target interface through the second system and the second interface resource file can be: parsing the second interface resource file through the second system to obtain the interface rendering data of the second target interface; rendering the interface rendering data to display the second target interface.

[0066] In some embodiments, the step of obtaining the interface rendering data of the second target interface by parsing the second interface resource file through the second system can be as follows: parsing the second interface resource file through the firmware code on the second processor to obtain the interface rendering data of the second target interface, wherein the interface rendering data is the interface data that the second system can directly render; the second processor is used to run the second system.

[0067] In other embodiments, the power consumption of the first system is less than the functionality of the second system; and / or, the performance of the first system is lower than that of the second system, i.e., the first system is a small-core system and the second system is a large-core system. In this case, the step of displaying the second target interface through the second system and the second interface resource file can be: parsing the second interface resource file through the logic code on the second processor to obtain interface resource data; displaying the second target interface based on the interface resource data, and the second processor is used to run the second system.

[0068] In some embodiments of this application, since the first system can convert the first interface resource file of the target interface (which can be called the first target interface) into a second interface resource file (which can be called the resource file of the second target interface) that the second system can parse, not only can the first system parse the first interface resource file to display the target interface (which can be called the first target interface), but the second system can also parse the second interface resource file to display the target interface (which can be called the second target interface), thereby realizing the display of the target interface in a dual-core dual-system wearable device.

[0069] When the target interface is a watch face, the embodiments of this application can enable any third-party watch face to be displayed not only in the first system, but also in the second system, thereby improving the consistency of watch face display.

[0070] Furthermore, when the first target interface and the second target interface are the same, since the method provided by the embodiments of this application can realize the display of the same target interface by the two systems based on the first interface resource file, when developing the target interface for a dual-core dual-system wearable device, only one interface resource file (the first interface resource file) needs to be developed, which reduces the tediousness and cost of human development, thereby speeding up the display of the target interface and improving the user's ultimate experience.

[0071] Please refer to Figure 2, which shows a flowchart illustrating an exemplary embodiment of the interface display method of this application. The method is executed by a wearable device, which includes a first system and a second system. The power consumption of the first system is greater than that of the second system; and / or, the performance of the first system is higher than that of the second system. In some embodiments of this application, the method is illustrated by the example of the first system parsing and converting a first interface resource file into a second interface resource file and then storing it in the first system. Referring to Figure 2, the method includes:

[0072] Step 201: The wearable device parses the first interface resource file of the first target interface into interface rendering data through the first system.

[0073] In some embodiments, a first interface resource file is stored in a first system; the first interface resource file includes interface element files and style files; correspondingly, this step can be: the wearable device parses the interface element files and style files into renderable interface element information and style information respectively through the first system, and determines the interface element information and style information as interface rendering data. Here, interface rendering data refers to interface data that can be directly rendered; for example, the format of the interface rendering data is binary format, that is, the format of the interface element information and the format of the style information can both be binary format; for example, referring to Figure 3, the first system parses the interface element files included in the first interface resource file into binary interface element information, the interface element information including a background image (bg.bin) and a preview image (preview.bin). The first system parses the style files included in the first interface resource file into binary style information, the style information including style information (style.bin), layout information (setting.bin), font information (font_x.bin), and language information (language_x.bin). Here, the layout information includes the coordinate position of each interface element.

[0074] Step 202: The wearable device generates a second interface resource file suitable for the second system based on the interface rendering data.

[0075] For example, the first system of the wearable device generates a second interface resource file suitable for the second system based on the interface rendering data.

[0076] For example, the first system can repackage the parsed interface rendering data into a data package suitable for the second system's dial according to the second system's dial framework rules. For example, the first system stores the interface rendering data into the corresponding field in the second interface resource file based on the field to which the interface rendering data belongs.

[0077] For example, the interface rendering data includes interface element information and style information; the second interface resource file includes element fields and style fields. The wearable device stores the interface element information in the element fields included in the second interface resource file and stores the style information in the style fields included in the second interface resource file through the first system.

[0078] The first system packages the renderable interface element information and style information into the second interface resource file, so that the second interface file contains data that can be directly rendered. In this way, the second system (small core system) can directly parse the second interface file and render it to display the target interface.

[0079] Step 203: The wearable device stores the second interface resource file in the first interface directory of the first system.

[0080] For example, the first system of the wearable device stores the second interface resource file in the first interface directory of the first system.

[0081] In some embodiments, when the target interface is a watch face, the first interface directory can be the watch face directory, that is, in this step, the second interface resource file is stored in the watch face directory of the big core system. The first interface directory of the first system can be a directory in the independent storage space of the first system, or it can be a directory in the shared storage space of the first system.

[0082] Step 204: The wearable device obtains the second interface resource file from the first interface directory of the first system through the second system, and displays the second target interface based on the second interface resource file through the second system.

[0083] Understandably, when the foreground system is the second system, the first system may be running in the background or in a dormant state. When the first system is running in the background, the steps for the wearable device to retrieve the second interface resource file from the first interface directory of the first system via the second system can be as follows: the second system sends a retrieval request to the first system; the first system receives the retrieval request, retrieves the second interface resource file from the first interface directory, and sends the second interface resource file to the second system; the second system receives the second interface resource file sent by the first system. When the first system is in a dormant state, the steps for the wearable device to retrieve the second interface resource file from the first interface directory of the first system via the second system can be as follows: the second system sends a wake-up request to the first system; the first system is woken up based on the wake-up request; then the second system sends a retrieval request to the first system; the first system receives the retrieval request, retrieves the second interface resource file from the first interface directory, and sends the second interface resource file to the second system; the second system receives the second interface resource file sent by the first system.

[0084] In some embodiments, the first system runs on the first processor, and the second system runs on the second processor. Accordingly, the step of the first system sending the second interface resource file to the second system can be: the first system sending the second interface resource file to the second system through a dual-core communication channel between the first and second processors. Similarly, the step of the second system receiving the second interface resource file sent by the first system can be: the second system receiving the second interface resource file sent by the first system through a dual-core communication channel between the first and second processors.

[0085] For example, please refer to Figure 3. The large core system (first system) sends the parsed and converted second interface resource file to the small core system (second system), which then directly parses the second interface resource file to display the dial.

[0086] Step 205: Display the first target interface using the first system and first interface resource files.

[0087] In some embodiments, this step is the same as step 102, and will not be repeated here. For example, please continue to refer to Figure 3. The first interface resource file includes a dial image resource, other dial resources (dial animation resources), and a dial layout file. The first system directly parses the first interface resource file through logic code to obtain the dial image resource, other dial resources (dial animation resources), and dial layout file. The first target interface is obtained by drawing the dial image resource, other dial resources (dial animation resources), and dial layout file. That is, the first interface resource file is directly parsed to display the dial. The logic code can be stored in the first interface resource file or in other storage space of the first processor.

[0088] In some embodiments of this application, since the first system (large-core system) can convert the first interface resource file of the target interface (which can be called the first target interface) into a second interface resource file (which can be called the resource file of the second target interface) that can be parsed by the second system (small-core system), not only can the first system parse the first interface resource file to display the target interface (which can be called the first target interface), but the second system can also parse the second interface resource file to display the target interface (which can be called the second target interface), thereby realizing the display of the target interface in a dual-core, dual-system wearable device. Furthermore, storing the first interface resource file and the second interface resource file in the first system (large-core system) saves storage space in the second system (small-core system).

[0089] Please refer to Figure 4, which shows a flowchart illustrating an exemplary embodiment of the interface display method of this application. The method is executed by a wearable device, which includes a first system and a second system. The power consumption of the first system is greater than that of the second system; and / or, the performance of the first system is higher than that of the second system. In some embodiments of this application, the method is illustrated by the example of the first system parsing and converting a first interface resource file into a second interface resource file and then storing it in the second system. Referring to Figure 4, the method includes:

[0090] Step 401: The wearable device parses the first interface resource file of the first target interface into interface rendering data through the first system.

[0091] In some embodiments, this step is the same as step 201, and will not be described again here.

[0092] Step 402: The wearable device stores the interface rendering data to the second interface resource file through the first system.

[0093] In some embodiments, this step is the same as step 202, and will not be described again here.

[0094] Step 403: The wearable device stores the second interface resource file in the second interface directory of the second system.

[0095] In some embodiments, when the first target interface is a watch face, the first interface directory can be the watch face directory, meaning that the second interface resource file is stored in the watch face directory of the small-core system in this step. In some embodiments of this application, the wearable device stores the second interface resource file in the second system. This way, when the second system displays the second target interface based on the second interface resource file, it can directly retrieve the second interface resource file from its local storage, saving the time required to transfer the second interface resource file between the first and second systems, thereby improving the display efficiency of the second target interface.

[0096] Step 404: The wearable device obtains the second interface resource file from the second interface directory of the second system through the second system, and displays the second target interface based on the second interface resource file through the second system.

[0097] In some embodiments, this step is the same as step 204, and will not be described again here.

[0098] Step 405: Display the first target interface using the first system and first interface resource files.

[0099] In some embodiments, this step is the same as step 205, and will not be described again here.

[0100] In some embodiments of this application, since the first system can convert the first interface resource file of the target interface (which can be referred to as the first target interface) into a second interface resource file (which can be referred to as the resource file of the second target interface) that the second system can parse, not only can the first system parse the first interface resource file to display the target interface (which can be referred to as the first target interface), but the second system can also parse the second interface resource file to display the target interface (which can be referred to as the second target interface), thereby realizing the display of the target interface in a dual-core, dual-system wearable device. Furthermore, by storing the first interface resource file in the first system and the second interface resource file in the second system (the large-core system), when the first system displays the first target interface based on the first interface resource file and the second system displays the second target interface based on the second interface resource file, both can directly obtain the corresponding interface resource file locally, saving the time required for transmitting interface resource files between the first and second systems, thereby improving the display efficiency of the target interface.

[0101] Please refer to Figure 5, which shows a flowchart illustrating an exemplary embodiment of the interface display method of this application. The method is executed by a wearable device, which includes a first system and a second system. The power consumption of the first system is less than that of the second system; and / or, the performance of the first system is lower than that of the second system. In some embodiments of this application, the method is illustrated by the example of the first system parsing and converting a first interface resource file into a second interface resource file and then storing it in the second system. Referring to Figure 5, the method includes:

[0102] Step 501: The wearable device encapsulates the interface rendering data included in the first interface resource file of the first target interface into a resource file through the first system.

[0103] The interface rendering data includes interface element information and style information; the first system encapsulates the interface element information and style information into interface element files and style files.

[0104] Step 502: The wearable device stores the resource file in the second interface resource file through the first system.

[0105] Step 503: The wearable device stores the second interface resource file in the first interface directory of the first system.

[0106] Step 504: The wearable device obtains the second interface resource file from the first interface directory of the first system through the second system, and displays the second target interface based on the second interface resource file through the second system.

[0107] In some embodiments, the process of the wearable device obtaining the second interface resource file from the first interface directory of the first system through the second system can refer to step 204; the step of the wearable device obtaining the second interface resource file from the first interface directory of the first system through the second system and displaying the second target interface based on the second interface resource file can be as follows: the wearable device parses the second interface resource file through the logic code on the second processor to obtain interface resource data; and displays the second target interface based on the interface resource data, wherein the second processor is used to run the second system.

[0108] Step 505: The wearable device displays the first target interface through the first system and the first interface resource file.

[0109] In some embodiments, the step of a wearable device displaying a first target interface through a first system and a first interface resource file may be as follows: the wearable device parses the interface rendering data in the first interface resource file through firmware code on the first processor, renders the interface rendering data to display the first target interface, and the first processor is used to run the first system.

[0110] In some embodiments of this application, since the first system (small core system) can encapsulate the interface rendering data included in the first interface resource file of the target interface (which can be called the first target interface) into a second interface resource file (which can be called the resource file of the second target interface) that can be parsed by the second system (large core system), not only can the first system parse the first interface resource file to display the target interface (which can be called the first target interface), but the second system can also parse the second interface resource file to display the target interface (which can be called the second target interface), thereby realizing the display of the target interface in a dual-core dual-system wearable device.

[0111] Please refer to Figure 6, which shows a flowchart illustrating an exemplary embodiment of the interface display method of this application. The method is executed by a wearable device, which includes a first system and a second system. The power consumption of the first system is less than that of the second system; and / or, the performance of the first system is lower than that of the second system. In some embodiments of this application, the method is illustrated by the example of the first system parsing and converting a first interface resource file into a second interface resource file and then storing it in the second system. Referring to Figure 6, the method includes:

[0112] Step 601: The wearable device encapsulates the interface rendering data included in the first interface resource file of the first target interface into a resource file through the first system.

[0113] The interface rendering data includes interface element information and style information; the first system encapsulates the interface element information and style information into interface element files and style files.

[0114] Step 602: The wearable device stores the resource file in the second interface resource file through the first system.

[0115] Step 603: The wearable device stores the second interface resource file in the second interface directory of the second system.

[0116] In some embodiments of this application, the wearable device stores the second interface resource file in the second system. When the second system displays the second target interface based on the second interface resource file, it can directly obtain the second interface resource file from the local system, saving the time required to transfer the second interface resource file between the first system and the second system, thereby improving the display efficiency of the second target interface.

[0117] Step 604: The wearable device obtains the second interface resource file from the second interface directory of the second system through the second system, and displays the second target interface based on the second interface resource file through the second system.

[0118] In some embodiments, this step is similar to step 504, and will not be described again here.

[0119] Step 605: The wearable device displays the first target interface through the first system and the first interface resource file.

[0120] In some embodiments, this step is similar to step 505, and will not be described again here.

[0121] In some embodiments of this application, since the first system (small-core system) can encapsulate the interface rendering data included in the first interface resource file of the target interface (which can be referred to as the first target interface) into a second interface resource file that can be parsed by the second system (large-core system), not only can the first system parse the first interface resource file to display the target interface (which can be referred to as the first target interface), but the second system can also parse the second interface resource file to display the target interface (which can be referred to as the second target interface), thereby realizing the display of the target interface in a dual-core, dual-system wearable device. Furthermore, by storing the first interface resource file in the first system (small-core system) and the second interface resource file in the second system (large-core system), when the first system displays the first target interface based on the first interface resource file and the second system displays the second target interface based on the second interface resource file, both can directly obtain the corresponding interface resource file locally, saving the time required for transmitting interface resource files between the first and second systems, thereby improving the display efficiency of the target interface.

[0122] Please refer to Figure 7, which illustrates an interface display device according to an exemplary embodiment of this application. The device is deployed in a wearable device, which includes a first system and a second system. Referring to Figure 7, the device includes:

[0123] The conversion module 701 is used to convert the first interface resource file of the first target interface through the first system to obtain the second interface resource file;

[0124] The first display module 702 is configured to display the first target interface using the first system and the first interface resource file; and / or,

[0125] The second display module 703 is used to display the second target interface through the second system and the second interface resource file.

[0126] In some embodiments, the power consumption of the first system is greater than that of the second system; and / or, the performance of the first system is higher than that of the second system.

[0127] In some embodiments, the conversion module 701 is used to parse the first interface resource file of the first target interface into interface rendering data through the first system; and generate a second interface resource file suitable for the second system based on the interface rendering data. For example, based on the field to which the interface rendering data belongs, the interface rendering data is stored in the corresponding field of the second interface resource file.

[0128] In some embodiments, the first interface resource file includes an interface element file and a style file;

[0129] The conversion module 701 is used to parse the interface element file and the style file into renderable interface element information and style information respectively through the first system, and determine the interface element information and style information as the interface rendering data.

[0130] In some embodiments, the apparatus further includes:

[0131] The first storage module is used to store the second interface resource file in the first interface directory of the first system;

[0132] The second display module 703 is used to obtain the second interface resource file from the first interface directory of the first system through the second system.

[0133] In some embodiments, the apparatus further includes:

[0134] The second storage module is used to store the second interface resource file in the second interface directory of the second system;

[0135] The second display module 703 is used to obtain the second interface resource file from the second interface directory of the second system through the second system.

[0136] In some embodiments, the second display module 703 is used to parse the second interface resource file through the second system to obtain the interface rendering data of the second target interface; and to render the interface rendering data to display the second target interface.

[0137] In some embodiments, the second display module 703 is used to parse the second interface resource file through firmware code on the second processor to obtain interface rendering data of the second target interface, and the second processor is used to run the second system.

[0138] In some embodiments, the first display module 702 is configured to parse the first interface resource file through logic code on the first processor to obtain interface resource data, the first processor being configured to run the first system; and to display the first target interface based on the interface resource data.

[0139] In some embodiments, the power consumption of the first system is less than that of the second system; and / or, the performance of the first system is lower than that of the second system; and / or, the first target interface and the second target interface are completely or partially the same, and the second system cannot parse the resource file of the first interface.

[0140] In some embodiments, the conversion module 701 is configured to encapsulate the interface rendering data included in the first interface resource file of the first target interface into a resource file through the first system; and store the resource file in the second interface resource file. For example, a second interface resource file suitable for the second system is generated based on the resource file.

[0141] In some embodiments of this application, since the first system can convert the first interface resource file of the target interface (which can be referred to as the first target interface) into a second interface resource file (which can be referred to as the resource file of the second target interface) that can be parsed by the second system, not only can the first system parse the first interface resource file to display the target interface (which can be referred to as the first target interface), but the second system can also parse the second interface resource file to display the target interface (which can be referred to as the second target interface), thereby realizing the display of the target interface in a dual-core dual-system wearable device.

[0142] It should be noted that the interface display device provided in the above embodiments is only illustrated by the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the wearable device can be divided into different functional modules to complete all or part of the functions described above. In addition, the interface display device and the interface display method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0143] Please refer to Figure 8, which shows a block diagram of a wearable device 800 according to an exemplary embodiment of this application. The wearable device 800 in this application may include one or more of the following components: a processor 810, a memory 820, and a display screen 830.

[0144] Processor 810 includes at least two processors, designated as a first processor and a second processor. The first processor runs a first system, and the second processor runs a second system. Processor 810 may include one or more processing cores. Processor 810 connects to various parts within the wearable device 800 using various interfaces and lines. It executes various functions and processes data of the wearable device 800 by running or executing instructions, programs, code sets, or instruction sets stored in memory 820, and by calling data stored in memory 820. Optionally, processor 810 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). Processor 810 may integrate one or a combination of several of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), Neural-network Processing Unit (NPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content displayed on the screen 830; the NPU is used to implement artificial intelligence (AI) functions; and the modem is used for wireless communication. It is understood that the modem may not be integrated into the processor 810 and can be implemented separately as a computer program product.

[0145] The memory 820 may include random access memory (RAM) or read-only memory (ROM). Optionally, the memory 820 may include a non-transitory computer-readable storage medium. The memory 820 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 820 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the various method embodiments described below, etc.; the data storage area may store data (such as audio data, phone book, etc.) created based on the use of the wearable device 800.

[0146] Display screen 830 is a display component used to display a user interface. Optionally, display screen 830 is a touch-enabled display screen, through which users can use their fingers, styluses, or any suitable object to perform touch operations on display screen 830.

[0147] The display screen 830 is typically located on the front panel of the wearable device 800. The display screen 830 can be designed as a full-screen, curved screen, irregularly shaped screen, dual-sided screen, or foldable screen. The display screen 830 can also be designed as a combination of a full-screen and a curved screen, or a combination of an irregularly shaped screen and a curved screen, etc., but this embodiment does not limit it in this way.

[0148] In addition, those skilled in the art will understand that the structure of the wearable device 800 shown in the above figures does not constitute a limitation on the wearable device 800. The wearable device 800 may include more or fewer components than shown, or combine certain components, or have different component arrangements. For example, the wearable device 800 may also include a Wi-Fi module, an audio acquisition device, a speaker, a radio frequency circuit, an input unit, a sensor, an audio circuit, a Bluetooth module, a power supply, and other components, which will not be described in detail here.

[0149] This application also provides a computer-readable medium storing at least one piece of program code, which is loaded and executed by a processor to implement the interface display method shown in the above embodiments.

[0150] This application also provides a computer program product that stores at least one piece of program code, which is loaded and executed by a processor to implement the interface display method shown in the above embodiments.

[0151] In some embodiments, the computer program product involved in this application may be deployed and executed on a wearable device, or on multiple wearable devices located in one location, or on multiple wearable devices distributed in multiple locations and interconnected through a communication network. Multiple wearable devices distributed in multiple locations and interconnected through a communication network may form a blockchain system.

[0152] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0153] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for displaying an interface, characterized in that, Performed by a wearable device, the wearable device comprising a first system and a second system; the method comprising: The first interface resource file is obtained by converting the first interface resource file of the first target interface through the first system; Display the first target interface using the first system and the first interface resource file; and / or, The second target interface is displayed using the second system and the second interface resource file.

2. The method according to claim 1, characterized in that, The power consumption of the first system is greater than that of the second system; and / or, the performance of the first system is higher than that of the second system.

3. The method according to claim 1 or 2, characterized in that, The process of converting the first interface resource file of the first target interface into a second interface resource file through the first system includes: The first system parses the first interface resource file of the first target interface into interface rendering data. The second interface resource file suitable for the second system is generated based on the interface rendering data.

4. The method according to claim 3, characterized in that, The first interface resource file includes interface element files and style files; The step of parsing the first interface resource file of the first target interface into interface rendering data through the first system includes: The first system parses the interface element file and the style file into renderable interface element information and style information, respectively, and determines the interface element information and style information as the interface rendering data.

5. The method according to claim 1, characterized in that, The method further includes: Store the second interface resource file in the first interface directory of the first system; Before displaying the second target interface through the second system and the second interface resource file, the method further includes: The second system obtains the second interface resource file from the first interface directory of the first system.

6. The method according to claim 1, characterized in that, The method further includes: Store the second interface resource file in the second interface directory of the second system; Before displaying the second target interface through the second system and the second interface resource file, the method further includes: The second interface resource file is obtained from the second interface directory of the second system through the second system.

7. The method according to claim 1, characterized in that, The step of displaying the second target interface through the second system and the second interface resource file includes: The second system parses the second interface resource file to obtain the interface rendering data of the second target interface; The rendered interface displays the data of the second target interface.

8. The method according to claim 7, characterized in that, The step of parsing the second interface resource file through the second system to obtain the interface rendering data of the second target interface includes: The firmware code on the second processor is used to parse the second interface resource file to obtain the interface rendering data of the second target interface. The second processor is used to run the second system.

9. The method according to claim 1, characterized in that, The step of displaying the first target interface through the first system and the first interface resource file includes: The first interface resource file is parsed using logic code on the first processor to obtain interface resource data. The first processor is used to run the first system. Based on the interface resource data, the first target interface is displayed.

10. The method according to claim 1, characterized in that, The power consumption of the first system is less than that of the second system; and / or, the performance of the first system is lower than that of the second system; and / or, the first target interface and the second target interface are completely or partially the same, and the second system cannot parse the resource file of the first interface.

11. The method according to claim 1 or 10, characterized in that, The process of converting the first interface resource file of the first target interface into a second interface resource file through the first system includes: The first system encapsulates the interface rendering data included in the first interface resource file of the first target interface into a resource file. Store the resource file in the second interface resource file.

12. An interface display device, characterized in that, The device is deployed in a wearable device, the wearable device including a first system and a second system; the device includes: The conversion module is used to convert the first interface resource file of the first target interface through the first system to obtain the second interface resource file; The first display module is configured to display the first target interface using the first system and the first interface resource file; and / or, The second display module is used to display the second target interface through the second system and the second interface resource file.

13. A wearable device, characterized in that, The wearable device includes a processor and a memory, the memory storing at least one line of program code, which is loaded and executed by the processor to implement the interface display method as described in any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that, The storage medium stores at least one piece of program code, which is loaded and executed by a processor to implement the interface display method as described in any one of claims 1 to 11.

15. A computer program product, characterized in that, The computer program product stores at least one piece of program code, which is executed by a processor to implement the interface display method as described in any one of claims 1 to 11.

Images